WO2005094075A2 - Gestion de ressources centralise et support de dispositif support non gere - Google Patents

Gestion de ressources centralise et support de dispositif support non gere Download PDF

Info

Publication number
WO2005094075A2
WO2005094075A2 PCT/US2005/009237 US2005009237W WO2005094075A2 WO 2005094075 A2 WO2005094075 A2 WO 2005094075A2 US 2005009237 W US2005009237 W US 2005009237W WO 2005094075 A2 WO2005094075 A2 WO 2005094075A2
Authority
WO
WIPO (PCT)
Prior art keywords
crm
resource
aware
resources
centralized
Prior art date
Application number
PCT/US2005/009237
Other languages
English (en)
Other versions
WO2005094075A3 (fr
Inventor
Carlton J. Sparrell
Original Assignee
Ucentric Holdings Inc.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US10/490,224 external-priority patent/US20040268406A1/en
Priority claimed from US10/490,325 external-priority patent/US20040251887A1/en
Priority claimed from US10/490,225 external-priority patent/US20040268407A1/en
Priority claimed from US10/835,552 external-priority patent/US20060031888A1/en
Application filed by Ucentric Holdings Inc. filed Critical Ucentric Holdings Inc.
Publication of WO2005094075A2 publication Critical patent/WO2005094075A2/fr
Publication of WO2005094075A3 publication Critical patent/WO2005094075A3/fr

Links

Classifications

    • 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/282—Controlling appliance services of a home automation network by calling their functionalities based on user interaction within the home
    • 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
    • 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
    • G—PHYSICS
    • G11—INFORMATION STORAGE
    • G11B—INFORMATION STORAGE BASED ON RELATIVE MOVEMENT BETWEEN RECORD CARRIER AND TRANSDUCER
    • G11B2220/00—Record carriers by type
    • G11B2220/40—Combinations of multiple record carriers
    • G11B2220/41—Flat as opposed to hierarchical combination, e.g. library of tapes or discs, CD changer, or groups of record carriers that together store one title
    • 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/2801—Broadband local area networks
    • 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

Definitions

  • the present invention broadly relates to digital recording and playback systems and methods administered by home area networks. More particularly, the present invention relates to improving the flexibility of home area networks by facilitating the interoperability of resources that are not compatible with a centralized resource manager in a home area network incorporating a centralized resource manager.
  • HAVi Home Audio Video Interactive
  • UPF Universal Plug and Play
  • Jini Jim Network Technology
  • PVR personal video recording
  • ReplayTV do not support distributed networks or distributed resources management.
  • the device wishing to establish a complete media pipeline/session is responsible for establishing the reservations with each of the components. This is inefficient, and can possibly result in deadlock timing situations from competing reservation requests.
  • only devices on the network providing local resource managers may be reserved.
  • the distributed nature results in added complexity for each device that must support a local resource manager.
  • a superior approach comprises a home area network (HAN) that incorporates a centralized resource manager (CRM) so that it is not necessary to rely on a plurality of local resource managers in the HAN.
  • CRM centralized resource manager
  • the CRM assigns network resources in the most efficient manner, and provides proxy reservations where necessary for devices on the distributed network that do not include a local resource manager.
  • One limitation of this approach is that it requires each network to provide at least one CRM-capable device.
  • a typical UPnP-enabled network includes “control points" and “devices".
  • a control point is an entity capable of controlling another UPnP-enabled device, such as a light switch, or a remote control.
  • the device capable of being controlled could include devices such as a television.
  • devices and control points discover each other using a discovery protocol (typically, Simple Service Discovery Protocol, or SSDP).
  • Any control point is capable of controlling any other UPnP-enabled device - the user can configure the light switch to control any light on the network.
  • a control point can control many devices, and a device may be controllable by many control points.
  • UPnP A/V Architecture An extension to UPnP is the UPnP A/V Architecture. This architecture is similar to basic UPnP in that it also includes control points and devices. The difference is that UPnP A V devices can be thought of as being either Servers or Renderers.
  • a Server is a device capable of sending content to a Renderer, and a Renderer is capable of displaying that content.
  • the link mechanism between the Server and Renderer is not defined by
  • the control point is responsible for discovering the devices and configuring them according to the users wishes. For example, the control point might generate a user interface (UI) allowing the user to select content to play. The control point would populate this UI with titles discovered by querying the Server. When the user selects a program to play, the control point will set up the Server to send the content to the Renderer, and set up the Renderer to receive the content from the server.
  • UI user interface
  • the UPnP architecture operates in a resource environment that is unmanaged in important respects.
  • Devices on the network offer up their services to any control point. No method of reserving resources is provided, and how a device already being controlled by a control point behaves when a second control point in the network attempts to access that device is undefined, and left to the discretion of individual manufacturers to implement as they see fit. Additionally, if a control point wants to send content from a Server to a Renderer, the control point explicitly needs to establish contact with, and configure the Server, and establish contact with and configure the Renderer. Moreover, there is no provision for reserving a plurality of resources or components for accomplishing a specific task.
  • the CRM may detect a request made by a non-CRM aware resource to a CRM-aware resource in a home area network for a service from the latter resource. The CRM may then determine whether a conflict arises from granting the request. If the CRM determines that a conflict arises, then the CRM may transmit a termination message to the CRM-aware resource directing the latter to terminate providing the service.
  • the CRM-aware resource may then receive a request from the CRM for provision of a service to another CRM-aware resource.
  • the CRM-aware resource may then terminate provision of the former service to the non-CRM aware resource and may initiate provision of a new service to the other CRM-aware resource.
  • a CRM may implement a first control protocol for providing centralized control of one or more CRM-aware resources, and may implement a second control protocol for communicating with, requesting and providing services to one or more non-CRM aware resources.
  • FIG. 2 shows another example of a network using the CRM of the present invention.
  • FIG. 3 illustrates a basic audio-video pipeline configuration suitable for use with the present invention.
  • FIG. 4 illustrates another audio-video pipeline configuration.
  • FIG. 5 illustrates yet another audio-video pipeline configuration, utilizing LAN resources.
  • FIG. 6 illustrates still another audio-video pipeline configuration, utilizing the resources of two clients.
  • FIG. 7 shows a basic block diagram of a media server and a typical client as taught in the present invention.
  • FIG. 8 is a block diagram of another embodiment of a CRM according to the present invention.
  • FIG. 9 illustrates another aspect of the present invention which includes a current sensing system to detect the ON or OFF status of a television set.
  • FIG. 10 illustrates an example of circuitry used to implement the current sensing system of FIG. 9.
  • FIG. 11 shows an example using an IR sensing system to detect the ON or OFF status of a television set to automatically control resource allocation.
  • FIG .12 shows further detail of the embodiment of FIG. 11.
  • FIG. 13 is a flowchart of one method for prioritizing resource allocation using IR signals from the IR sensing system.
  • FIG. 14 is a flowchart of an alternative method for prioritizing resource allocation using IR signals from the IR sensing system.
  • FIG. 15 illustrates another aspect of the present invention in which an electromagnetic field sensing system is used to detect the ON or OFF status of a television set.
  • the IR monitoring channel 402 could detect the IR "On" signal at the same time the TV 104 does. But the IR signal to the IR monitoring channel 402 could be blocked when the TV 104 is turned off. The IR detection circuit within the channel 402 would then be out of sync. This is why other key presses in combination with the On/Off signal are useful. This method is shown in FIG. 14.
  • a means for learning the On and Off codes (or common On/Off code) of the remote control unit (secondary) used for the television It may be preferable that such a means be operative to learn the complete code set for the television.
  • One method is to allow the user to enter the model number or an ID cross-referencing the model number of the TV into such means.
  • Another method is to put the means in learn mode and to press the key to be learned. In the method depicted in FIG.
  • This EMF sensing system 469 may be either tethered, as shown in FIG. 16, or physically attached to the client device 112 (or media server 108).
  • this aspect of a CRM-enabled network is a power switch 307 that can be used in an STB 300 or similar client device to control the turning on and turning off of the television which powered through the STB 300.
  • the STB 300 is connected to the AC power (in the United States, typically 110 volts AC) by means of a standard power cord plug 302.
  • the STB 300 includes a power supply 304. A connection is made from this power source 304 to an outlet 306 on the STB 300 to which the television power cord is connected. Thus, the television will draw its current through this connection in the STB 300.
  • One of the power conductors going to the outlet is passed through a power switch 307, allowing the circuit shown in FIG. 18 to control the voltage and thus control whether the television is in the ON or OFF state.
  • the CRM receives a user request to render data on the HAN.
  • the user may request that a program from an electronic program guide be rendered on a selected display device of the HAN at a predetermined time or for a specified future time period.
  • the user may request that a program or other media data be streamed to a particular display device in real-time.
  • the user may transmit such a user request by using a remote control, or by otherwise programming a resource on the HAN.
  • the CRM receives the user request by virtue of the fact that it is connected directly, or indirectly through one or more other resources, to the resources of the HAN.
  • the destination resource associated with a user request may not be limited to a display device.
  • the user may request that a program being broadcast by a service provider be recorded to memory resource 2210.
  • a user request may not directly specify the recording or playback of a specific program at a specific time.
  • the user may request that all James Bond movie-content be recorded.
  • Media server 2270 may determine based on information from a newly updated electronic program guide that "Thunderball" will be played on a specific cable channel at 9 pm. Based on this, media server 2270 may request that CRM 2280 construct and implement a media pipeline resulting in the recording of "Thunderball" from that cable channel at that time.
  • the user request may involve the streaming of a 4 Mbps program from one of two HAN tuners to a particular display device.
  • the user request may include the ability to use live-pause DVR functionality in viewing the program.
  • a HAN resource with buffering functionality e.g., a drive — may be required to fulfill the user request.
  • the CRM in the present embodiment may use the tuner that is local to the drive, because data flowing from the tuner would then travel a shorter distance than would be the case if the other tuner were used.
  • network bandwidth consumption would be reduced, because media data from the tune local to the display would need to traverse the network twice (once from the display to the disk, and once from the disk to the display, while a media data stream from a tuner local to the drive would only traverse the network once (from the drive to the display). In this manner, network bandwidth consumption would be reduced.
  • the set of available resources for fulfilling the user's request may be determined from the resources available at that time or time interval, as indicated by pre-existing entries in a reservations database that can be accessed by the CRM.
  • the CRM may then consider these resources to be unavailable for other uses until it detects or otherwise decides that such real-time us of the resources has terminated.
  • the CRM may construct the media pipeline for fulfilling the user request as discussed above (e.g., based on bandwidth considerations as discussed earlier).
  • the CRM at step 1930 initiates the rendering of media data in accordance with the constructed media pipeline and the associated time-usage indication.
  • a user request for a live session may result in the CRM implementing a live session media pipeline that utilizes one or more HAN resources that are also represented in media pipelines of the reservations database that are scheduled for implementation in the future.
  • the CRM may provide the user with a warning and the option of terminating the pre-existing media pipeline.
  • the CRM may assume that the user is no longer watching the live session and may terminate it, freeing up the resources for implementation of the conflicting pre-existing media pipeline.
  • the CRM treats live sessions as having lower priority compared to pre-existing media pipelines represented in the reservations database.
  • FIG. 20 illustrates another embodiment exemplifying CRM functionality.
  • the CRM detects the removal of a resource from the HAN and subsequently checks whether any media pipelines represented in a reservations database include representations of the removed resource. If one or more media pipelines include a representation of the removed resource, then in embodiments those media pipelines are reconstructed with resources that remain available in the HAN.
  • the embodiment depicted in FIG. 20 begins with step 2000 in which the CRM detects the removal of a first resource from the HAN.
  • the first resource is physically removed from the HAN — e.g., the device including or implementing the resource is physically removed or its power connection is disconnected.
  • a user may override pre-existing entries in the reservations database by, for example, requesting a real-time streaming event requiring a number of resources that are unavailable at the relevant time a reflected in the pre-existing entries in the reservations database.
  • Such a resource found by the CRM may be used to replace the resource removed from the HAN. If more than one such resource is identified, then the CRM may determine the replacement resource that is to be actually used by an algorithm as discussed earlier. In one embodiment, if no replacement resource is identified, then a message may be displayed to the user indicating the occurrence of an error, and the relevant media pipeline may be abandoned and deleted from the reservations database.
  • the CRM may not perform at least one of steps 2010, 2020 and 2030 until after some time elapses following step 2000. This may be done in these embodiments to avoid the needless reallocation of resources where the first resource is only temporarily removed from the HAN — e.g., where the first resource needs to be shut down and rebooted.
  • the CRM may not carry out steps 2010, 2020 and or 2030 until after a pre-determined amount of time elapses after the CRM detects the removal of the first resource.
  • the CRM may not carry out steps 2020 and or 2030 until a time shortly before a pre-existing media pipeline containing a representation of the removed first resource is scheduled to be implemented.
  • the CRM may not carry out steps 2010, 2020 and/or 2030 until after an explicit message is received from the first resource that it is leaving the HAN.
  • the CRM determines whether it would be desirable to amend or reconfigure any media pipeline identified in step 2110 so that the pre-existing resource is replaced with the new resource for that media pipeline.
  • the CRM may detennine whether such amendment or reconfiguration is desirable by, for example, using an algorithm as described earlier to compare a media pipeline that includes a representation of a pre-existing resource with one including a representation of the new resource.
  • Such an algorithm may be based on one or more pre-determined selection criteria that are programmed into the hardware and/or software logic implementing the CRM. If the CRM determines in step 2130 that replacement would be desirable, then the
  • the user adds a second tuner local to the storage disk (e.g., the user may connect the second tuner using a USB interface to a server or local resource manager that is local to the storage disk).
  • the CRM may determine that it should replace the representation of the pre-existing tuner with a representation of the second tuner in the media pipeline, because this will result in a lower cost network due to the shorter distance media data will need to travel through use of the second tuner instead of the pre-existing tuner.
  • a CRM may have the capability to detect the addition to the HAN of another resource that is also capable of CRM functionality. Either or both CRMs may also have the ability to negotiate and agree with one another regarding which CRM is to provide centralized control over HAN resources, and which CRM is to operate in a manner that does not conflict with the other CRM's centralized control. In embodiments, such detection and/or negotiation may take place in accordance with a pre-defined protocol implementing logic programmed into the software unit and/or the hardware device implementing CRM functionality. Each CRM may be capable of implementing any or any combination of the CRM features discussed above.
  • embodiments of the present invention include a CRM that has the capability to implement any or any combination of the CRM features discussed above, and that is further capable of detecting and negotiating with, when present, another CRM in the HAN that also has the capability to implement any or any combination of the discussed CRM features.
  • Such communications using the first control protocol may include, for example, control commands and/or query commands that allow the CRM to cause a resource from the first set (i.e., a "CRM-aware resource") to carry out the functionality corresponding to its representation in a media pipeline constructed by the CRM.
  • a first control protocol command issued by the CRM may indirectly cause a CRM-aware tuner that is represented in a media pipeline to tune into a program associated with the media pipeline and provide output to the next resource indicated in that media pipeline.
  • the CRM may provide a representation of the relevant media pipeline to an application or application service that contains a pointer to the assigned resource. The application or application service may then cause the resource to perform its functionality through use of the pointer.
  • first control protocol commands issued by the CRM may cause the other resources represented in the media pipeline to carry out the functionality indicated by that media pipeline.
  • One or more of the resources illustrated in FIG. 22 may be connected to a set-top box providing known local resource management functionality.
  • Such set-top box functionality associated with a resource of the HAN may alternatively be implemented within the resource itself, as will be apparent to one skilled in the art based on this disclosure.
  • display devices 2200, 2240 and 2260 may each have a local decoder resource (not shown) that is utilized, for example, for decoding MPEG2 (or other MPEG) encoded data.
  • a decoder may be a part of a display device, or in an alternative embodiment, may be implemented in a set-top box local to a display device.
  • media server 2270 may have a local memory or other storage resource (not shown).
  • tuners that are utilized in embodiments of the invention include analog timers as well as digital tuners.
  • An analog tuner in embodiments of the invention may additionally include an MPEG2 (or other MPEG) encoder (not shown).
  • CRM 2280 may be located in a physical unit that is distinct from the physical unit in which media server 2270 is located. Additionally, the CRM-aware resources in the HAN may not be directly connected to media server 2270 and/or CRM 2280, but may instead be connected to either or both of these indirectly through one or more other resources (e.g., in accordance with known network topologies such as a bus, ring or tree topology). All of these and other variations apparent to those skilled in the art are within the scope of the present invention in light of this disclosure.
  • a CRM-aware resource that implements both the CRM-compatible first control protocol and a second control protocol not compatible with the first control protocol (e.g., any of encoder 2220, decoder 2230, memory 2210 and tuner 2290 in the example of FIG. 23), and receives a request for the provision of services from a non- CRM aware resource (e.g., display device 2260 in the example of FIG. 23).
  • a non- CRM aware resource e.g., display device 2260 in the example of FIG. 23.
  • Such a request message could, for example, in turn be prompted by user input through a remote control unit requesting the streaming of a program or other real-time media data to display device 2260.
  • the request message is formatted according to the rules of the second control protocol.
  • the dually enabled resource receives the request message, and in response to this, in step 2420 transmits a permission request message, or a notification message implicitly requesting such permission, to the CRM for permission to provide the requested service to the non-CRM aware resource.
  • the permission request message (or the notification message) may be formatted according to the rules of the first control protocol.
  • the CRM receives the permission request message (or the notification message) from the dually enabled resource.
  • the CRM in step 2440 determines whether to grant permission to the dually enabled resource to provide the requested service to the non-CRM aware resource.
  • the CRM's decision as to whether to grant permission may be based on the request and pre-existing entries in the reservations database of the CRM. For example, the CRM may search the reservations database for pre-existing entries that would conflict with the provision of the requested service by the dually enabled resource to the non-CRM aware resource. If a conflict is determined to exist, than the CRM may not provide permission for the dually enabled resource to provide the service to the non-CRM aware resource. If no conflict is identified, then the CRM may determine to provide permission to the dually enabled resource.
  • the CRM may optionally enter an indication in the reservations database indicating that the dually enabled resource is or will be busy at a time or during a time interval indicated by the timing requirement information. Alternatively, the CRM may not make such an entry and treat subsequent requests from CRM-aware resources in the HAN for services from the dually enabled resource as having a greater priority than the request made by the non-CRM aware resource.
  • the CRM after receiving a request from a CRM-aware resource for the provision of a service by the dually enabled resource that conflicts with the service being provided to or scheduled to be provided to the non-CRM aware device, transmits a revocation message to the dually enabled device revoking the prior permission.
  • the dually enabled resource may subsequently terminate the provision of the service to the non-CRM enabled resource, or if such service was scheduled for a future time, may not initiate the provision of that service at the future time.
  • the dually enabled resource provides the service requested by the non-CRM aware resource without waiting for any permission from the CRM, and transmits a notification message to the CRM regarding its provision of the service to the non-CRM aware resource. If the CRM subsequently determines that a conflict exists between pre-existing entries in the reservations database and the provision of the service to the non-CRM aware resource, then the CRM transmits a termination message to the dually enabled resource directing the dually enabled resource to terminate the provision of the service to the non-CRM aware resource. The dually enabled resource receives this termination message and subsequently terminates the provision of the service to the non-CRM aware resource.
  • the dually enabled resource receives the request message, and in response to this, in step 2520, transmits a notification message to the CRM notifying the CRM that it has initiated the provision of the service or that it will provide the service in the future.
  • the dually enabled resource may include timing requirement information in the notification message relating to the time at which the non-CRM aware device requests that the service be provided, similar to the description of how timing requirement information may be included in the permission message of the first embodiment discussed above.
  • the dually enabled resource in step 2540 initiates the provision of the requested service to the non-CRM aware resource.
  • step 2540 may be carried out before, after or at the same time as step 2520.
  • the CRM in step 2530 receives the notification message transmitted by the dually enabled resource at step 2520.
  • the CRM may make an entry in the reservations database indicating that the dually enabled resource will be busy at a time indicated by any timing requirement information that is received with the notification message.
  • the CRM may determine at step 2550 that a conflict exists or arose in the reservations database among entries relating to the dually enabled resource.
  • the CRM may determine such a conflict exists, for example, based on the timing requirement information relating to the request of the non-CRM aware resource and the time-usage indication associated with a media pipeline that is represented in the reservations database and that includes a representation of the dually enabled resource. It will be apparent to those skilled in the art, based on the disclosure in connection with the embodiment discussed above with reference to FIG. 24 how a CRM may be configured to implement such conflict determination.
  • the CRM in one aspect of the second embodiment, will not intervene and will allow the dually enabled resource to provide the service to the non-CRM aware resource. If, on the other hand, in the embodiment depicted in FIG. 25, the CRM at step 2550 determines the presence of a conflict, then the CRM at step 2560 transmits a termination message to the dually enabled resource directing the latter to terminate the provision of the service to the non-CRM aware resource. Alternatively, where the request of the non-CRM aware resource relates to a future service to be provided by the dually enabled resource, the termination message may direct the dually enabled resource to not initiate the provision of the service to the non-CRM aware resource.
  • the dually enabled resource terminates provision of the service to the non-CRM aware resource.
  • the request of the non-CRM aware resource relates to a future service to be provided by the dually enabled resource
  • the dually enabled resource does not initiate the provision of the service to the non-CRM aware resource.
  • the dually enabled resource provides the service requested by the non-CRM aware resource without waiting for any permission from the CRM and without providing any notification to the CRM. However, if the dually enabled resource subsequently receives a request from the CRM to provide a service to a CRM- aware resource that conflicts with the provision of the service to the non-CRM aware device, then the dually enabled resource terminates provision of the service to the non- CRM aware resource and initiates provision of a service to the CRM-aware resource.
  • FIG. 26 illustrates this embodiment summarized directly above.
  • a non-CRM enabled resource in the HAN sends a message to a dually enabled resource requesting that that the latter provide a service.
  • the dually enabled resource receives the message of the CRM of step 2640.
  • the dually enabled resource in step 2660 terminates provision of the service to the non-CRM aware resource.
  • the dually enabled resource in step 2670 subsequently initiates the provision of the different service to the CRM-aware resource.
  • the CRM by using the second control protocol ⁇ e.g., UPnP ⁇ may act as a UPnP control point for treating and controlling non-CRM aware resources on the HAN as UPnP servers and UPnP renderers, as will be apparent to those skilled in the art.
  • FIG. 27 shows an example of an apparatus used in some embodiments of the present invention.
  • a medium 2740 containing Instructions 2745 may be operatively coupled to a computer 2700.
  • instructions 2745 may contain the steps in an embodiment of a method of the present invention.
  • instructions 2745 in a specific implementation may comprise the instructions corresponding to the steps carried out by the CRM in any of FIGS. 19-21 and 24-26, or the steps carried out by the dually enabled resource in any of FIGS. 24-26.
  • computer 2700 contains a processor 2710 which is coupled to an input/output unit 2730 and a memory 2720.
  • Memory 2720 may also have instructions 2725, which correspond to the steps in an embodiment of a method of the present invention.
  • instructions 2745 of medium 2740 may be copied into memory 2720. Variations to the embodiments discussed above will be apparent to those skilled in the art based on the present disclosure. Such variations are within the scope of embodiments of the invention.
  • actions discussed above as being taken by a resource of the HAN may be taken by a local resource manager of the relevant resource.
  • the control protocol that is used by CRM-aware resources may be a superset of the control protocol that is used by non-CRM aware resources.
  • the former protocol may use UPnP A/V commands and statements to control UPnP A/V source and rendering services, but extensions to effect the protocol used by CRM.
  • the structures shown and discussed in apparatus embodiments of the invention are exemplary only and the functions performed by these structures may be performed by any number of structures, as is known to those of skill in the art in view of this specification. All of such possible variations are within the scope and spirit of embodiments of the invention and the appended claims.
  • Propagating signals embodied in a medium such as a carrier wave or other carrier medium, that are products of embodiments of methods of the invention, or products of the use of embodiments of systems or devices of the present invention, are within the scope and spirit of the present invention and the appended claims.
  • a medium such as a carrier wave or other carrier medium
  • any medium containing instructions that are readable by a processor and that, when executed by the processor, perform the steps of method embodiments of the present invention are also within the scope and spirit of the present invention and the appended claims.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Automation & Control Theory (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Human Computer Interaction (AREA)
  • Multimedia (AREA)
  • Computer And Data Communications (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)

Abstract

Les modes de réalisation de la présente invention concernent un gestionnaire de ressources centralisé et des ressources qui répondent au gestionnaire de ressources centralisé dans un réseau local pouvant également comprendre des ressources qui ne répondent pas au gestionnaire de ressources centralisé. Dans certains modes de réalisation, le gestionnaire de ressources centralisé peut commander et réguler les demandes adressées par les ressources qui ne répondent pas au gestionnaire de ressources centralisé afin d'accéder aux ressources qui répondent au gestionnaire de ressources centralisé et d'utiliser ces dernières. Dans d'autres modes de réalisation, les ressources qui répondent au gestionnaire peuvent communiquer avec le gestionnaire de ressources centralisé dans des cas où les ressources qui ne répondent pas au gestionnaire accèdent aux ressources qui répondent au gestionnaire ou interrogent ces dernières afin d'y accéder. Dans d'autres modes de réalisation, le gestionnaire de ressources centralisé peut mettre en oeuvre différents protocoles de commande afin de commander ces deux types de ressources.
PCT/US2005/009237 2004-03-19 2005-03-21 Gestion de ressources centralise et support de dispositif support non gere WO2005094075A2 (fr)

Applications Claiming Priority (8)

Application Number Priority Date Filing Date Title
US10/490,224 US20040268406A1 (en) 2001-09-20 2002-08-23 Centralized resource manager with passive sensing system
US10/490,325 US20040251887A1 (en) 2001-09-20 2002-08-23 Centralized resource manager with power switching system
US10/490,225 US20040268407A1 (en) 2001-09-20 2002-09-06 Centralized resource manager
US10/490,225 2004-03-19
US10/490,325 2004-03-19
US10/490,224 2004-03-19
US10/835,552 2004-04-30
US10/835,552 US20060031888A1 (en) 2004-04-30 2004-04-30 Centralized resource management and un-managed device support

Publications (2)

Publication Number Publication Date
WO2005094075A2 true WO2005094075A2 (fr) 2005-10-06
WO2005094075A3 WO2005094075A3 (fr) 2006-05-26

Family

ID=34963439

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2005/009237 WO2005094075A2 (fr) 2004-03-19 2005-03-21 Gestion de ressources centralise et support de dispositif support non gere

Country Status (1)

Country Link
WO (1) WO2005094075A2 (fr)

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2007143218A2 (fr) * 2006-06-09 2007-12-13 The Directv Group, Inc. Modes de présentation pour trains binaires de formats divers
US7954127B2 (en) 2002-09-25 2011-05-31 The Directv Group, Inc. Direct broadcast signal distribution methods
US7958531B2 (en) 2005-04-01 2011-06-07 The Directv Group, Inc. Automatic level control for incoming signals of different signal strengths
CN111736953A (zh) * 2020-06-23 2020-10-02 深圳市云智融科技有限公司 虚拟资源投放方法、装置、计算机设备及存储介质

Families Citing this family (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7945932B2 (en) 2005-04-01 2011-05-17 The Directv Group, Inc. Narrow bandwidth signal delivery system
US7987486B2 (en) 2005-04-01 2011-07-26 The Directv Group, Inc. System architecture for control and signal distribution on coaxial cable
US7900230B2 (en) 2005-04-01 2011-03-01 The Directv Group, Inc. Intelligent two-way switching network
US8024759B2 (en) 2005-04-01 2011-09-20 The Directv Group, Inc. Backwards-compatible frequency translation module for satellite video delivery
US7950038B2 (en) 2005-04-01 2011-05-24 The Directv Group, Inc. Transponder tuning and mapping
US7937732B2 (en) 2005-09-02 2011-05-03 The Directv Group, Inc. Network fraud prevention via registration and verification
US8789115B2 (en) 2005-09-02 2014-07-22 The Directv Group, Inc. Frequency translation module discovery and configuration
US8019275B2 (en) 2005-10-12 2011-09-13 The Directv Group, Inc. Band upconverter approach to KA/KU signal distribution
US7991348B2 (en) 2005-10-12 2011-08-02 The Directv Group, Inc. Triple band combining approach to satellite signal distribution

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2001050290A1 (fr) * 1999-12-30 2001-07-12 Sony Electronics, Inc. Gestionnaire de ressources realisant un controle d'acces lie aux utilisateurs
EP1124357A1 (fr) * 2000-02-08 2001-08-16 Canon Kabushiki Kaisha Procédé et dispositif de communication entre un premier et un second réseau
US20030005130A1 (en) * 2001-06-29 2003-01-02 Cheng Doreen Yining Audio-video management in UPnP
WO2003025726A1 (fr) * 2001-09-20 2003-03-27 Ucentric Holdings, Inc. Gestionnaire de ressources centralisees a systeme de detection passif

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2001050290A1 (fr) * 1999-12-30 2001-07-12 Sony Electronics, Inc. Gestionnaire de ressources realisant un controle d'acces lie aux utilisateurs
EP1124357A1 (fr) * 2000-02-08 2001-08-16 Canon Kabushiki Kaisha Procédé et dispositif de communication entre un premier et un second réseau
US20030005130A1 (en) * 2001-06-29 2003-01-02 Cheng Doreen Yining Audio-video management in UPnP
WO2003025726A1 (fr) * 2001-09-20 2003-03-27 Ucentric Holdings, Inc. Gestionnaire de ressources centralisees a systeme de detection passif

Cited By (6)

* 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
US7958531B2 (en) 2005-04-01 2011-06-07 The Directv Group, Inc. Automatic level control for incoming signals of different signal strengths
WO2007143218A2 (fr) * 2006-06-09 2007-12-13 The Directv Group, Inc. Modes de présentation pour trains binaires de formats divers
WO2007143218A3 (fr) * 2006-06-09 2009-02-19 Directv Group Inc Modes de présentation pour trains binaires de formats divers
KR101316166B1 (ko) * 2006-06-09 2013-10-08 더 디렉티브 그룹, 인크. 다양한 포맷 비트 스트림들을 위한 프리젠테이션 모드들
CN111736953A (zh) * 2020-06-23 2020-10-02 深圳市云智融科技有限公司 虚拟资源投放方法、装置、计算机设备及存储介质

Also Published As

Publication number Publication date
WO2005094075A3 (fr) 2006-05-26

Similar Documents

Publication Publication Date Title
US20060031888A1 (en) Centralized resource management and un-managed device support
US20040268407A1 (en) Centralized resource manager
US20070226344A1 (en) Centralized Resource Manager With Power Switching System
US20060031887A1 (en) Centralized resource manager
WO2005094075A2 (fr) Gestion de ressources centralise et support de dispositif support non gere
US20040268406A1 (en) Centralized resource manager with passive sensing system
EP2039058B1 (fr) Communication pour noeud de multi-enregistreur vidéo numérique
US6363434B1 (en) Method of managing resources within a network of consumer electronic devices
EP1673940B1 (fr) Systeme d'enregistrement et de lecture video numerique avec lecture en qualite de service depuis plusieurs emplacements par l'intermediaire d'un reseau domestique
US7412538B1 (en) Request event manager and event lists for home and office systems and networks
KR100611985B1 (ko) 실시간 컨텐츠 관리 방법, 소오스 장치 및 싱크 장치
US20040221304A1 (en) Digital video recording and playback system with seamless advertisement insertion and playback from multiple locations via a home area network
US20040226034A1 (en) Digital video recording and playback system with seamless advertisement insertion and playback from multiple locations via a home area network
WO2000059230A9 (fr) Procede et dispositif de gestion de ressources dans un reseau
US20040251887A1 (en) Centralized resource manager with power switching system
JP2007336553A (ja) ホーム・ネットワーク内で赤外線パススルー・プロトコルを具現化するためのメディアサーバ、システム、方法、プログラム、および記録媒体
WO2005029770A1 (fr) Systeme de reproduction de contenus de medias a base upnp et procede associe
AU2005320439A1 (en) Device, system, and method for providing error information in XHT network
US9237323B2 (en) Media rendering device providing uninterrupted playback of content
EP2686985A1 (fr) Gestion de ressources basée sur un nuage
US20050271040A1 (en) Centralized resource manager and resource conflicts in a home area network
US8739230B2 (en) Manager/remote content architecture
WO2007086652A1 (fr) Procédé et appareil permettant de réserver une fonction d'un dispositif upnp
JP2001094583A (ja) デジタルインタフェースに連結されたネットワークシステムでのシステム資源管理方法
KR19990084417A (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 KP KR KZ LC LK LR LS LT LU LV MA MD MG MK MN MW MX MZ NA 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 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 in:

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