Generating and delivering a wrap package of cards including custom content and/or services in response to a triggered event

• US 9,460,228 B2
• Filed: 01/15/2016
• Issued: 10/04/2016
• Est. Priority Date: 10/09/2014
• Status: Active Grant

• Current Assignee: Brunoco, Inc.
• Original Assignee: Wrap Media, LLC (DXC Technology Company)
• Inventors: Foster, Peter M., BHASIN, Kunal K., Garris, John M., Greenberg, Eric H.
• Primary Examiner(s): Patel, Manglesh M
• Application Number:
  US14/997,087
• Publication Number:
  US 20160132516A1
• Time in Patent Office: 263 Days
• Field of Search: 715/243, 715/200, 715234-235, 715/204
• US Class Current: 1/1
• 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/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/134 Hyperlinking
• 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: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]

Abstract

Delivery of a wrap package in reply to a notice of the occurrence of a trigger event sensed by a “Thing” among the Internet of Things. In response, a wrap package, including custom content presented within cards of the wrap is automatically generated. The custom content selectively encompasses, one or more media types, application functionality and/or e-commerce related services. A wrap descriptor, which defines the wrap package including the custom content, is then delivered to a computing device associated with a target recipient. When consumed, the computing device generates a runtime instance of the wrap package from the wrap descriptor.

Claims

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

receiving a notice indicating that a trigger event as determined by a Thing among the Internet of Things (“

IoT”

) has occurred, the trigger event defined as an occurrence or condition that the Thing is configured to monitor or sense;

automatically generating custom content pertinent to the event in response to the notice indicating that the trigger event as determined by the Thing has occurred;

automatically generating a wrap descriptor for a wrap package, the wrap package including a plurality of cards arranged to be browsed in one or more directions, each card having;

(1) a fixed aspect ratio; and

(2) an immutable position of content within an immutable card layout,

wherein at least one of the cards of the wrap package includes the custom content pertinent to the event that was automatically generated in response to the notice indicating that the trigger event has occurred;

the wrap descriptor including a plurality of card descriptors, each card descriptor arranged to define;

(3) a card component container defining the fixed aspect ratio for the associated card; and

(4) one or more component descriptor(s) each defining a component container arranged to contain or associate a component with the associated card, each of the component container(s) having a fixed position within the associated card component container so that the immutable position of the component within the immutable card layout is maintained;

ascertaining a target recipient for the wrap package; and

automatically delivering the wrap descriptor to a computing device associated with the target recipient, the wrap descriptor arranged for the computing device to generate a runtime instance of the wrap package on a display associated with the computing device from the 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 directions; and

(b) the custom content pertinent to the event.

2. The method of claim 1, further comprising authoring the plurality of cards of the wrap package by:

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

(d) defining one or more linear sequences for browsing the cards in the one or more directions; and

(e) in response to the notice, inserting or associating the generated custom content into the one or more empty component container(s) of the defined one or more cards.

3. The method of claim 2, wherein the one or more empty component container(s) are each arranged to contain or associate one of the following:

(c) text;

(d) an image/photo;

(e) a video;

(f) a widget;

(g) an appointment, reservation or booking function;

(h) GPS or positional functionality;

(i) an application;

(j) transactional functionality;

(k) a link;

(l) a document; and

/or

(m) a feed for presenting data from a feed source.

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 container in the select card;

(g) generating the card descriptor for the select card from the data object(s) generated for each component container 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 1, wherein the custom content further includes one of the following:

(c) information pertinent to the Thing;

(d) information pertinent to the trigger event;

(e) information pertinent to the target recipient;

or

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

7. The method of claim 1, wherein the trigger event comprises one or more of the following:

(c) a detected condition indicating that the Thing needs maintenance or servicing;

(d) a warning indicating that the Thing is malfunctioning or operating improperly;

(e) an emergency; and

/or

(f) a condition sensed by the Thing.

8. The method of claim 1, wherein the notice includes a code that identifies the trigger event among a plurality of possible trigger events.

9. The method of claim 1, wherein the notice includes one of the following:

(c) a code identifying the event;

(d) an identification number for identifying the Thing;

(e) one or more designated persons or entities associated with the Thing;

or

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

10. The method of claim 1, wherein the notice includes a specific code that identifies the trigger event and the custom content is related to the identified trigger event specified by the code.

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

(c) information identifying a make and/or model of the Thing;

(d) information describing the trigger event;

(e) instructional text information informing how to correct or address the trigger event;

(f) an instructional photo, image and/or video informing how to correct or address the trigger event;

(g) functionality for contacting a repair or service organization;

(h) functionality for making a service or repair appointment;

(i) functionality for contacting emergency services;

(j) functionality for facilitating a transaction to purchase a good or service related to the Thing; and

/or

(l) functionality for conducting an online chat.

12. 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.

13. 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 sequence; and

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

14. 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.

15. 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 one 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;

(g) GPS or a positional functionality; and

/or

(h) a transaction function for facilitating a transaction for a good and/or service.

16. The method of claim 1, wherein the one or more directions extend:

(c) horizontally;

(d) vertically;

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

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

18. The method of claim 1, wherein at least one of the card descriptors 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.

19. The method of claim 1, wherein at least one of the card descriptors includes a behavior declaration that declares a behavior that is bound to the card when rendered by a runtime viewer responsible for generating the runtime instance of the wrap package at the computing device, wherein the behavior is selected among a plurality of behavior definitions maintained by the runtime viewer.

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

21. The method of claim 20, wherein the predefined call-to-action, in response to the trigger, invokes one of the following:

(c) a chat session;

(d) initiating a purchase transaction for 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”

buy operation.

22. The method of claim 1, wherein the plurality of cards of the wrap package includes at least one transaction card for implementing a transaction, 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;

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

or

(f) associating one or more dependent cards with the transaction card, the one or more dependent cards facilitating the transaction.

23. The method of claim 1, further comprising:

authoring the wrap package of cards to have the predefined presentation; and

configuring the wrap descriptor for the wrap package so that the runtime instance of the wrap package has the same presentation as authored,

wherein the presentation of the wrap package includes;

one or more non-gallery cards each having a first aspect ratio and navigable along a first of the one or more directions; and

a gallery card that is navigable along a second of the one or more directions, the gallery card having a second aspect ratio that is different than the first aspect ratio of the one or more non-gallery cards, wherein the first direction and the second direction are perpendicular.

24. The method of claim 1, wherein:

each of the card descriptors includes at least one style or attribute that is applied at a card level;

at least some of the one or more component descriptor(s) selectively define at least one style or attribute that is applied at a component container level;

all of the styles and attributes included in the wrap package are applied at one of a wrap level, the card level, or the component container level.

25. The method of claim 1, wherein no markup language tags are used in the wrap descriptor.

26. The method of claim 1, wherein no executable code or scripts are used in the wrap descriptor.

27. The method of claim 1, wherein the runtime instance of the wrap package is generated on the computing device from the delivered wrap descriptor by either:

(c) creating an object graph from the wrap descriptor, generating a document object model from the object graph and generating the runtime instance of the cards of the wrap package from the document object model;

or

(d) by a native application running on the consuming device by generating the runtime instance of the wrap package from the wrap descriptor.

28. The method of claim 1, wherein the component container(s) defined by the one or more component descriptor(s) are each selectively configured to include one of the following:

(c) a document;

(d) text;

(e) an image/photo

(f) a video;

(g) a link;

(h) location/GPS information;

(i) a widget;

(j) a data feed;

(k) an application function; and

/or

(l) a transaction function.

29. The method of claim 1, wherein the fixed aspect ratio of each card, the immutable position of the content within the immutable layout of each of the cards, and the arrangement of the plurality of cards to be browsed in the one or more directions, results in the runtime instance of the wrap package having a same presentation regardless of the type or class of the computing device or the rendering environment provided within the associated display.

30. The method of claim 1, wherein, the wrap descriptor is a portable data-interchange object that is deliverable to the computing device over a network.