Information Processing Method, Apparatus, Electronic Device, and Storage Medium

Abstract

An embodiment of the present invention discloses an information processing method, apparatus, electronic device, and storage medium. The method includes: when a request message is received, determining a target subsystem for processing the request message; retrieving at least one target login state data acquisition component pre-configured to match the target subsystem, and acquiring corresponding target login state data based on the target login state data acquisition component; wherein the target login state data is data used by the target subsystem to process the request message; generating user login state information based on each target login state data, performing verification processing on the user login state information to obtain a verification result, and feeding back the verification result to the target client; wherein the user login state information is information obtained after formatting the target login state data. The technical solution of the embodiment of the present invention achieves the technical effect of effectively and conveniently generating login state information and processing the login state information.

Description

Technical Field

[0001] Embodiments of the present invention relate to the field of computer technologies, and in particular, to an information processing method, apparatus, electronic device, and storage medium. Background Art

[0002] With the refined service division of the system, the system can be divided into multiple subsystems according to the functions to be realized. In order to process the corresponding information, each subsystem needs to deploy a set of logic codes that match the functions implemented by the subsystem. Based on the logic codes, login state information can be generated and the login state information can be processed. Alternatively, each subsystem can copy the login state information generation code and verification logic code in the main system, and generate and verify the login state information based on the same program as the main system. For example, the function implemented by subsystem A is qualification verification, and the relevant information to be obtained is identity identification information, name, registration number of the registered company, etc. When performing qualification verification based on the above-mentioned subsystem A, it is necessary to obtain all the user information based on the logic code in the subsystem, and screen out the login state information for qualification verification from all the information, and then verify the login state information to determine whether the verification can pass.

[0003] When the inventors implemented the technical solution based on the above method, they found the following problems:

[0004] If a set of codes for generating and processing login state information is deployed in each subsystem, there is a technical problem of high code research and development cost; further, if each subsystem copies the login state information generation and processing codes in the main system, there is a technical problem that it is necessary to obtain all the user information, extract the login state information required by the subsystem from all the information, and verify it, resulting in cumbersome and complex processing of the login state information. Summary of the Invention

[0005] The present invention provides a method, apparatus, electronic device, and storage medium for determining a target item, so as to achieve the technical effect of determining an item that matches the item browsed by the user, thereby improving the item conversion rate and user experience.

[0006] In a first aspect, an embodiment of the present invention provides an information processing method, and the method includes:

[0007] When a request message is received, determine a target subsystem for processing the request message;

[0008] Retrieve at least one target login state data acquisition component preconfigured to match the target subsystem, and acquire corresponding target login state data based on the target login state data acquisition component; wherein, the target login state data is the data used by the target subsystem to process the request message;

[0009] Generate user login state information based on each target login state data, perform verification processing on the user login state information to obtain a verification result, and feedback the verification result to the target client; wherein, the user login state information is the information obtained by formatting the target login state data.

[0010] In a second aspect, an embodiment of the present invention further provides an information processing device, and the device includes:

[0011] A target subsystem determination module, configured to determine a target subsystem for processing the request message when receiving the request message;

[0012] A login state data acquisition module, configured to retrieve at least one target login state data acquisition component preconfigured to match the target subsystem, and acquire corresponding target login state data based on the target login state data acquisition component; wherein, the target login state data is the data used by the target subsystem to process the request message;

[0013] A login state information generation module, configured to generate user login state information based on each target login state data, perform verification processing on the user login state information to obtain a verification result, and feedback the verification result to the target client; wherein, the user login state information is the information obtained by formatting the target login state data.

[0014] In a third aspect, an embodiment of the present invention further provides an electronic device, and the electronic device includes:

[0015] One or more processors;

[0016] A storage device, configured to store one or more programs,

[0017] When the one or more programs are executed by the one or more processors, the one or more processors implement the information processing method as described in any one of the embodiments of the present invention.

[0018] In a fourth aspect, an embodiment of the present invention further provides a storage medium containing computer-executable instructions, and the computer-executable instructions are used to execute the information processing method as described in any one of the embodiments of the present invention when executed by a computer processor.

[0019] In the technical solution of the embodiment of the present invention, when a request message is received, the target subsystem for processing the request message can be determined, and then at least one logged-in state data acquisition component matching the target subsystem can be retrieved, so as to obtain the corresponding target logged-in state data based on the logged-in state data acquisition component, and then generate user logged-in state data, which solves the technical problem in the prior art that a set of code for generating and processing logged-in state information needs to be deployed in each subsystem, resulting in a relatively high R & D cost. Further, if the code for generating and processing the logged-in state information of the main system is replicated in each subsystem, there is a technical problem that all information of the user needs to be obtained, and the logged-in state information required by the subsystem needs to be extracted from all the information and verified, resulting in a cumbersome and complex processing of the logged-in state information. Further, when the program code of the main system changes, it is necessary to repeatedly copy multiple sets of the same code to the corresponding subsystems, resulting in a waste of resources and a relatively high maintenance cost. The technical effect is achieved that since the logged-in state data required by each subsystem is pre-componentized, and the logged-in state data acquisition components corresponding to each subsystem are configured, when a request message is received, the logged-in state data can be obtained based on the corresponding logged-in state data acquisition component and the logged-in state information can be generated, and then the user logged-in state data is processed to obtain the corresponding response result, improving the convenience of processing the logged-in state data and eliminating the need to develop multiple sets of code, thus greatly reducing the development cost. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] In order to more clearly illustrate the technical solutions of the exemplary embodiments of the present invention, the drawings required for describing the embodiments will be briefly introduced below. Obviously, the drawings introduced are only the drawings of a part of the embodiments to be described by the present invention, rather than all the drawings. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0021] Figure 1 FIG. is a schematic flow chart of an information processing method provided in Embodiment 1 of the present invention;

