Prosecution Insights
Last updated: November 20, 2026
Application No. 18/984,740

METHODS AND SYSTEMS FOR AUTHENTICATION WITHIN A STORAGE DEVICE

Final Rejection §102§103
Filed
Dec 17, 2024
Examiner
AMEVIGBE, KOMI NOUNYANOU
Art Unit
2493
Tech Center
2400 — Computer Networks
Assignee
SK hynix Inc.
OA Round
2 (Final)
0%
Grant Probability
At Risk
3-4
OA Rounds
2y 0m
Est. Remaining
0%
With Interview

Examiner Intelligence

Grants only 0% of cases
0%
Career Allowance Rate
0 granted / 2 resolved
-58.0% vs TC avg
Minimal +0% lift
Without
With
+0.0%
Interview Lift
resolved cases with interview
Typical timeline
3y 11m
Avg Prosecution
20 currently pending
Career history
24
Total Applications
across all art units

Statute-Specific Performance

§103
81.0%
+41.0% vs TC avg
§102
9.5%
-30.5% vs TC avg
§112
9.5%
-30.5% vs TC avg
Black line = Tech Center average estimate • Based on career data from 2 resolved cases

Office Action

§102 §103
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 The amendment filed 07/30/2026 has been fully considered and entered into record. Claims 1-22 remain pending in the application. Claims 1, 10 and 19 have been amended. Claims 8 and 17 have been canceled and claims 21 and 22 have been added. Response to Arguments Applicant's arguments with respect to claims 1, 2, 3-10, 11 and 12-20 have been considered but are moot because the present rejection constitutes a new ground of rejection. The present rejection no longer relies only on Sela, Flynn and Feghali for the disputed limitations, but instead relies on LEE, Sela, Flynn and Campagna for teachings set forth in the rejection. Accordingly, Applicant’s arguments directed to the prior combination are not persuasive. Claim Rejections - 35 USC § 102 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,3, 6, 7, 9, 10, 12, 15, 16, 18, 19, 22 are rejected under 35 U.S.C. 102(a)(1) as being anticipated by LEE et al (US 20220091760 A1) [hereinafter "LEE"]. As per claim 1, LEE discloses a method of authentication,(LEE, claim 5]” The storage device of claim 4, wherein the memory controller comprises: an authentication manager configured to perform the authentication and output a result of the authentication”) comprising: at a memory device that comprises non-volatile memory(LEE, [0003]” The memory device may include characterized as a volatile memory device or a nonvolatile memory device depending on its capability to hold stored data in the absence of power.”) and control circuitry(LEE, claim 5]” The storage device of claim 4, wherein the memory controller comprises ….): receiving, from a host, a data request that includes a set of data(LEE, [0177],[0182]” The authenticated data write request may be provided by transmitting, by the host 400, the RPMB message requesting to store data in the RPMB 110a and the data to be stored to the storage device 50” and “the RPMB message corresponding to the authenticated data write request. The RPMB message transferred in operation S805 may include a stuff byte, authenticated data, and metadata.”) and a reference digest, (LEE, [0009]” the host MAC”) the reference digest being generated by the host(LEE, [claim 40]” a host MAC calculator configured to calculate the host MAC using the host metadata”) for the set of data; (LEE, [0194]” The metadata may include the data to be stored in the RPMB 110a, ”). generating, at the memory device, an authentication digest for the set of data included in the data request; (LEE, claim 38]” a device MAC calculator configured to generate a device MAC using the host metadata and the device authentication key; ”). determining whether the reference digest matches the authentication digest; (LEE, claim 38],[0284]” a MAC comparator configured to generate the result of the authentication according to whether the host MAC and the device MAC match” and “The MAC comparator 2730 may compare whether the MAC received from the PIU parser 2710 and the MAC received from the MAC calculator 2720 match, and may output an authentication result according to a comparison result. ”). in accordance with a determination that the reference digest matches the authentication digest, performing an operation corresponding to the data request in the non- volatile memory; (LEE, claim 8]” the access controller controls the nonvolatile memory device to store the write data in the RPMB, when the host MAC and the device MAC match ”).and in accordance with a determination that the reference digest does not match the authentication digest, indicating that the data request is not to be performed. (LEE, [0170]” When the authentication is failed, the access controller 212 may not store the data requested to be stored in the RPMB 110a in the RPMB data area. The access controller 212 may maintain the value of the write counter 112 and store information indicating that the authentication is failed in the result register 113.”). As per claim 3, LEE discloses the method of claim 1. LEE further discloses wherein: the control circuitry comprises an authentication controller and an access controller; (LEE, claim 5]” The storage device of claim 4, wherein the memory controller comprises: an authentication manager configured to perform the authentication…and an access controller configured to control the RPMB based on the result of the authentication, and the host RPMB message includes a host message authentication code (MAC) and host metadata.”) and the authentication controller determines whether the reference digest matches the authentication digest. (LEE, claim 6]” the authentication manager comprises: a device MAC calculator configured to generate a device MAC using the metadata and the authentication key; and a MAC comparator configured to generate the result of the authentication according to whether the host MAC and the device MAC match.”). As per claim 6, LEE discloses the method of claim 1. LEE further discloses wherein performing the data request comprises writing a subset of the set of data to the non-volatile memory. ([LEE, [0194]]” The metadata may include the data to be stored in the RPMB 110a, the nonce, the current write count value, the address corresponding to the data, the number of blocks of data (here one block is 256B), and the request message type indicating the RPMB message is the authenticated data write request. In an embodiment, a field corresponding to the nonce may be “0.””). As per claim 7, LEE discloses the method of claim 1. LEE further discloses wherein performing the data request comprises reading from the non-volatile memory. ([LEE, (claim 13)]” a memory controller configured to receive a command protocol information unit (PIU) which includes a host RPMB message from a host and to read data stored in the RPMB, ”). As per claim 9, LEE discloses the method of claim 1. LEE further discloses wherein indicating that the data request is not to be performed comprises generating a failure notification. ([LEE, [0170]”The access controller 212 may maintain the value of the write counter 112 and store information indicating that the authentication is failed in the result register 113” and “ The result read response may include a response in which the storage device 50 transfers the RPMB message providing the value of the result register to the host 400” ). As per claim 10, LEE discloses a memory device, comprising: non-volatile memory; (LEE, [0003]” The memory device may include characterized as a volatile memory device or a nonvolatile memory device depending on its capability to hold stored data in the absence of power.”) and control circuitry(LEE, claim 5]” The storage device of claim 4, wherein the memory controller comprises ….) configured to: receiving, from a host, a data request that includes a set of data(LEE, [0177],[0182]” The authenticated data write request may be provided by transmitting, by the host 400, the RPMB message requesting to store data in the RPMB 110a and the data to be stored to the storage device 50” and “the RPMB message corresponding to the authenticated data write request. The RPMB message transferred in operation S805 may include a stuff byte, authenticated data, and metadata.”) and a reference digest, (LEE, [0009]” the host MAC”) the reference digest being generated by the host(LEE, [claim 40]” a host MAC calculator configured to calculate the host MAC using the host metadata”) for the set of data; (LEE, [0194]” The metadata may include the data to be stored in the RPMB 110a, ”). generating, at the memory device, an authentication digest for the set of data included in the data request; (LEE, claim 38]” a device MAC calculator configured to generate a device MAC using the host metadata and the device authentication key; ”). determining whether the reference digest matches the authentication digest; (LEE, claim 38],[0284]” a MAC comparator configured to generate the result of the authentication according to whether the host MAC and the device MAC match” and “The MAC comparator 2730 may compare whether the MAC received from the PIU parser 2710 and the MAC received from the MAC calculator 2720 match, and may output an authentication result according to a comparison result. ”). in accordance with a determination that the reference digest matches the authentication digest, performing an operation corresponding to the data request in the non- volatile memory; (LEE, claim 8]” the access controller controls the nonvolatile memory device to store the write data in the RPMB, when the host MAC and the device MAC match ”).and in accordance with a determination that the reference digest does not match the authentication digest, indicating that the data request is not to be performed. (LEE, [0170]” When the authentication is failed, the access controller 212 may not store the data requested to be stored in the RPMB 110a in the RPMB data area. The access controller 212 may maintain the value of the write counter 112 and store information indicating that the authentication is failed in the result register 113.”). As per claim 12, the substance of the claimed invention is identical or substantially similar to that of claim 3. Accordingly, this claim is rejected under the same rationale. As per claim 15, the substance of the claimed invention is identical or substantially similar to that of claim 6. Accordingly, this claim is rejected under the same rationale. As per claim 16, the substance of the claimed invention is identical or substantially similar to that of claim 7. Accordingly, this claim is rejected under the same rationale. As per claim 18, the substance of the claimed invention is identical or substantially similar to that of claim 9. Accordingly, this claim is rejected under the same rationale. As per claim 19, LEE discloses a non-transitory computer-readable storage medium storing instructions, which when executed by a memory device(LEE, [0003]” The memory device may include characterized as a volatile memory device or a nonvolatile memory device depending on its capability to hold stored data in the absence of power.”) that comprises non-volatile memory, cause the memory device to: receiving, from a host, a data request that includes a set of data(LEE, [0177],[0182]” The authenticated data write request may be provided by transmitting, by the host 400, the RPMB message requesting to store data in the RPMB 110a and the data to be stored to the storage device 50” and “the RPMB message corresponding to the authenticated data write request. The RPMB message transferred in operation S805 may include a stuff byte, authenticated data, and metadata.”) and a reference digest, (LEE, [0009]” the host MAC”) the reference digest being generated by the host(LEE, [claim 40]” a host MAC calculator configured to calculate the host MAC using the host metadata”) for the set of data; (LEE, [0194]” The metadata may include the data to be stored in the RPMB 110a, ”). generating, at the memory device, an authentication digest for the set of data included in the data request; (LEE, claim 38]” a device MAC calculator configured to generate a device MAC using the host metadata and the device authentication key; ”). determining whether the reference digest matches the authentication digest; (LEE, claim 38],[0284]” a MAC comparator configured to generate the result of the authentication according to whether the host MAC and the device MAC match” and “The MAC comparator 2730 may compare whether the MAC received from the PIU parser 2710 and the MAC received from the MAC calculator 2720 match, and may output an authentication result according to a comparison result. ”). in accordance with a determination that the reference digest matches the authentication digest, performing an operation corresponding to the data request in the non- volatile memory; (LEE, claim 8]” the access controller controls the nonvolatile memory device to store the write data in the RPMB, when the host MAC and the device MAC match ”).and in accordance with a determination that the reference digest does not match the authentication digest, indicating that the data request is not to be performed. (LEE, [0170]” When the authentication is failed, the access controller 212 may not store the data requested to be stored in the RPMB 110a in the RPMB data area. The access controller 212 may maintain the value of the write counter 112 and store information indicating that the authentication is failed in the result register 113.”). As per claim 22, the substance of the claimed invention is identical or substantially similar to that of claim 3. Accordingly, this claim is rejected under the same rationale. Claim Rejections - 35 USC § 103 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. The factual inquiries for establishing a background for determining obviousness under 35 U.S.C. 103 are summarized as follows: 1. Determining the scope and contents of the prior art. 2. Ascertaining the differences between the prior art and the claims at issue. 3. Resolving the level of ordinary skill in the pertinent art. Considering objective evidence present in the application indicating obviousness or nonobviousness. Claims 2, 11 and 21 are rejected under 35 U.S.C. §103 as being unpatentable over LEE et al.( US 20220091760 A1) [hereinafter “LEE”] as applied to claim 1 and 10 in view of Campagna et al (US 20170171174 A1) [hereinafter “Campagna”]. As per claim 2, LEE discloses the method of claim 1. LEE fails to disclose wherein the data request further includes a key identifier, and wherein the authentication digest is generated using a key identified by the key identifier. However, Campagna in the same field of endeavor discloses wherein the data request further includes a key identifier, ([Campagna, [0049])” The client may provide a key identifier to the cryptography service as part of the request. ”) and wherein the authentication digest is generated [using a key identified by the key identifier]([ Campagna, [0058])” The cryptography service 510 may generate a digital signature or MAC tag over the message using a cryptographic key. Client A may provide, to the cryptography service, as part of the request to Authenticate, a unique identifier corresponding to the cryptography key to be used… for authenticating the message”). Therefore, it would have been obvious before the effective filing date of the claimed invention for one of ordinary skill in the art to modify LEE to include wherein the data request further includes a key identifier, and wherein the authentication digest is generated using a key identified by the key identifier as suggested by Campagna. One of ordinary skill in the art would have been motivated to do so because incorporating Campagna’s key identifier into LEE’s already disclosed authentication digest framework would have predictably enabled authentication digest generation using an identified key, thereby improving key management, supporting selection among multiple keys, and enhancing secure processing of memory requests. As per claim 11, the substance of the claimed invention is identical or substantially similar to that of claim 2. Accordingly, this claim is rejected under the same rationale. As per claim 21, the substance of the claimed invention is identical or substantially similar to that of claim 2. Accordingly, this claim is rejected under the same rationale. Claims 4, 13 and 20 are rejected under 35 U.S.C. §103 as being unpatentable over LEE et al.( US 20220091760 A1) [hereinafter “LEE”] in view of Sela et al. (US 10521617 B2) [hereinafter “Sela”]. As per claim 4, LEE discloses the method of claim 3. LEE further discloses the method comprising, while the authentication controller determines whether the reference digest matches the authentication digest, (LEE, claim 6]” the authentication manager comprises: a device MAC calculator configured to generate a device MAC using the metadata and the authentication key; and a MAC comparator configured to generate the result of the authentication according to whether the host MAC and the device MAC match.”). LEE fails to disclose performing one or more checks on the set of data using the access controller. However, Sela in the same field of endeavor discloses [performing one or more checks on the set of data]([Sela, (col.12 ln50-57), (col.12 ln55-65)]” the step 504 may include performing error correction on the data. For example, ECC engine 224 may be used to decode and error correct the data read from the non-volatile memory 24” and “Step 506 includes the non-volatile memory device 20 verifying the accessed data….include verifying the integrity and/or authenticity of the accessed data” )[ using the access controller]([Sela, (col.11 ln50-55)]” The data transfer controller 406 may restrict access depending on whether the computed data digest matched the expected data digest. “). Therefore, it would have been obvious before the effective filing date of the claimed invention for one of ordinary skill in the art to modify LEE to include performing one or more checks on the set of data using the access controller as suggested by Sela. One of ordinary skill in the art would have been motivated to do so because incorporating Sela’s performing the access-controller checks while the authentication determination is being performed would improve processing efficiency by allowing the checks to occur in parallel, thereby reducing latency before the requested memory operation is authorized. As per claim 13, the substance of the claimed invention is identical or substantially similar to that of claim 4. Accordingly, this claim is rejected under the same rationale. As per claim 20, the substance of the claimed invention is identical or substantially similar to that of claim 4. Accordingly, this claim is rejected under the same rationale. Claims 5 and 14 are rejected under 35 U.S.C. §103 as being unpatentable over LEE et al.( US 20220091760 A1) [hereinafter “LEE”] in view of Sela et al. (US 10521617 B2) [hereinafter “Sela”] as applied to claim 4, and in view of Flynn et al (US 20160140004 A1) [hereinafter “Flynn”]. As per claim 5, the combination of LEE and Sela discloses the method of claim 4. Sela further discloses wherein the set of data comprises an address, ([Sela, (col.4 ln37-45)]” the host may specify a logical address. The memory controller 22 may translate the logical address to a physical address within the non-volatile memory 24,”). Sela fails to discloses and wherein the one or more checks comprise checking whether the address is valid. However, Flynn in the same endeavor discloses wherein the one or more checks comprise checking whether the address is valid. ([Flynn, [0183], [0252]]” The depacketizer 324 may validate the packet headers by checking packet identifiers, data length, data location, etc. within the headers. In one embodiment, the header includes a hash code that can be used to validate that the packet delivered to the read data pipeline 303 is the requested packet.” and “The logical-to-physical map may indicate storage locations comprising valid data (e.g., storage locations comprising valid data). ”). Therefore, it would have been obvious before the effective filing date of the claimed invention for one of ordinary skill in the art to modify LEE to include performing one or more checks on the set of data using the access controller as suggested by Sela to further include wherein the one or more checks comprise checking whether the address is valid as suggested by Flynn. One of ordinary skill in the art would have been motivated to do so because incorporating Flynn’s address-validation into LEE’s memory-access scheme would have helped ensure that a requested storage location is performed, thereby reducing erroneous accesses and improving reliability. As per claim 14, the substance of the claimed invention is identical or substantially similar to that of claim 5. Accordingly, this claim is rejected under the same rationale. Conclusion The prior art made of record and not relied upon is considered pertinent to applicant's disclosure. JANG et al, (US 20210255802 A1) discloses “STORAGE DEVICE AND METHOD OF OPERATING THE SAME “. LEE et al, (US 20210281414 A1) discloses “COMPUTING SYSTEM AND OPERATING METHOD THEREOF” Applicant's amendment necessitated the new ground(s) of rejection presented in this Office action. Accordingly, THIS ACTION IS MADE FINAL. See MPEP § 706.07(a). 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 Komi N. AMEVIGBE whose telephone number is (571)272-3381. The examiner can normally be reached Monday-Friday 2pm-10pm. 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, Carl Colin can be reached at (571) 272-3862. 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. /K.N.A./Examiner, Art Unit 2493 /CARL G COLIN/Supervisory Patent Examiner, Art Unit 2493
Read full office action

