Information processing method and device, electronic equipment, storage medium and computer program product

Abstract

The invention relates to an information processing method and device, electronic equipment, a storage medium and a computer program product. The method comprises the following steps: when a function extension application requests to obtain service information provided for a target account, determining a target service end, and obtaining global authorization information; the target service end is at least one of a plurality of service ends, and the global authorization information represents that the target account has an authority of acquiring service information provided by any service end in the plurality of service ends; simulating and generating a first interaction request of the browser according to a first interaction link between the browser and the target service end; the first interaction request comprises an interaction request carrying global authorization information; sending a first interaction request generated by simulation to the target service end, and triggering the target service end to return corresponding target service information under the condition of determining that the authentication of the target account is passed; and providing the target service information for the function extension application. By adopting the method, the efficiency of acquiring the service information by the function extension application can be improved.

Description

Technical Field

[0001] The present disclosure relates to the technical field of function extension applications, and in particular, to an information processing method, apparatus, electronic device, storage medium, and computer program product. Background Art

[0002] With the development of computer technology, various function extension applications can be used to add various functions to the original application, effectively improving the flexibility and scalability of the application.

[0003] In the related art, when a function extension application needs to obtain business information provided by a certain service end, such as obtaining authorization information provided by Service A, it is necessary to first externally jump to the corresponding browser page, and after the user completes the login operation on the browser page, the business information provided by the specified service end can be obtained.

[0004] However, the above method can only jump to a page with a specific domain name each time it externally jumps to the browser page, and it is impossible to obtain information provided by different service ends at the same time; when the function extension application needs to obtain business information provided by multiple service ends, it is necessary to repeatedly externally jump to different browser pages and the user needs to repeat the login operation. It can be seen that the function extension application in the related art is very inefficient when obtaining business information provided by multiple service ends. Summary of the Invention

[0005] The present disclosure provides an information processing method, apparatus, electronic device, storage medium, and computer program product to at least solve the problem of low efficiency in obtaining business information in the related art. The technical solution of the present disclosure is as follows:

[0006] According to a first aspect of an embodiment of the present disclosure, there is provided an information processing method, including:

[0007] In the case where a function extension application requests to obtain business information provided for a target account, determining a target service end and obtaining global authorization information; the target service end is at least one of multiple service ends, and the global authorization information indicates that the target account has the right to obtain business information provided by any service end among the multiple service ends;

[0008] Simulating and generating a first interaction request of the browser according to a first interaction link pre-acquired between the browser and the target service end; the first interaction request includes an interaction request carrying the global authorization information;

[0009] Sending the simulated first interaction request to the target service end, and triggering the target service end to return corresponding target business information when it is determined that the target account authentication is passed;

[0010] Provide the target service information to the function extension application.

[0011] In an exemplary embodiment, the obtaining of the global authorization information includes:

[0012] Obtain the login information provided by the target account;

[0013] According to a pre-obtained second interaction link between the browser and the authentication center, simulate and generate a second interaction request of the browser; the second interaction request includes an interaction request carrying the login information, and the authentication center is associated with the multiple service terminals;

[0014] Send the simulated and generated second interaction request to the authentication center, and trigger the authentication center to return the global authorization information after determining that the login information is authenticated.

[0015] In an exemplary embodiment, the simulating and generating a second interaction request of the browser according to a pre-obtained second interaction link between the browser and the authentication center includes:

[0016] According to the pre-obtained second interaction link between the browser and the authentication center, sequentially determine the authentication center interaction behaviors that occur between the browser and the authentication center during the process of obtaining the global authorization information;

[0017] Simulate and generate a second interaction request corresponding to the authentication center interaction behavior.

[0018] In an exemplary embodiment, the simulating and generating a second interaction request corresponding to the authentication center interaction behavior includes:

[0019] If the type of the authentication center interaction behavior is an interaction behavior triggered by the browser, simulate and generate a second interaction request corresponding to the authentication center interaction behavior;

[0020] If the type of the authentication center interaction behavior is an interaction behavior executed by the browser in response to the second redirect information returned by the authentication center, simulate and generate a corresponding second interaction request according to the service terminal interaction behavior that occurs on the jump page pointed to by the second redirect information of the browser.

[0021] In an exemplary embodiment, it further includes:

[0022] If the type of the authentication center interaction behavior is an interaction behavior executed by the browser in response to the second redirect information returned by the authentication center, prevent jumping to the jump page pointed to by the second redirect information.

[0023] In an exemplary embodiment, simulating and generating a first interaction request for the browser according to a pre-acquired first interaction link between the browser and the target service end includes:

[0024] According to the first interaction link between the browser and the target service end, sequentially determine the service end interaction behaviors that occur between the browser and the target service end during the process of obtaining service information;

[0025] Simulate and generate a first interaction request corresponding to the service end interaction behavior.

[0026] In an exemplary embodiment, simulating and generating a first interaction request corresponding to the service end interaction behavior includes:

[0027] If the type of the service end interaction behavior is an interaction behavior triggered by the browser, simulate and generate a first interaction request corresponding to the service end interaction behavior;

[0028] If the type of the service end interaction behavior is an interaction behavior executed by the browser in response to the received first redirect information, simulate and generate a corresponding first interaction request according to the service end interaction behavior that occurs on the jump page pointed to by the first redirect information for the browser.

[0029] In an exemplary embodiment, it further includes:

[0030] If the service end interaction behavior is an interaction behavior executed by the browser in response to the received first redirect information, prevent jumping to the jump page pointed to by the first redirect information.

[0031] In an exemplary embodiment, simulating and generating a first interaction request corresponding to the service end interaction behavior includes:

[0032] Obtain the interaction request type corresponding to the service end interaction behavior;

[0033] Determine a target interface corresponding to the interaction request type from a plurality of pre-provided request generation interfaces, and call the target interface to simulate and generate a first interaction request.

[0034] In an exemplary embodiment, when a function extension application requests to obtain service information provided for a target account, determining a target service end and obtaining global authorization information includes:

[0035] Receive an interface call request from the function extension application for an information acquisition interface; the information acquisition interface is provided by an extension application for obtaining service information provided by a service end;

[0036] In response to the interface call request, the extended application for obtaining service information provided by the service side determines the target service side for providing service information to the target account requested by the function extension application, and obtains global authorization information from the authentication center according to the login information corresponding to the target account.

[0037] According to a second aspect of the embodiments of the present disclosure, there is provided an information processing apparatus, including:

[0038] A global authorization acquisition unit, configured to determine a target service side and obtain global authorization information when a function extension application requests to obtain service information provided for a target account; the target service side is at least one of a plurality of service sides, and the global authorization information represents that the target account has the right to obtain service information provided by any service side among the plurality of service sides;

[0039] A first interaction unit, configured to simulate and generate a first interaction request of the browser according to a pre-acquired first interaction link between the browser and the target service side; the first interaction request includes an interaction request carrying the global authorization information;

[0040] A first interaction request sending unit, configured to send the simulated first interaction request to the target service side, and trigger the target service side to return corresponding target service information when it is determined that the target account authentication is passed;

[0041] A service information providing unit, configured to provide the target service information to the function extension application.

