WO2020233059A1 - 一种基于数据处理的登录处理方法及相关设备 - Google Patents

一种基于数据处理的登录处理方法及相关设备 Download PDF

Info

Publication number
WO2020233059A1
WO2020233059A1 PCT/CN2019/120966 CN2019120966W WO2020233059A1 WO 2020233059 A1 WO2020233059 A1 WO 2020233059A1 CN 2019120966 W CN2019120966 W CN 2019120966W WO 2020233059 A1 WO2020233059 A1 WO 2020233059A1
Authority
WO
WIPO (PCT)
Prior art keywords
session information
session
browser
login
user
Prior art date
Application number
PCT/CN2019/120966
Other languages
English (en)
French (fr)
Inventor
许剑勇
Original Assignee
深圳壹账通智能科技有限公司
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by 深圳壹账通智能科技有限公司 filed Critical 深圳壹账通智能科技有限公司
Publication of WO2020233059A1 publication Critical patent/WO2020233059A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/90—Details of database functions independent of the retrieved data types
    • G06F16/904—Browsing; Visualisation therefor
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0815—Network architectures or network communication protocols for network security for authentication of entities providing single-sign-on or federations
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/146—Markers for unambiguous identification of a particular session, e.g. session cookie or URL-encoding

Definitions

  • This application relates to the field of computer technology, and in particular to a login processing method and related equipment based on data processing.
  • the session information is generally time-sensitive. If the user is using the function that needs to log in (such as viewing personal information or logging in to the system), it is just right The expiration of the session information will cause the page corresponding to the login function to load abnormally, or even cause the page to be blank, which seriously affects the user experience.
  • the embodiment of the present application provides a login processing method and related equipment based on data processing, which can prevent the problem of abnormal page loading caused by invalid session information.
  • an embodiment of the present application provides a login processing method based on data processing.
  • the method is applied to a server, and the method includes:
  • the pre-recorded historical acquisition time when the first session information is successfully acquired and determine whether the time difference between the historical acquisition time and the system time is less than a preset time difference threshold, and the preset time difference threshold is less than the first
  • the expiration time corresponding to the session information, the historical acquisition time is earlier than the time when the first login request is received;
  • the first session information is returned to the browser, so that the browser can proceed based on the first session information Login processing.
  • an embodiment of the present application provides a data processing-based login processing device, and the data processing-based login processing device includes a module for executing the method of the first aspect.
  • an embodiment of the present application provides a server, the server includes a processor, a network interface, and a memory, the processor, the network interface, and the memory are connected to each other, wherein the network interface is controlled by the processor Used to send and receive messages, the memory is used to store a computer program that supports the server to execute the above method, the computer program includes program instructions, and the processor is configured to call the program instructions to execute the method of the above first aspect.
  • an embodiment of the present application provides a computer non-volatile readable storage medium, the computer non-volatile readable storage medium stores a computer program, the computer program includes program instructions, and the program instructions When executed by a processor, the processor is caused to execute the method of the first aspect.
  • the server may determine the first session information matching the session identifier from at least one piece of pre-stored session information, if it is determined that the time difference between the historical acquisition time when the first session information is successfully acquired and the system time If it is less than the preset time difference threshold, the first session information is returned to the browser, so that the browser performs login processing based on the first session information. It can prevent the problem of abnormal page loading caused by invalid session information.
  • FIG. 1 is a schematic structural diagram of a login processing system provided by an embodiment of the present application
  • FIG. 2 is a schematic flowchart of a login processing method based on data processing provided by an embodiment of the present application
  • FIG. 3 is a schematic flowchart of another login processing method based on data processing provided by an embodiment of the present application.
  • FIG. 4 is a schematic block diagram of a login processing device based on data processing provided by an embodiment of the present application
  • Fig. 5 is a schematic block diagram of a server provided by an embodiment of the present application.
  • the login processing system may include: a client 10, a browser 11, and a server 12 corresponding to the business system.
  • the client 10 may be an application program corresponding to the business system, or may be a terminal installed with an application program corresponding to the business system for interacting with users; the browser 11 provides page loading services for the browser
  • the browser 11 may be an application program installed on the terminal corresponding to the client 10;
  • the server 12 is a server corresponding to the business system, and is used to provide related services of the business system.
  • a user in an unlogged state logs in to the business system for the first time through the client 10, it needs to provide login information required for login, such as account number, password, etc., and send the browser 11 with the login information.
  • Information login request The browser 11 may forward the login request (that is, the second login request) to the server 12, and the server 12 may create a session information (such as session) specific to the browser 11 for the user according to the login information in the login request, and transfer the The user's login information is stored in the exclusive session information, and all subsequent user status information in the business system can be stored in the exclusive session information session.
  • the server may generate a session identifier (such as session id) corresponding to the session, store the session information in association with the session identifier, return the session identifier to the browser 11, and the browser 11 may store the session identifier.
  • a session identifier such as session id
  • the server since the server stores a large number of session information corresponding to the user's browser (hereinafter referred to as the user browser), each user corresponds to one session information. Therefore, in order to prevent the server storage space from being excessively occupied by the session information, each session corresponds to One failure duration.
  • the invalidation duration of the session is calculated from the time when the session is not active. If the session is always active, the session will never become invalid. The invalidation duration starts when the session is not accessed (that is, successfully acquired). Once the session is Access, the timer is cleared.
  • the client terminal 10 when the client terminal 10 detects that the user wants to switch to a page that requires login information (such as viewing personal information, viewing a shopping cart, etc.), the client terminal 10 can automatically send the browser 11 Send the first login request corresponding to the user.
  • the browser 11 After receiving the first login request, the browser 11 can put the pre-stored session identifier into the first login request, and send the first login request carrying the session identifier To the server 12, after the server 12 detects the session identifier in the first login request, it determines the first session that matches the session identifier from at least one pre-stored session (that is, the pre-stored session information).
  • the server 12 since each time the first session is successfully acquired, the server 12 will record the time when the first session is successfully acquired, and record the time when the first session is successfully acquired as the historical acquisition time when the first session is successfully acquired.
  • the historical acquisition time is stored in association with the first session.
  • the server 12 determines the first session matching the above-mentioned session identifier from the at least one pre-stored session, it can obtain the pre-recorded historical acquisition time of the successful acquisition of the first session, and determine the historical acquisition time and the system time Whether the time difference between is less than a preset time difference threshold, the preset time difference threshold is less than the invalidation duration corresponding to the first session information, and the history acquisition time is earlier than the time when the first login request is received.
  • the server 12 determines that the time difference between the historical acquisition time and the system time is less than the preset time difference threshold, by returning the first session to the browser 11, the browser 11 can use the login information of the user included in the first session , The login operation is automatically performed, and the page that requires login information that the user wants to view is loaded. After the page is loaded, the client 10 can display the page. In this way, the problem of abnormal page loading caused by session failure can be prevented, which is beneficial to improve user experience.
  • Figure 2 is a schematic flow chart of a data processing-based login processing method provided by an embodiment of the present application. The method is applied to a server and can be executed by the server. As shown in the figure, the data processing-based login processing method can include:
  • 201 Receive a first login request sent by a user through a browser, where the first login request carries a session identifier.
  • the server may receive a second login request for logging in to the service system for the first time sent by the user through a browser, and the second login request carries login information for the user to log in to the service system. Further, the server may generate session information including the login information and a session identifier corresponding to the session information, store the session identifier and the session information in association with the database, and return the session identifier to the browser.
  • a user when a user logs in to the business system for the first time through a client, he can input his own login information through the client corresponding to the business system and submit a first login request.
  • the login information includes the personal information submitted by the user in the registered account of the business system , Such as account name, login password, etc.
  • the client can add the aforementioned login information to the first login request, and send the first login request (ie, the second login request) carrying the login information to the server.
  • the server when it receives the second login request sent by the user through the browser to log in to the business system for the first time, it may create a session (ie session information) corresponding to the user, and put the login information in the second login request into the user In the corresponding session, the session identifier (such as session id) of the session corresponding to the user is generated, the session and session id corresponding to the user are stored in association, and the session id is returned to the browser. When the browser receives the session id, it will store the session id in its own process memory.
  • the client detects that the webpage the user wants to visit is a target webpage that needs to be logged in (such as a webpage for viewing personal information, a webpage for viewing a shopping cart, a webpage for viewing account balance, etc. ), the client can send a login request (that is, the first login request) to the browser to access the target webpage.
  • a login request that is, the first login request
  • the browser can add the aforementioned session id to the login request and send it to the server corresponding to the business system.
  • the server After the server receives the login request carrying the session id, it can be based on the session id. Find the corresponding session, take out the login information from the session, and use it again to serve the user, thus realizing the session tracking of the user.
  • At least one session information and at least one session identifier are associated and stored in the database of the server, and the session information and the session identifier have a one-to-one correspondence relationship.
  • the session information is session
  • the monogram identifier is session id
  • the correspondence between the session information and the session identifier is shown in Table 1.
  • session1 can be determined as the first session information matching the session identifier "2E28D987".
  • the 203 Acquire the pre-recorded historical acquisition time when the first session information is successfully acquired, and determine whether the time difference between the historical acquisition time and the system time is less than a preset time difference threshold.
  • the preset time difference threshold is less than the invalidation duration corresponding to the first session information, and the historical acquisition time is earlier than the time when the first login request is received.
  • each user since the server stores a large amount of user browser session information (such as session), each user corresponds to one session information. Therefore, in order to prevent the server storage space from being excessively occupied by the session information, each session information is There is a pre-set expiration time.
  • the invalidation duration of the session information is calculated from when the session information is not active. If the session information is always active, then the session information will never become invalid. The invalidation duration is from the session information not being accessed (that is, being successfully obtained) Start timing, once the session information is accessed, the timing is cleared.
  • the historical acquisition time when the session information is successfully acquired is recorded. For example, if the first session information session1 was successfully acquired at the system time of 2018.12.29-21:11:00, the historical acquisition time of the successful acquisition of the session1 may be recorded in the database as 2018.12.29-21:11:00. Later, if the session1 is successfully acquired again, the current system time (for example, 2018.12.29-21:11:59) can be used again to update the historical acquisition time.
  • the historical acquisition time when the first session information was successfully acquired obtained in step 203 is the historical acquisition time when the first session information was successfully acquired last time, that is, it can be understood as the latest historical acquisition time this time. .
  • the foregoing preset time difference threshold is less than the invalidation duration preset in the first session information.
  • the preset time difference threshold may be 8 minutes. Both the failure duration and the preset time difference threshold may be set by the developer according to experimental data.
  • the invalidation duration of the session information corresponding to different types of users may be different. Then, since the preset time difference threshold is less than the invalidation duration, the preset time difference thresholds corresponding to the session information of different types of users are also different.
  • This type can refer to the role of the user. For example, if the user is a manager (for example, the operation and maintenance personnel of the business system) after logging in to the business system, the business system may need to be checked and adjusted, then the duration of the invalidation of the corresponding session information for the manager can be Longer than ordinary users.
  • the user may be further classified by combining the user's historical access frequency or user level. For example, users with high historical access frequency may be more familiar with the business system, and the session information corresponding to such users can be set with a smaller invalidation duration (compared to users with lower historical access frequency). That is, a user with a higher historical access frequency has a smaller invalidation period of the corresponding session information.
  • a user with a higher user level can set a longer invalidation time corresponding to the session information. In this way, users with higher levels can enjoy a better user experience.
  • the server may determine the target user type to which the user belongs from at least one preset user type based on the login information carried in the second login request, and compare the preset user type with the preset user type based on the target user type.
  • the invalidation duration of the session information corresponding to the user is determined, and further, the session identifier corresponding to the session information, the session information, and the invalidation duration of the session information can be associated and stored in the database. Further, the developer can set the preset time difference threshold corresponding to the session information according to the invalidation duration of the session information.
  • user types are divided into operation and maintenance personnel and ordinary users.
  • the corresponding relationship between user types and invalidation duration indicates that the invalidation duration corresponding to the session information of ordinary users is 15 minutes, and the invalidation duration corresponding to operation and maintenance personnel is 10 minutes.
  • the server determines that the user is an operation and maintenance personnel based on the login information in the second login request, it can determine that the invalidation duration of the session information corresponding to the user is based on the correspondence between the user type and the invalidation duration 15 minutes, and then the preset time difference threshold corresponding to the user's session information can be set according to the failure duration of 15 minutes, for example, it can be 8 minutes.
  • the server may obtain the pre-recorded historical acquisition time when the first session information is successfully acquired, and determine whether the time difference between the historical acquisition time and the system time is less than a preset time difference threshold.
  • the first session information is session1
  • the historical acquisition time when the first session information was successfully acquired last time is 2018.12.29-21:11:59
  • the current system time is 2018.12.29-21:12:59
  • the preset time difference threshold is 8 minutes.
  • the server can calculate that the time difference between the historical acquisition time 2018.12.29-21:11:59 and the system time 2018.12.29-21:12:59 when the first session information was successfully acquired last time is 1 minute Further, it can be obtained that the time difference of 1 minute is less than the preset time difference threshold of 8 minutes, and the session1 can be directly returned to the browser.
  • the browser may perform login processing based on the login information and configuration information of the user in the first session information, and load the login processed page.
  • the above-mentioned first login request also carries transmission parameters corresponding to the first login request, and the transmission parameters include the user ID of the user and the identification information of the client corresponding to the browser.
  • the client is an application. Program, the client's identification information can be the client's name, ID, version number, etc.
  • the server determines that the time difference between the historical acquisition time and the system time is not less than the preset time difference threshold, it can acquire the second session information required by the user to log in to the business system based on the transmission parameters, and return the information to the browser.
  • the second session information is convenient for the browser to perform login processing based on the second session information.
  • the second session information may be understood as the latest session information obtained by the server calling the network data interface according to the transmission parameters, and the first session information mentioned above is session information cached in advance.
  • the implementation of the embodiments of the present application can prevent the problem of abnormal page loading caused by session information failure.
  • FIG. 3 is a schematic flowchart of another login processing method based on data processing provided by an embodiment of the present application.
  • the method can be executed by a server.
  • the login processing method based on data processing may include:
  • 301 Receive a first login request sent by a user through a browser, where the first login request carries a session identifier and a transmission parameter corresponding to the first login request.
  • step 301 to step 303 For the specific implementation manners of step 301 to step 303, reference may be made to the related description of step 201 to step 203 in the foregoing embodiment, which will not be repeated here.
  • the client needs to load the H5 page through a browser.
  • the target page can be, for example, a page for viewing personal accounts
  • the browser wants to load the target page
  • the user's login information needs to be used for login processing To load the target page normally.
  • the login information of the user is stored in the session information (such as session) corresponding to the user. Therefore, if the browser wants to load the target page, it needs to obtain the session information corresponding to the user.
  • this application can detect in real time whether the timing duration corresponding to the timer is less than the preset duration threshold, and whether the latest session is successfully obtained in real time. If the second session information is successfully obtained, and the time duration corresponding to the timer is less than the preset duration threshold, the latest obtained session is returned to the browser, so that the browser can log in based on the second session information and load the target page. In this way, the page white screen phenomenon caused by too long acquisition time can be avoided.
  • the browser if the second session information is not successfully obtained when the timing duration corresponding to the timer is greater than or equal to the preset duration threshold, the browser returns the first session information so that the browser can base on the first session information.
  • the session information is processed for login.
  • the preset duration threshold is 3s
  • the server triggers the execution of the acquisition operation of acquiring the second session information required by the user to log in to the business system based on the transmission parameters, that is, starting to acquire the second session information
  • the server obtains the timing duration of the timer in real time, and detects in real time whether the timing duration is less than a preset duration threshold.
  • the server successfully acquires the second session information, and detects that the timing duration is 2s, which is less than the preset duration threshold of 3s, the acquired second session information can be returned to the browser. If it is detected that the current timing duration is equal to 3s, and the second session information has not been successfully obtained, the first session information obtained in advance may be returned to the browser.
  • the timing duration of the acquisition timer may be acquired in real time, or acquired at a preset time interval, or acquired according to other time rules, which is not specifically limited in this application.
  • the system time is used as the historical acquisition time when the second session information is successfully acquired. Further, the historical acquisition time when the second session information is successfully acquired may be stored in a database in association with the second session information.
  • the server when the server associates the historical acquisition time when the second session information is successfully acquired with the second session information and stores it in the database, it may also associate the session identifier carried in the first login request with the second session information and the history.
  • the acquisition time is associated and stored in the database, that is, the session identifier, the second session information, and the historical acquisition time at which the second session information is successfully acquired have a one-to-one correspondence.
  • the server if it successfully obtains the second session information, it can also generate a new session identifier for the second session information in real time. Further, the server may associate the new session identifier, the second session information, and the historical acquisition time when the second session information is successfully acquired into the database; on the other hand, the server may return the new session identifier to The browser, after receiving the new session identifier, the browser can store the new session identifier in the process memory, and when it needs to continue to access the service system corresponding to the server, it can carry the new session identifier in the access request (Such as the first login request).
  • the session identifier carried in the first login request is "2E28D987”
  • the first session information is session1
  • the second session information is session2
  • the server successfully obtains the session2
  • the timer corresponding to the timer is less than the preset duration Threshold
  • the current system time is 2018.12.29-21:13:59.
  • the three are associated and stored in the database.
  • the session2 can be determined as the session information matching the session identifier "2E28D987", and the session2 can be used to perform subsequent steps.
  • the first login request carries identification information of the browser, and the identification information of the browser may be, for example, the name, version number, ID, etc. of the browser.
  • the identification information of the browser may be, for example, the name, version number, ID, etc. of the browser.
  • access to the business system only provides services to a designated browser.
  • the developer can pre-enter the preset identification information of these designated browsers (that is, the preset browser) in the database of the server.
  • the The identification information of the browser carried in the first login request is compared with the preset identification information,
  • the execution of the step of determining the first session information matching the session identification from the at least one pre-stored session information is triggered.
  • the preset identification information pre-stored in the database includes multiple preset identification information
  • the server may sequentially compare the identification information of the browser with the preset identification information according to the storage order of the multiple preset identification information itself. In the sequential comparison process, if it is determined that the identification information of the browser matches any preset identification information, the comparison process is ended, and it is determined that the identification information matches the preset identification information.
  • the server may randomly compare one or more preset identification information of the plurality of preset identification information with the identification information at the same time, and if the comparison shows that the identification information of the browser matches any preset identification information, the comparison is ended Process and determine that the identification information matches the preset identification information.
  • the server may compare the similarity between the identification information and the any preset identification information. If the similarity is greater than or equal to a preset similarity threshold (for example, 90%), it can be determined that the identification information matches any preset identification information.
  • a preset similarity threshold for example, 90%
  • the implementation of the embodiments of this application can prevent the problem of abnormal page loading caused by session information failure.
  • the embodiment of the present application also provides a login processing device based on data processing.
  • the device includes a module for executing the method described in FIG. 2 or FIG. 3, and is configured on a server.
  • FIG. 4 it is a schematic block diagram of a login processing apparatus based on data processing provided by an embodiment of the present application.
  • the login processing device based on data processing in this embodiment includes:
  • the communication module 40 is configured to receive a first login request sent by a user through a browser, where the first login request carries a session identifier;
  • the processing module 41 is configured to determine first session information matching the session identifier from at least one piece of pre-stored session information, where the first session information includes login information for the user to log in to the service system corresponding to the server ;
  • the processing module 41 is further configured to obtain the pre-recorded historical acquisition time when the first session information is successfully acquired, and determine whether the time difference between the historical acquisition time and the system time is less than a preset time difference threshold, A preset time difference threshold is less than the invalidation duration corresponding to the first session information, and the history acquisition time is earlier than the time when the first login request is received;
  • the communication module 40 is further configured to return the first session information to the browser if the processing module determines that the time difference between the historical acquisition time and the system time is less than the preset time difference threshold, so that Performing login processing in the browser based on the first session information.
  • the first login request also carries transmission parameters corresponding to the first login request, and the transmission parameters include the user ID of the user and the identification information of the client corresponding to the browser.
  • the processing module 41 is further configured to, if it is determined that the time difference between the historical acquisition time and the system time is not less than the preset time difference threshold, obtain the second time required for the user to log in to the business system based on the transmission parameters. Session information
  • the communication module 40 is further configured to return the second session information to the browser, so that the browser can perform login processing based on the second session information.
  • the first login request also carries the transmission parameters corresponding to the first login request
  • the processing module 41 is further configured to determine whether the historical acquisition time and the system time are obtained. If the time difference is not less than the preset time difference threshold, trigger the execution of the acquisition operation of acquiring the second session information required for the user to log in to the business system based on the transmission parameters, and start a timer for timing;
  • the communication module 40 is further configured to return the second session information to the browser if the processing module 41 successfully obtains the second session information and the timing duration corresponding to the timer is less than a preset duration threshold. Session information, so that the browser performs login processing based on the second session information;
  • the communication module 40 is further configured to return to the browser if the processing module 41 fails to acquire the second session information when the timing duration corresponding to the timer is greater than or equal to the preset duration threshold
  • the first session information facilitates the browser to perform login processing based on the first session information.
  • the processing module 41 is further configured to, if the second session information is successfully obtained, and the timing duration corresponding to the timer is less than the preset duration threshold, then the system time is used as the second session information.
  • the historical acquisition time when the session information is successfully acquired; and the historical acquisition time when the second session information is successfully acquired is stored in a database in association with the second session information.
  • the communication module 40 is further configured to receive a second login request for logging in to the service system for the first time sent by a user through a browser, and the second login request carries the user logging in to the service.
  • System login information ;
  • the processing module 41 is further configured to generate session information including the login information and a session identifier corresponding to the session information, and store the session identifier and the session information in a database in association with each other;
  • the communication module 40 is also used to return the session identifier to the browser.
  • the processing module 41 is further configured to determine the target user type to which the user belongs from at least one preset user type based on the log-in information, and obtain the target user type based on the target user type.
  • the invalidation duration of the session information corresponding to the user is determined, and the session identifier, the session information, and the invalidation duration of the session information are stored in a database in association with each other.
  • the first login request carries identification information of the browser
  • the processing module 41 is also used to compare the identification information of the browser with preset identification information. If the identification information matches the preset identification information, the step of determining the first session information matching the session identification from at least one pre-stored session information is performed.
  • each functional module of the data processing-based login processing device described in the embodiment of the present application can be implemented according to the method in the method embodiment described in FIG. 2 or FIG. 3, and the specific implementation process can be referred to The related description of the method embodiment of FIG. 2 or FIG. 3 will not be repeated here.
  • FIG. 5 is a schematic block diagram of a server provided by an embodiment of the present application.
  • the server includes a processor 501, a memory 502 and a network interface 503.
  • the above-mentioned processor 501, memory 502, and network interface 503 may be connected through a bus or other methods.
  • the connection through a bus is taken as an example.
  • the network interface 503 is controlled by the processor to send and receive messages
  • the memory 502 is used to store a computer program
  • the computer program includes program instructions
  • the processor 501 is used to execute the program instructions stored in the memory 502.
  • the processor 501 is configured to call the program instructions to execute: receive a first login request sent by a user through a browser, the first login request carries a session identifier; and determine from at least one piece of pre-stored session information First session information that matches the session identifier, the first session information includes the login information of the user logging in to the service system corresponding to the server; acquiring the pre-recorded history of the successful acquisition of the first session information Time, and determine whether the time difference between the historical acquisition time and the system time is less than a preset time difference threshold, the preset time difference threshold is less than the expiration time corresponding to the first session information, and the history acquisition time is earlier than the received The time of the first login request; if it is determined that the time difference between the historical acquisition time and the system time is less than the preset time difference threshold, the first session information is returned to the browser to facilitate the browsing
  • the device performs login processing based on the first session information
  • the first login request also carries transmission parameters corresponding to the first login request, and the transmission parameters include the user ID of the user and the identification information of the client corresponding to the browser.
  • the processor 501 is further configured to, if it is determined that the time difference between the historical acquisition time and the system time is not less than the preset time difference threshold, acquire the second time required for the user to log in to the business system based on the transmission parameters. Session information
  • the network interface 503 is also used to return the second session information to the browser, so that the browser can perform login processing based on the second session information.
  • the first login request also carries the transmission parameters corresponding to the first login request
  • the processor 501 is further configured to determine whether the historical acquisition time and the system time are If the time difference is not less than the preset time difference threshold, trigger the execution of the acquisition operation of acquiring the second session information required for the user to log in to the business system based on the transmission parameters, and start a timer for timing;
  • the network interface 503 is further configured to return the second session information to the browser if the processor 501 successfully obtains the second session information and the timing duration corresponding to the timer is less than a preset duration threshold. Session information, so that the browser performs login processing based on the second session information;
  • the network interface 503 is further configured to return to the browser if the processor 501 fails to obtain the second session information when the timing duration corresponding to the timer is greater than or equal to the preset duration threshold
  • the first session information facilitates the browser to perform login processing based on the first session information.
  • the processor 501 is further configured to, if the second session information is successfully obtained and the timing duration corresponding to the timer is less than the preset duration threshold, then the system time is used as the second session information.
  • the historical acquisition time when the session information is successfully acquired; and the historical acquisition time when the second session information is successfully acquired is stored in a database in association with the second session information.
  • the network interface 503 is further configured to receive a second login request for logging in to the service system for the first time sent by a user through a browser, and the second login request carries the user logging in to the service System login information;
  • the processor 501 is further configured to generate session information including the login information and a session identifier corresponding to the session information, and store the session identifier and the session information in a database in association;
  • the network interface 503 is also used to return the session identifier to the browser.
  • the processor 501 is further configured to determine the target user type to which the user belongs from at least one preset user type based on the login information, and to obtain the target user type based on the target user type.
  • the invalidation duration of the session information corresponding to the user is determined, and the session identifier, the session information, and the invalidation duration of the session information are stored in a database in association with each other.
  • the first login request carries identification information of the browser
  • the processor 501 is further configured to compare the identification information of the browser with preset identification information. If the identification information matches the preset identification information, the step of determining the first session information matching the session identification from at least one pre-stored session information is performed.
  • the so-called processor 501 may be a central processing unit (Central Processing Unit, CPU), and the processor 501 may also be other general-purpose processors or digital signal processors (Digital Signal Processors, DSPs). ), Application Specific Integrated Circuit (ASIC), Field-Programmable Gate Array (FPGA) or other programmable logic devices, discrete gates or transistor logic devices, discrete hardware components, etc.
  • the general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like.
  • the memory 502 may include a read-only memory and a random access memory, and provides instructions and data to the processor 501.
  • a part of the memory 502 may also include a non-volatile random access memory.
  • the memory 502 may also store device type information.
  • the processor 501, the memory 502, and the network interface 503 described in the embodiment of this application can execute the implementation described in the method embodiment described in FIG. 2 or FIG.
  • the implementation of the login processing device based on data processing described in the embodiment of the present application will not be repeated here.
  • a computer non-volatile readable storage medium stores a computer program.
  • the computer program includes program instructions. When executed by the processor, it is implemented: receiving a first login request sent by a user through a browser, the first login request carrying a session identifier; determining the first one matching the session identifier from at least one piece of pre-stored session information Session information, the first session information includes the login information for the user to log in to the service system corresponding to the server; obtain the pre-recorded historical acquisition time when the first session information is successfully acquired, and determine the historical acquisition time Whether the time difference with the system time is less than a preset time difference threshold, the preset time difference threshold is less than the invalidation duration corresponding to the first session information, and the history acquisition time is earlier than the time when the first login request is received; If it is determined that the time difference between the historical acquisition time and the system time is less than the preset time difference threshold, the first session information is returned
  • the computer non-volatile readable storage medium may be the internal storage unit of the server described in any of the foregoing embodiments, such as the hard disk or memory of the server.
  • the computer non-volatile readable storage medium may also be an external storage device of the server, such as a plug-in hard disk equipped on the server, a smart memory card (Smart Media Card, SMC), and a secure digital (Secure Digital) , SD) card, flash card (Flash Card), etc.
  • the computer non-volatile readable storage medium may also include both an internal storage unit of the server and an external storage device.
  • the computer non-volatile readable storage medium is used to store the computer program and other programs and data required by the server.
  • the computer non-volatile readable storage medium can also be used to temporarily store data that has been output or will be output.
  • the program can be stored in a computer readable storage medium. During execution, it may include the procedures of the above-mentioned method embodiments.
  • the storage medium may be a magnetic disk, an optical disc, a read-only memory (Read-Only Memory, ROM), or a random access memory (Random Access Memory, RAM), etc.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Theoretical Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Data Mining & Analysis (AREA)
  • Computer Hardware Design (AREA)
  • Computer Security & Cryptography (AREA)
  • Computing Systems (AREA)
  • Information Transfer Between Computers (AREA)
  • Computer And Data Communications (AREA)

