CN113761508B - Information processing method, device, electronic device and storage medium - Google Patents
Information processing method, device, electronic device and storage medium Download PDFInfo
- Publication number
- CN113761508B CN113761508B CN202110127498.8A CN202110127498A CN113761508B CN 113761508 B CN113761508 B CN 113761508B CN 202110127498 A CN202110127498 A CN 202110127498A CN 113761508 B CN113761508 B CN 113761508B
- Authority
- CN
- China
- Prior art keywords
- login state
- target
- state data
- subsystem
- data acquisition
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING OR CALCULATING; COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/30—Authentication, i.e. establishing the identity or authorisation of security principals
- G06F21/45—Structures or tools for the administration of authentication
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Information Transfer Between Computers (AREA)
Abstract
本发明实施例公开了一种信息处理方法、装置、电子设备及存储介质，该方法包括：当接收到请求消息时，确定对请求消息处理的目标子系统；调取预先配置的与目标子系统相匹配的至少一个目标登录态数据获取组件，并基于目标登录态数据获取组件获取对应的目标登录态数据；其中，目标登录态数据为目标子系统对请消息进行处理时所使用的数据；基于各个目标登录态数据生成用户登录态信息，对用户登录态信息进行校验处理得到校验结果，并将校验结果反馈至目标客户端；其中，用户登录态信息为对目标登录态数据格式化处理后得到的信息。本发明实施例的技术方案，实现了有效、便捷的生成登录态信息并对登录态信息进行处理的技术效果。
The embodiment of the present invention discloses an information processing method, device, electronic device and storage medium, the method comprising: when receiving a request message, determining the target subsystem for processing the request message; calling at least one pre-configured target login state data acquisition component that matches 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 the data used by the target subsystem when processing the request message; generating user login state information based on each target login state data, verifying 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 the 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
The embodiment of the invention relates to the technical field of computers, in particular to an information processing method, an information processing device, electronic equipment and a storage medium.
Background
With the refined service division of the system, the system can be divided into a plurality of subsystems according to the functions to be implemented by the system. In order to process the corresponding information, each subsystem needs to deploy a set of logic codes matched with the functions realized by the subsystem in the subsystem, and login state information can be generated based on the logic codes and processed. Alternatively, each subsystem may copy the login state information generating code and the check logic code in the main system, generate the login state information based on the same program as the main system, and perform the check process on the login state information. If the function implemented by the subsystem a is qualification verification, the related information to be obtained is identity information, name, registration number of the registration company, etc., when the qualification verification is performed based on the subsystem a, all information of the user needs to be obtained based on logic codes in the subsystem, login state information for qualification verification is screened out from all information, and further verification is performed on the login state information to determine whether the verification can be performed.
The inventors found that when implementing the present technical solution based on the above-described mode, the following problems exist:
If each subsystem copies the code for generating and processing the login state information of the main system, all information of a user needs to be acquired, and the login state information required by the subsystem is extracted from all information and verified, so that the technical problem of complicated and complex login state information processing is caused.
Disclosure of Invention
The invention provides a method, a device, electronic equipment and a storage medium for determining a target object, so as to determine an object matched with the object browsed by a user, thereby improving the object conversion rate and the technical effect of user experience.
In a first aspect, an embodiment of the present invention provides an information processing method, including:
when a request message is received, determining a target subsystem for processing the request message;
Invoking at least one target login state data acquisition component which is pre-configured and matched with 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 when 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.
In a second aspect, an embodiment of the present invention further provides an information processing apparatus, including:
The target subsystem determining module is used for determining a target subsystem for processing the request message when the request message is received;
The login state data acquisition module is used for calling at least one target login state data acquisition component which is matched with the target subsystem in advance 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 when processing the request message;
The login state information generation module is used for 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 the verification result back to the target client, wherein the user login state information is obtained after the target login state data are formatted.
In a third aspect, an embodiment of the present invention further provides an electronic device, including:
one or more processors;
Storage means 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 are caused to implement the information processing method according to any one of the embodiments of the present invention.
In a fourth aspect, embodiments of the present invention also provide a storage medium containing computer-executable instructions, which when executed by a computer processor, are configured to perform an information processing method according to any of the embodiments of the present invention.
According to the technical scheme, when the request message is received, the target subsystem for processing the request message can be determined, at least one login state data acquisition component matched with the target subsystem is further acquired, so that corresponding target login state data is acquired based on the login state data acquisition component, further, user login state data is generated, the technical problems that a set of codes for generating login state information and processing the login state information are required to be deployed in each subsystem in the prior art are solved, the technical problem that research and development cost is high is solved, further, if all login state information of a user needs to be acquired when each subsystem copies login state information generation and processing codes of a main system, all login state information required by the user is extracted from all information and verified, and the technical problem that the login state information is complex in processing is caused, and further, if a program code of the main system is changed, a plurality of sets of identical codes are required to be repeatedly copied to the corresponding subsystem, the technical problem that resource waste and maintenance cost is high is solved, the technical problems that the login state data required by each subsystem are required to be processed in a modularized mode in advance, the corresponding to the corresponding state data are not required to the sub-system are required to be configured, the login state information is required to be acquired when the login state information is required to be processed, the login state information is required to be greatly required to be acquired, the login state information is required to be processed, and the login state information is required to be greatly required to be processed, and the login state information is required to be greatly required to be processed is required to be compared, and the login state information is required to be processed is required to be is greatly is required to be processed.
Drawings
In order to more clearly illustrate the technical solution of the exemplary embodiments of the present invention, a brief description is given below of the drawings required for describing the embodiments. It is obvious that the drawings presented are only drawings of some of the embodiments of the invention to be described, and not all the drawings, and that other drawings can be made according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a flowchart of an information processing method according to an embodiment of the present invention;
Fig. 2 is a schematic flow chart of an information processing method according to a second embodiment of the present invention;
FIG. 3 is a schematic diagram of a login-type component customization device according to a second embodiment of the present invention;
Fig. 4 is a flow chart of an information processing method according to a third embodiment of the present invention;
FIG. 5 is a schematic diagram of a login component list according to a third embodiment of the present invention;
Fig. 6 is a schematic diagram of an information processing method according to a third embodiment of the present invention;
fig. 7 is a schematic diagram of an information processing apparatus according to a fourth embodiment of the present invention;
fig. 8 is a schematic structural diagram of an electronic device according to a fifth embodiment of the present invention.
Detailed Description
The invention is described in further detail below with reference to the drawings and examples. It is to be understood that the specific embodiments described herein are merely illustrative of the invention and are not limiting thereof. It should be further noted that, for convenience of description, only some, but not all of the structures related to the present invention are shown in the drawings.
Example 1
Fig. 1 is a schematic flow chart of an information processing method provided in an embodiment of the present invention, where the embodiment is applicable to a case where when a request message is received, a target subsystem for processing the request message may be determined, and login state information is further obtained based on a login state component corresponding to the target subsystem, so as to obtain a corresponding result by processing the login state information. The execution of the technical scheme can be executed by a server, can be executed by terminal equipment, and can be executed by the cooperation of the server and the terminal equipment.
As shown in fig. 1, the method includes:
s110, when receiving the request message, determining a target subsystem for processing the request message.
It should be noted that, the system may be divided into a plurality of subsystems according to the functions to be implemented by the system. The system can correspond to an application program, can also be a corresponding page, can trigger various controls on the page by a user, and can generate a request message based on the triggered controls.
The request message may be a request generated after triggering a control, for example, to perform qualification verification, a control corresponding to the qualification verification may be triggered, and when triggering the qualification verification control is detected, a request message corresponding to the qualification verification may be generated. The target subsystem is a subsystem that processes the request message, e.g., the target subsystem may be a qualification subsystem.
Specifically, when detecting that a user triggers a control, a request message corresponding to the control may be generated. At the same time, the target subsystem that processed the request message may be determined.
In this embodiment, the method for determining the target subsystem for processing the request message may be that, when the request message is received, a request identifier of the request message is obtained, and the target subsystem for processing the request message is determined according to the request identifier.
The request message may carry a request identifier. The request identification corresponds to the respective target subsystem.
Specifically, when the request message is received, a request identifier in the request message may be acquired, and a target subsystem corresponding to processing the request message may be determined according to the acquired request identifier.
S120, at least one target login state data acquisition component matched with the target subsystem is invoked, and corresponding target login state data is acquired based on the target login state data acquisition component.
At least one login-state data acquisition component corresponding to each subsystem can be preconfigured in order to facilitate processing of the respective request messages. The login-state data acquisition component is mainly an independent component which is determined after data is divided from two dimensions. The two dimensions may be a user-associated information dimension and a subsystem processing rules dimension. The corresponding data can be independently used as components from the dimension of user associated information, namely, the data related to the user, such as user login PIN, user basic information, user head portrait information, user gender information, user identity card number information, registered account number information and the like, are independently used as data processing components, the dimension of subsystem processing rules can be processing rules of information processing by a system, such as, if the function of the subsystem is identity verification, the processing rules can be verification of user tag information, and correspondingly, the login state component can be verification of user tag information components, if the function of the subsystem is qualification verification, the processing rules can be acquisition of a registered account number, verification of the registered account number, and correspondingly, the login state component can be verification of registration type information components. After each login state component is obtained, at least one login state component corresponding to each subsystem may be configured. The target login state data acquisition component is a login state component corresponding to a target subsystem for processing the request message. The target login state data may be data acquired by at least one target login state data acquisition component corresponding to the subsystem when the subsystem executes the corresponding function. That is, the target login state data is data used when the target subsystem processes the request message.
Specifically, after determining the target subsystem for processing the request message, a pre-configured target login state data acquisition component matched with the target subsystem can be invoked, and then corresponding target login state data can be acquired based on the target login state data acquisition component.
In the embodiment, the method for retrieving the at least one target login state data acquisition component which is pre-configured and matched with the target subsystem and acquiring corresponding target login state data based on the target login state data acquisition component comprises the steps of retrieving a pre-configured target login state component list corresponding to the target subsystem based on a pre-written retrieval program, determining each target login state data acquisition component in the target login state component list and an execution cursor of the target login state data acquisition component, and sequentially acquiring the target login state data matched with each target login state data acquisition component from user attribute information which a request message belongs to based on the execution cursor of each target login state data acquisition component.
Wherein the pre-written calling program may be a login interceptor. The login interceptor may invoke the list of login state components. The login component list is a login component list formed by login components configured according to functions to be realized by each subsystem, namely, according to service scenes of the subsystems. It may be understood that the login component list may include unique identifiers corresponding to a plurality of login components, for example, when the unique identifier in the login component list is1, the corresponding login component is a user id card number acquiring component. The execution cursor refers to the execution sequence of each login-state data acquisition component in the data login-state component list. The location information of each login state data acquisition component in the login state component list in the pre-divided login state data acquisition component set may also be used. The login state data acquisition component set comprises a plurality of elements, each element is a partitioned login state component to be configured, and the login state component to be configured is a component to be configured for each subsystem.
Specifically, a preconfigured target login component list corresponding to the target subsystem may be invoked based on a pre-written invoking program. And determining the execution sequence of each target login state component acquisition component and each target login state data acquisition component in the target login state component list. And sequentially acquiring the target login state data matched with each target login state data acquisition component from the user attribute information belonging to the request message according to the execution sequence of each target login state component.
S130, 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.
The user login state information is information obtained after target login state data are formatted. The user login state information can be obtained by formatting each login state data, for example, processing the login state data into data with a uniform format or processing the login state data into data with a preset format. The user login state information is information needed to be used when the target subsystem executes the request message. The verification result may include verification pass and verification fail. For example, in a medicine purchasing application program, if the purchased medicine needs real-name authentication, if the medicine can be purchased through verification, the medicine can be purchased through feedback to the target client, otherwise, the medicine can not be purchased.
Generating user login state information based on each target login state data in the embodiment comprises filling each target login state data into a corresponding target login state data acquisition component based on a data assignment method or a login state data verification method inherited by each target login state data acquisition component; and obtaining user login state information matched with the target subsystem based on the target login state data obtaining components filled with the target login state data.
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.
On the basis of the technical scheme, the verification processing of the user login state information is carried out to obtain a verification result, and the verification result is fed back to the target client, wherein the verification of the user login state information is carried out through the verification login state component in the target login state data acquisition component list to obtain the verification result, and the verification result is fed back to the target client.
Specifically, the target login state data acquisition component not only comprises a verification login component but also comprises a data acquisition component, corresponding target login state data is acquired based on the login state data acquisition component, verification is performed on the target login state data based on the login state data verification component, and a corresponding verification result can be obtained. The verification result may be fed back to the target client so that the user confirms the processing state of the request message.
According to the technical scheme, when the request message is received, the target subsystem for processing the request message can be determined, at least one login state data acquisition component matched with the target subsystem is further acquired, so that corresponding target login state data is acquired based on the login state data acquisition component, further, user login state data is generated, the technical problems that a set of codes for generating login state information and processing the login state information are required to be deployed in each subsystem in the prior art are solved, the technical problem that research and development cost is high is solved, further, if all login state information of a user needs to be acquired when each subsystem copies login state information generation and processing codes of a main system, all login state information required by the user is extracted from all information and verified, and the technical problem that the login state information is complex in processing is caused, and further, if a program code of the main system is changed, a plurality of sets of identical codes are required to be repeatedly copied to the corresponding subsystem, the technical problem that resource waste and maintenance cost is high is solved, the technical problems that the login state data required by each subsystem are required to be processed in a modularized mode in advance, the corresponding to the corresponding state data are not required to the sub-system are required to be configured, the login state information is required to be acquired when the login state information is required to be processed, the login state information is required to be greatly required to be acquired, the login state information is required to be processed, and the login state information is required to be greatly required to be processed, and the login state information is required to be greatly required to be processed is required to be compared, and the login state information is required to be processed is required to be is greatly is required to be processed.
On the basis of the technical scheme, the technical scheme of the embodiment of the invention also realizes that the corresponding login state data acquisition component can be dynamically configured for each subsystem, so that the subsystem can execute corresponding functions.
Example two
Fig. 2 is a flowchart of an information processing method according to a second embodiment of the present invention. Based on the foregoing embodiment, the target login state data acquisition component corresponding to each subsystem may be preconfigured, so that the corresponding target login state data may be acquired based on the target login state data acquisition component. Wherein, the technical terms identical to or corresponding to the above embodiments are not repeated herein.
As shown in fig. 2, the method includes:
s210, configuring a target login state data acquisition component corresponding to each subsystem.
It should be noted that the functions to be implemented by each subsystem are different, so that the specific content of the user login status information processed by each subsystem is also different. On this basis, there is also a certain difference from the login-state data acquisition component configured by each subsystem.
It should be further noted that, the configuration manner of configuring the corresponding target login state data obtaining component for each subsystem is the same, and only the login state data obtaining component configured for one subsystem is described herein as an example.
Specifically, according to the function to be realized by the current subsystem, a required login state data acquisition component is selected from a plurality of login state data acquisition components which are divided in advance, and the login state data acquisition component is used as a target login state data acquisition component.
For example, referring to fig. 3, a plurality of login state data acquisition components may be displayed on the display interface, such as 1, a parse user login PIN component, 2, a query user basic information component, and 3, a query user avatar information component. If the login state data obtaining components required by the current subsystem a are 4,5, 6, 7, 9, 10 and 12, the login state data obtaining components corresponding to the current subsystem a can be checked on the display interface. The configuration has the advantages that the login state data acquisition component is dynamically configured for each subsystem, and further the technical effect of corresponding functions is achieved.
S220, determining the dependency relationship of the target login state data acquisition component corresponding to the current subsystem aiming at each subsystem, and generating a login state component list according to the dependency relationship.
If the processing result of the previous data affects the processing mode of the next data, it is indicated that the data are in a dependency relationship. The dependency relationship at this time can be understood as whether the data acquired by the target login state data acquisition component has the dependency relationship, if so, the execution sequence 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 according to the execution sequence. The login component list comprises names, execution sequences and position information of the target login data acquisition components in the login component set. If the login components in the login component list are already ordered according to the order, the execution order may be the position information of each target login data acquisition component between the login data acquisitions split in advance.
Optionally, the generating a login state component list according to the dependency relationship includes determining an execution cursor of each target login state data acquisition component according to the dependency relationship, and generating a login state component list corresponding to the current subsystem according to the target login state data acquisition component and the corresponding execution cursor.
Wherein, the execution cursor can be the execution sequence of the target login state data acquisition component. The login component list also comprises the position information of each target login data acquisition component in the login component set.
Specifically, according to the dependency relationship corresponding to the data acquired by each target login state data acquisition component, determining the execution sequence 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 determining a login state component list based on the position information, the execution sequence and the name of the login state data acquisition component.
S230, establishing a corresponding relation 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 corresponding relation.
Specifically, after determining the login component list corresponding to each subsystem, a correspondence between the login component list and the subsystems may be established, so that when a request message is received and a target subsystem for processing the request message is determined, a target login data acquisition component matched with the target subsystem may be invoked according to the correspondence.
S240, when the request message is received, determining a target subsystem for processing the request message.
S250, at least one target login state data acquisition component matched with the target subsystem is invoked, and corresponding target login state data is acquired based on the target login state data acquisition component.
S260, 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.
According to the technical scheme of the embodiment of the invention, through pre-configuring the login state data acquisition component matched with each subsystem and generating the corresponding login state component list, after receiving the request message and determining the target subsystem, the target login state component list corresponding to the target subsystem can be called, thereby calling the corresponding target login state data acquisition component, generating the user login state information based on the target login state data acquired by the target login state data acquisition component, processing the user login state information to obtain the corresponding processing result, solving the technical problem that in the prior art, a set of codes for generating the login state information and processing the login state information are required to be deployed in each subsystem, and having higher research and development cost, further, if each subsystem copies the login state information generation and processing codes of the main system, all the information of the user needs to be acquired, and the login state information required by the subsystem is extracted from all the information and verified, thereby causing complex technical problems of processing the login state information, further, if the program of the main system is changed, the same sets of corresponding login state information needs to be repeatedly copied and the corresponding login state information needs to be acquired by the corresponding subsystems, the corresponding to the login state information is required to be processed, the corresponding to be realized, the login state information is required to be processed, the login state information is required to be further, the login state information is required to be processed by the corresponding to be received in the corresponding system, and the corresponding to the corresponding request state information is required to be processed, and the login state information is required to be high, and the login state information is required to be processed, the convenience of processing the login state data is improved, and a plurality of sets of codes are not required to be developed, so that the technical effect of development cost is greatly reduced.
Example III
Fig. 4 is a flowchart of an information processing method according to a third embodiment of the present invention. On the basis of the foregoing embodiment, user login state information on which each subsystem depends is further required to be divided into a plurality of target login state components, so as to configure the login state components corresponding to each subsystem, and further obtain corresponding login state data, and specific implementation manners thereof can be explained in detail with reference to this embodiment. Wherein, the technical terms identical to or corresponding to the above embodiments are not repeated herein.
As shown in fig. 4, the method includes:
S301, dividing user attribute information and verification rule information into at least one login state component to be inherited according to user login state information relied by each subsystem.
The user login state information on which each subsystem depends comprises part of user attribute information and verification rule information. The user attribute information may be data of the user, such as name, age, identification card number, and user related data, such as registered account number, registered funds, etc., and the verification rule information may be a rule for verifying the data by the subsystem, such as qualification verification rule, etc. The user attribute information and the verification rule information may be divided into a plurality of components, respectively, each of which is independent of the other. The collection of the above components may be used as a login-state customizing device. The login component to be inherited is a component obtained after division according to a certain rule, and the component at the moment has no corresponding function.
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 a plurality of login state components of the interface protocol to be inherited.
S302, calling each login state component to be inherited and inheriting a predefined interface protocol to obtain a login state component to be configured corresponding to each login state component to be inherited, so as to configure a target login state data acquisition component corresponding to each subsystem from the login state components to be configured.
The login state components to be inherited can be unified in an interface, and two methods, such as a method for assigning login state data and a method for verifying login state data, can be configured in the interface. After each login state component to be inherited inherits the corresponding method, a plurality of login state data acquisition components can be obtained.
It should be noted that, the inheritance method in each login state data obtaining component is alternatively used.
Specifically, after each login state component to be inherited inherits a predefined access protocol, a login state component to be configured corresponding to each login state component to be inherited can be obtained, so that a target login state data acquisition component corresponding to each subsystem is selected from the login state components to be configured.
S303, configuring a target login state data acquisition component corresponding to each subsystem.
Specifically, all login state components to be configured can be used as a set. The elements in the set are login-state components to be configured, and the position information of each login-state component in the set can be set, for example, the login-state component corresponding to the position number 1. And starting to configure the target login state data acquisition components corresponding to the subsystems from all the login state components to be configured.
S304, aiming at 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.
Specifically, for each subsystem, determining the dependency relationship of the target login state data acquisition component corresponding to the current subsystem, and determining the execution sequence of each login state component and the position information of each login state component in the login state component set to be configured. The order of execution and location information may be used as a list of logged components. Referring to fig. 5, the login state components to be configured that match the current subsystem include three, and a login state linked list (login state component list) may be obtained based on the dependency relationship and the name of the login state component to be configured.
S305, establishing a corresponding relation 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 corresponding relation.
Specifically, a corresponding relationship between the login component list and the corresponding subsystem may be established, so that when the request message is received, a target subsystem for processing the request message may be determined, and further, the login component list matched with the target subsystem is invoked based on the corresponding relationship, so as to obtain each login data obtaining component in the login component list.
S306, when the request message is received, determining a target subsystem for processing the request message.
For example, referring to fig. 6, a user may trigger a control on a display interface, and a corresponding request message is generated based on a trigger operation on the control. A request message is received and a target subsystem for processing the request message is determined.
S307, at least one target login state data acquisition component matched with the target subsystem is invoked, and corresponding target login state data is acquired based on the target login state data acquisition component, wherein the target login state data is data used by the target subsystem when processing the request message.
For example, with continued reference to FIG. 6, a login interceptor in the target subsystem may determine from the login state device a login state component linked list that matches the target subsystem. The target login state data acquisition component may be determined based on the login state component linked list. The corresponding target login state data can be acquired based on the interface protocol inherited in the target login state data acquisition component.
S308, 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.
For example, with continued reference to fig. 6, user login state information may be generated according to the target login state data, the target subsystem may process the user login state information to obtain a corresponding verification result, and the corresponding verification result may be fed back to the target client, so that the user logs in or performs an operation matched with the request message.
On the basis of fig. 6, the implementation flow of the technical scheme of the embodiment may be that when a user triggers a request control, a target subsystem for processing a request may be determined, a login component list generated by a login data acquisition component configured in advance according to a service scene corresponding to each subsystem is called based on a login interceptor configured in the target subsystem, and the purpose of generating the login component list is thread security ordered call and dynamic configuration. And according to the execution cursors of the login state data acquisition components, executing the login state component linked list step by step, finally acquiring the login state information of the whole user of the subsystem, and responding the acquired login state information to the client corresponding to the user in the target subsystem.
According to the technical scheme, when the request message is received, the target subsystem for processing the request message can be determined, at least one login state data acquisition component matched with the target subsystem is further acquired, so that corresponding target login state data is acquired based on the login state data acquisition component, further, user login state data is generated, the technical problems that a set of codes for generating login state information and processing the login state information are required to be deployed in each subsystem in the prior art are solved, the technical problem that research and development cost is high is solved, further, if all login state information of a user needs to be acquired when each subsystem copies login state information generation and processing codes of a main system, all login state information required by the user is extracted from all information and verified, and the technical problem that the login state information is complex in processing is caused, and further, if a program code of the main system is changed, a plurality of sets of identical codes are required to be repeatedly copied to the corresponding subsystem, the technical problem that resource waste and maintenance cost is high is solved, the technical problems that the login state data required by each subsystem are required to be processed in a modularized mode in advance, the corresponding to the corresponding state data are not required to the sub-system are required to be configured, the login state information is required to be acquired when the login state information is required to be processed, the login state information is required to be greatly required to be acquired, the login state information is required to be processed, and the login state information is required to be greatly required to be processed, and the login state information is required to be greatly required to be processed is required to be compared, and the login state information is required to be processed is required to be is greatly is required to be processed.
Example IV
Fig. 7 is a schematic diagram of an information processing apparatus according to a fourth embodiment of the present invention. As shown in fig. 4, the apparatus includes a target subsystem determining module 410, a login state data obtaining module 420, and a login state information generating module 430.
The system comprises a target subsystem determining module, a login state data acquisition module, a verification result and a target client, wherein the target subsystem determining module is used for determining a target subsystem for processing a request message when the request message is received, the login state data acquisition module is used for calling at least one target login state data acquisition component which is matched with the target subsystem in advance and acquiring corresponding target login state data based on the target login state data acquisition component, the target login state data are data used by the target subsystem when the request message is processed, the login state information generating module is used for generating user login state information based on each target login state data, verifying the user login state information to obtain the verification result and feeding the verification result back to the target client, and the user login state information is information obtained after the target login state data are formatted.
On the basis of the above technical solutions, the target subsystem determining module includes:
the system comprises a request message receiving unit for receiving a request message, a request identification determining unit for obtaining the request identification of the request message when the request message is received, and a target subsystem determining unit for determining a target subsystem for processing the request message according to the request identification.
On the basis of the above technical solutions, the target login state data determining module includes:
The system comprises a target subsystem, an execution cursor determining unit, a target login state data acquiring unit and a target login state data acquiring unit, wherein the target login state data acquiring unit is used for acquiring a target login state component list which is pre-configured and corresponds to the target subsystem based on a pre-written calling program and determining execution cursors of each target login state data acquiring component and each target login state data acquiring component in the target login state component list, and the target login state data acquiring unit is used for sequentially acquiring target login state data matched with each target login state data acquiring component from user attribute information which the request message belongs to based on the execution cursors of each target login state data acquiring component.
On the basis of the above technical solutions, the login state information generating module includes:
The login state data filling unit is used for filling the login state data of each target into the corresponding login state data acquisition component based on the data assignment method or the login state data verification method inherited by the login state data acquisition component of each target; and the login state information generating unit is used for obtaining the user login state information matched with the target subsystem based on the target login state data acquisition components filled with the target login state data.
On the basis of the technical schemes, the device further comprises:
The system comprises a configuration module, a login component list generation module, a corresponding relation establishment module and a corresponding relation establishment module, wherein the configuration module is used for configuring target login data acquisition components corresponding to all subsystems, the login component list generation module is used for determining the dependency relation of the target login data acquisition components corresponding to the current subsystem for all the subsystems and generating a login component list according to the dependency relation, and the corresponding relation establishment module is used for establishing the corresponding relation between the login component list and the corresponding subsystem so as to call the target login data acquisition components corresponding to the target subsystem according to the corresponding relation.
On the basis of the above technical solutions, before the configuration module is configured to configure the target login state data acquisition component corresponding to each subsystem, the apparatus further includes:
The system comprises a login state component to be inherited determining module, a target login state data acquisition component configuration module and a target login state data acquisition module, wherein the login state component to be inherited determining module is used for dividing user attribute information and check rule information into at least one login state component to be inherited according to user login state information relied by each subsystem, the at least one login state component to be inherited is mutually independent, and the target login state data acquisition module is used for calling each login state component to be inherited and inheriting a predefined interface protocol to obtain login state components to be configured corresponding to each login state component to be inherited so as to configure target login state data acquisition components corresponding to each subsystem from the login state components to be configured.
On the basis of the technical schemes, the configuration module is further used for determining current login state information depending on the current subsystem for each subsystem and determining at least one target login state data acquisition component from each login state component to be configured according to the current login state information.
On the basis of the technical schemes, the login state component list generation module further comprises an execution cursor determination unit and a login state list generation unit, wherein the execution cursor determination unit is used for determining the execution cursor of each target login state data acquisition component according to the dependency relationship, and the login state list generation unit is used for generating a login state component list corresponding to the current subsystem according to the target login state data acquisition component and the corresponding execution cursor.
On the basis of the technical schemes, the login state information generation module is further used for verifying 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 the verification result is fed back to the target client.
According to the technical scheme, when the request message is received, the target subsystem for processing the request message can be determined, at least one login state data acquisition component matched with the target subsystem is further acquired, so that corresponding target login state data is acquired based on the login state data acquisition component, further, user login state data is generated, the technical problems that a set of codes for generating login state information and processing the login state information are required to be deployed in each subsystem in the prior art are solved, the technical problem that research and development cost is high is solved, further, if all login state information of a user needs to be acquired when each subsystem copies login state information generation and processing codes of a main system, all login state information required by the user is extracted from all information and verified, and the technical problem that the login state information is complex in processing is caused, and further, if a program code of the main system is changed, a plurality of sets of identical codes are required to be repeatedly copied to the corresponding subsystem, the technical problem that resource waste and maintenance cost is high is solved, the technical problems that the login state data required by each subsystem are required to be processed in a modularized mode in advance, the corresponding to the corresponding state data are not required to the sub-system are required to be configured, the login state information is required to be acquired when the login state information is required to be processed, the login state information is required to be greatly required to be acquired, the login state information is required to be processed, and the login state information is required to be greatly required to be processed, and the login state information is required to be greatly required to be processed is required to be compared, and the login state information is required to be processed is required to be is greatly is required to be processed.
The information processing device provided by the embodiment of the invention can execute the information processing method provided by any embodiment of the invention, and has the corresponding functional modules and beneficial effects of the execution method.
It should be noted that the above-mentioned units and modules included in the apparatus are only divided according to the functional logic, but not limited to the above-mentioned division, so long as the corresponding functions can be implemented, and the specific names of the functional units are only used for distinguishing from each other, and are not used for limiting the protection scope of the embodiments of the present invention.
Example five
Fig. 8 is a schematic structural diagram of an electronic device according to a fifth embodiment of the present invention. Fig. 8 shows a block diagram of an exemplary electronic device 40 suitable for use in implementing the embodiments of the present invention. The electronic device 40 shown in fig. 8 is merely an example and should not be construed as limiting the functionality and scope of use of embodiments of the present invention.
As shown in fig. 8, the electronic device 40 is in the form of a general purpose computing device. The components of 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 the various system components, including system memory 402 and processing units 401.
Bus 403 represents one or more of several types of bus structures, including a memory bus or memory controller, a peripheral bus, an accelerated graphics port, a processor, or a local bus using any of a variety of bus architectures. By way of example, and not limitation, such architectures include 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.
Electronic device 40 typically includes a variety of computer system readable media. Such media can be any available media that is accessible by electronic device 40 and includes both volatile and non-volatile media, removable and non-removable media.
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. Electronic device 40 may further include other removable/non-removable, volatile/nonvolatile computer system storage media. By way of example only, storage system 406 may be used to read from and write to non-removable, nonvolatile magnetic media (not shown in FIG. 8, commonly referred to as a "hard drive"). Although not shown in fig. 8, a magnetic disk drive for reading from and writing to a removable non-volatile magnetic disk (e.g., a "floppy disk"), and an optical disk drive for reading from or writing to a removable non-volatile optical disk (e.g., a CD-ROM, DVD-ROM, or other optical media) may be provided. In such cases, each drive may be coupled to bus 403 through one or more data medium interfaces. Memory 402 may include at least one program product having a set (e.g., at least one) of program modules configured to carry out the functions of embodiments of the invention.
A program/utility 408 having a set (at least one) of program modules 407 may be stored in, for example, memory 402, such program modules 407 including, but not limited to, an operating system, one or more application programs, other program modules, and program data, each or some combination of which may include an implementation of a network environment. Program modules 407 generally perform the functions and/or methods of the described embodiments of the invention.
The electronic device 40 may also communicate with one or more external devices 409 (e.g., keyboard, pointing device, display 410, etc.), one or more devices that enable a user to interact with the electronic device 40, and/or any devices (e.g., network card, modem, etc.) that enable the electronic device 40 to communicate with one or more other computing devices. Such communication may occur through an input/output (I/O) interface 411. Also, electronic device 40 may 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 network adapter 412. As shown, network adapter 412 communicates with other modules of electronic device 40 over bus 403. It should be appreciated that although not shown in FIG. 8, other hardware and/or software modules may be used in connection with electronic device 40, including, but not limited to, microcode, device drivers, redundant processing units, external disk drive arrays, RAID systems, tape drives, data backup storage systems, and the like.
The processing unit 401 executes various functional applications and data processing by running a program stored in the system memory 402, for example, implements the information processing method provided by the embodiment of the present invention.
Example six
A sixth embodiment of the present invention also provides a storage medium containing computer-executable instructions for performing an information processing method when executed by a computer processor.
The method comprises the following steps:
when a request message is received, determining a target subsystem for processing the request message;
Invoking at least one target login state data acquisition component which is pre-configured and matched with 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 when 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.
The computer storage media of embodiments of the invention may take the form of any combination of one or more computer-readable media. The computer readable medium may be a computer readable signal medium or a computer readable storage medium. The computer readable storage medium can be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or a combination of any of the foregoing. More specific examples (a non-exhaustive list) of the computer-readable storage medium include an electrical connection having one or more wires, a portable computer diskette, 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 disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In this document, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device.
The computer readable signal medium may include a propagated data signal with computer readable program code embodied therein, either in baseband or as part of a carrier wave. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination of the foregoing. A computer readable signal medium may also be any computer readable medium that is not a computer readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.
Program code embodied on a computer readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.
Computer program code for carrying out operations for embodiments of the present invention may be written in one or more programming languages, including an object oriented programming language such as Java, smalltalk, C ++ and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the case of a remote computer, the remote computer may be connected to the user's computer through any kind of network, including a Local Area Network (LAN) or a Wide Area Network (WAN), or may be connected to an external computer (for example, through the Internet using an Internet service provider).
Note that the above is only a preferred embodiment of the present invention and the technical principle applied. It will be understood by those skilled in the art that the present invention is not limited to the particular embodiments described herein, but is capable of various obvious changes, rearrangements and substitutions as will now become apparent to those skilled in the art without departing from the scope of the invention. Therefore, while the invention has been described in connection with the above embodiments, the invention is not limited to the embodiments, but may be embodied in many other equivalent forms without departing from the spirit or scope of the invention, which is set forth in the following claims.
Claims (12)
1. An information processing method, characterized by comprising:
when a request message is received, determining a target subsystem for processing the request message;
Invoking at least one target login state data acquisition component which is pre-configured and matched with 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 when 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 of claim 1, wherein the determining the target subsystem for processing the request message when the request message is received comprises:
When receiving a request message, acquiring a request identifier of the request message;
And determining a target subsystem for processing the request message according to the request identification.
3. The method of claim 1, wherein the invoking the pre-configured at least one target login state data acquisition component that matches the target subsystem and acquiring corresponding target login state data based on the target login state data acquisition component comprises:
Based on a pre-written calling program, a pre-configured target login state component list corresponding to the target subsystem is called, and each target login state data acquisition component and each execution cursor of the target login state data acquisition component in the target login state component list are determined;
and sequentially acquiring target login state data matched with each target login state data acquisition component from the user attribute information of the request message based on the execution cursors of each target login state data acquisition component.
4. The method of claim 1, wherein generating user login state information based on the respective target login state data comprises:
Filling each target login state data into a corresponding target login state data acquisition component based on a data assignment method or a login state data verification method inherited by each target login state data acquisition component;
And obtaining user login state information matched with the target subsystem based on the target login state data obtaining components filled with the target login state data.
5. The method as recited in claim 1, further comprising:
Configuring a target login state data acquisition component corresponding to each subsystem;
Aiming at each subsystem, determining the dependency relationship of a target login state data acquisition component corresponding to the current subsystem, and generating a login state component list according to the dependency relationship;
and establishing a corresponding relation between the login state component list and the corresponding subsystem so as to call a target login state data acquisition component corresponding to the target subsystem according to the corresponding relation.
6. The method of claim 5, wherein prior to said configuring the target login state data acquisition component corresponding to each subsystem, the method further comprises:
Dividing user attribute information and verification rule information into at least one login state component to be inherited according to user login state information relied on by each subsystem, wherein the at least one login state component to be inherited is mutually independent;
And calling each login state component to be inherited and inheriting a predefined interface protocol to obtain a login state component to be configured corresponding to each login state component to be inherited, so as to configure a target login state data acquisition component corresponding to each subsystem from the login state components to be configured.
7. The method of claim 6, wherein configuring the target login state data acquisition component corresponding to each subsystem comprises:
and determining current login state information relied by the current subsystem aiming at each subsystem, and determining at least one target login state data acquisition component from each login state component to be configured according to the current login state information.
8. The method of claim 5, wherein generating a list of logged components from the dependency comprises:
Determining an execution cursor of each target login state data acquisition component according to the dependency relationship;
And generating a login state component list corresponding to the current subsystem according to the target login state data acquisition component and the corresponding execution cursor.
9. The method of claim 1, wherein the performing a verification process on the user login status information to obtain a verification result, and feeding back the verification result to the target client, includes:
and verifying 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 feeding back the verification result to the target client.
10. An information processing apparatus, characterized by comprising:
The target subsystem determining module is used for determining a target subsystem for processing the request message when the request message is received;
The login state data acquisition module is used for calling at least one target login state data acquisition component which is matched with the target subsystem in advance 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 when processing the request message;
The login state information generation module is used for 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 the verification result back to the target client, wherein the user login state information is obtained after the target login state data are formatted.
11. An electronic device, the electronic device comprising:
one or more processors;
Storage means for storing one or more programs,
The one or more programs, when executed by the one or more processors, cause the one or more processors to implement the information processing method of any of claims 1-9.
12. A storage medium containing computer executable instructions for performing the information processing method of any of claims 1-9 when executed by a computer processor.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110127498.8A CN113761508B (en) | 2021-01-29 | 2021-01-29 | Information processing method, device, electronic device and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110127498.8A CN113761508B (en) | 2021-01-29 | 2021-01-29 | Information processing method, device, electronic device and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113761508A CN113761508A (en) | 2021-12-07 |
| CN113761508B true CN113761508B (en) | 2025-07-15 |
Family
ID=78786482
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110127498.8A Active CN113761508B (en) | 2021-01-29 | 2021-01-29 | Information processing method, device, electronic device and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113761508B (en) |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105306423A (en) * | 2014-07-04 | 2016-02-03 | 中国银联股份有限公司 | Unified login method for distributed web station system |
Family Cites Families (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7020645B2 (en) * | 2001-04-19 | 2006-03-28 | Eoriginal, Inc. | Systems and methods for state-less authentication |
| CN107948167B (en) * | 2017-11-29 | 2020-11-06 | 浙江数链科技有限公司 | Single sign-on method and device |
| CN108650262B (en) * | 2018-05-09 | 2020-12-01 | 聚龙股份有限公司 | Cloud platform expansion method and system based on micro-service architecture |
| CN110311899A (en) * | 2019-06-17 | 2019-10-08 | 平安医疗健康管理股份有限公司 | Multiservice system access method, device and server |
| CN112100613A (en) * | 2020-08-27 | 2020-12-18 | 腾讯科技（深圳）有限公司 | Application login control method and device, electronic equipment and storage medium |
-
2021
- 2021-01-29 CN CN202110127498.8A patent/CN113761508B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN105306423A (en) * | 2014-07-04 | 2016-02-03 | 中国银联股份有限公司 | Unified login method for distributed web station system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113761508A (en) | 2021-12-07 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN110505162B (en) | Message transmission method and device and electronic equipment | |
| CN111782523B (en) | Cloud service deployment test method, device, electronic device and storage medium | |
| CN109995523B (en) | Activation code management method and device and activation code generation method and device | |
| WO2022142536A1 (en) | Grayscale publishing method, system and apparatus, and device and storage medium | |
| CN111797351A (en) | Page data management method and device, electronic equipment and medium | |
| US9350738B2 (en) | Template representation of security resources | |
| CN114528044B (en) | Interface calling method, device, equipment and medium | |
| CN110688111A (en) | Configuration method, device, server and storage medium for business process | |
| CN112596932A (en) | Service registration and interception method and device, electronic equipment and readable storage medium | |
| CN110231965A (en) | A kind of cloud device, applied program processing method and electronic equipment | |
| CN111324441A (en) | Operating environment switching method and device, computer equipment and storage medium | |
| CN114205156A (en) | Aspect technology-oriented packet detection method, device, electronic device and medium | |
| CN113485927A (en) | Test data generation method, device, equipment and storage medium | |
| CN108874441A (en) | A kind of board configuration method, device, server and storage medium | |
| CN112130850A (en) | Method and device for implementing functions in application programs | |
| CN114327939B (en) | Message distribution method, device, electronic device and storage medium | |
| CN115270196A (en) | Interface data filtering method, apparatus, computer equipment and readable storage medium | |
| CN113986995A (en) | Request distribution method, device, storage medium and electronic device | |
| CN114615138A (en) | Service containerization platform, service containerization method, apparatus and electronic device | |
| CN110096543B (en) | Application data manipulation method, apparatus, server and medium | |
| CN114302207A (en) | Bullet screen display method, device, system, equipment and storage medium | |
| CN115665265B (en) | Request processing method, device, equipment, storage medium and system | |
| CN113761508B (en) | Information processing method, device, electronic device and storage medium | |
| CN117573773A (en) | Method for synchronizing products from development end to production end | |
| CN112445790A (en) | Report data storage method, device, equipment and medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |