EP2656522A1

EP2656522A1 - Usage data feedback loop

Info

Publication number: EP2656522A1
Application number: EP11851060.1A
Authority: EP
Inventors: Lee Douglas SHARTZER; Kenneth Alan RUDMAN; Dan Han DIEP; Samir M. AHMED; James Earl BOOTH
Original assignee: Thomson Licensing SAS
Current assignee: InterDigital CE Patent Holdings SAS
Priority date: 2010-12-22
Filing date: 2011-12-20
Publication date: 2013-10-30
Also published as: KR101890448B1; JP2014507830A; KR20130131411A; JP6001554B2; BR112013015937A2; EP2656522A4; WO2012088084A1; CN103392307A

Abstract

The invention is related to the idea of tracking user navigation, consumption, and/or behavior and applying analytics to help shape future offerings (customized offerings, up-sells, recommendations, etc) to a user and to provide reporting data to service providers and studios. Methods and systems of providing viewing recommendations for a user are set forth. This involves collecting usage data related to a session of interaction by the user; processing the user data for the session; and providing feedback regarding the session. The sessions involve multiple stages tracking a user's interactions. These include stage such as an inquiry stage, a results stage, a details stage, a selection stage; and a confirmation stage.

Description

USAGE DATA FEEDBACK LOOP

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of U.S. Provisional Application Serial No. 61/459,986 filed December 22, 2010, which is incorporated by reference herein in its entirety.

Technical Field

The present invention generally relates to personalization features, and more particularly the gathering of user data feedback to improve personalization.

Background

Traditional usage tracking on media devices tends to focus on the resulting content selection from a limited number of sources. These systems do not track the process of how the selected content was arrived at.

For example, the Nelson rating system just tracks what broadcast television shows are being watched. One limitations of this type of system is that it doesn't track or otherwise account for other types of media (DVR recordings, VOD selections, internet content, etc) that may be selected and/or viewed in place of broadcast television. Another limitation is that the system does not provide any insight as to how or why particular content is selected and/or viewed.

Summary

The invention is related to the idea of tracking user navigation, consumption, and/or behavior and applying analytics to help shape future offerings (customized offerings, upsells, recommendations, etc...) to a user and to provide reporting data to service providers and studios. In accordance with one embodiment, a method of providing viewing recommendations for a user is provided. The method comprises collecting usage data related to a session of interaction by the user, processing the user data for the session, and providing feedback regarding the session. In certain embodiments the session comprises an inquiry stage, a results stage, a details stage, a selection stage; and a confirmation stage.

In accordance with another embodiment a system for providing viewing

recommendations for a user is provided. The system comprises a front end and a back end. The front-end is configured to collect usage data related to a session of interaction by the user. The back-end is configured to process the user data for the session and provide feedback regarding the session.

Brief Description of the Drawings

Figure 1 is a system diagram outlining the delivery of video and audio content to the home in accordance with one embodiment.

Figure 2 is system diagram showing further detail of a representative set top box receiver.

Figure 3 is a diagram depicting a touch panel control device in accordance with one embodiment.

Figure 4 is a flow diagram depicting an exemplary process in accordance with one embodiment.

Figure 5 is a system diagram depicting an Aggregator system in accordance with one embodiment. Figure 6 is a flow diagram depicting an exemplary process in accordance with one embodiment.

Figure 7 is a system diagram outlining the inter-workings of an aggregation module in accordance with one embodiment. Figure 8 is a flow diagram depicting an exemplary process in accordance with one embodiment.

Detailed Description

Turning now to Figure 1, a block diagram of an embodiment of a system 100 for delivering content to a home or end user is shown. The content originates from a content source 102, such as a movie studio or production house. The content may be supplied in at least one of two forms. One form may be a broadcast form of content. The broadcast content is provided to the broadcast affiliate manager 104, which is typically a national broadcast service, such as the American Broadcasting Company (ABC), National

Broadcasting Company (NBC), Columbia Broadcasting System (CBS), etc. The broadcast affiliate manager may collect and store the content, and may schedule delivery of the content over a deliver network, shown as delivery network 1 (106). Delivery network 1 (106) may include satellite link transmission from a national center to one or more regional or local centers. Delivery network 1 (106) may also include local content delivery using local delivery systems such as over the air broadcast, satellite broadcast, or cable broadcast. The locally delivered content is provided to a receiving device 108 in a user's home, where the content will subsequently be searched by the user. It is to be appreciated that the receiving device 108 can take many forms and may be embodied as a set top box/digital video recorder (DVR), a gateway, a modem, etc. Further, the receiving device 108 may act as entry point, or gateway, for a home network system that includes additional devices configured as either client or peer devices in the home network.