[0022] Figure 2 FIG. is a schematic flow chart of an information processing method provided in Embodiment 2 of the present invention;

[0023] Figure 3 FIG. is a schematic structural diagram of a logged-in state component customization device provided in Embodiment 2 of the present invention;

[0024] Figure 4 FIG. is a schematic flow chart of an information processing method provided in Embodiment 3 of the present invention;

[0025] Figure 5 FIG. is a schematic diagram of a logged-in state component list provided in Embodiment 3 of the present invention;

[0026] Figure 6 Schematic diagram of an information processing method provided in the third embodiment of the present invention;

[0027] Figure 7 Schematic diagram of the structure of an information processing device provided in the fourth embodiment of the present invention;

[0028] Figure 8 Schematic diagram of the structure of an electronic device provided in the fifth embodiment of the present invention. Detailed implementation manners

[0029] The present invention will be further described in detail below with reference to the accompanying drawings and embodiments. It can be understood that the specific embodiments described herein are only used to explain the present invention, rather than limiting the present invention. In addition, it should be noted that, for the sake of description, only parts related to the present invention are shown in the drawings rather than all structures.

[0030] Embodiment 1

[0031] Figure 1 Schematic flowchart of an information processing method provided in the first embodiment of the present invention. This embodiment is applicable to the situation where when a request message is received, the target subsystem for processing the request message can be determined, and then the login state information can be obtained based on the login state component corresponding to the target subsystem, and then the login state information is processed to obtain a corresponding result. This method can be executed by an information processing device, and the device can be implemented in the form of software and / or hardware. The hardware can be an electronic device, and the electronic device can be a mobile terminal, a PC, etc. The execution of this technical solution can be performed by a server, or by a terminal device, or by the cooperation of a server and a terminal device.

[0032] As Figure 1 shown, the method includes:

[0033] S110. When a request message is received, determine the target subsystem for processing the request message.

[0034] It should be noted that, according to the functions to be implemented by the system, the system can be divided into multiple subsystems. The system can correspond to an application program or a corresponding page. The user can trigger each control on the page, and a request message can be generated based on the triggered control.

[0035] Among them, the request message can be a request generated after triggering a certain control. For example, to perform qualification verification, the control corresponding to qualification verification can be triggered. When it is detected that the qualification verification control is triggered, a request message corresponding to qualification verification can be generated. The target subsystem is the subsystem for processing the request message. For example, the target subsystem can be the subsystem for performing qualification verification.

[0036] Specifically, when it is detected that the user triggers a certain control, a request message corresponding to the control can be generated. At the same time, the target subsystem for processing the request message can be determined.

[0037] In this embodiment, the method for determining the target subsystem for processing the request message can be: when the request message is received, obtain the request identifier of the request message; according to the request identifier, determine the target subsystem for processing the request message.

[0038] Among them, the request identifier can be carried in the request message. The request identifier corresponds to the corresponding target subsystem.

[0039] Specifically, when the request message is received, the request identifier in the request message can be obtained, and according to the obtained request identifier, the target subsystem for processing the request message can be determined.

[0040] S120. Retrieve at least one target login state data acquisition component pre-configured to match the target subsystem, and obtain the corresponding target login state data based on the target login state data acquisition component.

[0041] To facilitate the processing of each request message, at least one login state data acquisition component corresponding to each subsystem can be pre-configured. The login state data acquisition component is mainly an independent component determined after dividing the data from two dimensions. The two dimensions can be the user association information dimension and the subsystem processing rule dimension. Dividing the corresponding data into components from the user association information dimension can be: separating the data related to the user, such as the user login PIN, user basic information, user avatar information, user gender information, user ID card number information, registered account information, etc., and separating the above information or related information into data processing components; the subsystem processing rule dimension can be the processing rules for the system to process information. For example, if the function of the subsystem is identity verification, the processing rule can be to verify the user label information. Correspondingly, the login state component can be a component for verifying user label information; if the function of the subsystem is qualification verification, the processing rule can be to obtain the registered account and verify the registered account. Correspondingly, the login state component can be a component for verifying registration type information. After obtaining each login state component, at least one login state component corresponding to each subsystem can be configured. The target login state data acquisition component is the login state component corresponding to the target subsystem for processing the request message. The target login state data can be the data obtained by at least one corresponding target login state data acquisition component when the subsystem executes the corresponding function. That is, the target login state data is the data used by the target subsystem when processing the request message.

[0042] Specifically, after determining the target subsystem for processing the request message, a target login state data acquisition component pre-configured to match the target subsystem can be invoked, and then the corresponding target login state data can be acquired based on the target login state data acquisition component.

[0043] In this embodiment, invoking at least one target login state data acquisition component pre-configured to match the target subsystem and acquiring the corresponding target login state data based on the target login state data acquisition component includes: invoking a target login state component list pre-configured to match the target subsystem based on a pre-written invocation program, and determining each target login state data acquisition component and the execution cursor of the target login state data acquisition component in the target login state component list; and sequentially acquiring target login state data matching each target login state data acquisition component from the user attribute information to which the request message belongs based on the execution cursor of each target login state data acquisition component.

