GENERATING AND DELIVERING A WRAP PACKAGE OF CARDS INCLUDING CUSTOM CONTENT AND/OR SERVICES IN RESPONSE TO A VEHICLE DIAGNOSTIC SYSTEM TRIGGERED EVENT

• US 20160133062A1
• Filed: 01/15/2016
• Published: 05/12/2016
• Est. Priority Date: 10/09/2014
• Status: Active Grant

• Current Assignee: Brunoco, Inc.
• Original Assignee: Wrap Media, LLC (DXC Technology Company)
• Inventors: GREENBERG, Eric H., GARRIS, John M., BHASIN, Kunal K., FOSTER, Peter M.
• Granted Patent: US 9,412,208 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: B60R 16/0234 related to maintenance or repairing of vehicles
• CPC Class Codes: G06F 16/9535 Search customisation based on user profiles and personalisation
• CPC Class Codes: G06F 16/9577 Optimising the visualization of content, e.g. distillation of HTML documents
• CPC Class Codes: G06F 16/958 Organisation or management of web site content, e.g. publishing, maintaining pages or automatic linking
• CPC Class Codes: G06F 16/972 Access to data in other repository systems, e.g. legacy data or dynamic Web page generation
• CPC Class Codes: G06F 3/04817 using icons graphical or visual programming using iconic symbols G06F8/34
• CPC Class Codes: G06F 3/0482 Interaction with lists of selectable items, e.g. menus
• CPC Class Codes: G06F 3/0483 Interaction with page-structured environments, e.g. book metaphor
• CPC Class Codes: G06F 3/04842 Selection of displayed objects or displayed text elements G06F3/0482 takes precedence
• CPC Class Codes: G06F 3/0485 Scrolling or panning
• CPC Class Codes: G06F 40/106 Display of layout of documents; Previewing
• CPC Class Codes: G06F 40/117 Tagging; Marking up details of markup languages G06F40/143; Designating a block; Setting of attributes style sheets, e.g. eXtensible Stylesheet Language Transformation [XSLT], G06F40/154
• CPC Class Codes: G06F 40/143 Markup, e.g. Standard Generalized Markup Language [SGML] or Document Type Definition [DTD]
• CPC Class Codes: G06F 40/186 Templates
• CPC Class Codes: G06Q 30/0643 Graphical representation of items or shoppers
• CPC Class Codes: G06T 11/60 Editing figures and text; Combining figures or text
• CPC Class Codes: G07C 5/006 Indicating maintenance
• CPC Class Codes: G07C 5/008 communicating information to a remotely located station transmission systems for measured values G08C

Abstract

Delivery of a wrap package “on the fly” in reply to a vehicle onboard diagnostic (OBD) system triggered event. When a notice of the event is received, a wrap package, including custom content presented within a plurality of cards arranged in one or more linear sequences, is automatically authored. The custom content encompasses, but is not limited to, one or more media types, application functionality and/or e-commerce related services. In one embodiment, the custom content pertains to a specific code generated by the OBD system that corresponds to the event. In another embodiment, the triggered event is an accident.

Claims

1. A method performed at a node on a network, comprising:

receiving a notice indicating that an event triggered by an onboard diagnostic system on a vehicle has occurred;

generating custom content pertinent to the event;

generating a wrap descriptor for a wrap package including a plurality of cards arranged to be browsed in one or more linear sequences and including the custom content pertinent to the event, the wrap descriptor including a plurality of card descriptors, each card descriptor arranged to define content, a structure and a layout of an associated one of the cards respectively; and

delivering the wrap descriptor to a computing device, the wrap descriptor arranged so that the computing device can generate a runtime instance of the wrap package on a display associated with the computing device from the delivered wrap descriptor, the runtime instance of the wrap package including;

(a) the plurality of cards arranged to be browsed on the display in the one or more linear sequences; and

(b) the custom content pertinent to the event.

2. The method of claim 1, further comprising:

(c) authoring the plurality of cards of the wrap package from one or more card templates including one or more empty container component(s); and

(d) inserting or associating the custom content into the one or more empty container component(s) of the one or more card templates in response to receiving the notice indicating that the event triggered by the onboard diagnostic system on the vehicle has occurred.

3. The method of claim 2, wherein the one or more empty component container(s) is/are selected from the following types of component containers:

(c) text;

(d) image/photo;

(e) video;

(f) an appointment, reservation or booking function for facilitating an appointment, reservation or booking;

(g) GPS or positional function for providing GPS or positional services;

(h) emergency services;

(i) an application for providing application functionality; and

/or

(j) a transaction for providing or implementing a transaction service.

4. The method of claim 1, wherein generating the wrap descriptor for the wrap package further comprises:

(c) generating the plurality of card descriptors for the plurality of cards of the wrap package respectively; and

(d) generating the wrap descriptor from the plurality of card descriptors.

5. The method of claim 4, wherein generating the plurality of card descriptors for the plurality of cards of the wrap package further comprises:

(e) selecting a first card among the plurality of cards of the wrap package;

(f) generating data object(s) for each component in the select card;

(g) generating a card descriptor for the select card from the data object(s) generated for each component in the select card; and

(h) generating the plurality of card descriptors by repeating steps (e) through (g) for each card among the plurality of cards of the wrap package respectively.

6. The method of claim 5, further comprises generating the data object(s) for each of the following component types associated with the selected card:

(h) content;

(i) attribute(s);

(j) style(s);

(k) trigger(s);

(l) behavior(s).

7. The method of claim 1, wherein the custom content further includes one of the following:

(c) information pertinent to the vehicle;

(d) information pertinent to the user of the vehicle

(e) information pertinent to the location of the vehicle;

or

(f) any combination of (c) through (e).

8. The method of claim 1, further comprising identifying a user of the vehicle after receiving the notice indicating that the event triggered by the onboard diagnostic system on the vehicle has occurred.

9. The method of claim 8, wherein the user is identified by one of the following:

(c) receiving identifying information from the onboard diagnostic system of the vehicle;

(d) from the computing device, which is associated with the user;

(e) the user identifying him/herself by logging into the network.

10. The method of claim 1, wherein the event triggered by the onboard diagnostic system on the vehicle comprises one or more of the following:

(c) an odometer reading on the vehicle indicating that vehicle servicing is needed;

(d) the onboard diagnostic system determining that vehicle servicing is needed;

(e) the onboard diagnostic system generating a dashboard warning light indicating that there is a problem with the vehicle;

(f) the onboard diagnostic system detecting that an airbag has been deployed in the vehicle; and

/or

(g) the onboard diagnostic system detecting that the vehicle has been in a collision or accident.

11. The method of claim 1, wherein the notice includes a code, generated by the onboard diagnostic system, that identifies the event among a plurality of possible events.

12. The method of claim 1, wherein the notice includes one or more of the following:

(c) a code identifying the event;

(d) a Vehicle Identification Number for the vehicle;

(e) a driver, passenger(s) and/or owner of the vehicle.

13. The method of claim 1, wherein the notice includes a specific onboard diagnostic system code that identifies the event and the custom content pertinent to the event is specifically related to the specific onboard diagnostic system code.

14. The method of claim 1, wherein the custom content pertinent to the event further comprises one or more of the following:

(c) a vehicle identification number (VIN);

(d) a make and/or model of the vehicle;

(e) warning information pertaining to the event;

(f) instructional information informing how to correct or address a mechanical problem with the vehicle as identified by the onboard diagnostic system;

(g) an instructional video informing how to correct or address a mechanical problem with the vehicle as identified by the onboard diagnostic system;

(h) application functionality for contacting a tow truck and/or roadside assistance;

(i) application functionality for making a service appointment at a vehicle repair facility; and

/or

(j) application functionality for contacting emergency medical services.

15. The method of claim 1, wherein generating the wrap descriptor further comprises either:

(c) generating a JavaScript Object Notation (JSON) wrap descriptor, or

(d) generating a Binary JSON (BSON) wrap descriptor.

16. The method of claim 1, wherein the runtime instance of the wrap package is generated on the computing device by:

(c) creating an object graph from the wrap descriptor,

(d) generating a document object model from the object graph; and

(e) generating the runtime instance of the cards of the wrap package from the document object model.

17. The method of claim 1, wherein the cards of the wrap package include a gallery card configured to display a plurality of gallery items by:

(c) arranging the plurality of gallery items in a vertical sequence; and

(d) sequentially displaying the plurality of gallery items in the vertical sequence in response to navigational inputs.

18. The method of claim 1, wherein the wrap package includes a widget card that presents, when rendered, a widget that appears within a frame in the widget card, the widget configured to interact with a remote widget server while the widget card is rendered on the computing device and to present, within the frame, one or more views to either receive information and/or present information.

19. The method of claim 1, wherein at least one of the cards of the wrap package is an application card having an application embedded in or associated therewith, wherein the application comprises of the following:

(c) an online chat function;

(d) a reservation, appointment or booking function for making a reservation, appointment or booking;

(e) an approval function configured for entry of an approval;

(f) a data input/entry function for enabling data to be input/entered through the application card;

or

(g) GPS or a positional functionality.

20. The method of claim 1, wherein the wrap package is configured to be rendered on the display associated with the computing device so that:

(h) each of the cards is each rendered in a same portrait aspect ratio respectively; and

(i) within each card, a same relative positioning of the content is maintained regardless of the size and/or type of the display.

21. The method of claim 1, wherein the one or more linear sequence(s) extend:

(c) horizontally;

(d) vertically;

(f) both (c) and (d).

22. The method of claim 1, wherein the plurality of the cards of the wrap package are configured to be swipe-browsed in the one or more linear sequences when the display associated with the computing device is touch-sensitive.

23. The method of claim 1, wherein the card descriptors of the wrap descriptor are selectively authored to include one or more component descriptors, the one or more component descriptors selected from the following group of component descriptor types:

(c) container;

(d) text;

(e) image/photo

(f) video;

(g) link;

(h) location/GPS;

(i) widget; and

/or

(j) feed.

24. The method of claim 1, wherein at least one of the card descriptors of the wrap descriptor includes a feed descriptor that defines a feed for the associated card, the feed descriptor defining a feed source and feed content, wherein, the feed content is retrieved from the feed source and rendered when the associated card is rendered.

25. The method of claim 1, wherein at least one of the card descriptors included in the wrap descriptor references an asset located external to the wrap descriptor using an asset identifier, wherein the asset identifier is used to retrieve the asset so that it can be rendered when the associated card is rendered.

26. The method of claim 1, wherein the wrap descriptor further comprises a global component that is associated with two or more of the cards of the wrap package.

27. The method of claim 1, wherein at least one of the card descriptors of the wrap descriptor includes a behavior declaration that declares a behavior to be associated with the card when rendered.

28. The method of claim 1, wherein the cards of the wrap package includes at least one card having a trigger associated therewith, the trigger invoking a predetermined action.

29. The method of claim 28, wherein the predefined action, in response to the trigger, invokes one of the following:

(c) a chat session;

(d) purchase of a displayed item;

(e) an appointment, reservation or booking function;

(f) a GPS/location service;

(g) cul-de-sacing to a target web site;

(h) placement of an item into a shopping cart;

or

(i) a “

one-click”

or analogous buy operation.

30. The method of claim 1, wherein the plurality of cards of the wrap package includes at least one transaction card for implementing a transaction while the wrap package is consumed on the computing device, the transaction card implementing the transaction by one of the following:

(c) associating a transaction widget with the transaction card;

(d) cul-de-sacing from the transaction card to a remote server for performing the transaction and then returning to the wrap package;

or

(e) associating a buy function with the transaction card.