[0042] According to a third aspect of the embodiments of the present disclosure, there is provided an electronic device, including:

[0043] A processor;

[0044] A memory for storing executable instructions of the processor;

[0045] Wherein, the processor is configured to execute the instructions to implement the information processing method as described in any one of the above.

[0046] According to a fourth aspect of the embodiments of the present disclosure, there is provided a computer-readable storage medium, when the instructions in the computer-readable storage medium are executed by a processor of an electronic device, enabling the electronic device to execute the information processing method as described in any one of the above.

[0047] According to a fifth aspect of the embodiments of the present disclosure, there is provided a computer program product, the computer program product includes instructions, when the instructions are executed by a processor of an electronic device, enabling the electronic device to execute the information processing method as described in any one of the above.

[0048] The technical solutions provided by the embodiments of the present disclosure at least bring the following beneficial effects:

[0049] On the one hand, by obtaining the global authorization information, the function extension application can obtain the target service information of different target service terminals according to the global authorization information, avoiding the user from repeatedly performing the login operation; on the other hand, by simulating and generating a first interaction request according to the first interaction link between the browser and the target service terminal, it is possible to normally trigger the target service information provided by the service terminal without jumping out to a specific browser page, reducing the operations that the user needs to perform when the function extension application obtains the service information of multiple target service terminals, thereby effectively improving the information acquisition efficiency of the function extension application for obtaining service information from different service terminals.

[0050] It should be understood that the above general description and the following detailed description are only exemplary and explanatory, and cannot limit the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0051] The accompanying drawings herein are incorporated into the specification and constitute a part of this specification, showing embodiments consistent with the present disclosure and, together with the specification, are used to explain the principles of the present disclosure and do not constitute an improper limitation of the present disclosure.

[0052] Figure 1 is an application environment diagram of an information processing method shown according to an exemplary embodiment.

[0053] Figure 2 is a flowchart of an information processing method shown according to an exemplary embodiment.

[0054] Figure 3 is a timing diagram of an interaction link shown according to an exemplary embodiment.

[0055] Figure 4 is a flowchart of steps for obtaining global authorization information shown according to an exemplary embodiment.

[0056] Figure 5 is a logical schematic diagram for obtaining service information of different service terminals shown according to an exemplary embodiment.

[0057] Figure 6 is a block diagram of an information processing device shown according to an exemplary embodiment.

[0058] Figure 7 is a block diagram of an electronic device shown according to an exemplary embodiment. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0059] In order to enable those of ordinary skill in the art to better understand the technical solutions of the present disclosure, the technical solutions in the embodiments of the present disclosure will be clearly and completely described below with reference to the accompanying drawings.

[0060] It should be noted that the terms "first", "second", etc. in the specification and claims of the present disclosure and the above-mentioned drawings are used to distinguish similar objects, and do not necessarily have to be used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged under appropriate circumstances, so that the embodiments of the present disclosure described here can be implemented in an order other than those illustrated or described here. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present disclosure. On the contrary, they are only examples of devices and methods consistent with some aspects of the present disclosure as detailed in the appended claims.

[0061] It should also be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data for display, data for analysis, etc.) involved in the present disclosure are all information and data authorized by the user or fully authorized by all parties.

[0062] In order to enable those skilled in the art to better understand the present disclosure, the related technologies will be introduced below.

[0063] With the development of computer technology, various function extension applications can be used to add various functions to the original application, effectively improving the flexibility and expandability of the application. Taking a certain code editor used in the data processing process as an example, this code editor has the characteristics of being lightweight, high-performance, and easy to expand. With the help of various function extension applications, various functions can be efficiently and flexibly added to the open-source code editor. For example, function extension application P1 can help maintain the consistency of the code style, function extension application P2 can automatically format the code, and function extension application P3 can preview the web page effect in real time. Through the above-mentioned various function extension applications, the editor function can be quickly enhanced.

[0064] When a function extension application needs to obtain business information provided by a certain service end (such as obtaining authorization information provided by Service A), since it is in a non-browser scenario and cannot directly complete the login on the function extension application, the related technology is to first jump from the function extension application to the browser page corresponding to the specified service end (that is, leave the page of the current function extension application and open a browser page). After the user successfully logs in by performing a series of login operations on this browser page, the business information provided by this service end can be obtained through the browser, and then the obtained business information is passed back to the function extension application as a parameter and jumps back to the function extension application.

[0065] However, the above method can only jump to the domain name page of a specific service end every time the browser page jumps outwards, and it is impossible to obtain the information provided by different service ends at the same time. When the function expansion application needs to obtain the information provided by multiple services, it is necessary to jump outwards to different browser pages repeatedly, and the user needs to repeat the login operation; moreover, during a single login process, the user needs to perform operations at multiple operation nodes. It can be seen that in the related technology, when the function expansion application obtains the service information provided by multiple service ends for the user, the process is cumbersome, and the user also needs to perform multiple repeated and cumbersome login operations, and the information acquisition efficiency is very low.

[0066] The present disclosure provides an information processing method, apparatus, electronic device, storage medium, and computer program product to at least solve the problem of low efficiency in obtaining service information of different service ends by a function expansion application in the related technology. The resource information processing method provided by the present disclosure can be applied to an application environment as Figure 1 shown. In this application environment, it includes a terminal, a service end, and an authentication center. Among them, a function expansion application is deployed on the terminal, and the service end can be multiple or one; the terminal, the service end, and the authentication center can communicate with each other through a network, and the service end and the authentication center can have corresponding data storage systems, and the data storage systems can store the data that the service end and the authentication center need to process. In actual applications, the data storage systems can be integrated on the service end and the authentication center, or placed on the cloud or other network servers.

[0067] In the present disclosure, in the case where the function expansion application requests to obtain the service information provided for the target account, the terminal can determine the corresponding target service end and obtain the global authorization information; where the target service end is at least one of multiple service ends, and the global authorization information indicates that the target account has the permission to obtain the service information provided by any service end among the multiple service ends; then the terminal can simulate and generate a first interaction request of the browser according to the first interaction link between the pre-obtained browser and the target service end, and the first interaction request includes an interaction request carrying the global authorization information; furthermore, the terminal can send the first interaction request to the target service end to trigger the target service end to return the corresponding target service information when it determines that the target account authentication is passed; then the terminal can provide the target service information to the function expansion application.

[0068] Among them, the terminal can be, but is not limited to, various personal computers, laptop computers, smart phones, tablet computers, Internet of Things devices, and portable wearable devices. The Internet of Things devices can be smart speakers, smart TVs, smart air conditioners, smart in-vehicle devices, etc., and the portable wearable devices can be smart watches, smart bracelets, head-mounted devices, etc. The authentication center and the service end can be implemented by independent servers or a server cluster composed of multiple servers.

[0069] Figure 2 is a flowchart of an information processing method shown according to an exemplary embodiment. As Figure 2 shown, this information processing method is used in a terminal and includes the following steps.

[0070] In step S210, when a function extension application requests to obtain service information provided for a target account, determine a target service end, and obtain global authorization information; the target service end is at least one of multiple service ends, and the global authorization information indicates that the target account has the right to obtain service information provided by any service end among the multiple service ends.

[0071] In specific implementation, the function extension application can request to obtain service information provided for the target account. In some embodiments, the function extension application can include function plugins for expanding application functions. The function extension application can be applied to one or more nodes in the service process. For example, taking the data process A as an example, this data process includes multiple nodes A1, A2, and A3, and the user can complete the tasks of each node such as A1, A2, and A3 with the help of one or more function extension applications. For the same function extension application, it may involve obtaining service information provided by one or more service ends. For example, at node A1 of the data process, it involves obtaining the service information of service end A, and at node A2, it involves obtaining the service information of service end A and service end B.

[0072] The service information can be understood as one or more types of information provided by the service end to the target account. In some alternative embodiments, the service information can be authorization information provided by the service end, such as an authorization cookie (an authentication data provided for identifying the account identity) or an authorization token provided by the service end, or it can also be other service resources provided by the service end. For example, it can be one or more of text resources, audio resources, and video resources.

[0073] In this step, when it is detected that the function extension application requests to obtain service information provided for the target account, the terminal can determine at least one target service end that provides service information for the target account and obtain global authorization information. In some embodiments, when the function extension application requests to obtain service information provided for the target account, it can first determine whether the global authorization information has been obtained. For example, it can query whether the previously obtained global authorization information is stored locally.

[0074] If so, the obtained global authorization information can be read. If not, the global authorization information can be obtained in real time. For example, the global authorization information can be obtained from the authentication center according to the login information provided by the target account. In one example, the terminal can send the login information corresponding to the target account to the authentication center, and the authentication center can authenticate whether the target account is legal according to the received login information. If the authentication is passed, the global authorization information is returned. If the authentication fails, the information of refusing authorization can be returned.

[0075] It can be understood that since the global authorization information indicates that the target account has the permission to obtain the service information provided by any service end among multiple service ends, after obtaining the global authorization information, requests can be sent to any service end among multiple service ends for the target account multiple times within the valid period of the global authorization information to obtain the service information.

[0076] In step S220, according to the first interaction link between the browser and the target service end obtained in advance, a first interaction request of the browser is simulated; the first interaction request includes an interaction request carrying the global authorization information.

[0077] Among them, the interaction link between the browser and the target service end can represent the interaction process between the browser and the target service end and the interaction requests sent by the browser during the process of the browser obtaining the target service information from the target service end. For the convenience of distinction, the interaction link between the browser and the target service end is called the first interaction link.

[0078] In the related art, within the function extension application end, when some authentication and authorization processing needs to be done, the function extension application will be jumped out first, and then a browser page will be opened for authorization, and then it will jump back to the function extension application end. The reason for this processing is that during the login authorization process, there are often some redirects with a 302 status code, and the function extension application end does not support redirects. Therefore, it will be externally jumped to the browser end in some ways. After obtaining the authentication token through authorization on the browser page, it will carry the token and jump back to the function extension application end to complete the subsequent operations.

[0079] In this regard, this embodiment can obtain the first interaction link corresponding to each service end in advance. Figure 3 The first interaction link between the browser and the App service end is shown. Only one App service end in the figure is an example. In actual applications, the service end can be one or more. For the convenience of understanding, Figure 3 The interaction link between the browser and the service end is shown in the form of a sequence diagram. In the specific implementation, the first interaction link can be recorded in the form of code or interaction link configuration information. It can be understood that the first interaction link can be obtained before generating the first interaction request, so as to guide the generation of the first interaction request through the first interaction link.

[0080] Furthermore, after determining the target service end, the first interaction link corresponding to the target service end can be determined. According to the first interaction link, each interaction request involved in the browser obtaining the target service information from the target service end is simulated and generated. For the sake of distinction, this interaction request is called the first interaction request. The first interaction request can be one or more. Among the simulated and generated first interaction requests, at least one interaction request carries global authorization information, so that the target service end receiving the first interaction request can authenticate the target account according to the interaction request carrying the global authorization information. Take Figure 3 the interaction link shown as an example. For the first interaction link between the browser and the App, the first interaction request simulated and generated by the terminal can include a GET-type interaction request, and this interaction request carries global authorization information, such as "ticket=12345678".

[0081] It can be understood that in this step, by simulating and generating the first interaction request sent by the browser according to the first interaction link, on the one hand, there is no need to jump to the browser page corresponding to the specific service end, and on the other hand, without the user performing the login operation on the browser page corresponding to the service end, the first interaction request for the target service end can also be normally generated, thereby triggering the subsequent processing of the target service end.

[0082] In step S230, the simulated and generated first interaction request is sent to the target service end, triggering the target service end to return the corresponding target service information when it is determined that the target account authentication is passed.

[0083] In this step, the simulated and generated first interaction request can be sent to the target service end. After receiving the first interaction request, the target service end can authenticate the target account according to the interaction request carrying the global authorization information. When the authentication is passed, the corresponding target service information can be provided to the terminal, such as the authorization information of the target service end or other service resources.

[0084] In some embodiments, as Figure 3 shown, after sending the first interaction request carrying the global authorization information to the target service end (App), if the global authorization carried therein is authenticated by the target service end, the target service end can return the service end authorization information corresponding to the target service end. The terminal can continue to simulate and generate the first interaction request carrying this service end authorization information according to the first interaction link and send it to the target service end, so that the target service end can provide the corresponding service resources according to the service end authorization information carried in the first interaction request.

[0085] In step S240, the target service information is provided to the function extension application.

[0086] After obtaining the target service information provided by the target service end, the service information can be provided to the function extension application.

[0087] In the above information processing method, when the function extension application requests to obtain the service information provided for the target account, the target service end is determined, and the global authorization information is obtained; the target service end is at least one of multiple service ends, and the global authorization information represents that the target account has the right to obtain the service information provided by any service end among the multiple service ends; then, according to the first interaction link between the browser and the target service end obtained in advance, a first interaction request of the browser is simulated and generated, and the interaction request carried with the global authorization information is included in the first interaction request; furthermore, the simulated first interaction request is sent to the target service end, triggering the target service end to return the corresponding target service information when it is determined that the target account authentication is passed, and providing the target service information to the function extension application. In this embodiment, on the one hand, by obtaining the global authorization information, the function extension application can obtain the target service information of different target service ends according to the global authorization information, avoiding the user from repeatedly performing the login operation; on the other hand, by simulating and generating the first interaction request according to the first interaction link between the browser and the target service end, it is possible to normally trigger the service end to provide the target service information without jumping out to a specific browser page, reducing the operations that the user needs to perform when the function extension application obtains the service information of multiple target service ends, thereby effectively improving the information acquisition efficiency of the function extension application for obtaining service information from different service ends.

[0088] In addition, when the function extension application obtains the information of the specified service end, in the related technology, since it is necessary to jump out of the function extension application to the browser page and then jump back to the function extension application from the browser page, the user will feel that the front and back operations are relatively disjointed, that is, in the process of the function extension application obtaining the resource information, there is an obvious sense of disconnection between the front and back links, the process coherence is insufficient, and the connection between the links is rigid. In this embodiment, by simulating and generating the first interaction request according to the first interaction link, it is possible to normally obtain the service information of the target service end without jumping out to the browser page, improving the fluency and coherence of the whole process of the function extension application obtaining the service information, and effectively optimizing the user experience.