[0044] Among them, the pre-written invocation program can be a login interceptor. The login interceptor can invoke the login state component list. The login state component list is composed of login state components configured according to the functions to be implemented by each subsystem, that is, according to the business scenarios of the subsystems. It can be understood that the login state component list can include unique identifiers corresponding to multiple login state components. For example, when the unique identifier in the login state component list is 1, the corresponding login state component is the user ID number acquisition component. The execution cursor refers to the execution order of each login state data acquisition component in the login state component list. It can also be the position information of each login state data acquisition component in the pre-divided login state data acquisition component set. The login state data acquisition component set includes multiple elements, and each element is a to-be-configured login state component after division, and the to-be-configured login state component is a component to be configured for each subsystem.

[0045] Specifically, based on the pre-written invocation program, a target login state component list pre-configured to match the target subsystem can be invoked. Determine the execution order of each target login state component acquisition component and the target login state data acquisition component in the target login state component list. According to the execution order of each target login state component, sequentially acquire target login state data matching each target login state data acquisition component from the user attribute information to which the request message belongs.

[0046] S130. Generate user login state information based on each target login state data, perform verification processing on the user login state information to obtain a verification result, and feedback the verification result to the target client.

[0047] Among them, the user login state information is the information obtained after formatting the target login state data. Each login state data can be formatted, for example, processed into data with a unified format or data with a preset format, to obtain the user login state information. The user login state information is the information required when the target subsystem executes the request message. The verification result can include verification passed and verification failed. For example, in a drug purchase application, if the purchased medicine requires real-name authentication, if the verification is passed, the feedback to the target client can be that the medicine can be purchased, otherwise, it cannot be purchased.

[0048] In this embodiment, generating user login state information based on each target login state data includes: obtaining the data assignment method or login state data verification method inherited by each target login state data acquisition component, and filling each target login state data into the corresponding target login state data acquisition component; based on each target login state data acquisition component filled with the target login state data, obtaining user login state information that matches the target subsystem.

[0049] Specifically, user login state information can be generated based on each target login state data, and the target subsystem corresponding to the request message can perform verification processing on the user login state information to obtain a verification result.

[0050] Based on the above technical solution, performing verification processing on the user login state information to obtain a verification result and feedbacking the verification result to the target client includes: verifying the user login state information through the verification login state component in the target login state data acquisition component list, obtaining a verification result, and feedbacking the verification result to the target client.

[0051] Specifically, the target login state data acquisition component not only includes a component for verifying login but also a data acquisition component. Based on the login state data acquisition component, the corresponding target login state data is obtained, and based on the login state data verification component, the target login state data is verified, and the corresponding verification result can be obtained. The verification result can be feedbacked to the target client so that the user can confirm the processing status of the request message.

[0052] In the technical solution of the embodiment of the present invention, when a request message is received, the target subsystem for processing the request message can be determined, and then at least one logged-in state data acquisition component matching the target subsystem can be retrieved, so as to obtain the corresponding target logged-in state data based on the logged-in state data acquisition component, and then generate user logged-in state data, which solves the technical problem in the prior art that a set of code for generating and processing logged-in state information needs to be deployed in each subsystem, resulting in a relatively high R & D cost. Further, if the code for generating and processing the logged-in state information of the main system is replicated in each subsystem, there is a technical problem that all user information needs to be obtained, and the logged-in state information required by the subsystem needs to be extracted from all the information and verified, resulting in a cumbersome and complex processing of the logged-in state information. Further, if the program code of the main system changes, it is necessary to repeatedly copy multiple sets of the same code to the corresponding subsystems, resulting in technical problems of resource waste and relatively high maintenance costs. The present invention realizes that since the logged-in state data required by each subsystem is pre-componentized and the logged-in state data acquisition component corresponding to each subsystem is configured, when a request message is received, the logged-in state data can be obtained based on the corresponding logged-in state data acquisition component and the logged-in state information can be generated, and then the user logged-in state data can be processed to obtain the corresponding response result, which improves the convenience of processing the logged-in state data and eliminates the need to develop multiple sets of code, thus greatly reducing the development cost.

[0053] Based on the above technical solution, the technical solution of the embodiment of the present invention also realizes that the corresponding logged-in state data acquisition component can be dynamically configured for each subsystem, so that the subsystem can execute the corresponding function.

[0054] Embodiment 2

[0055] Figure 2 It is a schematic flowchart of an information processing method provided by Embodiment 2 of the present invention. Based on the foregoing embodiment, the target logged-in state data acquisition component corresponding to each subsystem can be pre-configured, and then the corresponding target logged-in state data can be obtained based on the target logged-in state data acquisition component. The specific implementation manner can refer to the technical solution of this embodiment. The same or corresponding technical terms as those in the above embodiment will not be described herein again.

[0056] As Figure 2 shown, the method includes:

[0057] S210. Configure the target logged-in state data acquisition component corresponding to each subsystem.

[0058] It should be noted that the functions to be implemented by each subsystem are different. Therefore, the specific content of the user login state information processed by each subsystem also varies. On this basis, there are also certain differences in the login state data acquisition components configured for each subsystem.

[0059] It should also be noted that the configuration method of configuring the corresponding target login state data acquisition component for each subsystem is the same. Here, only the configuration of the login state data acquisition component for one of the subsystems will be taken as an example for introduction.

