CTNF 18/565,154 CTNF 89041 DETAILED ACTION Continued Examination under 37 CFR 1.114 07-42-04 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 05/14/2026 has been entered. An action on the RCE follows. The present application, filed on or after March 16, 2013, is being examined under the first inventor to file provisions of the AIA. 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. Status of the application This Office Action is in response to Applicant's amendments filed on 05/14/2026. Claims 1-7 are pending for this examination. Acknowledgement This Office action has been issued in response to reconsideration request filed on 05/14/2026. Claims 1-7 are pending. Claims 1, 6 and 7 are amended. Response to Arguments Applicants' arguments have been carefully and respectfully considered and addressed. Accordingly, this action has been made non-final. Applicant’s arguments were fully considered and are moot in view of the new ground of rejection. Arguments are moot in light of the new ground of rejection, which relies upon prior art made of record Kui at el. (Pub. No.: CN111651156A). Objection to Drawings Drawings Fig. 2 has been objected. The drawing shows an arrow from M7 to M6. The arrow is between two ICI boxes. ICI boxes are input communication interface. There should not be an arrow between two input communication interfaces. An arrow is supposed to be from an output to an input communication interface. As such, the examiner thinks, this arrow should not be in the drawing. Appropriate correction or explanation is required. Claim Rejections - 35 USC § 112 07-30-01 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. 07-31-01 Claims 1, 6 and 7 rejected under 35 U.S.C. 112(a) as failing to comply with the written description requirement. The claims contain 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 at the time the application was filed, had possession of the claimed invention. Claim 1 recites “ wherein the pre-configured communication component includes a communication library with a plurality of functions in multiple programming languages;”. The limitation has no support in the originally submitted disclosure. Specification recites on page 10 starting at line 6, “ The communication component is a pre-configured communication library, which may include a plurality of functions to implement different functions. Moreover, the communication library may support function modules using different programming languages .” This paragraph teaches that communication library supports function modules using different languages. Please note that function modules are building blocks which are put together to form an application. Function modules may use different languages to communicate with the library functions. In other words, library provides interfaces for different languages to call library functions. The claim limitation teaches that library functions are in multiple program languages, which is not supported in the specification. Examiner would suggest using claim language close to the specification language to avoid new matter issues. Claims 6 and 7 have substantially similar claim limitations as above and can be rejected using the same rationale as above. Claims 2 - 5 are rejected for being dependent on a rejected base claim. For this examination, examiner interprets the claim limitation in light of the specification as shown above. Claim Rejections - 35 USC § 103 07-20-aia AIA 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. Claims 1, 3 and 4 are rejected under AIA 35 U.S.C. 103 as being unpatentable over Gruby et al. (hereinafter Gruby, Publication No.: US 2016/0124782) in view of Kui et al. (hereinafter Kui, Publication No.: CN111651156). As per claim 1, (Currently amended) Gruby teaches, An application program construction method comprising: determining a plurality of functional modules that constituting an application program; (Gruby recites in [0017] “An "independent component block" may refer an independent application, but an independent component block may also refer to a portion of an application if the application has multiple independent component blocks . In certain embodiments, a first independent application may be integrated with a second independent application to create a third independent application that has a first component block and a second component block .” Here an independent block is equivalent to a functional module. Please note that an independent application can be a collection of independent blocks.) attaching a pre-configured communication component to each functional module; (Gruby Fig. 1B shows each component block [e.g., 131 and 136] is attached to a block communication module [e.g., 133 and 138]. Gruby recites in [0019] “ This structure allows both independent applications and independent component blocks to be created and used modularly without a need to customize communications between the blocks in different implementations. ” This shows that the communication blocks are preconfigured.) establishing a connection relationship between the functional modules by using the communication components; and (Gruby recites in [0021] “ FIG. 1B then illustrates a block diagram of a device, in accordance with an example embodiment, for communications between independent component blocks .”) storing the connection relationship in a configuration file. (Gruby recites in [0022] starting at line 5 “ First application module 120 may thus operate as an independent element which uses 1 st resource identifier 122 and block communication module 123 to register a protocol name with the URL handler module 140. A record of this association may be stored in URL Association module 142. This record may be part of a table, a linked list, or any other record that may be used by the URL handler module 140 to route subsequent messages using communication routing module 149 .” Here the URL associate module 142 saves the record in a table or linked list, etc. This is the connection configuration file.) Gruby teaches creation of an application using independent component modules where component modules communicate with each other via a communication module and a communication library. Gruby does not explicitly teach “ wherein the pre-configured communication component includes a communication library with a plurality of functions in multiple programming languages ;”. However, in analogous art of software application creation, Kui teaches, wherein the pre-configured communication component includes a communication library with a plurality of functions in multiple programming languages ; (Please see the 35 USC 112(a) rejection above for proper interpretation of this claim limitation. Kui recites in claim 1 “ A software development kit adapting to a plurality of development languages is characterized by comprising an interface layer and a core dynamic library ; the i nterface layer contains interface APls of a plurality of different languages ; the core dynamic library is developed and generated by adopting C or C + + language, and a plurality of functions with different functions are encapsulated in the core dynamic library; each interface API calls the functions of the core dynamic library through different tools .” This shows a library can have an interface layer which allows using the library from different language. Please note here library refers to any library including a communication library.) Therefore, it would have been obvious to a person of the ordinary skill in the art before the effective filling date of the invention to modify the above teaching of Gruby of use of a library by incorporating the teaching “ wherein the pre-configured communication component includes a communication library with a plurality of functions in multiple programming languages; ” of Kui. The modification would have been obvious because one of the ordinary skills of the art would have implemented the function of Kui to make the library universal by providing interface to the library which will allow the library to be used from modules written in different languages. As per claim 3, Gruby teaches, wherein the communication component comprises at least one of an input communication interface and an output communication interface. (Gruby Fig. 2 shows block communication module 233 outputs 250 and inputs 260. This shows input and output interface.) As per claim 4, ( Currently amended) Gruby teaches, wherein the communication component further comprises at least one of: a monitoring module, a caching module, and a load balancing module. (Gruby recites in [0047] last sentence “ Further, sending the second message 260 in response to the performing of the first process may involve a trigger message being sent by the first process, a second process monitoring resource usage to determine when the first process is complete, or any other such indication associated with the first process .” This shows that the second process is monitoring resource usage.) Claims 2 and 5 are rejected under AIA 35 U.S.C. 103 as being unpatentable over Gruby and Kui as applied to claim 1 in view of Chen (hereinafter Chen, Publication No.: US 2020/0293383). As per claim 2, Gruby and Kui teach creation of application using independent component blocks. They do not explicitly teach, “ wherein the functional modules comprise threads or processes to implement independent functions.” However, in analogous art of application creation using component blocks, Chen teaches, wherein the functional modules comprise threads or processes to implement independent functions. (Chen recites in [0070] starting at line 2, “ FIG. 3A shows an application 12" in its execution phase, where the module implementation definition is translated by runtime into hardware-executable instructions 22A' 22 B', which are in tum executed in computer hardware as processes ( or threads) 24A 24B that perform the modules' intended tasks .”) Therefore, it would have been obvious to a person of the ordinary skill in the art before the effective filling date of the invention to modify the above teaching of Gruby and Kui of application creation by incorporating the teaching “ wherein the functional modules comprise threads or processes to implement independent functions ” of Chen. The modification would have been obvious because one of the ordinary skills of the art would have implemented the function of executing each independent function as a task or as a thread to perform the function it is supposed to perform. As per claim 5, Chen teaches, further comprising modifying execution logic of the application program by modifying the configuration file. (Chen recites in [0003] starting at line 5, “ One character of application module is that it exposes its attributes or parameters through the application-building environment (i.e. an IDE), where a developer can change the application's setting or behaviour by configuring these parameters .”) Claims 6 and 7 are rejected under AIA 35 U.S.C. 103 as being unpatentable over Comer (Pub. No.: US 2023/0058197) in view of Gruby et al. (hereinafter Gruby, Pub. No.: US 2016/0124782) in view of Chen (Publication No.: US 2020/0293383) and further in view of Kui et al. (hereinafter Kui, CN111651156A). As per claim 6, (Currently amended) Comer teaches, An execution method of an application program, the method comprising: initializing an application program, and loading an application program configuration file; (Comer recites in claim 1, last 3 limitations “ programmatically build the software application, by: registering a plurality of reusable software modules from the set to the software application; and …. initialize the software application as a configuration file , wherein the initialization automatically applies a theme to each activity of each reusable software module registered to the software application ,..”.) wherein the output communication interface of the first functional module connects directly to an input communication interface of the second functional module. (Comer Fig. 2A and 2B show software module 2 and software module 3 communicates directly. Comer recites in [0065] starting at line 7, “ For example, modules may reference each other by utilizing 'deeplinks' which are managed by example frameworks described herein ( .g., the module 22 can 'fire' a deep link which is intended for the module 23, ….). ” Please note that here “deeplinks” provides output and input communication interfaces.) Comer teaches creation of software applications. Comer does not explicitly teach, “ a pre-configured port in an output communication interface of the second functional module” and “a pre-configured port in an output communication interface of the second functional module, each functional module includes a pre-configured communication component with a communication library ”. However, in analogous art of software application creation Gruby teaches, “ a pre-configured port in an output communication interface of the second functional module” and “a pre-configured port in an output communication interface of the second functional module” (Gruby Fig. 1B shows each component block or functional module [e.g., 131 and 136] is attached to a block communication module [e.g., 133 and 138]. Gruby recites in [0019] “ This structure allows both independent applications and independent component blocks to be created and used modularly without a need to customize communications between the blocks in different implementations. ” This shows that the communication blocks are preconfigured. Fig. 1B also shows that the communication blocks have both input and output interfaces.) each functional module includes a pre-configured communication component with a communication library (Gruby Fig. 1B shows each component block [e.g., 131 and 136] is attached to a block communication module [e.g., 133 and 138]. Gruby recites in [0019] “ This structure allows both independent applications and independent component blocks to be created and used modularly without a need to customize communications between the blocks in different implementations. ” This shows that the communication blocks are preconfigured.) Therefore, it would have been obvious to a person of the ordinary skill in the art before the effective filling date of the invention to modify the above teaching of Comer of application creation by incorporating the teaching “ a pre-configured port in an output communication interface of the second functional module” and “a pre-configured port in an output communication interface of the second functional module, each functional module includes a pre-configured communication component with a communication library ” of Gruby. The modification would have been obvious because one of the ordinary skills of the art would have implemented the function of providing input and output ports to each function modules for inter-process communication. Comer and Gruby teach software application creation using independent software modules. They do not explicitly teach, “ when a first functional module of the application program receives data, triggering execution of the first functional module; and sending, by the first functional module, data to a [preconfigured port in an output communication interface of the first functional module] according to an execution result of the first functional module, so as to trigger execution of a second functional module bound to the port, sending, by the second functional module, data to a [pre-configured port in an output communication interface of the second functional module] according to an execution result of the second functional module, so as to trigger execution of a third functional module bound to the port, and so on, until execution of the application program ends.” However, Chen and Gruby together teach, when a first functional module of the application program receives data, triggering execution of the first functional module; and (Chen recites in [0069] and [0070] “ Application Runtime Process. An application enters its execution phase when its implementation is executed by a runtime .” Chen recites in [0079] “ The "Reading" task, which reads input files and parses the file content for retrieving HL 7 records, output retrieved records; ”. Please refer to Fig. 4. This shows that the first functional module [or task] receives input file and triggering execution of parsing the file and retrieves HL7 records.) sending, by the first functional module, data to a preconfigured port in an output communication interface of the first functional module according to an execution result of the first functional module, so as to trigger execution of a second functional module bound to the port, (Chen Fig. 4 shows output from the “reading” task [or function] to the filtering task and triggers the filtering task. Please note it has been shown above that Gruby teaches preconfigured port in an output communication interface.) sending, by the second functional module, data to a pre-configured port in an output communication interface of the second functional module according to an execution result of the second functional module, so as to trigger execution of a third functional module bound to the port, and (Chen Fig. 4 shows output from the filtering task sends input to the “writing” task and triggers the writing task. Please note it has been shown above that Gruby teaches preconfigured port in an output communication interface.) so on, until execution of the application program ends[[.]] ; (Chen Fig. 4 shows out from the “writing” task ends the application program.) Therefore, it would have been obvious to a person of the ordinary skill in the art before the effective filling date of the invention to modify the above teaching of Comer and Gruby of application creation by incorporating the teaching “ when a first functional module of the application program receives data, triggering execution of the first functional module; and sending, by the first functional module, data to a [preconfigured port in an output communication interface of the first functional module] according to an execution result of the first functional module, so as to trigger execution of a second functional module bound to the port, sending, by the second functional module, data to a [pre-configured port in an output communication interface of the second functional module] according to an execution result of the second functional module, so as to trigger execution of a third functional module bound to the port, and so on, until execution of the application program ends” of Chen and Gruby. The modification would have been obvious because one of the ordinary skills of the art would have implemented the function of inter-process communication for an application to work using independent software modules. Comer, Gruby and Chen teach creation of software applications using functional modules and application program configuration files. They do not explicitly teach, “ [communication library] having a plurality of functions in multiple programming languages .” However, in analogous art of software application creation using a library, Kui teaches, [communication library] having a plurality of functions in multiple programming languages . (Please see the 35 USC 112(a) rejection above for proper interpretation of this claim limitation. Kui recites in claim 1 “ A software development kit adapting to a plurality of development languages is characterized by comprising an interface layer and a core dynamic library ; the i nterface layer contains interface APls of a plurality of different languages ; the core dynamic library is developed and generated by adopting C or C + + language, and a plurality of functions with different functions are encapsulated in the core dynamic library; each interface API calls the functions of the core dynamic library through different tools .” This shows a library can have an interface layer which allows using the library from different language. Please note here library refers to any library including a communication library.) Therefore, it would have been obvious to a person of the ordinary skill in the art before the effective filling date of the invention to modify the above teaching of Comer, Gruby and Chen of application creation by incorporating the teaching “ [communication library] having a plurality of functions in multiple programming languages .” of Kui. The modification would have been obvious because one of the ordinary skills of the art would have implemented the function of Kui to make the library universal by providing interface to the library which will allow the library to be used from modules written in different languages. As per claim 7 , this is a device claim that substantially parallels the limitations of the method claim 6. It would have been obvious to one of ordinary skill in the art before the time of the effective filing date of the invention to implement the prescribed method steps as a device. References of Note Examiner has cited particular columns, line numbers, references, or figures in the references applied to the claims above for the convenience of the applicant. Although the specified citations are representative of the teachings of the art and are applied to specific limitations within the individual claim, other passages and figures may apply as well. It is respectfully requested from the applicant in preparing responses to fully consider the reference in entirety, as potentially teaching all or part of the claimed invention. See MPEP §§ 2141.02 and 2123. Contact Information Any inquiry concerning this communication or earlier communications from the examiner should be directed to HOSSAIN MORSHED whose telephone number is (571)272-3335. The examiner can normally be reached on Monday – Friday12:00 PM – 9 PM Eastern Time. The email address for the examiner is hossain.morshed@uspto.gov. Examiner interviews are available via telephone or 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, Wei Mui can be reached on (571)272-3708. /HOSSAIN M MORSHED/Primary Examiner, Art Unit 2191 May 28, 2026 Application/Control Number: 18/565,154 Page 2 Art Unit: 2191 Application/Control Number: 18/565,154 Page 3 Art Unit: 2191 Application/Control Number: 18/565,154 Page 4 Art Unit: 2191 Application/Control Number: 18/565,154 Page 5 Art Unit: 2191 Application/Control Number: 18/565,154 Page 7 Art Unit: 2191 Application/Control Number: 18/565,154 Page 8 Art Unit: 2191 Application/Control Number: 18/565,154 Page 9 Art Unit: 2191 Application/Control Number: 18/565,154 Page 10 Art Unit: 2191 Application/Control Number: 18/565,154 Page 11 Art Unit: 2191 Application/Control Number: 18/565,154 Page 12 Art Unit: 2191 Application/Control Number: 18/565,154 Page 13 Art Unit: 2191 Application/Control Number: 18/565,154 Page 14 Art Unit: 2191 Application/Control Number: 18/565,154 Page 15 Art Unit: 2191 Application/Control Number: 18/565,154 Page 16 Art Unit: 2191 Application/Control Number: 18/565,154 Page 17 Art Unit: 2191
Prosecution Insights