[0089] In an exemplary embodiment, as Figure 4 shown, in step S210, obtaining the global authorization information may include the following steps:

[0090] In step S410, obtain the login information provided by the target account.

[0091] Among them, the login information may be the information used when the authentication center authenticates the target account.

[0092] In a specific implementation, such as Figure 5 shown, the target account can provide login information. Exemplarily, the login information can be input by the user through the target account, such as inputting an account identifier and a login password. In some other examples, the login information can also be verification information sent in real time, such as a verification code, or can be the login information of the target account obtained by scanning a code for login.

[0093] In step S420, according to a second interaction link between the browser and the authentication center obtained in advance, a second interaction request of the browser is simulated and generated; the second interaction request includes an interaction request carrying the login information, and the authentication center is associated with multiple service terminals.

[0094] Among them, the interaction link between the browser and the authentication center can represent the interaction process between the browser and the authentication center and the interaction requests sent by the browser during the process of the browser obtaining global authorization information from the authentication center. For the convenience of distinction, the interaction link between the browser and the authentication center is called the second interaction link.

[0095] In practical applications, multiple service terminals and an authentication center associated with the multiple service terminals can be set. Among them, each service terminal in the multiple service terminals trusts the authentication center. When an account successfully logs in to the authentication center using its login information, it can obtain global authorization information from the authentication center. In one example, it can be obtaining a ticket-granting cookie from the authentication center. The global authorization information can include the identification information and authorization information corresponding to the account, and subsequent authentication and authorization can be performed on the associated multiple service terminals through the global authorization information. In this embodiment, the terminal can obtain the second interaction link between the browser and the authentication center in advance. Figure 3 Shows the second interaction link between the browser and the authentication center. For the convenience of understanding, Figure 3 the second interaction link between the browser and the authentication center is shown in the form of a sequence diagram. In a specific implementation, the second interaction link can be recorded in the form of code or interaction link configuration information. It can be understood that the second interaction link is obtained before generating the second interaction request, so as to guide the generation of the second interaction request through the second interaction link.

[0096] Furthermore, when requesting to obtain global authorization information, the second interaction link with the authentication center can be determined, and according to the second interaction link, each interaction request involved in the browser obtaining global authorization information from the authentication center is simulated and generated. For the convenience of distinction, this interaction request is called the second interaction request.

[0097] Among them, the second interaction requests can be one or more. Among the second interaction requests generated by simulation, at least one interaction request carrying login information is included, so that the authentication center receiving the second interaction request can authenticate the target account according to the interaction request carrying login information. For Figure 3 Taking the interaction link shown in Figure 3 as an example, for the second interaction link between the browser and the authentication center, the second interaction requests simulated and generated by the terminal can include interaction requests of the GET type and interaction requests of the POST type. Among them, the interaction requests of the POST type can carry login information such as account identifiers, passwords, and login tickets.

[0098] In step S430, send the second interaction requests simulated and generated to the authentication center, triggering the authentication center to return global authorization information after determining that the login information authentication is passed.

[0099] After obtaining the second interaction requests, the second interaction requests simulated and generated can be sent to the authentication center. After receiving the second interaction requests, the authentication center can authenticate the target account according to the interaction requests carrying login information among them. In the case of successful authentication, global authorization information can be provided to the terminal. Subsequently, target service information can be obtained from different service ends based on the global authorization information. For example, the target service information provided by one or more of Service A, Service B, and Service C can be obtained successively or simultaneously based on this global authorization information.

[0100] In this embodiment, by simulating and generating the second interaction requests sent by the browser according to the second interaction link, it is not necessary to jump to the browser page corresponding to the authentication center, nor is it necessary for the user to perform a login operation on the browser page corresponding to the authentication center, so that the login in the authentication center can be completed. While reducing the number of browser page jumps and logins, the number of user operations is reduced, and the efficiency of the user's login and obtaining global authorization information is improved.

[0101] In an exemplary embodiment, in step S420, according to the second interaction link between the browser and the authentication center obtained in advance, simulating and generating the second interaction requests of the browser may include the following steps:

[0102] According to the second interaction link between the browser and the authentication center obtained in advance, successively determine the authentication center interaction behaviors that occur between the browser and the authentication center during the process of obtaining global authorization information; simulate and generate the second interaction requests corresponding to the authentication center interaction behaviors.

[0103] In practical applications, when the browser requests to obtain global authorization information from the authentication center, the browser may sequentially perform multiple interaction behaviors. To facilitate the distinction from other interaction behaviors in the following text, the interaction behaviors that occur between the browser and the authentication center during the process of obtaining global authorization information are referred to as authentication center interaction behaviors. Specifically, the browser can first attempt to log in to the authentication center. In the case of failing to successfully log in to the authentication center, the browser will obtain the login information entered by the user in the corresponding login interface of the authentication center and then send it to the authentication center to attempt to log in again.

[0104] In this regard, in this embodiment, the terminal can sequentially determine the authentication center interaction behaviors that occur between the browser and the authentication center during the process of obtaining global authorization information according to the pre-obtained second interaction link between the browser and the authentication center, and then simulate and generate a second interaction request corresponding to the determined authentication center interaction behavior. Among them, the corresponding second interaction request can be understood as an interaction request used to implement the authentication center interaction behavior. For example, when it is necessary to send login information to the authentication center, the type of the corresponding second interaction request can be a POST type request, and the second interaction request carrying the login information is sent to the authentication center through this request.

[0105] In this embodiment, by sequentially determining the authentication center interaction behaviors that occur between the browser and the authentication center during the process of obtaining global authorization information and sending the corresponding second interaction requests, it is possible to accurately simulate each process of the browser obtaining global authorization information in the background, so that the global authorization information can be normally obtained without jumping out to the browser page and without the user performing a trigger operation.

[0106] In an exemplary embodiment, simulating and generating a second interaction request corresponding to the authentication center interaction behavior may include the following steps:

[0107] If the type of the authentication center interaction behavior is an interaction behavior triggered by the browser, then simulate and generate a second interaction request corresponding to the authentication center interaction behavior; if the type of the authentication center interaction behavior is an interaction behavior executed by the browser in response to the second redirect information returned by the authentication center side, then simulate and generate a corresponding second interaction request according to the business-side interaction behavior that occurs on the jump page pointed to by the second redirect information of the browser.

[0108] In a specific implementation, the interaction behaviors of the authentication center can be divided into two types. One is the interaction behavior actively triggered by the browser, such as the browser actively triggering an attempt to log in to the authentication center; the other is the interaction behavior executed by the browser in response to the redirect information returned by the authentication center end. Among them, the redirect information can be information indicating that an application (such as a browser or other application / program with redirect capabilities) redirects to a specified page. For the convenience of distinguishing from other redirect information, the redirect information provided by the authentication center is called the second redirect information.

