WO2006017218A2 - Service de syntoniseur et recepteur dtv en tant que dispositif upnp - Google Patents

Service de syntoniseur et recepteur dtv en tant que dispositif upnp Download PDF

Info

Publication number
WO2006017218A2
WO2006017218A2 PCT/US2005/024521 US2005024521W WO2006017218A2 WO 2006017218 A2 WO2006017218 A2 WO 2006017218A2 US 2005024521 W US2005024521 W US 2005024521W WO 2006017218 A2 WO2006017218 A2 WO 2006017218A2
Authority
WO
WIPO (PCT)
Prior art keywords
service
network
dtv
resource
resource manager
Prior art date
Application number
PCT/US2005/024521
Other languages
English (en)
Other versions
WO2006017218A3 (fr
Inventor
Rajesh B. Khandelwal
Arlis Boyd Dodson
Luyang Li
Original Assignee
Matsushita Electric Industrial Co. Ltd.
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 Matsushita Electric Industrial Co. Ltd. filed Critical Matsushita Electric Industrial Co. Ltd.
Publication of WO2006017218A2 publication Critical patent/WO2006017218A2/fr
Publication of WO2006017218A3 publication Critical patent/WO2006017218A3/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N7/00—Television systems
    • H04N7/16—Analogue secrecy systems; Analogue subscription systems
    • H04N7/162—Authorising the user terminal, e.g. by paying; Registering the use of a subscription channel, e.g. billing
    • H04N7/163—Authorising the user terminal, e.g. by paying; Registering the use of a subscription channel, e.g. billing by receiver means only
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2803—Home automation networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2803—Home automation networks
    • H04L12/2807—Exchanging configuration information on appliance services in a home automation network
    • H04L12/281—Exchanging configuration information on appliance services in a home automation network indicating a format for calling an appliance service function in a home automation network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2803—Home automation networks
    • H04L12/2816—Controlling appliance services of a home automation network by calling their functionalities
    • H04L12/2821—Avoiding conflicts related to the use of home appliances
    • 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/20—Servers specifically adapted for the distribution of content, e.g. VOD servers; Operations thereof
    • H04N21/23—Processing of content or additional data; Elementary server operations; Server middleware
    • H04N21/235—Processing of additional data, e.g. scrambling of additional data or processing content descriptors
    • 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/41—Structure of client; Structure of client peripherals
    • H04N21/426—Internal components of the client ; Characteristics thereof
    • H04N21/42607—Internal components of the client ; Characteristics thereof for processing the incoming bitstream
    • H04N21/4263—Internal components of the client ; Characteristics thereof for processing the incoming bitstream involving specific tuning arrangements, e.g. two tuners
    • 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/434—Disassembling of a multiplex stream, e.g. demultiplexing audio and video streams, extraction of additional data from a video stream; Remultiplexing of multiplex streams; Extraction or processing of SI; Disassembling of packetised elementary stream
    • H04N21/4345—Extraction or processing of SI, e.g. extracting service information from an MPEG stream
    • 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/434—Disassembling of a multiplex stream, e.g. demultiplexing audio and video streams, extraction of additional data from a video stream; Remultiplexing of multiplex streams; Extraction or processing of SI; Disassembling of packetised elementary stream
    • H04N21/4348—Demultiplexing of additional data and video streams
    • H04N21/4349—Demultiplexing of additional data and video streams by extracting from data carousels, e.g. extraction of software modules from a DVB carousel
    • 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/435—Processing of additional data, e.g. decrypting of additional data, reconstructing software from modules extracted from the transport stream
    • 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/435—Processing of additional data, e.g. decrypting of additional data, reconstructing software from modules extracted from the transport stream
    • H04N21/4355—Processing of additional data, e.g. decrypting of additional data, reconstructing software from modules extracted from the transport stream involving reformatting operations of additional data, e.g. HTML pages on a television screen
    • 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/436—Interfacing a local distribution network, e.g. communicating with another STB or one or more peripheral devices inside the home
    • H04N21/43615—Interfacing a Home Network, e.g. for connecting the client to a plurality of peripherals
    • 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/462—Content or additional data management, e.g. creating a master electronic program guide from data received from the Internet and a Head-end, controlling the complexity of a video stream by scaling the resolution or bit-rate based on the client capabilities
    • H04N21/4622—Retrieving content or additional data from different sources, e.g. from a broadcast channel and the Internet
    • 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/8166—Monomedia components thereof involving executable data, e.g. software
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N7/00—Television systems
    • H04N7/10—Adaptations for transmission by electrical cable
    • H04N7/106—Adaptations for transmission by electrical cable for domestic distribution
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2803—Home automation networks
    • H04L2012/2847—Home automation networks characterised by the type of home appliance used
    • H04L2012/2849—Audio/video appliances
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services
    • 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/41—Structure of client; Structure of client peripherals
    • H04N21/426—Internal components of the client ; Characteristics thereof
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N5/00—Details of television systems
    • H04N5/44—Receiver circuitry for the reception of television signals according to analogue transmission standards
    • H04N5/50—Tuning indicators; Automatic tuning control

Definitions

  • the present invention generally relates to a DTV receiver as a UPnP device, where the basic functionalities of the DTV receiver are exposed as UPnP services, such as a tuner service, a resource manager service, and/or time and stream event service, etc.
  • UPnP services such as a tuner service, a resource manager service, and/or time and stream event service, etc.
  • DTV services are composed of audio media and video media synchronized with one another and with a software application that is bundled with the audio and video media.
  • the application bundled with the media is termed a service bound application.
  • Service bound applications are signaled via an Application Information Table (AlT) in the in- band Transport Stream (TS).
  • AlT Application Information Table
  • TS Transport Stream
  • an unbound application is not bound to any audio or video media.
  • XAIT extended AIT
  • a complete XAIT is delivered via a CableCARD extended data channel
  • an XAIT fragment is passed as a parameter to a DTV Application Program Interface (API method).
  • API method DTV Application Program Interface
  • the architecture includes a broadcast network, such as Cable, Terrestrial, or Satellite, a home network, a DTV receiver connected to both the broadcast network and the home network, and a set of DTV-related UPnP services implemented on the DTV receiver to expose its functionalities to other devices on the home network.
  • a tuner service exposes characteristics and capabilities of tuner(s) in the DTV receiver, and controls operation of the tuners in accordance with control commands received from control points.
  • a resource manager service is adapted to manage allocation of resources on the DTV receiver and keep track of resource allocation status.
  • a time and stream event service maintains a common time for the network and delivers triggers to the network from a cache of triggers received from a broadcast carousel.
  • Figure 1 is a block diagram illustrating a DTV receiver as a UPnP device in accordance with the present invention
  • Figure 2 is a block diagram illustrating an OCAP home networking device in accordance with the present invention
  • FIG. 3 is a network diagram illustrating a DTV receiver integrated with other UPnP devices and control points in accordance with the present invention
  • FIG. 4 is a network diagram illustrating a legacy receiver implemented as a UPnP device in accordance with the present invention
  • FIG. 5 is a block diagram illustrating DTV actions and events performed and generated by a DTV device in accordance with the present invention
  • Figure 6 is a network diagram for a method of signaling OCAP services stored on removable storage media in accordance with the present invention
  • Figure 7 is a network diagram illustrating SI data translation in accordance with the present invention.
  • Figure 8 is a block diagram illustrating mapping of XAIT to secondary storage services and applications in accordance with the present invention.
  • Figure 9 is a block diagram illustrating the prior art XAIT update mechanism
  • Figure 10 is a block diagram illustrating XAIT update in accordance with the present invention.
  • Figure 11 is a block diagram illustrating common-media XAIT update event/XAIT delivery in accordance with the present invention
  • Figure 12 is a block diagram illustrating dual-media update event/XAIT delivery in accordance with the present invention
  • Figure 13 is a block diagram illustrating an EPG user interface with merged broadcast/secondary SI in accordance with the present invention
  • Figure 14 is a block diagram illustrating recording of broadcast service applications in accordance with the present invention
  • Figure 15 is a block diagram illustrating a DTV-HNF distributed resource manager working in tandem with an OCAP resource manager to keep track of resource allocation status in accordance with the present invention
  • Figure 16 is a block diagram illustrating a local reservation process in accordance with the present invention.
  • Figure 17 is a block diagram illustrating a remote reservation process in accordance with the present invention.
  • Figure 18 is a network diagram illustrating triggers from a broadcast carousel being cached in a datastore for later dispatch by the receiver via broadcast on a home network to appliances in accordance with the present invention
  • Figure 19 is a block diagram illustrating a DTV receiver including a trigger service that operates according to a time service in accordance with the present invention
  • Figure 20 is a block diagram illustrating a content listing service interfacing with an OCAP SI manager and an OCAP recording manger in accordance with the present invention.
  • Figure 21 is a block diagram of the content listing service architecture, including the content listing service employing uniform locators mapped to multiple content sources in accordance with the present invention.
  • the DTV receiver 100 as a UPnP device can include several services.
  • the receiver 100 can include an EPG content listing service 102, a content display service 104, and a tuner service 106. It can also include a time and stream event service 108, a resource manager service 110, a content recording or duplication service 112, a Diagnostic service 114, and a DRM service 116. Additionally, it can include a playback control service 118 including an AVT service 120, and a content delivery service 122 including a CM service 124.
  • the DTV receiver 200 can have a network manager 202 providing registration, discovery, and eventing mechanisms for services described above. These services can include a tuner service 204 as described above, a content delivery service 206, a content display service 208, a playback control service 210, a content rec./dup. service 212, a content management service 214, a DRM service 216, a diagnostic service 218, a resource manager 220, and other services.
  • Technology glue 222 such as UPnP, OSGi, etc.), serves to support the underlying functionality.
  • the DTV receiver 300 can be integrated with other UPnP devices 302A-302C and control points 304 by functioning as both a service and a control point. Services reside on the DTV receiver.
  • the receiver 300 automatically announces its presence, description, allows control, and generates events. It also exports its functionalities by way of various services, such as the tuner service, hard disk service, and EPG service. It further controls other UPnP services, and allows dynamic plug-in and plug-out.
  • a legacy receiver 400 can also be implemented as a UPnP device according to some embodiments of the present invention.
  • the legacy receiver can be operably connected to a PC via an appropriate interface such as Ethernet or USB interface of the legacy DTV receiver.
  • Service can be deployed and therefore reside on the PC as proxy services.
  • the legacy receiver is adapted by configuration with the proxy services to automatically announce its presence, description, allow control, and generate events.
  • Embodiments of the invention can export services from the legacy system for smooth integration, control other UPnP devices, and allow dynamic plug-in and plug-out.
  • FIG. 5 shows actions, events and state variables. These are generalized and are applicable to all the services mentioned above.
  • Each service mentioned above implements actions and generates events based on its functionality in accordance with UPnP architecture.
  • Each service 502A and 502B on a device 500 also maintains state variables 504A and 504B.
  • An action 506 can be performed on a service, potentially modifying one or more of its state variables. Action examples include: tune an RF receiver; render an MPEG-2 video elementary stream; launch a VOD session, get service information tables, reserve a resource such as a tuner, etc..
  • An event listener 508 is notified of events 510 for which the listener has registered, with events being generated by services, for example, in response to change in their state variables.
  • Event examples include: RF tuning complete; MPEG-2 video elementary stream playout status change; VOD session status change; new DTV service announcement; DTV service status change; new DTV device announcement; DVT device status change; and DTV resources busy or free.
  • the examples of actions, events, and state variables mentioned above are merely exemplary in nature and each service mentioned above can implement more or different actions, events, and state variables based on its functionality.
  • the present invention is directed toward signaling and sharing (launching) DTV applications/services to other DTV devices [and PCs] in a home network.
  • Signaling implies notifying the receiver that a DTV service is available on a particular channel (or transport stream).
  • Launching implies the mechanism by which the application/video/audio/data is transmitted to the receiver so that the receiver can launch or execute the service.
  • a DTV service is a combination of audio/video/application/data that can be presented as a whole to the user.
  • In-band - (broadcast - one way) - carries signaling, application, AA/, data (bound services) from the head-end to the receiver. This signaling is performed via the AIT.
  • Out-of-band (OOB) - (used for two-way communication with the head-end) - is used for signaling unbound services.
  • unbound applications are applications that are not related to any broadcast service (e.g., EPG or game application).
  • Unbound applications are signaled via an XAIT delivered via OOB channel to the receiver. The signaling of the unbound application is performed via OOB channel, but the actual delivery could be performed either via OOB or in-band.
  • Today, unbound applications originate either from the head-end or installed by the manufacturer at the time of manufacturer.
  • Some embodiments of the present invention prepare for the possibility that applications or DTV services can also become available from other means such as DVD, SD memory card, home network, and other data storage sources.
  • other means such as DVD, SD memory card, home network, and other data storage sources.
  • the present invention includes a tuner service that exposes functionalities of a real tuner to other DTV devices [and PCs] on a home network. For example, close captions, vertical blanking interval (VBI) contents, emergency alert messages, channel maps, and/or system information tables can be exposed.
  • VBI vertical blanking interval
  • the virtual tuner thus accomplished can use a real tuner as a source of media, the Internet or similar communications system as a source of media, or storage on the home network as a source of media.
  • the virtual tuner exposes SI (metadata) about broadcast, stored, or other dynamically discovered content.
  • Dynamically discovered content is dynamically discovered when a datastore containing media is operably connected to the home network. For example, when a SD card with a DTV service is inserted in an SD interface of the DTV receiver, the virtual tuner service registers that service and makes it available to other devices in the network. As another example, content on a DVD disk can be dynamically discovered when the disk is inserted in a DVD drive connected to the home network.
  • the virtual tuner can be logically identical to a real tuner (i.e. supports all the functions supported by a real tuner). It can enable a receiver with both a real tuner and a home networking interface to act as a head-end in the home by exposing tuner functionalities in the home network.
  • the virtual tuner service accomplishes notification of AITVXAIT, CAS, Emergency Alert, and other bound and unbound applications from storage. Additionally, the service accomplishes SI translation; for example, EPG data can be translated into a known XML format requested by a client.
  • the service discovery protocol to which the tuner service adheres can vary, and can include UPnP, OSGi, and other specified protocols.
  • the device I/F appearance can vary, and can be determined in part by a stylesheet on the DTV device or control point in question.
  • some controls that can be provided include controls for switching channels on a real tuner or in recorded content.
  • the user of the DTV as a control point can interface with the virtual tuner in order to select between real channels, and in order to switch between channels of recorded content.
  • the implementation may also attach a time-shift buffer to enable live-TV transmission to other devices in the home network
  • the virtual tuner service can maintain copy protection for content by observing copy protection data associated with the content and obeying it. For example, content on a disk may be labeled read only, and thus the service can prevent the user from selecting to record the content. Similarly, the service can observe copy protection data associated with a bound service arriving by broadcast and obey that data. As an example, the data can specify that the service can be recorded to one place on the network in an encrypted fashion, with the decryption key being hidden elsewhere on the network by the service. In this case, the user may be allowed to view the content on the home network a given number of times, but not to record or transfer the content.
  • a virtual tuner provided by the tuner service can have various properties.
  • it can record the last time it was tuned. Also, it can attach a time shift buffer. Further, it can store user profiles. Additionally, it can achieve a required metadata format. Still further, it can accomplish encryption and decryption, and engage in or enable encryption/decryption key exchange. Finally, it can accomplish tuner reservation and notification of tuner availability.
  • the tuner service can employ various actions.
  • the service can have actions for tuning a real tuner. It can also have actions for acquiring and/or assigning a channel number. It can additionally have actions for acquiring or assigning a frequency. It can further have actions for reserving and releasing tuners. It can still further have actions for attaching time shift buffers. Yet further, it can have actions for getting channel maps.
  • the tuner service may also implement and expose functionalities of a point-of-deployment module. Finally, it can have trick-play actions, including play, stop, forward and rewind.
  • the tuner service can have various state variables and events.
  • the service can have the following state variables: current set frequency; current set channel number; and reservation status.
  • the service can have the following events: tuner reserved; tuner released; AIT/XAIT; EAS; MMI/CAS; triggers such as stream events; system time table; start of advertisement; and end of advertisement.
  • the home network can include a cable network 600 connected to an OCAP server 602, which is also connected to OCAP clients 604A-604D. "Live" OCAP services are received from the cable network.
  • An OCAP monitor application may bridge or control the sharing between the OCAP network with a UPnP AV network.
  • the UPnP AV network can include a UPnP optical drive 606, a UPnP DVD drive 608, and a UPnP CD drive 610, each connected to the OCAP server 602 by Ethernet 612.
  • Each of the OCAP clients 604A-604D can be configured with inexpensive, fixed-frequency RF tuners, as well as other network interfaces, such as 802.11 , 1394, and USB.
  • OCAP server 602 can be configured with multiple RF tuners. SD cards and DVD drives can also be integrated with the OCAP server 602 and/or clients 604A- 604D. [0048] Turning now to Figure 7, SI data translation can occur according to an XML format requested by a client.
  • DTV terminal 700 connects a home RF network having an OCAP DTV terminal 702A and MHP DTV terminal 702B to a home Ethernet network having an MPEG-2 player 704A, laptop computer 704B running a home networking application, and another DTV terminal 704C.
  • the DTV terminal 700 also connects these networks with cable network 706 and XML SI database 708.
  • Broadcast SI data are received from cable network 706, converted to XML, and merged with home network SI data on database 708.
  • XML document type description (DTD) specifies format of merged broadcast/home network SI data.
  • DTV terminal can thus deliver the contents of database 708 to the home RF network and Ethernet network.
  • the home network devices provide home network SI data and, in turn, accept merged XML SI data.
  • XML SI data are converted to an appropriate format before transmission to DTV terminals that cannot ingest XML SI data, such as OCAP or DVB-MHP.
  • XML SI data are converted to an appropriate format before transmission to home network devices that cannot ingest XML SI data, such as MPEG-2 tables.
  • Merged SI can include location-resolution information; for example: IP address; TCP/IP or UDP port number; IEEE1394 identifier; and hardware interfaces. Such information is needed when multiple sources provide a common service (e.g., a given media file). This information can be co-located on the DTV terminal or anywhere on the home network [0050] Turning now to Figures 8-14, signaling the secondary storage
  • OCAP service is described in greater detail.
  • the signaling occurs in a manner that ensures the service is handled by the OCAP terminal in the same fashion as a broadcast OCAP service.
  • the signaling mechanisms in OCAP include the (DVB-MHP) Application Information Table (AIT) and the Extended AIT (XAIT). It is currently expected that the XAIT will be used to announce the presence of unbound applications delivered in the lnband broadcast stream or resident in the OCAP terminal, although it is possible that unbound applications could be delivered to the terminal via Out-of-Band (OOB).
  • OOB Out-of-Band
  • Some embodiments of the present invention broaden usage of the XAIT to include announcing the presence of OCAP services and OCAP applications (service-bound or unbound) resident in secondary storage.
  • the XAIT can be used (though AITs could be used as well) to signal service-bound applications associated with secondary storage AA/ media assets.
  • the current OCAP specification provides two mechanisms for delivering XAIT updates: the OOB stream and an API available to privileged OCAP applications (so-called “Monitor Applications").
  • Some embodiments of the present invention employ a third, broad, mechanism for delivering XAIT updates: the OCAP implementation monitors every OCAP terminal interface (other than lnband and OOB) for XAIT Update Events.
  • the format of these events can be determined in part by the nature of the interface (e.g., PCMCIA, IEEE1394, IP, 801.11x).
  • Each XAIT Update Event can identify the media on which the XAIT is to be received and whether the XAIT must be "pulled” into the OCAP terminal or will be "pushed” at the OCAP terminal by an outside agent.
  • the XAIT Update Event and the XAIT itself may arrive by the same medium, this is not necessarily the case.
  • an open specification like the Session Description Protocol (SDP) and/or the Session Initial Protocol (SIP) may be used to "signal" the secondary storage XAIT.
  • SDP Session Description Protocol
  • SIP Session Initial Protocol
  • the current OCAP specification implies the XAIT is distinguished from the AIT by the delivery mechanism alone: a table arriving via lnband is assumed to be an AIT; a table arriving via OOB is assumed to be an XAIT.
  • the two MPEG-2 table IDs are identical. Therefore, the following rule can be added to the OCAP specification: "an *AIT arriving by any mechanism other than lnband is assumed to be an XAIT".
  • Some changes or additions can be made to the OCAP specification that supports signaling according to the present invention. Some of these changes can be viewed as new rules. For example, one rule can be that any AIT or XAIT arriving by any mechanism other than lnband is assumed to be XAIT. Also, another rule can be that XAIT can be used to announce the presence of DTV services and applications (service-bound or unbound) resident in secondary storage. Additionally, a third rule can be that the XAIT format is extended to identify the origin of the XAIT. Another change or addition that can be made to the OCAP specification is definition of a new XAIT source that is consistent with the existing DTV model.
  • XAIT-update events can occur in various ways and in response to varying stimuli.
  • one implementation of the present invention can continuously monitor all interfaces. When a connection on an interface is detected and presence of a DTV service is detected, an XAIT- update event can be generated. Another implementation can choose to scan the attached storage for XAITs without needing an XAIT-update event.
  • Each XAIT Update Event can identify the media on which the XAIT is to be received and whether the XAIT must be "pulled” into the DTV terminal or will be “pushed” at the DTV terminal by an outside agent. Although the XAIT Update Event and the XAIT itself may arrive by the same medium, this is not necessarily the case.
  • a transport stream 806 stored in DVD-RAM 800B can contain, in addition to an application on an object carousel and audio/video/digital assets, an AIT executed as a bound service.
  • SD card 808A can contain XAIT service description 810 mapped to unbound application 812, which is executed as an abstract service.
  • hard disk 814 can contain XAIT service description 816 mapped to an unbound application 818 executed as an abstract service, and TS AIT service description 820 mapped to a bound application 822 executed within a bound service. If appropriate, the XAIT need not be co-located with the service media.
  • multiple XAIT service descriptions 824 on SD card 808B can be mapped to unbound applications 826A-826D on remote hard disk 828, which can be executed as bound services
  • Varying service discovery protocols can be employed in accordance with varying embodiments.
  • an open specification like the Session Description Protocol (SDP) and/or the Session Initiation Protocol (SIP) may be used to "signal" the secondary storage XAIT.
  • SDP Session Description Protocol
  • SIP Session Initiation Protocol
  • AITs arriving at the edge of a DTV Home Network lnband can be mapped to XAIT format by the framework on-the-fly.
  • XAITs that encapsulate AIT data can be disseminated to the DTV Home Network.
  • XAIT-update events can trigger a service registration in UPnP or OSGi.
  • broadcast of XAIT update events to networked clients can occur via SIP/SDP or the OSGi or UPnP frameworks.
  • embodiments can have the ability to broadcast DTV services to other clients that are in NGNA Guaranteed Service Domain or Authorized Service Domain.
  • a monitor application can drive update of the SI database, reflecting stored DTV services.
  • the monitor application can modify XAIT schema to identify sharable services.
  • sharing of services can be under MSO control.
  • a monitor application can act as a registrar of applications stored on secondary storage.
  • Figure 9 illustrates the prior art XAIT update mechanism
  • Figure 10 illustrates update according to some embodiments of the present invention.
  • the OCAP terminal 900 and its resident monitor application 902 can register XAIT update via API.
  • the native layer 904 containing the service descriptions is updated via OOB.
  • the XAIT update mechanism depicted in Figure 10 allows the service descriptions in the native layer to additionally be updated from a communications system 1000, SD memory card 1002, DVD-RAM 1004, or other source. Communication of XAIT updates from system 1000 can occur over PCM/CIA 1006A, IEEE 1394 1006B, IP network 1006C, wireless 1006D, USB 1006E, and/or other communication mechanisms. Accordingly, OCAP host 1008 can place OCAP services on secondary storage 1010, such as SD card, hard drive, DVD-RAM, and other storage mechanisms. [0062] Turning now to Figure 11 , common-media XAIT update event/XAIT delivery is illustrated by example.
  • Terminal 1100A can push the XAIT to terminal 1100B.
  • terminal 1100A can pull the XAIT after receiving a separate XAIT update event (such as a UPnP event).
  • Terminal 1100A could alternatively broadcast secondary storage service throughout the virtual private domain.
  • terminal 1100B can simultaneously record a separate broadcast service to local storage disk 1102.
  • XAIT can be transmitted from terminal 1100A to terminal 1100B following an XAIT update event, and the broadcast stream can be enabled and transmitted from terminal 1100A to terminal 1100B following selection of the broadcast service 604 on terminal 110OA by terminal 1100B.
  • an XAIT update event can originate at one device while the XAIT and the service stream originate at another device.
  • Two scenarios are explored in Figure 12 to illustrate this point.
  • an XAIT update event is communicated from OCAP terminal 1200A to OCAP terminal 1200B.
  • Terminal 1200B then pulls the XAIT update from hard disk 1202, and subsequently selects a service on the hard disk 1202. Streaming then occurs from hard disk 1202 to terminal 1200B.
  • terminal 1200A first pulls an XAIT update from hard disk 1202.
  • Terminal 1200A modifies the update and pushes it to OCAP terminal 1200C.
  • Terminal 1200C selects the service from terminal 1200A, unaware that the content is stored on hard disk 1202. In response, terminal 1200A pulls the selected stream from hard disk 1202, modifies tables in the stream as needed, and transmits the modified stream to terminal 1200C.
  • the user interface 1300 can provide guide video 1302 with controls for selecting service categories, including broadcast service control 1304, abstract service control 1306, and secondary storage service control 1308. Selecting a service category results in access and display information about of services of the category. The categorical services information can be displayed in services list display area 1310 for final selection by the user.
  • XAIT of broadcasts, monitor applications, and secondary storage are accessed in the EPG 1312 having the interface 1300 through services database 1314. It should be noted that secondary storage services can be mapped to broadcast services or abstract services and accessed and executed as such in some embodiments of the present invention.
  • FIG 14 recording of broadcast service applications according to some embodiments of the present invention is explored with an example. Applications 1400 arriving inband at a OCAP terminal 1402 are delivered to a media rendering device 1404, such as a TV, and also recorded to DVD-RAM 1406. The Applications persisting with XAIT, certificates, hard files, and media assets on DVD-RAM 1406 are thereafter accessible by any other OCAP terminal 908 for delivery to another media rendering device 1410.
  • Some embodiments of the present invention are or include a discoverable soft-tuner/interface service capable of launching remote DTV services. Entries in the SI database marked appropriately to indicate if the application is sharable/stored/local or remote. Applications are selected and launched from the EPG as if the application is local. The service allows launching of live applications from a remote client. In some embodiments, the application is downloaded from the remote client and executed locally. For example, an application can be cached locally and then launched. Alternatively, an application can be launched locally from remote storage. In additional or alternative embodiments, an application is launched on a remote client, with only the screen displayed locally as if the application is running on the local machine.
  • the soft tuner service exposes VOD, I PPV, and comparable sessions in the same fashion as for standard broadcast and stored DTV services.
  • the service can also allow launching and control of these sessions from EPG (via soft-tuner), potentially spanning multiple DTV terminals.
  • a session can be initiated at a given DTV terminal and then transferred to a second DTV terminal (perhaps in a different room).
  • the soft-tuner service can be implemented as a discoverable UPnP or OSGi service. Alternatively or additionally, it can be implemented as a DTV service with a UPnP or OSGi proxy. Either approach allows clients to select and tune to local or remote services in a seamless fashion.
  • the architecture can bridge a UPnP AV network and a DTV home network.
  • Some embodiments of the soft-tuner service define new OCAP monitor application functionality to control bridging of UPnP AV network and DTV home network.
  • the MA can play the role of a UPnP control point.
  • the MA can be configured to translate services information from UPnP to OCAP.
  • the MA uses OCAP API to transparently update SI database, mimicking receipt of XAIT updates.
  • DTV services live, stored
  • OSGi services can be exposed as UPnP or OSGi services.
  • the service can define a new UPnP device template, such as: DTV Services Removable Storage Device; and/or UPnP DTV Tuner Device.
  • the resource manager service of the DTV receiver provides a resource manager that manages local resources such as tuners, bandwidth (in terms of input and output streams per interface and cumulative), graphics device, background device, video device, decoder/JMF, and storage and others. It also allows reservations from a remote device.
  • the service can accomplish priority-based and/or user-profile based allocation. For example, requests originating from the device itself may have the highest priority, while requests originating from a device in a bedroom of a home in which the home network is implemented may have a next-highest priority. Accordingly, requests originating from a device in a basement of the home may have the lowest priority.
  • Such parameters may be set during network administration and may be considered during resource contention resolution.
  • different users registered to the network can have different priorities and can identify themselves by password. The priorities can be stored and accessed on the network in user profiles.
  • the resource manager service Being a discoverable service, the resource manager service provides notifications when resources are idle versus busy by broadcast or based on subscription. In addition to managing local resources, it provides a resource allocation snapshot either distributed and/or available to all interested clients. It further maps OCAP/DTV resource allocation requests to UPnP/OSGi events and vice-versa. It is envisioned that resources can be allocated for a fixed time, with the resource requestor renewing the resource before the expiration time.
  • DTV-HNF distributed resource manager 1500 works in tandem with OCAP resource manager 1502 to keep track of resource allocation status. Remote allocations allocate resources through distributed RM 1500, which in turn allocates resources with OCAP/DTV resource manager 1502. Examples of local and remote reservations are detailed with reference to Figure 16 and Figure 17, respectively.
  • a local reservation process begins with DTV/OCAP application 1600 requesting a resource from OCAP resource manager 1502.
  • OCAP resource manager 1502 signals the application1600 that the resource has been successfully reserved.
  • OCAP resource manager 1502 notifies distributed resource manager 1500 that the resource is busy.
  • distributed resource manager 1500 notifies devices on the home network 1602 that the resource is busy.
  • a remote reservation process begins with a device on the home network 1602 requesting a resource from distributed resource manager 1500.
  • distributed resource manager 1500 requests the resource from OCAP resource manager 1502.
  • OCAP resource manager 1600 signals distributed resource manager 1500 that the resource has been successfully reserved.
  • distributed resource manager signals the requesting device on the home network 1602 that the resource has been successfully reserved. Thereafter, DTV/OCAP application 1600 requests the same resource from OCAP resource manager 1502. In response, OCAP resource manager 1502 signals DTV/OCAP application 1600 that the resource is busy. Resource contention is handled by OCAP rules (e.g., monitor application).
  • the broadcast time and stream event service of the DTV receiver accomplishes distribution and synchronization of broadcast triggers with devices in the home network.
  • Triggers are mechanisms to synchronize DTV applications with program content. Analog triggers are carried in VBI, while digital triggers can be carried as DSMCC stream event or as a playlist in an alternate channel. Three kinds of triggers are absolute time triggers, relative time triggers, and do it now triggers. Triggers are meant for consumption at the DTV receiver.
  • the invention provides a mechanism to synchronize a real-time clock between the DTV receiver and other home appliances.
  • the invention can be or include a discoverable, self- describing service, which makes time (time of the day) information available to any requesting entity on the home network.
  • the service description can be provided using XML.
  • the service can be discoverable by using different service discovery protocols (e.g., SSDP).
  • Time information can be extracted from STT and provided as events/actions over a variety of home networking frameworks (e.g., OSGi, UPnP, DENI, and others).
  • Some embodiments can provide a mechanism to extend availability of DSMCC triggers on the home network with time synchronization.
  • the DTV receiver extracts time information from MPEG2 PSl. For example, it converts the time information into XML or other, appropriate formats. It also manages subscription and notification of time of day to network appliances for time synchronization. Home network devices can update themselves with broadcast time extracted from STT by invoking the following actions, wherein GetTime() returns STT time: GetTime(TimeFormatParameter) returns STT converted into other various formats (for instance, GMT).
  • GetTime() returns STT time: GetTime(TimeFormatParameter) returns STT converted into other various formats (for instance, GMT).
  • the service can also pose the "BroadcastTime/SystemTime" evented state variable. Accordingly, all entities that subscribe to this service receive time change events. This can be a moderated state variable in order to decrease the frequency of eventing, for example, if once per second eventing is too frequent.
  • a trigger relay service can be provided.
  • triggers can be extracted as stream events from a broadcast carousel. Triggers can also be converted to XML or other, appropriate formats. Time information can further be synchronized with a broadcast time service. Still further, subscription and notification to home appliances can be managed.
  • triggers can be cached for later access, and/or converted to UPnP or
  • DTV receiver 1900 includes a trigger service 1902 that operates according to a time service 1904 and receives events from broadcast carousel 1904.
  • Home appliance 1908 registers for or subscribes to time and trigger information.
  • receiver 1900 sends time information and trigger notifications to home appliance 1908.
  • Trigger notifications can include time information and be in XML format.
  • the content listing service (or EPG service) of the DTV receiver has some similarities to the UPnP CDS, but has extended capabilities. For example, it can import VOD/PPV sessions and exports events. It can also make metadata available from multiple tuners, such as cable and terrestrial tuners. It can further make bandwidth requirements available, along with copy protection rules. Finally, it can provide metadata translations.
  • the content listing service 2000 can interface with an OCAP SI manager 2002 and an OCAP recording manger 2004, which in turn interface with the OCAP application 2006.
  • content listing and launching can be a discoverable home network service.
  • it can be a consolidated Java TV service or content listing from sources such as: SI manager for broadcast services; recording manager for stored services via DVR; VOD/PPV sessions; contents stored in removable and/or fixed storage via SD card, hard disk, DVD/CD, and others; and Internet content. Metadata can be provided in association with each entry.
  • Metadata information can include various components. For example, it can include metadata in XML format that has been translated form SI data, VOD metadata, TV-AnyTime metadata, and others. Metadata can also contain one or more uniform locators for launching the service in question. Metadata can further specify format, such as SD, HD, audio/video, mp3, and others. Metadata can still further provide an estimate of bandwidth requirements. Metadata can even further specify that a service is XAIT or AIT. Yet still further, metadata can specify that the service in question is remote launchable. Finally, metadata can describe copy protection rules for a content service.
  • the content listing and launching service can monitor removable storage (SD, DVD, CD, etc.) media for content.
  • the service can generate notifications.
  • the content listing service architecture can include the content listing service 2100 employing uniform locators 2102 mapped to multiple content sources.
  • Sources can include broadcast content 2104 from SI manager, including tuners 2106, cable, ATSC, etc..
  • Sources can also include stored content 2108, and stored services 2110 from recording manager (DVR), each of which can be stored on hard disk 2112 or on removable storage, such as SD card 2114.
  • DVR recording manager
  • Sources can also include VOD/PPV sessions 2116, the Internet 2118, and multi-player games 2120.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Multimedia (AREA)
  • Automation & Control Theory (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Computer Security & Cryptography (AREA)
  • Databases & Information Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)
  • Small-Scale Networks (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

L’invention concerne une architecture de réseau comprenant un réseau domestique, un réseau de diffusion, un récepteur DTV connecté au réseau domestique et au réseau de diffusion, et un service lié à DTV mis en œuvre dans le réseau domestique et opérationnel pour exposer des fonctionnalités du récepteur DTV sur le réseau. Selon d’autres aspects, un service de syntoniseur expose des caractéristiques et des possibilités de syntoniseurs sur d’autres dispositifs dans un réseau, et contrôle le fonctionnement des syntoniseurs selon des commandes de contrôle reçues de points de contrôle. Selon encore d’autres aspects, un service de gestion de ressources est adapté pour gérer l’attribution de ressources sur le dispositif DTV et suivre un état d’attribution de ressources. Selon d’autres aspects en plus, un service d’évènements de temps et de flux maintient un temps commun pour le réseau et achemine des déclencheurs sur le réseau à partir d’un cache de déclencheurs reçu d’un carrousel de diffusion.
PCT/US2005/024521 2004-07-13 2005-07-13 Service de syntoniseur et recepteur dtv en tant que dispositif upnp WO2006017218A2 (fr)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US58757604P 2004-07-13 2004-07-13
US60/587,576 2004-07-13
US60757104P 2004-09-07 2004-09-07
US60/607,571 2004-09-07

Publications (2)

Publication Number Publication Date
WO2006017218A2 true WO2006017218A2 (fr) 2006-02-16
WO2006017218A3 WO2006017218A3 (fr) 2006-09-14

Family

ID=35839762

Family Applications (2)

Application Number Title Priority Date Filing Date
PCT/US2005/024810 WO2006017330A2 (fr) 2004-07-13 2005-07-13 Mobilite de session video a la demande dans un reseau domestique
PCT/US2005/024521 WO2006017218A2 (fr) 2004-07-13 2005-07-13 Service de syntoniseur et recepteur dtv en tant que dispositif upnp

Family Applications Before (1)

Application Number Title Priority Date Filing Date
PCT/US2005/024810 WO2006017330A2 (fr) 2004-07-13 2005-07-13 Mobilite de session video a la demande dans un reseau domestique

Country Status (1)

Country Link
WO (2) WO2006017330A2 (fr)

Cited By (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1841227A1 (fr) 2006-03-21 2007-10-03 Samsung Electronics Co., Ltd. Confirmation de la validité d'un certificat et affichage des informations du contenu
GB2438916A (en) * 2006-06-09 2007-12-12 Martin Hall Digital broadcast receiver and streamer
WO2007149414A2 (fr) * 2006-06-19 2007-12-27 The Directv Group, Inc. Bloc d'accord dédié pour fonctions d'administration de réseau
WO2008077456A1 (fr) * 2006-12-22 2008-07-03 Koninklijke Kpn N.V. Procédé et système pour sélectionner un signal de diffusion dans un environnement multi-utilisateur
EP2087649A1 (fr) * 2006-12-01 2009-08-12 Teliasonera AB Système et procédé pour un traitement de largeur de bande
CN102625170A (zh) * 2012-03-13 2012-08-01 深圳市九洲电器有限公司 一种可即插即用调谐解调器的机顶盒及方法
JP2013009357A (ja) * 2011-05-20 2013-01-10 Nippon Hoso Kyokai <Nhk> 放送通信連携受信装置
JP2013009356A (ja) * 2011-05-20 2013-01-10 Nippon Hoso Kyokai <Nhk> 放送通信連携受信装置
WO2013112276A1 (fr) * 2012-01-24 2013-08-01 General Instrument Corporation Système et procédé servant à communiquer des informations de ressources
EP2648137A3 (fr) * 2012-04-02 2014-12-17 Telefonaktiebolaget L M Ericsson AB (Publ) Procédé de distribution de raisonnement générique
WO2018009287A1 (fr) * 2016-07-02 2018-01-11 Qualcomm Incorporated Architecture de mise en œuvre distribuée pour récepteur de diffusion

Families Citing this family (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7954127B2 (en) 2002-09-25 2011-05-31 The Directv Group, Inc. Direct broadcast signal distribution methods
US7950038B2 (en) 2005-04-01 2011-05-24 The Directv Group, Inc. Transponder tuning and mapping
US7958531B2 (en) 2005-04-01 2011-06-07 The Directv Group, Inc. Automatic level control for incoming signals of different signal strengths
US8024759B2 (en) 2005-04-01 2011-09-20 The Directv Group, Inc. Backwards-compatible frequency translation module for satellite video delivery
US7987486B2 (en) 2005-04-01 2011-07-26 The Directv Group, Inc. System architecture for control and signal distribution on coaxial cable
US7945932B2 (en) 2005-04-01 2011-05-17 The Directv Group, Inc. Narrow bandwidth signal delivery system
US7900230B2 (en) 2005-04-01 2011-03-01 The Directv Group, Inc. Intelligent two-way switching network
US8789115B2 (en) 2005-09-02 2014-07-22 The Directv Group, Inc. Frequency translation module discovery and configuration
US7937732B2 (en) 2005-09-02 2011-05-03 The Directv Group, Inc. Network fraud prevention via registration and verification
US7991348B2 (en) 2005-10-12 2011-08-02 The Directv Group, Inc. Triple band combining approach to satellite signal distribution
US8019275B2 (en) 2005-10-12 2011-09-13 The Directv Group, Inc. Band upconverter approach to KA/KU signal distribution
US20080155062A1 (en) * 2006-11-02 2008-06-26 Andre Rabold System for providing media data
CN101316204B (zh) * 2007-05-28 2013-08-07 华为技术有限公司 会话移动方法和会话移动系统
CN101123718B (zh) * 2007-09-13 2011-12-21 华为技术有限公司 多媒体点播的方法及系统
US9438642B2 (en) 2012-05-01 2016-09-06 Google Technology Holdings LLC Methods for coordinating communications between a plurality of communication devices of a user
US9560108B2 (en) 2012-09-13 2017-01-31 Google Technology Holdings LLC Providing a mobile access point
EP2947825A4 (fr) * 2013-03-08 2016-02-17 Huawei Device Co Ltd Procédé de communication vidéo, terminal domestique et serveur domestique

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6249914B1 (en) * 1995-06-15 2001-06-19 Intel Corporation Simulating two way connectivity for one way data streams for multiple parties including the use of proxy
US20020174433A1 (en) * 2001-03-22 2002-11-21 Baumgartner Joseph P. Personal video recorder systems and methods
US20020194334A1 (en) * 2001-06-14 2002-12-19 Alcatel Processor system, access server system, method and computer program product
US20030217369A1 (en) * 2002-05-17 2003-11-20 Heredia Edwin Arturo Flexible application information formulation
US20040049794A1 (en) * 2000-12-28 2004-03-11 Jiang Shao Method for managing audiovisual broadcast recordings and associated devices
US20040088731A1 (en) * 2002-11-04 2004-05-06 Daniel Putterman Methods and apparatus for client aggregation of media in a networked media system
US20040098398A1 (en) * 2001-01-30 2004-05-20 Sang-Woo Ahn Method and apparatus for delivery of metadata synchronized to multimedia contents

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6154206A (en) * 1998-05-06 2000-11-28 Sony Corporation Of Japan Method and apparatus for distributed conditional access control on a serial communication network
CN1115824C (zh) * 1998-05-07 2003-07-23 三星电子株式会社 网络中的装置对装置命令与控制的方法和系统

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6249914B1 (en) * 1995-06-15 2001-06-19 Intel Corporation Simulating two way connectivity for one way data streams for multiple parties including the use of proxy
US20040049794A1 (en) * 2000-12-28 2004-03-11 Jiang Shao Method for managing audiovisual broadcast recordings and associated devices
US20040098398A1 (en) * 2001-01-30 2004-05-20 Sang-Woo Ahn Method and apparatus for delivery of metadata synchronized to multimedia contents
US20020174433A1 (en) * 2001-03-22 2002-11-21 Baumgartner Joseph P. Personal video recorder systems and methods
US20020194334A1 (en) * 2001-06-14 2002-12-19 Alcatel Processor system, access server system, method and computer program product
US20030217369A1 (en) * 2002-05-17 2003-11-20 Heredia Edwin Arturo Flexible application information formulation
US20040088731A1 (en) * 2002-11-04 2004-05-06 Daniel Putterman Methods and apparatus for client aggregation of media in a networked media system

Cited By (14)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP1841227A1 (fr) 2006-03-21 2007-10-03 Samsung Electronics Co., Ltd. Confirmation de la validité d'un certificat et affichage des informations du contenu
GB2438916A (en) * 2006-06-09 2007-12-12 Martin Hall Digital broadcast receiver and streamer
WO2007149414A2 (fr) * 2006-06-19 2007-12-27 The Directv Group, Inc. Bloc d'accord dédié pour fonctions d'administration de réseau
WO2007149414A3 (fr) * 2006-06-19 2009-03-12 Directv Group Inc Bloc d'accord dédié pour fonctions d'administration de réseau
EP2087649A4 (fr) * 2006-12-01 2009-11-25 Teliasonera Ab Système et procédé pour un traitement de largeur de bande
EP2087649A1 (fr) * 2006-12-01 2009-08-12 Teliasonera AB Système et procédé pour un traitement de largeur de bande
WO2008077456A1 (fr) * 2006-12-22 2008-07-03 Koninklijke Kpn N.V. Procédé et système pour sélectionner un signal de diffusion dans un environnement multi-utilisateur
JP2013009357A (ja) * 2011-05-20 2013-01-10 Nippon Hoso Kyokai <Nhk> 放送通信連携受信装置
JP2013009356A (ja) * 2011-05-20 2013-01-10 Nippon Hoso Kyokai <Nhk> 放送通信連携受信装置
WO2013112276A1 (fr) * 2012-01-24 2013-08-01 General Instrument Corporation Système et procédé servant à communiquer des informations de ressources
US8904462B2 (en) 2012-01-24 2014-12-02 Motorola Mobility Llc System and method for communication resource information
CN102625170A (zh) * 2012-03-13 2012-08-01 深圳市九洲电器有限公司 一种可即插即用调谐解调器的机顶盒及方法
EP2648137A3 (fr) * 2012-04-02 2014-12-17 Telefonaktiebolaget L M Ericsson AB (Publ) Procédé de distribution de raisonnement générique
WO2018009287A1 (fr) * 2016-07-02 2018-01-11 Qualcomm Incorporated Architecture de mise en œuvre distribuée pour récepteur de diffusion

Also Published As

Publication number Publication date
WO2006017330A2 (fr) 2006-02-16
WO2006017330A3 (fr) 2006-11-16
WO2006017218A3 (fr) 2006-09-14

Similar Documents

Publication Publication Date Title
WO2006017218A2 (fr) Service de syntoniseur et recepteur dtv en tant que dispositif upnp
WO2006015186A2 (fr) Systeme et procede pour l&#39;enregistrement et le partage reparti de programmes de television en direct
EP2039058B1 (fr) Communication pour noeud de multi-enregistreur vidéo numérique
CN102007732B (zh) UPnP/DNLA兼容的MR-DVR
CA2546598C (fr) Procedes et dispositifs permettant l&#39;enregistrement de materiel dans un dispositif reseau
EP2139237B1 (fr) Récepteur IPTV et procédé de contrôle de contenus affichés dans le récepteur IPTV
US8244829B2 (en) Data transmitting apparatus, data receiving apparatus, data transmitting method and data receiving method
US8893205B2 (en) IPTV receiver and method of providing channel map management information
US20080022331A1 (en) Multi-DVR Media Stream Transition
US20090300231A1 (en) Data output device, equipment control device, and multimedia delivery system
WO2007112155A2 (fr) Gestion de l&#39;extinction de contenu multimédia
US20090158327A1 (en) IPTV receiver and method of providing channel map information
US8869219B2 (en) Method for controlling a channel and an IPTV receiver
US20080022330A1 (en) Multi-DVR Content Management
US10116986B2 (en) Digital video recorder state cache
KR100728256B1 (ko) 홈네트워크와 방송 간에 멀티미디어 콘텐츠를 상호이용하기 위한 홈네트워크/방송 연동 시스템 및 그 방법
US20110296460A1 (en) Method and apparatus for providing remote user interface (ui) service
US20090158348A1 (en) IPTV receiver and method of discovering an IPTV service
KR101249784B1 (ko) 근거리 통신망 내에서 수신된 서비스를 관리하기 위한 장치 및 방법
KR100677614B1 (ko) 홈 네트워크에서 디지털 방송 부가 정보를 전송하는 방법및 장치
US20090077236A1 (en) Apparatus and method for managing services received in a local area network
WO2006047128A1 (fr) Systeme de fourniture de fichiers de diffusion sur reseau
US20090216854A1 (en) Controlled device, control system, and management device
US20140012955A1 (en) Communication System, Communication Device, And Communication Method
KR100873950B1 (ko) 디지털 방송에서의 어플리케이션 데이터 전송시스템 및 그방법

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A2

Designated state(s): AE AG AL AM AT AU AZ BA BB BG BR BW BY BZ CA CH CN CO CR CU CZ DE DK DM DZ EC EE EG ES FI GB GD GE GH GM HR HU ID IL IN IS JP KE KG KM KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA NG NI NO NZ OM PG PH PL PT RO RU SC SD SE SG SK SL SM SY TJ TM TN TR TT TZ UA UG US UZ VC VN YU ZA ZM ZW

AL Designated countries for regional patents

Kind code of ref document: A2

Designated state(s): BW GH GM KE LS MW MZ NA SD SL SZ TZ UG ZM ZW AM AZ BY KG KZ MD RU TJ TM AT BE BG CH CY CZ DE DK EE ES FI FR GB GR HU IE IS IT LT LU LV MC NL PL PT RO SE SI SK TR BF BJ CF CG CI CM GA GN GQ GW ML MR NE SN TD TG

121 Ep: the epo has been informed by wipo that ep was designated in this application
NENP Non-entry into the national phase

Ref country code: DE

WWW Wipo information: withdrawn in national office

Country of ref document: DE

122 Ep: pct application non-entry in european phase