DETAILED ACTION
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 20 January 2026 has been entered. Claims 1-20 have been examined.
Pertinent Prior Art
The following are prior art references made of record but not currently relied upon:
US 20090171897 A1
Pars. 21-25
Hierarchical placeholder case management nodes
US 20080201190 A1
Pars. 41-46
Automated processing of default case files including foreclosure and bankruptcy related documents
US 20020040339 A1
Pars. 70-85
Automated loan processing system and workflow engine
US 20010034701 A1
Pars. 60-69
Hierarchical loan document management
US 20050027651 A1
Pars. 109-115
Validation of collected loan document data using transaction workflows
US 20060253478 A1
Par. 18
“Through the use of an intuitive context-sensitive computer software interface, documents are organized in a hierarchal fashion according to client, then matter, and finally in a listing of the documents generated for that client/matter. This hierarchy more closely matches the workflow paradigm of businesses. A template manager organizes the system's legal templates in a hierarchal fashion and links each template to a specific pattern answer file which provides default answers during a document interview process. A template manager also allows users to select correct templates and pattern or answer files which are subsequently merged to form assembled documents.”
Double Patenting
The nonstatutory double patenting rejection is based on a judicially created doctrine grounded in public policy (a policy reflected in the statute) so as to prevent the unjustified or improper timewise extension of the “right to exclude” granted by a patent and to prevent possible harassment by multiple assignees. A nonstatutory double patenting rejection is appropriate where the conflicting claims are not identical, but at least one examined application claim is not patentably distinct from the reference claim(s) because the examined application claim is either anticipated by, or would have been obvious over, the reference claim(s). See, e.g., In re Berg, 140 F.3d 1428, 46 USPQ2d 1226 (Fed. Cir. 1998); In re Goodman, 11 F.3d 1046, 29 USPQ2d 2010 (Fed. Cir. 1993); In re Longi, 759 F.2d 887, 225 USPQ 645 (Fed. Cir. 1985); In re Van Ornum, 686 F.2d 937, 214 USPQ 761 (CCPA 1982); In re Vogel, 422 F.2d 438, 164 USPQ 619 (CCPA 1970); In re Thorington, 418 F.2d 528, 163 USPQ 644 (CCPA 1969).
A timely filed terminal disclaimer in compliance with 37 CFR 1.321(c) or 1.321(d) may be used to overcome an actual or provisional rejection based on nonstatutory double patenting provided the reference application or patent either is shown to be commonly owned with the examined application, or claims an invention made as a result of activities undertaken within the scope of a joint research agreement. See MPEP § 717.02 for applications subject to examination under the first inventor to file provisions of the AIA as explained in MPEP § 2159. See MPEP § 2146 et seq. for applications not subject to examination under the first inventor to file provisions of the AIA . A terminal disclaimer must be signed in compliance with 37 CFR 1.321(b).
The filing of a terminal disclaimer by itself is not a complete reply to a nonstatutory double patenting (NSDP) rejection. A complete reply requires that the terminal disclaimer be accompanied by a reply requesting reconsideration of the prior Office action. Even where the NSDP rejection is provisional the reply must be complete. See MPEP § 804, subsection I.B.1. For a reply to a non-final Office action, see 37 CFR 1.111(a). For a reply to final Office action, see 37 CFR 1.113(c). A request for reconsideration while not provided for in 37 CFR 1.113(c) may be filed after final for consideration. See MPEP § 706.07(e) and 714.13.
The USPTO Internet website contains terminal disclaimer forms which may be used. Please visit www.uspto.gov/patent/patents-forms. The actual filing date of the application in which the form is filed determines what form (e.g., PTO/SB/25, PTO/SB/26, PTO/AIA /25, or PTO/AIA /26) should be used. A web-based eTerminal Disclaimer may be filled out completely online using web-screens. An eTerminal Disclaimer that meets all requirements is auto-processed and approved immediately upon submission. For more information about eTerminal Disclaimers, refer to www.uspto.gov/patents/apply/applying-online/eterminal-disclaimer.
Claims 1-20 are rejected on the ground of nonstatutory double patenting as being unpatentable over claims 1-20 of U.S. Patent Nos. 11899635 and 10515124. Although the claims at issue are not identical, they are not patentably distinct from each other because the patented claims anticipate the instant claims. It has been held that generic invention is anticipated by the species. See MPEP 804.
Patent 11899635
Instant claims
1. A method comprising:
controlling progress of processing of a case in a case management system by:
receiving an indication to create a case instance;
loading a case model definition defining a case model comprising a hierarchical data model, wherein the case model includes a placeholder case node that is designated as a placeholder in the case model;
parsing the case model definition to generate runtime data structures representing a hierarchy of case nodes to determine the hierarchical data model to be used to create the case instance and a placeholder data to be associated with the placeholder case node;
using the case model definition to create the case instance, including by associating the placeholder data with the placeholder case node in the case instance as created, wherein a placeholder container corresponding to the placeholder case node in the case instance includes a definition of content requirements to be satisfied by a container in order to replace the placeholder container, including required content, with the container;
controlling replacement of the placeholder data for the placeholder case node with data satisfying a criteria of the case model definition, the replacement defined as a precondition for a state transition of a user defined state machine of the case model definition, the user defined state machine associated with the placeholder case node; and
evaluating the placeholder case node to determine whether the placeholder case node is populated by content items as required by the definition of content requirements of the placeholder container.
2. The method of claim 1, wherein the case instance includes a behavior, defined in the case model definition, that comprises taking an action with respect to the placeholder data.
3. The method of claim 1, wherein the placeholder data comprises a placeholder document.
4. The method of claim 3, wherein the case instance includes a behavior, defined in the case model definition, that includes taking an action associated with replacing the placeholder document with a corresponding document associated with the case instance.
5. The method of claim 4, wherein the action includes prompting a user to replace the placeholder document with a user document.
6. The method of claim 1, wherein the placeholder data comprises a placeholder case node.
7. The method of claim 1, wherein the placeholder data comprises metadata associated with the case node.
8. The method of claim 1, further comprising receiving a user data to replace the placeholder data.
9. The method of claim 8, further comprising replacing the placeholder data with the user data.
10. The method of claim 1, further comprising receiving and storing the case model definition.
11. The method of claim 10, wherein receiving and storing the case model definition includes receiving, via a case model definition interface, an indication to include the placeholder data in the case model definition.
12. A case management system, comprising:
a storage device configured to store a case model definition; and
a processor coupled to the storage device and configured to:
control progress of processing of a case in a case management system by:
receiving an indication to create a case instance;
loading a case model definition defining a case model comprising a hierarchical data model, wherein the case model includes a placeholder case node that is designated as a placeholder in the case model;
parsing the case model definition to generate runtime data structures representing a hierarchy of case nodes to determine the hierarchical data model to be used to create the case instance and a placeholder data to be associated with the placeholder case node; and
using the case model definition to create the case instance, including by associating the placeholder data with the placeholder case node in the case instance as created, wherein a placeholder container corresponding to the placeholder case node in the case instance includes a definition of content requirements to be satisfied by a container in order to replace the placeholder container, including required content, with the container;
controlling replacement of the placeholder data for the placeholder case node with data satisfying a criteria of the case model definition, the replacement defined as a precondition for a state transition of a user defined state machine of the case model definition, the user defined state machine associated with the placeholder case node; and
evaluating the placeholder case node to determine whether the placeholder case node is populated by content items as required by the definition of content requirements of the placeholder container.
13. The system of claim 12, wherein the placeholder data comprises a placeholder document.
14. The system of claim 13, wherein the case instance includes a behavior, defined in the case model definition, that includes taking an action associated with replacing the placeholder document with a corresponding document associated with the case instance; and wherein the processor is further configured to take the action as defined in the case model definition.
15. The system of claim 14, wherein the action includes prompting a user to replace the placeholder document with a user document.
16. The system of claim 12, wherein the processor is further configured to receive a user data to replace the placeholder data.
17. A computer program product embodied in a non-transitory computer readable storage medium and comprising computer instructions for:
controlling progress of processing of a case in a case management system by:
receiving an indication to create a case instance;
loading a case model definition defining a case model comprising a hierarchical data model, wherein the case model includes a placeholder case node that is designated as a placeholder in the case model;
parsing the case model definition to generate runtime data structures representing a hierarchy of case nodes to determine the hierarchical data model to be used to create the case instance and a placeholder data to be associated with the placeholder case node; and
using the case model definition to create the case instance, including by associating the placeholder data with the placeholder case node in the case instance as created, wherein a placeholder container corresponding to the placeholder case node in the case instance includes a definition of content requirements to be satisfied by a container in order to replace the placeholder container, including required content, with the container;
controlling replacement of the placeholder data for the placeholder case node with data satisfying a criteria of the case model definition, the replacement defined as a precondition for a state transition of a user defined state machine of the case model definition, the user defined state machine associated with the placeholder case node; and
evaluating the placeholder case node to determine whether the placeholder case node is populated by content items as required by the definition of content requirements of the placeholder container.
18. The computer program product of claim 17, wherein the placeholder data comprises a placeholder document.
19. The computer program product of claim 18, wherein the case instance includes a behavior, defined in the case model definition, that includes taking an action associated with replacing the placeholder document with a corresponding document associated with the case instance.
20. The computer program product of claim 19, wherein the action includes prompting a user to replace the placeholder document with a user document.
1. A method of case management, the method comprising:
receiving an indication to create a new case instance; loading a case model definition defining a case model, wherein the case model includes a placeholder case node that is designated as a placeholder in the case model;
parsing the case model definition to generate runtime data structures representing a hierarchy of case nodes to be used to create the case instance and placeholder data to be associated with the placeholder case node, wherein creating the case instance includes associating the placeholder data with the placeholder case node in the case instance as created, wherein a placeholder container corresponding to the placeholder case node in the case instance includes a definition of content requirements to be satisfied by a container in order to replace the placeholder container, including required content items of a specific type, with the container;
controlling replacement of the placeholder data for the placeholder case node with data satisfying a criteria of the case model definition, wherein the placeholder data includes a state transition of a state machine that is user-defined by a per case-node definition for the placeholder case node; and
evaluating the placeholder case node to determine whether the placeholder case node is populated by content items as required by the definition of content requirements of the placeholder container.
2. The method of claim 1, wherein the case instance includes a behavior, defined in the case model definition, that comprises taking an action with respect to the placeholder data.
3. The method of claim 1, wherein the placeholder data comprises a placeholder document.
4. The method of claim 3, wherein the case instance includes a behavior, defined in the case model definition, that includes taking an action associated with replacing the placeholder document with a corresponding document associated with the case instance.
5. The method of claim 4, wherein the action includes prompting a user to replace the placeholder document with a user document.
6. The method of claim 1, wherein the placeholder data comprises a placeholder case node.
7. The method of claim 1, wherein the placeholder data comprises metadata associated with the case node.
8. The method of claim 1, further comprising receiving user data to replace the placeholder data.
9. The method of claim 8, further comprising replacing the placeholder data with the user data.
10. The method of claim 1, further comprising receiving and storing the case model definition.
11. The method of claim 10, wherein receiving and storing the case model definition includes receiving, via a case model definition interface, an indication to include the placeholder data in the case model definition.
12. A case management system, comprising:
a storage device configured to store a case model definition; and
a processor coupled to the storage device and configured to control progress of processing of a case in a case management system by:
receiving an indication to create a new case instance; loading a case model definition defining a case model, wherein the case model includes a placeholder case node that is designated as a placeholder in the case model;
parsing the case model definition to generate runtime data structures representing a hierarchy of case nodes to be used to create the case instance and placeholder data to be associated with the placeholder case node, wherein creating the case instance includes associating the placeholder data with the placeholder case node in the case instance as created, wherein a placeholder container corresponding to the placeholder case node in the case instance includes a definition of content requirements to be satisfied by a container in order to replace the placeholder container, including required content items of a specific type, with the container;
controlling replacement of the placeholder data for the placeholder case node with data satisfying a criteria of the case model definition, wherein the placeholder data includes a state transition of a state machine that is user-defined by a per case-node definition for the placeholder case node; and
evaluating the placeholder case node to determine whether the placeholder case node is populated by content items as required by the definition of content requirements of the placeholder container.
13. The system of claim 12, wherein the placeholder data comprises a placeholder document.
14. The system of claim 13, wherein the case instance includes a behavior, defined in the case model definition, that includes taking an action associated with replacing the placeholder document with a corresponding document associated with the case instance; and wherein the processor is further configured to take the action as defined in the case model definition.
15. The system of claim 14, wherein the action includes prompting a user to replace the placeholder document with a user document.
16. The system of claim 12, wherein the processor is further configured to receive user data to replace the placeholder data.
17. A computer program product for case management, the computer program product being embodied in a non-transitory computer readable storage medium and comprising computer instructions for:
receiving an indication to create a new case instance; loading a case model definition defining a case model, wherein the case model includes a placeholder case node that is designated as a placeholder in the case model;
parsing the case model definition to generate runtime data structures representing a hierarchy of case nodes to be used to create the case instance and placeholder data to be associated with the placeholder case node, wherein creating the case instance includes associating the placeholder data with the placeholder case node in the case instance as created, wherein a placeholder container corresponding to the placeholder case node in the case instance includes a definition of content requirements to be satisfied by a container in order to replace the placeholder container, including required content items of a specific type, with the container;
controlling replacement of the placeholder data for the placeholder case node with data satisfying a criteria of the case model definition, wherein the placeholder data includes a state transition of a state machine that is user-defined by a per case-node definition for the placeholder case node; and
evaluating the placeholder case node to determine whether the placeholder case node is populated by content items as required by the definition of content requirements of the placeholder container.
18. The computer program product of claim 17, wherein the placeholder data comprises a placeholder document.
19. The computer program product of claim 18, wherein the case instance includes a behavior, defined in the case model definition, that includes taking an action associated with replacing the placeholder document with a corresponding document associated with the case instance.
20. The computer program product of claim 19, wherein the action includes prompting a user to replace the placeholder document with a user document.
Patent 10515124
Instant claims
1. A method of controlling progress of processing of a case in a case management system, the method comprising:
at a computer having a processor and at least one non-transitory memory, the at least one non-transitory memory containing instructions causing the processor to:
load a case model definition of a case model that comprises a hierarchical container model, the case model definition defining a hierarchy of case nodes, wherein each case node is associated with user data and behaviors, wherein the case model includes a non-leaf placeholder container node that is designated as a placeholder in the case model, wherein the placeholder container node includes a definition of attributes content requirements to be satisfied by a container in order to replace the placeholder container node with the container;
receive an indication to create a case instance based on the case model definition;
responsive to receiving the indication to create the case instance, create the case instance by parsing the case model definition to generate runtime data structures representing the hierarchy of case nodes wherein the runtime data structures include placeholder data associated with the placeholder container node, wherein a presence of the placeholder data in the runtime data structures enables controlling replacement of the placeholder data for the placeholder container node with data satisfying a criteria of the case model definition.
2. The method of claim 1, wherein the generated runtime data structures comprise a runtime data struture for at least one node of the case instance, and the runtime data structure for the at least one node of the case instance includes a behavior, defined in the case model definition, that comprises taking an action with respect to the placeholder data.
3. The method of claim 1, wherein the placeholder data comprises a placeholder document.
4. The method of claim 3, wherein the case instance includes a behavior, defined in the case model definition, that includes taking an action associated with replacing the placeholder document with a corresponding document associated with the case instance.
5. The method of claim 4, wherein the action includes prompting a user to replace the placeholder document with a user document.
6. The method of claim 1, wherein the placeholder data comprises a placeholder case node.
7. The method of claim 1, wherein the placeholder data comprises metadata associated with the placeholder container node.
8. The method of claim 1, further comprising receiving user data to replace the placeholder data.
9. The method of claim 8, further comprising replacing the placeholder data with user data.
10. The method of claim 1, further comprising receiving and storing the case model definition as an xml file.
11. The method of claim 10, wherein receiving and storing the case model definition includes receiving, via a case model definition interface, an indication to include the placeholder data in the case model definition.
12. A case management system, comprising:
a storage device configured to store a case model definition; and
a processor coupled to the storage device and configured to control progress of processing of a case in a case management system by:
loading the case model definition of a case model that comprises a hierarchical container model, the case model definition defining a hierarchy of case nodes, wherein each case node is associated with user data and behaviors, wherein the case model includes a non-leaf placeholder container node that is designated as a placeholder in the case model wherein the placeholder container node includes a definition of content requirements to be satisfied by a container in order to replace the placeholder container node with the container;
receiving an indication to create a case instance based on the case model definition;
responsive to receiving the indication to create the case instance, creating the case instance by parsing the case model definition to generate runtime data structures representing the hierarchy of case nodes, wherein the runtime data structures include placeholder data associated with the placeholder container node, wherein a presence of the placeholder data in the runtime data structures enables controlling replacement of the placeholder data for the placeholder container node with data satisfying a criteria of the case model definition.
13. The system of claim 12, wherein the placeholder data comprises a placeholder document.
14. The system of claim 13, wherein the case instance includes a behavior, defined in the case model definition, that includes taking an action associated with replacing the placeholder document with a corresponding document associated with the case instance; and wherein the processor is further configured to take the action as defined in the case model definition.
15. The system of claim 14, wherein the action includes prompting a user to replace the placeholder document with a user document.
16. The system of claim 12, wherein the processor is further configured to receive user data to replace the placeholder data.
17. A computer program product to control progress of processing of a case in a case management system, the computer program product being embodied in a non-transitory computer readable storage medium and comprising computer instructions for:
loading a case model definition of a case model that comprises a hierarchical container model the case model definition defining a heirarchy of case nodes, wherein each case node is associated with user data and behaviors, wherein the case model includes a non-leaf placeholder container node that is designated as a placeholder in the case model wherein the placeholder container node includes a definition of content requirements to be satisfied by a container in order to replace the placeholder container node with the container;
receiving an indication to create a case instance based on the case model definition;
responsive to receiving the indication to create the case instance, create the case instance by parsing the case model definition to generate runtime data structures representing the hierarchy of case nodes, wherein the runtime data structures include placeholder data associated with the placeholder container node, wherein a presence of the placeholder data in the runtime data structures enables controlling replacement of the placeholder data for the placeholder container node with data satisfying a criteria of the case model definition.
18. The computer program product of claim 17, wherein the placeholder data comprises a placeholder document.
19. The computer program product of claim 18, wherein the case instance includes a behavior, defined in the case model definition, that includes taking an action associated with replacing the placeholder document with a corresponding document associated with the case instance.
20. The computer program product of claim 19, wherein the action includes prompting a user to replace the placeholder document with a user document.
1. A method of case management, the method comprising:
receiving an indication that a new case instance; loading a case model definition defining a case model, wherein the case model includes a placeholder case node that is designated as a placeholder in the case model;
parsing the case model definition to generate runtime data structures representing a hierarchy of case nodes to be used to create the case instance and placeholder data to be associated with the placeholder case node, wherein creating the case instance includes associating the placeholder data with the placeholder case node in the case instance as created, wherein a placeholder container corresponding to the placeholder case node in the case instance includes a definition of content requirements to be satisfied by a container in order to replace the placeholder container, including required content, with the container;
controlling replacement of the placeholder data for the placeholder case node with data satisfying a criteria of the case model definition, wherein the placeholder data includes a state transition of a state machine that is user-defined by a per case-node definition for the placeholder case node; and
evaluating the placeholder case node to determine whether the placeholder case node is populated by content items as required by the definition of content requirements of the placeholder container.
2. The method of claim 1, wherein the case instance includes a behavior, defined in the case model definition, that comprises taking an action with respect to the placeholder data.
3. The method of claim 1, wherein the placeholder data comprises a placeholder document.
4. The method of claim 3, wherein the case instance includes a behavior, defined in the case model definition, that includes taking an action associated with replacing the placeholder document with a corresponding document associated with the case instance.
5. The method of claim 4, wherein the action includes prompting a user to replace the placeholder document with a user document.
6. The method of claim 1, wherein the placeholder data comprises a placeholder case node.
7. The method of claim 1, wherein the placeholder data comprises metadata associated with the case node.
8. The method of claim 1, further comprising receiving a user data to replace the placeholder data.
9. The method of claim 8, further comprising replacing the placeholder data with the user data.
10. The method of claim 1, further comprising receiving and storing the case model definition.
11. The method of claim 10, wherein receiving and storing the case model definition includes receiving, via a case model definition interface, an indication to include the placeholder data in the case model definition.
12. A case management system, comprising:
a storage device configured to store a case model definition; and
a processor coupled to the storage device and configured to control progress of processing of a case in a case management system by:
receiving an indication that a new case instance; loading a case model definition defining a case model, wherein the case model includes a placeholder case node that is designated as a placeholder in the case model;
parsing the case model definition to generate runtime data structures representing a hierarchy of case nodes to be used to create the case instance and placeholder data to be associated with the placeholder case node, wherein creating the case instance includes associating the placeholder data with the placeholder case node in the case instance as created, wherein a placeholder container corresponding to the placeholder case node in the case instance includes a definition of content requirements to be satisfied by a container in order to replace the placeholder container, including required content, with the container;
controlling replacement of the placeholder data for the placeholder case node with data satisfying a criteria of the case model definition, wherein the placeholder data includes a state transition of a state machine that is user-defined by a per case-node definition for the placeholder case node; and
evaluating the placeholder case node to determine whether the placeholder case node is populated by content items as required by the definition of content requirements of the placeholder container.
13. The system of claim 12, wherein the placeholder data comprises a placeholder document.
14. The system of claim 13, wherein the case instance includes a behavior, defined in the case model definition, that includes taking an action associated with replacing the placeholder document with a corresponding document associated with the case instance; and wherein the processor is further configured to take the action as defined in the case model definition.
15. The system of claim 14, wherein the action includes prompting a user to replace the placeholder document with a user document.
16. The system of claim 12, wherein the processor is further configured to receive a user data to replace the placeholder data.
17. A computer program product for case management, the computer program product being embodied in a non-transitory computer readable storage medium and comprising computer instructions for:
receiving an indication that a new case instance; loading a case model definition defining a case model, wherein the case model includes a placeholder case node that is designated as a placeholder in the case model;
parsing the case model definition to generate runtime data structures representing a hierarchy of case nodes to be used to create the case instance and placeholder data to be associated with the placeholder case node, wherein creating the case instance includes associating the placeholder data with the placeholder case node in the case instance as created, wherein a placeholder container corresponding to the placeholder case node in the case instance includes a definition of content requirements to be satisfied by a container in order to replace the placeholder container, including required content, with the container;
controlling replacement of the placeholder data for the placeholder case node with data satisfying a criteria of the case model definition, wherein the placeholder data includes a state transition of a state machine that is user-defined by a per case-node definition for the placeholder case node; and
evaluating the placeholder case node to determine whether the placeholder case node is populated by content items as required by the definition of content requirements of the placeholder container.
18. The computer program product of claim 17, wherein the placeholder data comprises a placeholder document.
19. The computer program product of claim 18, wherein the case instance includes a behavior, defined in the case model definition, that includes taking an action associated with replacing the placeholder document with a corresponding document associated with the case instance.
20. The computer program product of claim 19, wherein the action includes prompting a user to replace the placeholder document with a user document.
Response to Arguments / Allowable Subject Matter
Applicant’s arguments filed 20 January 2026 directed to the prior art rejection have been fully considered and are persuasive. The 35 USC 103 rejection has been withdrawn.
Prior art of record does not teach or suggest the subject matter of claims 1-20; claims 1-20 would be allowable if the double patenting rejection is overcome.
Conclusion
Any inquiry concerning this communication or earlier communications from the examiner should be directed to SYED HASAN whose telephone number is (571)270-5008. The examiner can normally be reached M-F 8am - 5 pm.
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, Boris Gorney can be reached at (571)270-5626. 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.
/SYED H HASAN/Primary Examiner, Art Unit 2154