[0109] In this embodiment, if it is determined that the interaction behavior of the authentication center is the interaction behavior actively triggered by the browser, a second interaction request corresponding to the interaction behavior of the authentication center can be directly simulated and generated. If the interaction behavior of the authentication center is the interaction behavior executed by the browser in response to the second redirect information returned by the authentication center end, for example Figure 3 receiving the second redirect information ( Figure 3 "redirect to the specified page" indicated by the authentication center) returned by the authentication center, the jump page pointed to by the second redirect information can be first identified, and then the business-side interaction behavior that the browser will have on the jump page can be predicted according to the second interaction link, and then the corresponding second interaction request can be simulated and generated accordingly.

[0110] In this embodiment, if the type of the interaction behavior of the authentication center is the interaction behavior triggered by the browser, the second interaction request can be directly simulated and generated, so that the interaction with the authentication center can be actively triggered; if the type of the interaction behavior of the authentication center is the interaction behavior executed by the browser in response to the second redirect information returned by the authentication center end, the second interaction request is simulated through the business-side interaction behavior that the browser has on the pointed jump page, so that a matching second interaction request can be generated accordingly as the page content changes, and the subsequent interaction behavior can be accurately and smoothly continued.

[0111] In an exemplary embodiment, the method may further include the following steps:

[0112] If the type of the interaction behavior of the authentication center is the interaction behavior executed by the browser in response to the second redirect information returned by the authentication center end, prevent the jump to the jump page pointed to by the second redirect information.

[0113] In practical applications, when receiving the second redirect information returned by the authentication center, related technologies will respond to the second redirect information and display the corresponding jump page. However, in this embodiment, since the corresponding interaction behavior can be normally triggered and executed by simulating an interaction request, there is no need to externally jump to the browser page or for the user to perform a triggering operation. Therefore, when receiving the second redirect information, it is possible to prevent or intercept the jump to the jump page pointed to by the second redirect information, while ensuring that subsequent operations are normally triggered and increasing the fluency of the entire business information acquisition process, and can avoid additional network resource consumption.

[0114] In one exemplary embodiment, in step S220, according to the first interaction link between the pre-acquired browser and the target service end, simulating and generating a first interaction request of the browser may include the following steps:

[0115] According to the first interaction link between the browser and the target service end, sequentially determine the service end interaction behaviors that occur between the browser and the target service end during the process of obtaining service information; simulate and generate a first interaction request corresponding to the service end interaction behavior.

[0116] In specific implementation, when the browser requests to obtain global authorization information from the target service end, the browser may sequentially execute multiple interaction behaviors. To facilitate distinction from other interaction behaviors, the interaction behaviors that occur between the browser and the target service end during the process of obtaining the target service information are referred to as service end interaction behaviors. Specifically, after obtaining the global authorization information, the browser may first attempt to log in to the target service end based on the global authorization information. In the case of successfully logging in to the target service end, the browser will continue to attempt to obtain the service end page of the target service end.

[0117] In this regard, in this embodiment, the terminal can sequentially determine the service end interaction behaviors that occur between the browser and the target service end during the process of service information according to the pre-acquired first interaction link between the browser and the target service end, and then simulate and generate a first interaction request corresponding to the service end interaction behavior. Among them, the corresponding first interaction request can be understood as an interaction request for implementing the service end interaction behavior. For example, when it is necessary to log in to the target service end, the corresponding second interaction request can be a GET type request carrying the global authorization information.

[0118] In this embodiment, by sequentially determining the service end interaction behaviors that occur between the browser and the target service end during the process of obtaining service information and sending the corresponding first interaction request, it is possible to accurately simulate various processing operations of the browser obtaining service information from the target service end in the background, so that the service information of the service end can be normally obtained without externally jumping to the browser page corresponding to the service end and without the user performing a triggering operation.

[0119] In an exemplary embodiment, simulating and generating a first interaction request corresponding to the interaction behavior with the service end may include the following steps:

[0120] If the type of the interaction behavior with the service end is an interaction behavior triggered by a browser, then simulate and generate a first interaction request corresponding to the interaction behavior with the service end; if the type of the interaction behavior with the service end is an interaction behavior executed by the browser in response to the received first redirect information, then according to the interaction behavior with the service end that occurs on the jump page pointed to by the first redirect information by the browser, simulate and generate a corresponding first interaction request.

[0121] In practical applications, the interaction behavior with the service end can be divided into two types. One is an interaction behavior actively triggered by a browser, such as actively triggering an attempt to log in to the authentication center by the browser; the other is an interaction behavior executed by the browser in response to the returned first redirect information. Among them, for the convenience of distinguishing from other redirect information, the redirect information received during the process of obtaining service information is called the first redirect information.

[0122] In this embodiment, if it is determined that the interaction behavior with the service end is an interaction behavior actively triggered by a browser, then a first interaction request corresponding to the interaction behavior with the service end can be directly simulated and generated. If the interaction behavior with the service end is an interaction behavior executed by the browser in response to the received first redirect information, such as Figure 3 in obtaining the first redirect information returned by the target service end App ( Figure 3 "redirect to the specified page" indicated by the service end App in the example), then the jump page pointed to by the first redirect information can be first identified, and then according to the interaction behavior with the service end that occurs on this jump page predicted by the first interaction link, a corresponding second interaction request can be simulated and generated accordingly.

[0123] In this embodiment, if the type of the interaction behavior with the service end is an interaction behavior triggered by a browser, then a first interaction request can be directly simulated and generated to actively trigger the interaction with the target service end; if the type of the authentication center interaction behavior is an interaction behavior executed by the browser in response to the received first redirect information, by predicting the interaction behavior with the service end that occurs on the pointed jump page and simulating the first interaction request, a matching first interaction request can be generated accordingly as the page content changes, and the subsequent interaction behavior with the target service end can be accurately and smoothly continued.

[0124] In an exemplary embodiment, the method may further include the following steps:

[0125] If the interaction behavior with the service end is an interaction behavior executed by the browser in response to the received first redirect information, prevent jumping to the jump page pointed to by the first redirect information.

[0126] In the related art, after receiving the first redirect message, the corresponding jump page will be responded to and displayed. However, in this embodiment, since the interaction behavior with the target service end can be normally triggered by simulating an interaction request, there is no need to externally jump to the browser page and no need for the user to perform a triggering operation. Therefore, when receiving the first redirect message, it is possible to block or intercept the jump to the jump page pointed to by the first redirect message, while ensuring that subsequent operations are normally triggered, increasing the fluency of the entire business information acquisition process, and avoiding additional network resource consumption.

[0127] In an exemplary embodiment, simulating and generating a first interaction request corresponding to the interaction behavior with the service end may include the following steps:

[0128] Obtain the interaction request type corresponding to the interaction behavior with the service end; determine the target interface corresponding to the interaction request type from a plurality of pre-provided request generation interfaces, and call the target interface to simulate and generate the first interaction request.

[0129] In some embodiments, the first interaction request and the second interaction request can be simulated and generated through a headless browser. The headless browser can simulate and send corresponding interaction requests according to the link logic of the browser without displaying the browser page. By using the headless browser, the user is unaware of the process of jumping to the browser. For the user, the entire login link is completed at the function extension application end, which can effectively optimize the user experience. In some cases, the headless browser needs to use a specified browser kernel, and the browser kernel versions relied on by different operating systems are different. In this regard, the function extension application layer can detect whether the specified browser kernel already exists locally on the terminal. If not, the operating system can obtain the corresponding kernel resource package from the CDN.