Abstract

本申请实施例公开了一种基于数据处理的登录处理方法及相关设备，所述方法应用于数据处理技术领域，包括：接收用户通过浏览器发送的携带有会话标识的第一登录请求，并从预先存储的至少一个会话信息中确定出与会话标识匹配，获取预先记录的第一会话信息被成功获取的历史获取时间，若判断得到历史获取时间与系统时间之间的时间差小于预设时间差阈值，则将第一会话信息返回至浏览器，以便于该浏览器基于该第一会话信息进行登录处理。采用本申请，可以防止会话信息失效而导致的页面加载异常的问题。

Description

一种基于数据处理的登录处理方法及相关设备
本申请要求于2019年5月21日提交中国专利局、申请号为201910427042.6、申请名称为“一种基于数据处理的登录处理方法及相关设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及计算机技术领域，尤其涉及一种基于数据处理的登录处理方法及相关设备。
背景技术
随着信息时代的到来，一套IT系统已经不能满足企业发展的需求，往往会建设多套IT系统，多套IT系统一般采用互不联系的域名或者采用多级域名的方式实现。而这些系统之间一般会采用单点登录(Single Sign On，SSO)实现系统间互相登录，避免用户在个系统间反复登录的问题。
在系统间互相登录过程中，需要通过获取用户的会话信息(如session)进行登录，但会话信息一般具有时效性，如果用户在使用需要登录的功能时(如查看个人信息或者登录系统)，正好会话信息过期，会导致该登录功能对应页面加载异常，甚至可能导致页面白屏，严重影响用户体验。
发明内容
本申请实施例提供了一种基于数据处理的登录处理方法及相关设备，可以防止会话信息失效而导致的页面加载异常的问题。
第一方面，本申请实施例提供了一种基于数据处理的登录处理方法，所述方法应用于服务器，该方法包括：
接收用户通过浏览器发送的第一登录请求，所述第一登录请求携带有会话标识；
从预先存储的至少一个会话信息中确定出与所述会话标识匹配的第一会话信息，所述第一会话信息中包括所述用户登录所述服务器对应业务系统的登录信息；
获取预先记录的所述第一会话信息被成功获取的历史获取时间，并判断所述历史获取时间与系统时间之间的时间差是否小于预设时间差阈值，所述预设时间差阈值小于所述第一会话信息对应的失效时长，所述历史获取时间早于接收到所述第一登录请求的时间；
若判断得到所述历史获取时间与系统时间的时间差小于所述预设时间差阈值，则将所述第一会话信息返回至所述浏览器，以便于所述浏览器基于所述第一会话信息进行登录处理。
第二方面，本申请实施例提供了一种基于数据处理的登录处理装置，该基于数据处理的登录处理装置包括用于执行上述第一方面的方法的模块。
第三方面，本申请实施例提供了一种服务器，该服务器包括处理器、网络接口和存储器，所述处理器、网络接口和存储器相互连接，其中，所述网络接口受所述处理器的控制用于收发消息，所述存储器用于存储支持服务器执行上述方法的计算机程序，所述计算机程序包括程序指令，所述处理器被配置用于调用所述程序指令，执行上述第一方面的方法。
第四方面，本申请实施例提供了一种计算机非易失性可读存储介质，所述计算机非易失性可读存储介质存储有计算机程序，所述计算机程序包括程序指令，所述程序指令当被处理器执行时使所述处理器执行上述第一方面的方法。
本申请实施例中，服务器可以从预先存储的至少一个会话信息中确定出与会话标识匹配的第一会话信息，若判断得到第一会话信息被成功获取的历史获取时间与系统时间之间的时间差小于预设时间差阈值，则将第一会话信息返回至浏览器，以便于该浏览器基于第一会话信息进行登录处理。可以防止会话信息失效而导致的页面加载异常的问题。
附图说明
图1是本申请实施例提供的一种登录处理系统的结构示意图；
图2是本申请实施例提供的一种基于数据处理的登录处理方法的流程示意图；
图3是本申请实施例提供的另一种基于数据处理的登录处理方法的流程示意图；
图4是本申请实施例提供的一种基于数据处理的登录处理装置的示意性框图；
图5是本申请实施例提供的一种服务器的示意性框图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述，显然，所描述的实施例是本申请一部分实施例，而不是全部的实施例。基于本申请中的实施例，本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其他实施例，都属于本申请保护的范围。
请参见图1，是本申请实施例提供的一种基于数据处理的登录处理系统的结构示意图。如图1所示，该登录处理系统可包括：业务系统对应的客户端10、浏览器11和服务器12。其中，该客户端10可以为该业务系统对应的应用程序，也可以为安装有该业务系统对应的应用程序终端，用于与用户进行交互；该浏览器11为该浏览器提供页面加载的服务，该浏览器11可以为一个应用程序安装于客户端10对应的终端；该服务器12为该业务系统对应的服务器，用于提供该业务系统的相关服务。
在一个实施例中，当处于未登录状态的用户通过客户端10首次登录该业务系统时，需要提供登录所需的登录信息，例如：账号，密码等，并向浏览器11发送携带有该登录信息的登录请求。浏览器11可以将该登录请求(即第二登录请求)转发至服务器12，服务器12可以根据登录请求中的登录信息创建一个该用户对应浏览器11专属的会话信息(如session)，并将该用户的登录信息存入该专属的会话信息中，后续用户在该业务系统中的所有状态信息均可以存入该专属的会话信息session中。进一步地，服务器可以生成该session对应的会话标识(如session id)，并将该会话信息与会话标识关联存储，将该会话标识返回至浏览器11，浏览器11可以将该会话标识存储。但由于服务器存储有大量用户对应浏览器(以下简称用户浏览器)的会话信息，每个用户对应一个会话信息，因此，为了防止服务器存储空间被会话信息过多的占用，每个session均对应有一个失效时长。该session的失效时长是从session不活跃的时候开始计算，如果session一直活跃，那么session就总不会失效，该失效时长是从该session未被访问(即被成功获取)开始计时，一旦session被访问，计时清零。
进一步地，后续用户继续访问该业务系统过程中，当客户端10检测到用户想要切换到需要登录信息的页面(如查看个人信息、查看购物车等等)，客户端10可以自动向浏览器11发送该用户对应的第一登录请求，浏览器11接收到该第一登录请求后，可以将预先存储的会话标识放入该第一登录请求，并将携带该会话标识的第一登录请求发送至服务器12，服务器12检测到该第一登录请求中的会话标识后，从预先存储的至少一个session中确定出与上述会话标识匹配的第一session(即预先存储的上述会话信息)。其中，由于每一次该第一session被成功获取，服务器12均会记录一次该第一session被成功获取的时间，并将 该成功获取的时间记为第一session被成功获取的历史获取时间，进而将该历史获取时间与该第一session关联存储。
进一步地，服务器12从预先存储的至少一个session中确定出与上述会话标识匹配的第一session后，可以获取预先记录的第一session被成功获取的历史获取时间，并判断历史获取时间与系统时间之间的时间差是否小于预设时间差阈值，该预设时间差阈值小于第一会话信息对应的失效时长，该历史获取时间早于接收到第一登录请求的时间。进一步地，若服务器12判断得到历史获取时间与系统时间的时间差小于预设时间差阈值，则通过将第一session返回至浏览器11，浏览器11可以根据第一session中包括的该用户的登录信息，自动进行登录操作，并加载用户想要查看的该需要登录信息的页面，页面加载完成后，客户端10可以展示该页面。采用这种方式，可以防止由于session失效而导致的页面加载异常的问题，有利于提高用户体验。
参见图2，图2是本申请实施例提供的一种基于数据处理的登录处理方法的流程示意图，该方法应用于服务器，可由服务器执行，如图所示，该基于数据处理的登录处理方法可包括：
201：接收用户通过浏览器发送的第一登录请求，该第一登录请求携带有会话标识。
在一个实施例中，服务器可以接收用户通过浏览器发送的首次登录业务系统的第二登录请求，该第二登录请求中携带有用户登录业务系统的登录信息。进一步地，服务器可以生成包括该登录信息的会话信息以及会话信息对应的会话标识，并将该会话标识和会话信息关联存储至数据库中，并将会话标识返回至浏览器。
示例性地，当用户通过客户端首次登录业务系统时，可以通过该业务系统对应的客户端输入自身的登录信息，并提交首次登录请求，该登录信息包括用户在业务系统注册账号提交的个人信息，如账号名、登录密码等。进一步地，客户端可以将上述登录信息加入该首次登录请求，并将携带有该登录信息的首次登录请求(即第二登录请求)发送至服务器。
进一步地，服务器接收用户通过浏览器发送的首次登录该业务系统的第二登录请求时，可以创建该用户对应的session(即会话信息)，并将第二登录请求中的登录信息放入该用户对应的session中，并生成该用户对应session的会话标识(如session id)，关联存储该用户对应的session和session id，并将该session id返回至浏览器。当浏览器接收到该session id后，会将这个session id存放在自身的进程内存里。进一步地，当用户通过继续访问该业务系统时，客户端检测到用户想要访问的网页为需要登录的目标网页(如查看个人信息的网页、查看购物车的网页、查看账户余额的网页等等)时，客户端可以向浏览器发送登录请求(即第一登录请求)用于访问该目标网页。
进一步地，该浏览器接收到该登录请求后，可以将上述session id加入该登录请求里发送给业务系统对应的服务器，该服务器接收到该携带有session id的登录请求之后，可以依据该session id找到相应的session，并从该session中取出登录信息，再次使用，为该用户服务，从而实现对该用户的会话跟踪。
202：从预先存储的至少一个会话信息中确定出与会话标识匹配的第一会话信息，该第一会话信息中包括该用户登录服务器对应业务系统的登录信息。
在一个实施例中，服务器的数据库中关联存储有至少一个会话信息以及至少一个会话标识，会话信息与会话标识具有一一对应关系。示例性地，会话信息为session，会标标识为session id，该会话信息与会话标识的对应关系如表1所示。这种情况下，假设步骤201中第一登录请求携带的会话标识为“2E28D987”，那么，则可以将session1确定为与会话标识“2E28D987”匹配的第一会话信息。
表1
session session id
session1 2E28D987
session2 1E00D987
session3 3B00D180
203：获取预先记录的第一会话信息被成功获取的历史获取时间，并判断历史获取时间与系统时间之间的时间差是否小于预设时间差阈值。其中，该预设时间差阈值小于第一会话信息对应的失效时长，该历史获取时间早于接收到该第一登录请求的时间。
204：若判断得到该历史获取时间与系统时间的时间差小于预设时间差阈值，则将第一会话信息返回至浏览器，以便于该浏览器基于第一会话信息进行登录处理。
在一个实施例中，由于服务器存储有大量用户浏览器的会话信息(如session)，每个用户对应一个会话信息，因此，为了防止服务器存储空间被会话信息过多的占用，每个会话信息均预先设置有一个失效时长。该会话信息的失效时长是从会话信息不活跃的时候开始计算，如果会话信息一直活跃，那么该会话信息就总不会失效，该失效时长是从该会话信息未被访问(即被成功获取)开始计时，一旦会话信息被访问，计时清零。
进一步地，每一次会话信息被成功获取，均会记录一次该会话信息被成功获取的历史获取时间。例如，第一会话信息session1在系统时间为2018.12.29-21:11:00被成功获取，则可以在数据库中记录该session1被成功获取的历史获取时间为2018.12.29-21:11:00。后续，若该session1再次被成功获取，则可以再次利用当前的系统时间(例如2018.12.29-21:11:59)去更新该历史获取时间。
其中，步骤203中获取的第一会话信息被成功获取的历史获取时间，则是获取的上一次第一会话信息被成功获取的历史获取时间，也即，可以理解为最新的这一次历史获取时间。
其中，上述预设时间差阈值小于该第一会话信息预先设置的失效时长。例如，第一会话信息预先设置的失效时长为15分钟，那么该预设时间差阈值可以为8分钟。该失效时长和预设时间差阈值均可以是开发人员根据实验测算数据设置的。
在一个实施例中，不同类型的用户所对应会话信息的失效时长可以不同，那么，由于预设时间差阈值小于失效时长，那么不同类型的用户的会话信息所对应的预设时间差阈值也不相同。该类型可以指用户的角色，例如，若用户为管理人员(例如业务系统的运维人员)登录业务系统后，可能需要对业务系统进行检查调整，那么该管理人员对应会话信息的失效时长则可以比普通用户长。
或者，除了结合用户的角色以外，还可以进一步地结合用户的历史访问频率或者用户等级对用户进行分类。例如，历史访问频率高的用户，可能对业务系统比较熟悉，则可以对此类用户对应的会话信息设置较小(相比于历史访问频率较低的用户的较小)的失效时长。也即，历史访问频率越高的用户，对应会话信息的失效时长较小。
又例如，用户等级越高的用户对应会话信息可以设置更长的失效时长。采用这样的方式，可以让等级更高的用户享受更好的用户体验。
在一个实施例中，服务器可以基于第二登录请求中携带的登录信息从预先设置的至少一种用户类型中确定出用户所属的目标用户类型，并基于该目标用户类型从预先设置的用户类型与失效时长的对应关系中，确定出该用户对应会话信息的失效时长，进一步地，可以将该会话信息对应的会话标识、会话信息以及会话信息的失效时长关联存储至数据库中。 进一步地，开发人员可以根据该会话信息的失效时长设置该会话信息对应的预设时间差阈值。
例如，用户类型分为运维人员和普通用户，用户类型与失效时长的对应关系中表示：普通用户的会话信息对应的失效时长为15分钟，运维人员对应的失效时长为10分钟。这种情况下，当服务器基于第二登录请求中的登录信息确定出该用户为运维人员后，则可以根据该用户类型与失效时长的对应关系，确定出该用户对应会话信息的失效时长为15分钟，进而可以依据该15分钟的失效时长设置该用户的会话信息对应的预设时间差阈值，例如可以为8分钟。
在一个实施例中，服务器可以获取预先记录的第一会话信息被成功获取的历史获取时间，并判断历史获取时间与系统时间之间的时间差是否小于预设时间差阈值。
示例性地，第一会话信息为session1，第一会话信息上一次被成功获取的历史获取时间为2018.12.29-21:11:59，当前的系统时间为2018.12.29-21:12:59，预设时间差阈值为8分钟。这种情况下，服务器可以计算出第一会话信息上一次被成功获取的历史获取时间2018.12.29-21:11:59与系统时间2018.12.29-21:12:59之间的时间差为1分钟，进一步地，可以得到该时间差1分钟小于预设时间差阈值8分钟，则可以直接将该session1返回浏览器。进一步地，该浏览器可以基于第一会话信息中的该用户的登录信息和配置信息进行登录处理，并加载登录处理后的页面。
在一个实施例中，上述第一登录请求中还携带有第一登录请求对应的传输参数，该传输参数包括该用户的用户ID和该浏览器对应客户端的标识信息，例如，客户端为一个应用程序，该客户端的标识信息可以为客户端的名字、ID、版本号等等。这种情况下，若服务器判断得到历史获取时间与系统时间的时间差不小于预设时间差阈值，则可以基于该传输参数获取用户登录该业务系统所需的第二会话信息，并向浏览器返回该第二会话信息，以便于浏览器基于第二会话信息进行登录处理。其中，该第二会话信息可以理解为服务器根据传输参数调用网络数据接口获取到的最新的会话信息，而上述提到的第一会话信息，是预先缓存的会话信息。
实施本申请实施例，可以防止会话信息失效而导致的页面加载异常的问题。
参见图3，图3是本申请实施例提供的另一种基于数据处理的登录处理方法的流程示意图，该方法可由服务器执行，如图所示，该基于数据处理的登录处理方法可包括：
301：接收用户通过浏览器发送的第一登录请求，该第一登录请求携带有会话标识和第一登录请求对应的传输参数。
302：从预先存储的至少一个会话信息中确定出与会话标识匹配的第一会话信息，该第一会话信息中包括该用户登录服务器对应业务系统的登录信息。
303：获取预先记录的第一会话信息被成功获取的历史获取时间，并判断历史获取时间与系统时间之间的时间差是否小于预设时间差阈值。
其中，步骤301～步骤303的具体实施方式可以参见上述实施例中步骤201～步骤203的相关描述，此处不再赘述。
304：若判断得到该历史获取时间与系统时间的时间差不小于预设时间差阈值，则触发执行基于上述传输参数获取用户登录该业务系统所需的第二会话信息的获取操作，并开启计时器进行计时。
305：若成功获取该第二会话信息，且计时器对应的计时时长小于预设时长阈值，则向浏览器返回该第二会话信息，以便于该浏览器基于第二会话信息进行登录处理。
在一个实施例中，由于客户端需要通过浏览器加载H5页面。当用户想要访问需要登录的页面(以下简称目标页面，该目标页面例如可以为查看个人账户的页面)时，若浏览器想要加载该目标页面，则需要利用该用户的登录信息进行登录处理，才能正常加载该目 标页面。其中，该用户的登录信息存储在该用户对应的会话信息(如session)中。因此，浏览器想要加载该目标页面，则需要获取该用户对应的会话信息。
在一个实施例中，当服务端根据传输参数获取最新的session(即第二会话信息)时，若该获取时间过长，会影响到目标页面的加载，进而引起目标页面出现白屏。为了避免这种情况发生，本申请可以实时检测计时器对应的计时时长是否小于预设时长阈值，以及实时检测是否成功获取该最新的session。若成功获取该第二会话信息时，计时器对应的计时时长小于预设时长阈值，则将该获取到的最新的session返回浏览器，以便于浏览器基于第二会话信息进行登录处理，加载目标页面。采用这种方式，可以避免获取时间过长，而导致的页面白屏现象。
在一个实施例中，若在该计时器对应的计时时长大于或者等于预设时长阈值时，未成功获取到该第二会话信息，则浏览器返回第一会话信息，以便于浏览器基于第一会话信息进行登录处理。
示例性地，预设时长阈值为3s，服务器触发执行基于传输参数获取用户登录该业务系统所需的第二会话信息的获取操作，也即，启动获取第二会话信息，
并开启计时器进行计时。进一步地，服务器实时获取计时器的计时时长，并实时检测该计时时长是否小于预设时长阈值。当服务器成功获取到第二会话信息时，检测到该计时时长为2s，该2s小于预设时长阈值3s，则可以将获取到的第二会话信息返回至浏览器。若检测到当前计时时长等于3s时，还未成功获取到该第二会话信息，则可以将预先获取的第一会话信息返回至浏览器。
其中，获取计时器的计时时长可以是实时获取，也可以是按照预设时间间隔获取，或者其他时间规则获取，本申请对此不作具体限定。
在一个实施例中，若服务器成功获取到该第二会话信息，且计时器对应的计时时长小于该预设时长阈值，则将系统时间作为第二会话信息被成功获取的历史获取时间。进一步地，可以将第二会话信息被成功获取的历史获取时间与该第二会话信息关联存储至数据库中。
其中，当服务器将第二会话信息被成功获取的历史获取时间与该第二会话信息关联存储至数据库中时，还可以将上述第一登录请求携带的会话标识与该第二会话信息以及该历史获取时间关联存储至数据库中，也即，该会话标识、第二会话信息以及第二会话信息被成功获取的历史获取时间三者具有一一对应关系。
或者，在另一个实施例中，若服务器成功获取到该第二会话信息，还可以实时为该第二会话信息生成新的会话标识。进一步地，服务器可以将该新的会话标识、第二会话信息以及第二会话信息被成功获取的历史获取时间三者关联存储至数据库中；另一方面，服务器可以将该新的会话标识返回至浏览器，浏览器接收到该新的会话标识后，可以将该新的会话标识存储在进程内存中，当后续需要继续访问服务器对应的业务系统时，可以将该新的会话标识携带在访问请求(如第一登录请求)中。
示例性地，假设第一登录请求携带的会话标识为“2E28D987”，第一会话信息为session1，第二会话信息为session2，服务器成功获取到该session2，且计时器对应的计时时长小于预设时长阈值，当前的系统时间为2018.12.29-21:13:59。这种情况下，可以把该2018.12.29-21:13:59作为session2被成功获取的历史获取时间，并将该历史获取时间2018.12.29-21:13:59、session2和会话标识“2E28D987”三者关联存储至数据库中。当再次接收到携带该会话标识“2E28D987”的访问请求时，则可以将该session2确定为与会话标识“2E28D987”匹配的会话信息，并利用该session2执行后续的步骤。
在一个实施例中，所述第一登录请求中携带有浏览器的标识信息，该浏览器的标识信息例如可以为浏览器的名称、版本号、ID等等。在一个实施例中，基于业务需求或者安全 性的考虑，业务系统的访问只对指定的浏览器提供服务。这种情况下，开发人员可以预先在服务器的数据库中录入这些指定的浏览器(即预设浏览器)的预设标识信息，当接收到用户通过浏览器发送的第一登录请求时，可以将第一登录请求中携带的浏览器的标识信息与预设标识信息进行对比，
若对比得到该标识信息与预设标识信息匹配，则触发执行从预先存储的至少一个会话信息中确定出与会话标识匹配的第一会话信息的步骤。
在一个实施例中，数据库中预先存储的预设标识信息包括多个，服务器可以按照多个预设标识信息本身的存储顺序，依次将该浏览器的标识信息与预设标识信息进行对比，若在依次对比过程中，确定出该浏览器的标识信息与任一预设标识信息匹配，则结束对比过程，并确定该标识信息与预设标识信息匹配。
或者，服务器可以随机将多个预设标识信息中的一个或者多个预设标识信息同时与该标识信息对比，若对比得到该浏览器的标识信息与任一预设标识信息匹配，则结束对比过程，并确定该标识信息与预设标识信息匹配。
在一个实施例中，在浏览器的标识信息与任一预设标识信息的对比过程中，服务器可以对该标识信息和该任一预设标识信息进行相似度对比，若检测到两者之间的相似度大于或者等于预设相似度阈值(例如90％)，则可以确定该标识信息和该任一预设标识信息匹配。
实施本申请实施例可以防止会话信息失效而导致的页面加载异常的问题。
本申请实施例还提供了一种基于数据处理的登录处理装置。该装置包括用于执行前述图2或者图3所述的方法的模块，配置于服务器。具体地，参见图4，是本申请实施例提供的基于数据处理的登录处理装置的示意框图。本实施例的基于数据处理的登录处理装置包括：
通信模块40，用于接收用户通过浏览器发送的第一登录请求，所述第一登录请求携带有会话标识；
处理模块41，用于从预先存储的至少一个会话信息中确定出与所述会话标识匹配的第一会话信息，所述第一会话信息中包括所述用户登录所述服务器对应业务系统的登录信息；
所述处理模块41，还用于获取预先记录的所述第一会话信息被成功获取的历史获取时间，并判断所述历史获取时间与系统时间之间的时间差是否小于预设时间差阈值，所述预设时间差阈值小于所述第一会话信息对应的失效时长，所述历史获取时间早于接收到所述第一登录请求的时间；
所述通信模块40，还用于若所述处理模块判断得到所述历史获取时间与系统时间的时间差小于所述预设时间差阈值，则将所述第一会话信息返回至所述浏览器，以便于所述浏览器基于所述第一会话信息进行登录处理。
在一个实施例中，所述第一登录请求中还携带有所述第一登录请求对应的传输参数，所述传输参数包括所述用户的用户ID和所述浏览器对应客户端的标识信息，所述处理模块41，还用于若判断得到所述历史获取时间与系统时间的时间差不小于所述预设时间差阈值，则基于所述传输参数获取所述用户登录所述业务系统所需的第二会话信息；
所述通信模块40，还用于向所述浏览器返回所述第二会话信息，以便于所述浏览器基于所述第二会话信息进行登录处理。
在一个实施例中，所述第一登录请求中还携带有所述第一登录请求对应的所述传输参数，所述处理模块41，还用于若判断得到所述历史获取时间与系统时间的时间差不小于所述预设时间差阈值，则触发执行基于所述传输参数获取所述用户登录所述业务系统所需的第二会话信息的获取操作，并开启计时器进行计时；
所述通信模块40，还用于若所述处理模块41成功获取所述第二会话信息，且所述计时器对应的计时时长小于预设时长阈值，则向所述浏览器返回所述第二会话信息，以便于 所述浏览器基于所述第二会话信息进行登录处理；
所述通信模块40，还用于若所述处理模块41在所述计时器对应的计时时长大于或者等于预设时长阈值时，未成功获取所述第二会话信息，则向所述浏览器返回所述第一会话信息，以便于所述浏览器基于所述第一会话信息进行登录处理。
在一个实施例中，所述处理模块41还用于若成功获取所述第二会话信息，且所述计时器对应的计时时长小于所述预设时长阈值，则将系统时间作为所述第二会话信息被成功获取的历史获取时间；将所述第二会话信息被成功获取的历史获取时间与所述第二会话信息关联存储至数据库中。
在一个实施例中，所述通信模块40，还用于接收用户通过浏览器发送的首次登录所述业务系统的第二登录请求，所述第二登录请求中携带有所述用户登录所述业务系统的登录信息；
所述处理模块41，还用于生成包括所述登录信息的会话信息以及所述会话信息对应的会话标识，将所述会话标识和所述会话信息关联存储至数据库中；
所述通信模块40，还用于将所述会话标识返回至所述浏览器。
在一个实施例中，所述处理模块41，还用于基于所述登录信息从预先设置的至少一种用户类型中确定出所述用户所属的目标用户类型，并基于所述目标用户类型从预先设置的用户类型与失效时长的对应关系中，确定出所述用户对应会话信息的失效时长，进而将所述会话标识、所述会话信息以及所述会话信息的失效时长关联存储至数据库中。
在一个实施例中，所述第一登录请求中携带有所述浏览器的标识信息，所述处理模块41，还用于所述浏览器的标识信息与预设标识信息进行对比，若对比得到所述标识信息与所述预设标识信息匹配，则执行所述从预先存储的至少一个会话信息中确定出与所述会话标识匹配的第一会话信息的步骤。
需要说明的是，本申请实施例所描述的基于数据处理的登录处理装置的各功能模块的功能可根据图2或者图3所述的方法实施例中的方法具体实现，其具体实现过程可以参照图2或者图3的方法实施例的相关描述，此处不再赘述。
请参见图5，图5是本申请实施例提供的一种服务器的示意性框图，如图5所示，该服务器包括，处理器501、存储器502和网络接口503。上述处理器501、存储器502和网络接口503可通过总线或其他方式连接，在本申请实施例所示图5中以通过总线连接为例。其中，网络接口503受所述处理器的控制用于收发消息，存储器502用于存储计算机程序，所述计算机程序包括程序指令，处理器501用于执行存储器502存储的程序指令。其中，处理器501被配置用于调用所述程序指令执行：接收用户通过浏览器发送的第一登录请求，所述第一登录请求携带有会话标识；从预先存储的至少一个会话信息中确定出与所述会话标识匹配的第一会话信息，所述第一会话信息中包括所述用户登录所述服务器对应业务系统的登录信息；获取预先记录的所述第一会话信息被成功获取的历史获取时间，并判断所述历史获取时间与系统时间之间的时间差是否小于预设时间差阈值，所述预设时间差阈值小于所述第一会话信息对应的失效时长，所述历史获取时间早于接收到所述第一登录请求的时间；若判断得到所述历史获取时间与系统时间的时间差小于所述预设时间差阈值，则将所述第一会话信息返回至所述浏览器，以便于所述浏览器基于所述第一会话信息进行登录处理
在一个实施例中，所述第一登录请求中还携带有所述第一登录请求对应的传输参数，所述传输参数包括所述用户的用户ID和所述浏览器对应客户端的标识信息，所述处理器501，还用于若判断得到所述历史获取时间与系统时间的时间差不小于所述预设时间差阈值，则基于所述传输参数获取所述用户登录所述业务系统所需的第二会话信息；
所述网络接口503，还用于向所述浏览器返回所述第二会话信息，以便于所述浏览器 基于所述第二会话信息进行登录处理。
在一个实施例中，所述第一登录请求中还携带有所述第一登录请求对应的所述传输参数，所述处理器501，还用于若判断得到所述历史获取时间与系统时间的时间差不小于所述预设时间差阈值，则触发执行基于所述传输参数获取所述用户登录所述业务系统所需的第二会话信息的获取操作，并开启计时器进行计时；
所述网络接口503，还用于若所述处理器501成功获取所述第二会话信息，且所述计时器对应的计时时长小于预设时长阈值，则向所述浏览器返回所述第二会话信息，以便于所述浏览器基于所述第二会话信息进行登录处理；
所述网络接口503，还用于若所述处理器501在所述计时器对应的计时时长大于或者等于预设时长阈值时，未成功获取所述第二会话信息，则向所述浏览器返回所述第一会话信息，以便于所述浏览器基于所述第一会话信息进行登录处理。
在一个实施例中，所述处理器501还用于若成功获取所述第二会话信息，且所述计时器对应的计时时长小于所述预设时长阈值，则将系统时间作为所述第二会话信息被成功获取的历史获取时间；将所述第二会话信息被成功获取的历史获取时间与所述第二会话信息关联存储至数据库中。
在一个实施例中，所述网络接口503，还用于接收用户通过浏览器发送的首次登录所述业务系统的第二登录请求，所述第二登录请求中携带有所述用户登录所述业务系统的登录信息；
所述处理器501，还用于生成包括所述登录信息的会话信息以及所述会话信息对应的会话标识，将所述会话标识和所述会话信息关联存储至数据库中；
所述网络接口503，还用于将所述会话标识返回至所述浏览器。
在一个实施例中，所述处理器501，还用于基于所述登录信息从预先设置的至少一种用户类型中确定出所述用户所属的目标用户类型，并基于所述目标用户类型从预先设置的用户类型与失效时长的对应关系中，确定出所述用户对应会话信息的失效时长，进而将所述会话标识、所述会话信息以及所述会话信息的失效时长关联存储至数据库中。
在一个实施例中，所述第一登录请求中携带有所述浏览器的标识信息，所述处理器501，还用于所述浏览器的标识信息与预设标识信息进行对比，若对比得到所述标识信息与所述预设标识信息匹配，则执行所述从预先存储的至少一个会话信息中确定出与所述会话标识匹配的第一会话信息的步骤。
应当理解，在本申请实施例中，所称处理器501可以是中央处理单元(Central Processing Unit，CPU)，该处理器501还可以是其他通用处理器、数字信号处理器(Digital Signal Processor，DSP)、专用集成电路(Application Specific Integrated Circuit，ASIC)、现成可编程门阵列(Field-Programmable Gate Array，FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
该存储器502可以包括只读存储器和随机存取存储器，并向处理器501提供指令和数据。存储器502的一部分还可以包括非易失性随机存取存储器。例如，存储器502还可以存储设备类型的信息。
具体实现中，本申请实施例中所描述的处理器501、存储器502和网络接口503可执行本申请实施例提供的图2或者图3所述的方法实施例所描述的实现方式，也可执行本申请实施例所描述的基于数据处理的登录处理装置的实现方式，在此不再赘述。
在本申请的另一实施例中提供一种计算机非易失性可读存储介质，所述计算机非易失性可读存储介质存储有计算机程序，所述计算机程序包括程序指令，所述程序指令被处理器执行时实现：接收用户通过浏览器发送的第一登录请求，所述第一登录请求携带有会话 标识；从预先存储的至少一个会话信息中确定出与所述会话标识匹配的第一会话信息，所述第一会话信息中包括所述用户登录所述服务器对应业务系统的登录信息；获取预先记录的所述第一会话信息被成功获取的历史获取时间，并判断所述历史获取时间与系统时间之间的时间差是否小于预设时间差阈值，所述预设时间差阈值小于所述第一会话信息对应的失效时长，所述历史获取时间早于接收到所述第一登录请求的时间；若判断得到所述历史获取时间与系统时间的时间差小于所述预设时间差阈值，则将所述第一会话信息返回至所述浏览器，以便于所述浏览器基于所述第一会话信息进行登录处理。
所述计算机非易失性可读存储介质可以是前述任一实施例所述的服务器的内部存储单元，例如服务器的硬盘或内存。所述计算机非易失性可读存储介质也可以是所述服务器的外部存储设备，例如所述服务器上配备的插接式硬盘，智能存储卡(Smart Media Card，SMC)，安全数字(Secure Digital，SD)卡，闪存卡(Flash Card)等。进一步地，所述计算机非易失性可读存储介质还可以既包括所述服务器的内部存储单元也包括外部存储设备。所述计算机非易失性可读存储介质用于存储所述计算机程序以及所述服务器所需的其他程序和数据。所述计算机非易失性可读存储介质还可以用于暂时地存储已经输出或者将要输出的数据。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程，是可以通过计算机程序来指令相关的硬件来完成，所述的程序可存储于一计算机可读取存储介质中，该程序在执行时，可包括如上述各方法的实施例的流程。其中，所述的存储介质可为磁碟、光盘、只读存储记忆体(Read-Only Memory，ROM)或随机存储记忆体(Random Access Memory，RAM)等。
以上所揭露的仅为本申请的部分实施例而已，当然不能以此来限定本申请之权利范围，本领域普通技术人员可以理解实现上述实施例的全部或部分流程，并依本申请权利要求所作的等同变化，仍属于发明所涵盖的范围。

Claims (20)

  1. 一种基于数据处理的登录处理方法，其特征在于，所述方法应用于服务器，所述方法包括：
    接收用户通过浏览器发送的第一登录请求，所述第一登录请求携带有会话标识；
    从预先存储的至少一个会话信息中确定出与所述会话标识匹配的第一会话信息，所述第一会话信息中包括所述用户登录所述服务器对应业务系统的登录信息；
    获取预先记录的所述第一会话信息被成功获取的历史获取时间，并判断所述历史获取时间与系统时间之间的时间差是否小于预设时间差阈值，所述预设时间差阈值小于所述第一会话信息对应的失效时长，所述历史获取时间早于接收到所述第一登录请求的时间；
    若判断得到所述历史获取时间与系统时间的时间差小于所述预设时间差阈值，则将所述第一会话信息返回至所述浏览器，以便于所述浏览器基于所述第一会话信息进行登录处理。
  2. 根据权利要求1所述的方法，其特征在于，所述第一登录请求中还携带有所述第一登录请求对应的传输参数，所述传输参数包括所述用户的用户ID和所述浏览器对应客户端的标识信息，所述方法还包括：
    若判断得到所述历史获取时间与系统时间的时间差不小于所述预设时间差阈值，则基于所述传输参数获取所述用户登录所述业务系统所需的第二会话信息；
    向所述浏览器返回所述第二会话信息，以便于所述浏览器基于所述第二会话信息进行登录处理。
  3. 根据权利要求1所述的方法，其特征在于，所述第一登录请求中还携带有所述第一登录请求对应的所述传输参数，所述方法还包括：
    若判断得到所述历史获取时间与系统时间的时间差不小于所述预设时间差阈值，则触发执行基于所述传输参数获取所述用户登录所述业务系统所需的第二会话信息的获取操作，并开启计时器进行计时；
    若成功获取所述第二会话信息，且所述计时器对应的计时时长小于预设时长阈值，则向所述浏览器返回所述第二会话信息，以便于所述浏览器基于所述第二会话信息进行登录处理；
    若在所述计时器对应的计时时长大于或者等于预设时长阈值时，未成功获取所述第二会话信息，则向所述浏览器返回所述第一会话信息，以便于所述浏览器基于所述第一会话信息进行登录处理。
  4. 根据权利要求3所述的方法，其特征在于，所述方法还包括：
    若成功获取所述第二会话信息，且所述计时器对应的计时时长小于所述预设时长阈值，则将系统时间作为所述第二会话信息被成功获取的历史获取时间；
    将所述第二会话信息被成功获取的历史获取时间与所述第二会话信息关联存储至数据库中。
  5. 根据权利要求1所述的方法，其特征在于，所述接收用户通过浏览器发送的第一登录请求之前，所述方法还包括：
    接收用户通过浏览器发送的首次登录所述业务系统的第二登录请求，所述第二登录请求中携带有所述用户登录所述业务系统的登录信息；
    生成包括所述登录信息的会话信息以及所述会话信息对应的会话标识；
    将所述会话标识和所述会话信息关联存储至数据库中，并将所述会话标识返回至所述 浏览器。
  6. 根据权利要求5所述的方法，其特征在于，所述将所述会话标识和所述会话信息关联存储至数据库中之前，所述方法还包括：
    基于所述登录信息从预先设置的至少一种用户类型中确定出所述用户所属的目标用户类型；
    基于所述目标用户类型从预先设置的用户类型与失效时长的对应关系中，确定出所述用户对应会话信息的失效时长；
    其中，所述将所述会话标识和所述会话信息关联存储至数据库中，包括：
    将所述会话标识、所述会话信息以及所述会话信息的失效时长关联存储至数据库中。
  7. 根据权利要求5所述的方法，其特征在于，所述将所述会话标识和所述会话信息关联存储至数据库中之前，所述方法还包括：
    基于所述登录信息获取所述用户的历史访问频率；
    从预先设置的访问频率与失效时长的对应关系中将所述历史访问频率对应的失效时长，确定为所述用户对应会话信息的失效时长；
    其中，所述将所述会话标识和所述会话信息关联存储至数据库中，包括：
    将所述会话标识、所述会话信息以及所述会话信息的失效时长关联存储至数据库中。
  8. 一种基于数据处理的登录处理装置，其特征在于，所述装置配置于服务器，所述登录处理装置包括：
    通信模块，用于接收用户通过浏览器发送的第一登录请求，所述第一登录请求携带有会话标识；
    处理模块，用于从预先存储的至少一个会话信息中确定出与所述会话标识匹配的第一会话信息，所述第一会话信息中包括所述用户登录所述服务器对应业务系统的登录信息；
    所述处理模块，还用于获取预先记录的所述第一会话信息被成功获取的历史获取时间，并判断所述历史获取时间与系统时间之间的时间差是否小于预设时间差阈值，所述预设时间差阈值小于所述第一会话信息对应的失效时长，所述历史获取时间早于接收到所述第一登录请求的时间；
    所述通信模块，还用于若所述处理模块判断得到所述历史获取时间与系统时间的时间差小于所述预设时间差阈值，则将所述第一会话信息返回至所述浏览器，以便于所述浏览器基于所述第一会话信息进行登录处理。
  9. 根据权利要求8所述的装置，其特征在于，所述第一登录请求中还携带有所述第一登录请求对应的传输参数，所述传输参数包括所述用户的用户ID和所述浏览器对应客户端的标识信息，所述处理模块，还用于若判断得到所述历史获取时间与系统时间的时间差不小于所述预设时间差阈值，则基于所述传输参数获取所述用户登录所述业务系统所需的第二会话信息；所述通信模块，还用于向所述浏览器返回所述第二会话信息，以便于所述浏览器基于所述第二会话信息进行登录处理。
  10. 根据权利要求8所述的装置，其特征在于，所述第一登录请求中还携带有所述第一登录请求对应的所述传输参数，所述处理模块，还用于若判断得到所述历史获取时间与系统时间的时间差不小于所述预设时间差阈值，则触发执行基于所述传输参数获取所述用户登录所述业务系统所需的第二会话信息的获取操作，并开启计时器进行计时；所述通信模块，还用于若成功获取所述第二会话信息，且所述计时器对应的计时时长小于预设时长阈值，则向所述浏览器返回所述第二会话信息，以便于所述浏览器基于所述第二会话信息进行登录处理，若在所述计时器对应的计时时长大于或者等于预设时长阈值时，未成功获取所述第二会话信息，则向所述浏览器返回所述第一会话信息，以便于所述浏览器基于所述第一会话信息进行登录处理。
  11. 根据权利要求10所述的装置，其特征在于，所述处理模块，还用于若成功获取所述第二会话信息，且所述计时器对应的计时时长小于所述预设时长阈值，则将系统时间作为所述第二会话信息被成功获取的历史获取时间；将所述第二会话信息被成功获取的历史获取时间与所述第二会话信息关联存储至数据库中。
  12. 根据权利要求8所述的装置，其特征在于，所述通信模块，还用于接收用户通过浏览器发送的首次登录所述业务系统的第二登录请求，所述第二登录请求中携带有所述用户登录所述业务系统的登录信息；所述处理模块，还用于生成包括所述登录信息的会话信息以及所述会话信息对应的会话标识，将所述会话标识和所述会话信息关联存储至数据库中；所述通信模块，还用于将所述会话标识返回至所述浏览器。
  13. 根据权利要求12所述的装置，所述处理模块，还用于基于所述登录信息从预先设置的至少一种用户类型中确定出所述用户所属的目标用户类型；基于所述目标用户类型从预先设置的用户类型与失效时长的对应关系中，确定出所述用户对应会话信息的失效时长；将所述会话标识、所述会话信息以及所述会话信息的失效时长关联存储至数据库中。
  14. 根据权利要求12所述的装置，其特征在于，所述处理模块，还用于基于所述登录信息获取所述用户的历史访问频率；从预先设置的访问频率与失效时长的对应关系中将所述历史访问频率对应的失效时长，确定为所述用户对应会话信息的失效时长；将所述会话标识、所述会话信息以及所述会话信息的失效时长关联存储至数据库中。
  15. 一种服务器，其特征在于，包括处理器、存储器和网络接口，所述处理器、所述存储器和所述网络接口相互连接，其中，所述存储器用于存储计算机程序，所述计算机程序包括程序指令，所述处理器被配置用于调用所述程序指令执行：通过所述网络接口接收用户通过浏览器发送的第一登录请求，所述第一登录请求携带有会话标识；从预先存储的至少一个会话信息中确定出与所述会话标识匹配的第一会话信息，所述第一会话信息中包括所述用户登录所述服务器对应业务系统的登录信息；获取预先记录的所述第一会话信息被成功获取的历史获取时间，并判断所述历史获取时间与系统时间之间的时间差是否小于预设时间差阈值，所述预设时间差阈值小于所述第一会话信息对应的失效时长，所述历史获取时间早于接收到所述第一登录请求的时间；若判断得到所述历史获取时间与系统时间的时间差小于所述预设时间差阈值，则通过所述网络接口将所述第一会话信息返回至所述浏览器，以便于所述浏览器基于所述第一会话信息进行登录处理。
  16. 根据权利要求15所述的服务器，其特征在于，所述第一登录请求中还携带有所述第一登录请求对应的传输参数，所述传输参数包括所述用户的用户ID和所述浏览器对应客户端的标识信息，所述处理器，还用于若判断得到所述历史获取时间与系统时间的时间差不小于所述预设时间差阈值，则基于所述传输参数获取所述用户登录所述业务系统所需的第二会话信息，通过所述网络接口向所述浏览器返回所述第二会话信息，以便于所述浏览器基于所述第二会话信息进行登录处理。
  17. 根据权利要求15所述的服务器，其特征在于，所述第一登录请求中还携带有所述第一登录请求对应的所述传输参数，所述处理器，还用于若判断得到所述历史获取时间与系统时间的时间差不小于所述预设时间差阈值，则触发执行基于所述传输参数获取所述用户登录所述业务系统所需的第二会话信息的获取操作，并开启计时器进行计时，若通过所述网络接口成功获取所述第二会话信息，且所述计时器对应的计时时长小于预设时长阈值，则向所述浏览器返回所述第二会话信息，以便于所述浏览器基于所述第二会话信息进行登录处理，若在所述计时器对应的计时时长大于或者等于预设时长阈值时，未成功获取所述第二会话信息，则通过所述网络接口向所述浏览器返回所述第一会话信息，以便于所述浏览器基于所述第一会话信息进行登录处理。
  18. 根据权利要求17所述的服务器，其特征在于，所述处理器，还用于若成功获取所 述第二会话信息，且所述计时器对应的计时时长小于所述预设时长阈值，则将系统时间作为所述第二会话信息被成功获取的历史获取时间；将所述第二会话信息被成功获取的历史获取时间与所述第二会话信息关联存储至数据库中。
  19. 根据权利要求15所述的服务器，其特征在于，所述处理器，还用于通过所述网络接口接收用户通过浏览器发送的首次登录所述业务系统的第二登录请求，所述第二登录请求中携带有所述用户登录所述业务系统的登录信息；所述处理器，还用于生成包括所述登录信息的会话信息以及所述会话信息对应的会话标识，将所述会话标识和所述会话信息关联存储至数据库中，并通过所述网络接口将所述会话标识返回至所述浏览器。
  20. 一种计算机非易失性可读存储介质，其特征在于，所述计算机非易失性可读存储介质存储有计算机程序，所述计算机程序包括程序指令，所述程序指令当被处理器执行时使所述处理器执行如权利要求1-7任一项所述的方法。
PCT/CN2019/120966 2019-05-21 2019-11-26 一种基于数据处理的登录处理方法及相关设备 WO2020233059A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201910427042.6A CN110213356B (zh) 2019-05-21 2019-05-21 一种基于数据处理的登录处理方法及相关设备
CN201910427042.6 2019-05-21

Publications (1)

Publication Number Publication Date
WO2020233059A1 true WO2020233059A1 (zh) 2020-11-26

Family

ID=67788187

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2019/120966 WO2020233059A1 (zh) 2019-05-21 2019-11-26 一种基于数据处理的登录处理方法及相关设备

Country Status (2)

Country Link
CN (1) CN110213356B (zh)
WO (1) WO2020233059A1 (zh)

Cited By (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112529534A (zh) * 2020-12-18 2021-03-19 中国平安财产保险股份有限公司 登录态续时提醒方法、装置、设备及计算机可读存储介质
CN112751851A (zh) * 2020-12-29 2021-05-04 成都科来网络技术有限公司 一种ssh登录成功行为判断方法、装置及存储介质
CN113194039A (zh) * 2021-04-23 2021-07-30 京东数科海益信息科技有限公司 系统数据流量的切分方法和装置、电子设备和存储介质
CN113282354A (zh) * 2021-06-28 2021-08-20 中国平安人寿保险股份有限公司 应用程序的h5页面加载方法、装置、设备及存储介质
CN113297601A (zh) * 2021-06-17 2021-08-24 国网信通亿力科技有限责任公司 一种基于敏感特征的数据处理系统
CN113452753A (zh) * 2021-05-21 2021-09-28 北京奇艺世纪科技有限公司 数据分发方法、装置、设备及存储介质
CN113709514A (zh) * 2021-09-02 2021-11-26 北京一起教育科技有限责任公司 一种数据处理方法、装置和电子设备
CN113778832A (zh) * 2021-09-28 2021-12-10 京东方科技集团股份有限公司 设备信息处理方法及装置、可读存储介质、电子设备
CN113838238A (zh) * 2021-09-26 2021-12-24 北京紫光展锐通信技术有限公司 业务处理方法、装置及设备
CN113923797A (zh) * 2021-09-26 2022-01-11 深圳市广和通无线通信软件有限公司 会话建立方法、装置、客户端设备和计算机存储介质
CN113965380A (zh) * 2021-10-21 2022-01-21 上海高顿教育科技有限公司 一种基于多个后台应用的单点登录控制方法和装置
CN114143285A (zh) * 2021-10-29 2022-03-04 青岛海尔科技有限公司 分布式系统中生成id的方法、装置及服务器
CN114301688A (zh) * 2021-12-29 2022-04-08 天翼物联科技有限公司 基于客户权限的登录校验方法、装置、物联网终端及介质
CN114866247A (zh) * 2022-04-18 2022-08-05 杭州海康威视数字技术股份有限公司 一种通信方法、装置、系统、终端及服务器
CN114885005A (zh) * 2022-04-08 2022-08-09 北京齐尔布莱特科技有限公司 减少同步消息数据的方法、装置、设备及介质

Families Citing this family (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN110213356B (zh) * 2019-05-21 2021-11-12 深圳壹账通智能科技有限公司 一种基于数据处理的登录处理方法及相关设备
CN112839016B (zh) * 2019-11-25 2023-03-21 上海哔哩哔哩科技有限公司 会话控制方法及装置
CN111385356B (zh) * 2020-03-04 2023-06-23 平安科技（深圳）有限公司 分布式会话处理方法、装置及系统
CN111818179A (zh) * 2020-08-07 2020-10-23 中国工商银行股份有限公司 用户请求的处理方法、装置、计算设备和介质
CN112738218A (zh) * 2020-12-28 2021-04-30 平安消费金融有限公司 基于区块链的跨会话链路追踪方法、装置及存储介质
CN114363395A (zh) * 2021-12-31 2022-04-15 深圳金蝶账无忧网络科技有限公司 会话处理方法、装置及计算机可读存储介质
CN115225716B (zh) * 2022-07-15 2023-08-01 中国联合网络通信集团有限公司 数据处理方法、装置和电子设备

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104954331A (zh) * 2014-03-27 2015-09-30 杭州迪普科技有限公司 一种登录认证配置装置及方法
CN107483418A (zh) * 2017-07-27 2017-12-15 阿里巴巴集团控股有限公司 登录处理方法、业务处理方法、装置及服务器
CN108234483A (zh) * 2017-12-29 2018-06-29 五八有限公司 用户登录续约方法、装置、终端及存储介质
CN110213356A (zh) * 2019-05-21 2019-09-06 深圳壹账通智能科技有限公司 一种基于数据处理的登录处理方法及相关设备

Family Cites Families (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101635707A (zh) * 2008-07-25 2010-01-27 国际商业机器公司 在Web环境中为用户提供身份管理的方法和装置
CN103532919B (zh) * 2012-07-06 2018-06-12 腾讯科技（深圳）有限公司 用户账户保持登录态的方法及系统
CN104158818B (zh) * 2014-08-25 2018-09-11 中国联合网络通信集团有限公司 一种单点登录方法及系统
CN104468506A (zh) * 2014-10-28 2015-03-25 大唐移动通信设备有限公司 会话状态检测方法及装置
CN108650334B (zh) * 2018-08-02 2021-03-30 东软集团股份有限公司 一种会话失效的设置方法及装置

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN104954331A (zh) * 2014-03-27 2015-09-30 杭州迪普科技有限公司 一种登录认证配置装置及方法
CN107483418A (zh) * 2017-07-27 2017-12-15 阿里巴巴集团控股有限公司 登录处理方法、业务处理方法、装置及服务器
CN108234483A (zh) * 2017-12-29 2018-06-29 五八有限公司 用户登录续约方法、装置、终端及存储介质
CN110213356A (zh) * 2019-05-21 2019-09-06 深圳壹账通智能科技有限公司 一种基于数据处理的登录处理方法及相关设备

Cited By (24)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112529534B (zh) * 2020-12-18 2024-04-05 中国平安财产保险股份有限公司 登录态续时提醒方法、装置、设备及计算机可读存储介质
CN112529534A (zh) * 2020-12-18 2021-03-19 中国平安财产保险股份有限公司 登录态续时提醒方法、装置、设备及计算机可读存储介质
CN112751851A (zh) * 2020-12-29 2021-05-04 成都科来网络技术有限公司 一种ssh登录成功行为判断方法、装置及存储介质
CN112751851B (zh) * 2020-12-29 2023-05-23 科来网络技术股份有限公司 一种ssh登录成功行为判断方法、装置及存储介质
CN113194039A (zh) * 2021-04-23 2021-07-30 京东数科海益信息科技有限公司 系统数据流量的切分方法和装置、电子设备和存储介质
CN113452753A (zh) * 2021-05-21 2021-09-28 北京奇艺世纪科技有限公司 数据分发方法、装置、设备及存储介质
CN113297601B (zh) * 2021-06-17 2022-07-12 国网信通亿力科技有限责任公司 一种基于敏感特征的数据处理系统
CN113297601A (zh) * 2021-06-17 2021-08-24 国网信通亿力科技有限责任公司 一种基于敏感特征的数据处理系统
CN113282354A (zh) * 2021-06-28 2021-08-20 中国平安人寿保险股份有限公司 应用程序的h5页面加载方法、装置、设备及存储介质
CN113282354B (zh) * 2021-06-28 2023-04-07 中国平安人寿保险股份有限公司 应用程序的h5页面加载方法、装置、设备及存储介质
CN113709514B (zh) * 2021-09-02 2023-06-23 北京一起教育科技有限责任公司 一种数据处理方法、装置和电子设备
CN113709514A (zh) * 2021-09-02 2021-11-26 北京一起教育科技有限责任公司 一种数据处理方法、装置和电子设备
CN113838238A (zh) * 2021-09-26 2021-12-24 北京紫光展锐通信技术有限公司 业务处理方法、装置及设备
CN113923797A (zh) * 2021-09-26 2022-01-11 深圳市广和通无线通信软件有限公司 会话建立方法、装置、客户端设备和计算机存储介质
CN113778832B (zh) * 2021-09-28 2024-05-14 京东方科技集团股份有限公司 设备信息处理方法及装置、可读存储介质、电子设备
CN113778832A (zh) * 2021-09-28 2021-12-10 京东方科技集团股份有限公司 设备信息处理方法及装置、可读存储介质、电子设备
CN113965380A (zh) * 2021-10-21 2022-01-21 上海高顿教育科技有限公司 一种基于多个后台应用的单点登录控制方法和装置
CN114143285B (zh) * 2021-10-29 2023-11-28 青岛海尔科技有限公司 分布式系统中生成id的方法、装置及服务器
CN114143285A (zh) * 2021-10-29 2022-03-04 青岛海尔科技有限公司 分布式系统中生成id的方法、装置及服务器
CN114301688B (zh) * 2021-12-29 2023-08-01 天翼物联科技有限公司 基于客户权限的登录校验方法、装置、物联网终端及介质
CN114301688A (zh) * 2021-12-29 2022-04-08 天翼物联科技有限公司 基于客户权限的登录校验方法、装置、物联网终端及介质
CN114885005A (zh) * 2022-04-08 2022-08-09 北京齐尔布莱特科技有限公司 减少同步消息数据的方法、装置、设备及介质
CN114866247B (zh) * 2022-04-18 2024-01-02 杭州海康威视数字技术股份有限公司 一种通信方法、装置、系统、终端及服务器
CN114866247A (zh) * 2022-04-18 2022-08-05 杭州海康威视数字技术股份有限公司 一种通信方法、装置、系统、终端及服务器

Also Published As

Publication number Publication date
CN110213356B (zh) 2021-11-12
CN110213356A (zh) 2019-09-06

Similar Documents

Publication Publication Date Title
WO2020233059A1 (zh) 一种基于数据处理的登录处理方法及相关设备
CN111030936B (zh) 网络访问的限流控制方法、装置及计算机可读存储介质
RU2622876C2 (ru) Способ, устройство и электронное устройство для управления соединениями
US9491182B2 (en) Methods and systems for secure internet access and services
US9544295B2 (en) Login method for client application and corresponding server
US11652905B2 (en) Systems and methods for controlling real-time traffic surge of application programming interfaces (APIs) at server
CN108989263B (zh) 短信验证码攻击防护方法、服务器和计算机可读存储介质
US10050899B2 (en) Data processing method, apparatus, client, server and system
US20170063836A1 (en) Method, device, and system for access control of a cloud hosting service
US10542044B2 (en) Authentication incident detection and management
US10419445B2 (en) Credential change management system
CN110784457B (zh) 一种业务访问方法及装置
TW202018558A (zh) 驗證及授權的方法及驗證伺服器
CN112134954A (zh) 服务请求处理方法、装置、电子设备及存储介质
CN109688109B (zh) 基于客户端信息识别的验证码的验证方法及装置
US20160381160A1 (en) System and Computer Implemented Method of Personal Monitoring
CN108881929B (zh) 一种设置直播间登录提示的方法和装置
CN114866247B (zh) 一种通信方法、装置、系统、终端及服务器
US20160036853A1 (en) Storage medium storing program for login alerts, and method and system thereof
US11363020B2 (en) Method, device and storage medium for forwarding messages
CN112506896A (zh) 一种数据删除方法、装置及电子设备
CN110673971A (zh) 登录会话过期的处理方法、装置及用户终端
CN111385358B (zh) 会话控制对象的同步方法、装置和服务器
CN113742697B (zh) 一种设备所有权变更方法、装置、设备及介质
CN115037557B (zh) 一种用于用户访问应用的临时身份认证方法和装置

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 19929614

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205 DATED 01/03/2022)

122 Ep: pct application non-entry in european phase

Ref document number: 19929614

Country of ref document: EP

Kind code of ref document: A1