DETAILED ACTION
Notice of Pre-AIA or AIA Status
The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA .
Response to Amendment
With respect to Applicant’s amendment to Claim 17 in regards to 37 CFR 1.75, objection with respect to the same has been withdrawn.
Terminal Disclaimer
The terminal disclaimer filed on 4/9/2026 disclaiming the terminal portion of any patent granted on this application which would extend beyond the expiration date of US Patent No. 12,159,059 has been reviewed and is accepted. The terminal disclaimer has been recorded and the double patenting rejection has been withdrawn.
Claim Rejections - 35 USC § 102
In the event the determination of the status of the application as subject to AIA 35 U.S.C. 102 and 103 (or as subject to pre-AIA 35 U.S.C. 102 and 103) is incorrect, any correction of the statutory basis (i.e., changing from AIA to pre-AIA ) for the rejection will not be considered a new ground of rejection if the prior art relied upon, and the rationale supporting the rejection, would be the same under either status.
The following is a quotation of the appropriate paragraphs of 35 U.S.C. 102 that form the basis for the rejections under this section made in this Office action:
A person shall be entitled to a patent unless –
(a)(1) the claimed invention was patented, described in a printed publication, or in public use, on sale, or otherwise available to the public before the effective filing date of the claimed invention.
Claims 1-6, 8, 10-15 and 17-21 are rejected under 35 U.S.C. 102(a)(1) as being anticipated by Reina (US PGPUB 2020/0202938).
With regard to Claim 2, Reina teaches a memory system, comprising:
one or more memory devices (Fig. 1: Memory Units 120); and
processing circuitry coupled with the one or more memory devices and configured to cause the memory system to (Fig. 1: Controller 106):
receive an indication of a count of program/erase cycles associated with an address of the memory system; determine whether the count of program/erase cycles associated with the address satisfies a threshold; and adjust a duration for performing a programming operation on the address based at least in part on determining whether the count of program/erase cycles satisfies the threshold ([0010] “The memory device... can decrease the voltage step size when the device conditions are more likely to cause errors (e.g., .... when there are above a threshold number of program/erase cycles),” wherein the “number of program/erase cycles” of the memory device are “the count of program/erase cycles associated with the address” since the address is within the memory device. [0043] “At block 310, a reduced voltage step size can be selected. The reduced voltage step size, when in strenuous conditions, causes smaller iterations of voltage to be applied... The standard voltage step size, when not in strenuous conditions, allows for fewer iterations of voltage to be applied, reducing the time need to perform the program operation,” wherein the selection of a “reduced voltage step size” increases the duration for performing the programming operation.); and
perform the programming operation using the adjusted duration ([0045] “At block 312, the program operation can be performed using the selected voltage step size, as described above in relation to FIG. 2.”).
With regard to Claim 3, Reina teaches the memory system of claim 2, wherein the processing circuitry is configured to cause the memory system to:
adjust a distribution of a states stored in a memory cell based at least in part on determining that the count of program/erase cycles satisfies the threshold, wherein performing the programming operation is based at least in part on adjusting the distribution of the states ([0023] “The memory device 102 can use processing levels 154 for storing or accessing data. The processing levels 154 can include thresholds or operating levels for voltage or current. The processing levels 154 can include a threshold voltage 156, a read level voltage 158, a programming level voltage 160, one or more programming voltage steps 162A-N, or any combination thereof.” [0037] “The memory system 100 can dynamically calculate or adjust the processing levels 154 based on feedback information... The memory system 100 can dynamically adjust the distribution targets based on feedback data using a target calibration mechanism 178 to adjust for the shift in the measured values,” wherein the “feedback” information is associated with the “threshold number of program/erase cycles” as discussed above.).
With regard to Claim 4, Reina teaches the memory system of claim 3, wherein the processing circuitry is configured to cause the memory system to:
determine whether to improve a reliability of data stored at the address of the memory system based at least in part on determining that the count of program/erase cycles satisfies the threshold, wherein adjusting the distribution of the states stored in the memory cell is based at least in part on determining to improve the reliability of the data stored at the address ([0041] “At block 306, method 300 can determine whether the identified device conditions are strenuous device conditions... strenuous device conditions can be a number of program/erase cycles being above a threshold.” [0043] “If there are strenuous device conditions, method 300 can proceed to block 310... At block 310, a reduced voltage step size can be selected. The reduced voltage step size, when in strenuous conditions, causes smaller iterations of voltage to be applied, reducing the likelihood that memory cells will be over-charged,” wherein “reducing the likelihood that memory cells will be over-charged” serves to “improve the reliability of data”.).
With regard to Claim 5, Reina teaches the memory system of claim 2, wherein the processing circuitry is configured to cause the memory system to:
adjust a trim parameter for operating the memory system based at least in part on determining whether the count of program/erase cycles satisfies the threshold, the programming operation is performed using the adjusted trim parameter ([0041] “At block 306, method 300 can determine whether the identified device conditions are strenuous device conditions... strenuous device conditions can be a number of program/erase cycles being above a threshold.” [0043] “If there are strenuous device conditions, method 300 can proceed to block 310... At block 310, a reduced voltage step size can be selected,” wherein the “voltage step size” is the “trim parameter”.).
With regard to Claim 6, Reina teaches the memory system of claim 2, wherein the processing circuitry is configured to cause the memory system to:
determine that a quantity of errors associated with the address of the memory system fails satisfies a threshold based at least in part on determining whether the count of program/erase cycles satisfies the threshold, wherein performing the programming operation is based at least in part on determining that the quantity of error fails to satisfy the threshold ([0040] “At block 304, method 300 can determine device conditions for the program operation. Device conditions can comprise various contexts such as... a rate of errors for a block containing the target memory cells.” [0044] “In some cases, trigger conditions can cause the selecting of reduced voltage step sizes. For example, an error rate at which the memory device is over-charging memory cells can be tracked, and when this rate exceeds a threshold it can trigger a reduction in the voltage step size.”).
With regard to Claim 8, Reina teaches the memory system of claim 2, wherein the processing circuitry is configured to cause the memory system to:
adjust a trim parameter to a first value for operating the memory system based at least in part on determining that the count of program/erase cycles satisfies the threshold ([0040] “At block 304, method 300 can determine device conditions for the program operation. Device conditions can comprise various contexts such as... a rate of errors for a block containing the target memory cells.” [0044] “In some cases, trigger conditions can cause the selecting of reduced voltage step sizes. For example, an error rate at which the memory device is over-charging memory cells can be tracked, and when this rate exceeds a threshold it can trigger a reduction in the voltage step size.” Fig. 3: Step 310 - Select reduced voltage step size).; or
adjust the trim parameter to a second value for operating the memory system based at least in part on determining that the count of program/erase cycles fails to satisfy the threshold ([0043] “If there are not strenuous device conditions, method 300 can proceed to block 308... At block 308, a standard voltage step size can be selected.” Fig. 3: Step 308 - Select standard voltage step size).
With regard to Claim 10, Reina teaches the memory system of claim 2, wherein, to receive the indication of the count of program/erase cycles, the processing circuitry is configured to cause the memory system to:
receive, from a host system, a sequence of one or more commands to perform the programming operation on the address ([0009] “The host system can provide data to be stored at the memory sub-system and can request data to be retrieved from the memory sub-system.” [0039] “At block 302, a program operation is initiated to record values in target cells of a memory.”).
With regard to Claims 11-15 and 17, these claims are equivalent in scope to Claims 2-6 and 8 rejected above, merely having a different independent claim type, and as such Claims 11-15 and 17 are respectively rejected under the same grounds and for the same reasons as discussed above with regard to Claims 2-6 and 8.
With further regard to Claim 11, the claim recites additional elements not specifically addressed in the rejection of Claim 2. The Reina reference also anticipates these additional elements of Claim 11, for example, Reina teaches:
A non-transitory computer-readable medium storing code comprising instructions that, when executed by one or more processors of an electronic device, cause the electronic device to [perform operations] ([0049] “Processing device 402 represents one or more general-purpose processing devices such as a microprocessor, a central processing unit, or the like... The processing device 402 is configured to execute instructions 426 for performing the operations and steps discussed herein.” [0050] “The data storage system 418 can include a machine-readable storage medium 424 (also known as a computer-readable medium) on which is stored one or more sets of instructions 426 or software embodying any one or more of the methodologies or functions described herein. The instructions 426 can also reside, completely or at least partially, within the main memory 404 and/or within the processing device 402.”).
With regard to Claims 18-21, these claims are equivalent in scope to Claims 2-5 rejected above, merely having a different independent claim type, and as such Claims 18-21 are respectively rejected under the same grounds and for the same reasons as discussed above with regard to Claims 2-5.
Claim Rejections - 35 USC § 103
In the event the determination of the status of the application as subject to AIA 35 U.S.C. 102 and 103 (or as subject to pre-AIA 35 U.S.C. 102 and 103) is incorrect, any correction of the statutory basis (i.e., changing from AIA to pre-AIA ) for the rejection will not be considered a new ground of rejection if the prior art relied upon, and the rationale supporting the rejection, would be the same under either status.
The following is a quotation of 35 U.S.C. 103 which forms the basis for all obviousness rejections set forth in this Office action:
A patent for a claimed invention may not be obtained, notwithstanding that the claimed invention is not identically disclosed as set forth in section 102, if the differences between the claimed invention and the prior art are such that the claimed invention as a whole would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to which the claimed invention pertains. Patentability shall not be negated by the manner in which the invention was made.
Claims 7 and 16 are rejected under 35 U.S.C. 103 as being unpatentable over Reina as applied to Claims 5 and 12 above, and further in view of Lin et al. (US PGPUB 2021/0342097).
With regard to claim 7, Reina teaches all the limitations of claim 5 as described above. Reina does not teach the write amplification determination as described in claim 7. Lin teaches wherein the processing circuitry is configured to cause the memory system to:
determine that a write amplification associated with the memory system satisfies a threshold based at least in part on determining whether the count of program/erase cycles satisfies the threshold, wherein performing the programming operation is based at least in part on determining that the write amplification satisfies the threshold ([0101] “the life cycle parameters can be one of TeraBytes Written (TBW), Program/Erase count (P/E count).” [0106] “In step S1102, the write command is received from the host system. In step S1104, it is determined whether the life cycle parameter is greater than the preset cycle threshold... If it is determined that the life cycle parameter is greater than the preset cycle threshold (step S1104, the determining result is YES), then in step S1108, it is determined whether the write amplification factor is greater than the preset threshold. If it is determined that the write amplification factor is not greater than the preset threshold (step S1108, the determining result is NO), then the data is written into the first area in step S1110.”).
Therefore, it would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to have modified the system as disclosed by Reina with the write amplification determination as taught by Lin in order “to avoid reduction of the service life of flash memory module” (Lin [0007]).
With regard to Claim 16, this claim is equivalent in scope to Claim 7 rejected above, merely having a different independent claim type, and as such Claim 16 is rejected under the same grounds and for the same reasons as discussed above with regard to Claim 7.
Claim 9 is rejected under 35 U.S.C. 103 as being unpatentable over Reina as applied to Claim 2 above, and further in view of Melik-Martirosian (US PGPUB 2012/0239858; hereinafter “Melik”).
With regard to claim 9, Reina teaches all the limitations of claim 2 as described above. Reina does not teach the management scheme as described in claim 9. Melik teaches wherein the processing circuitry is configured to cause the memory system to:
identify a management scheme for operating the memory system based at least in part on a look-up table and the count of program/erase cycles, wherein performing the programming operation is based at least in part on identifying the management scheme ([0043] “controller 101 may access one or more trigger lookup tables stored on storage medium 102 to determine when a trigger should take place. The one or more lookup tables may provide trigger information based on a number of P/E cycles or range of cycles and/or a duration as previously described. In some aspects, adjustments to parameter values are planned as the drive ages via one or more parameter lookup tables, which may be indexed by cycle and/or timestamp. Once a trigger event is met (for example, ‘BOL’, ‘low cycles’, ‘mid cycles’, ‘EOL’), controller 101 accesses the one or more parameter lookup tables to facilitate adjustment of the ISPP and/or ISPE parameters.”).
Therefore, it would have been obvious before the effective filing date of the claimed invention to a person having ordinary skill in the art to have modified the system as disclosed by Reina with the write management scheme as taught by Melik in order “to achieve a higher number of cycles the device can undergo, thereby improving the reliability and endurance of flash memory, making it suitable for enterprise applications” (Melik [0024]).
Response to Arguments
Applicant’s arguments, see Pages 9-11 of the Remarks filed 4/9/2026, with respect to the rejections under 35 U.S.C. 102/103 have been fully considered but they are not persuasive.
With respect to Applicant’s argument regarding Claims 2, 11 and 18, Pages 9-10 of the Remarks, that Reina does not teach the limitation which recites, “adjust a duration for performing a programming operation on the address based at least in part on determining whether the count of program/erase cycles satisfies the threshold” (emphasis added), the Office respectfully disagrees.
The Office would like to note that the system and method of Reina does decrease the voltage step size for programming when the number of program/erase cycles is above a threshold, wherein the voltage step size directly correlates to the duration of the programming operation; therefore Reina does adjust the programming operation duration based on whether the program/erase cycles satisfies a threshold. In support of this assertion, see the following citations in Reina:
[0010] “A memory device can dynamically calibrate a voltage step size for programming (i.e., charging) memory cells. The memory device can increase the voltage step size to reduce programming time or decrease the voltage step size to reduce errors. The memory device can identify device conditions, such as temperature (e.g., total value or change between programming and read) or amount of use (e.g., a count of program/erase cycles). The memory device can increase the voltage step size when the device conditions are less likely to cause errors (e.g., in a middle temperature range, when program and read temperatures are within a threshold of each other, and/or when there are below a threshold number of program/erase cycles) or can decrease the voltage step size when the device conditions are more likely to cause errors (e.g., in a high or low temperature range, when program and read temperatures are not within a threshold of each other, or when there are above a threshold number of program/erase cycles).” (emphasis added)
[0041] “At block 306, method 300 can determine whether the identified device conditions are strenuous device conditions. In some implementations, strenuous device conditions can be a temperature above a high threshold or below a low threshold. Examples of the high threshold are 85 or 105 degrees Celsius, and examples of the low threshold are 0, −10, or −40 degrees Celsius. In some implementations, strenuous device conditions can be a number of program/erase cycles being above a threshold. Examples of program/erase cycle thresholds are 2,000 or 3,000 cycles.” (emphasis added)
[0043] “If there are strenuous device conditions, method 300 can proceed to block 310. If there are not strenuous device conditions, method 300 can proceed to block 308. At block 310, a reduced voltage step size can be selected. The reduced voltage step size, when in strenuous conditions, causes smaller iterations of voltage to be applied, reducing the likelihood that memory cells will be over-charged. At block 308, a standard voltage step size can be selected. The standard voltage step size, when not in strenuous conditions, allows for fewer iterations of voltage to be applied, reducing the time need to perform the program operation.” (emphasis added)
[0044] “In some implementations, instead of a binary determination for strenuous device conditions, multiple ranges e.g., of temperatures, program/erase cycles, etc., can be defined, with each range mapped to a corresponding voltage step size. Once device conditions are identified at block 304, a corresponding voltage step size can be selected from the mappings. This allows more precise control in striking the balance between programming time and error rates. In some cases, trigger conditions can cause the selecting of reduced voltage step sizes. For example, an error rate at which the memory device is over-charging memory cells can be tracked, and when this rate exceeds a threshold it can trigger a reduction in the voltage step size.” (emphasis added)
As such, in view of at least the above citations, the Office contends that Reina has been shown to teach a system and method which decreases the voltage step size for programming when a number of program/erase cycles is above a threshold, and furthermore that Reina has been shown to disclose that the adjusted voltage step size directly correlates to the programming time. Accordingly, the Office has mapped the adjustment of voltage step size and programming time based on whether a number of program/erase cycles is above threshold of Reina, as applied supra, to the claimed step which recites, “adjust a duration for performing a programming operation on the address based at least in part on determining whether the count of program/erase cycles satisfies the threshold”.
For at least the reasons discussed above, the Office maintains that Reina does teach and anticipate the limitations of Claims 2, 11 and 18.
With respect to the Applicant’s arguments, Pages 10-11 of the Remarks, that the features of the remaining claims are not taught by the cited prior art, the Office respectfully disagrees. These arguments rely upon the arguments as presented in relation to Claims 2, 11 and 18, and as such the Office directs the Applicant to the response above regarding these arguments.
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure is as follows:
Luo et al. (US PGPUB 2021/0149564) discloses techniques to improve memory device reliability in cross-temperature conditions, wherein a memory trim set can be selected from multiple candidate memory trim sets when performing a memory operation (such as a memory write operation) based on a P/E cycle metric.
Ha et al. (US PGPUB 2009/0116283) discloses methods and systems for determining a degradation parameter associated with memory cells and adjusting the memory control signals, wherein the degradation parameter includes the number of program/erase cycles and the adjusted control signals include a program time.
Micheloni et al. (US PGPUB 2016/0064096) discloses a system and method for using programming time to reduce bit errors in a nonvolatile memory system, wherein a programming time can be selected according to a number of program/erase cycles that have been performed.
THIS ACTION IS MADE FINAL. Applicant is reminded of the extension of time policy as set forth in 37 CFR 1.136(a).
A shortened statutory period for reply to this final action is set to expire THREE MONTHS from the mailing date of this action. In the event a first reply is filed within TWO MONTHS of the mailing date of this final action and the advisory action is not mailed until after the end of the THREE-MONTH shortened statutory period, then the shortened statutory period will expire on the date the advisory action is mailed, and any nonprovisional extension fee (37 CFR 1.17(a)) pursuant to 37 CFR 1.136(a) will be calculated from the mailing date of the advisory action. In no event, however, will the statutory period for reply expire later than SIX MONTHS from the mailing date of this final action.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to NICHOLAS J SIMONETTI whose telephone number is (571)270-7702. The examiner can normally be reached Monday-Thursday 10AM-6PM EST.
Examiner interviews are available via telephone, in-person, and video conferencing using a USPTO supplied web-based collaboration tool. To schedule an interview, applicant is encouraged to use the USPTO Automated Interview Request (AIR) at http://www.uspto.gov/interviewpractice.
If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Arpan Savla can be reached at (571) 272-1077. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300.
Information regarding the status of published or unpublished applications may be obtained from Patent Center. Unpublished application information in Patent Center is available to registered users. To file and manage patent submissions in Patent Center, visit: https://patentcenter.uspto.gov. Visit https://www.uspto.gov/patents/apply/patent-center for more information about Patent Center and https://www.uspto.gov/patents/docx for information about filing in DOCX format. For additional questions, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000.
/NICHOLAS J SIMONETTI/ Primary Examiner, Art Unit 2137 June 3, 2026