[0130] However, it is found in practice that in the above method, due to the high implementation cost of caching business data, including the need to determine whether the cached business data has expired, and the lack of a general judgment interface, the service end needs to separately judge whether the cached business data of each has expired, resulting in the need to repeat the above complete information acquisition process each time business information is obtained to obtain the cached business data, causing unnecessary time consumption, and the acquisition time is relatively long, and the overall interaction duration needs to be shortened and optimized.

[0131] In response to this, in this embodiment, a plurality of pre-provided request generation interfaces can be determined. For example, various request generation interfaces provided by a network request library can be used, and the plurality of request generation interfaces can respectively generate different types of browser requests. Furthermore, after determining the interaction behavior with the service end, the interaction request type corresponding to the interaction behavior with the service end can be obtained, such as the GET type or the POST type, etc. Then, the target interface corresponding to the interaction request type can be determined from the plurality of pre-provided request generation interfaces, and the target interface can be called to simulate and generate the first interaction request.

[0132] Since the time taken to execute the interaction behavior can be approximated as the sum of the response durations of the request generation interfaces, and the request generation interfaces can often respond quickly. In this embodiment, by calling the corresponding target interface to simulate the generation of the first interaction request, the time taken to execute the interaction behavior on the service side (such as the login time on the service side) can be greatly reduced, and the efficiency of obtaining the target service information can be improved. It can be understood that when generating the first interaction request, it can also be simulated and generated by calling the corresponding target interface. Specifically, the interaction request type corresponding to the authentication center interaction behavior can be obtained; the target interface corresponding to the interaction request type is determined from multiple pre-provided request generation interfaces, and the target interface is called to simulate the generation of the second interaction request. Thus, the time taken to execute the authentication center interaction behavior (such as the login time in the authentication center) can be greatly reduced, and the efficiency of obtaining the global authorization information can be improved. Compared with the time taken to simulate the login process through a headless browser, which is more than 10 seconds, by calling the target interface to generate the interaction request, the overall login time can be controlled within 2 seconds, and at the same time, there is no need to consider the compatibility issues between different operating systems, effectively improving the versatility of this method.

[0133] In an exemplary embodiment, in step S210, when the function extension application requests to obtain the service information provided for the target account, determining the target service side and obtaining the global authorization information may include the following steps:

[0134] Receiving an interface call request from the function extension application for the information acquisition interface; the information acquisition interface is provided by the extension application for obtaining the service information provided by the service side; in response to the interface call request, the extension application for obtaining the service information provided by the service side determines the target service side for which the function extension application requests to provide the service information for the target account, and obtains the global authorization information from the authentication center according to the login information corresponding to the target account.

[0135] In this embodiment, an extension application for obtaining the service information provided by the service side can be deployed on the terminal, and the extension application simulates the generation of interaction requests between the browser and the authentication center. In some examples, the extension application for obtaining the service information provided by the service side can be deployed on the terminal in the form of a plugin, and this plugin can also be called a single sign-on plugin.

[0136] In practical applications, the function extension application can be divided into a webview end and an extension end. Among them, the extension end can be understood as a running environment that can parse and execute target-type code, such as a lightweight running environment. There are various types of UI (User Interface) frameworks for the implementation of the webview end, and the login components designed based on different UI frameworks cannot be universal. When encapsulating the execution logic from step S210 to step S230 into a login component using UI framework 1, if the webview of function extension application P4 is also built with UI framework 1, it can be directly used. If the webview of function extension application P5 is built with UI framework 2, since it is different from UI framework 1 used by the login component, it will cause function extension application P5 to be unable to use the same login component properly, that is, there is a problem that it cannot be directly reused due to different technology stacks, affecting the universality of the login component.

[0137] In response to this, the execution logic from step S210 to step S230 can be encapsulated into an extension application for obtaining business information provided by the business end and deployed on the terminal. In other words, one or more of the foregoing embodiments in the present disclosure can be applied to this extension application deployed on the terminal. This extension application can provide an information acquisition interface that can be called by any function extension application. Since this extension application is encapsulated based on target-type code, and the extension ends of multiple function extension applications have the same or similar running environments, they can all communicate with this extension application and call its interface. After sending a call request to the information acquisition interface, this extension application can be called and this extension application can execute the processing from step S210 to step S230.

[0138] In this embodiment, specifically, it can be detected whether there is a function extension application sending an interface call request to the information acquisition interface. When an interface call request is detected, the extension application for obtaining business information provided by the business end can be called. This extension application determines the target business end requested by the function extension application for providing business information for the target account, and the information acquisition plugin obtains the global authorization information from the authentication center according to the login information corresponding to the target account.

[0139] In this embodiment, by setting up an extended application for obtaining service information provided by the service side and providing a corresponding information acquisition interface for other function extension applications to call, rather than using the form of a resource package for access, it is possible to determine the target service side and trigger the acquisition of global authorization information through this extended application after receiving an interface call request, effectively solving the problem of non-reusability caused by different UI frameworks in the web view layer of function extension applications, and improving the generality and reusability of the present disclosure. In addition, the information acquisition plug-in is based on a set of general permission authentication systems, which can enhance the linkage between function extension applications in different departments. Only by logging in to the information acquisition plug-in once, different function extension applications can share the global authorization information of the information acquisition plug-in to obtain the service information they need, greatly improving the service information acquisition efficiency and effectively optimizing the user experience.

[0140] Based on the same inventive concept, an embodiment of the present disclosure also provides an information processing apparatus for implementing the information processing method involved above.

[0141] Figure 6 It is a block diagram of an information processing apparatus shown according to an exemplary embodiment. Referring to Figure 6 , the apparatus includes:

[0142] A global authorization acquisition unit 610, configured to determine a target service side and acquire global authorization information when a function extension application requests to acquire service information provided for a target account; the target service side is at least one of multiple service sides, and the global authorization information indicates that the target account has the permission to acquire service information provided by any service side among the multiple service sides;

[0143] A first interaction unit 620, configured to simulate and generate a first interaction request of the browser according to a first interaction link between the pre-acquired browser and the target service side; the first interaction request includes an interaction request carrying the global authorization information;

[0144] A first interaction request sending unit 630, configured to send the simulated first interaction request to the target service side, triggering the target service side to return corresponding target service information when it determines that the target account authentication is passed;

[0145] A service information providing unit 640, configured to provide the target service information to the function extension application.

[0146] In an exemplary embodiment, the global authorization acquisition unit 610 is configured to execute:

[0147] Acquire the login information provided by the target account;

[0148] Simulate and generate a second interaction request of the browser according to a pre-acquired second interaction link between the browser and the authentication center; the second interaction request includes an interaction request carrying the login information, and the authentication center is associated with the multiple service terminals;

[0149] Send the simulated second interaction request to the authentication center, and trigger the authentication center to return the global authorization information after determining that the login information is authenticated successfully.

[0150] In an exemplary embodiment, the global authorization acquisition unit 610 is configured to execute:

[0151] According to a pre-acquired second interaction link between the browser and the authentication center, sequentially determine the authentication center interaction behaviors that occur between the browser and the authentication center during the process of obtaining the global authorization information;