[0060] Specifically, according to the function to be implemented by the current subsystem, select the required login state data acquisition component from multiple pre-divided login state data acquisition components and use it as the target login state data acquisition component.

[0061] Exemplarily, refer to Figure 3 , multiple login state data acquisition components can be displayed on the display interface. For example, 1. Component for parsing user login PIN; 2. Component for querying user basic information; 3. Component for querying user avatar information... If the login state data acquisition components required by the current subsystem A are 4, 5, 6, 7, 9, 10, and 12, then on the display interface, check the login state data acquisition components corresponding to the current subsystem A. The advantage of such a setting is that it realizes the dynamic configuration of the login state data acquisition component for each subsystem, and then realizes the technical effect of the corresponding function.

[0062] S220. For each subsystem, determine the dependency relationship of the target login state data acquisition component corresponding to the current subsystem, and generate a login state component list according to the dependency relationship.

[0063] Among them, if the processing result of the previous data affects the processing method of the subsequent data, it means that there is a dependency relationship between the data. At this time, the dependency relationship can be understood as whether there is a dependency relationship between the data obtained by the target login state data acquisition component. If there is a dependency relationship, the execution order of each login state data acquisition component can be determined according to the dependency relationship, and the list items in the login state component list can be generated based on the execution order. The login state component list includes the name of the login state component, the execution order, and the position information of the target login state data acquisition component in the login state component set. If the login state components in the login state component list are already sorted in order, the execution order can be the position information of each target login state data acquisition component among the pre-split login state data acquisitions.

[0064] Optionally, the generating the login state component list according to the dependency relationship includes: determining the execution cursor of each target login state data acquisition component according to the dependency relationship; generating the login state component list corresponding to the current subsystem based on the target login state data acquisition component and the corresponding execution cursor.

[0065] Among them, the execution cursor may be the execution order of the target login state data acquisition component. The login state component list also includes the position information of each target login state data acquisition component in the login state component set.

[0066] Specifically, according to the dependency relationships corresponding to the data obtained by each target login state data acquisition component, determine the execution order of each target login state data acquisition component and the position information of each target login state data acquisition component in the login state component set, and determine the login state component list based on the position information, execution order, and the name of the login state data acquisition component.

[0067] S230. Establish a correspondence between the login state component list and the corresponding subsystem, so as to retrieve the target login state data acquisition component corresponding to the target subsystem according to the correspondence.

[0068] Specifically, after determining the login state component list corresponding to each subsystem, a correspondence between the login state component list and the subsystem can be established, so that when a received request message is received and the target subsystem for processing the request message is determined, the target login state data acquisition component matching the target subsystem can be retrieved according to the correspondence.

[0069] S240. When a request message is received, determine the target subsystem for processing the request message.

[0070] S250. Retrieve at least one target login state data acquisition component pre-configured to match the target subsystem, and obtain the corresponding target login state data based on the target login state data acquisition component.

[0071] S260. Generate user login state information based on each target login state data, perform verification processing on the user login state information to obtain a verification result, and feedback the verification result to the target client.

[0072] In the technical solution of the embodiment of the present invention, by pre-configuring a login state data acquisition component that matches each subsystem and generating a corresponding list of login state components, when a request message is received and the target subsystem is determined, the target login state component list corresponding to the target subsystem can be retrieved, and then the corresponding target login state data acquisition component can be retrieved, so that user login state information can be generated based on the target login state data obtained by the target login state data acquisition component, and the user login state information can be processed to obtain a corresponding processing result. This solves the technical problem in the prior art that a set of code for generating login state information and processing login state information needs to be deployed in each subsystem, resulting in a relatively high R & D cost. Further, when the login state information generation and processing code of the main system is copied to each subsystem, it is necessary to obtain all the information of the user, extract the login state information required by the subsystem from all the information and verify it, resulting in a cumbersome and complex processing of the login state information. Further, when the program code of the main system changes, it is necessary to repeatedly copy multiple sets of the same code to the corresponding subsystems, resulting in technical problems of resource waste and high maintenance cost. It is realized that since the login state data required by each subsystem is pre-componentized and a login state data acquisition component corresponding to each subsystem is configured, when a request message is received, the login state data can be obtained based on the corresponding login state data acquisition component and the login state information can be generated, and then the user login state data can be processed to obtain a corresponding response result, improving the convenience of processing the login state data and eliminating the need to develop multiple sets of code, thus greatly reducing the development cost.

[0073] Embodiment III

[0074] Figure 4 FIG. is a schematic flowchart of an information processing method provided in Embodiment III of the present invention. On the basis of the foregoing embodiments, it is further necessary to divide the user attribute information and the verification rule information into multiple target login state components according to the user login state information relied on by each subsystem, so as to configure the login state components corresponding to each subsystem, and then obtain the corresponding login state data. The specific implementation manner can be elaborated in detail in this embodiment. Among them, the same or corresponding technical terms as those in the above embodiments will not be described again.

[0075] As Figure 4 shown, the method includes:

[0076] S301. Divide the user attribute information and the verification rule information into at least one pending inheritance login state component according to the user login state information relied on by each subsystem.

[0077] Among them, the user login state information relied on by each subsystem includes partial user attribute information and verification rule information. The user attribute information can be data of the user himself, such as name, age, ID number, and can also include user-related data, such as registered account number, registered funds, etc.; the verification rule information can be the rules for the subsystem to verify data, for example, qualification verification rules, etc. The user attribute information and the verification rule information can be respectively divided into multiple components, and each component is independent of each other. The set of the above components can be used as the login state customization device. The login components to be inherited are the components obtained after being divided according to certain rules, and the components at this time do not have corresponding functions.

