WO2008015187A1 - User preferences in interactive personal television - Google Patents

User preferences in interactive personal television Download PDF

Info

Publication number
WO2008015187A1
WO2008015187A1 PCT/EP2007/057831 EP2007057831W WO2008015187A1 WO 2008015187 A1 WO2008015187 A1 WO 2008015187A1 EP 2007057831 W EP2007057831 W EP 2007057831W WO 2008015187 A1 WO2008015187 A1 WO 2008015187A1
Authority
WO
WIPO (PCT)
Prior art keywords
user
notification
service
message
sent
Prior art date
Application number
PCT/EP2007/057831
Other languages
French (fr)
Inventor
Mattias LIDSTRÖM
Theo Gerrit Kanter
Ignacio MAS IVÁRS
Johan Hjelm
Göran ERIKSSON
Michael ASTRÖM
Original Assignee
Telefonaktiebolaget Lm Ericsson (Publ)
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from PCT/EP2007/054075 external-priority patent/WO2008015033A1/en
Application filed by Telefonaktiebolaget Lm Ericsson (Publ) filed Critical Telefonaktiebolaget Lm Ericsson (Publ)
Priority to CA002665795A priority Critical patent/CA2665795A1/en
Publication of WO2008015187A1 publication Critical patent/WO2008015187A1/en

Links

Classifications

    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N7/00Television systems
    • H04N7/16Analogue secrecy systems; Analogue subscription systems
    • H04N7/173Analogue secrecy systems; Analogue subscription systems with two-way working, e.g. subscriber sending a programme selection signal
    • H04N7/17309Transmission or handling of upstream communications
    • H04N7/17318Direct or substantially direct transmission and handling of requests
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/23Processing of content or additional data; Elementary server operations; Server middleware
    • H04N21/236Assembling of a multiplex stream, e.g. transport stream, by combining a video stream with other content or additional data, e.g. inserting a URL [Uniform Resource Locator] into a video stream, multiplexing software data into a video stream; Remultiplexing of multiplex streams; Insertion of stuffing bits into the multiplex stream, e.g. to obtain a constant bit-rate; Assembling of a packetised elementary stream
    • H04N21/2362Generation or processing of Service Information [SI]
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/20Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/25Management operations performed by the server for facilitating the content distribution or administrating data related to end-users or client devices, e.g. end-user or client device authentication, learning user preferences for recommending movies
    • H04N21/258Client or end-user data management, e.g. managing client capabilities, user preferences or demographics, processing of multiple end-users preferences to derive collaborative data
    • H04N21/25866Management of end-user data
    • H04N21/25891Management of end-user data being end-user preferences
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/41Structure of client; Structure of client peripherals
    • H04N21/422Input-only peripherals, i.e. input devices connected to specially adapted client devices, e.g. global positioning system [GPS]
    • H04N21/42201Input-only peripherals, i.e. input devices connected to specially adapted client devices, e.g. global positioning system [GPS] biosensors, e.g. heat sensor for presence detection, EEG sensors or any limb activity sensors worn by the user
    • HELECTRICITY
    • H04ELECTRIC COMMUNICATION TECHNIQUE
    • H04NPICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/47End-user applications
    • H04N21/488Data services, e.g. news ticker
    • H04N21/4882Data services, e.g. news ticker for displaying messages, e.g. warnings, reminders