[0152] Simulate and generate a second interaction request corresponding to the authentication center interaction behavior.

[0153] In an exemplary embodiment, the global authorization acquisition unit 610 is configured to execute:

[0154] If the type of the authentication center interaction behavior is an interaction behavior triggered by the browser, simulate and generate a second interaction request corresponding to the authentication center interaction behavior;

[0155] If the type of the authentication center interaction behavior is an interaction behavior executed by the browser in response to the second redirect information returned by the authentication center end, simulate and generate a corresponding second interaction request according to the service terminal interaction behavior that occurs on the jump page pointed to by the second redirect information of the browser.

[0156] In an exemplary embodiment, the global authorization acquisition unit 610 is configured to execute:

[0157] If the type of the authentication center interaction behavior is an interaction behavior executed by the browser in response to the second redirect information returned by the authentication center end, prevent the jump to the jump page pointed to by the second redirect information.

[0158] In an exemplary embodiment, the first interaction unit 620 is configured to execute:

[0159] According to a first interaction link between the browser and the target service terminal, sequentially determine the service terminal interaction behaviors that occur between the browser and the target service terminal during the process of obtaining the service information;

[0160] Simulate and generate a first interaction request corresponding to the service terminal interaction behavior.

[0161] In an exemplary embodiment, the first interaction unit 620 is configured to perform:

[0162] If the type of the service-side interaction behavior is an interaction behavior triggered by the browser, a first interaction request corresponding to the service-side interaction behavior is simulated and generated;

[0163] If the type of the service-side interaction behavior is an interaction behavior performed by the browser in response to the received first redirect information, a corresponding first interaction request is simulated and generated according to the service-side interaction behavior that occurs on the jump page pointed to by the first redirect information by the browser.

[0164] In an exemplary embodiment, the first interaction unit 620 is configured to perform:

[0165] If the service-side interaction behavior is an interaction behavior performed by the browser in response to the received first redirect information, prevent jumping to the jump page pointed to by the first redirect information.

[0166] In an exemplary embodiment, the first interaction unit 620 is configured to perform:

[0167] Obtain the interaction request type corresponding to the service-side interaction behavior;

[0168] Determine a target interface corresponding to the interaction request type from a plurality of pre-provided request generation interfaces, and call the target interface to simulate and generate a first interaction request.

[0169] In an exemplary embodiment, the global authorization acquisition unit 610 is configured to perform:

[0170] Receive an interface call request of a function extension application for an information acquisition interface; the information acquisition interface is provided by an extension application for acquiring service information provided by a service side;

[0171] In response to the interface call request, the extension application for acquiring service information provided by the service side determines a target service side for providing service information for the target account requested by the function extension application, and obtains global authorization information from the authentication center according to the login information corresponding to the target account.

[0172] Regarding the device in the above embodiments, the specific manners in which each module performs operations have been described in detail in the embodiments related to the method, and will not be elaborated herein.

[0173] Each module in the above information processing device can be implemented in whole or in part by software, hardware, or a combination thereof. Each of the above modules can be embedded in the processor of the computer device in hardware form or be independent of it, or stored in the memory of the computer device in software form, so that the processor can call and execute the operations corresponding to each of the above modules.

[0174] Figure 7 FIG. 4 is a block diagram of an electronic device 700 for implementing an information processing method according to an exemplary embodiment. For example, the electronic device 700 can be a mobile phone, a computer, a digital broadcast terminal, a messaging device, a game console, a tablet device, a medical device, a fitness device, a personal digital assistant, etc.

[0175] Referring to Figure 7 , the electronic device 700 can include one or more of the following components: a processing component 702, a memory 704, a power supply component 706, a multimedia component 708, an audio component 710, an input / output (I / O) interface 712, a sensor component 714, and a communication component 716.

[0176] The processing component 702 generally controls the overall operation of the electronic device 700, such as operations associated with display, telephone call, data communication, camera operation, and recording operation. The processing component 702 can include one or more processors 720 to execute instructions to complete all or part of the steps of the above method. In addition, the processing component 702 can include one or more modules to facilitate the interaction between the processing component 702 and other components. For example, the processing component 702 can include a multimedia module to facilitate the interaction between the multimedia component 708 and the processing component 702.

[0177] The memory 704 is configured to store various types of data to support the operation of the electronic device 700. Examples of these data include instructions for any application or method operating on the electronic device 700, contact data, phone book data, messages, pictures, videos, etc. The memory 704 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic memory, flash memory, magnetic disk, optical disk, or graphene memory.

[0178] The power supply component 706 provides power to various components of the electronic device 700. The power supply component 706 can include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power for the electronic device 700.

[0179] The multimedia component 708 includes a screen that provides an output interface between the electronic device 700 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen can be implemented as a touch screen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensors can sense not only the boundaries of touch or swipe actions but also detect the duration and pressure associated with the touch or swipe operation. In some embodiments, the multimedia component 708 includes a front camera and / or a rear camera. When the electronic device 700 is in an operating mode, such as a shooting mode or a video mode, the front camera and / or the rear camera can receive external multimedia data. Each of the front camera and the rear camera can be a fixed optical lens system or have a focal length and optical zoom capabilities.

[0180] The audio component 710 is configured to output and / or input audio signals. For example, the audio component 710 includes a microphone (MIC) that is configured to receive external audio signals when the electronic device 700 is in an operating mode, such as a call mode, a recording mode, and a voice recognition mode. The received audio signals can be further stored in the memory 704 or transmitted via the communication component 716. In some embodiments, the audio component 710 further includes a speaker for outputting audio signals.

[0181] The I / O interface 712 provides an interface between the processing component 702 and a peripheral interface module, which can be a keyboard, a click wheel, buttons, etc. These buttons can include but are not limited to: a home button, a volume button, a power button, and a lock button.

[0182] The sensor component 714 includes one or more sensors for providing status assessments of various aspects of the electronic device 700. For example, the sensor component 714 can detect the on / off state of the electronic device 700, the relative positioning of components, such as the display and the keypad of the electronic device 700. The sensor component 714 can also detect a change in the position of the electronic device 700 or an electronic device 700 component, the presence or absence of user contact with the electronic device 700, the orientation or acceleration / deceleration of the device 700, and a change in the temperature of the electronic device 700. The sensor component 714 can include a proximity sensor configured to detect the presence of nearby objects without any physical contact. The sensor component 714 can also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, the sensor component 714 can further include an acceleration sensor, a gyroscope sensor, a magnetic sensor, a pressure sensor, or a temperature sensor.

[0183] The communication component 716 is configured to facilitate communication between the electronic device 700 and other devices in a wired or wireless manner. The electronic device 700 can access a communication standard-based wireless network, such as WiFi, a carrier network (such as 2G, 3G, 4G, or 5G), or a combination thereof. In an exemplary embodiment, the communication component 716 receives a broadcast signal or broadcast-related information from an external broadcast management system via a broadcast channel. In an exemplary embodiment, the communication component 716 further includes a Near Field Communication (NFC) module to facilitate short-range communication. For example, the NFC module can be implemented based on Radio Frequency Identification (RFID) technology, Infrared Data Association (IrDA) technology, Ultra Wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.

