IP Library Granted Patent US 10,182,058
Granted Patent B2
US 10,182,058 · App. 15/146,074 · Granted Jan 15, 2019

Method, device and server for managing user login sessions

Inventor: Dian Xu (Hangzhou, CN)
Assignee: ALIBABA GROUP HOLDING LIMITED
H04L63/102H04L63/08H04L63/20
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 10,182,058
App. No.
15/146,074
Granted
Jan 15, 2019
Kind
B2
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 (74)

1. A method comprising:

detecting, at a server computing device, a successful login of a user via a login medium, the successful login including a user ID (UID) associated with the user;

querying, using the server computing device and the UID, a first database to detect whether a login session queue corresponding to the user ID exists in a session cache list, the login session queue comprising a mapping of the UID to at least one session ID;

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, the managing comprising archiving at least one session ID associated with the UID from the login session queue in a second database; and

storing, using the server computing device, a session ID in a new 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, the new login session queue stored in the first database.

2. The method of claim 1 , further comprising:

creating the 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 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 the second 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 the first 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 processor; and

a storage medium for tangibly storing thereon program logic for execution by the processor, the stored program logic comprising:

logic for detecting a successful login of a user via a login medium, the successful login including a user ID (UID) associated with the user;

logic executed by the processor for querying, using the UID, a first database to detect whether a login session queue corresponding to the user ID exists in a session cache list, the login session queue comprising a mapping of the UID to at least one session ID;

logic executed by the processor for managing the user's login status through the login session queue upon detecting that the login session queue corresponding to the user ID exists in the session cache list, the managing comprising archiving at least one session ID associated with the UID from the login session queue in a second database; and

logic executed by the processor for storing a session ID in a new login session queue corresponding to the UID in the session cache list upon detecting an absence of the login session queue corresponding to the user ID in the session cache list, the new login session queue stored in the first database.

11. The device of claim 10 , further comprising:

logic executed by the processor for creating the session ID in response to the user's login; and

logic executed by the processor for establishing a mapping relationship between the user ID and the session ID.

12. The device of claim 10 , the logic for managing the user's login status through the login session queue further comprising:

logic executed by the processor for determining whether a size of the login session queue exceeds a predetermined threshold;

logic executed by the processor for determining whether each login session in the login session queue is an invalid login session in the login session queue and deleting each invalid login session from the login session queue, if the size of the login session queue is determined to exceed the predetermined threshold;

logic executed by the processor for 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

logic executed by the processor for storing, in the second database, each invalid login session.

13. The device of claim 12 , the logic for managing the user's login status through the login session queue further comprising:

logic executed by the processor for determining the user's login permission settings after detecting that the user is performing a password change via a current login medium; and

logic executed by the processor formanaging each currently-active session ID in the login session queue according to the login permission settings in accordance with the login permission settings, the logic for managing the user's login status through the login session queue further comprising:

logic executed by the processor for 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

logic executed by the processor for keeping each currently-active session ID to be permitted in the login session queue, and deleting, from the login session queue, each currently-active session ID to be unpermitted.

14. The device of claim 10 , the logic for managing the user's login status through the login session queue further comprising:

logic executed by the processor for 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;

logic executed by the processor for 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 exceeds the predetermined storage cycle;

logic executed by the processor for deleting each invalid login session from the login session queue; and

logic executed by the processor for storing each invalid login session deleted from the login session queue in the second database.

15. The device of claim 14 , further comprising:

logic executed by the processor for 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

logic executed by the processor for storing each determined active session ID in the first database.

16. The device of claim 14 , the logic for managing the user's login status through the login session queue further comprising:

logic executed by the processor for determining the user's login permission settings after detecting that the user is performing a password change via a current login medium; and

logic executed by the processor for managing each currently-active session ID in the login session queue according to the login permission settings in accordance with the login permission settings, the logic for managing the user's login status through the login session queue further comprising:

logic executed by the processor for 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

logic executed by the processor for keeping each currently-active session ID to be permitted in the login session queue, and deleting, from the login session queue, each currently-active session ID to be unpermitted.

17. The device of claim 10 , the logic for managing the user's login status through the login session queue further comprising:

logic executed by the processor for determining the user's login permission settings after detecting that the user is performing a password change via a current login medium; and

logic executed by the processor for managing each currently-active session ID in the login session queue according to the login permission settings in accordance with the login permission settings.

18. The device of claim 17 , the logic for managing the user's login status through the login session queue further comprising:

logic executed by the processor for 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

logic executed by the processor for keeping each currently-active session ID to be permitted in the login session queue, and deleting, from the login session queue, each currently-active session ID to be unpermitted.

Assignments (3)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 10, 2020
From: ALIBABA GROUP HOLDING LIMITED
To: ADVANTAGEOUS NEW TECHNOLOGIES CO., LTD.
Reel/Frame 053735/0724 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 10, 2020
From: ADVANTAGEOUS NEW TECHNOLOGIES CO., LTD.
To: ADVANCED NEW TECHNOLOGIES CO., LTD.
Reel/Frame 053735/0867 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 17, 2016
From: XU, DIAN
To: ALIBABA GROUP HOLDING LIMITED
Reel/Frame 038943/0307 →
Priority Claims (1)
CN 2015 1 0229467 · May 7, 2015 · national
Continuity (1)
Related Publication 20160330206A1 · Nov 10, 2016
Cited By (86)
US 12,206,696 US 12,244,621 US 12,267,345 US 12,309,185 US 12,323,449 US 12,335,286 US 12,335,348 US 12,341,797 US 12,348,545 US 12,355,626 US 12,355,787 US 12,355,793 US 12,363,148 US 12,368,745 US 12,368,746 US 12,368,747 US 12,375,573 US 12,395,573 US 12,401,669 US 12,405,849 US 12,407,701 US 12,407,702 US 12,418,552 US 12,418,555 US 12,425,428 US 12,425,430 US 12,445,474 US 12,452,279 US 12,457,231 US 12,463,995 US 12,463,996 US 12,463,997 US 12,464,003 US 12,470,577 US 12,470,578 US 12,483,576 US 12,489,770 US 12,495,052 US 12,500,910 US 12,500,911 US 12,500,912 US 12,505,126 US 12,506,762 US 12,513,221 US 12,537,836 US 12,537,837 US 12,537,839 US 12,537,840 US 12,537,884 US 12,549,575 US 12,549,577 US 12,556,548 US 12,556,559 US 12,563,060 US 12,563,064 US 12,563,071 US 12,563,072 US 12,580,934 US 12,580,935 US 12,580,936 US 12,580,937 US 12,587,553 US 12,592,950 US 12,598,205 US 12,613,930 US 12,615,271 US 12,621,324 US 12,621,329 US 12,627,686 US 12,627,687 US 12,627,690 US 12,634,312 US 12,634,376 US 12,652,302 US 12,659,325 US 12,659,326 US 12,659,327 US 12,659,333 US 12,676,874 US 12,689,638 US 12,689,640 US 12,695,768 US 12,706,932 US 12,706,933 US 12,712,897 US 12,719,896