A second form of content is referred to as special content. Special content may include content delivered as premium viewing, pay-per-view, or other content otherwise not provided to the broadcast affiliate manager, e.g., movies, video games or other video elements. In many cases, the special content may be content requested by the user. The special content may be delivered to a content manager 110. The content manager 110 may be a service provider, such as an Internet website, affiliated, for instance, with a content provider, broadcast service, or delivery network service. The content manager 110 may also incorporate Internet content into the delivery system. The content manager 110 may deliver the content to the user's receiving device 108 over a separate delivery network, delivery network 2 (112). Delivery network 2 (112) may include high-speed broadband Internet type communications systems. It is important to note that the content from the broadcast affiliate manager 104 may also be delivered using all or parts of delivery network 2 (112) and content from the content manager 110 may be delivered using all or parts of delivery network 1 (106). In addition, the user may also obtain content directly from the

Internet via delivery network 2 (112) without necessarily having the content managed by the content manager 110.

Several adaptations for utilizing the separately delivered content may be possible. In one possible approach, the special content is provided as an augmentation to the broadcast content, providing alternative displays, purchase and merchandising options, enhancement material, etc. In another embodiment, the special content may completely replace some programming content provided as broadcast content. Finally, the special content may be completely separate from the broadcast content, and may simply be a media alternative that the user may choose to utilize. For instance, the special content may be a library of movies that are not yet available as broadcast content.

The receiving device 108 may receive different types of content from one or both of delivery network 1 and delivery network 2. The receiving device 108 processes the content, and provides a separation of the content based on user preferences and commands. The receiving device 108 may also include a storage device, such as a hard drive or optical disk drive, for recording and playing back audio and video content. Further details of the operation of the receiving device 108 and features associated with playing back stored content will be described below in relation to Figure 2. The processed content is provided to a display device 114. The display device 114 may be a conventional 2-D type display or may alternatively be an advanced 3-D display. The receiving device 108 may also be interfaced to a second screen such as a touch screen control device 116. The touch screen control device 116 may be adapted to provide user control for the receiving device 108 and/or the display device 114. The touch screen device 116 may also be capable of displaying video content. The video content may be graphics entries, such as user interface entries, or may be a portion of the video content that is delivered to the display device 114 The touch screen control device 116 may interface to receiving device 108 using any well known signal transmission system, such as infra-red (IR) or radio frequency (RF) communications and may include standard protocols such as infra-red data association (IRDA) standard, Wi-Fi, Bluetooth and the like, or any other proprietary protocols. Operations of touch screen control device 116 will be described in further detail below. The receiving device 108 and touch screen control device 116 make up a front end.

In the example of Figure 1, the system 100 also includes a back end including a server 118 and a usage database 120. The back end server 118 includes a personalization engine that analyzes the usage habits of a user and makes recommendations based on those usage habits. The usage database 120 is where the usage habits for a user are stored. In some cases, the usage database 120 may be part of the back end server 118 a. In the present example, the back end server 118 (as well as the usage database 120) is connected to the system the system 100 and accessed through the delivery network 2 (112).

Turning now to Figure 2, a block diagram of an embodiment of a receiving device 200 is shown. Receiving device 200 may operate similar to the receiving device described in Figure 1 and may be included as part of a gateway device, modem, set-top box, or other similar communications device. The device 200 shown may also be incorporated into other systems including an audio device or a display device. In either case, several components necessary for complete operation of the system are not shown in the interest of conciseness, as they are well known to those skilled in the art. In the device 200 shown in Figure 2, the content is received by an input signal receiver 202. The input signal receiver 202 may be one of several known receiver circuits used for receiving, demodulation, and decoding signals provided over one of the several possible networks including over the air, cable, satellite, Ethernet, fiber and phone line networks. The desired input signal may be selected and retrieved by the input signal receiver 202 based on user input provided through a control interface or touch panel interface 222. Touch panel interface 222 may include an interface for a touch screen device. Touch panel interface 222 may also be adapted to interface to a cellular phone, a tablet, a mouse, a high end remote or the like.

The decoded output signal is provided to an input stream processor 204. The input stream processor 204 performs the final signal selection and processing, and includes separation of video content from audio content for the content stream. The audio content is provided to an audio processor 206 for conversion from the received format, such as compressed digital signal, to an analog waveform signal. The analog waveform signal is provided to an audio interface 208 and further to the display device or audio amplifier. Alternatively, the audio interface 208 may provide a digital signal to an audio output device or display device using a High-Definition Multimedia Interface (HDMI) cable or alternate audio interface such as via a Sony/Philips Digital Interconnect Format (SPDIF). The audio interface may also include amplifiers for driving one more sets of speakers. The audio processor 206 also performs any necessary conversion for the storage of the audio signals.

The video output from the input stream processor 204 is provided to a video processor 210. The video signal may be one of several formats. The video processor 210 provides, as necessary a conversion of the video content, based on the input signal format. The video processor 210 also performs any necessary conversion for the storage of the video signals.