[0184] In an exemplary embodiment, the electronic device 700 can be implemented by one or more Application Specific Integrated Circuits (ASICs), Digital Signal Processors (DSPs), Digital Signal Processing Devices (DSPDs), Programmable Logic Devices (PLDs), Field Programmable Gate Arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components for performing the above method.

[0185] In an exemplary embodiment, a computer-readable storage medium including instructions is also provided, such as a memory 704 including instructions, and the above instructions can be executed by a processor 720 of the electronic device 700 to complete the above method. For example, the computer-readable storage medium can be a ROM, Random Access Memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage device, etc.

[0186] In an exemplary embodiment, a computer program product is also provided, and the computer program product includes instructions that can be executed by a processor 720 of the electronic device 700 to complete the above method.

[0187] It should be noted that the above-mentioned device, electronic device, computer-readable storage medium, computer program product, etc. may also include other implementation manners according to the description of the method embodiments. The specific implementation manners can refer to the description of the relevant method embodiments and will not be elaborated here one by one.

[0188] Those skilled in the art will readily conceive of other embodiments of the present disclosure after considering the specification and practicing the invention disclosed herein. The present disclosure is intended to cover any variations, uses, or adaptations of the present disclosure that follow the general principles of the present disclosure and include known common knowledge or conventional technical means in the technical field not disclosed in the present disclosure. The specification and embodiments are only regarded as exemplary, and the true scope and spirit of the present disclosure are pointed out by the claims.

[0189] It should be understood that the present disclosure is not limited to the exact structures described above and shown in the drawings, and various modifications and changes can be made without departing from its scope. The scope of the present disclosure is only limited by the appended claims.

Claims

1. An information processing method, characterized in that: The method comprises: In the case where the function extension application requests to obtain business information provided for a target account, determining a target business terminal, and obtaining global authorization information; the target business terminal is at least one of a plurality of business terminals, and the global authorization information indicates that the target account has the authority to obtain business information provided by any of the plurality of business terminals; According to the first interactive link between the browser and the target service end obtained in advance, a first interactive request of the browser is simulated and generated; the first interactive request includes an interactive request carrying the global authorization information; Sending the first interaction request generated in simulation to the target service end, triggering the target service end to return corresponding target service information when determining that the target account authentication is passed; The target service information is provided to the function extension application.

2. The method according to claim 1, characterized in that The obtaining of global authorization information includes: Obtaining login information provided by the target account; According to the pre-acquired second interactive link between the browser and the authentication center, a second interactive request of the browser is simulated and generated; the second interactive request includes an interactive request carrying the login information, and the authentication center is associated with the multiple service terminals; The simulated second interaction request is sent to the authentication center, triggering the authentication center to return the global authorization information after determining that the login information authentication is passed.

3. The method according to claim 2, characterized in that The step of simulating and generating a second interactive request of the browser according to the pre-acquired second interactive link between the browser and the authentication center includes: According to the pre-acquired second interactive link between the browser and the authentication center, sequentially determining the authentication center interactive behaviors that occur between the browser and the authentication center in the process of acquiring the global authorization information; Simulate and generate a second interaction request corresponding to the interaction behavior of the authentication center.

4. The method according to claim 3, characterized in that The simulating and generating a second interaction request corresponding to the interaction behavior of the authentication center includes: If the type of the authentication center interaction behavior is an interaction behavior triggered by the browser, then simulating and generating a second interaction request corresponding to the authentication center interaction behavior; If the type of interaction behavior of the authentication center is an interaction behavior performed by the browser in response to the second redirection information returned by the authentication center, then a corresponding second interaction request is simulated and generated based on the business-end interaction behavior occurring in the browser at the jump page pointed to by the second redirection information.

5. The method according to claim 3, characterized in that: Also includes: If the type of the authentication center interaction behavior is an interaction behavior performed by the browser in response to the second redirection information returned by the authentication center, it is prevented from jumping to the jump page pointed to by the second redirection information.

6. The method according to claim 1, characterized in that The simulating and generating a first interactive request of the browser according to the pre-acquired first interactive link between the browser and the target service end includes: Determining, in sequence, the business end interaction behaviors occurring between the browser and the target business end in the process of acquiring business information according to the first interaction link between the browser and the target business end; A first interaction request corresponding to the business end interaction behavior is generated by simulation.

7. The method according to claim 6, characterized in that The simulating and generating a first interaction request corresponding to the business end interaction behavior includes: If the type of the business-side interactive behavior is an interactive behavior triggered by the browser, simulating and generating a first interactive request corresponding to the business-side interactive behavior; If the type of the business-side interactive behavior is an interactive behavior performed by the browser in response to the received first redirection information, a corresponding first interactive request is simulated and generated based on the business-side interactive behavior occurring in the browser on the jump page pointed to by the first redirection information.

8. The method according to claim 7, characterized in that Also includes: If the business-end interactive behavior is an interactive behavior performed by the browser in response to the received first redirection information, the jump to the jump page pointed to by the first redirection information is prevented.

9. The method according to claim 7, characterized in that: The simulating and generating a first interaction request corresponding to the business end interaction behavior includes: Obtaining the interaction request type corresponding to the business end interaction behavior; A target interface corresponding to the interaction request type is determined from a plurality of request generation interfaces provided in advance, and the target interface is called to simulate and generate a first interaction request.

10. The method according to any one of claims 1 to 9, characterized in that In the case where the function extension application requests to obtain the business information provided for the target account, determining the target business end and obtaining the global authorization information include: Receiving an interface call request from a function extension application for an information acquisition interface; the information acquisition interface is provided by an extension application for acquiring business information provided by a business end; In response to the interface call request, the extended application for obtaining the business information provided by the business terminal determines the target business terminal requested by the functional extension application to provide business information for the target account, and obtains global authorization information from the authentication center based on the login information corresponding to the target account.

11. An information processing device, characterized in that: include: A global authorization acquisition unit is configured to determine a target service end and acquire global authorization information when the function extension application requests to acquire service information provided for a target account; The target business end is at least one of the multiple business ends, and the global authorization information indicates that the target account has the authority to obtain business information provided by any of the multiple business ends; A first interaction unit is configured to simulate and generate a first interaction request of the browser according to a pre-acquired first interaction link between the browser and the target service end; The first interaction request includes an interaction request carrying the global authorization information; A first interaction request sending unit is configured to execute sending the first interaction request generated in simulation to the target service end, triggering the target service end to return corresponding target service information when determining that the target account authentication is passed; The service information providing unit is configured to provide the target service information to the function extension application.

12. An electronic device, characterized in that: include: processor; a memory for storing instructions executable by the processor; The processor is configured to execute the instructions to implement the information processing method according to any one of claims 1 to 10.

13. A computer-readable storage medium, characterized in that: When the instructions in the computer-readable storage medium are executed by a processor of an electronic device, the electronic device is enabled to execute the information processing method according to any one of claims 1 to 10.

14. A computer program product, comprising instructions, characterized in that: When the instruction is executed by a processor of an electronic device, the electronic device is enabled to execute the information processing method according to any one of claims 1 to 10.

Images