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 .
This is in response to Application filed 09/30/24. Claims 1 – 7 have been examined and are pending. Application claims foreign priority to 113117056, filed 05/08/2024.
Claim Rejections - 35 USC § 101
35 U.S.C. 101 reads as follows:
Whoever invents or discovers any new and useful process, machine, manufacture, or composition of matter, or any new and useful improvement thereof, may obtain a patent therefor, subject to the conditions and requirements of this title.
Claims 1 – 7 are rejected under 35 U.S.C. 101 because the claimed invention is directed to non-statutory subject matter.
Regarding Step 1:
Claims 1 – 7 are directed to a method and recites steps of:
(a) creating a first super APP through an APP development tool,
(b) selecting the main APP through the APP development tool;
(c) in response to the main APP selected, creating an information transfer manager and a background application programming interface (API) executor in the main APP;
(d) with the main APP selected through the APP development tool, selecting the at least one slave APP through the APP development tool; creating a transmission path between the main APP and each of the slave APPs through the information transfer manager; and
(e) creating a call association between the main APP and a background API executable master file of each of the slave APPs through the background API executor.
Regarding Step 2A Prong 1:
Steps (a), (b), (c), (d) and (e) are mental processes (i.e., evaluation/judgement) which can be performed in the human mind or by a human by using pen and paper).
Regarding Step 2A Prong 2:
Claim 1 recites additional elements, i.e., building a super application (APP), adapted to utilize a processor to execute. However, they are recited at a high level of generality. Thus, the claims as a whole do not integrate the exception into a practical application.
Regarding Step 2B:
The identified additional elements do not amount significantly more than the judicial exception.
The same analysis applies here in 2B, i.e., simply planning a build of an app or creating an abstract intent to create and build associations between the App and a Background API does not integrate a judicial exception into a practical application.
Therefore, claims are ineligible.
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)(2) the claimed invention was described in a patent issued under section 151, or in an application for patent published or deemed published under section 122(b), in which the patent or application, as the case may be, names another inventor and was effectively filed before the effective filing date of the claimed invention.
Claim(s) 1 – 7 s/are rejected under 35 U.S.C. 102(a)(2) as being anticipated by Montes US 20040162103 A1.
Regarding claim 1, Montes anticipates a method of building a super application (APP), adapted to utilize a processor to execute the method, the method comprising:
creating a first super APP through an APP development tool, wherein the first super APP comprises a plurality of first APPs, and the plurality of first APPs comprise a main APP and at least one slave APP (0038 – 0044, shows a client main Application, a secondary application and a slave application), and creating the first super APP comprises:
selecting the main APP through the APP development tool (0033, see development process of client application also see 0038 shows main App/Application);
in response to the main APP selected, creating an information transfer manager and a background application programming interface (API) executor in the main APP [0124. See API, main and secondary application];
with the main APP selected through the APP development tool, selecting the at least one slave APP through the APP development tool [0038, see slave application];
creating a transmission path between the main APP and each of the slave APPs through the information transfer manager [Claim 21, shows the main app as well as client and destination applications and how it must be directed, i.e. same as path]; and
creating a call association between the main APP and a background API executable master file of each of the slave APPs through the background API executor [0042, shows main and slave applications as well as placing calls and see 0124 for API commands].
Regarding claim 2. the method according to claim 1, wherein creating the transmission path between the main APP and cach of the slave APPs through the information transfer manager comprises: creating a directory path corresponding to each of the slave APPs in the main APP through the information transfer manager; and storing each of the slave APPs in the directory path corresponding to each of the slave APPs, so that the information transfer manager stores data content transmitted individually by the main APP and each of the slave APPs through the directory path, and allows the main APP and each of the slave APPs to read the data content stored in the directory path [0036 – 0044, shows Main app, slave App and shows utilizing memory] .
Regarding claim 3, the method according to claim 2, wherein in a condition where the APP development tool starts the main APP, after the APP development tool selects the at least one slave APP, the method further comprising: adding an object corresponding to each of the slave APPs to a designated page of a first super APP, and associating the object with the directory path of each of the slave APPs [0038 – 0044].
Regarding claim 4, the method according to claim 1, wherein in a condition where the APP development tool selects the main APP, the method further comprising: selecting a second super APP through the APP development tool, wherein the second super APP comprises a plurality of second APPs, and one of the plurality of second APPs is a main APP of the second super APP; and importing the second super APP into the first super APP, so that the plurality of second APPs comprised in the second super APP become a slave APP of the first super APP, comprising: creating a transmission path between the main APP of the first super APP and each of the plurality of second APPs of the second super APP through the information transfer manager of the first super APP; and creating a call association between the main APP of the first super APP and a background API executable master file of each of the plurality of second APPs of the second super APP through the background API executor of the first super APP [0038 – 0044].
Regarding claim 5, the method according to claim 4, wherein creating the transmission path between the main APP of the first super APP and each of the plurality of second APPs of the second super APP through the information transfer manager of the first super APP comprises: creating a directory path corresponding to each of the plurality of second APPs in the main APP of the first super APP through the information transfer manager; and storing each of the plurality of second APPs in the directory path corresponding to each of the plurality of second APPs [0038 – 0044].
Regarding claim 6, the method according to claim 1, wherein the background API executor is configured to call the background API executable master file of each of the slave APPs [0038 – 0044].
Regarding claim 7, the method according to claim 1, further comprising: adding a backend management function to the first super APP through the APP development tool [0038 – 0044].
Correspondence Information
Any inquiry concerning this communication or earlier communications from the examiner should be directed to Chuck Kendall whose telephone number is 571-272-3698. The examiner can normally be reached on 10:00 am - 6:30pm.
If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Hyung Sough can be reached on 571-272-6799. 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 [0060 – 0080].
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).
/CHUCK O KENDALL/
Primary Examiner, Art Unit 2192
Prosecution Insights