A storage device 212 stores audio and video content received at the input. The storage device 212 allows later retrieval and playback of the content under the control of a controller 214 and also based on commands, e.g., navigation instructions such as fast- forward (FF) and rewind (Rew), received from a user interface 216 and/or touch panel interface 222. The storage device 212 may be a hard disk drive, one or more large capacity integrated electronic memories, such as static RAM (SRAM), or dynamic RAM (DRAM), or may be an interchangeable optical disk storage system such as a compact disk (CD) drive or digital video disk (DVD) drive.

The converted video signal, from the video processor 210, either originating from the input or from the storage device 212, is provided to the display interface 218. The display interface 218 further provides the display signal to a display device of the type described above. The display interface 218 may be an analog signal interface such as red- green-blue (RGB) or may be a digital interface such as HDMI. It is to be appreciated that the display interface 218 will generate the various screens for presenting the search results in a three dimensional gird as will be described in more detail below.

The controller 214 is interconnected via a bus to several of the components of the device 200, including the input stream processor 202, audio processor 206, video processor 210, storage device 212, and a user interface 216. The controller 214 manages the conversion process for converting the input stream signal into a signal for storage on the storage device or for display. The controller 214 also manages the retrieval and playback of stored content. Furthermore, as will be described below, the controller 214 performs searching of content and the creation and adjusting of the gird display representing the content, either stored or to be delivered via the delivery networks, described above.

The controller 214 is further coupled to control memory 220 (e.g., volatile or nonvolatile memory, including RAM, SRAM, DRAM, ROM, programmable ROM (PROM), flash memory, electronically programmable ROM (EPROM) , electronically erasable programmable ROM (EEPROM), etc.) for storing information and instruction code for controller 214. Control memory 220 may store instructions for controller 214. Control memory may also store a database of elements, such as graphic elements containing content. The database may be stored as a pattern of graphic elements. Alternatively, the memory may store the graphic elements in identified or grouped memory locations and use an access or location table to identify the memory locations for the various portions of information related to the graphic elements. Additional details related to the storage of the graphic elements will be described below. Further, the implementation of the control memory 220 may include several possible embodiments, such as a single memory device or,

alternatively, more than one memory circuit communicatively connected or coupled together to form a shared or common memory. Still further, the memory may be included with other circuitry, such as portions of bus communications circuitry, in a larger circuit.

The user interface process of the present disclosure employs an input device that can be used to express functions, such as fast forward, rewind, etc. To allow for this, a touch panel device 300 may be interfaced via the user interface 216 and/or touch panel interface 222 of the receiving device 200, as shown in Figure 3. The touch panel device 300 allows operation of the receiving device or set top box based on hand movements, or gestures, and actions translated through the panel into commands for the set top box or other control device. In one embodiment, the touch panel 300 may simply serve as a navigational tool to navigate the gird display. In other embodiments, the touch panel 300 will additionally serve as the display device allowing the user to more directly interact with the navigation through the grid display of content. The touch panel device may be included as part of a remote control device containing more conventional control functions such as activator buttons. The touch panel 300 can also includes at least one camera element. Figure 4 depicts a flow diagram 400 of the process involved in providing user data feedback as described in this disclosure. The process involves collecting or obtaining usage data (step 410), processing the usage data (step 420), and providing feedback (step 430). Each of these steps will be discussed in more detail below. Pursuant to the first step of Figure 4, data regarding the usage habits of a user is collected. The usage information can include information collected at the front end from the receiving device 108 and the touch screen control device 116. The type of information collected my include channels watched on the display device 114, the time the channels where watched, how long the channel was watched, the type of program on the channel, information about the program watched (e.g. genre, director, actor, etc.); what was viewed on the touch screen control device 116 (i.e. program guide, additional program information, websites, applications, etc.); what time content was viewed on the touch screen control device 116, how long the content was viewed, and information about the content watched (type of content, genre, etc.). There are other types of data and behaviors that can be tracked as well. For example, a subscriber's migratory behavior can be tracked from media source to media source and from media to media. Consider an example, where a user is watching a television program delivered from a network service provider such as Comcast. The user then changes their media selection to an over the top media service provider (such as Netflix). The described system can tracks the two media selections (television show, movie) the source of such media selections (Comcast, Netflix, and the like), and the time spent using/watching each media selection.

