EP1166549A1 - Recepteur de television numerique avec interface de programme d'application pour gestion utilisateur - Google Patents

Recepteur de television numerique avec interface de programme d'application pour gestion utilisateur

Info

Publication number
EP1166549A1
EP1166549A1 EP99950245A EP99950245A EP1166549A1 EP 1166549 A1 EP1166549 A1 EP 1166549A1 EP 99950245 A EP99950245 A EP 99950245A EP 99950245 A EP99950245 A EP 99950245A EP 1166549 A1 EP1166549 A1 EP 1166549A1
Authority
EP
European Patent Office
Prior art keywords
user
terminal
preferences
registry
access
Prior art date
Legal status (The legal status 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 status listed.)
Withdrawn
Application number
EP99950245A
Other languages
German (de)
English (en)
Inventor
Petr Peterka
Branislav N. Meandzija
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Arris Technology Inc
Original Assignee
Arris Technology Inc
General Instrument Corp
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
Application filed by Arris Technology Inc, General Instrument Corp filed Critical Arris Technology Inc
Publication of EP1166549A1 publication Critical patent/EP1166549A1/fr
Withdrawn legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/45—Management operations performed by the client for facilitating the reception of or the interaction with the content or administrating data related to the end-user or to the client device itself, e.g. learning user preferences for recommending movies, resolving scheduling conflicts
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/43—Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
    • H04N21/443—OS processes, e.g. booting an STB, implementing a Java virtual machine in an STB or power management in an STB
    • H04N21/4431—OS processes, e.g. booting an STB, implementing a Java virtual machine in an STB or power management in an STB characterized by the use of Application Program Interface [API] libraries
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/43—Processing of content or additional data, e.g. demultiplexing additional data from a digital video stream; Elementary client operations, e.g. monitoring of home network or synchronising decoder's clock; Client middleware
    • H04N21/443—OS processes, e.g. booting an STB, implementing a Java virtual machine in an STB or power management in an STB
    • H04N21/4437—Implementing a Virtual Machine [VM]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/45—Management operations performed by the client for facilitating the reception of or the interaction with the content or administrating data related to the end-user or to the client device itself, e.g. learning user preferences for recommending movies, resolving scheduling conflicts
    • H04N21/4508—Management of client data or end-user data
    • H04N21/4532—Management of client data or end-user data involving end-user characteristics, e.g. viewer profile, preferences
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/45—Management operations performed by the client for facilitating the reception of or the interaction with the content or administrating data related to the end-user or to the client device itself, e.g. learning user preferences for recommending movies, resolving scheduling conflicts
    • H04N21/454—Content or additional data filtering, e.g. blocking advertisements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/40—Client devices specifically adapted for the reception of or interaction with content, e.g. set-top-box [STB]; Operations thereof
    • H04N21/47—End-user applications
    • H04N21/475—End-user interface for inputting end-user data, e.g. personal identification number [PIN], preference data
    • H04N21/4751—End-user interface for inputting end-user data, e.g. personal identification number [PIN], preference data for defining user accounts, e.g. accounts for children
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N21/00—Selective content distribution, e.g. interactive television or video on demand [VOD]
    • H04N21/80—Generation or processing of content or additional data by content creator independently of the distribution process; Content per se
    • H04N21/81—Monomedia components thereof
    • H04N21/812—Monomedia components thereof involving advertisement data