[0078] Specifically, according to the user login state information relied on by each subsystem, the user attribute information and the verification rule information can be divided into multiple login state components to be inherited from the interface protocol.

[0079] S302. Retrieve each login state component to be inherited and inherit the predefined interface protocol to obtain the to-be-configured login state components corresponding to each login state component to be inherited, so as to configure the target login state data acquisition components corresponding to each subsystem from the to-be-configured login state components.

[0080] Among them, each login state component to be inherited can have a unified interface, and two methods can be configured in the interface, such as the method responsible for assigning login state data and the method responsible for verifying login state data. After each login state component to be inherited inherits the corresponding method, multiple login state data acquisition components can be obtained.

[0081] It should be noted that the methods inherited in each login state data acquisition component are used alternatively.

[0082] Specifically, after each login state component to be inherited inherits the predefined interface protocol, the to-be-configured login state components corresponding to each login state component to be inherited can be obtained, so as to select the target login state data acquisition components corresponding to each subsystem from the to-be-configured login state components.

[0083] S303. Configure the target login state data acquisition components corresponding to each subsystem.

[0084] Specifically, all to-be-configured login state components can be regarded as a set. The elements in the set are the to-be-configured login state components, and the position information of each login state component in the set can be set. For example, which login state component does the position number 1 correspond to. Start to configure the target login state data acquisition components corresponding to each subsystem from all to-be-configured login state components.

[0085] S304. For each subsystem, determine the dependency relationship of the target login state data acquisition component corresponding to the current subsystem, and generate a login state component list according to the dependency relationship.

[0086] Specifically, for each subsystem, determine the dependency relationship of the target login state data acquisition component corresponding to the current subsystem, determine the execution order of each login state component, and the position information of each login state component in the set of login state components to be configured. The execution order and position information can be used as the login state component list. Refer to Figure 5 , there are three login state components to be configured that match the current subsystem. The login state linked list (login state component list) can be obtained based on the dependency relationship and the names of the login state components to be configured.

[0087] S305. Establish the corresponding relationship between the login state component list and the corresponding subsystem, so as to retrieve the target login state data acquisition component corresponding to the target subsystem according to the corresponding relationship.

[0088] Specifically, the corresponding relationship between the login state component list and the corresponding subsystem can be established, so that when a request message is received, the target subsystem for processing the request message can be determined, and then based on the corresponding relationship, the login state component list matching the target subsystem can be retrieved, so as to obtain each login state data acquisition component in the login state component list.

[0089] S306. When a request message is received, determine the target subsystem for processing the request message.

[0090] Exemplarily, refer to Figure 6 , the user can trigger a certain control on the display interface, and generate a corresponding request message based on the trigger operation of the certain control. Receive the request message and determine the target subsystem for processing the request message.

[0091] S307. Retrieve at least one target login state data acquisition component pre-configured to match the target subsystem, and obtain the corresponding target login state data based on the target login state data acquisition component; wherein, the target login state data is the data used by the target subsystem when processing the request message.

[0092] Exemplarily, continue to refer to Figure 6 , the login interceptor in the target subsystem can determine the login state component linked list that matches the target subsystem from the login state device. The target login state data acquisition component can be determined based on the login state component linked list. The corresponding target login state data can be obtained based on the interface protocol inherited in the target login state data acquisition component.

[0093] S308. Generate user login state information based on each target login state data, perform verification processing on the user login state information to obtain a verification result, and feedback the verification result to the target client.

[0094] Exemplarily, continue to refer to Figure 6, user login state information can be generated based on the target login state data. The target subsystem can process the user login state information to obtain the corresponding verification result, and the corresponding verification result can be fed back to the target client to enable the user to log in or perform an operation matching the request message.

[0095] Based on Figure 6 , the implementation process of the technical solution of this embodiment can be as follows: When the user triggers the request control, the target subsystem for request processing can be determined. Based on the login interceptor configured in the target subsystem, the login state component list generated by the login state data acquisition component pre-configured according to the business scenarios corresponding to each subsystem is retrieved. The purpose of generating the login state component list is: thread-safe and orderly invocation and dynamic configuration. According to the execution cursor of each login state data acquisition component, the login state component linked list is executed step by step, and finally the overall user login state information of the subsystem is obtained, and the obtained login state information is responded to the client corresponding to the user in the target subsystem.

[0096] In the technical solution of the embodiment of the present invention, when a request message is received, the target subsystem for processing the request message can be determined, and then at least one login state data acquisition component matching the target subsystem is retrieved, so as to obtain the corresponding target login state data based on the login state data acquisition component, and then generate user login state data. This solves the technical problem in the prior art that a set of code for generating login state information and processing login state information needs to be deployed in each subsystem, resulting in a relatively high R & D cost. Further, if the login state information generation and processing code of the main system is copied to each subsystem, it is necessary to obtain all the information of the user, extract the login state information required by the subsystem from all the information and verify it, resulting in a cumbersome and complex processing of the login state information; further, if the program code of the main system changes, it is necessary to repeatedly copy multiple sets of the same code to the corresponding subsystems, resulting in waste of resources and relatively high maintenance costs. The technical effect is achieved that since the login state data required by each subsystem is pre-componentized and the login state data acquisition component corresponding to each subsystem is configured, when a request message is received, the login state data can be obtained based on the corresponding login state data acquisition component and the login state information can be generated, and then the user login state data can be processed to obtain the corresponding response result, improving the convenience of processing the login state data and eliminating the need to develop multiple sets of code, thus greatly reducing the development cost.