This current example provides meaningful information in that in with many network service providers, over the top services, personal media servers, broadcast sources, cable sources, satellite sources, IPTV sources, websites, on-line sources that supply media (such as Amazon, Emusic, ITunes, and the like), there is value to keeping track of: a. What sources exist for a particular media selection b. Tracking what source the media selection comes from. c. Tracking whether a media source that is accessed, was suggested by the system. d. Tracking whether a user purchases a media selection from a specific source, (clickthrough) e. Tracking if a user went to a particular source to look at a media selection that was selected, but was not purchased. f. Tracking the amount of time a user accessing/watches a media selection from a particular source. g. Tracking whether a user is responsive to a particular advertisement and the source of such an advertisement (local/network operator/over the top service/broadcaster, etc.). h. Tracking what version of a particular media asset was selected, and the source. a. Low v. High Resolution/ SD/HD b. Bitrate of the Media Asset c. Regular Version v. Special Features d. How long where the "Special Features" accessed e. Whether advertisements embedded or pushed into the media asset are selected. i. Keeping track of what application was used for selecting a media asset, and for how long it took to get to a particular media asset: a. Search Engine b. Electronic Program Guide c. Advertisement d. Social Networking Recommendation from a Friend

It is expected that other attributes can be tracked as well and delivered in a report, where such attributes can be group together. This information may be collected and aggregated by an Aggregator system such as seen in Figure 5 The Aggregation EAR file 500 contains both SpectrumCommon JAR module 510 and Aggregation WAR module 520. The SpectrumCommon module JAR 510 is a shared module to obtain errors codes, error messages and logging services. Aggregation module 520 is an internal API to aggregate the collected customer usage data on device and later the gathered logs are used for reporting. Aggregated user data can then be sent to and saved in the database 120 and used for report generation.

Examples of properties recorded for user activity logging include: Timestamp; Household ID, User ID, Device ID, Session ID, Application ID, Action Type, as well as other parameters associated with the Action Type. This information is provided in log messages having the format:

where:

• <Timestamp> format is "yyyy-mm-dd hh:mi:ss.millis"

• <ActionType> is one of the values in the RP_ACTION_TYPE table (see Database Schema Design section for values)

• <MsgParams> are message specific key value pairs delimited by a ";" character. Key value pairs are delimited by a ":" character.

An example of such a log message for an acquire action would look as follows: ACQUIRE Log Message

2010-10-12 16:52:12.0141 Householdl231 beOl | dev4561 Sessl231 AppOOl | ACQUIRE |

ITEM_ID:987;ITEM_TYPE:VOD;OFFER_ID:Offerl23; PROVIDER:NETFLIX ; ACQUI E_SOU CE:SEA CH;ACQUI E_TYPE:BUY;P ICE:7.99;CU ENCY:USD;STATUS:SUCCESS;

The aggregation module provides log messages in response to a request such as:

• CollectUserData

o Request: List of log messages

o Response: Boolean true value (even if web service processing failure)

The web service request is parsed to extract individual log messages. Each individual log message is parsed to extract user information, device information, activity type, and key value pairs of activity type specific data. Each key value pair of data is stored in a database table. The current implementation processes and parses all the log record data in each web service request before returning the web service response.

Database Schema Design The reporting database schema design will be based on a modified Entity- Attribute-

Value (EAV) model also known as "sparse matrix". This model will store each log message attribute value pair as a separate row in another table. This approach involves minor changes to the existing reporting database schema such as removing OFFER_ID and CONTENTJD columns from the RP_LOG table.

RP_LOG Table

LOG_ID NUMBER LOG_DATE TIMESTAMP HOUSEHOLD_ID VARCHAR2 (20 CHAR) USER_ID VARCHAR2 (20 CHAR)

DEVICE_ID VARCHAR2 (20 CHAR) SERVICEJD VARCHAR2 (20 CHAR) SESSION_ID NUMBER ACTION_TYPE_ID NUMBER (FK to RP_ACTION_TYPE table)

The OFFER_ID and CONTENT_ID columns have been removed since they are only used for ACQUIRE messages. These attributes will be added to the RP_INFORMATION table.

RP_LOG_INFORMATION Table

LOG_ID NUMBER (FK to RP_LOG table)

INFORMATIONS NUMBER (FK to RP_INFORMATION table)

LOG_INFORMATION_ VALUE VARCHAR2 (512 CHAR)

RP_INFORMATION Table

INFORMATIONS NUMBER

INFORMATION_NAME VARCHAR2 (20 CHAR)

INFORMATION_DEFINITION VARCHAR2 (200 CHAR)

This table should contain records for all the key parameters (ID and names)

3 ITEM_TYPE Item type

4 OFFER_ID Offer ID

5 ACQUIRE_SOURCE Acquire source

(SEARCH/RECOMMEND)

6 ACQUIRE_TYPE Acquire type (BUY/RENT)

7 PRICE Acquire price

8 CURRENCY_TYPE Currency type

9 STATUS Status (SUCCESS/FAIL/CANCEL)

10 SEARCH_CRITERIA Search criteria

11 FRIEND_ID Friend ID

12 FRIEND_ACTION Friend action

(ADD/DELETE/ ACCEPT_INVITE/ S END_INVITE/SEARCH)

