In-vehicle web presentation

• US 9,250,856 B2
• Filed: 04/21/2014
• Issued: 02/02/2016
• Est. Priority Date: 04/21/2014
• Status: Active Grant

• Current Assignee: Livio, Inc.
• Original Assignee: Myine Electronics, Inc. (Ford Motor Company)
• Inventors: Danne, Philip Joseph, Sigal, Jacob R., Smereka, Scott, Grover, Joey Ray
• Primary Examiner(s): Le, Thien M
• Assistant Examiner(s): Brown, Claude J
• Application Number:
  US14/257,491
• Publication Number:
  US 20150301794A1
• Time in Patent Office: 652 Days
• Field of Search: 235/472.01
• US Class Current: 1/1
• CPC Class Codes: B60K 2360/186 Displaying information according to relevancy
• CPC Class Codes: B60K 2360/589 Wireless data transfers
• CPC Class Codes: B60K 35/00 Instruments specially adapted for vehicles; Arrangement of instruments in or on vehicles
• CPC Class Codes: B60K 35/29 Instruments characterised by the way in which information is handled, e.g. showing information on plural displays or prioritising information according to driving conditions
• CPC Class Codes: B60K 35/85 Arrangements for transferring vehicle- or driver-related data
• CPC Class Codes: B60R 16/0373 Voice control in general G10L
• CPC Class Codes: G06F 3/167 Audio in a user interface, e.g. using voice commands for navigating, audio feedback
• CPC Class Codes: G06F 40/103 Formatting, i.e. changing of presentation of documents automatic justification G06F40/189; automatic line break hyphenation G06F40/191
• CPC Class Codes: G06F 40/143 Markup, e.g. Standard Generalized Markup Language [SGML] or Document Type Definition [DTD]
• CPC Class Codes: H04L 67/12 specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
• CPC Class Codes: H04L 67/51 Discovery or management thereof, e.g. service location protocol [SLP] or web services
• CPC Class Codes: H04L 67/60 Scheduling or organising the servicing of application requests, e.g. requests for application data transmissions using the analysis and optimisation of the required network resources admission control or resource allocation H04L47/70

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

1. A system comprising:

web content including hypertext markup tags and voice commands defined for voice control of the hypertext markup tags; and

at least one controller programmed to

extract the voice commands from the web content,

provide the web content for display, formatted according to vehicle computing system (VCS) specific formatting information, and

update a voice command interface of the VCS according to the voice commands as extracted.

2. The system of claim 1, the at least one controller further programmed to validate the web content as being in compliance with in-vehicle web standard requirements.

3. The system of claim 2, 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.

4. The system of claim 1, the at least one controller 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.

5. The system of claim 4, wherein the at least one 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 VCS.

6. The system of claim 1, wherein the formatting information 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.

7. The system of claim 1, wherein the formatting information is implemented at least in part as one of:

at least one cascading style sheet, information to be included in a cascading style sheet, and at least one template defining a presentation of elements of web content.

8. The system of claim 1 wherein the formatting information includes vehicle manufacturer branding information to be applied to the web content.

9. 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;

formatting the web content according to vehicle computing system (VCS) specific formatting information;

providing the web content as formatted for display by the VCS; and

updating a voice commands interface of the VCS according to the voice commands as extracted.

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

11. The method 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 method of claim 9, 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.

13. The method of claim 12, further comprising providing user-agent information in a header of the request indicating that request is for display by the VCS.

14. The method of claim 12, wherein the formatting information 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.

15. The method of claim 12, wherein the formatting information is implemented at least in part by at least one of:

at least one cascading style sheet, information to be included in a cascading style sheet, and at least one template defining a presentation of elements of web content.

16. A system comprising:

a server configured to

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 vehicle computing system (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.

17. The system of claim 16, the server further configured to redirect 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.

18. The system of claim 16, 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.