Prosecution Insights
Last updated: April 19, 2026
Application No. 18/498,838

SCHEMA-BASED OBJECT PROCESSING

Non-Final OA §103
Filed
Oct 31, 2023
Examiner
ALMANI, MOHSEN
Art Unit
2159
Tech Center
2100 — Computer Architecture & Software
Assignee
Capital One Services LLC
OA Round
3 (Non-Final)
50%
Grant Probability
Moderate
3-4
OA Rounds
4y 0m
To Grant
72%
With Interview

Examiner Intelligence

Grants 50% of resolved cases
50%
Career Allow Rate
189 granted / 374 resolved
-4.5% vs TC avg
Strong +21% interview lift
Without
With
+21.3%
Interview Lift
resolved cases with interview
Typical timeline
4y 0m
Avg Prosecution
24 currently pending
Career history
398
Total Applications
across all art units

Statute-Specific Performance

§101
12.4%
-27.6% vs TC avg
§103
49.4%
+9.4% vs TC avg
§102
21.5%
-18.5% vs TC avg
§112
10.0%
-30.0% vs TC avg
Black line = Tech Center average estimate • Based on career data from 374 resolved cases

Office Action

§103
Continued Examination Under 37 CFR 1.114 A request for continued examination under 37 CFR 1.114, including the fee set forth in 37 CFR 1.17(e), was filed in this application after final rejection. Since this application is eligible for continued examination under 37 CFR 1.114, and the fee set forth in 37 CFR 1.17(e) has been timely paid, the finality of the previous Office action has been withdrawn pursuant to 37 CFR 1.114. Applicant's submission filed on 12/16/2025 has been entered. Detailed Action Applicant amended claims 1, 5 13 and 16 and presented claims 1-20 for reconsideration on 12/16/2025. 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 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 of this title, 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 1-20 are rejected under 35 U.S.C. 103(a) as being unpatentable over Katzer, Patent No.: US 7,752,292 B1 (Katzer), in view of Xiao et al., Patent No.: US 10, 380,090 B1 (Xiao). Claim 1. Katzer teaches: A system for schema-based object serialization, the system comprising: one or more memories; and one or more processors, coupled to the one or more memories, configured to: obtain an object comprising a plurality of sub-objects; (5:23-6:21, a received message is the object comprising sub-objects/data items and the “predefined class schema” in the “object definition schema file” is a file associated with a set of sub-objects/data items, in response to the received message and processing the received message the object definition schema file comprising predefined class schema is accessed: “parsing the service request message and the object definition schema, mapping the data items into the predefined class schema contained in the object definition schema file, and then generating a complex object from the data-filled class schema”) identify a schema associated with serialization and deserialization of the object, the schema defining a plurality of mappings, wherein each mapping in the plurality of mappings associates a respective set of sub-objects in the plurality of sub-objects with a file in a plurality of files; (5:39-6:21, see above, object definition schema files comprising predefined class schema are obtained for converting the message to a complex object; sub-objects, e.g. parsed values of the received object are mapped into a class schema: “the document object model (DOM) parser is used to parse the object definition schema, and the simple API for XML (SAX) parser is used to parse the XML-based data items contained in the service request message. Then the object definition schema, which is held in storage space by the DOM parser, is used to map the data items into a hierarchical structure of the parsed object definition schema. For example, the service request message may have a subscriber ID, one or more MDNs that belong to the subscriber and uniquely identifies a mobile device, and a port on the mobile device to which the service request message is directed. A three-level containment relationship, or three level place holders, from the subscriber ID to the MDN, to the port, may be first defined in the object definition schema”) process the object according to the schema to obtain the plurality of files; and (5:39-6:21, see above, a received object is processed based on the object definition schema files comprising predefined class schema for converting the message to a complex object) provide an output including the plurality of files. (5:39-6:21, object definition schema files comprising predefined class schema are obtained and provided for converting the message to a complex object) Katzer did not specifically disclose but Xiao discloses wherein at least two mappings in the plurality of mappings associates a different set of sub-objects in the plurality of sub-objects with a different file in a plurality of files; (Xiao, a series of nested maps is used for mapping two different sub-objects of a nested object to two different map files: 2: 19-28, “While the object is being scanned, a map may be formed to associate numeric identifiers with names used in the nested object. The names may be strings or other alphanumeric sequences used to identify portions of the nested object. For example, a nested object may be viewed as a hierarchy of sub-objects, each of which might be associated with a name. Alternatively, a nested object may be viewed as a collection of name-value pairs, in which the values (i.e. sub-objects) may themselves contain additional collections of name-value pairs”, 7: 21-45, “A map 600 may be formed as the object is written to a storage device or memory. The map may be written to the storage device so as to include data structures linking numeric identifiers to names and, in some cases, to other information, such as type information…In some cases, rather than a global map 600 that applies to an entire object, a series of nested maps may be employed”) It would have been obvious before the effective filling date of the claimed invention to a person having ordinary skill in the art to combine the applied references for disclosing wherein at least two mappings in the plurality of mappings associates a different set of sub-objects in the plurality of sub-objects with a different file in a plurality of files because doing so would provide for using multiple mapping files as desired instead of single mapping file for achieving the same predictable result. Claim 5. Katzer teaches: A system for schema-based object processing, the system comprising: one or more memories; and one or more processors, communicatively coupled to the one or more memories, configured to: obtain a plurality of files; (5:39-6:21, object definition schema files comprising predefined class schema are obtained for converting the message to a complex object; sub-objects, e.g. parsed values of the received object are mapped into a class schema: “the document object model (DOM) parser is used to parse the object definition schema, and the simple API for XML (SAX) parser is used to parse the XML-based data items contained in the service request message. Then the object definition schema, which is held in storage space by the DOM parser, is used to map the data items into a hierarchical structure of the parsed object definition schema. For example, the service request message may have a subscriber ID, one or more MDNs that belong to the subscriber and uniquely identifies a mobile device, and a port on the mobile device to which the service request message is directed. A three-level containment relationship, or three level place holders, from the subscriber ID to the MDN, to the port, may be first defined in the object definition schema”) identify a schema associated with serialization and deserialization of an object comprising a plurality of sub-objects, the schema defining a plurality of mappings, wherein each mapping in the plurality of mappings associates a respective set of sub-objects in the plurality of sub-objects with a file in the plurality of files; (5:23-6:21, see above, a message request is an object comprising sub-objects to be converted to a complex object using object definition schema files) process one or more files in the plurality of files according to the schema to obtain one or more sets of sub-objects in the plurality of sub-objects; (5:39-6:21, see above, a complex object comprises sub-objects and wherein an object definition schema file is used for obtaining sub-objects from the received message request) provide an output including the one or more sets of sub-objects. (5:39-6:21, sub-objects are provided for generating a complex object) Katzer did not specifically disclose but Xiao discloses wherein at least two mappings in the plurality of mappings associates a different set of sub-objects in the plurality of sub-objects with a different file in a plurality of files; (Xiao, a series of nested maps is used for mapping two different sub-objects of a nested object to two different map files: 2: 19-28, “While the object is being scanned, a map may be formed to associate numeric identifiers with names used in the nested object. The names may be strings or other alphanumeric sequences used to identify portions of the nested object. For example, a nested object may be viewed as a hierarchy of sub-objects, each of which might be associated with a name. Alternatively, a nested object may be viewed as a collection of name-value pairs, in which the values (i.e. sub-objects) may themselves contain additional collections of name-value pairs”, 7: 21-45, “A map 600 may be formed as the object is written to a storage device or memory. The map may be written to the storage device so as to include data structures linking numeric identifiers to names and, in some cases, to other information, such as type information…In some cases, rather than a global map 600 that applies to an entire object, a series of nested maps may be employed”) It would have been obvious before the effective filling date of the claimed invention to a person having ordinary skill in the art to combine the applied references for disclosing wherein at least two mappings in the plurality of mappings associates a different set of sub-objects in the plurality of sub-objects with a different file in a plurality of files because doing so would provide for using multiple mapping files as desired instead of single mapping file for achieving the same predictable result. Claim 13. Katzer teaches: A method of schema-based object serialization and deserialization, the method comprising: receiving, by a system, a file; (5:39-6:21, object definition schema files are received for converting a message to a JAVA complex object) identifying, by the system, a schema associated with serialization and deserialization of an object, the schema defining a mapping that associates a set of sub-objects in a plurality of sub-objects of an object with the file; (5:23-6:21, a message request is an object comprising sub-objects to be converted to a JAVA complex object using object definition schema files) processing, by the system, the file based on the schema to obtain the set of sub-objects; and; (5:39-6:21, a complex object comprises sub-objects and wherein an object definition schema file is used for obtaining sub-objects from the received message request) providing, by the system, an output including the set of sub-objects. (5:39-6:21, sub-objects are provided for generating a JAVA complex object) Katzer did not specifically disclose but Xiao discloses the schema defining a plurality of mappings, wherein at least two mappings in the plurality of mappings associates a different set of sub-objects in a plurality of sub-objects of an object with the file; (Xiao, a series of nested maps is used for mapping two different sub-objects of a nested object to two different map files: 2: 19-28, “While the object is being scanned, a map may be formed to associate numeric identifiers with names used in the nested object. The names may be strings or other alphanumeric sequences used to identify portions of the nested object. For example, a nested object may be viewed as a hierarchy of sub-objects, each of which might be associated with a name. Alternatively, a nested object may be viewed as a collection of name-value pairs, in which the values (i.e. sub-objects) may themselves contain additional collections of name-value pairs”, 7: 21-45, “A map 600 may be formed as the object is written to a storage device or memory. The map may be written to the storage device so as to include data structures linking numeric identifiers to names and, in some cases, to other information, such as type information…In some cases, rather than a global map 600 that applies to an entire object, a series of nested maps may be employed”) It would have been obvious before the effective filling date of the claimed invention to a person having ordinary skill in the art to combine the applied references for disclosing a plurality of mappings, wherein at least two mappings in the plurality of mappings associates a different set of sub-objects in a plurality of sub-objects of an object with the file because doing so would provide for using multiple mapping files as desired instead of single mapping file for achieving the same predictable result. Katzer as modified teaches: Claim 2. The system of claim 1, wherein a sub-object in the plurality of sub-objects includes a model associated with the object, an item of metadata associated with the model, or a sub-model associated with the model. (Katzer, 5:39-6:21, a particular type/model is associated with a service request message) Claims 7 and 15 are rejected the same. Claim 3. The system of claim 1, wherein the one or more processors are configured to identify the schema based on information that identifies a class associated with the object. (Katzer, 5:39-6:21, data items are mapped “into the predefined class schema contained in the object definition schema file”) Claims 6 and 14 are rejected the same. Claim 4. The system of claim 1, wherein the one or more processors, to process the object, are configured to encode a set of sub-objects, of the plurality of sub-objects, using an encoder associated with a mapping, of the plurality of mappings, that is associated with the set of sub-objects. (Katzer, 5:39-6:21, wherein mapping data items “into the predefined class schema contained in the object definition schema file” using parsers indicates that an encoder/decoder is associated with the mapping) Claim 8. The system of claim 5, wherein the one or more processors, to process the one or more files, are configured to decode a file, of the one or more files, using a decoder associated with a mapping, of the plurality of mappings, that associates a set of sub-objects with the file. (Katzer, 5:39-6:21, wherein mapping data items “into the predefined class schema contained in the object definition schema file” using parsers indicates that an encoder/decoder is associated with the mapping) Claim 9. The system of claim 5, wherein the one or more processors are further configured to: obtain loading information that indicates a file of the one or more files; and process the file based on the loading information. (Katzer, 5:39-6:21, an object schema definition file has to be loaded before being parsed) Claim 17 is rejected the same. Claim 10. The system of claim 9, wherein the loading information is obtained via user input. (Katzer, 5:39-6:21, an object schema definition is defined by user before being parsed) Claim 18 is rejected the same. Claim 11. The system of claim 5, wherein the one or more files do not include all files in the plurality of files and the output does not include all sub-objects in the plurality of sub-objects. (Katzer, 5:39-6:21, files and sub-objects are loaded based on the type of the received message) Claim 19 is rejected the same. Claim 12. The system of claim 5, wherein the one or more files include all files in the plurality of files and the output is the object including the plurality of sub-objects. (Katzer, 5:39-6:21, files and sub-objects are loaded based on the type of the received message) Claim 20 is rejected the same. Claim 16. The method of claim 13, wherein processing the file comprises decoding the file using a decoder associated with the plurality of mappings. (Katzer, 5:39-6:21, wherein mapping data items “into the predefined class schema contained in the object definition schema file” using parsers indicates that an encoder/decoder is associated with the mapping; Xiao, 7: 21-45, wherein a series of nested maps are used) Response to Amendment and Arguments Applicant’s arguments with respect to rejected claims have been fully considered but are moot in view of the new ground of rejections as provided above. Conclusion Any inquiry concerning this communication or earlier communications from the examiner should be directed to MOHSEN ALMANI whose telephone number is (571)270-7722. The examiner can normally be reached on M-F, 9:00 to 5:00. If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Ann J. Lo can be reached on 571-272-9767. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300. Information regarding the status of an application may be obtained from the Patent Application Information Retrieval (PAIR) system. Status information for published applications may be obtained from either Private PAIR or Public PAIR. Status information for unpublished applications is available through Private PAIR only. For more information about the PAIR system, see http://pair-direct.uspto.gov. Should you have questions on access to the Private PAIR system, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative or access to the automated information system, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000. /MOHSEN ALMANI/Primary Examiner, Art Unit 2159
Read full office action