13 CONTENT_POSITIO Content position (HH:MI:SS format)

N

14 DEVICE_TYPE Device type (TABLET/TV)

15 CHANNEL_ID Channel ID

16 UNKNOWNJNFO Unknown info

17 DVR_ ACTION DVR action

(DELETE/SAVE_UNTIL)

18 FILE_DOWNLOAD 3rd party application download info

19 PROVIDERJD Provider ID (YOUTUBE, NETFLIX,

NSP)

RP_ACTION_TYPE Table

ACTION_TYPE_ID NUMBER ACTION_TYPE VARCHAR2 (20 CHAR) This table should contain records for all the activity names such as ACQUIRE, SEARCH, VIEWCHANNEL, PLAY, FASTFORWARD, REVERSE, PAUSE, etc. Additional action names are TBD.

RP_APPLICATION Table APP_ID NUMBER APP_DESCRIPTION VARCHAR2 (20 CHAR)

Figure 6 depicts the collection of user activity data by aggregation system using the CollecUserData operation 600. Here the request 610 is made by an External Web Service client 620, which can be located at Back end Server 118. The request is received by the aggregation skeleton 620 of the aggregation module which is located on receiving device 108 or the second screen 116. The aggregation skeleton 630 responds with a Boolean Value 640. An example of inter-workings of the aggregation module can be seen in Figure 7.

Figure 7 depicts a system 700 showing the intercommunication by the SpectrumCommon Jar 510 and the Aggregation WAR 520. The SpectrumCommon module 510 provides logging services, error codes, and error messages to Aggregation module 520. The aggregation skeleton 620 using the aggregation skeleton interface 710 receives a CoUectUSerData request 610 and parses through the LocalLogList 720 and LocalLog 730 for LogListType 740 and LogType 750. A response 640 to the CollectUserData request is then returned.

The following user activities in the Flash/Flex applications can be logged:

Application User Activity Parameters

Application start Timestamp

Householdld

Notes: Use same message for Userld

Spectrum shell start, Spectrum app

start, and 3^rd party application start Deviceld

Sessionld

Application^

Itemld

ItemType (VOD, TV_P OG AM, APP, CLIP, other types

TBD)

Application end Timestamp Application User Activity Parameters

Householdld

Notes: Use same message for Userld

Spectrum shell start, Spectrum app

start, and 3^rd party application start Deviceld

Sessionld

Application^

Screen saver start Timestamp

Householdld

Userld

Deviceld

Sessionld

Application^

Screen saver end Timestamp

Householdld

Userld

Deviceld

Sessionld

Application^

Acquire Timestamp

Householdld

Userld

Deviceld

Sessionld

Application^

Itemld

ItemType (VOD, TV_PROGRAM, APP, CLIP, other types

TBD)

Offerld

Providerld (YOUTUBE, NETFLIX, NSP, other types are Application User Activity Parameters

TBD)

AcquireSource (SEARCH, RECOMMEND)

AcquireType (BUY, RENT)

Price

Currency

Status (SUCCESS, FAIL, CANCEL)

Search Timestamp

Householdld

Userld

Deviceld

Sessionld

Applicationld

Search term

Share Timestamp

Householdld

Notes: This is a separate activity Userld

message instead of using

User Action message since friendld Deviceld

parameter is needed.

Sessionld

Applicationld

Itemld

ItemType

Friendld

UserAction Timestamp

Householdld

Notes: This message is used for Userld

common user activities (rate and

social messaging) that can be Deviceld

accessed from multiple places in

Sessionld

the application and which don't

require additional message Application User Activity Parameters

parameters. Applicationld

Itemld

ItemType (VOD, TV_PROGRAM, APP, CLIP, other types TBD)

ActionType (RATE, SOCIAL_MESSAGE, etc)

ManageLibrary Timestamp

Householdld

Userld

Deviceld

Sessionld

Applicationld

Itemld

ItemType (VOD, TV_PROGRAM, APP, CLIP, other types TBD)

ActionType (ADD_COLL, DELETE_COLL,

ADD_COLL_ITEM, DELETE_COLL_ITEM)

ManageFriend Timestamp

Householdld

Userld

Deviceld

Sessionld

Applicationld

Action (ADD, DELETE, ACCEPTJNVITE, SENDJNVITE, SEARCH, other types TBD)

Mirror (throw to TV) Timestamp

Householdld

Userld

Deviceld

Sessionld Application User Activity Parameters

Application^

Itemld

ItemType (VOD, TV_PROGRAM, APP, CLIP, other types TBD)

Content position

FileDownload (3^rd party apps) Timestamp

Householdld

Userld

Deviceld

Sessionld

Application^

Itemld

ItemType (VOD, TV_PROGRAM, APP, CLIP, other types

TBD)

DVR activity may also be logged. This includes:

Key presses on the remote control

DVR recording management

