DETAILED ACTION
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 .
Information Disclosure Statement
The information disclosure statements filed 1/30/2025 & 3/30/20256 fail to comply with the provisions of 37 CFR 1.98(a)(4) because it lacks the appropriate size fee assertion. It has been placed in the application file, but the information referred to therein has not been considered as to the merits.
Claim Rejections - 35 USC § 102
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 (i.e., changing from AIA to pre-AIA ) 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 the appropriate paragraphs of 35 U.S.C. 102 that form the basis for the rejections under this section made in this Office action:
A person shall be entitled to a patent unless –
(a)(1) the claimed invention was patented, described in a printed publication, or in public use, on sale, or otherwise available to the public before the effective filing date of the claimed invention.
Claim(s) 1, 2, 3, 5, 6, 7, and 20 is/are rejected under 35 U.S.C. 102(a)(1) as being anticipated by Penilla (US 9229623).
Regarding claim 1, (Original) A vehicle display device, comprising: a display unit; a user input unit; (Penilla: figure 6)
a vehicle client configured to receive a first execution screen of an external device application from an external device by communicating with the external device executing the external device application, display the first execution screen on the display unit, (“In one embodiment, the user can custom configure to have content from applications running on the portable device 210 to be displayed in the vehicle displayed 162 in a specific location. This location on the display can then be synchronized or mirrored to that part of the display based on the configuration. In still other embodiments, the custom configuration can determine to synchronize an application running on the portal device to occupy the entire display 162. For example, if the user wishes to use his own telephone calling interface and contacts that are stored on the portable device 210, that information can be populated and mirrored to the display device” Penilla: column 16, lines 3-15)
and generate an external device gesture recognition reference by receiving an external device gesture list relating to the first execution screen from the external device, (“The customization is defined by the user, for example, by selecting specific applications, selecting different background colors, wallpapers, for the user interfaces, selecting different input interfaces,” Penilla: column 13, lines 16-19 & “The generated custom configuration can then be transferred to the vehicle 160 and operated using vehicle electronics 162. Vehicle electronics 162 can also include a display. As mentioned above, the display can be a single display or a plurality of displays. The displays are configured to generate images for various screens, selections, icons, buttons, controls, and received touch input and communicate text information and other data to users.” Penilla: column 14, lines 53-60)
and a gesture identifier identifying a gesture inputted through the user input unit based on the external device gesture recognition reference while the first execution screen is displayed. (“The method enables system controls, using the vehicle computer, to enable access to the plurality of native applications and the plurality of mobile device applications, the system controls including one or more of button inputs of the vehicle, touch screen inputs via the user interface of the display screen of the vehicle, and voice input via microphones of the vehicle.” Penilla: abstract)
Regarding claim 2, (Currently Amended) The vehicle display device of claim 1, wherein the display unit and the user input unit comprise a touchscreen, wherein the inputted gesture is a touch gesture, and wherein the external device gesture list is-a an external device touch gesture list. (“The method enables system controls, using the vehicle computer, to enable access to the plurality of native applications and the plurality of mobile device applications, the system controls including one or more of button inputs of the vehicle, touch screen inputs via the user interface of the display screen of the vehicle, and voice input via microphones of the vehicle.” Penilla: column 2, lines 7-13, “The customization is defined by the user, for example, by selecting specific applications, selecting different background colors, wallpapers, for the user interfaces, selecting different input interfaces,” Penilla: column 13, lines 16-19 & “The generated custom configuration can then be transferred to the vehicle 160 and operated using vehicle electronics 162. Vehicle electronics 162 can also include a display. As mentioned above, the display can be a single display or a plurality of displays. The displays are configured to generate images for various screens, selections, icons, buttons, controls, and received touch input and communicate text information and other data to users.” Penilla: column 14, lines 53-60)
Regarding claim 3, (Original) The vehicle display device of claim 2, wherein based on the touch gesture related to the external device gesture recognition reference, the vehicle client transmits information on the touch gesture to the external device, receives a second execution screen of the external device application related to the touch gesture, and displays the second execution screen on the display unit. (“Also shown in FIG. 7 is an embodiment where a user's smart phone or mobile device is synchronized with the user interface of the vehicle 160. In this embodiment, the user's portable device 210 can synchronize and upload content and UI controls from applications stored and running on the portable device 210. This provides for safer driving, as the controls shown on the vehicle display can be restricted based on driving or operation status.” Penilla: column 15, line 63 – column 16, line 2)
Regarding claim 5, (Original) The vehicle display device of claim 2, further comprising an app executor configured to execute a vehicle application and display a third execution screen of the vehicle application on the touchscreen, wherein based on a pre-stored vehicle gesture recognition reference, the gesture recognizer identifies a touch gesture inputted through the touchscreen while the third execution screen is displayed. (“In one embodiment, the user can custom configure to have content from applications running on the portable device 210 to be displayed in the vehicle displayed 162 in a specific location. This location on the display can then be synchronized or mirrored to that part of the display based on the configuration. In still other embodiments, the custom configuration can determine to synchronize an application running on the portal device to occupy the entire display 162. For example, if the user wishes to use his own telephone calling interface and contacts that are stored on the portable device 210, that information can be populated and mirrored to the display device” Penilla: column 16, lines 3-15 & “Also shown in FIG. 7 is an embodiment where a user's smart phone or mobile device is synchronized with the user interface of the vehicle 160. In this embodiment, the user's portable device 210 can synchronize and upload content and UI controls from applications stored and running on the portable device 210. This provides for safer driving, as the controls shown on the vehicle display can be restricted based on driving or operation status.” Penilla: column 15, line 63 – column 16, line 2)
Regarding claim 6, (Original) The vehicle display device of claim 5, wherein based on the touch gesture related to the vehicle gesture recognition reference, the app executor displays a fourth execution screen of the vehicle application related to the touch gesture on the touchscreen. (“Also shown in FIG. 7 is an embodiment where a user's smart phone or mobile device is synchronized with the user interface of the vehicle 160. In this embodiment, the user's portable device 210 can synchronize and upload content and UI controls from applications stored and running on the portable device 210. This provides for safer driving, as the controls shown on the vehicle display can be restricted based on driving or operation status.” Penilla: column 15, line 63 – column 16, line 2)
Regarding claim 7, (Original) The vehicle display device of claim 2, wherein the vehicle client further receives an external device function list relating to a function supported by the external device from the external device and wherein at least one item of the external device function list is related to the external device touch gesture list. (“In one embodiment, the user can custom configure to have content from applications running on the portable device 210 to be displayed in the vehicle displayed 162 in a specific location. This location on the display can then be synchronized or mirrored to that part of the display based on the configuration. In still other embodiments, the custom configuration can determine to synchronize an application running on the portal device to occupy the entire display 162. For example, if the user wishes to use his own telephone calling interface and contacts that are stored on the portable device 210, that information can be populated and mirrored to the display device” Penilla: column 16, lines 3-15)
Regarding claim 20, the claim is interpreted and rejected as claim 1 stated above.
Allowable Subject Matter
Claims 4 and 8-19 are objected to as being dependent upon a rejected base claim, but would be allowable if rewritten in independent form including all of the limitations of the base claim and any intervening claims.
The following is a statement of reasons for the indication of allowable subject matter: the prior art does not disclose nor suggest a vehicle client receiving an additional device gesture list relating to a second execution screen (claim 4) or a vehicle generating an integrated function and touch gesture list based on the external device function and touch list, a previously stored function and touch list and where at least one item on the function list is related to the touch gesture list (claims 8-19).
Conclusion
Related Prior Art:
US 20230368548 A1 – vehicle display device for interacting with a user mobile device
US 20230138838 A1 – vehicle display device for interacting with a user mobile device
US 20220076282 A1 – vehicle display device for interacting with a user mobile device
US 20160263996 A1 – vehicle display device for interacting with a user mobile device
US 20140188970 A1 – vehicle display device for interacting with a user mobile device
Any inquiry concerning this communication or earlier communications from the examiner should be directed to TRAVIS R HUNNINGS whose telephone number is (571)272-3118. The examiner can normally be reached M: 6-7:30a, 9:30a-4:45p, 8:30-10p; T: 6-7:30a, 12-4p, 7:30p-12a; W: 6-7:30a, 9:30a-4:45p; H: 6-7:30a, 8:15a-4:45p; F: 12:00-4:45p.
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, Davetta Goins can be reached at 571-272-2957. 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.
/TRAVIS R HUNNINGS/ Primary Examiner, Art Unit 2689
Prosecution Insights