IP Library › Granted Patent US 11,360,912
Granted Patent B2
US 11,360,912 · App. 17/106,206 · Granted Jun 14, 2022

Method for performing adaptive locking range management, associated data storage device and controller thereof

Inventors: Chih-Yu Lin (Hsinchu County, TW); Hung-Ting Pan (Taoyuan, TW); Sung-Ling Hsu (New Taipei, TW)
Assignee: Silicon Motion, Inc.
G06F12/1466G06F3/0622G06F3/0658G06F3/0659G06F3/0679G06F12/06G06F21/62
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 11,360,912
App. No.
17/106,206
Granted
Jun 14, 2022
Kind
B2
Abstract

A method for performing adaptive locking range management, an associated data storage device and a controller thereof are provided. The method may include: receiving a security command from outside of the data storage device, wherein the security command is related to changing an old locking range into a new locking range; obtaining a start Logical Block Address (LBA) and a length value of the new locking range according to the security command; determining whether the start LBA of the new locking range is less than an end LBA of the old locking range, and determining whether an end LBA of the new locking range is greater than a start LBA of the old locking range; and in response to both determination results being true, performing data trimming on any respective non-overlapped portions of the new locking range and the old locking range.

Claims (37)

1. A method for performing adaptive locking range management, the method being applicable to a data storage device, the data storage device comprising a non-volatile (NV) memory, the NV memory comprising at least one NV memory element, the method comprising:

in response to a request of changing an old locking range into a new locking range, determining whether a start Logical Block Address (LBA) of the new locking range is less than an end LBA of the old locking range, and determining whether an end LBA of the new locking range is greater than a start LBA of the old locking range; and

in response to the start LBA of the new locking range being less than the end LBA of the old locking range and the end LBA of the new locking range being greater than the start LBA of the old locking range, performing data trimming on any respective non-overlapped portions of the new locking range and the old locking range.

2. The method of claim 1 , further comprising:

in response to a request of changing another old locking range into another new locking range, determining whether a start LBA of the another new locking range is less than an end LBA of the another old locking range;

in response to the start LBA of the another new locking range being less than the end LBA of the another old locking range, determining whether an end LBA of the another new locking range is greater than a start LBA of the another old locking range; and

in response to the end LBA of the another new locking range being not greater than the start LBA of the another old locking range, performing data trimming on the another new locking range and the another old locking range, respectively.

3. The method of claim 2 , further comprising:

in response to a request of changing yet another old locking range into yet another new locking range, determining whether a start LBA of the yet another new locking range is less than an end LBA of the yet another old locking range; and

in response to the start LBA of the yet another new locking range being not less than the end LBA of the yet another old locking range, performing data trimming on the yet another new locking range and the yet another old locking range, respectively.

4. The method of claim 3 , wherein the old locking range and the new locking range have partial locking ranges that are overlapped, the another new locking range and the another old locking range are not overlapped at all, and the yet another new locking range and the yet another old locking range are not overlapped at all.

5. The method of claim 2 , wherein the old locking range and the new locking range have partial locking ranges that are overlapped, and the another new locking range and the another old locking range are not overlapped at all.

6. The method of claim 1 , wherein the old locking range and the new locking range have partial locking ranges that are overlapped.

7. The method of claim 1 , further comprising:

in response to a request of changing another old locking range into another new locking range, determining whether a start LBA of the another new locking range is less than an end LBA of the another old locking range; and

in response to the start LBA of the another new locking range being not less than the end LBA of the another old locking range, performing data trimming on the another new locking range and the another old locking range, respectively.

8. The method of claim 7 , wherein the old locking range and the new locking range have partial locking ranges that are overlapped, and the another new locking range and the another old locking range are not overlapped at all.

9. A data storage device, comprising:

a non-volatile (NV) memory, configured to store information, wherein the NV memory comprises at least one NV memory element; and

a controller, coupled to the NV memory, configured to control operations of the data storage device, wherein the controller comprises:

a processing circuit, configured to control the controller according to a plurality of host commands from a host device, to allow the host device to access the NV memory through the controller, wherein:

in response to a request of changing an old locking range into a new locking range, the controller determines whether a start Logical Block Address (LBA) LBA of the new locking range is less than an end LBA of the old locking range, and determines whether an end LBA of the new locking range is greater than a start LBA of the old locking range; and