Parameters

Timestamp

Householdld

Userld

Deviceld

Sessionld

Application^

DeviceType (TABLET, TV)

Itemld

ItemType (VOD, TV_PROGRAM, APP, CLIP, other types DVR User Activity Parameters

TBD)

Providerld (YOUTUBE, NETFLIX, NSP, other types are TBD)

Content position

Pause Timestamp

Householdld

Userld

Deviceld

Sessionld

Application^

DeviceType (TABLET, TV)

Itemld

ItemType (VOD, TV_PROGRAM, APP, CLIP, other types TBD)

Content position

Fast forward Timestamp

Householdld

Userld

Deviceld

Sessionld

Application^

DeviceType (TABLET, TV)

Itemld

ItemType (VOD, TV_PROGRAM, APP, CLIP, other types TBD)

Content position

Reverse Timestamp

Householdld

Userld DVR User Activity Parameters

Deviceld

Sessionld

Application^

DeviceType (TABLET, TV)

Itemld

ItemType (VOD, TV_PROGRAM, APP, CLIP, other types TBD)

Content position

Stop Timestamp

Householdld

Userld

Deviceld

Sessionld

Application^

DeviceType (TABLET, TV)

Itemld

ItemType (VOD, TV_PROGRAM, APP, CLIP, other types TBD)

Content position

ViewTVStart Timestamp

Householdld

Userld

Deviceld

Sessionld

Application^

Channelld

ViewTVEnd Timestamp

Householdld DVR User Activity Parameters

Userld

Deviceld

Sessionld

Application^

Channelld

ManageDV ecording Timestamp

Householdld

Userld

Deviceld

Sessionld

Applicationld

Itemld

ItemType (VOD, TV_PROGRAM, APP, CLIP, other types

TBD)

Action (DELETE, SAVEJJNTIL, other types TBD)

An example of a transaction using a CollectUserData JSON Request can be seen below