[0097] Embodiment 4

[0098] Figure 7 is a schematic structural diagram of an information processing device provided in Embodiment 4 of the present invention. As Figure 4As shown in the figure, the device includes: a target subsystem determination module 410, a logged-in state data acquisition module 420, and a logged-in state information generation module 430.

[0099] The target subsystem determination module is used to determine the target subsystem for processing the request message when receiving the request message; the logged-in state data acquisition module is used to retrieve at least one target logged-in state data acquisition component pre-configured to match the target subsystem, and obtain the corresponding target logged-in state data based on the target logged-in state data acquisition component; wherein, the target logged-in state data is the data used by the target subsystem to process the request message; the logged-in state information generation module is used to generate user logged-in state information based on each target logged-in state data, perform verification processing on the user logged-in state information to obtain a verification result, and feedback the verification result to the target client; wherein, the user logged-in state information is the information obtained after formatting the target logged-in state data.

[0100] Based on the above technical solutions, the target subsystem determination module includes:

[0101] The request identifier determination unit is used to obtain the request identifier of the request message when receiving the request message; the target subsystem determination unit is used to determine the target subsystem for processing the request message according to the request identifier.

[0102] Based on the above technical solutions, the target logged-in state data determination module includes:

[0103] The execution cursor determination unit is used to retrieve the target logged-in state component list pre-configured to match the target subsystem based on the pre-written retrieval program, and determine each target logged-in state data acquisition component and the execution cursor of the target logged-in state data acquisition component in the target logged-in state component list; the target logged-in state data acquisition unit is used to sequentially obtain the target logged-in state data matching each target logged-in state data acquisition component from the user attribute information to which the request message belongs based on the execution cursor of each target logged-in state data acquisition component.

[0104] Based on the above technical solutions, the logged-in state information generation module includes:

[0105] The logged-in state data filling unit is used to fill each target logged-in state data into the corresponding target logged-in state data acquisition component based on the data assignment method or logged-in state data verification method inherited by each target logged-in state data acquisition component; the logged-in state information generation unit is used to obtain the user logged-in state information matching the target subsystem based on each target logged-in state data acquisition component filled with the target logged-in state data.

[0106] Based on the above technical solutions, the device further includes:

[0107] A configuration module, configured to configure a target login state data acquisition component corresponding to each subsystem; a login state component list generation module, configured to determine, for each subsystem, the dependency relationship of the target login state data acquisition component corresponding to the current subsystem, and generate a login state component list according to the dependency relationship; a correspondence establishment module, configured to establish a correspondence between the login state component list and the corresponding subsystem, so as to call the target login state data acquisition component corresponding to the target subsystem according to the correspondence.

[0108] Based on the above technical solutions, before the configuration module is configured to configure a target login state data acquisition component corresponding to each subsystem, the device further includes:

[0109] A to-be-inherited login state component determination module, configured to divide user attribute information and verification rule information into at least one to-be-inherited login state component according to the user login state information relied on by each subsystem; wherein the at least one to-be-inherited login state component is independent of each other; a target login state data acquisition component configuration module, configured to call each to-be-inherited login state component and inherit a predefined interface protocol to obtain a to-be-configured login state component corresponding to each to-be-inherited login state component, so as to configure a target login state data acquisition component corresponding to each subsystem from the to-be-configured login state components.

[0110] Based on the above technical solutions, the configuration module is further configured to: for each subsystem, determine the current login state information relied on by the current subsystem, and determine at least one target login state data acquisition component from each to-be-configured login state component according to the current login state information.

[0111] Based on the above technical solutions, the login state component list generation module further includes: an execution cursor determination unit, configured to determine an execution cursor of each target login state data acquisition component according to the dependency relationship; a login state list generation unit, configured to generate a login state component list corresponding to the current subsystem based on the target login state data acquisition component and the corresponding execution cursor.

[0112] Based on the above technical solutions, the login state information generation module is further configured to verify the user login state information through the verification login state component in the target login state data acquisition component list to obtain a verification result, and feedback the verification result to the target client.

[0113] In the technical solution of the embodiment of the present invention, when a request message is received, the target subsystem for processing the request message can be determined, and then at least one logged-in state data acquisition component matching the target subsystem can be retrieved, so as to obtain the corresponding target logged-in state data based on the logged-in state data acquisition component, and then generate user logged-in state data, which solves the technical problem in the prior art that a set of code for generating and processing logged-in state information needs to be deployed in each subsystem, resulting in a relatively high R & D cost. Further, when the logged-in state information generation and processing code of the main system is replicated in each subsystem, there is a technical problem that all information of the user needs to be obtained, and the logged-in state information required by the subsystem needs to be extracted from all the information and verified, resulting in a cumbersome and complex processing of the logged-in state information; further, when the program code of the main system changes, it is necessary to repeatedly copy multiple sets of the same code to the corresponding subsystems, resulting in a technical problem of waste of resources and relatively high maintenance costs. It is realized that since the logged-in state data required by each subsystem is pre-componentized and the logged-in state data acquisition component corresponding to each subsystem is configured, when a request message is received, the logged-in state data can be obtained based on the corresponding logged-in state data acquisition component and the logged-in state information can be generated, and then the user logged-in state data can be processed to obtain the corresponding response result, which improves the convenience of processing the logged-in state data and eliminates the need to develop multiple sets of code, thereby greatly reducing the development cost.

