IP Library Granted Patent US 9,680,963
Granted Patent B2
US 9,680,963 · App. 14/993,729 · Granted Jun 13, 2017

In-vehicle web presentation

Inventors: Philip Joseph Danne (Royal Oak, MI); Jacob R. Sigal (Ferndale, MI); Scott Smereka (Warren, MI); Joey Ray Grover (Madison Heights, MI)
Assignee: Livio, Inc.
H04L67/32G06F3/167G06F17/211G06F17/2247H04L67/12H04L67/16B60K35/00B60K2350/1096B60K2350/357B60R16/0373
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 9,680,963
App. No.
14/993,729
Granted
Jun 13, 2017
Kind
B2
Abstract

One or more controller may extract voice commands from retrieved web content, format the web content according to vehicle computing system (VCS) specific formatting information, provide the formatted web content for display by the VCS, and update the recognized voice commands of the VCS according to the extracted voice commands. A server may identify whether a received web request for web content is directed to a vehicle sub-domain for providing an in-vehicle-specific version of the content, identify whether the received web request is for presentation of web content via a VCS, and redirect the web request to the vehicle sub-domain when the request is not directed to the vehicle sub-domain and is for presentation via the VCS.

Claims (46)

1. A method comprising:

identifying, by a server, whether a received web request for web content is directed to a vehicle sub-domain for providing an in-vehicle-specific version of the content;

identifying whether the received web request is for presentation of web content via a vehicle computing system (VCS); and

redirecting the web request to the vehicle sub-domain when the request is not directed to the vehicle sub-domain and is for presentation via the VCS.

2. The method of claim 1 , further comprising redirecting the web request away from the vehicle sub-domain when the request is directed to the vehicle sub-domain and is not for presentation via the VCS.

3. The method of claim 1 , further comprising identifying that the web content is for presentation via the VCS according to user-agent information included in a header of the request indicating that request is for display by the VCS.

4. The method of claim 1 , wherein the in-vehicle-specific version of the content includes hypertext markup tags and voice commands defined for voice control of the hypertext markup tags.

5. The method of claim 1 , wherein the in-vehicle-specific version of the content includes a cascading style sheet for in-vehicle web content presentation.

6. The method of claim 1 , further comprising receiving user-agent information in a header of the web request indicating that the web content is for display by the VCS, wherein identifying whether the received web request for web content is directed to the vehicle sub-domain for providing an in-vehicle-specific version of the content includes reviewing the header of the web request.

7. The method of claim 1 , wherein the vehicle sub-domain is one or more of: c, car, v, vehicle, or ivi.

8. A system comprising:

a memory storing a cascading style sheet for in-vehicle web content presentation and retrieved web content including hypertext markup tags and voice commands defined for voice control of the hypertext markup tags; and

a controller programmed to

provide the web content to an in-vehicle display formatted according to the cascading style sheet, and

update an in-vehicle voice command interface according to the voice commands.

9. The system of claim 8 , wherein the controller is further programmed to:

update the cascading style sheet based on vehicle requirements including at least two of color, size, or location; and

apply the cascading style sheet as updated to the web content to cause the web content to be configured in conformance with the vehicle requirements.

10. The system of claim 8 , wherein the controller is further programmed to validate the web content as being in compliance with in-vehicle web standard requirements.

11. The system of claim 10 , wherein the in-vehicle web standard requirements include at least one of: restrictions on allowable web formatting, restrictions on allowable hypertext markup tags, and requirements for predetermined web controls to include voice command information configured to allow users to select the web controls by voice command.

12. The system of claim 8 , wherein the controller is further programmed to:

send a web request for the web content to a web server;

receive a redirect from the web server to a vehicle-specific version of the web content; and

retrieve the vehicle-specific version of the web content as the web content.

13. The system of claim 12 , wherein controller is further programmed to provide user-agent information in a header of the web request indicating that the web content is for display by the controller to the in-vehicle display.

14. The system of claim 12 , wherein the redirect is to a vehicle sub-domain.

15. The system of claim 14 , wherein the vehicle sub-domain is one or more of: c, car, v, vehicle, or ivi.

16. The system of claim 8 , wherein the cascading style sheet specifies at least two of: text size, button size, page background, element color information, total number of elements of web content, and position of elements of web content.

17. The system of claim 8 , wherein the cascading style sheet specifies vehicle manufacturer branding information to be applied to the web content.

18. A computer-implemented method comprising:

extracting voice commands from retrieved web content, the web content including hypertext markup tags and the voice commands defined for voice control of the hypertext markup tags;

providing the web content to an in-vehicle display formatted according to a cascading style sheet; and

updating an in-vehicle voice command interface according to the voice commands.

19. The method of claim 18 , further comprising:

updating the cascading style sheet based on vehicle requirements including at least two of color, size, or location; and

applying the cascading style sheet as updated to the web content to cause the web content to be configured in conformance with the vehicle requirements.

20. The method of claim 18 , further comprising validating the web content as being in compliance with in-vehicle web standard requirements.

21. The method of claim 20 , wherein the in-vehicle web standard requirements include at least one of: restrictions on allowable web formatting, restrictions on allowable hypertext markup tags, and requirements for predetermined web controls to include voice command information configured to allow users to select the web controls by voice command.

22. The method of claim 18 , further comprising:

requesting the web content from a web server,

receiving a redirect from the web server to a vehicle-specific version of the web content, and

retrieving the vehicle-specific version of the web content.

23. The method of claim 22 , further comprising providing user-agent information in a header of the request indicating that request is for display to the in-vehicle display.

24. The method of claim 22 , wherein the redirect is to a vehicle sub-domain.

25. The method of claim 24 , wherein the vehicle sub-domain is one or more of: c, car, v, vehicle, or ivi.

26. The method of claim 18 , wherein the cascading style sheet specifies at least two of: text size, button size, page background, element color information, manufacturer branding information, total number of elements, and position of elements.

Assignments (2)
CHANGE OF NAME Recorded Feb 28, 2017
From: MYINE ELECTRONICS, INC.
To: LIVIO, INC.
Reel/Frame 041397/0724 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 13, 2016
From: DANNE, PHILIP JOSEPH; SIGAL, JACOB R.; SMEREKA, SCOTT; GROVER, JOEY RAY
To: MYINE ELECTRONICS, INC.
Reel/Frame 037480/0313 →
Continuity (2)
Continuation 14257491 · Apr 21, 2014
Related Publication 20160127503A1 · May 5, 2016