IP Library Granted Patent US 11,526,435
Granted Patent B2
US 11,526,435 · App. 16/781,688 · Granted Dec 13, 2022

Storage system and method for automatic data phasing

Inventor: Ramanathan Muthiah (Bangalore, IN)
Assignee: Western Digital Technologies, Inc.
G06F12/0253G06F12/10G06F2212/1044
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,526,435
App. No.
16/781,688
Granted
Dec 13, 2022
Kind
B2
Abstract

A storage system and method for automatic data phasing are disclosed. In one embodiment, a storage system is configured to receive, from a host, data to be written in the memory and an indication of an expected lifespan of the data; and determine whether to perform a garbage collection operation on the data based on the expected lifespan of the data. Other embodiments are provided.

Claims (45)

1. A storage system comprising:

a memory; and

a controller configured to:

receive, from a host, a first write command comprising first data to be written in the memory, a first logical address, and an expiration time of the first data;

store the expiration time of the first data in a first entry in a logical-to-physical address map that associates the first logical address with a first physical address in the memory that stores the first data;

receive, from the host, a second write command comprising second data to be written in the memory, a second logical address, and an expiration time of the second data;

store the expiration time of the second data in a second entry in the logical-to-physical address map that associates the second logical address with a second physical address in the memory that stores the second data; and

prior to performing a garbage collection operation:

determine that the first data has expired by determining that a current time is later than the expiration time of the first data and, in response, invalidate the first entry in the logical-to-physical address map while maintaining the first data in the memory, wherein invalidating the first entry in the logical-to-physical address map causes the controller to forgo performing the garbage collection operation on the first data, and

determine that the second data has not expired by determining that the current time is earlier than the expiration time of the second data and, in response, perform the garbage collection operation on the second data.

2. The storage system of claim 1 , wherein the controller is further configured to inform the host that the first data has been invalidated.

3. The storage system of claim 1 , wherein the controller is further configured to forgo performing a garbage collection operation on other data even though the other data has not expired expected.

4. The storage system of claim 1 , wherein the controller is further configured to receive an update to the expiration time of the first data.

5. The storage system of claim 1 , wherein the memory comprises a three-dimensional memory.

6. The storage system of claim 1 , wherein the storage system is configured to be integrated in the host.

7. The storage system of claim 1 , wherein the storage system is configured to be removably connected with the host.

8. The storage system of claim 1 , wherein providing the expiration time of the first data avoids a need of the host to erase the first data.

9. The storage system of claim 1 , wherein the controller is further configured to determine how the first data should be stored based on the expiration time of the first data.

10. The storage system of claim 9 , wherein the controller is further configured to determine how the first data should be stored by choosing a data protection method to store the first data.

11. The storage system of claim 9 , wherein the controller is further configured to determine how the first data should be stored by choosing an endurance parameter to store the first data.

12. The storage system of claim 9 , wherein the controller is further configured to determine how the first data should be stored by choosing a trim parameter to store the first data.

13. The storage system of claim 9 , wherein the controller is further configured to determine how the first data should be stored by choosing a region of the memory to store the first data.

14. A method comprising:

performing the following in a storage system comprising a memory:

receiving, from a host, a first write command comprising first data to be written in the memory, a first logical address and an expiration time of the first data;

storing the expiration time of the first data in a first entry in a logical-to-physical address map that associates the first logical address with a first physical address in the memory that stores the first data;

receiving, from the host, a second write command comprising second data to be written in the memory, a second logical address, and an expiration time of the second data;

storing the expiration time of the second data in a second entry in the logical-to-physical address map that associates the second logical address with a second physical address in the memory that stores the second data; and

prior to performing a garbage collection operation:

determining that the first data has expired by determining that a current time is later than the expiration time of the first data and, in response, invalidating the first entry in the logical-to-physical address map while maintaining the first data in the memory, wherein invalidating the first entry in the logical-to-physical address map causes the controller to forgo performing; the garbage collection operation on the first data, and