Definitions

  • the present invention provides an Application Programming Interface (API) for downloadable broadcast applications to manage/access user-related information on a Digital Television (DTV) Receiver/Terminal.
  • a set-top terminal also referred to as an Integrated Receiver-Decoder (IRD) or a subscriber terminal, is a device that receives and decodes television signals for presentation by a television.
  • IRD Integrated Receiver-Decoder
  • the signals can be delivered over a satellite, through a cable plant, or by means of terrestrial broadcast, for example.
  • Various applications have been proposed, or are currently available, via modern set tops, including video on demand (VOD) , audio on demand, pay- per-view, interactive shopping, electronic commerce, electronic program guides, Internet browsers, mail services (e.g., text e-mail, voice mail, audio mail, and/or video mail) , telephony services, stock ticker, weather data, travel information, games, gambling, banking, shopping, voting, and others.
  • VOD video on demand
  • voice mail e.g., text e-mail, voice mail, audio mail, and/or video mail
  • telephony services e.g., text e-mail, voice mail, audio mail, and/or video mail
  • telephony services e.g., text e-mail, voice mail, audio mail, and/or video mail
  • telephony services e.g., text e-mail, voice mail, audio
  • the applications may be downloaded by terminals via a network, loaded locally (e.g., via a smart card), or installed at the time of manufacture, for example.
  • a network loaded locally (e.g., via a smart card), or installed at the time of manufacture, for example.
  • computer networks such as the Internet, telephony networks, and broadband distribution networks, many opportunities arise for providing new types of applications.
  • the API should allow new users to be recognized, or old users to be deleted, as well as recognizing a current user of the terminal .
  • the API should provide a profile of the each user and maintain a record of permissions that have been granted to the users, e.g., for accessing applications such as pay-per-view, or enforcing rating guidelines for children.
  • the API should maintain a record of user preferences, such as preferred language and rating ceilings, personal data such as age, address, zip code, account numbers, as well as system-wide preferences, such as favorite channels, language, etc.
  • the API should also maintain a registry of applications, resources, preferences and users.
  • An application may use/access a resource, which is usually a device, function or a process on the receiver (e.g. tuner, modem, database, etc.)
  • the API should be compatible with Java(tm) , ActiveX (tm) or an equivalent type of component based object-oriented technology.
  • the API should be compatible with Digital Audio Visual Council (DAVIC) , American Television Standards Committee (ATSC) T3/S17 Digital TV Application Software Environment (DASE) , Digital Video Broadcast (DVB) - Multi-Media Home Platform (MHP) and other related environments .
  • DAVIC Digital Audio Visual Council
  • ATSC American Television Standards Committee
  • DASE Digital TV Application Software Environment
  • DVB Digital Video Broadcast
  • MHP Multi-Media Home Platform
  • the API should be compatible with any application at a terminal, regardless of how the application was received or installed (e.g., downloaded, resident, from smart card, etc.)
  • the present invention provides a system having the above and other advantages .
  • the present invention provides a software architecture a set-top television terminal.
  • an Application Programming Interface (API) is provided for applications to manage/access user-related information on the terminal.
  • API Application Programming Interface
  • a "user” is one who is watching the TV or using its other functions, e.g., E-mail, games, etc.
  • the API includes a user software package that includes registry, profile, permissions, change cause, change event, and registry event functions.
  • a preferences package includes a registry, names, rating, preferred language, change cause, change event and registry event functions.
  • a registry package includes type, factory, change event, listener, user, preference, resource and application functions.
  • the present invention provides a multi-user environment (user registry and user profile) , and a registry for preferences which can be associated with an individual user (user-specific) or be common to all users (system-wide) .
  • a set of permissions is associated with each user, or at least with a default user, which represents anybody watching the TV.
  • a television set-top terminal includes a computer readable medium having computer program code means, and means for executing the computer program code means to implement an Application Programming Interface (API) .
  • the API provides (a) a user registry of a plurality of users of the terminal, (b) a preferences registry of preferences of the users, and (c) permission (s) for controlling the users' access to at least one application that is provided at the terminal .
  • the API provides a security policy to allow only specified applications to access the preferences registry.
  • the security policy may be user-controlled. Thus, some applications can, and some cannot, access the preferences based on a security policy. This means that the user may allow only specified trusted applications to access his/her credit card number but not others, for example. These applications may be specified shop-at-home channels or the like.
  • the API disallows access to user preferences by an application that does not have the required permission (s) .
  • the permission (s) may be associated with each user individually, or may be associated with a default user.
  • a default user might be provided to indicate that the entire family is watching the television together, or to indicate a guest or unknown person.
  • the application generally is responsive to the user preferences. For example, if an application such as an Electronic Program Guide (EPG) accesses a language preference of a particular user, the application can automatically select the language for text when the service information (SI) is multilingual. An application that tunes to channels (audio/video or audio-only) may automatically select the appropriate audio language based on the user's language preference.
  • EPG Electronic Program Guide
  • SI service information
  • An application that tunes to channels may automatically select the appropriate audio language based on the user's language preference.
  • an EPG application may access favorite channel information of a user to prepare a custom made guide to the programs that are currently playing.
  • an application which enables targeted advertisements may access information regarding a user's location (ZIP code), gender, age, family status, and other personal information, such as pets, hobbies, etc .
  • e-commerce-type applications may need to look at user credit card numbers, permissions to do on-line purchases, and other related preferences.
  • the permission may also provide, for example, a parental control/rating ceiling or permission to buy Impulse Pay Per View (IPPV) programs, or engage in e- commerce transactions (e.g., purchase goods or services via the television - home shopping) .
  • IPPV Impulse Pay Per View
  • the preferences include a ratings ceiling preference .
  • the user preferences may include system- wide or user-specific.
  • the user registry can be used to register a new user of the terminal, identify a current user of the terminal , and remove a former user of the terminal .
  • an application when it needs to switch between users, it may do it by identifying the user using a logon screen, by PIN codes or passwords, or even personalized smart cards, or voice control, for example .
  • the permission (s) enable the users to access a resource/invoke functions of the terminal. This refers to accessing either some physical resource on the receiver, such as a modem or a tuner, the smart card, etc., or an application, such as e-mail, web browsing, e-commerce, etc.
  • the resource may be, for example, a device, function or a process on the receiver, such as a tuner, modem, database, plug- in module, cable, software module, network interface card, persistent storage, TV screen space, memory, CPU, conditional access (CA) module, and so forth.
  • a device function or a process on the receiver, such as a tuner, modem, database, plug- in module, cable, software module, network interface card, persistent storage, TV screen space, memory, CPU, conditional access (CA) module, and so forth.
  • CA conditional access
  • the API also is adapted to define one or more new types of user preferences, and add the new types of user preferences to the preferences registry.
  • the new user preferences can be defined by a base interface, Preference, which is an object that can be added or removed from the PreferenceRegistry . This allows one to define new types of user preferences, e.g., by extending it the same way as the LanguagePreference extends the base Preference.
  • the preferences may include specific types of programs (sports, drama, humor, action, etc.).
  • the API also is adapted to associate the new types of user preferences with the users.
  • the API may be independent of an operating system and hardware of the terminal .
  • FIG. 1 shows package relationships and dependencies in accordance with the present invention.
  • FIG. 2 illustrates a user class/interface diagram in accordance with the present invention.
  • FIG. 3 illustrates a preferences class/interface diagram in accordance with the present invention.
  • FIG. 4 illustrates a registry class/interface diagram in accordance with the present invention.
  • the present invention provides an Application Programming Interface (API) for downloadable broadcast applications to manage/access user-related information on a Digital Television (DTV) Receiver.
  • API Application Programming Interface
  • the invention comprises the following two API components: 1) User API; and 2) User Preferences API. They can be used together where each user has a set of user preferences associated with it, or separately where there is a system-level set of preferences without a user association.
  • a Registry package is also described herein, which provides a generic mechanism for registry-type constructs.
  • FIG. 1 illustrates an API package in accordance with the present invention, namely a User package 110, a Preferences package 120, and a Registry package 130. These packages are described in the following sections, in connection with FIGs 2-4.
  • Rational Rose depiction of the Unified Modeling Language (UML) , which is a language for specifying, constructing, visualizing, and documenting the artifacts of a software- intensive system.
  • UML Unified Modeling Language
  • a class diagram represents the static structure of a system, and shows a pattern of behaviors that the system exhibits. This is accomplished by showing the existence of classes and their relationships. Each class is represented by a box with three sections. The top section lists the class name. The middle section denotes a list of attributes, and the bottom section denotes a list of operations.
  • a solid or dashed line between classes denotes an association or dependency.
  • a white diamond tip denotes aggregation by reference, while a black diamond tip denotes aggregation by value.
  • a triangular arrowhead denotes a restricted navigation, e.g., inheritance of operation but not of structure.
  • a class is a template that defines a data structure, method and function calls for an object.
  • An interface defines a set of methods/function calls that can be manipulated by a class.
  • the class provides the code for implementing an interface.
  • FIG. 2 illustrates a user class/interface diagram in accordance with the present invention.
  • a main UserRegistry interface 210 is the access point for getting information about any user.
  • One or more users can be associated with each terminal (e.g., DTV receiver, set-top box, IRD, TV-enabled PC, etc.)
  • Existing users can be retrieved, new ones can be created, and the current active user can be set via the UserRegistry object 210.
  • the user is represented by the UserProfile object 220, which holds the user's name and the user's preferences.
  • the preferences may be that the user prefers to view/use certain types of television programs (e.g., favorite channels) and/or applications, preferred audio language, personal data, such age, location (address/ zip code) , credit card numbers, etc.
  • the user can be authenticated by invoking the implementation-neutral method authenticate () , which may invoke the particular mechanism of authenticating a user, such as Personal Identification Number (PIN) codes, passwords, etc.
  • PIN Personal Identification Number
  • Users are associated with permissions which are internally used to enforce a security policy. Therefore, new permissions can be granted to each user.
  • the permissions are implementation- specific since they are internal to the terminal .
  • FIG. 3 illustrates a preferences class/interface diagram in accordance with the present invention.
  • the preference package 120 serves two primary purposes: to hold system-wide preferences and to hold user-specific preferences.
  • a system-wide preference is anything that applies to all users.
  • English may be a system wide preferred language which applies to all user unless they override it with their own user-specific preference (e.g., Spanish) .
  • the access to it is provided via the PreferenceRegistry 310 obtained from the RegistryFactory 430 (FIG. 4) .
  • the user-specific preferences can be obtained directly from the user (UserProfile 220) .
  • the abstract Preference interface 330 provides the listener mechanism and access to the unique preference name.
  • the derived class/interface can provide any methods, behavior and data structures needed to describe the specific preference or settings object.
  • Each application can register as a listener (using the addPropertyChangeListener ( ) method) to a specific preference and be notified via the propertyChange ( ) method it must implement .
  • Properties are uniquely identified by their names.
  • the PreferenceAlreadyExists Exception 390 will be thrown. If the application does not have enough privileges to perform any of the PreferenceRegistry 310 methods, the
  • AccessDeniedException 385 will be thrown.
  • PropertyChangeEvent 350 is defined in the standard Java packages (JDK 1.2) . Also, the notations “from security” in class 385, and “from beans” refer to classes ("Security” and “Beans”, respectively) that are defined in JDK 1.2.
  • FIG. 4 illustrates a registry class/interface diagram in accordance with the present invention.
  • the Registry package 130 provides a basic mechanism to construct a Registry object of any kind.
  • the Registry interface 410 is a base interface which is extended by all specific Registries, such as the UserRegistry 210 or the PreferenceRegistry 310.
  • a RegistryListener interface 440 and a RegistryChangeEvent interface 250 are associated with this package.
  • the listener interface 440 is used by any object that wants to be notified of any changes in the Registry 410. Changes are considered those that affect the Registry 410 itself (not necessarily the individual elements in the registry) , such as adding or removing elements to/from the Registry.
  • the RegistryChangeEvent 250 is an abstract class which is extended by the specific registry events.
  • RegistryFactory 430 is a class that hides the actual object construction implementation.
  • the notation "from util" in the EventObject class 415 refers to a class "Util” that is defined in JDK 1.2.
  • This package 110 provides classes and interfaces necessary for user management functions.
  • UserRegistry interface 210 provides access to all users defined on the system. It is derived from Registry 130.
  • This method will create a new user of the specified name.
  • This method returns a list of all known users in the registry. setCurrentUser (newUser : String) : UserProfile
  • This method defines a new current user.
  • the implementation may prompt the user for a password or some other method of authentication.
  • getUser (name : String) : UserProfile
  • This method returns a UserProfile object of the specified name.
  • This interface 220 represents a container of a single user information, such as settings and preferences, billing info, etc. it is derived from UserPermissions 230.
  • This method is called to authenticate a user. It invokes an implementation- specific mechanism for user authentication. It may use a user dialog to ask for a password or PIN, or other authentication mechanisms.
  • This interface 230 defines a list of user permissions that can be granted to a user.
  • This method returns the User Name of the User that caused this event.
  • This interface 240 defines possible causes for the UserRegistryEvent 260.
  • This package 120 defines a set of interfaces and classes which provide a mechanism to define a set of preferences, either at the system level or at the user level .
  • This interface 310 represents a registry of all settings and preferences that can be shared by multiple applications. It is derived from Registry 130. Public Operations: getPreference (preferenceName : String) : org. atsc .preferences .Preference
  • This method allows an application to insert a new preference object into the registry.
  • the new preference must be of a unique name.
  • removePreference preferenceName : String
  • void void
  • This method returns a list of all Preferences currently stored in the registry.
  • This interface 340 is an example of a language preference interface.
  • An ordered list of ISO 639.2 alpha-3 strings is used. The first language in the list is the most desirable language. It is derived from the Preference interface 330.
  • This method returns an ordered list (most desirable first) of three letter ISO language codes. setLanguage (valueList : String []) : void
  • This method allows an application to change the language preference. It returns the new list.
  • This interface 335 represents a parental rating preference based, e.g., on age. It is derived from the Preference interface 330.
  • This method allows an application to change the rating ceiling. It returns the new rating level.
  • This method allows a preference change listener to remove itself from the list of listeners.
  • GetPreferenceName () String This method returns a unique preference name.
  • This interface 320 contains a list of predefined preference names.
  • This event 360 informs the RegistryListener 440 about changes in the PreferenceRegistry 310. It is derived from RegistryChangeEvent 250. Public Operations: getPreference () : org. atsc .preferences .Preference
  • This change concerns the repository, such as adding or removing a Preference from the PreferenceRegistry 310, not a change in the value of the Preference.
  • This package 130 provides a set of supporting and utility classes and interfaces used by other packages.
  • This interface 410 provides a common root to all specialized registry interfaces, such
  • a “base type” is known from the field of object - oriented programming. To illustrate, one can define a class with a set of functions (methods) and internal variables (e.g., a class "Fruit” which represents fruit and its basic characteristics) . One can specialize it by defining a new class, "Apple”, which inherits everything from the class “Fruit”, and adds new functions that are applicable only to Apples but not to Fruit in general. "Fruit” is then referred to as a "base class” or a “base type.”
  • the Registry interface 410 is derived from RegistryType 405.
  • getRegistryType () String Called to determine the type of registry implemented by the object returned by the RegistryFatory ' s (430) method getRegistry () .
  • addRegistryListener listener: RegistryListener
  • This class 430 provides a mechanism to create objects that implement specific Registry interfaces, such as the ApplicationRegistry 490.
  • This class is modeled after the Factory Method design pattern, which, as is known from the field of object-oriented programming, is a methodology and structure for solving a problem.
  • RegistryFactory () : Constructor getRegistry (registryName : String) : org . atsc . registry.Registry
  • RegistryListener This interface 440 allows an object to listen to changes made to the Registry 410.
  • This method of all registered ApplicationRegistryListeners is called by the ApplicationRegistry object 490 when an ApplicaionRegistryEvent is fired (emitted) .
  • This event 250 is a generic registry change event that is extended by all specific registries (such as ApplicationRegistry 490, etc.) to provide specific information about the change. It is derived from EventObject 415. Public Operations: getRegistryType () : Java. lang. String
  • Each derived event will define a set of causes appropriate for the registry it represents.
  • the present invention provides an API for applications to manage/access user-related information on a Digital Television (DTV) Receiver/Terminal.
  • the API provides a multi-user environment, and a registry for preferences which can be associated with an individual user or be common to all users.
  • a set of permissions is associated with each user, or at least with a default user.
  • the permission may provide, for example, a parental control/rating ceiling or permission to buy Impulse Pay Per View (IPPV) programs, or engage in e- commerce transactions (e.g., purchase goods or services via the television) .
  • IPPV Impulse Pay Per View
  • the invention also supports a mechanism where some applications can, and some cannot, access the preferences based on a security policy. This means that the user may allow only specified trusted applications to access his/her credit card number- but not others, for example, for an e-commerce application.
  • the invention is suitable for use with virtually any type of network, including cable or satellite television broadband communication networks, local area networks (LANs) , metropolitan area networks (MANs) , wide area networks (WANs) , internets, intranets, and the Internet, or combinations thereof.
  • LANs local area networks
  • MANs metropolitan area networks
  • WANs wide area networks
  • internets intranets
  • intranets and the Internet, or combinations thereof.

Abstract

Cette invention a trait à une interface de programme d'application (API) relative à des applications, assurant une gestion d'information utilisateur, et/ou permettant d'accéder à cette information et ce, dans un récepteur/terminal de télévision numérique (DTV). Cette interface API fournit un environnement multi-utilisateurs (en utilisant un index utilisateur (210) et des classes de profil utilisateur (220)) ainsi qu'un index de préférences (310) pouvant être associé à un utilisateur individuel (spécifique de l'utilisateur) ou être commun à tous les utilisateurs (à l'échelle du réseau). Un ensemble d'autorisations (230) est associé à chaque utilisateur ou à au moins un utilisateur par défaut, lequel utilisateur représente n'importe qui en train de regarder la télévision. L'autorisation peut porter, par exemple, sur un contrôle parental/plafonnement de tarification ou sur la permission d'acheter des programmes de télévision payante à la carte par unitéIPPV) ou d'entreprendre des transactions de commerce électronique (achat de biens ou de services par l'entremise de la télévision). Le système comporte également un mécanisme (220) par le fait duquel certaines applications peuvent, d'autres ne le pouvant pas, accéder aux préférences fondées sur une politique de sécurité. Ce qui signifie que l'utilisateur peut autoriser des applications précises et validées à accéder à son numéro de cartes de crédit, par exemple, une application de commerce électronique, mais interdire cet accès à d'autres.
EP99950245A 1998-11-12 1999-10-07 Recepteur de television numerique avec interface de programme d'application pour gestion utilisateur Withdrawn EP1166549A1 (fr)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
US10794998P 1998-11-12 1998-11-12
US107949P 1998-11-12
PCT/US1999/023346 WO2000030345A1 (fr) 1998-11-12 1999-10-07 Recepteur de television numerique avec interface de programme d'application pour gestion utilisateur