Prosecution Timeline

Dec 17, 2024
Application Filed
Apr 30, 2026
Non-Final Rejection mailed — §102, §103
Jul 20, 2026
Interview Requested
Jul 28, 2026
Examiner Interview (Telephonic)
Jul 28, 2026
Examiner Interview Summary
Jul 30, 2026
Response Filed
Oct 22, 2026
Final Rejection mailed — §102, §103 (current)

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12634308
METHOD FOR DETECTING NETWORK ATTACK BASED ON KERNEL OPERATING CHARACTERISTICS OF SOFTWARE SWITCH
1y 8m to grant Granted May 19, 2026
Study what changed to get past this examiner. Based on 1 most recent grants.

Strategy Recommendation AI-generated — please review before filing

Get a prosecution strategy drawn from examiner precedents, rejection analysis, and claim mapping.
Typically takes 5-10 seconds — AI-generated, attorney review required before filing

Prosecution Projections

3-4
Expected OA Rounds
0%
Grant Probability
0%
With Interview (+0.0%)
3y 11m (~2y 0m remaining)
Median Time to Grant
Moderate
PTA Risk
Based on 2 resolved cases by this examiner. Grant probability derived from career allowance rate.

Sign in with your work email

Enter your email to receive a magic link. No password needed.

Personal email addresses (Gmail, Yahoo, etc.) are not accepted.

Free tier: 3 strategy analyses per month