Prosecution Insights
Last updated: August 17, 2026
Application No. 19/145,165

DATA SECURITY FOR REPLAY PROTECTED MEMORY BLOCK (RPMP)

Non-Final OA §102§103
Filed
Jul 01, 2025
Priority
Feb 15, 2025 — nonprovisional of PCTCN2023076088
Examiner
CHRISTENSEN, SCOTT B
Art Unit
2444
Tech Center
2400 — Computer Networks
Assignee
Qualcomm Incorporated
OA Round
1 (Non-Final)
78%
Grant Probability
Favorable
1-2
OA Rounds
2y 3m
Est. Remaining
99%
With Interview

Examiner Intelligence

Grants 78% — above average
78%
Career Allowance Rate
782 granted / 1004 resolved
+19.9% vs TC avg
Strong +33% interview lift
Without
With
+32.8%
Interview Lift
resolved cases with interview
Typical timeline
3y 4m
Avg Prosecution
29 currently pending
Career history
1032
Total Applications
across all art units

Statute-Specific Performance

§101
10.7%
-29.3% vs TC avg
§103
52.7%
+12.7% vs TC avg
§102
13.0%
-27.0% vs TC avg
§112
12.6%
-27.4% vs TC avg
Black line = Tech Center average estimate • Based on career data from 1004 resolved cases

Office Action

§102 §103
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 . 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. Claim(s) 1-7, 11-17, and 21-22 is/are rejected under 35 U.S.C. 102a1 as being anticipated by US 2022/0091757 (Lee). With regard to claim 1, Lee discloses an apparatus, comprising: a memory controller: coupled to a memory module through a first channel and configured to access data stored in the memory module through the first channel; and coupled to a host device through a first interface and configured to communicate with the host device over the first interface (Lee: Figure 1), the memory controller configured to perform operations comprising: receiving a read request for requested data stored in a replay protected memory block (RPMB) portion of the memory module, wherein the read request comprises first information corresponding to the RPMB portion and a first message authentication code (MAC) determined by the host device based on at least a portion of the first information (Lee: Paragraphs [0010], [0048], and Figure 7); determining a second message authentication code (MAC) based on second information stored in the memory module and the first information (Lee: Paragraph [0223]); determining whether the read request is valid based on comparing the first MAC with the second MAC (Lee: Paragraph [0048]); and transmitting the requested data to the host device through the first interface based on the determining whether the read request is valid (Lee: Paragraph [0048]). With regard to claim 2, Lee discloses that the first information comprises an address, a nonce, a block count, and a write counter (Lee: Figure 7). With regard to claim 3, Lee discloses wherein the first MAC is based on a first authentication key stored on the host device, and wherein determining the second MAC is based on second information comprising a second authentication key stored by the memory controller (Lee: Paragraph [0048]. Both the host and the data storage device (at least under control of the memory controller) store the authentication key.). With regard to claim 4, Lee discloses wherein the first information comprises at least one of an address, a nonce, a block count, and a write counter (Lee: Figure 7). With regard to claim 5, Lee discloses, wherein the memory controller is further configured to perform operations comprising: determining whether an address and a block count of the first information corresponding to the RPMB portion in the read request corresponds to a valid region for the RPMB portion, wherein determining whether the read request is valid is based on determining the address and the block count corresponds to a valid region of the memory module for the RPMB portion (Lee: Paragraphs [0141], [0193], and [0215]. The read operation utilizes several pieces of information, including the block count and address, where the read request would clearly only be able to be performed if this information indicates a valid region of the memory module for the RPMB portion, with a successful access resulting from a determination that the information indicates a valid region to provide the read information.). With regard to claim 6, Lee discloses wherein the memory controller is further configured to perform operations comprising: transmitting an authentication failure response to the host device based on the determining whether the read request is valid (Lee: Paragraph [0128]). With regard to claim 7, Lee discloses, wherein the memory controller is further configured to perform operations comprising: not transmitting the requested data to the host device until after determining whether the read request is valid (Lee: Paragraphs [0128], [0141], [0193], and [0215]. Lee discloses that a request may fail, where one of ordinary skill in the art would have recognized that an invalid read request would result in the requested information not being transmitted, with Lee instead providing failure information.). With regard to claim 10, Lee discloses wherein determining the second message authentication code comprises determining a HMAC SHA-256 value based on a first address, a nonce, a block count, and a write counter in the first information and based on an authentication key stored by the memory controller (Lee: Paragraphs [0048], [0212], [0210], and [0215]). With regard to claims 11-17 and 21-22, the instant claims are directed towards subject matter found within claims 1-7, and are rejected for similar reasons. 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. Claim(s) 8, 18, and 23 is/are rejected under 35 U.S.C. 103 as being unpatentable over Lee. With regard to claim 8, Lee fails to disclose, but knowledge possessed by one of ordinary skill in the art at the time of filing teaches wherein the requested data comprises at least one of a user identifier, a password, a digital rights management (DRM) key, a file system key, or a rollback version of a computer program product (More specifically, RPMB was known to store critical security and integrity data using the enhanced protection provided by RPMB, where Official Notice is taken that the storage of each of the listed items (where the instant claim only requires one of the listed items to teach the instant claim, as a whole), with the subsequent reading utilizing a read request, was known to one of ordinary skill in the art at the time of filing.). Accordingly, it would have been obvious to one of ordinary skill in the art to store at least one of a user identifier, a password, a digital rights management (DRM) key, a file system key, or a rollback version of a computer program product in the RPMB of Lee to provide the enhanced protection of RPMB for these different data items according to the wishes of the users. As a note, the functionality of the instant claim does not appear to be impacted by the specific type of requested data, where this would appear to amount to the intended use of the RPMB, with the RPMB of Lee being fully capable of storing any type data (including at least these listed types of data) desired by the users of the system. With regard to claims 18 and 23, the instant claims are similar to claim 8, and are rejected for similar reasons. Conclusion Any inquiry concerning this communication or earlier communications from the examiner should be directed to SCOTT B CHRISTENSEN whose telephone number is (571)270-1144. The examiner can normally be reached Monday through Friday, 6AM to 2PM. 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, John Follansbee can be reached at (571) 272-3964. 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. SCOTT B. CHRISTENSEN Examiner Art Unit 2444 /SCOTT B CHRISTENSEN/Primary Examiner, Art Unit 2444
Read full office action