[0114] The information processing device provided in the embodiment of the present invention can execute the information processing method provided in any embodiment of the present invention, and has the corresponding functional modules and beneficial effects for executing the method.

[0115] It should be noted that the various units and modules included in the above device are only divided according to functional logic, but are not limited to the above division, as long as the corresponding functions can be realized; in addition, the specific names of the functional units are only for the convenience of mutual distinction and do not limit the protection scope of the embodiment of the present invention.

[0116] Embodiment 5

[0117] Figure 8 It is a schematic structural diagram of an electronic device provided in Embodiment 5 of the present invention. Figure 8 It shows a block diagram of an exemplary electronic device 40 suitable for implementing the implementation manner of the embodiment of the present invention. Figure 8 The shown electronic device 40 is only an example and should not bring any limitation to the functions and usage scope of the embodiment of the present invention.

[0118] Such as Figure 8As shown, the electronic device 40 is presented in the form of a general-purpose computing device. The components of the electronic device 40 may include, but are not limited to: one or more processors or processing units 401, a system memory 402, and a bus 403 that connects different system components (including the system memory 402 and the processing unit 401).

[0119] The bus 403 represents one or more of several types of bus architectures, including a memory bus or memory controller, a peripheral bus, a graphics acceleration port, a processor, or a local bus using any of the various bus architectures. By way of example, these architectures include, but are not limited to, Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MAC) bus, Enhanced ISA bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI) bus.

[0120] The electronic device 40 typically includes a variety of computer system-readable media. These media can be any available media that can be accessed by the electronic device 40, including volatile and non-volatile media, removable and non-removable media.

[0121] The system memory 402 may include computer system-readable media in the form of volatile memory, such as random access memory (RAM) 404 and / or cache memory 405. The electronic device 40 may further include other removable / non-removable, volatile / non-volatile computer system storage media. By way of example only, a storage system 406 can be used for reading and writing on non-removable, non-volatile magnetic media ( Figure 8 not shown, typically referred to as a "hard disk drive"). Although Figure 8 not shown in the figure, a disk drive for reading and writing on removable non-volatile disks (such as "floppy disks") and an optical disk drive for reading and writing on removable non-volatile optical disks (such as CD-ROM, DVD-ROM, or other optical media) can be provided. In these cases, each drive can be connected to the bus 403 through one or more data media interfaces. The memory 402 may include at least one program product having a set (e.g., at least one) of program modules that are configured to perform the functions of the various embodiments of the present invention.

[0122] A program / utility 408 having a set (at least one) of program modules 407 can be stored, for example, in the memory 402. Such program modules 407 include, but are not limited to, an operating system, one or more application programs, other program modules, and program data. Each or some combination of these examples may include an implementation of a network environment. The program modules 407 generally perform the functions and / or methods described in the embodiments of the present invention.

[0123] The electronic device 40 can also communicate with one or more external devices 409 (such as a keyboard, a pointing device, a display 410, etc.), and can also communicate with one or more devices that enable a user to interact with the electronic device 40, and / or communicate with any device that enables the electronic device 40 to communicate with one or more other computing devices (such as a network card, a modem, etc.). Such communication can be carried out through an input / output (I / O) interface 411. Moreover, the electronic device 40 can also communicate with one or more networks (such as a local area network (LAN), a wide area network (WAN), and / or a public network, such as the Internet) through a network adapter 412. As shown in the figure, the network adapter 412 communicates with other modules of the electronic device 40 through a bus 403. It should be understood that although Figure 8 not shown in the figure, other hardware and / or software modules can be used in combination with the electronic device 40, including but not limited to: microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, and data backup storage systems, etc.

[0124] The processing unit 401 executes various functional applications and data processing by running programs stored in the system memory 402, for example, implementing the information processing method provided by the embodiments of the present invention.

[0125] Embodiment Six

[0126] Embodiment Six of the present invention also provides a storage medium containing computer-executable instructions, and the computer-executable instructions are used to execute an information processing method when executed by a computer processor.

[0127] The method includes:

[0128] When a request message is received, determining a target subsystem for processing the request message;

[0129] Invoking at least one target login state data acquisition component pre-configured to match the target subsystem, and acquiring corresponding target login state data based on the target login state data acquisition component; wherein, the target login state data is data used by the target subsystem to process the request message;

[0130] Generating user login state information based on each target login state data, performing verification processing on the user login state information to obtain a verification result, and feeding back the verification result to the target client; wherein, the user login state information is information obtained by formatting the target login state data.

[0131] The computer storage medium of the embodiments of the present invention may adopt any combination of one or more computer-readable media. The computer-readable media may be computer-readable signal media or computer-readable storage media. The computer-readable storage media may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the above. More specific examples (a non-exhaustive list) of the computer-readable storage media include: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In this document, the computer-readable storage media may be any tangible medium that contains or stores a program, and the program can be used by or in combination with an instruction execution system, apparatus, or device.

[0132] The computer-readable signal media may include data signals propagated in a baseband or as part of a carrier wave, which carry computer-readable program codes. Such propagated data signals may take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. The computer-readable signal media may also be any computer-readable media other than the computer-readable storage media, and the computer-readable media may send, propagate, or transmit a program for use by or in combination with an instruction execution system, apparatus, or device.

