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 .
DETAILED ACTION
1. This is a first non-final Office Action on the merits for application 18957278. Claims 1-20 are pending examination.
Claim Rejections - 35 USC § 101
2. 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 a judicial exception (i.e., a law of nature, a natural phenomenon, or an abstract idea) without significantly more.
Claim(s) 1 is/are drawn to method (i.e., a process), claim(s) 8 is/are drawn to a system (i.e., a machine/manufacture), and claim(s) 15 is/are drawn to non-transitory computer readable medium (i.e., a machine/manufacture). As such, claims 1, 8, and 15 is/are drawn to one of the statutory categories of invention.
Claims 1-20 are directed to generating conversion measurement diagnostics for contents for plurality of applications using diagnostic status request and common data layer associated with user applications. Specifically, claim(s) 1, 8, and 15 recite(s) requesting feature data associated with a particular account at a configured interval from a plurality of features, the feature data being indicative of interactions associated with content items; receiving the feature data at the configured interval; processing the feature data received to generate diagnostic signals according to predetermined logic for each of a plurality of available diagnostics for a plurality of applications; storing the diagnostic signals with corresponding timestamps within a common data layer; receiving a diagnostic status request associated with the particular account from a user via a first application of the plurality of applications; retrieving first diagnostic signals from the diagnostic signals stored within the common data layer in response to receiving the diagnostic status request, each of the first diagnostic signals being associated with one or more first diagnostics of the plurality of available diagnostics, the one or more first diagnostics being enabled for the first application; and providing a user interface for the first application to display a diagnostic status interface, the diagnostic status interface including a separate interface element for each of the one or more first diagnostics, each interface element indicating corresponding ones of the first diagnostic signals, which is grouped within the Methods Of Organizing Human Activity and is similar to the concept of (commercial or legal interactions including agreements in the form of contracts, legal obligations, advertising, marketing or sales activities or behaviors business relations) grouping of abstract ideas in prong one of step 2A of the Alice/Mayo test (See 2019 Revised Patent Subject Matter Eligibility Guidance, 84 Fed. Reg. 50, 52, 54 (January 7, 2019)). Accordingly, the claims recite an abstract idea (See pages 7, 10, Alice Corporation Pty. Ltd. v. CLS Bank International, et al., US Supreme Court, No. 13-298, June 19, 2014; 2019 Revised Patent Subject Matter Eligibility Guidance, 84 Fed. Reg. 50, 53-54 (January 7, 2019)).
The Claim limitations are listed under Methods Of Organizing Human Activity, and grouped as following:
requesting feature data associated with a particular account at a configured interval from a plurality of features, the feature data being indicative of interactions associated with content items; receiving the feature data at the configured interval; which is similar to the concept of (advertising, marketing or sales activities or behaviors business relations),
processing the feature data received to generate diagnostic signals according to predetermined logic for each of a plurality of available diagnostics for a plurality of applications; which is similar to the concept of (advertising, marketing or sales activities or behaviors business relations),
storing the diagnostic signals with corresponding timestamps within a common data layer; which is similar to the concept of (advertising, marketing or sales activities or behaviors business relations),
receiving a diagnostic status request associated with the particular account from a user via a first application of the plurality of applications; retrieving first diagnostic signals from the diagnostic signals stored within the common data layer in response to receiving the diagnostic status request, each of the first diagnostic signals being associated with one or more first diagnostics of the plurality of available diagnostics, the one or more first diagnostics being enabled for the first application; and providing a user interface for the first application to display a diagnostic status interface, the diagnostic status interface including a separate interface element for each of the one or more first diagnostics, each interface element indicating corresponding ones of the first diagnostic signals; which is similar to the concept of (advertising, marketing or sales activities or behaviors business relations).
This judicial exception is not integrated into a practical application because, when analyzed under prong two of step 2A of the Alice/Mayo test (See 2019 Revised Patent Subject Matter Eligibility Guidance, 84 Fed. Reg. 50, 54-55 (January 7, 2019)), the additional element(s) of the claim(s) such as intelligence engines, system, non-transitory computer-readable media, processors merely use(s) a computer as a tool to perform an abstract idea and/or generally link(s) the use of a judicial exception to a particular technological environment. Specifically, the intelligence engines, system, non-transitory computer-readable media, processors perform(s) the steps or functions of requesting feature data associated with a particular account at a configured interval from a plurality of features, the feature data being indicative of interactions associated with content items; receiving the feature data at the configured interval; processing the feature data received to generate diagnostic signals according to predetermined logic for each of a plurality of available diagnostics for a plurality of applications; storing the diagnostic signals with corresponding timestamps within a common data layer; receiving a diagnostic status request associated with the particular account from a user via a first application of the plurality of applications; retrieving first diagnostic signals from the diagnostic signals stored within the common data layer in response to receiving the diagnostic status request, each of the first diagnostic signals being associated with one or more first diagnostics of the plurality of available diagnostics, the one or more first diagnostics being enabled for the first application; and providing a user interface for the first application to display a diagnostic status interface, the diagnostic status interface including a separate interface element for each of the one or more first diagnostics, each interface element indicating corresponding ones of the first diagnostic signals. The use of a processor/computer as a tool to implement the abstract idea and/or generally linking the use of the abstract idea to a particular technological environment does not integrate the abstract idea into a practical application because it requires no more than a computer performing functions that correspond to acts required to carry out the abstract idea. The additional elements do not involve improvements to the functioning of a computer, or to any other technology or technical field (MPEP 2106.05(a)), the claims do not apply or use the abstract idea to effect a particular treatment or prophylaxis for a disease or medical condition (Vanda Memo), the claims do not apply the abstract idea with, or by use of, a particular machine (MPEP 2106.05(b)), the claims do not effect a transformation or reduction of a particular article to a different state or thing (MPEP 2106.05(c)), and the claims do not apply or use the abstract idea in some other meaningful way beyond generally linking the use of the abstract idea to a particular technological environment, such that the claim as a whole is more than a drafting effort designed to monopolize the exception (MPEP 2106.05(e) and Vanda Memo). Therefore, the claims do not, for example, purport to improve the functioning of a computer. Nor do they effect an improvement in any other technology or technical field. Accordingly, the additional elements do not impose any meaningful limits on practicing the abstract idea, and the claims are directed to an abstract idea.
The claim(s) does/do not include additional elements that are sufficient to amount to significantly more than the judicial exception because, when analyzed under step 2B of the Alice/Mayo test (See 2019 Revised Patent Subject Matter Eligibility Guidance, 84 Fed. Reg. 50, 52, 56 (January 7, 2019)), the additional element(s) of using a intelligence engines, system, non-transitory computer-readable media, processors to perform the steps amounts to no more than using a computer or processor to automate and/or implement the abstract idea of generating conversion measurement diagnostics for contents for plurality of applications using diagnostic status request and common data layer associated with user applications. As discussed above, taking the claim elements separately, the intelligence engines, system, non-transitory computer-readable media, processors, perform(s) the steps or functions of requesting feature data associated with a particular account at a configured interval from a plurality of features, the feature data being indicative of interactions associated with content items; receiving the feature data at the configured interval; processing the feature data received to generate diagnostic signals according to predetermined logic for each of a plurality of available diagnostics for a plurality of applications; storing the diagnostic signals with corresponding timestamps within a common data layer; receiving a diagnostic status request associated with the particular account from a user via a first application of the plurality of applications; retrieving first diagnostic signals from the diagnostic signals stored within the common data layer in response to receiving the diagnostic status request, each of the first diagnostic signals being associated with one or more first diagnostics of the plurality of available diagnostics, the one or more first diagnostics being enabled for the first application; and providing a user interface for the first application to display a diagnostic status interface, the diagnostic status interface including a separate interface element for each of the one or more first diagnostics, each interface element indicating corresponding ones of the first diagnostic signals. These functions correspond to the actions required to perform the abstract idea. Viewed as a whole, the combination of elements recited in the claims merely recite the concept of generating conversion measurement diagnostics for contents for plurality of applications using diagnostic status request and common data layer associated with user applications. Therefore, the use of these additional elements does no more than employ the computer as a tool to automate and/or implement the abstract idea. The use of a computer or processor to merely automate and/or implement the abstract idea cannot provide significantly more than the abstract idea itself (MPEP 2106.05(I)(A)(f) & (h)). Therefore, the claim is not patent eligible.
As for dependent claims 2-7, 9-14, and 16-20 further describe the abstract idea of generating conversion measurement diagnostics for contents for plurality of applications using diagnostic status request and common data layer associated with user applications. Claim(s) 2-7, 9-14, and 16-20 does/do not include additional elements that are sufficient to amount to significantly more than the judicial exception because, when analyzed under step 2B of the Alice/Mayo test (See 2019 Revised Patent Subject Matter Eligibility Guidance, 84 Fed. Reg. 50, 52, 56 (January 7, 2019)), the additional element(s) of using a intelligence engines, system, non-transitory computer-readable media to perform the steps amounts to no more than using a computer or processor to automate and/or implement the abstract idea of generating conversion measurement diagnostics for contents for plurality of applications using diagnostic status request and common data layer associated with user applications. As discussed above, taking the claim elements separately, the intelligence engines, system, non-transitory computer-readable media perform(s) the steps or functions of generating a recommendation for changing a setting associated with the first application based at least in part on the first diagnostic signals, wherein the diagnostic status interface further includes the recommendation; wherein the diagnostic status interface further includes a link to an interface for changing the setting; generating a historical trend for one or more of the first diagnostic signals based at least in part on the first diagnostic signals and the corresponding timestamps, wherein the diagnostic status interface further includes the historical trend; determining an impact score for each of the first diagnostic signals, each impact score indicating an effect that the respective first diagnostic signal has on the one or more first diagnostics; wherein retrieving the first diagnostic signals comprises referencing client configuration settings to determine the first diagnostics enabled for the first application; wherein the feature data includes at least one of offline conversion data, consent data, or tag data. These functions correspond to the actions required to perform the abstract idea. Viewed as a whole, the combination of elements recited in the claims merely recite the concept of generating conversion measurement diagnostics for contents for plurality of applications using diagnostic status request and common data layer associated with user applications. Therefore, the use of these additional elements does no more than employ the computer as a tool to automate and/or implement the abstract idea. The use of a computer or processor to merely automate and/or implement the abstract idea cannot provide significantly more than the abstract idea itself (MPEP 2106.05(I)(A)(f) & (h)). Therefore, the claim is not patent eligible.
Prior Art
3. In reference to independent claims 1, 8, and 15, the Office is unaware of any references that teach, individually or without an unreasonable combination of references, the combination of limitations steps found in the claims especially limitation that says: “processing the feature data to generate diagnostic signals according to predetermined logic for each of the plurality of available diagnostics for a plurality of application;
receiving a diagnostic status request associated with the particular account from a user via a first application of the plurality of applications;
retrieving first diagnostic signals from the diagnostic stored within the common data layer in response to receiving the diagnostic status request each of the first diagnostic signals being associated with one or more first diagnostics of the plurality of available diagnostics, the one or more first diagnostics being enabled for the first application and providing a user interface for the first application to display a diagnostic status interface, the diagnostic status interface including a separate interface element for each of the one or more first diagnostics, each interface element indicating corresponding ones of the first diagnostic signals.
providing a user interface for the first application to display a diagnostic status interface, the diagnostic status interface including a separate interface element for each of the one or more first diagnostics, each interface element indicating corresponding ones of the first diagnostic signals”. No reference found that would teach the above limitation(s).
The most relevant prior art identified by the Examiner is 20240357017. The reference teaches collecting usage data of plurality of applications not content and the usage data is analyzed to determine metrics associated with the plurality of different applications, with an interactive user interface dashboard providing the determined metrics is provided, but does not teach collecting usage data of conversion measurements diagnostics for different content applications of content items with interval from plurality of features. Therefore, it lacks the combination of claimed elements as claimed by the independent claims.
The most relevant prior art identified by the Examiner is 20100114714. The reference teaches tracking usage of the plurality of applications and monitor and record data as metric for the value an application provided to the user, but does not teach all the other features of the claim that collecting usage data of conversion measurements diagnostics for different content applications of content items with interval from plurality of features and storing data on the same layer then provide an interface that would display diagnostics enabled data of the first application to the user. Therefore, it lacks the combination of claimed elements as claimed by the independent claims.
All these references listed above teaches some of the features in the limitations of the claim but when combining it becomes not obvious and the references would teach the claim as a whole.
Examiner note: none of the references or combined references teach the combination of limitations of claim 1, 8, and 15 or no reference found that would teaches the combination of limitations of claim 1, 8, and 15, especially claim limitations: processing the feature data to generate diagnostic signals according to predetermined logic for each of the plurality of available diagnostics for a plurality of application;
receiving a diagnostic status request associated with the particular account from a user via a first application of the plurality of applications; retrieving first diagnostic signals from the diagnostic stored within the common data layer in response to receiving the diagnostic status request each of the first diagnostic signals being associated with one or more first diagnostics of the plurality of available diagnostics, the one or more first diagnostics being enabled for the first application and providing a user interface for the first application to display a diagnostic status interface, the diagnostic status interface including a separate interface element for each of the one or more first diagnostics, each interface element indicating corresponding ones of the first diagnostic signals; providing a user interface for the first application to display a diagnostic status interface, the diagnostic status interface including a separate interface element for each of the one or more first diagnostics, each interface element indicating corresponding ones of the first diagnostic signals, and which is an idea of generating conversion measurement diagnostics for different content applications based on feature data from multiple features that include requesting feature data associated with a particular account at a configured interval from a plurality of features, the feature data being indicative of interactions associated with content items by processing the feature data received to generate diagnostic signals according to predetermined logic for each of a plurality of available diagnostics for a plurality of applications, then storing the diagnostic signals with corresponding timestamps within a common data layer and then receiving a diagnostic status request associated with the particular account from a user via a first application of the plurality of applications and retrieving first diagnostic signals from the diagnostic signals stored within the common data layer in response to receiving the diagnostic status request, where each of the first diagnostic signals may be associated with one or more first diagnostics of the plurality of available diagnostics, and where the one or more first diagnostics may be enabled for the first application and providing a user interface for the first application to display a diagnostic status interface, where the diagnostic status interface may include a separate interface element for each of the one or more first diagnostics, and where each interface element may indicate corresponding ones of the first diagnostic signals.
When taken as a whole, the claims are not rendered obvious as the available prior art does not suggest or otherwise render obvious the noted features nor does the available prior art suggest or otherwise render obvious further modification of the evidence at hand. Such modifications would require substantial reconstruction relying solely on improper hindsight bias, and thus would not be obvious.
NPL Reference
4. The prior art made of record and not relied upon is considered pertinent to applicant's disclosure. The NPL “Mobile app conversion rate: benchmarks & best practices 2024” describes “Are you looking to increase the conversion rate of your mobile app?
If so, you’re not alone. Roughly 48% of all businesses are looking to connect and convert customers with
mobile apps. But many companies still struggle to make their apps more effective at boosting sales and
engagement. Luckily, there are some simple steps you can take to improve your mobile app conversions. In this UXCam guide, we'll cover best practices for improving your app's performance and provide benchmarks for measuring success. Ready? Let's dive in!”.
Pertinent Art
5. The prior art made of record and not relied upon is considered pertinent to applicant's disclosure. Reference#20180137252 teaches similar invention which describes determining the association with the monitoring device can be terminated, the data transfer process 200 dissociates the monitoring device (task 212). For example, once 7 days' worth of measurement data has been uploaded, the client application 108 may autonomously transmit or otherwise provide an indication to the monitoring device 102 that the measurement data has been uploaded to the server 114 and that the devices 102, 106 can be dissociated. In one or more embodiments, the client application 108 provides a study completed status indication to the monitoring device 102. In response to the study completed status indication, the firmware at the control module 122 causes the monitoring device 102 to establish a communications session with the client device 106 to upload or otherwise transmit diagnostic data to the client application 108. After uploading diagnostic data, the firmware at the control module 122 may be configured to automatically delete any measurement data, diagnostic data, or other patient-specific information from the memory 124 along with any identification information or pairing information corresponding to the client device 106, to thereby terminate communications with the client device 106.
Conclusion
Any inquiry concerning this communication or earlier communications from the examiner should be directed to TAREK ELCHANTI whose telephone number is (571) 272-9638. The examiner can normally be reached on Flex Mon - Thur 7-7:00 and Fri 7-4:00.
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, Waseem Ashraf can be reached on (571) 270-3948. 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). If you would like assistance from a USPTO Customer Service Representative or access to the automated information system, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000.
/TAREK ELCHANTI/Primary Examiner, Art Unit 3621B