Prosecution Timeline

Oct 31, 2023
Application Filed
May 12, 2025
Non-Final Rejection — §103
Jul 20, 2025
Interview Requested
Jul 31, 2025
Applicant Interview (Telephonic)
Aug 01, 2025
Response Filed
Oct 01, 2025
Final Rejection — §103
Nov 03, 2025
Interview Requested
Nov 19, 2025
Response after Non-Final Action
Dec 16, 2025
Request for Continued Examination
Dec 31, 2025
Response after Non-Final Action
Feb 19, 2026
Non-Final Rejection — §103 (current)

Precedent Cases

Applications granted by this same examiner with similar technology

Patent 12596740
INFERRING RIGHT LEAF-CATEGORY FOR A PRODUCT USING LLM
2y 5m to grant Granted Apr 07, 2026
Patent 12591605
COMPUTER SESSION MANAGEMENT USING A LANGUAGE MODEL
2y 5m to grant Granted Mar 31, 2026
Patent 12547620
NETWORK CONFIGURATION AND MONITORING USING A FEDERATED GATEWAY
2y 5m to grant Granted Feb 10, 2026
Patent 12541551
Behavioral Curation of Media Assets
2y 5m to grant Granted Feb 03, 2026
Patent 12499084
Maintaining Block Level Snapshots Using Free Storage Space
2y 5m to grant Granted Dec 16, 2025
Study what changed to get past this examiner. Based on 5 most recent grants.

AI Strategy Recommendation

Get an AI-powered prosecution strategy using examiner precedents, rejection analysis, and claim mapping.
Powered by AI — typically takes 5-10 seconds

Prosecution Projections

3-4
Expected OA Rounds
50%
Grant Probability
72%
With Interview (+21.3%)
4y 0m
Median Time to Grant
High
PTA Risk
Based on 374 resolved cases by this examiner. Grant probability derived from career allow 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