DETAILED ACTION
In the response filed May 14, 2026, the Applicant amended claims 1, 8, 19, 21, and 22. Claims 1-11, 13-15, and 17-22, are pending in the current application.
Notice of 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 .
Response to Arguments
Applicant’s arguments for claims 1-11, 13-15, and 17-22, with respect to the 35 U.S.C. 101 rejection have been considered but are unpersuasive. Applicant argues that the claims integrate the judicial exception into a practical application. Examiner respectfully disagrees.
The claims do not explicitly disclose any form of security or security measures. The recited additional elements of “generating an onboarding hyperlink, wherein the onboarding hyperlink is uniquely associated with the subject data object;” “transmitting, from the service onboarding system to the user device via a user communication channel associated with the user communication channel data, a custom onboarding message comprising the onboarding hyperlink associated with the subject data object;” “causing rendering of a graphical user interface at a user device in response to receiving a first indication based on interaction with (i) an onboarding hyperlink via the user device or (ii) a machine-readable symbology;” (claims 1, 19, and 21), simply append insignificant extra-solution activity to the judicial exception, (e.g., mere pre-solution activity, such as data gathering, in conjunction with an abstract idea; mere post-solution activity in conjunction with an abstract idea). The term “extra-solution activity” is understood as activities incidental to the primary process or product that are merely a nominal or tangential addition to the claim. The recited additional elements are deemed “extra-solution” because they are merely presenting data/information to a user. These limitations do not impose any meaningful limits on practicing the abstract idea, and therefore do/does not integrate the abstract idea into a practical application. See MPEP § 2106.05(g).
The claims as described above, even if considered to be an “additional” element for the purpose of the eligibility analysis, would simply append insignificant extra-solution activity to the judicial exception, (e.g., mere post-solution activity in conjunction with an abstract idea).
These additional elements, taken individually or in combination, additionally amount to well-understood, routine and conventional activities previously known to the industry, specified at a high level of generality, appended to the judicial exception. These additional elements, taken individually or in combination, are well-understood, routine and conventional to those in the field of user interfaces. These limitations therefore do not qualify as “significantly more.” See MPEP § 2106.05(d). This conclusion is based on a factual determination. The determination that receiving data/messages over a network is well-understood, routine, and conventional is supported by Symantec, 838 F.3d at 1321, 120 USPQ2d at 1362; TLI Communications LLC v. AV Auto. LLC, 823 F.3d 607, 610, 118 USPQ2d 1744, 1745 (Fed. Cir. 2016); OIP Techs., Inc., v. Amazon.com, Inc., 788 F.3d 1359, 1363, 115 USPQ2d 1090, 1093 (Fed. Cir. 2015); buySAFE, Inc. v. Google, Inc., 765 F.3d 1350, 1355, 112 USPQ2d 1093, 1096 (Fed. Cir. 2014), and MPEP 2106.05(d)(II), which note the well-understood, routine, conventional nature of receiving data/messages over a network.
Viewing the additional limitations in combination also shows that they fail to ensure the claims amount to significantly more than the abstract idea. When considered as an ordered combination, the additional components of the claims add nothing that is not already present when considered separately, and thus simply append the abstract idea with words equivalent to “apply it” on a generic computer and/or mere instructions to implement the abstract idea on a generic computer, generally link the abstract idea to a particular technological environment or field of use, append the abstract idea with insignificant extra solution activity associated with the implementation of the judicial exception, (e.g., mere data gathering, post-solution activity), and appended with well-understood, routine and conventional activities previously known to the industry. Applicant’s arguments remain unpersuasive. The 35 U.S.C. 101 rejection is hereby maintained.
Applicant’s arguments for claims 1-11, 13-15, and 17-22, with respect to the 35 U.S.C. 103 rejection have been considered but are moot because the arguments do not apply to the combination of references being used in the current rejection. To clarify, Applicant argues that allowability is not destroyed by amending the claims and omitting certain limitations of the claim. Examiner respectfully disagrees. The complete limitations of claim 8 include “wherein the first indication is triggered in response to interaction with the onboarding hyperlink by the user via the user device,” and incorporation of this limitation would require the limitations of independent claims 1, 19, and 21, to require receiving a first indication based on interaction with the onboarding hyperlink by the user via the user device and subsequently claimed steps based on the interaction with the onboarding hyperlink via the user device. However, the claims do not incorporate such limitations and are still written to include an indication based on an interaction with a machine-readable symbology. Here, under broadest reasonable interpretation, the claim requires a graphical user interface at a user device in response to receiving a first indication based on interaction with (i) an onboarding hyperlink via the user device or (ii) a machine-readable symbology. Neuhaeuser still teaches causing rendering of a graphical user interface at a user device in response to receiving a first indication based on interaction with (i) an onboarding hyperlink via the user device or (ii) a machine-readable symbology (Par. [0069], The HMI guides the customer to the management server touchpoint, e.g., by showing a QR code which opens the management server app or the management server web portal). As such, the 35 U.S.C. 103 rejection is hereby maintained.
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-11, 13-15, and 17-22 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.
Step 1: Claims 1-11, 13-15, 17, 18, 21, and 22, are drawn to processes and claims 19 and 20 are drawn to a device, each of which is within the four statutory categories (e.g., a process, a machine). (Step 1: YES).
Step 2A – Prong One: In prong one of step 2A, the claims are analyzed to evaluate whether they recite a judicial exception.
Claim 1 (representative of claim 19) recites/describes the following steps:
“receiving, … acquisition data comprising the subject information associated with a subject, wherein the acquisition data further comprises user information associated with a user, the user information comprising user communication channel data usable for transmitting information…;”
“receiving telematics data associated with the subject;”
“associating the telematics data with a subject data object that comprises at least a portion of the subject information;”
“…receiving a first indication based on interaction with (i) the onboarding hyperlink via the user device or (ii) a machine-readable symbology embodying the onboarding hyperlink;”
“…display at least a portion of the telematics data … while the subject data object is pending onboarding, such that the acquisition data is configured to facilitate access to the telematics data… while the subject data object is pending onboarding,”
“…display a glovebox interface, wherein the glovebox interface is configured to (i) display at least a portion of the subject information associated with the subject and/or (ii) display at least one icon or menu item that causes the graphical user interface to display at least a portion of the subject information associated with the subject when selected by the user of the user device.”
These steps, under broadest reasonable interpretation, describe or set-forth receiving, associating, and displaying telematics data to a user for customer onboarding, which amounts to commercial or legal interactions (including agreements in the form of contracts; legal obligations; advertising, marketing or sales activities or behaviors; business relations). These limitations therefore fall within the “certain methods of organizing human activity” subject matter grouping of abstract ideas.
Claim 21 recites/describes the following steps:
“receiving, … acquisition data comprising the subject information associated with a subject, wherein the acquisition data further comprises user information associated with a user, the user information comprising user communication channel data usable for transmitting information…;”
“receiving telematics data associated with the subject;”
“associating the telematics data with a subject data object that comprises at least a portion of the subject information;”
“…receiving a first indication based on interaction…”
“…display at least a portion of the telematics data … while the subject data object is pending onboarding, such that the acquisition data is configured to facilitate access to the telematics data… while the subject data object is pending onboarding,”
“…generating a data slug and associating the data slug with the subject data object to cause the subject data object to be associated with the indication of pending onboarding, wherein removing the indication of pending onboarding comprises removing the data slug following completion of onboarding.”
These steps, under broadest reasonable interpretation, describe or set-forth receiving, associating, and displaying telematics data to a user for customer onboarding and determining a completion of onboarding, which amounts to commercial or legal interactions (including agreements in the form of contracts; legal obligations; advertising, marketing or sales activities or behaviors; business relations). These limitations therefore fall within the “certain methods of organizing human activity” subject matter grouping of abstract ideas.
As such, the Examiner concludes that claim 1 recites an abstract idea (Step 2A – Prong One: YES).
Dependent claim 3 recites the additional element “causing rendering, via the user device in response to receiving the second indication, of a user onboarding interface comprising a set of user information input fields,” which is analyzed in the steps below.
Dependent claim 5 recites the additional elements “a communication channel that is associated with the user communication channel data,” “presenting, via the provider system, the machine-readable symbology, wherein the first indication is triggered in response to the user device scanning the machine-readable symbology,” which is analyzed in the steps below.
Dependent claim 6 recites the additional element “wherein the machine-readable symbology is presented via the provider system by causing the provider system to render a user interface comprising the machine-readable symbology,” which is analyzed in the steps below.
Dependent claim 7 recites the additional element “wherein the machine-readable symbology is presented via the provider system by causing the provider system to print a physical medium comprising the machine-readable symbology,” which is analyzed in the steps below.
Dependent claim 9 recites the additional elements, “a cellular communication channel associated with the mobile phone number,” which is analyzed in the steps below.
Dependent claim 10 recites the additional elements, “in a circumstance where the service application is determined not to be installed to the user device, access at least one application distribution platform to install the service application to the user device; and in a circumstance where the service application is determined to be installed to the user device, initiating the service application based on the subject data object,” which is analyzed in the steps below.
Dependent claim 13 recites the additional element “a first set of application programming interfaces,” “a second set of application programming interfaces,” which is analyzed in the steps below.
Each of the remaining depending claims 2, 4, 8, 11, 14, 15, 17, 18, 20, and 22, likewise recite/describe these steps (by incorporation - and therefore also recite limitations that fall within this subject matter grouping of abstract ideas), and these claims are therefore determined to recite an abstract idea under the same analysis. Any elements recited in a dependent claim that are not specifically identified/addressed by the Examiner under step 2A (prong two) or step 2B of this analysis shall be understood to be an additional part of the abstract idea recited by that particular claim.
Step 2A – Prong Two:
The claims recite the additional elements/limitations of: “a service onboarding system from a provider system,” “a user device that is associated with the user;” “a user communication channel associated with the user communication channel data,” “a graphical user interface at a user device,” (claim 1); “an apparatus for pre-onboarding user access control to subject information, the apparatus comprising at least one processor and at least one non-transitory memory,” “a user device that is associated with the user;” “a user communication channel associated with the user communication channel data,” “a graphical user interface at a user device,” (claim 19); “a service onboarding system from a provider system,” “a user device that is associated with the user;” “a user communication channel associated with the user communication channel data,” “a graphical user interface at a user device,” (claim 21).
The claims further recite the additional elements/limitations of: “a communication channel that is associated with the user communication channel data,” (claim 5); “a user communication channel,” (claim 8); “a cellular communication channel associated with the mobile phone number,” (claim 9); and “a first set of application programming interfaces,” “a second set of application programming interfaces,” (claim 13).
The requirement to execute the claimed steps/functions using “a service onboarding system from a provider system,” “a user device that is associated with the user;” “a user communication channel associated with the user communication channel data,” “a graphical user interface at a user device,” (claim 1); “an apparatus for pre-onboarding user access control to subject information, the apparatus comprising at least one processor and at least one non-transitory memory,” “a user device that is associated with the user;” “a user communication channel associated with the user communication channel data,” “a graphical user interface at a user device,” (claim 19); “a service onboarding system from a provider system,” “a user device that is associated with the user;” “a user communication channel associated with the user communication channel data,” “a graphical user interface at a user device,” (claim 21); “a communication channel that is associated with the user communication channel data,” (claim 5); “a user communication channel,” (claim 8); “a cellular communication channel associated with the mobile phone number,” (claim 9); and “a first set of application programming interfaces,” “a second set of application programming interfaces,” (claim 13), is equivalent to adding the words “apply it” on a generic computer and/or mere instructions to implement the abstract idea on a generic computer. These limitations do not impose any meaningful limits on practicing the abstract idea, and therefore do/does not integrate the abstract idea into a practical application. See § MPEP 2106.05(f).
The claims also recite the additional elements/limitations of: “generating an onboarding hyperlink, wherein the onboarding hyperlink is uniquely associated with the subject data object;” “transmitting, from the service onboarding system to the user device via a user communication channel associated with the user communication channel data, a custom onboarding message comprising the onboarding hyperlink associated with the subject data object;” “causing rendering of a graphical user interface at a user device in response to receiving a first indication based on interaction with (i) an onboarding hyperlink via the user device or (ii) a machine-readable symbology;” (claims 1, 19, and 21).
The claims further recite the additional elements/limitations of: “causing rendering, via the user device in response to receiving the second indication, of a user onboarding interface comprising a set of user information input fields,” (claim 3); “presenting, via the provider system, the machine-readable symbology, wherein the first indication is triggered in response to the user device scanning the machine-readable symbology,” (claim 5); “wherein the machine-readable symbology is presented via the provider system by causing the provider system to render a user interface comprising the machine-readable symbology,” (claim 6); “wherein the machine-readable symbology is presented via the provider system by causing the provider system to print a physical medium comprising the machine-readable symbology,” (claim 7); “in a circumstance where the service application is determined not to be installed to the user device, access at least one application distribution platform to install the service application to the user device; and in a circumstance where the service application is determined to be installed to the user device, initiating the service application based on the subject data object,” (claim 10).
The recited additional elements of “generating an onboarding hyperlink, wherein the onboarding hyperlink is uniquely associated with the subject data object;” “transmitting, from the service onboarding system to the user device via a user communication channel associated with the user communication channel data, a custom onboarding message comprising the onboarding hyperlink associated with the subject data object;” “causing rendering of a graphical user interface at a user device in response to receiving a first indication based on interaction with (i) an onboarding hyperlink via the user device or (ii) a machine-readable symbology;” (claims 1, 19, and 21); “causing rendering, via the user device in response to receiving the second indication, of a user onboarding interface comprising a set of user information input fields,” (claim 3); “presenting, via the provider system, the machine-readable symbology, wherein the first indication is triggered in response to the user device scanning the machine-readable symbology,” (claim 5); “wherein the machine-readable symbology is presented via the provider system by causing the provider system to render a user interface comprising the machine-readable symbology,” (claim 6); “wherein the machine-readable symbology is presented via the provider system by causing the provider system to print a physical medium comprising the machine-readable symbology,” (claim 7); “in a circumstance where the service application is determined not to be installed to the user device, access at least one application distribution platform to install the service application to the user device; and in a circumstance where the service application is determined to be installed to the user device, initiating the service application based on the subject data object,” (claim 10), simply append insignificant extra-solution activity to the judicial exception, (e.g., mere pre-solution activity, such as data gathering, in conjunction with an abstract idea; mere post-solution activity in conjunction with an abstract idea). The term “extra-solution activity” is understood as activities incidental to the primary process or product that are merely a nominal or tangential addition to the claim. The recited additional elements are deemed “extra-solution” because they are merely presenting data/information to a user. These limitations do not impose any meaningful limits on practicing the abstract idea, and therefore do/does not integrate the abstract idea into a practical application. See MPEP § 2106.05(g).
Remaining dependent claims 2, 4, 8, 11, 14, 15, 17, 18, 20, and 22, either recite the same additional elements as noted above or fail to recite any additional elements (in which case, note prong one analysis as set forth above – those claims are further part of the abstract idea as identified by the Examiner for each respective dependent claim).
The Examiner has therefore determined that the additional elements, or combination of additional elements, do not integrate the abstract idea into a practical application. Accordingly, the claims are directed to an abstract idea (Step 2A – Prong two: NO).
Step 2B:
As discussed above in “Step 2A – Prong 2,” the requirement to execute the claimed steps/functions using “a service onboarding system from a provider system,” “a user device that is associated with the user;” “a user communication channel associated with the user communication channel data,” “a graphical user interface at a user device,” (claim 1); “an apparatus for pre-onboarding user access control to subject information, the apparatus comprising at least one processor and at least one non-transitory memory,” “a user device that is associated with the user;” “a user communication channel associated with the user communication channel data,” “a graphical user interface at a user device,” (claim 19); “a service onboarding system from a provider system,” “a user device that is associated with the user;” “a user communication channel associated with the user communication channel data,” “a graphical user interface at a user device,” (claim 21); “a communication channel that is associated with the user communication channel data,” (claim 5); “a user communication channel,” (claim 8); “a cellular communication channel associated with the mobile phone number,” (claim 9); and “a first set of application programming interfaces,” “a second set of application programming interfaces,” (claim 13), is equivalent to adding the words “apply it” on a generic computer and/or mere instructions to implement the abstract idea on a generic computer. These limitations therefore do not qualify as “significantly more.” See MPEP § 2106.05(f).
As discussed above in “Step 2A – Prong 2”, the recited additional elements of “generating an onboarding hyperlink, wherein the onboarding hyperlink is uniquely associated with the subject data object;” “transmitting, from the service onboarding system to the user device via a user communication channel associated with the user communication channel data, a custom onboarding message comprising the onboarding hyperlink associated with the subject data object;” “causing rendering of a graphical user interface at a user device in response to receiving a first indication based on interaction with (i) an onboarding hyperlink via the user device or (ii) a machine-readable symbology;” (claims 1, 19, and 21); “causing rendering, via the user device in response to receiving the second indication, of a user onboarding interface comprising a set of user information input fields,” (claim 3); “presenting, via the provider system, the machine-readable symbology, wherein the first indication is triggered in response to the user device scanning the machine-readable symbology,” (claim 5); “wherein the machine-readable symbology is presented via the provider system by causing the provider system to render a user interface comprising the machine-readable symbology,” (claim 6); “wherein the machine-readable symbology is presented via the provider system by causing the provider system to print a physical medium comprising the machine-readable symbology,” (claim 7); “in a circumstance where the service application is determined not to be installed to the user device, access at least one application distribution platform to install the service application to the user device; and in a circumstance where the service application is determined to be installed to the user device, initiating the service application based on the subject data object,” (claim 10), even if considered to be an “additional” element for the purpose of the eligibility analysis, would simply append insignificant extra-solution activity to the judicial exception, (e.g., mere post-solution activity in conjunction with an abstract idea).
These additional elements, taken individually or in combination, additionally amount to well-understood, routine and conventional activities previously known to the industry, specified at a high level of generality, appended to the judicial exception. These additional elements, taken individually or in combination, are well-understood, routine and conventional to those in the field of user interfaces. These limitations therefore do not qualify as “significantly more.” See MPEP § 2106.05(d). This conclusion is based on a factual determination. The determination that receiving data/messages over a network is well-understood, routine, and conventional is supported by Symantec, 838 F.3d at 1321, 120 USPQ2d at 1362; TLI Communications LLC v. AV Auto. LLC, 823 F.3d 607, 610, 118 USPQ2d 1744, 1745 (Fed. Cir. 2016); OIP Techs., Inc., v. Amazon.com, Inc., 788 F.3d 1359, 1363, 115 USPQ2d 1090, 1093 (Fed. Cir. 2015); buySAFE, Inc. v. Google, Inc., 765 F.3d 1350, 1355, 112 USPQ2d 1093, 1096 (Fed. Cir. 2014), and MPEP 2106.05(d)(II), which note the well-understood, routine, conventional nature of receiving data/messages over a network.
Viewing the additional limitations in combination also shows that they fail to ensure the claims amount to significantly more than the abstract idea. When considered as an ordered combination, the additional components of the claims add nothing that is not already present when considered separately, and thus simply append the abstract idea with words equivalent to “apply it” on a generic computer and/or mere instructions to implement the abstract idea on a generic computer, generally link the abstract idea to a particular technological environment or field of use, append the abstract idea with insignificant extra solution activity associated with the implementation of the judicial exception, (e.g., mere data gathering, post-solution activity), and appended with well-understood, routine and conventional activities previously known to the industry.
Remaining dependent claims 2, 4, 8, 11, 14, 15, 17, 18, 20, and 22, either recite the same additional elements as noted above or fail to recite any additional elements (in which case, note prong one analysis as set forth above – those claims are further part of the abstract idea as identified by the Examiner for each respective dependent claim).
The Examiner has therefore determined that no additional element, or combination of additional claims elements is/are sufficient to ensure the claims amount to significantly more than the abstract idea identified above (Step 2B: NO).
Claim Rejections - 35 USC § 103
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.
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-4, 11, 13-15, and 17-21, are rejected under 35 U.S.C. 103 as being unpatentable over Elder (US 2015/0286994 A1) in view of Kueh (US 2016/0269898 A1) and Neuhaeuser (US 2023/0171593 A1).
Regarding claim 1, Elder discloses a computer-implemented method for pre-onboarding user access control to subject information (Par. 0031], In some embodiments, an application server 130 may create web pages dynamically for displaying user inter faces for registering users), the computer-implemented method comprising:
receiving, at a service onboarding system from a provider system, acquisition data comprising the subject information associated with a subject (Par. [0068], The service facility may have access to and be able to review records of work performed on the vehicle including details about types of service performed, where service was performed, what parts were used, where the parts were obtained, and warranty status of those parts), wherein the acquisition data further comprises user information associated with a user, the user information comprising user communication channel data usable for transmitting information to a user device that is associated with the user (Par. [0036], customer data includes phone number, Par. [0047], email address);
receiving telematics data associated with the subject (Par. [0068], Service technicians can also review results of diagnostic tests previously performed on the vehicle; Par. [0076], vehicle status 320 data may be downloaded from a computer associated with the vehicle 434 by a technician of a service facility 408 performing work on the vehicle);
associating the telematics data with a subject data object that comprises at least a portion of the subject information (Par. [0086], The system may then automatically extract information from the electronic file to update the service record 332 in data structure 300. The record of repairs or service may include information Such as the date of the service, vehicle mileage, where the service was performed, a name of the service technician, parts installed on the vehicle, a brand or manufacturer of the parts, a serial number of the parts, warranty information of the parts, images or photos illustrating repairs or damage noticed or repaired, comments describing the service, maintenance, or repairs, comments describing overall condition or service status or history of the vehicle, copies of receipts or invoices, and other such information);
causing the graphical user interface to display at least a portion of the telematics data on the user device while the subject data object is pending onboarding, such that the acquisition data is configured to facilitate access to the telematics data on the user device while the subject data object is pending onboarding (Par. [0031], displaying vehicle service records, entering information into the vehicle service records, searching for vehicles, searching for service facilities, etc.); and
causing the graphical user interface to display a glovebox interface, wherein the glovebox interface is configured to (i) display at least a portion of the subject information associated with the subject and/or (ii) display at least one icon or menu item that causes the graphical user interface to display at least a portion of the subject information associated with the subject when selected by the user of the user device (Par. [0010], The website also allows users to view vehicle manufacturer recommended preventative and periodic maintenance schedules for a vehicle; Par. [0031], an application server 130 may create web pages dynamically for displaying user interfaces for registering users, displaying vehicle service records, entering information into the vehicle service records, searching for vehicles, searching for service facilities, etc.).
Elder does not explicitly disclose generating an onboarding hyperlink, wherein the onboarding hyperlink is uniquely associated with the subject data object; transmitting, from the service onboarding system to the user device via a user communication channel associated with the user communication channel data, a custom onboarding message comprising the onboarding hyperlink associated with the subject data object. Kueh teaches generating an onboarding (Par. [0048]) hyperlink, wherein the onboarding hyperlink is uniquely associated with the subject data object (Par. [0041], The authentication service 240 generates an initial link (404), a custom link (406) and a session token (408), each of which are associated with the requesting MCD and the mobile application. The generated links and the session token along, with the ID data 203, are saved in a profile in the database for future queries (410)); transmitting, from the service onboarding system to the user device via a user communication channel associated with the user communication channel data, a custom onboarding message comprising the onboarding hyperlink associated with the subject data object (Par. [0041], The authentication service 240 further generates an SMS text message with a secure single action link (414). This message is sent through the wireless carrier of the MCD 220 via an SMS text message transport (416)).
It would have been obvious to one of ordinary skill in the art before the effective filing date to modify the onboarding system of Elder to include the message generating abilities of Kueh to teach “generating an onboarding hyperlink, wherein the onboarding hyperlink is uniquely associated with the subject data object; transmitting, from the service onboarding system to the user device via a user communication channel associated with the user communication channel data, a custom onboarding message comprising the onboarding hyperlink associated with the subject data object,” as a need exists to authenticate users without the need of entering sensitive data and ensure better security for users (Kueh, Par. [0002]). Such hyperlink generating abilities coupled with the message system as taught in Kueh would enable the onboarding system as disclosed in Elder to provide better security for users.
Elder does not explicitly disclose causing rendering of a graphical user interface at the user device in response to receiving a first indication based on interaction with (i) the onboarding hyperlink via the user device or (ii) a machine-readable symbology. Neuhaeuser teaches causing rendering of a graphical user interface at the user device in response to receiving a first indication based on interaction with (i) the onboarding hyperlink via the user device or (ii) a machine-readable symbology (Par. [0069], The HMI guides the customer to the management server touchpoint, e.g., by showing a QR code which opens the management server app or the management server web portal). It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify the vehicle record system of Elder and Kueh to include the device interface abilities of Neuhaeuser to teach “causing rendering of a graphical user interface at a user device in response to receiving a first indication based on interaction with (i) an onboarding hyperlink via the user device or (ii) a machine-readable symbology embodying the onboarding hyperlink,” since the claimed invention is merely a combination of old elements, and in the combination each element merely would have performed the same function as it did separately, and one of ordinary skill in the art would have recognized that the results of the combination were predictable. As in Neuhaeuser, it is within the capabilities of one of ordinary skill in the art before the effective filing date to apply the code reading and graphical user interface software to Elder and Kueh’s device communicating with the records system with the predicted result of transmitting vehicle data as needed in Elder.
Regarding claim 2, Elder discloses further comprising: receiving, at the service onboarding system following displaying at least the portion of the telematics data on the user device (Par. [0068]), a second indication via the graphical user interface at the user device, wherein the second indication is indicative of the user of the user device completing onboarding (Par. [0059], Once a user has registered with the system 100, the user may access information stored in database 135 over network 120; Par. [0064], By registering with the system 100, the vehicle owner 404 may also receive access to other features of the system. In an embodiment, the system 100 may optionally send emails, Voice messages to an owner's phone number, and/or text message reminders to the vehicle owner when recommended preventative maintenance is due or expected to be due based upon one or more of the age or mileage of the vehicle).
Regarding claim 3, Elder discloses further comprising: causing rendering, via the user device in response to receiving the second indication, of a user onboarding interface comprising a set of user information input fields (Par. [0046], The owner information 328 field may include information about owners of a vehicle, including a name, mailing address, billing address, phone number, email address, and owner interest type. Preferences of the owner, such as a preferred contact method for alerts generated by the system, may also be stored in field 328).
Regarding claim 4, Elder discloses wherein at least one of the set of user information input fields is automatically filled based on user information received from the service onboarding system (Par. [0076], The system 100 may use network 120 to automatically retrieve information from one or more registered users).
Regarding claim 11, Elder does not explicitly disclose further comprising causing, in response to receiving the first indication triggered by interaction with the onboarding hyperlink, the user device to initiate a web-based service application associated with the service onboarding system, wherein the web-based service application is initiated based on the subject data object. Neuhaeuser teaches causing, in response to receiving the first indication triggered by interaction with the onboarding hyperlink, the user device to initiate a web-based service application associated with the service onboarding system, wherein the web-based service application is initiated based on the subject data object (Par. [0069], The HMI guides the customer to the management server touchpoint, e.g., by showing a QR code which opens the management server app or the management server web portal). It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify the vehicle record system of Elder and Kueh to include the device interface abilities of Neuhaeuser since the claimed invention is merely a combination of old elements, and in the combination each element merely would have performed the same function as it did separately, and one of ordinary skill in the art would have recognized that the results of the combination were predictable. As in Neuhaeuser, it is within the capabilities of one of ordinary skill in the art before the effective filing date to apply the code reading and graphical user interface software to Elder and Kueh’s device communicating with the records system with the predicted result of transmitting vehicle data as needed in Elder.
Regarding claim 13, Elder discloses wherein the service onboarding system and the provider system communicate via a first set of application programming interfaces, and the service onboarding system and the user device communicate via a second set of application programming interfaces (Par. [0027], These computers 105, 110, and 115 may also have any of a variety of applications, including for example, database client and/or server applications, and web browser applications. Alternatively, the computers 105, 110, and 115 may be any other electronic device, such as a client computer, laptop, Internet-enabled mobile telephone or smartphone, a computer built into a vehicle (including a computer or processor that monitors, records, and controls the vehicle's performance) and/or tablet computer, capable of communicating via a network (e.g., the network 120 described below), running programs and applications, and/or displaying and navigating web pages or other types of electronic documents).
Regarding claim 14, Elder discloses further comprising: generating a temporary user data object and associating the temporary user data object with the subject data object while the subject data object is pending onboarding; and associating the temporary user data object with the user device while the subject data object is pending onboarding, wherein a user data object is generated based on assigning the temporary user data object to the user (Par. [0033], Similarly, any necessary files for performing the functions attributed to the computers 105, 110, 115, 125, 130 may be stored locally on the respective computer and/or remotely, as appropriate).
Regarding claim 15, Elder discloses further comprising causing the graphical user interface to display a plurality of icons and/or menu items associated with the subject, wherein the plurality of icons and/or menu items comprise at least one of: a maintenance schedule icon or menu item, a recalls icon or menu item, a roadside icon or menu item, a tech support icon or menu item, a home icon or menu item, a deals icon or menu item, a glovebox icon or menu item, and/or a menu icon or menu item (Par. [0010], The website also allows users to view vehicle manufacturer recommended preventative and periodic maintenance schedules for a vehicle; Par. [0031], an application server 130 may create web pages dynamically for displaying user interfaces for registering users, displaying vehicle service records, entering information into the vehicle service records, searching for vehicles, searching for service facilities, etc.).
Regarding claim 17, Elder discloses further comprising causing the graphical user interface to display a protection product interface, wherein the protection product interface is configured to initiate a protection product claim by the user of the user device (Par. [0010], The website also allows users to view vehicle manufacturer recommended preventative and periodic maintenance schedules for a vehicle; Par. [0031], an application server 130 may create web pages dynamically for displaying user interfaces for registering users, displaying vehicle service records, entering information into the vehicle service records, searching for vehicles, searching for service facilities, etc.; Par. [0041], The vehicle information 316 may also include information such as a license plate number, registration information, vehicle title information, insurance information, and pictures of the vehicle).
Regarding claim 18, Elder discloses wherein the telematics data comprises diagnostic data and/or mileage data (Par. [0068], Service technicians can also review results of diagnostic tests previously performed on the vehicle; Par. [0076], vehicle status 320 data may be downloaded from a computer associated with the vehicle 434 by a technician of a service facility 408 performing work on the vehicle).
Regarding claim 19, Elder discloses an apparatus for pre-onboarding user access control to subject information (Par. 0031], In some embodiments, an application server 130 may create web pages dynamically for displaying user inter faces for registering users), the apparatus comprising at least one processor and at least one non-transitory memory, the at least one non-transitory memory having computer-coded instructions stored thereon (Par. [0091]), the computer-coded instructions in execution with the at least one processor configured to:
receive, from a provider system, acquisition data comprising the subject information associated with a subject (Par. [0068], The service facility may have access to and be able to review records of work performed on the vehicle including details about types of service performed, where service was performed, what parts were used, where the parts were obtained, and warranty status of those parts);
receive telematics data associated with the subject (Par. [0068], Service technicians can also review results of diagnostic tests previously performed on the vehicle; Par. [0076], vehicle status 320 data may be downloaded from a computer associated with the vehicle 434 by a technician of a service facility 408 performing work on the vehicle);
associate the telematics data with a subject data object that comprises at least a portion of the subject information (Par. [0086], The system may then automatically extract information from the electronic file to update the service record 332 in data structure 300. The record of repairs or service may include information Such as the date of the service, vehicle mileage, where the service was performed, a name of the service technician, parts installed on the vehicle, a brand or manufacturer of the parts, a serial number of the parts, warranty information of the parts, images or photos illustrating repairs or damage noticed or repaired, comments describing the service, maintenance, or repairs, comments describing overall condition or service status or history of the vehicle, copies of receipts or invoices, and other such information);
cause the graphical user interface to display at least a portion of the telematics data on the user device while the subject data object is pending onboarding, such that the acquisition data is configured to facilitate access to the telematics data on the user device while the subject data object is pending onboarding (Par. [0031], displaying vehicle service records, entering information into the vehicle service records, searching for vehicles, searching for service facilities, etc.) ; and
causing the graphical user interface to display a glovebox interface, wherein the glovebox interface is configured to (i) display at least a portion of the subject information associated with the subject and/or (ii) display at least one icon or menu item that causes the graphical user interface to display at least a portion of the subject information associated with the subject when selected by the user of the user device (Par. [0010], The website also allows users to view vehicle manufacturer recommended preventative and periodic maintenance schedules for a vehicle; Par. [0031], an application server 130 may create web pages dynamically for displaying user interfaces for registering users, displaying vehicle service records, entering information into the vehicle service records, searching for vehicles, searching for service facilities, etc.).
Elder does not explicitly disclose generating an onboarding hyperlink, wherein the onboarding hyperlink is uniquely associated with the subject data object; transmitting, from the service onboarding system to the user device via a user communication channel associated with the user communication channel data, a custom onboarding message comprising the onboarding hyperlink associated with the subject data object. Kueh teaches generating an onboarding (Par. [0048]) hyperlink, wherein the onboarding hyperlink is uniquely associated with the subject data object (Par. [0041], The authentication service 240 generates an initial link (404), a custom link (406) and a session token (408), each of which are associated with the requesting MCD and the mobile application. The generated links and the session token along, with the ID data 203, are saved in a profile in the database for future queries (410)); transmitting, from the service onboarding system to the user device via a user communication channel associated with the user communication channel data, a custom onboarding message comprising the onboarding hyperlink associated with the subject data object (Par. [0041], The authentication service 240 further generates an SMS text message with a secure single action link (414). This message is sent through the wireless carrier of the MCD 220 via an SMS text message transport (416)).
It would have been obvious to one of ordinary skill in the art before the effective filing date to modify the onboarding system of Elder to include the message generating abilities of Kueh to teach “generating an onboarding hyperlink, wherein the onboarding hyperlink is uniquely associated with the subject data object; transmitting, from the service onboarding system to the user device via a user communication channel associated with the user communication channel data, a custom onboarding message comprising the onboarding hyperlink associated with the subject data object,” as a need exists to authenticate users without the need of entering sensitive data and ensure better security for users (Kueh, Par. [0002]). Such hyperlink generating abilities coupled with the message system as taught in Kueh would enable the onboarding system as disclosed in Elder to provide better security for users.
Elder does not explicitly disclose causing rendering of a graphical user interface at the user device in response to receiving a first indication based on interaction with (i) the onboarding hyperlink via the user device or (ii) a machine-readable symbology. Neuhaeuser teaches causing rendering of a graphical user interface at the user device in response to receiving a first indication based on interaction with (i) the onboarding hyperlink via the user device or (ii) a machine-readable symbology (Par. [0069], The HMI guides the customer to the management server touchpoint, e.g., by showing a QR code which opens the management server app or the management server web portal). It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify the vehicle record system of Elder and Kueh to include the device interface abilities of Neuhaeuser to teach “causing rendering of a graphical user interface at a user device in response to receiving a first indication based on interaction with (i) an onboarding hyperlink via the user device or (ii) a machine-readable symbology embodying the onboarding hyperlink,” since the claimed invention is merely a combination of old elements, and in the combination each element merely would have performed the same function as it did separately, and one of ordinary skill in the art would have recognized that the results of the combination were predictable. As in Neuhaeuser, it is within the capabilities of one of ordinary skill in the art before the effective filing date to apply the code reading and graphical user interface software to Elder and Kueh’s device communicating with the records system with the predicted result of transmitting vehicle data as needed in Elder.
Regarding claim 20, Elder discloses further comprising: receiving, at the service onboarding system following displaying at least the portion of the telematics data on the user device (Par. [0068]), a second indication via the graphical user interface at the user device, wherein the second indication is indicative of the user of the user device completing onboarding (Par. [0059], Once a user has registered with the system 100, the user may access information stored in database 135 over network 120; Par. [0064], By registering with the system 100, the vehicle owner 404 may also receive access to other features of the system. In an embodiment, the system 100 may optionally send emails, Voice messages to an owner's phone number, and/or text message reminders to the vehicle owner when recommended preventative maintenance is due or expected to be due based upon one or more of the age or mileage of the vehicle).
Claim 21 is rejected under 35 U.S.C. 103 as being unpatentable over Elder (US 2015/0286994 A1) in view of Kueh (US 2016/0269898 A1); Neuhaeuser (US 2023/0171593 A1); and Brady (US 2020/0258018 A1).
Regarding claim 21, Elder discloses a computer-implemented method for pre-onboarding user access control to subject information (Par. 0031], In some embodiments, an application server 130 may create web pages dynamically for displaying user inter faces for registering users), the computer-implemented method comprising:
receiving, at a service onboarding system from a provider system, acquisition data comprising the subject information associated with a subject (Par. [0068], The service facility may have access to and be able to review records of work performed on the vehicle including details about types of service performed, where service was performed, what parts were used, where the parts were obtained, and warranty status of those parts);
receiving telematics data associated with the subject (Par. [0068], Service technicians can also review results of diagnostic tests previously performed on the vehicle; Par. [0076], vehicle status 320 data may be downloaded from a computer associated with the vehicle 434 by a technician of a service facility 408 performing work on the vehicle);
associating the telematics data with a subject data object that comprises at least a portion of the subject information (Par. [0086], The system may then automatically extract information from the electronic file to update the service record 332 in data structure 300. The record of repairs or service may include information Such as the date of the service, vehicle mileage, where the service was performed, a name of the service technician, parts installed on the vehicle, a brand or manufacturer of the parts, a serial number of the parts, warranty information of the parts, images or photos illustrating repairs or damage noticed or repaired, comments describing the service, maintenance, or repairs, comments describing overall condition or service status or history of the vehicle, copies of receipts or invoices, and other such information);
causing the graphical user interface to display at least a portion of the telematics data on the user device while the subject data object is pending onboarding, such that the acquisition data is configured to facilitate access to the telematics data on the user device while the subject data object is pending onboarding (Par. [0031], displaying vehicle service records, entering information into the vehicle service records, searching for vehicles, searching for service facilities, etc.); and
causing the graphical user interface to display a glovebox interface, wherein the glovebox interface is configured to (i) display at least a portion of the subject information associated with the subject and/or (ii) display at least one icon or menu item that causes the graphical user interface to display at least a portion of the subject information associated with the subject when selected by the user of the user device (Par. [0010], The website also allows users to view vehicle manufacturer recommended preventative and periodic maintenance schedules for a vehicle; Par. [0031], an application server 130 may create web pages dynamically for displaying user interfaces for registering users, displaying vehicle service records, entering information into the vehicle service records, searching for vehicles, searching for service facilities, etc.).
Elder does not explicitly disclose generating an onboarding hyperlink, wherein the onboarding hyperlink is uniquely associated with the subject data object; transmitting, from the service onboarding system to the user device via a user communication channel associated with the user communication channel data, a custom onboarding message comprising the onboarding hyperlink associated with the subject data object. Kueh teaches generating an onboarding (Par. [0048]) hyperlink, wherein the onboarding hyperlink is uniquely associated with the subject data object (Par. [0041], The authentication service 240 generates an initial link (404), a custom link (406) and a session token (408), each of which are associated with the requesting MCD and the mobile application. The generated links and the session token along, with the ID data 203, are saved in a profile in the database for future queries (410)); transmitting, from the service onboarding system to the user device via a user communication channel associated with the user communication channel data, a custom onboarding message comprising the onboarding hyperlink associated with the subject data object (Par. [0041], The authentication service 240 further generates an SMS text message with a secure single action link (414). This message is sent through the wireless carrier of the MCD 220 via an SMS text message transport (416)).
It would have been obvious to one of ordinary skill in the art before the effective filing date to modify the onboarding system of Elder to include the message generating abilities of Kueh to teach “generating an onboarding hyperlink, wherein the onboarding hyperlink is uniquely associated with the subject data object; transmitting, from the service onboarding system to the user device via a user communication channel associated with the user communication channel data, a custom onboarding message comprising the onboarding hyperlink associated with the subject data object,” as a need exists to authenticate users without the need of entering sensitive data and ensure better security for users (Kueh, Par. [0002]). Such hyperlink generating abilities coupled with the message system as taught in Kueh would enable the onboarding system as disclosed in Elder to provide better security for users.
Elder does not explicitly disclose causing rendering of a graphical user interface at a user device in response to receiving a first indication based on interaction with (i) an onboarding hyperlink via the user device or (ii) a machine-readable symbology. Neuhaeuser teaches causing rendering of a graphical user interface at a user device in response to receiving a first indication based on interaction with (i) an onboarding hyperlink via the user device or (ii) a machine-readable symbology (Par. [0069], The HMI guides the customer to the management server touchpoint, e.g., by showing a QR code which opens the management server app or the management server web portal). It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify the vehicle record system of Elder and Kueh to include the device interface abilities of Neuhaeuser since the claimed invention is merely a combination of old elements, and in the combination each element merely would have performed the same function as it did separately, and one of ordinary skill in the art would have recognized that the results of the combination were predictable. As in Neuhaeuser, it is within the capabilities of one of ordinary skill in the art before the effective filing date to apply the code reading and graphical user interface software to Elder and Kueh’s device communicating with the records system with the predicted result of transmitting vehicle data as needed in Elder.
Elder does not explicitly disclose generating a data slug and associating the data slug with the subject data object to cause the subject data object to be associated with the indication of pending onboarding, wherein removing the indication of pending onboarding comprises removing the data slug following completion of onboarding. Brady teaches generating a data slug and associating the data slug with the subject data object to cause the subject data object to be associated with the indication of pending onboarding (Par. [0143], data entered when contract is opened), wherein removing the indication of pending onboarding comprises removing the data slug following completion of onboarding (Par. [0147], data entered upon closing of contract). It would have been obvious to one of ordinary skill in the art before the effective filing date of the claimed invention to modify the vehicle record system of Elder, Kueh, and Neuhaeuser to include the data abilities of Brady since the claimed invention is merely a combination of old elements, and in the combination each element merely would have performed the same function as it did separately, and one of ordinary skill in the art would have recognized that the results of the combination were predictable.
Conclusion
Applicant's amendment necessitated the new ground(s) of rejection presented in this Office action. Accordingly, THIS ACTION IS MADE FINAL. See MPEP § 706.07(a). Applicant is reminded of the extension of time policy as set forth in 37 CFR 1.136(a).
A shortened statutory period for reply to this final action is set to expire THREE MONTHS from the mailing date of this action. In the event a first reply is filed within TWO MONTHS of the mailing date of this final action and the advisory action is not mailed until after the end of the THREE-MONTH shortened statutory period, then the shortened statutory period will expire on the date the advisory action is mailed, and any nonprovisional extension fee (37 CFR 1.17(a)) pursuant to 37 CFR 1.136(a) will be calculated from the mailing date of the advisory action. In no event, however, will the statutory period for reply expire later than SIX MONTHS from the mailing date of this final action.
Any inquiry concerning this communication or earlier communications from the examiner should be directed to Patrick Kim whose telephone number is (571)272-8619. The examiner can normally be reached Monday - Friday, 9AM - 5PM EST.
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, Lynda Jasmin can be reached at (571)272-6782. The fax phone number for the organization where this application or proceeding is assigned is 571-273-8300.
Information regarding the status of published or unpublished applications may be obtained from Patent Center. Unpublished application information in Patent Center is available to registered users. To file and manage patent submissions in Patent Center, visit: https://patentcenter.uspto.gov. Visit https://www.uspto.gov/patents/apply/patent-center for more information about Patent Center and https://www.uspto.gov/patents/docx for information about filing in DOCX format. For additional questions, contact the Electronic Business Center (EBC) at 866-217-9197 (toll-free). If you would like assistance from a USPTO Customer Service Representative, call 800-786-9199 (IN USA OR CANADA) or 571-272-1000.
/Patrick Kim/Examiner, Art Unit 3629
Prosecution Insights