{

"userLog": {

"authToken":"?", "logs":[ {

"log":"2010-10-1216:52: 12.014IHouseholdl23lbe01ldev456ISessl23l

App001IACQUIREIITEM_ID:987;ITEM_TYPE:VOD;OFFER_ID:Offerl23;PROVIDER:NETFLI X;ACQUIRE_SOURCE:SEARCH;ACQUIRE_TYPE:BUY;PRICE:7.99;CURRENCY:USD;STAT US:SUCCESS;" {

"log":"2010-10-1216:52: 12.014IHouseholdl23lbe01 ldev456ISessl23l

App001 IACQUIREIITEM_ID:987;ITEM_TYPE:VOD;OFFER_ID:Offerl23;PROVIDER:NSP;AC QUIRE_SOURCE:SEARCH;ACQUIRE_TYPE:RENT;PRICE:2.99;CURRENCY:USD;STATUS:S UCCESS;"

}

1

}

An example of a CollectUserData JSON Response is:

{

"status" :"true"

}

One concept used in the collection of user data is that of a "session." A "session" is a collection of actions by a user that make a particular interaction between the user and the device. For example session may include all the action a user took to watch a particular piece of media. Figure 8 provides a flow chart 800 of one example of the process a session can involve.

In figure 8, there are five stages or steps to a session (800). These stages are inquiry (810), results(820), details(830), selection (840), and confirmation (850). Each of these stages will be discussed in more detail below. The inquiry stage (810) initiates the session. The inquiry stage can be thought of as analogous to the beginning of a users interaction with the device in which the user seek to answer the question "what is can I watch" For example, an inquiry may be a search on a particular topic, a request for listing of VOD offerings, a request for a EPG, or a request for listing of previously recorded programs. Any such activity starts the session and is logged as part of the session. In response to an Inquiry of the inquiry step ( step 810) results are provided for the user to review (step 820). The results could be the results of the search performed, the listing of available VOD offerings, the EPG, or the listing of previously recorded programs. The results can also include recommendations based on the user or device. In other embodiments the results provided can be filtered based on the user or device. The results provided to user are logged as part of the session. Based on the provided results the user can make a new inquiry (step 810) beginning a new session or get additional details (step 830) about the provided results.

The details step (step 830) involves the user being provided with and reviewing additional information about the provided results (step 820). The additional information can be plot summaries, cast and crew listings, ratings, etc. The additional information may also include trailers, video clips, and special promotional listings and offers. Again the additional information viewed by the user is logged as part of the session. After reviewing the additional information for a result the user may then make a new inquiry (step 810), review other results (step 820) or make a selection (step 840). The selection stage (step 840) involves the choice of content by the user to watch.

This may be a currently playing program, a VOD offering, downloadable content, a program previously recorded, or the like. When content is selected the user is then informed of what is necessary to view the content such as tuning the particular channel, starting the stream, starting the download, playing back from the recoding, as well as any pricing/purchasing information. This selection is logged as part of the session. The user again has the option of performing a new inquiry (step 810), returning to the results (step 820) or confirming the selection of the content (step 850).

Confirmation (step 850) involves the actually acquisition of the content including purchasing, tuning to the channel, downloading, etc. This is also where the user agrees to the terms in order to view the selected content. Any agreement to terms and acquisition is logged as part of the session and also concludes the session. Once usage data is collected (step 410), the usage data is provided to the back end where it can be processed (step 420) to build a user profile. The use of sessions allows for the tracking of not just content selection but the path pursued to arrive at the content selection. Thus it can be determined what inquiries, results, details, and acquisition requirements result in selection and consumption of content as well as what inquires results, details and acquisitions requirement can prevent the selection and consumption of content. By knowing what the user selects for viewing as well as how the user arrived at the selection, feedback can be provided (step 430) to evaluate the effectiveness of searches, recommendations, additional information, and pricing in the section of content by the user. The feedback may also be used to improve each stage of an acquisition session.

For example, results and recommendations, additional information, and acquisition requirements such as cost or rental terms can be adjusted in future session to improve "buy" selections by the user. Likewise this information can be used to improve/refine targeted advertising, including special offers. Other possible uses for the techniques discussed herein include.

1. Deciding where a user should be shown selections. I.e., it can be more likely that a user will end up buying VOD programming if it is suggestion made by the personalization engine, instead of the media asset being advertised at the bottom of an EPG banner advertisement.

2. Changing the order in which results in a search are made, based on the tracking information. For example, a search result from IMDB may be acted on more frequently by a user than Amazon. Also, what is shown in the search results (showing movie title first and actor second for a first user, and showing actor first and the movie title second, for a second user, based on user's tendencies).

3. Understanding the type of content a user seems to gravitate towards (e.g., action movies with cars, airplanes or travel programming with beaches, etc...) to provide a level of relevancy in content offerings and also up-sell services that range from premium programming (The air channel) to physical merchandize (a Ferrari F- 40 model vehicle). 4. Trending the purchase history of content for users and comparatively view other users in a peer group to, for example, track both the user and the peer group's reactions to marketing strategies. For example, a peer group in Beverly Hills may react favorably to a platinum tier programming package at $29.99 vs. a group elsewhere that maybe more interested in the same or slightly variant package at $12.99. Pricing effectiveness of marketing strategies can be measured on an individual basis as well.

A. User searches for Iron Man. Not currently available but user is proved with offer to purchase the latest Spiderman movie for $30, to rent the Hulk (circa 2008) for $6, or to rent the Hulk (circa 2003) for $4.00. User selects to rent Hulk (circa 2008). purchase data is stored that may (along with other tracked data) indicate the user's tendency to rent rather than buy and/or desire to view movies associated with the upcoming Avengers movie (circa 2012).

B. can track when a user is more likely to rent or purchase. For example, a user's consumption habits may reveal that the user is 80% more likely to rent a movie but 75% more likely to purchase a TV episode. This information can be used to shape future offers to the user.

C. Tracking and analyzing price resistance. Assisting content provider in

understanding user's decision making (i.e., was it the price of the movie or was it the time of day). Offer the same movie at different prices and different times of day to assist content provider in setting price for movie and understanding what caused purchase.

5. Provides a portal that bridges broadcast, VOD, over the top and user generated programming. As a result, can provide industry first programming measurement capabilities and effectiveness across the multiple sources of available content. That is, the research and the preference engine will go between applications and services which typically are not monitored (i.e., user spends 20% of their time watching TNT, 30% on Yahoo.com, 50% of their time watching Hulu.com). 6. May push user to a different source of the same content based on the user subscription. For example, User A may have a premium subscription ($150/month) and User B may just have a basic subscription ($45/month). If desired content (e.g., recent movie) is available both on a premium movie channel and on VOD, Spectrum would direct User A to the premium movie channel and User B to VOD. This would at least reduce the risk of User A dropping the premium subscription b/c the user is repeatedly directed to VOD offerings.

8. Methodology behind periodically reminding the user of what movies and television shows are stored in the digital locker. The system can remind the user that they already have such content archived on their personal locker. -

A. Consider possibility of having the reminder be that the content is available in a second person's digital locker (my wife has her own digital locker, and I want to access the content in the locker).

B. Making available through other people's lockers, content that can be freely distributed (home movies, YouTube content, etc.)

9. Tracking when a user repeatedly rents and views a movie and offering the user the option to buy the same movie or a related movie.

A. Consider a model where the more the user has rented a movie, the less costly the movie rental becomes, until the user has paid for it enough times that it gets uploaded to their digital locker for free.

B. Consider also the idea that if there is a series of movies to be rented, the first movie rented (Godfather I) is 5.00, (Godfather II) is 3.00, (Godfather III) is

1.00. This option can also apply for buying programs in a series (first episode 3.00, 2^nd episode 2.00, 3^rd 1.00).

10. Track users' use of recommendations. For example, user A may be 35% more likely to follow a friend's recommendation as opposed to a recommendation from a recommendation engine and User B may be 40% more likely to follow a recommendation from a recommendation engine as opposed to a friend' s recommendation. Spectrum can track this behavior and use it to prioritize recommendations made to different users.

11. Track explicit ratings (user given rating "4 stars") and implicit ratings (# of views, #of times given scenes are viewed, # of times user recommends content to friends, etc...) to determine what is recommended to a user. For example, a user gives Rocky a 5 star rating but only views Rocky once and never recommends the movie to a friend. The same user gives Twilight a 2 star rating but views the movie in its entirety 3 times, a particular scene in the movie 9 times, and recommends the movie to 10 friends. Based on this history, New Moon would be recommended to the user before recommending Rocky 2.

A. Concept considers the idea that people do not rate movies fairly, where a 5 star movie may not really be 5 stars for everything. Therefore, one has to consider the actual interaction a user has with a media asset aside for the explicit rating that is given to the asset.

B. Different algorithms can be developed that determines a rating by using both explicit (what the user rated a media asset) and implicitly (how the user interacts with the media asset).

12. Tracking when and where a user views a movie and using this context information to adjust what is offered to the user in different rooms and at different times (e.g., offering different recommendation for viewing in the living room at 1 pm as opposed to the bed room at 9 pm). -

A. User can specify which device is where. B. Define also what device, as well. Set top box, cell phone, Ipad, computer, and the like.

While the example set forth above has focused on a system, it should be understood that the present invention can also be embedded in a computer program product, which comprises all the features enabling the implementation of the methods described herein, and which, when loaded in a computer system, is able to carry out these methods. Computer program or application in the present context means any expression, in any language, code or notation, of a set of instructions intended to cause a system having an information processing capability to perform a particular function either directly or after either or both of the following a) conversion to another language, code or notation; b) reproduction in a different material form.

Additionally, the description above is intended by way of example only and is not intended to limit the present invention in any way, except as set forth in the following claims.

Claims

1. A method of providing viewing recommendations for a user, the method comprising: collecting usage data related to a session of interaction by the user;

processing the user data for the session; and

providing feedback regarding the session.

2. The method of claim 1, wherein the usage data relates to a content viewed by the user.

3. The method of claim 2, wherein the usage data related to content viewed by the user comprises one or more of: content viewed; time the content was viewed; how long the content was viewed; type of content viewed; information about the content viewed; source of the content; and what device was the content viewed on.

4. The method of claim 1 wherein the step of collecting user data is performed using an aggregation module.

5. The method of claim 1 wherein the session comprises the stages of: inquiry stage;

results stage;

details stage;

selection stage; and

confirmation stage.

6. The method of claim 5, wherein the inquiry stage comprises a search performed by the user.

7. The method of claim 6, wherein user data related to the inquiry stage comprises the topic of the search performed by the user.

8. The method of claim 5, wherein user data related to the results stage comprises data returned based on user input during inquiry stage.

9. The method of claim 5, wherein the results stage comprises providing one or more of: results of a search performed; listings of Video on Demand (VOD) offerings, listings of previously recorded programs; and listings in an Electronic Program Guide (EPG).

10. The method of claim 9, wherein the results are filtered based on user and/or device.

11. The method of claim 5, wherein user data related to the details stage comprises additional details regarding the data returned based on user input during inquiry stage.

12. The method of claim 5, wherein the details stage comprises providing one or more of: plot summaries; cast and crew listings; ratings; trailers; video clips; and promotional listings and offers.

13. The method of claim 5, wherein the selection stage comprises:

receiving a user selection of content to be viewed;

providing information regarding requirements to view content.

14. The method of claim 13, wherein the information regarding requirements to view content comprises pricing information.

15. The method of claim 13, wherein user data related to the selection stage comprises the content selected by the user.

16. The method of claim 5, wherein the confirmation stage comprises acquisition of content to be viewed.

17. The method of claim 16, wherein the acquisition of content further comprises receiving acceptance of terms by user to acquire content.

18. The method of claim 17, wherein user data related to the confirmation stage comprises data relating to the acquisition of content.

19. The method of claim 1, wherein the step of providing feedback comprises generating a user profile.

20. The method of claim 1, further comprising: modifying data of a session based on provided feedback.

21. A system providing viewing recommendations for a user, the system comprising: a front-end configured to collect usage data related to a session of interaction by the user;

a back end configured to process the user data for the session and provide feedback regarding the session.

22. The system of claim 21, the front end comprises a touch screen device.

23. The media system of claim 21, wherein the server comprises:

a personalization engine; and

a usage database.