Publications (1)

Publication Number Publication Date
EP1166549A1 true EP1166549A1 (fr) 2002-01-02

Family

ID=22319348

Family Applications (1)

Application Number Title Priority Date Filing Date
EP99950245A Withdrawn EP1166549A1 (fr) 1998-11-12 1999-10-07 Recepteur de television numerique avec interface de programme d'application pour gestion utilisateur

Country Status (6)

Country Link
EP (1) EP1166549A1 (fr)
JP (1) JP2002530943A (fr)
KR (1) KR20010080427A (fr)
AU (1) AU6294499A (fr)
CA (1) CA2351582A1 (fr)
WO (1) WO2000030345A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107888951A (zh) * 2017-11-27 2018-04-06 四川金熊猫新媒体有限公司 片单管理方法、装置及服务器

Families Citing this family (31)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
USRE47908E1 (en) 1991-12-23 2020-03-17 Blanding Hovenweep, Llc Ergonomic man-machine interface incorporating adaptive pattern recognition based control system
USRE48056E1 (en) 1991-12-23 2020-06-16 Blanding Hovenweep, Llc Ergonomic man-machine interface incorporating adaptive pattern recognition based control system
CN1867068A (zh) 1998-07-14 2006-11-22 联合视频制品公司 交互式电视节目导视系统及其方法
US6859799B1 (en) 1998-11-30 2005-02-22 Gemstar Development Corporation Search engine for video and graphics
US6618858B1 (en) * 2000-05-11 2003-09-09 At Home Liquidating Trust Automatic identification of a set-top box user to a network
US7103906B1 (en) 2000-09-29 2006-09-05 International Business Machines Corporation User controlled multi-device media-on-demand system
KR101399240B1 (ko) 2000-10-11 2014-06-02 유나이티드 비디오 프로퍼티즈, 인크. 매체 콘텐츠 배달 시스템 및 방법
JP4216460B2 (ja) * 2000-12-26 2009-01-28 パイオニア株式会社 情報処理システム、端末装置及び情報処理方法
US7089578B2 (en) * 2001-09-29 2006-08-08 Koninklijke Philips Electronics N.V. Apparatus and method for dynamically updating a viewer profile in a digital television device
DE10149977A1 (de) * 2001-10-10 2003-04-24 Siemens Ag Verfahren zum Zugriff auf Nutzerdaten, zugehörige Datenverarbeitungsanlage, zugehöriges Programm und zugehörige Datenstruktur
JP2003140890A (ja) * 2001-10-31 2003-05-16 Asgent Inc 電子機器設定情報作成方法及び装置並びにセキュリティポリシー作成方法及び関連装置
US20030121057A1 (en) * 2001-12-20 2003-06-26 Koninklijke Philips Electronics N.V. Script-based method for unattended control and feature extensions of a TV or settop box device
WO2003073762A1 (fr) * 2002-02-27 2003-09-04 Opentv, Inc. Procede et appareil permettant d'obtenir un objet a profil de securite hierarchique
AU2003208547A1 (en) * 2002-04-12 2003-10-27 Koninklijke Philips Electronics N.V. Downloading of programs into broadcast-receivers
US7493646B2 (en) 2003-01-30 2009-02-17 United Video Properties, Inc. Interactive television systems with digital video recording and adjustable reminders
KR100720712B1 (ko) * 2005-02-15 2007-05-21 삼성전자주식회사 접근권한 설정 시스템 및 방법 그리고 그에 적용되는 원격제어장치
KR20060128208A (ko) * 2005-06-09 2006-12-14 삼성전자주식회사 사용자 선호에 따른 어플리케이션 제공 장치 및 방법
US8074288B2 (en) * 2005-07-15 2011-12-06 Microsoft Corporation Isolation of application-specific data within a user account
KR100725397B1 (ko) 2005-07-22 2007-06-07 삼성전자주식회사 방송 수신 장치 및 상기 방송 수신 장치를 이용한데이터방송 어플리케이션 실행 방법
US7802267B2 (en) 2005-11-03 2010-09-21 Microsoft Corporation Compliance interface for compliant applications
US9681105B2 (en) 2005-12-29 2017-06-13 Rovi Guides, Inc. Interactive media guidance system having multiple devices
DE102006030284A1 (de) * 2006-06-30 2008-01-03 Siemens Home And Office Communication Devices Gmbh & Co. Kg System mit wenigstens zwei separaten personalisierten intelligenten Benutzerschnittstellen
KR20080024005A (ko) * 2006-09-12 2008-03-17 삼성전자주식회사 영상처리장치 및 그 제어방법
US20090019492A1 (en) 2007-07-11 2009-01-15 United Video Properties, Inc. Systems and methods for mirroring and transcoding media content
JPWO2009019828A1 (ja) * 2007-08-03 2010-10-28 パナソニック株式会社 受信装置
US10063934B2 (en) 2008-11-25 2018-08-28 Rovi Technologies Corporation Reducing unicast session duration with restart TV
US8621520B2 (en) 2009-05-19 2013-12-31 Qualcomm Incorporated Delivery of selective content to client applications by mobile broadcast device with content filtering capability
US9014546B2 (en) 2009-09-23 2015-04-21 Rovi Guides, Inc. Systems and methods for automatically detecting users within detection regions of media devices
US8805418B2 (en) 2011-12-23 2014-08-12 United Video Properties, Inc. Methods and systems for performing actions based on location-based rules
CN103152640B (zh) * 2013-03-07 2017-04-19 东莞宇龙通信科技有限公司 一种电视系统的控制方法及装置
US9674563B2 (en) 2013-11-04 2017-06-06 Rovi Guides, Inc. Systems and methods for recommending content

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5758257A (en) * 1994-11-29 1998-05-26 Herz; Frederick System and method for scheduling broadcast of and access to video programs and other data using customer profiles
US6163316A (en) * 1997-01-03 2000-12-19 Texas Instruments Incorporated Electronic programming system and method
EP0944257A1 (fr) * 1998-03-06 1999-09-22 CANAL+ Société Anonyme Terminal multimedia pour plusieurs utilisateurs

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
See references of WO0030345A1 *

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107888951A (zh) * 2017-11-27 2018-04-06 四川金熊猫新媒体有限公司 片单管理方法、装置及服务器
CN107888951B (zh) * 2017-11-27 2020-04-28 四川金熊猫新媒体有限公司 片单管理方法、装置及服务器