[0133] The program codes contained on the computer-readable media may be transmitted by any appropriate medium, including but not limited to wireless, wire, optical cable, RF, etc., or any suitable combination of the above.

[0134] The computer program codes for performing the operations of the embodiments of the present invention may be written in one or more programming languages or combinations thereof. The programming languages include object-oriented programming languages such as Java, Smalltalk, C++, and also include conventional procedural programming languages such as the "C" language or similar programming languages. The program codes may be executed entirely on the user's computer, partially on the user's computer, executed as an independent software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (for example, by using an Internet service provider to connect through the Internet).

[0135] Note that the above is only the preferred embodiment of the present invention and the technical principles applied. Those skilled in the art will understand that the present invention is not limited to the specific embodiments described herein, and various obvious changes, re-adjustments and substitutions can be made by those skilled in the art without departing from the protection scope of the present invention. Therefore, although the present invention has been described in more detail through the above embodiments, the present invention is not limited to the above embodiments. Without departing from the concept of the present invention, more other equivalent embodiments can be included, and the scope of the present invention is determined by the scope of the appended claims.

Claims

1. An information processing method, characterized in that, Including: When receiving a request message, determining a target subsystem for processing the request message; Invoking at least one target login state data acquisition component pre-configured to match the target subsystem, and acquiring corresponding target login state data based on the target login state data acquisition component; wherein, the target login state data is data used by the target subsystem for processing the request message; Generating user login state information based on each target login state data, performing verification processing on the user login state information to obtain a verification result, and feeding back the verification result to the target client; wherein, the user login state information is information obtained after formatting the target login state data.

2. The method according to claim 1, wherein The step of when receiving a request message, determining a target subsystem for processing the request message includes: When receiving a request message, acquiring a request identifier of the request message; Based on the request identifier, determining a target subsystem for processing the request message.

3. The method according to claim 1, wherein The step of invoking at least one target login state data acquisition component pre-configured to match the target subsystem, and acquiring corresponding target login state data based on the target login state data acquisition component includes: Based on a pre-written invocation program, invoking a target login state component list pre-configured to correspond to the target subsystem, and determining each target login state data acquisition component and the execution cursor of the target login state data acquisition component in the target login state component list; Based on the execution cursor of each target login state data acquisition component, sequentially acquiring target login state data matching each target login state data acquisition component from the user attribute information to which the request message belongs.

4. The method according to claim 1, wherein The step of generating user login state information based on each target login state data includes: Based on the data assignment method or login state data verification method inherited by each target login state data acquisition component, filling each target login state data into the corresponding target login state data acquisition component; Based on each target login state data acquisition component filled with target login state data, obtaining user login state information matching the target subsystem.

5. The method according to claim 1, characterized in that, It further includes: Configuring target login state data acquisition components corresponding to each subsystem; For each subsystem, determining the dependency relationship of the target login state data acquisition component corresponding to the current subsystem, and generating a login state component list according to the dependency relationship; Establishing a correspondence relationship between the login state component list and the corresponding subsystem, so as to invoke the target login state data acquisition component corresponding to the target subsystem according to the correspondence relationship.

6. The method according to claim 5, wherein Before the step of configuring target login state data acquisition components corresponding to each subsystem, the method further includes: According to the user login state information relied on by each subsystem, dividing the user attribute information and the verification rule information into at least one to-be-inherited login state component; wherein, the at least one to-be-inherited login state component is independent of each other. Retrieve each login state component to be inherited and inherit the predefined interface protocol to obtain the login state components to be configured corresponding to each login state component to be inherited, so as to configure the target login state data acquisition components corresponding to each subsystem from the login state components to be configured.

7. The method according to claim 6, wherein The configuration of the target login state data acquisition components corresponding to each subsystem includes: For each subsystem, determine the current login state information on which the current subsystem depends, and based on the current login state information, determine at least one target login state data acquisition component from each login state component to be configured.

8. The method according to claim 5, characterized in that, The generation of the login state component list according to the dependency relationship includes: Determine the execution cursor of each target login state data acquisition component according to the dependency relationship; Generate a login state component list corresponding to the current subsystem based on the target login state data acquisition component and the corresponding execution cursor.

9. The method according to claim 1, wherein The verification process of the user login state information to obtain a verification result and feedback the verification result to the target client includes: Verify the user login state information through the verification login state component in the target login state data acquisition component list to obtain a verification result, and feedback the verification result to the target client.

10. An information processing apparatus, characterized in that, It includes: A target subsystem determination module, configured to determine the target subsystem for processing the request message when receiving the request message; A login state data acquisition module, configured to retrieve at least one target login state data acquisition component pre-configured to match the target subsystem, and obtain the corresponding target login state data based on the target login state data acquisition component; wherein, the target login state data is the data used by the target subsystem to process the request message; A login state information generation module, configured to generate user login state information based on each target login state data, perform a verification process on the user login state information to obtain a verification result, and feedback the verification result to the target client; wherein, the user login state information is the information obtained after formatting the target login state data.

11. An electronic device, characterized in that, The electronic device includes: One or more processors; A storage device for storing one or more programs, When the one or more programs are executed by the one or more processors, the one or more processors implement the information processing method according to any one of claims 1-9.

12. A storage medium containing computer-executable instructions, where the computer-executable instructions are used to execute the information processing method according to any one of claims 1-9 when executed by a computer processor.

Images