determining that the second data has not expired by determining that the current time is earlier than the expiration time of the second data and, in response, performing the garbage collection operation on the second data.

15. The method of claim 14 , further comprising informing the host that the first data has been invalidated.

16. The method of claim 14 , further comprising receiving, from the host, an update to the expiration time of the first data updated lifetime of the data.

17. The method of claim 14 , wherein providing the expiration time of the first data avoids a need of the host to erase the first data.

18. The method of claim 14 , further comprising determining how the first data should be stored based on the expiration time of the first data.

19. A storage system comprising:

a memory;

means for receiving, from a host, a first write command comprising first data to be written in the memory, a first logical address, and an expiration time of the first data;

means for storing the expiration time of the first data in a first entry in a logical-to-physical address map that associates the first logical address with a first physical address in the memory that stores the first data;

means for receiving, from the host, a second write command comprising second data to be written in the memory, a second logical address, and an expiration time of the second data;

means for storing the expiration time of the second data in a second entry in the logical-to-physical address map that associates the second logical address with a second physical address in the memory that stores the second data; and

means for performing the following prior to performing a garbage collection operation:

determining that the first data has expired by determining that a current time is later than the expiration time of the first data and, in response, invalidating the first entry in the logical-to-physical address map while maintaining the first data in the memory, wherein invalidating the first entry in the logical-to-physical address map causes the controller to forgo performing the garbage collection operation on the first data, and

determining that the second data has not expired by determining that the current time is earlier than the expiration time of the second data and, in response, performing the garbage collection operation on the second data.

20. The storage system of claim 19 , wherein providing the expiration time of the first data avoids a need of a host to erase the first data.

Assignments (10)
PARTIAL RELEASE OF SECURITY INTERESTS Recorded Apr 25, 2025
From: JPMORGAN CHASE BANK, N.A., AS AGENT
To: SANDISK TECHNOLOGIES, INC.
Reel/Frame 071382/0001 →
SECURITY AGREEMENT Recorded Apr 25, 2025
From: SANDISK TECHNOLOGIES, INC.
To: JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT
Reel/Frame 071050/0001 →
PATENT COLLATERAL AGREEMENT Recorded Aug 23, 2024
From: SANDISK TECHNOLOGIES, INC.
To: JPMORGAN CHASE BANK, N.A., AS THE AGENT
Reel/Frame 068762/0494 →
CHANGE OF NAME Recorded Jun 27, 2024
From: SANDISK TECHNOLOGIES, INC.
To: SANDISK TECHNOLOGIES, INC.
Reel/Frame 067982/0032 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded May 29, 2024
From: WESTERN DIGITAL TECHNOLOGIES, INC.
To: SANDISK TECHNOLOGIES, INC.
Reel/Frame 067567/0682 →
PATENT COLLATERAL AGREEMENT - DDTL LOAN AGREEMENT Recorded Aug 21, 2023
From: WESTERN DIGITAL TECHNOLOGIES, INC.
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 067045/0156 →
PATENT COLLATERAL AGREEMENT - A&R LOAN AGREEMENT Recorded Aug 21, 2023
From: WESTERN DIGITAL TECHNOLOGIES, INC.
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 064715/0001 →
RELEASE OF SECURITY INTEREST AT REEL 053482 FRAME 0453 Recorded Feb 8, 2022
From: JPMORGAN CHASE BANK, N.A.
To: WESTERN DIGITAL TECHNOLOGIES, INC.
Reel/Frame 058966/0279 →
SECURITY INTEREST Recorded May 14, 2020
From: WESTERN DIGITAL TECHNOLOGIES, INC.
To: JPMORGAN CHASE BANK, N.A., AS AGENT
Reel/Frame 053482/0453 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 4, 2020
From: MUTHIAH, RAMANATHAN
To: WESTERN DIGITAL TECHNOLOGIES, INC.
Reel/Frame 051716/0812 →
Continuity (1)
Related Publication 20210240612A1 · Aug 5, 2021