US2019149553A1PendingUtilityA1

Method, device and server for managing user login sessions

Assignee: ALIBABA GROUP HOLDING LTDPriority: May 7, 2015Filed: Jan 9, 2019Published: May 16, 2019
Est. expiryMay 7, 2035(~8.8 yrs left)· nominal 20-yr term from priority
Inventors:Dian Xu
H04L 63/083G06F 21/46G06F 21/31H04L 67/14H04L 63/08H04L 63/20G06F 21/35H04L 63/102
48
PatentIndex Score
0
Cited by
0
References
0
Claims

Abstract

The present disclosure provides a method, device and server for managing user login sessions. A session cache list is queried, using a user ID and after a user has successfully logged in with the user ID via the login medium, whether a login session queue corresponding to the user ID exists in the session cache list. If the login session queue exists in the session cache list, a user login status is managed through the login session queue. If the login session queue corresponding to the user ID is absent from the session cache list, a session ID corresponding to the user's login is stored in a login session queue corresponding to the user ID in the session cache list. A legitimate user is able to effectively manage each login created with the user's user ID through the login session queue, and to prevent any login sessions created when the user ID is used to log in from being beyond the legitimate user's control.

Claims

exact text as granted — not AI-modified
1 . A method comprising:
 querying, using a server computing device and a user ID, to detect whether a login session queue corresponding to the user ID exists in a session cache list, the querying being performed after a successful login of the user with the user ID via a login medium;   managing, using the server computing device, the user's login status through the login session queue, if the querying detects that the login session queue corresponding to the user ID exists in the session cache list; and   storing, using the server computing device, a session ID in a login session queue corresponding to the UID in the session cache list if the querying detects an absence of the login session queue corresponding to the user ID in the session cache list.   
     
     
         2 . The method of  claim 1 , further comprising:
 creating a session ID in response to the user's login; and   establishing a mapping relationship between the user ID and the session ID.   
     
     
         3 . The method of  claim 1 , managing the user login status through the login session queue further comprising:
 determining, using the server computing device, whether a size of the login session queue exceeds a predetermined threshold;   determining, using the server computing device, whether each login session in the login session queue is an invalid login session in the login session queue, deleting each login session determined to be an invalid login session from the login session queue, and storing each invalid login session deleted from the login session queue in a first database, if the size of the login session queue is determined to exceed the predetermined threshold; and   storing, using the server computing device, the session ID corresponding to the user's login in the login session queue, if the size of the login session queue is determined not to exceed the predetermined threshold.   
     
     
         4 . The method of  claim 3 , managing the user login status through the login session queue further comprising:
 determining, using the server computing device, the user's login permission settings after detecting that the user is performing a password change via a current login medium; and   managing each currently-active session ID in the login session queue in accordance with the login permission settings, comprising:
 determining, using the server computing device and for each currently-active session ID in the login session queue, whether the currently-active session ID is a permitted session ID in accordance with the login permission settings; 
 keeping, using the server computing device, the currently-active session that is identified as permitted in the login session queue, and deleting, from the login session queue, each currently-active session ID identified as unpermitted. 
   
     
     
         5 . The method of  claim 1 , managing the user login status through the login session queue further comprising:
 determining, using the server computing device and for each session ID, whether a storage duration of a login session corresponding to the session ID in the login session queue exceeds a predetermined storage cycle;   determining, using the server computing device and for each session ID, that the corresponding login session is an invalid login session in the login session queue if the storage duration exceeds the predetermined storage cycle; and   deleting, using the server computing device and for each invalid login session, the invalid login session from the login session queue and storing the invalid login session in a first database.   
     
     
         6 . The method of  claim 5 , further comprising:
 determining, using the server computing device, each session ID in the login session queue having a storage duration not exceeding the predetermined storage cycle as an active session ID in the login session queue; and   storing each determined active session ID in a second database.   
     
     
         7 . The method of  claim 5 , managing the user login status through the login session queue further comprising:
 determining, using the server computing device, the user's login permission settings after detecting that the user is performing a password change via a current login medium; and   managing each currently-active session ID in the login session queue in accordance with the login permission settings, comprising:
 determining, using the server computing device and for each currently-active session ID in the login session queue, whether the currently-active session ID is a permitted session ID in accordance with the login permission settings; 
 keeping, using the server computing device, the currently-active session that is identified as permitted in the login session queue, and deleting, from the login session queue, each currently-active session ID identified as unpermitted. 
   
     
     
         8 . The method of  claim 1 , managing the user login status through the login session queue further comprising:
 determining, using the server computing device, the user's login permission settings after detecting that the user is performing a password change via a current login medium; and   managing each currently-active session ID in the login session queue in accordance with the login permission settings.   
     
     
         9 . The method of  claim 8 , managing each currently-active session ID in the login session queue according to the login permission settings further comprising:
 determining, using the server computing device and for each currently-active session ID in the login session queue, whether the currently-active session ID is a permitted session ID in accordance with the login permission settings;   keeping, using the server computing device, the currently-active session that is identified as permitted in the login session queue, and deleting, from the login session queue, each currently-active session ID identified as unpermitted.   
     
     
         10 . A server computing device comprising:
 a query module querying, using a user ID, to detect whether a login session queue corresponding to the user ID exists in a session cache list, the querying being performed after a successful login of the user with the user ID via a login medium;   a managing module managing the user's login status through the login session queue, if the query module detects that the login session queue corresponding to the user ID exists in the session cache list; and   a first storage module storing a session ID in a login session queue corresponding to the UID in the session cache list if the query module detects an absence of the login session queue corresponding to the user ID in the session cache list.   
     
     
         11 . The device of  claim 10 , further comprising:
 a creation module creating a session ID in response to the user's login; and   a mapping module establishing a mapping relationship between the user ID and the session ID created by the creation module.   
     
     
         12 . The device of  claim 10 , the managing module further comprising:
 a first determination unit determining whether a size of the login session queue exceeds a predetermined threshold;   a second determination unit determining whether each login session in the login session queue is an invalid login session in the login session queue and deleting each login session determined to be an invalid login session from the login session queue, if the size of the login session queue is determined to exceed the predetermined threshold;   a storage unit storing the session ID corresponding to the user's login in the login session queue, if the size of the login session queue is determined not to exceed the predetermined threshold; and   a second storage module storing, in a first database, each invalid login session identified by the second determination unit.   
     
     
         13 . The device of  claim 12 , the managing module further comprising:
 a fifth determination unit determining the user's login permission settings after detecting that the user is performing a password change via a current login medium; and   a managing unit managing each currently-active session ID in the login session queue according to the login permission settings in accordance with the login permission settings determined by the fifth determination unit, the managing unit further comprising:
 a determination subunit determining, for each currently-active session ID in the login session queue, whether the currently-active session ID is a permitted session ID in accordance with the login permission settings; and 
 a managing subunit keeping each currently-active session ID that is identified by the determination subunit to be permitted in the login session queue, and deleting, from the login session queue, each currently-active session ID that is identified by the determination subunit to be unpermitted. 
   
     
     
         14 . The device of  claim 10 , the managing module further comprising:
 a third determination unit determining, for each session ID, whether a storage duration of a login session corresponding to the session ID in the login session queue exceeds a predetermined storage cycle;   a fourth determination unit determining, for each session ID, that the corresponding login session is an invalid login session in the login session queue, if the login session's storage duration determined by the third determination unit exceeds the predetermined storage cycle;   a deletion unit deleting each invalid login session identified by the fourth determination unit from the login session queue; and   a third storage module storing each invalid login session deleted from the login session queue by the deletion unit in a first database.   
     
     
         15 . The device of  claim 14 , further comprising:
 a determination module determining each session ID in the login session queue having a storage duration not exceeding the predetermined storage cycle as an active session ID in the login session queue; and   a fourth storage module storing each determined active session ID in a second database.   
     
     
         16 . The device of  claim 14 , the managing module further comprising:
 a fifth determination unit determining the user's login permission settings after detecting that the user is performing a password change via a current login medium; and   a managing unit managing each currently-active session ID in the login session queue according to the login permission settings in accordance with the login permission settings determined by the fifth determination unit, the managing unit further comprising:
 a determination subunit determining, for each currently-active session ID in the login session queue, whether the currently-active session ID is a permitted session ID in accordance with the login permission settings; and 
 a managing subunit keeping each currently-active session ID that is identified by the determination subunit to be permitted in the login session queue, and deleting, from the login session queue, each currently-active session ID that is identified by the determination subunit to be unpermitted. 
   
     
     
         17 . The device of  claim 10 , the managing module further comprising:
 a fifth determination unit determining the user's login permission settings after detecting that the user is performing a password change via a current login medium; and   a managing unit managing each currently-active session ID in the login session queue according to the login permission settings in accordance with the login permission settings determined by the fifth determination unit.   
     
     
         18 . The device of  claim 17 , the managing unit further comprising:
 a determination subunit determining, for each currently-active session ID in the login session queue, whether the currently-active session ID is a permitted session ID in accordance with the login permission settings; and   a managing subunit keeping each currently-active session ID that is identified by the determination subunit to be permitted in the login session queue, and deleting, from the login session queue, each currently-active session ID that is identified by the determination subunit to be unpermitted.   
     
     
         19 . A server, comprising:
 a processor; and   a storage medium for tangibly storing thereon program logic for execution by the processor, the stored program logic comprising:   querying logic executed by the processor for querying, using a user ID, to detect whether a login session queue corresponding to the user ID exists in a session cache list, the querying being performed after a successful login of the user with the user ID via a login medium;   managing logic executed by the processor for managing the user's login status through the login session queue, if the querying detects that the login session queue corresponding to the user ID exists in the session cache list; and   storing logic executed by the processor for storing a session ID in a login session queue corresponding to the UID in the session cache list if the querying detects an absence of the login session queue corresponding to the user ID in the session cache list.

Join the waitlist — get patent alerts

Track US2019149553A1 — get alerts on status changes and closely related new filings.

We store only your email — no account needed. See our privacy policy.