Definitions

  • the invention relates to the field of Interactive Personal Television.
  • Interactive Personal Television programming requires feedback from its audience.
  • audience feedback is real-time voting, in which an audience member can influence the programme being watched. The influence may be, for example, taking part in a vote or choosing a camera angle from which to view a sports event.
  • the audience member In order to provide this degree of interaction, the audience member must have a return path to transmit information to the programme broadcaster.
  • This return path may use suitable media, for example, telephone, SMS messaging or cable (where a user who receives a cable broadcast can transmit information to the broadcaster using the same cable as a return path).
  • OMA BCAST OMA-TS-BCAST_Services-Vl_0-20060419-D, section 5.3
  • OMA BCAST OMA-TS-BCAST_Services-Vl_0-20060419-D, section 5.3
  • Interactivity media objects can be sent in-band (i.e., with the television signal), or out- of-band.
  • An Interactive Personal Television programme is broadcast from a broadcast network and rendered on the user's television set.
  • An "interactivity media object" document containing some or all of the interaction elements is sent from the broadcaster over the broadcast network to the user's mobile device.
  • the interactivity media object displays an indication that voting is available on the screen of the end-user's device (for example a mobile telephone or a television set).
  • the user may respond to the interaction object by sending an SMS message via the mobile network back to the Voting Management Server.
  • a user who wishes to use an Interactive Personal Television service must first activate the service, and can then choose to either check for available interaction services manually, or subscribe to notifications about available services, which are sent periodically.
  • users cannot indicate what information about the service may be useful to them and thus receive only updates of relevant information.
  • the entire "interactivity media object" document is downloaded to the user's device.
  • the service triggers updates, the user will receive information regardless of its importance or personal preferences and thus regardless of the user's current needs or situation. For example, a user may not wish to take part in an online vote, but may wish to send an opinion to the broadcaster for broadcasting as part of the programme.
  • the "interactivity media object" does not discriminate which information may be useful or not to the user.
  • OMA BCAST triggers cannot be used as a means to dynamically generate associated interactivity media objects, since these triggers must be pre-programmed into the media stream.
  • the invention provides means to automatically gather user preferences, and enable Interactive Personal Television services to automatically take user preferences into account. This ensures that only services and interaction invitations relevant to the user preferences are sent to the user, reducing the signalling required to support Interactive Personal Television, and providing a better user experience.
  • the broadcaster inspects and detects events in the media stream, and sets a broadcast trigger automatically that when an event occurs that is of interest to an individual.
  • the triggers cause the creation of an "interaction object" which is rendered on the screen on which the user is currently viewing the service.
  • the interaction object triggers may be generated by employing either OMA BCAST triggers followed by rendering via an "interactivity media object” or by using a Presence enabler and subsequent visualization by a client that is subscribed to Presence data.
  • interactivity media documents embedded in the media stream may be combined with interactivity media documents sent using SI(M)P(LE) NOTIFY as a separate interaction channel via either mobile or fixed network access.
  • SI(M)P(LE) SUBSCRIBE/NOTIFY messages are used in order to achieve personalization of delivery of the interactivity media document for the individual user.
  • the user can set or change his or her preferences manually. Preferences may include parameters related to data sources, which may have default values that are set by the owner of the information source.
  • interactivity media documents embedded in the media stream may be combined with dynamically created interactivity media documents.
  • the interactivity media documents may be obtained cia a web service, and employ suitable technologies in order to push the information to the end user. Examples of such technologies include WAP push, OMA BCAST, HTTP persistence, SMS and MMS. This allows a user to change preferences manually.
  • a method of providing an Interactive Television service comprises storing user preferences relating to the service and, at one of a Personal Interaction Profile function and a Group Interaction Profile function, receiving from a broadcast server information identifying an event relating to the interactive service A comparison is made between the received information with the user preferences to determine whether a notification should be sent to the user, and if it is determined that the notification should be sent to the user, the notification is sent to a user device.
  • the method may further comprise, at the user device, in response to receiving the notification, sending a response message to the broadcast server.
  • the method further comprises, at the user device, alerting the user to the presence of the notification; inviting the user to respond to the notification; receiving the user's response to the notification; and sending a response message based on the user's response to the broadcast server.
  • the method may comprise the step of sending a subscribe message to a Service Interaction Object function of an Interactive Television broadcast, the subscribe message containing information relating to user preferences.
  • the subscribe message may be sent from any one of a user device, a user's Presence Agent and a user's Group Management server, and the subscribe message may be a Session Initiation Protocol SUBSCRIBE message.
  • the Personal Interaction Profile and/or the Group Interaction Profile is located at an IP Multimedia Subsystem network.
  • the notification may be sent to a user device using a Push message.
  • the Push message may be of a type selected from a Wireless Application Protocol push message, an OMA BCAST message, an HTTP persistence message, a Short Message Service message and a Multimedia Message Service.
  • the method may require, prior to the step of storing user preferences relating to the service, the user to register with a web based presence service.
  • a Personal Interaction Profile function comprising a receiver for receiving from an Interactive Television broadcast server information identifying an event relating to an Interactive Television service.
  • a processor is provided for comparing the received information with user preferences to determine whether a notification should be sent to the user, and a transmitter is also provided for, if it is determined that the notification should be sent to the user, transmitting the notification to a user device.
  • the Personal Interaction Profile function may comprise a memory for storing the user preferences, or may comprise means to receive user preferences transmitted from a remote node.
  • a Group Interaction Profile function comprising a receiver for receiving from an Interactive Television broadcast server information identifying an event relating to an Interactive Television service.
  • a processor is also provided for comparing the received information with group user preferences to determine whether a notification should be sent to a group of users, and a transmitter is provided for, if it is determined that the notification should be sent to the user, transmitting the notification to all user devices belonging to the group.
  • a Service Interaction Object function comprising a receiver for receiving a subscribe message, the subscribe message containing information relating to user preferences, and a processor for comparing the received user preferences with Interactive Television services to determine whether information identifying services should be sent to one of a user's Personal Interaction Profile function or Group Interaction Profile function.
  • a transmitter is also provided for, if it is determined that information identifying services should be sent to the user's Personal Interaction Profile function or Group Interaction Profile function, transmitting information identifying the services to the user's Personal Interaction Profile function or Group Interaction Profile function.
  • a user device for allowing a user to receive an Interactive Television service
  • the user device comprising a receiver for receiving a notification of an event relating to the Interactive Television service, means for alerting the user to the presence of the notification, means for inviting the user to respond to the notification, means for allowing the user to input a response to the notification, and means for sending a response message based on the user's input response.
  • Figure 1 illustrates schematically an example of Interactive Personal Television architecture for a broadcast having an associated voting service
  • FIG. 2 illustrates schematically an Interactive Personal Television architecture according to an embodiment of the invention using an IP Multimedia Subsystem network
  • Figure 3 illustrates schematically the signalling required for a user interaction with an Interactive Personal Television service according to an embodiment of the invention using an IP Multimedia Subsystem network;
  • FIG. 4 is a flow diagram illustrating the basic steps of the invention.
  • Figure 5 illustrates schematically an Interactive Personal Television architecture according to a further embodiment of the invention using a non- IP Multimedia Subsystem network
  • Figure 6 illustrates schematically the signalling required for a user interaction with an Interactive Personal Television service according to an embodiment of the invention using a non- IP Multimedia Subsystem network.
  • FIG. 2 there is illustrated a user having a digital television set and a mobile device. There is also provided at the User end a Watcher, a Presence Agent, and a Personal Interaction Object (PIO). A Context Sensor is also provided at the User end.
  • a Watcher There is also provided at the User end a Watcher, a Presence Agent, and a Personal Interaction Object (PIO).
  • PIO Personal Interaction Object
  • the User device connects to a Personal Interaction Profile and/or a Group Interaction profile and a Presentity via an IP network.
  • the Personal Interaction Profile, Group Interaction Profile and Presentity are provided within an IP Multimedia subsystem (IMS) network.
  • IMS IP Multimedia subsystem
  • Interactive Personal Television services are broadcast from a Content Provider Server. At the Server end there is also provided a Service Interaction Object (SIO).
  • SIO Service Interaction Object
  • a PIO is created either as a result of notification sent by a Presentity and Personal Interaction Profile (PIP) joining a Service Interaction Object (SIO), or as a result of an OMA BCAST trigger.
  • PIP Presentity and Personal Interaction Profile
  • SIO Service Interaction Object
  • the Watcher subscribes with the Presence Agent and monitors notifications from the Presence Agent, and the Presence Agent sends notifications to the Watcher based on changes in the Presentity/PIP.
  • the Presence Agent also updates the Presentity/PIP.
  • the Context Sensor updates Personal- and Group Interaction Profiles (PIP and GIP) either via co-located Presence Agents, or directly via other means such as HTTP/SOAP. Any suitable means may be used for the Context Sensors to send updates to the PIP and GIP.
  • PIP and GIP Personal- and Group Interaction Profiles
  • Service Interaction Objects are specific to a particular service at the broadcast Server end, and send notifications to the PIP when relevant events are detected in media streams.
  • An index file for recordings is provided at the broadcast Server.
  • a Presence Server is located at the IMS network, the Presence Server having Presentities.
  • the Presence server is co-located with a Personal Interaction Profile (PIP), which filters requests from the SIO for relevance to the user based on the user's settings and preferences.
  • PIP Personal Interaction Profile
  • Group Management is co-located with Group Interaction Profile (GIP) at the IMS network.
  • GIP Group Interaction Profile
  • the GIP filters requests from the SIO for relevance and forwards them to the associated subscribed Presentity's PIP.
  • the system works as follows, with the numbered steps corresponding to the numbers shown in Figure 3 :
  • the user's Presentity on the IMS network or Group (Management) that the user is subscribed to identifies at least one service that may be of interest to the user. The identification is made when the service passes GIP/PIP filtering. By filtering out services that are not of interest to the user, irrelevant invitations to the user are avoided.
  • the user or the user's Presence Agent, or the Group Management that the user is subscribed to, or an external entity allocated this task and triggered by any of the aforementioned entities, subscribes to the service. This enables automatic user participation and user feedback such as voting.
  • a SIP subscribe message to subscribe to the service is sent to the service's SIO.
  • the subscribe message contains parameters that relate to user preferences, which could be preferences set by the user regarding the type of service of interest, and/or parameters relating to the capabilities of the device that the user using to view the broadcast; or other parameters valid for the process of delivering the service to the user.
  • the identified service's SIO in the application server receives the SIP subscribe from the user or Presence Agent or from the Group Management on the user's behalf.
  • the SIO detects a service of interest, taking into account relevant parameters that were received in the subscription request, it sends a notification to the user's PIP.
  • Figure 3 also illustrates how, during a SETUP phase, the user registers with the Presence service. Thereafter the Group Management invokes the GIP, and the Presence Server invokes the PIP from the Presentity, both of which may be subsequently updated with (sensor) context information.
  • the Service Provider's broadcast Server invokes the SIO. Event detection, as described in the next paragraph, leads to a filtered notification and invocation of a PIO on the user's device, enabling the user to provide feedback.
  • the SIO When an event is detected in a media stream, the SIO triggers a SIP notification, which is directed to a group of users.
  • the group of users is either held by the Application Server or identified as the Group (Management) co-located with the Presence System in the IMS network.
  • the media-stream related event may occur in a live-feed or in a recorded media.
  • the event triggers the notification as a result of an agent monitoring the media stream for events that match its configuration on the basis of the user preferences. Any suitable configuration method may be used and may, for example, employ meta-data descriptions such as found in MPEG-7 or similar technologies.
  • the detection agent sends a notification using a Push Application Engine (for example, PPG or similar), which retrieves the capabilities of available terminals for the user from the Presence server (PGM) and uses the information to adapt pushed content to the receiving terminal(s).
  • a Push Application Engine for example, PPG or similar
  • PPG Presence server
  • Automatically configured notification which is directed to a pre-selected group of users for continued processing (the configuration of the notification, including the user group etc, can be fetched from the user's profile), or
  • Manually configured notification which can use a script language to initiate actions (such as triggering different notifications to different groups when different events occur). Cost control may be built into the scripts. For example, if a user chooses to accept advertising then the notification may be sent at no cost to the user.
  • the group to which the notification is to be pushed to can be obtained from other applications, such as a Push to Talk over Cellular (PoC) group, a presence enabled phone book, etc.
  • the group will have its own profile information documents, typically PDF and XDM.
  • An automatic notification may be triggered when, for example, all members of a group have performed an action, such as watching a video stream past a certain point.
  • the user creates a set of instructions (a script), which is downloaded to a push provider and executed.
  • the user can either choose (in his configuration) to defer the notification (i.e. watch it later); or allow the reception of the notification to trigger the start of a video client.
  • This type of event can be a secondary condition to the automatic flow.
  • This notification configuration can have instructions for how the notification should be handled, for example what applications it should trigger etc. as described in the previous paragraph.
  • the notification may trigger a special-purpose client, which records the event on behalf of the user. Multiple users can use the same recording, and the information about the recording can be stored in an index file, which can be sent to the receiver (multiple receivers) as part of the notification.
  • the system is implemented as follows: 1. When the user registers, the user preferences are recorded. 2. The user preferences are noted in an index file (part of the PIP), where the preferences for notifications are marked.
  • the invention can be summarized as shown in the flow diagram of Figure 4.
  • User preferences are stored 5 when the user registers with a Presentity.
  • the user's Personal Interaction Profile function or a Group Interaction Profile function receives 6 information identifying the event.
  • the information identifying the event is compared 7 with the user preferences, and a decision is made 8 on whether to send a notification to the user. If it is determined that a notification should be sent, then the notification is sent 9 to the user's device.
  • the invention can be implemented in a non-IMS environment by using web service protocols and notification mechanism based on push or fake push technologies.
  • Examples of such technologies include WAP push, OMA BCAST, HTTP persistence, SMS or MMS. Any of these mechanisms may be used to send notifications to a user device.
  • a user logs in 11 to a web based presence system by using a Web page using a log in password.
  • the web based presence system updates the user's status.
  • any other type of presence system may be used.
  • an instant messaging application may be used to log in with a presence system.
  • the user manages his or her interests profile using, for example, a SOAP request from a client or a simple HTTP interaction with a web browser.
  • the client may be , for example, the same web browser that the user has used to log in with the presence system, or may be a separate profile management client.
  • the separate profile management client may be embedded in the presence application, or may be a standalone client.
  • the user's Presentity or group management behaves in the same way as the Presentity or group management does in the IMS embodiment described above. It filters relevant services and triggers bases on the PIP or the GIP.
  • a Push Application Engine is used to send a Push message 16 to the user's client.
  • the Push message is sent from the Application Server that is used to deliver the media content, and the Push message is sent to the user or a list of users.
  • the Push Application engine identifies the best channel to deliver the notification to the watcher at the user client. The best channel may be determined by user preferences.
  • Examples of ways in which the notification may be delivered to the watcher at the user client include the following: a. An open HTTP persistent session with the Presence Server can be used to deliver a notification to the client and trigger an HTTP GET message, the content of which will be delivered to the watcher (embedded in the browser in this case).
  • the HTTP GET message allows the notification to be received at the user device; b. an instant message to the presence and messaging applications can be automatically triggered, which is interpreted by the application as a control message and triggers the watcher to receive the pushed content; or c.
  • An SMS is automatically delivered to a mobile client, which triggers a notification client to open a connection to the notification server and download the content.
  • the watcher at the user device Once the watcher at the user device has received the notification, it then acts upon the notification by obtaining the required data relating to the event (if it has not included in the notification itself) and delivering it to the appropriate client in the user device. The data is then displayed to the user or acted upon by the client in an appropriate manner.
  • the mechanism requires a trigger handling service to run at the device.
  • the trigger handling service must understands the triggers to be received by different push or fake-push mechanisms.
  • the trigger handling service receives the triggers from different transport mechanisms and delivers the content to the appropriate watcher. It then acts as an enabler for other services (or an enabler for the watchers).
  • the invention reduces the amount of updates required and optimises network usage by limiting the number of irrelevant messages sent to a user. Further advantages of the invention include the following:

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Signal Processing (AREA)
  • Databases & Information Systems (AREA)
  • Chemical & Material Sciences (AREA)
  • Life Sciences & Earth Sciences (AREA)
  • Analytical Chemistry (AREA)
  • Biomedical Technology (AREA)
  • Biophysics (AREA)
  • General Health & Medical Sciences (AREA)
  • Neurosurgery (AREA)
  • Health & Medical Sciences (AREA)
  • Computer Graphics (AREA)
  • Telephonic Communication Services (AREA)

Abstract

A method and apparatus for providing an Interactive Television service. The method comprises storing user preferences relating to the service and, at one of a Personal Interaction Profile function and a Group Interaction Profile function, receiving from a broadcast server information identifying an event relating to the interactive service. The received information is compared with the user preferences to determine whether a notification should be sent to the user and, if it is determined that the notification should 10 be sent to the user, the notification is sent to a user device.

Description

User Preferences in Interactive Personal Television
Technical field
The invention relates to the field of Interactive Personal Television.
Background
Interactive Personal Television programming requires feedback from its audience. One example of audience feedback is real-time voting, in which an audience member can influence the programme being watched. The influence may be, for example, taking part in a vote or choosing a camera angle from which to view a sports event. In order to provide this degree of interaction, the audience member must have a return path to transmit information to the programme broadcaster. This return path may use suitable media, for example, telephone, SMS messaging or cable (where a user who receives a cable broadcast can transmit information to the broadcaster using the same cable as a return path).
Interactive Personal Television requires interaction with individual users. For this purpose, OMA BCAST (OMA-TS-BCAST_Services-Vl_0-20060419-D, section 5.3) has developed a set of interactivity triggers, which are sent by the broadcaster and can be used to render an "interactivity media object" message on the user's screen. These can trigger further interaction from the user, for example, ring tone ordering or voting.
Interactivity media objects can be sent in-band (i.e., with the television signal), or out- of-band.
Referring to Figure 1, an example architecture of an Interactive Personal Television voting service is illustrated. An Interactive Personal Television programme is broadcast from a broadcast network and rendered on the user's television set. An "interactivity media object" document containing some or all of the interaction elements is sent from the broadcaster over the broadcast network to the user's mobile device. When, for example, a vote is offered on the Interactive Personal Television programme, the interactivity media object displays an indication that voting is available on the screen of the end-user's device (for example a mobile telephone or a television set). The user may respond to the interaction object by sending an SMS message via the mobile network back to the Voting Management Server.
A user who wishes to use an Interactive Personal Television service must first activate the service, and can then choose to either check for available interaction services manually, or subscribe to notifications about available services, which are sent periodically. However, users cannot indicate what information about the service may be useful to them and thus receive only updates of relevant information. As a result, the entire "interactivity media object" document is downloaded to the user's device. When the service triggers updates, the user will receive information regardless of its importance or personal preferences and thus regardless of the user's current needs or situation. For example, a user may not wish to take part in an online vote, but may wish to send an opinion to the broadcaster for broadcasting as part of the programme. However, the "interactivity media object" does not discriminate which information may be useful or not to the user.
Another issue with current Interactive Personal Television is that, using existing communications means, it is not possible to notify individual users of the start of a TV programme or an event occurring during the program in an automated way. Any alerts required by the user must be triggered manually. In addition, users cannot join an interactive service spontaneously and must subscribe to the service in advance.
OMA BCAST triggers cannot be used as a means to dynamically generate associated interactivity media objects, since these triggers must be pre-programmed into the media stream.
Another problem with known systems is that user subscriptions are static and do not change over time. This means that the user will receive subscribed information regardless of time and place and thus regardless of changing preferences. This can be a problem, for example, when a user accesses a broadcast using one of several pieces of equipment, which may have different capabilities. The only way to modify the subscription is to un- subscribe and re-subscribe (or update the subscriber profile).
Existing solutions to this problem include downloading content using HTTP/RTSP; pushing content using Multimedia messaging Services (MMS) technology; mobile TV triggering using HTTP; and H.324m dial-up to content server. These solutions do not allow for re-use of an IP Multimedia Subsystem (IMS) infrastructure, and have either plain or no triggering mechanisms. Furthermore, there is either no or poor consideration of interaction with other services running on an IMS based network.
Summary
The invention provides means to automatically gather user preferences, and enable Interactive Personal Television services to automatically take user preferences into account. This ensures that only services and interaction invitations relevant to the user preferences are sent to the user, reducing the signalling required to support Interactive Personal Television, and providing a better user experience.
The broadcaster inspects and detects events in the media stream, and sets a broadcast trigger automatically that when an event occurs that is of interest to an individual. The triggers cause the creation of an "interaction object" which is rendered on the screen on which the user is currently viewing the service. The interaction object triggers may be generated by employing either OMA BCAST triggers followed by rendering via an "interactivity media object" or by using a Presence enabler and subsequent visualization by a client that is subscribed to Presence data.
Where the invention is used with an IP Multimedia Subsystem network, interactivity media documents embedded in the media stream may be combined with interactivity media documents sent using SI(M)P(LE) NOTIFY as a separate interaction channel via either mobile or fixed network access. SI(M)P(LE) SUBSCRIBE/NOTIFY messages are used in order to achieve personalization of delivery of the interactivity media document for the individual user. The user can set or change his or her preferences manually. Preferences may include parameters related to data sources, which may have default values that are set by the owner of the information source.
Where the invention is used without an IP Multimedia Subsystem network, interactivity media documents embedded in the media stream may be combined with dynamically created interactivity media documents. The interactivity media documents may be obtained cia a web service, and employ suitable technologies in order to push the information to the end user. Examples of such technologies include WAP push, OMA BCAST, HTTP persistence, SMS and MMS. This allows a user to change preferences manually.
According to a first aspect of the invention, there is provided a method of providing an Interactive Television service. The method comprises storing user preferences relating to the service and, at one of a Personal Interaction Profile function and a Group Interaction Profile function, receiving from a broadcast server information identifying an event relating to the interactive service A comparison is made between the received information with the user preferences to determine whether a notification should be sent to the user, and if it is determined that the notification should be sent to the user, the notification is sent to a user device.
The method may further comprise, at the user device, in response to receiving the notification, sending a response message to the broadcast server.
Preferably, the method further comprises, at the user device, alerting the user to the presence of the notification; inviting the user to respond to the notification; receiving the user's response to the notification; and sending a response message based on the user's response to the broadcast server. The method may comprise the step of sending a subscribe message to a Service Interaction Object function of an Interactive Television broadcast, the subscribe message containing information relating to user preferences.
The subscribe message may be sent from any one of a user device, a user's Presence Agent and a user's Group Management server, and the subscribe message may be a Session Initiation Protocol SUBSCRIBE message.
In a preferred embodiment of the invention, the Personal Interaction Profile and/or the Group Interaction Profile is located at an IP Multimedia Subsystem network.
The notification may be sent to a user device using a Push message. Where the invention is implemented in a non-IMS network, the Push message may be of a type selected from a Wireless Application Protocol push message, an OMA BCAST message, an HTTP persistence message, a Short Message Service message and a Multimedia Message Service.
In the case where the invention is implemented in a non-IMS network, the method may require, prior to the step of storing user preferences relating to the service, the user to register with a web based presence service.
According to a second aspect of the invention, there is provided a Personal Interaction Profile function comprising a receiver for receiving from an Interactive Television broadcast server information identifying an event relating to an Interactive Television service. A processor is provided for comparing the received information with user preferences to determine whether a notification should be sent to the user, and a transmitter is also provided for, if it is determined that the notification should be sent to the user, transmitting the notification to a user device. The Personal Interaction Profile function may comprise a memory for storing the user preferences, or may comprise means to receive user preferences transmitted from a remote node.
According to a third aspect of the invention, there is provided a Group Interaction Profile function comprising a receiver for receiving from an Interactive Television broadcast server information identifying an event relating to an Interactive Television service. A processor is also provided for comparing the received information with group user preferences to determine whether a notification should be sent to a group of users, and a transmitter is provided for, if it is determined that the notification should be sent to the user, transmitting the notification to all user devices belonging to the group.
According to a fourth aspect of the invention, there is provided a Service Interaction Object function comprising a receiver for receiving a subscribe message, the subscribe message containing information relating to user preferences, and a processor for comparing the received user preferences with Interactive Television services to determine whether information identifying services should be sent to one of a user's Personal Interaction Profile function or Group Interaction Profile function. A transmitter is also provided for, if it is determined that information identifying services should be sent to the user's Personal Interaction Profile function or Group Interaction Profile function, transmitting information identifying the services to the user's Personal Interaction Profile function or Group Interaction Profile function.
According to a fifth aspect of the invention, there is provided a user device for allowing a user to receive an Interactive Television service, the user device comprising a receiver for receiving a notification of an event relating to the Interactive Television service, means for alerting the user to the presence of the notification, means for inviting the user to respond to the notification, means for allowing the user to input a response to the notification, and means for sending a response message based on the user's input response. Brief Description of the Drawings
Figure 1 illustrates schematically an example of Interactive Personal Television architecture for a broadcast having an associated voting service;
Figure 2 illustrates schematically an Interactive Personal Television architecture according to an embodiment of the invention using an IP Multimedia Subsystem network;
Figure 3 illustrates schematically the signalling required for a user interaction with an Interactive Personal Television service according to an embodiment of the invention using an IP Multimedia Subsystem network;
Figure 4 is a flow diagram illustrating the basic steps of the invention;
Figure 5 illustrates schematically an Interactive Personal Television architecture according to a further embodiment of the invention using a non- IP Multimedia Subsystem network; and
Figure 6 illustrates schematically the signalling required for a user interaction with an Interactive Personal Television service according to an embodiment of the invention using a non- IP Multimedia Subsystem network.
Detailed Description
Referring to Figure 2, there is illustrated a user having a digital television set and a mobile device. There is also provided at the User end a Watcher, a Presence Agent, and a Personal Interaction Object (PIO). A Context Sensor is also provided at the User end.
The User device connects to a Personal Interaction Profile and/or a Group Interaction profile and a Presentity via an IP network. The Personal Interaction Profile, Group Interaction Profile and Presentity are provided within an IP Multimedia subsystem (IMS) network.
Interactive Personal Television services are broadcast from a Content Provider Server. At the Server end there is also provided a Service Interaction Object (SIO).
A PIO is created either as a result of notification sent by a Presentity and Personal Interaction Profile (PIP) joining a Service Interaction Object (SIO), or as a result of an OMA BCAST trigger.
The Watcher subscribes with the Presence Agent and monitors notifications from the Presence Agent, and the Presence Agent sends notifications to the Watcher based on changes in the Presentity/PIP. The Presence Agent also updates the Presentity/PIP.
The Context Sensor updates Personal- and Group Interaction Profiles (PIP and GIP) either via co-located Presence Agents, or directly via other means such as HTTP/SOAP. Any suitable means may be used for the Context Sensors to send updates to the PIP and GIP.
Service Interaction Objects (SIO) are specific to a particular service at the broadcast Server end, and send notifications to the PIP when relevant events are detected in media streams. An index file for recordings is provided at the broadcast Server.
A Presence Server is located at the IMS network, the Presence Server having Presentities. The Presence server is co-located with a Personal Interaction Profile (PIP), which filters requests from the SIO for relevance to the user based on the user's settings and preferences.
Group Management is co-located with Group Interaction Profile (GIP) at the IMS network. The GIP filters requests from the SIO for relevance and forwards them to the associated subscribed Presentity's PIP. The system works as follows, with the numbered steps corresponding to the numbers shown in Figure 3 :
1. The user's Presentity on the IMS network or Group (Management) that the user is subscribed to identifies at least one service that may be of interest to the user. The identification is made when the service passes GIP/PIP filtering. By filtering out services that are not of interest to the user, irrelevant invitations to the user are avoided.
2. The user, or the user's Presence Agent, or the Group Management that the user is subscribed to, or an external entity allocated this task and triggered by any of the aforementioned entities, subscribes to the service. This enables automatic user participation and user feedback such as voting. A SIP subscribe message to subscribe to the service is sent to the service's SIO. The subscribe message contains parameters that relate to user preferences, which could be preferences set by the user regarding the type of service of interest, and/or parameters relating to the capabilities of the device that the user using to view the broadcast; or other parameters valid for the process of delivering the service to the user.
3. The identified service's SIO in the application server receives the SIP subscribe from the user or Presence Agent or from the Group Management on the user's behalf. When the SIO detects a service of interest, taking into account relevant parameters that were received in the subscription request, it sends a notification to the user's PIP.
4. The user may manually select context sources and trigger conditions and link these to parameters in the Presentity/PIP. This allows the user to control which services are offered, and what alerts are required to be sent. Alternatively the system may do this automatically on the basis of configuration information that has been received from the service provider and the network operator. Figure 3 also illustrates how, during a SETUP phase, the user registers with the Presence service. Thereafter the Group Management invokes the GIP, and the Presence Server invokes the PIP from the Presentity, both of which may be subsequently updated with (sensor) context information. The Service Provider's broadcast Server invokes the SIO. Event detection, as described in the next paragraph, leads to a filtered notification and invocation of a PIO on the user's device, enabling the user to provide feedback.
When an event is detected in a media stream, the SIO triggers a SIP notification, which is directed to a group of users. The group of users is either held by the Application Server or identified as the Group (Management) co-located with the Presence System in the IMS network. The media-stream related event may occur in a live-feed or in a recorded media. The event triggers the notification as a result of an agent monitoring the media stream for events that match its configuration on the basis of the user preferences. Any suitable configuration method may be used and may, for example, employ meta-data descriptions such as found in MPEG-7 or similar technologies.
The detection agent sends a notification using a Push Application Engine (for example, PPG or similar), which retrieves the capabilities of available terminals for the user from the Presence server (PGM) and uses the information to adapt pushed content to the receiving terminal(s).
Notifications may be one of two types:
a. Automatically configured notification, which is directed to a pre-selected group of users for continued processing (the configuration of the notification, including the user group etc, can be fetched from the user's profile), or
b. Manually configured notification, which can use a script language to initiate actions (such as triggering different notifications to different groups when different events occur). Cost control may be built into the scripts. For example, if a user chooses to accept advertising then the notification may be sent at no cost to the user.
In the case of automatically configured notifications, the group to which the notification is to be pushed to can be obtained from other applications, such as a Push to Talk over Cellular (PoC) group, a presence enabled phone book, etc. The group will have its own profile information documents, typically PDF and XDM.
An automatic notification may be triggered when, for example, all members of a group have performed an action, such as watching a video stream past a certain point.
In the case of manually configured notifications, the user creates a set of instructions (a script), which is downloaded to a push provider and executed. The user can either choose (in his configuration) to defer the notification (i.e. watch it later); or allow the reception of the notification to trigger the start of a video client. This type of event can be a secondary condition to the automatic flow.
It is possible for the user to select a manual notification configuration which has been pre-set e.g. by a content provider. This notification configuration can have instructions for how the notification should be handled, for example what applications it should trigger etc. as described in the previous paragraph.
Where a notification is triggered by a real-time event, the notification may trigger a special-purpose client, which records the event on behalf of the user. Multiple users can use the same recording, and the information about the recording can be stored in an index file, which can be sent to the receiver (multiple receivers) as part of the notification.
In one embodiment of the invention, the system is implemented as follows: 1. When the user registers, the user preferences are recorded. 2. The user preferences are noted in an index file (part of the PIP), where the preferences for notifications are marked.
3. When the preferred point occurs, a notification is triggered, and the index file is transmitted. 4. The notification is sent to the push initiator, who triggers a push event.
The invention can be summarized as shown in the flow diagram of Figure 4. User preferences are stored 5 when the user registers with a Presentity. When the user is subsequently receiving a media stream, and an event occurs relating to an interactive service, the user's Personal Interaction Profile function or a Group Interaction Profile function receives 6 information identifying the event. The information identifying the event is compared 7 with the user preferences, and a decision is made 8 on whether to send a notification to the user. If it is determined that a notification should be sent, then the notification is sent 9 to the user's device.
The above description describes the invention as it works using an IMS network. However, in a further embodiment, the invention can also be implemented in a non-IMS network. The architecture of the invention in a non-IMS network is illustrated in Figure 5.
The invention can be implemented in a non-IMS environment by using web service protocols and notification mechanism based on push or fake push technologies. Examples of such technologies include WAP push, OMA BCAST, HTTP persistence, SMS or MMS. Any of these mechanisms may be used to send notifications to a user device.
By way of example, and referring to Figure 6, a user logs in 11 to a web based presence system by using a Web page using a log in password. The web based presence system updates the user's status. Note that any other type of presence system may be used. For example, an instant messaging application may be used to log in with a presence system. The user manages his or her interests profile using, for example, a SOAP request from a client or a simple HTTP interaction with a web browser. The client may be , for example, the same web browser that the user has used to log in with the presence system, or may be a separate profile management client. The separate profile management client may be embedded in the presence application, or may be a standalone client.
The user's Presentity or group management behaves in the same way as the Presentity or group management does in the IMS embodiment described above. It filters relevant services and triggers bases on the PIP or the GIP.
When a service of interest, or a notification is identified, a Push Application Engine is used to send a Push message 16 to the user's client. The Push message is sent from the Application Server that is used to deliver the media content, and the Push message is sent to the user or a list of users. The Push Application engine identifies the best channel to deliver the notification to the watcher at the user client. The best channel may be determined by user preferences.
Examples of ways in which the notification may be delivered to the watcher at the user client include the following: a. An open HTTP persistent session with the Presence Server can be used to deliver a notification to the client and trigger an HTTP GET message, the content of which will be delivered to the watcher (embedded in the browser in this case). The HTTP GET message allows the notification to be received at the user device; b. an instant message to the presence and messaging applications can be automatically triggered, which is interpreted by the application as a control message and triggers the watcher to receive the pushed content; or c. An SMS is automatically delivered to a mobile client, which triggers a notification client to open a connection to the notification server and download the content.
Once the watcher at the user device has received the notification, it then acts upon the notification by obtaining the required data relating to the event (if it has not included in the notification itself) and delivering it to the appropriate client in the user device. The data is then displayed to the user or acted upon by the client in an appropriate manner.
It is important to note that the mechanism requires a trigger handling service to run at the device. The trigger handling service must understands the triggers to be received by different push or fake-push mechanisms. The trigger handling service receives the triggers from different transport mechanisms and delivers the content to the appropriate watcher. It then acts as an enabler for other services (or an enabler for the watchers).
The invention reduces the amount of updates required and optimises network usage by limiting the number of irrelevant messages sent to a user. Further advantages of the invention include the following:
• Personalized subscriptions/requests
• Increased control / Added value
• Context awareness
• Intelligent concatenation and management of composite triggering events of content delivery. • Dynamic business relationship establishment between a Push Initiator and a Push Enabler.
• Reuse of the communication infrastructure for content delivery.
• Intelligent selection of supporting enablers.
• Management of interaction with other services. • Improved user experience It will be appreciated by a person skilled in the art that various modifications may be made to the above-described embodiments without departing from the scope of the present invention.

Claims

Claims:
1. A method of providing an Interactive Television service, the method comprising: storing user preferences relating to the service; at one of a Personal Interaction Profile function and a Group Interaction Profile function, receiving from a broadcast server information identifying an event relating to the interactive service; comparing the received information with the user preferences to determine whether a notification should be sent to the user; and if it is determined that the notification should be sent to the user, sending the notification to a user device.
2. A method according to claim 1, further comprising, at the user device, in response to receiving the notification, sending a response message to the broadcast server.
3. A method according to claim 1, further comprising, at the user device, alerting the user to the presence of the notification; inviting the user to respond to the notification; receiving the user's response to the notification; and sending a response message based on the user's response to the broadcast server.
4. A method according to any one claims 1, 2 or 3, comprising the step of sending a subscribe message to a Service Interaction Object function of an Interactive Television broadcast, the subscribe message containing information relating to user preferences.
5. A method according to claim 4, wherein the subscribe message is sent from any one of a user device, a user's Presence Agent and a user's Group Management server.
6. A method according to claim 4 or 5, wherein the subscribe message is a Session Initiation Protocol SUBSCRIBE message.
7. A method according to any one of the preceding claims, wherein the Personal Interaction Profile is located at an IP Multimedia Subsystem network.
8. A method according to any one of the preceding claims, wherein the Group Interaction Profile is located at an IP Multimedia Subsystem network.
9. A method according to any one of claims 1 to 3, comprising sending the notification to a user device using a Push message.
10. A method according to claim 9, wherein the Push message is sent using one of a Wireless Application Protocol push message, an OMA BCAST message, an HTTP persistence message, a Short Message Service message and a Multimedia Message Service.
11. A method according claim 9 or 10, wherein prior to storing user preferences relating to the service, a user registers with a web based presence service.
12. A Personal Interaction Profile function, comprising: a receiver for receiving from an Interactive Television broadcast server information identifying an event relating to an Interactive Television service; a processor for comparing the received information with user preferences to determine whether a notification should be sent to the user; and a transmitter for, if it is determined that the notification should be sent to the user, transmitting the notification to a user device.
13. A Personal Interaction Profile function according to claim 12, further comprising a memory for storing the user preferences.
14. A Personal Interaction Profile function according to claim 12, further comprising means to receive user preferences transmitted from a remote node.
15. A Group Interaction Profile function, comprising: a receiver for receiving from an Interactive Television broadcast server information identifying an event relating to an Interactive Television service; a processor for comparing the received information with group user preferences to determine whether a notification should be sent to a group of users; and a transmitter for, if it is determined that the notification should be sent to the user, transmitting the notification to all user devices belonging to the group.
16. A Service Interaction Object function, comprising: a receiver for receiving a subscribe message, the subscribe message containing information relating to user preferences; a processor for comparing the received user preferences with Interactive
Television services to determine whether information identifying services should be sent to one of a user's Personal Interaction Profile function or Group Interaction Profile function; a transmitter for, if it is determined that information identifying services should be sent to the user's Personal Interaction Profile function or Group Interaction Profile function, transmitting information identifying the services to the user's Personal Interaction Profile function or Group Interaction Profile function.
17. A user device for allowing a user to receive an Interactive Television service, the user device comprising: a receiver for receiving a notification of an event relating to the Interactive Television service; means for alerting the user to the presence of the notification; means for inviting the user to respond to the notification; means for allowing the user to input a response to the notification; and means for sending a response message based on the user's input response.
PCT/EP2007/057831 2006-08-01 2007-07-30 User preferences in interactive personal television WO2008015187A1 (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CA002665795A CA2665795A1 (en) 2006-08-01 2007-07-30 User preferences in interactive personal television

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
SE0601626 2006-08-01
SE0601626-5 2006-08-01
EPPCT/EP2007/054075 2007-04-25
PCT/EP2007/054075 WO2008015033A1 (en) 2006-08-01 2007-04-25 User preferences in interactive personal television

Publications (1)

Publication Number Publication Date
WO2008015187A1 true WO2008015187A1 (en) 2008-02-07

Family

ID=38466064

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2007/057831 WO2008015187A1 (en) 2006-08-01 2007-07-30 User preferences in interactive personal television

Country Status (1)

Country Link
WO (1) WO2008015187A1 (en)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2011037520A1 (en) * 2009-09-22 2011-03-31 Telefonaktiebolaget Lm Ericsson (Publ) Differentiating iptv notifications
US20130332559A1 (en) * 2011-02-08 2013-12-12 Telefonaktiebolaget L M Ericsson (Publ) Method and System for Mobility Support for Caching Adaptive HTTP Streaming Content in Cellular Networks
US20150081837A1 (en) * 2013-09-13 2015-03-19 Google Inc. Provisioning a plurality of computing devices
GB2556664A (en) * 2016-11-07 2018-06-06 Google Llc Third party application configuration for issuing notifications
US11191837B2 (en) 2007-12-28 2021-12-07 Takeda Pharmaceutical Company Limited Recombinant VWF formulations

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020010922A1 (en) * 2000-01-31 2002-01-24 Shai Darin Active program notification system and method
US20040034873A1 (en) * 2002-04-04 2004-02-19 Ian Zenoni Event driven interactive television notification
GB2394862A (en) * 2002-11-01 2004-05-05 Nokia Corp Hybrid network content delivery system
WO2004114109A1 (en) * 2003-06-13 2004-12-29 Yahoo, Inc. Method and system for delivery alerts to a user
US20050262145A1 (en) * 2004-05-19 2005-11-24 Dwango Co., Ltd. System, method and program for news updates

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20020010922A1 (en) * 2000-01-31 2002-01-24 Shai Darin Active program notification system and method
US20040034873A1 (en) * 2002-04-04 2004-02-19 Ian Zenoni Event driven interactive television notification
GB2394862A (en) * 2002-11-01 2004-05-05 Nokia Corp Hybrid network content delivery system
WO2004114109A1 (en) * 2003-06-13 2004-12-29 Yahoo, Inc. Method and system for delivery alerts to a user
US20050262145A1 (en) * 2004-05-19 2005-11-24 Dwango Co., Ltd. System, method and program for news updates

Cited By (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11191837B2 (en) 2007-12-28 2021-12-07 Takeda Pharmaceutical Company Limited Recombinant VWF formulations
WO2011037520A1 (en) * 2009-09-22 2011-03-31 Telefonaktiebolaget Lm Ericsson (Publ) Differentiating iptv notifications
CN102577426A (en) * 2009-09-22 2012-07-11 瑞典爱立信有限公司 Differentiating iptv notifications
JP2013504249A (en) * 2009-09-22 2013-02-04 テレフオンアクチーボラゲット エル エム エリクソン(パブル) Identification of IPTV notifications
EP2299710B1 (en) * 2009-09-22 2014-03-05 TELEFONAKTIEBOLAGET LM ERICSSON (publ) Differentiating IPTV notifications
US9118683B2 (en) 2009-09-22 2015-08-25 Telefonaktiebolaget L M Ericsson (Publ) Differentiating IPTV notifications
US20130332559A1 (en) * 2011-02-08 2013-12-12 Telefonaktiebolaget L M Ericsson (Publ) Method and System for Mobility Support for Caching Adaptive HTTP Streaming Content in Cellular Networks
US10027527B2 (en) * 2011-02-08 2018-07-17 Telefonaktiebolaget Lm Ericsson (Publ) Method and system for mobility support for caching adaptive HTTP streaming content in cellular networks
US20150081837A1 (en) * 2013-09-13 2015-03-19 Google Inc. Provisioning a plurality of computing devices
GB2556664A (en) * 2016-11-07 2018-06-06 Google Llc Third party application configuration for issuing notifications
US10397163B2 (en) 2016-11-07 2019-08-27 Google Llc Third party application configuration for issuing notifications

Similar Documents

Publication Publication Date Title
JP5136992B2 (en) Interactive multimedia broadcasting system with a dedicated advertising channel
KR101494111B1 (en) Methods and systems for broadcasting content based on user input
US20040005900A1 (en) Mobile terminal interactivity with multimedia programming
CN101583016B (en) Method for displaying and sending service status information, user terminal equipment and service processing unit
US20090125951A1 (en) System and method for a personal video inbox channel
CA2949460C (en) Companion device
JP2013085292A (en) Signal distribution system with interrupt processing and trick play functionality
US8463858B2 (en) System and method for binding notification types to applications for a notification framework
US20110321062A1 (en) Capturing events from and providing targeted messages to a digital media device
KR100808437B1 (en) Method and system for providing information concerning broadcast contents for a user
CN101588258A (en) Information uploading method and system
US20090210907A1 (en) Method and system for recommending multimedia content
CN101686249A (en) Subscription method and system of recommended information and recommended service server
US20110023065A1 (en) Method for providing a television electronic guide
CN101371570A (en) A method and apparatus for providing a picture in picture service
CA2960118A1 (en) System with a companion device and a primary device
WO2008015187A1 (en) User preferences in interactive personal television
US9402110B2 (en) Non-intrusive advertisement presentation methods and systems
GB2452519A (en) System and Method for Providing User Recommendations
US20090150956A1 (en) Television program broadcasting arrangement, and method
CN101355676B (en) Method for providing network television service information and network television service system
KR102482207B1 (en) A method and apparatus for supporting service change for digital broadcast systems
CN102577426A (en) Differentiating iptv notifications
WO2009101602A2 (en) System and method for delivering notification messages
KR101378217B1 (en) System and method for providing rls notification rule for multiple presentities

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 07788034

Country of ref document: EP

Kind code of ref document: A1

DPE1 Request for preliminary examination filed after expiration of 19th month from priority date (pct application filed from 20040101)
DPE1 Request for preliminary examination filed after expiration of 19th month from priority date (pct application filed from 20040101)
ENP Entry into the national phase

Ref document number: 2665795

Country of ref document: CA

NENP Non-entry into the national phase

Ref country code: DE

NENP Non-entry into the national phase

Ref country code: RU

122 Ep: pct application non-entry in european phase

Ref document number: 07788034

Country of ref document: EP

Kind code of ref document: A1