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 .
Status of Claims
This communication is responsive to the submission filed January 22, 2026.
Claims 1, 9, and 17 are amended.
Claims 1-20 are pending.
Response to Remarks
35 U.S.C. §§102/103
Applicant’s amendments and accompanying remarks have been considered and found persuasive. However, in view of the 35 U.S.C. § 112(a) rejection below, further search and consideration under this ground may be required at a later date.
Claim Rejections - 35 USC § 112
The following is a quotation of the first paragraph of 35 U.S.C. 112(a):
(a) IN GENERAL.—The specification shall contain a written description of the invention, and of the manner and process of making and using it, in such full, clear, concise, and exact terms as to enable any person skilled in the art to which it pertains, or with which it is most nearly connected, to make and use the same, and shall set forth the best mode contemplated by the inventor or joint inventor of carrying out the invention.
The following is a quotation of the first paragraph of pre-AIA 35 U.S.C. 112:
The specification shall contain a written description of the invention, and of the manner and process of making and using it, in such full, clear, concise, and exact terms as to enable any person skilled in the art to which it pertains, or with which it is most nearly connected, to make and use the same, and shall set forth the best mode contemplated by the inventor of carrying out his invention.
Claims 1-20 are rejected under 35 U.S.C. 112(a) or 35 U.S.C. 112 (pre-AIA ), first paragraph, as failing to comply with the written description requirement. The claim(s) contains subject matter which was not described in the specification in such a way as to reasonably convey to one skilled in the relevant art that the inventor or a joint inventor, or for applications subject to pre-AIA 35 U.S.C. 112, the inventor(s), at the time the application was filed, had possession of the claimed invention.
Per Claims 1-20: Independent claim 1 has been amended to recite “normalizing, by a blockchain-agnostic microservice of the system, the logic into a platform-independent logic based on a determined blockchain type associated with the distributed application”. However, the originally-filed specification fails to describe such subject matter. Rather, ¶ 31 of the originally-filed specification describes that the Network microservice normalizes data from the blockchain for each type of blockchain technology. Further, ¶ 33 describes that the data from a blockchain block is provided to Blockchain Normalizer module that converts the data to a data type that can be used with the remainder of the system and microservices. Also, ¶ 49 describes that the network microservices converts the data into a normalized format. Additionally, ¶ 54 describes that the claim, i.e., data, is normalized and provided to other microservices for processing. Paragraph 55 then describes that an insurance company receives the claim from the blockchain and normalizes it. In other words, in each of the instances of the originally-filed specification that describes normalizing, it is data being read from the blockchain that is being normalized. It does not describe normalizing logic as claimed. Therefore, there is insufficient written description for this claim amendment. Independent claims 9 and 17 recite similar subject matter and are rejected for similar reasons. The dependent claims are also rejected by reason of their dependency from the respective independent claims.
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure.
U.S. Patent Pub. No. 2017/0031874 discloses that a deep link can have a name of a mobile app and a network address of a device on which an instance of the app is running. Deep links can be stored in a blockchain, along with related data, like the location of the device running the app. The deep links in the blockchain can be analysed to make a social network graph. A node in the graph is a network address of a mobile device running a mobile app. An edge between 2 nodes is a mobile app, which had 2 instances of the app interacting, where each instance runs on one of the nodes. The edge could be directed, going from the first earlier instance to the second instance. A blockchain can be used by a mobile app to write a deep link referring to itself. The app instance is looking to interact with other instances of the app. Another device scans the blockchain to get the deep link. It makes an instance of the app that interacts with the instance that wrote the deep link to the blockchain. The deep link in the blockchain could have associated data like the start and stop times of an interaction with other instances. Thus a blockchain can promote the direct interaction of instances of mobile apps. The logic to decide whether an app writes a deep link to the blockchain can be instantiated as a Writer. This can exist inside the app, or on the device, but outside any app, or on the network. Also, the app server might use a Writer, where the Writer is on the server machine or on the network.
U.S. Patent Pub. No. 2017/0148021 discloses providing secure transaction functionality using a centralized digital gateway configured to process transactions of various types, using different transaction processing entities, within a single processing flow. The digital gateway may implement rules and logic to optimize transaction processing costs. Additionally, transaction authorization, various types of transaction analyses, and transaction processing and dispatch processes may be performed in parallel, as directed by the implemented rules and logic, in order to optimize transaction processing costs and processing speeds. Further, digital gateway may be configured to normalize transaction request data across different transaction types, allowing the transaction request data to be transmitted in a uniform manner to related back-end systems, partner systems, and transaction processors.
U.S. Patent No. 10,084,794 discloses a process including: processing, with a permission-management application requests to manage permissions of one or more users to access resources with client computing devices, wherein: the permission-management application is configured to manage permissions for users of an organization to access a plurality of network-accessible applications; the plurality of different network-accessible applications have different permission-management application program interfaces; and the permission-management application is configured to manage permissions for users to access respective instances of a plurality of different native applications executing on the client computing devices.
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 NILESH B KHATRI whose telephone number is (571)270-7083. The examiner can normally be reached 8:30 AM - 5:30 PM Monday-Friday, alternating Fridays off.
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, Neha Patel can be reached at (571) 270-1492. 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.
/NILESH B KHATRI/Primary Examiner, Art Unit 3699
Prosecution Insights