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/29/23. Claims 1 – 20 has been examined and is pending.
Claim Rejections - 35 USC § 112
The following is a quotation of 35 U.S.C. 112(b):
(b) CONCLUSION.—The specification shall conclude with one or more claims particularly pointing out and distinctly claiming the subject matter which the inventor or a joint inventor regards as the invention.
The following is a quotation of 35 U.S.C. 112 (pre-AIA ), second paragraph:
The specification shall conclude with one or more claims particularly pointing out and distinctly claiming the subject matter which the applicant regards as his invention.
Claims 19-20 are rejected under 35 U.S.C. 112(b) or 35 U.S.C. 112 (pre-AIA ), second paragraph, as being indefinite for failing to particularly point out and distinctly claim the subject matter which the inventor or a joint inventor (or for applications subject to pre-AIA 35 U.S.C. 112, the applicant), regards as the invention.
Claim 19, line 16, it is unclear whether “the mobile application” refers to “a mobile application” in line 5 or lines 12-13 of the claim. For the examination purposes, “a mobile application” in lines 12-13 will be treated as --the mobile application--.
Claim 20 depends on the rejected claim and inherit the same issue.
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-20 are rejected under 35 U.S.C. 101 because the claimed invention is directed to an abstract idea without significantly more.
Regarding Step 1:
Claims 1-9 are directed to a method and claims 10-18 are directed to a medium and claims 19 and 20 are directed a system. Thus, they fall into the statutory categories.
Claim 1 (clams 9 and 19 recite similar limitations) recites steps of:
receiving a product flow at a healing module;
receiving, at the healing module, a signal from one or more user devices executing a mobile application including the product flow;
determining, by the healing module, a health status of the product flow from the signal; and
in response to the health status of the product flow indicating a problem with a component of the mobile application, performing one or more actions by the healing module to heal the product flow.
Regarding Step 2A Prong 1:
Steps (a), (b), and (c) are mental processes (i.e., collecting information/ 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., step (d), a mobile application, a healing module, and a component. Claim 11 further recites storage medium, processors, and a computing system. Claim 19 further recites platform, user device, and networked communication. However, step (d) is insignificant extra-solution activity. Further, a mobile application, a healing module, a component storage medium, processors, a computing system, platform, user device, and networked communication 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 in step 2A, Prong 2 do not amount significantly more than the judicial exception.
Recited limitations in claims 2-9, 11-18, and 20 do not overcome 101 rejection based on abstract idea. Further, as disclosed by applicant (e.g., see paragraph [0003]), the claimed invention can be done manually.
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)(1) the claimed invention was patented, described in a printed publication, or in public use, on sale, or otherwise available to the public before the effective filing date of the claimed invention.
Claim(s) 1 - 20 is/are rejected under 35 U.S.C. 102(a)(1) as being anticipated by Wang et al. US 12430165 B2.
Regarding claims 1, and 10, Wang anticipates A method/non-transitory computer readable storage medium comprising instructions of healing a product flow for a mobile application, comprising:
receiving a product flow at a healing module (11:33 – 45, see upon receiving information and health monitor);
receiving, at the healing module, a signal from one or more user devices executing a mobile application including the product flow (11:33 – 45, see “…based on received execution times tracked by a plugin health monitor…” also 2:10 – 25, shows the one or more devices, see client device);
determining, by the healing module, a health status of the product flow from the signal (2:43 – 45, see health status);
and in response to the health status of the product flow indicating a problem with a component of the mobile application, performing one or more actions by the healing module to heal the product flow (2:23 – 25, see, “… plugin health monitor that collectively enable the client device and/or client agent to troubleshoot various problems and reduce a number of instances in which the client agent is shut down unnecessarily…” i.e. one or more actions by the healing module.
Regarding claims 2 and 11, the method of claim 1, wherein the healing module determines a subflow of the product flow related to the component of the mobile application and heals the product flow by redirecting the product flow from the subflow to a different subflow for the component (11:7 – 17, shows workflow and report plugin, and in 11:25 – 31, also see health monitors and report usage).
Regarding claims 3 and 12, the method of claim 1, wherein the product flow includes one or more flag points having analytics logging (16:20 – 27, see “exceed an acceptable threshold” Examiner interprets this action as equivalent functionality to flag points as exceeding the threshold would creating an action causing the health monitor to react); and the component is disabled at a flag point of the one or more flag points in response to the health status of the product flow indicating a problem related to the flag point. (16:25 – 35, see health monitor and disable or discontinue specific plugins).
Regarding claims 4 and 13, the method of claim 1, wherein the mobile application is reviewed by and published on a mobile application distribution platform (4:18 – 27, shows a distributed computing system, with a collection of devices, and 4:32 – 35, shows mobile devices. 6:23 – 27, regarding publishing, shows outputting to agent management systems).
Regarding claims 5 and 14, the method of claim 1, further comprising receiving one or more threshold values during configuration of the product flow and updating the threshold values based on the signal received from the mobile application(16:20 – 27, see “exceed an acceptable threshold”).
Regarding claims 6 and 15, the method of claim 1, wherein the healing module comprises a collection of stability rules for the product flow (3:34 – 45, see policy parameters for rules).
Regarding claims 7 and 16, the method of claim 1, wherein the product flow is one of a plurality of product flows, the signal is from a plurality of mobile devices executing a plurality of mobile applications including the plurality of product flows, and the method further comprises determining a health status of the plurality of product flows from the signal (5:50 – 60, see health status).
Regarding claims 8 and 17, the method of claim 7, wherein the signal comprises real-time metrics for the plurality of mobile applications, and determining the health status of the plurality of product flows comprises detecting an anomaly in the real-time metrics (2:20 – 25, shows troubleshooting various problems).
Regarding claims 9 and 18, the method of claim 1, further comprising generating an alert in response to the health status of the product flow indicating the problem metrics (2:20 – 25, shows troubleshooting various problems).
Regarding claim 19, a system comprising:
a mobile application distribution platform; a healing module; (4:18 – 27, shows a distributed computing system, with a collection of devices, and 4:32 – 35, shows mobile devices. 6:23 – 27);
a user device in networked communication with the healing module, the user device executing a mobile application received from the mobile application distribution platform, and the mobile application including a product flow (5:18 – 29, see client devices and network as well as agent health and update system);
wherein the healing module comprises a memory having executable instructions stored thereon (3:20 – 25, shows health monitors with CPU and memory); and
one or more processors configured to execute the executable instructions to cause the healing module to: receive the product flow; receive a signal from one or more user devices executing a mobile application including the product flow (11:13 – 18, shows associated agents and work flow also see 11:33 – 45, for “…based on received execution times tracked by a plugin health monitor…” also 2:10 – 25, shows the one or more devices, see client device);
determine a health status of the product flow from the signal; and in response to the health status of the product flow indicating a problem with a component of the mobile application, perform one or more actions to heal the product flow (2:23 – 25, see, “… plugin health monitor that collectively enable the client device and/or client agent to troubleshoot various problems and reduce a number of instances in which the client agent is shut down unnecessarily…” i.e. one or more actions by the healing module and 2:43 – 45, for Health status).
Regarding claim 20, the system of claim 19, wherein the user device is a user device of a plurality of user devices executing a plurality of mobile applications received from a plurality of platforms, the plurality of mobile applications includes a plurality of product flows validated by the healing module, and the healing module receives one or more signals from the plurality of user devices (13:32 – 50, shows health monitor and policy violations regarding the client devices).
Conclusion
The prior art made of record and not relied upon is considered pertinent to applicant's disclosure. US 20190132351 A1 discloses a similar limitation of health status monitor in a networked environment and utilizing dataflows.
Correspondence Information
Any comments considered necessary by applicant must be submitted no later than the payment of the issue fee and, to avoid processing delays, should preferably accompany the issue fee. Such submissions should be clearly labeled “Comments on Statement of Reasons for Allowance.”
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. 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