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
This action is in response to communications filed on 11/14/2024. Accordingly, claims 1- 20 are pending.
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—in particular Independent claims 1, 11 & 16—are rejected under 35 U.S.C. 101 because the claimed invention is directed to an abstract idea without significantly more. The claims recite “executing, obtaining, processing and providing” data. These limitations, as drafted, are processes that, under their broadest reasonable interpretation, covers performance of the limitations in the mind. But for the processing circuity and memory language, the claims encompass a user simply comparing the collected data to a predetermined/configurable threshold in his/her mind. The mere nominal recitation of a generic bus, processor and memory does not take the claim limitation out of the mental processes grouping. Thus, the claims recite a mental process which is an abstract idea.
This judicial exception is not integrated into a practical application. The claims recite the elements of executing, obtaining, processing and providing, and that a generic computer performs these steps. The executing and obtaining steps are recited at a high level of generality (i.e., as a general means of receiving/transmitting and storing data for use in the processing and providing steps), and as such they amount to mere data gathering, which is a form of insignificant extra-solution activity. The processor that performs the executing and obtaining steps is recited at a high level of generality, and merely automates the processing and providing steps. Each of the additional limitations are no more than mere instructions to apply the exception using a generic computer component (the processor). The combination of these additional elements are no more than mere instructions to apply the exception using a generic computer component (the processor). Accordingly, even in combination, these additional elements do not integrate the abstract idea into a practical application. The claims are directed to an abstract idea.
The claims do not include additional elements that are sufficient to amount to significantly more than the judicial exception. As discussed with respect to Step 2A Prong Two, the additional elements in the claim amount to no more than mere instructions to apply the exception using a generic computer component. The same analysis applies here in 2B and does not provide an inventive concept.
For the executing, obtaining, processing and providing steps were considered extra-solution activity in Step 2A, this has been re-evaluated in Step 2B and determined to be well-understood, routine, conventional activity in the field. The background does not provide any indication that the processor is anything other than a generic, off-the-shelf computer component, and the Symantec, TLI, and OIP Techs. court decisions (MPEP 2106.05(d)(II)) indicate that mere collection or receipt of data over a network is a well‐understood, routine, and conventional function when it is claimed in a merely generic manner (as it is here). For these reasons, there is no inventive concept. The claim is not patent eligible.
As per claims 2-10, 12-15 and 17-20 all depend from claims 1, 11 and 16 and as such are rejected for having the same deficiencies as those dependent upon claims 1, 11 and 16.
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.
Claims 1- 20 are rejected under 35 U.S.C. 102(a)(1) as being anticipated by WO 2022/164874 A1 (hereinafter 874).
874 discloses:
1: A method comprising:
executing, by processing circuitry of a vehicle, a vehicle hardware abstraction layer and a vehicle composite signal framework, where the vehicle composite signal framework manages component signals obtained from a plurality of vehicle services of the vehicle (see 874 at least fig. 1-10 in particular fig. 1 and Abstract and Background; vehicle information extraction service [102], in-vehicle computing Devices [150], encoded vehicle communications Bus [138]);
obtaining, by the processing circuitry, a component signal from a vehicle service of the plurality of vehicle services (see 874 at least fig. 1-10 in particular figs. 1-5 & 13-14 and Abstract and Background; designer canvas [202], management console [210], in-vehicle computing Device(s) [150]);
processing, by the processing circuitry, the component signal into composite signal based on a mapping of the vehicle services to vehicle properties (see 874 at least fig. 1-10 in particular figs. 1-5 & 13-14 and Abstract and Background; designer canvas [202], management console [210], vehicle information extraction service [102]); and
providing, by the processing circuitry, the composite signal to an application executed by the processing circuitry (see 874 at least fig. 1-10 in particular figs. 1-5 & 13-14 and Abstract and Background; storage buffer [158], cloud services [610], vehicle information extraction service webpage [700], providing API for customer to access analyzed data [816]).
2: wherein processing the component signal into the composite signal includes: associating the composite signal with a vehicle property of a plurality of vehicle properties via a declarative mapping of the composite signal to the vehicle property (see 874 at least fig. 1-10 in particular figs. 1-5 & 13-14 and Abstract and Background).
3: wherein the service is a first service, wherein the component signal is a first component signal, and wherein associating the composite signal further comprises: associating a second composite signal with the vehicle property of the plurality of vehicle properties (see 874 at least fig. 1-10 in particular figs. 1-5 & 13-14 and Abstract and Background).
4: wherein the vehicle services include at least one component of the vehicle and are representative of functions of the at least one component (see 874 at least fig. 1-10 in particular figs. 1-5 & 13-14 and Abstract and Background).
5: wherein the component signal includes a plurality of component signals, and wherein processing the component signal into the composite signal further comprises: aggregating the plurality of component signals into the composite signal (see 874 at least fig. 1-10 in particular figs. 1-5 & 13-14 and Abstract and Background).
6: wherein processing the component signal includes processing the component signal to conform to a standard associated with the mapping to vehicle properties (see 874 at least fig. 1-10 in particular figs. 1-5 & 13-14 and Abstract and Background).
7: wherein providing the composite signal further comprises: providing the composite signal via an application programming interface to the application (see 874 at least fig. 1-10 in particular figs. 1-5 & 13-14 and Abstract and Background).
8: wherein the vehicle composite signal framework is agnostic of vehicle manufacturer (see 874 at least fig. 1-10 in particular figs. 1-5 & 13-14 and Abstract and Background).
9: wherein providing the composite further comprises: providing the composite signal in response to a query from the application (see 874 at least fig. 1-10 in particular figs. 1-5 & 13-14 and Abstract and Background).
10: wherein the component signal is pre-processed by a component of the vehicle prior to being obtained by the processing circuitry (see 874 at least fig. 1-10 in particular figs. 1-5 & 13-14 and Abstract and Background).
11: A vehicle, comprising:
memory; and processing circuitry in communication with the memory and configured to (see 874 at least fig. 1-10 in particular fig. 1 & 10 and Abstract and Background; vehicle information extraction service [102], in-vehicle computing Devices [150], encoded vehicle communications Bus [138] and computer system [1000], system memory [1020]):
execute a vehicle hardware abstraction layer and a vehicle composite signal framework, where the vehicle composite signal framework manages component signals obtained from a plurality of vehicle services of the vehicle (see 874 at least fig. 1-10 in particular fig. 1 and Abstract and Background; vehicle information extraction service [102], in-vehicle computing Devices [150], encoded vehicle communications Bus [138]);
obtain a component signal from a vehicle service of the plurality of vehicle services (see 874 at least fig. 1-10 in particular figs. 1-5 & 13-14 and Abstract and Background; designer canvas [202], management console [210], in-vehicle computing Device(s) [150]);
process the component signal into composite signal based on a mapping of the vehicle services to vehicle properties (see 874 at least fig. 1-10 in particular figs. 1-5 & 13-14 and Abstract and Background; designer canvas [202], management console [210], analyze data and vehicle information extraction service [102]); and
provide the composite signal to an application executed by the processing circuitry (see 874 at least fig. 1-10 in particular figs. 1-5 & 13-14 and Abstract and Background; storage buffer [158], cloud services [610], vehicle information extraction service webpage [700], providing API for customer to access analyzed data [816]).
12: wherein to process the component signal into the composite signal, the processing circuitry is further configured to: associate the composite signal with a vehicle property of a plurality of vehicle properties via a declarative mapping of the composite signal to the vehicle property (see 874 at least fig. 1-10 in particular figs. 1-5 & 13-14 and Abstract and Background).
13: wherein the service is a first service, wherein the component signal is a first component signal and wherein to associate the component signal, the processing circuitry is further configured to: associate a second composite signal with the vehicle property of the plurality of vehicle properties (see 874 at least fig. 1-10 in particular figs. 1-5 & 13-14 and Abstract and Background).
14: wherein the vehicle services include at least one component of the vehicle and are representative of functions of the at least one component (see 874 at least fig. 1-10 in particular figs. 1-5 & 13-14 and Abstract and Background).
15: wherein the component signal includes a plurality of component signals, and wherein to process the component signal to the composite signal, the processing circuitry is further configured to: aggregate the plurality of component signals into the composite signal (see 874 at least fig. 1-10 in particular figs. 1-5 & 13-14 and Abstract and Background).
16: A non-transitory computer-readable storage media encoded with instructions that, when executed, cause at least one processor of a vehicle computing device to (see 874 at least fig. 1-10 in particular fig. 1 and Abstract and Background; vehicle information extraction service [102], in-vehicle computing Devices [150], encoded vehicle communications Bus [138]):
execute a vehicle hardware abstraction layer and a vehicle composite signal framework, where the vehicle composite signal framework manages component signals obtained from a plurality of vehicle services of the vehicle (see 874 at least fig. 1-10 in particular fig. 1 and Abstract and Background; vehicle information extraction service [102], in-vehicle computing Devices [150], encoded vehicle communications Bus [138]);
obtain a component signal from a vehicle service of the plurality of vehicle services (see 874 at least fig. 1-10 in particular figs. 1-5 & 13-14 and Abstract and Background; designer canvas [202], management console [210], in-vehicle computing Device(s) [150]);
process the component signal into composite signal based on a mapping of the vehicle services to vehicle properties (see 874 at least fig. 1-10 in particular figs. 1-5 & 13-14 and Abstract and Background; designer canvas [202], management console [210], analyze data and vehicle information extraction service [102]); and
provide the composite signal to an application executed by the at least one processor (see 874 at least fig. 1-10 in particular figs. 1-5 & 13-14 and Abstract and Background; storage buffer [158], cloud services [610], vehicle information extraction service webpage [700], providing API for customer to access analyzed data [816]).
17: wherein to process the component signal into the composite signal, the instructions further cause the at least one processor to: associate the composite signal with a vehicle property of a plurality of vehicle properties via a declarative mapping of the composite signal to the vehicle property (see 874 at least fig. 1-10 in particular figs. 1-5 & 13-14 and Abstract and Background).
18: wherein the service is a first service, wherein the component signal is a first component signal and wherein to associate the component signal, the instructions are further configured to cause the at least one processor to: associate a second composite signal with the vehicle property of the plurality of vehicle properties (see 874 at least fig. 1-10 in particular figs. 1-5 & 13-14 and Abstract and Background).
19: wherein the vehicle services include at least one component of the vehicle and are representative of functions of the at least one component (see 874 at least fig. 1-10 in particular figs. 1-5 & 13-14 and Abstract and Background).
20: wherein the component signal includes a plurality of component signals, and wherein to process the component signal to the composite signal, the instructions are further configured to cause the at least one processor to: aggregate the plurality of component signals into the composite signal (see 874 at least fig. 1-10 in particular figs. 1-5 & 13-14 and Abstract and Background).
Conclusion
Any inquiry concerning this communication or earlier communications from the examiner should be directed to MACEEH ANWARI whose telephone number is 571-272-7591. The examiner can normally be reached on 9-9:30.
If attempts to reach the examiner by telephone are unsuccessful, the examiner’s supervisor, Angela Ortiz can be reached on 571-272-1206. 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.
MACEEH . ANWARI
Primary Examiner
Art Unit 3663
/MACEEH ANWARI/ Primary Examiner, Art Unit 3663