Also Published As

Publication number Publication date
CA2351582A1 (fr) 2000-05-25
WO2000030345A1 (fr) 2000-05-25
JP2002530943A (ja) 2002-09-17
AU6294499A (en) 2000-06-05
KR20010080427A (ko) 2001-08-22

Similar Documents

Publication Publication Date Title
EP1166549A1 (fr) Recepteur de television numerique avec interface de programme d'application pour gestion utilisateur
KR100564273B1 (ko) 다수 이용자들에게 적합한 멀티미디어 단말장치
US7058964B2 (en) Flexible digital cable network architecture
US6587873B1 (en) System server for channel-based internet network
US6745223B1 (en) User terminal for channel-based internet network
EP1522191B1 (fr) Support de fonctionnalite de television interactive commune au moyen d'une syntaxe de moteur de presentation
JP4739370B2 (ja) 情報提供装置、情報表示装置、情報提供システム、制御方法、制御プログラム、および、記録媒体
Piesing The DVB multimedia home platform (MHP) and related specifications
US6993132B2 (en) System and method for reducing fraud in a digital cable network
US8484634B2 (en) System for signaling an application to a host device and method therefor
US20030192047A1 (en) Exporting data from a digital home communication terminal to a client device
EP1088446B1 (fr) Securite dynamique pour recepteurs de television numeriques
US20150264420A1 (en) Method for controlling the display of a digital television set
US6721949B1 (en) Kernel abstraction layer for digital television set-top box firmware
WO2010002756A1 (fr) Procédé et appareil pour une identification biométrique d'un utilisateur dans un récepteur de communication de diffusion
KR20090069385A (ko) Ｉｐｔｖ를 위한 사용자 인터페이스 방법 및 셋탑박스
US7328253B2 (en) Service providing system, service providing terminal, client terminal, and storage medium
CZ20003254A3 (cs) Terminál pro zpracování digitálních dat a způsob jeho provozu

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20010608

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE

RBV Designated contracting states (corrected)

Designated state(s): DE FR GB

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: THE APPLICATION IS DEEMED TO BE WITHDRAWN

18D Application deemed to be withdrawn

Effective date: 20070503

P01 Opt-out of the competence of the unified patent court (upc) registered

Effective date: 20230522