Prosecution Timeline

Jul 01, 2025
Application Filed
Aug 05, 2026
Non-Final Rejection mailed — §102, §103 (current)

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12705395
SYSTEMS AND METHODS FOR APPLYING DATA ANONYMIZATION SCHEMES BASED ON VERSIONS OF A SOFTWARE
1y 10m to grant Granted Aug 11, 2026
Patent 12665822
USER EQUIPMENT HOSTING FOR CUSTOMIZABLE 5G SERVICES
2y 9m to grant Granted Jun 23, 2026
Patent 12665808
STORAGE DEVICE SWAP IN A MULTIPLE COMPUTING CLUSTER ENVIRONMENT USING CROSS SYSTEM COMMUNICATION
2y 6m to grant Granted Jun 23, 2026
Patent 12652280
METHOD AND SYSTEM FOR IDENTITY AUTHENTICATION
3y 7m to grant Granted Jun 09, 2026
Patent 12626144
DATA PROCESSING METHOD, FEDERATED LEARNING TRAINING METHOD, AND RELATED APPARATUS AND DEVICE
3y 5m to grant Granted May 12, 2026
Study what changed to get past this examiner. Based on 5 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

1-2
Expected OA Rounds
78%
Grant Probability
99%
With Interview (+32.8%)
3y 4m (~2y 3m remaining)
Median Time to Grant
Low
PTA Risk
Based on 1004 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