in response to the start LBA of the new locking range being less than the end LBA of the old locking range and the end LBA of the new locking range being greater than the start LBA of the old locking range, the controller performs data trimming on any respective non-overlapped portions of the new locking range and the old locking range.

10. The data storage device of claim 9 , wherein in response to a request of changing another old locking range into another new locking range, the controller determines whether a start LBA of the another new locking range is less than an end LBA of the another old locking range; in response to the start LBA of the another new locking range being less than the end LBA of the another old locking range, the controller determines whether an end LBA of the another new locking range is greater than a start LBA of the another old locking range; and in response to the end LBA of the another new locking range being not greater than the start LBA of the another old locking range, the controller performs data trimming on the another new locking range and the another old locking range, respectively.

11. The data storage device of claim 10 , wherein in response to a request of changing yet another old locking range into yet another new locking range, the controller determines whether a start LBA of the yet another new locking range is less than an end LBA of the yet another old locking range; and in response to the start LBA of the yet another new locking range being not less than the end LBA of the yet another old locking range, the controller performs data trimming on the yet another new locking range and the yet another old locking range, respectively.

12. The data storage device of claim 11 , wherein the old locking range and the new locking range have partial locking ranges that are overlapped, the another new locking range and the another old locking range are not overlapped at all, and the yet another new locking range and the yet another old locking range are not overlapped at all.

13. The data storage device of claim 10 , wherein the old locking range and the new locking range have partial locking ranges that are overlapped, and the another new locking range and the another old locking range are not overlapped at all.

14. The data storage device of claim 9 , wherein the old locking range and the new locking range have partial locking ranges that are overlapped.

15. The data storage device of claim 9 , wherein in response to a request of changing another old locking range into another new locking range, the controller determines whether a start LBA of the another new locking range is less than an end LBA of the another old locking range; and in response to the start LBA of the another new locking range being not less than the end LBA of the another old locking range, the controller performs data trimming on the another new locking range and the another old locking range, respectively.

16. The data storage device of claim 15 , wherein the old locking range and the new locking range have partial locking ranges that are overlapped, and the another new locking range and the another old locking range are not overlapped at all.

17. A controller of a data storage device, the data storage device comprising the controller and a non-volatile (NV) memory, the NV memory comprising at least one NV memory element, the controller comprising:

a processing circuit, configured to control the controller according to a plurality of host commands from a host device, to allow the host device to access the NV memory through the controller, wherein:

in response to a request of changing an old locking range into a new locking range, the controller determines whether a start Logical Block Address (LBA) of the new locking range is less than an end LBA of the old locking range, and determines whether an end LBA of the new locking range is greater than a start LBA of the old locking range; and

in response to the start LBA of the new locking range being less than the end LBA of the old locking range and the end LBA of the new locking range being greater than the start LBA of the old locking range, the controller performs data trimming on any respective non-overlapped portions of the new locking range and the old locking range.

18. The controller of claim 17 , wherein in response to a request of changing another old locking range into another new locking range, the controller determines whether a start LBA of the another new locking range is less than an end LBA of the another old locking range; in response to the start LBA of the another new locking range being less than the end LBA of the another old locking range, the controller determines whether an end LBA of the another new locking range is greater than a start LBA of the another old locking range; and in response to the end LBA of the another new locking range being not greater than the start LBA of the another old locking range, the controller performs data trimming on the another new locking range and the another old locking range, respectively.

19. The controller of claim 18 , wherein in response to a request of changing yet another old locking range into yet another new locking range, the controller determines whether a start LBA of the yet another new locking range is less than an end LBA of the yet another old locking range; and in response to the start LBA of the yet another new locking range being not less than the end LBA of the yet another old locking range, the controller performs data trimming on the yet another new locking range and the yet another old locking range, respectively.

20. The controller of claim 19 , wherein the old locking range and the new locking range have partial locking ranges that are overlapped, the another new locking range and the another old locking range are not overlapped at all, and the yet another new locking range and the yet another old locking range are not overlapped at all.

Priority Claims (1)
TW 108109171 · Mar 18, 2019 · national
Continuity (3)
Continuation 16503591 · Jul 4, 2019
Provisional Application 62731993 · Sep 17, 2018
Related Publication 20210103529A1 · Apr 8, 2021