(12) INTERNATIONAL APPLICATION PUBLISHED UNDER THE PATENT COOPERATION TREATY (PCT)
`
`(19) World Intellectual Property Organization
`International Bureau
`
`(43) International Publication Date
`27 March 2003 (27.03.2003)
`
`
`
`PCT
`
`(10) International Publication Number
`WO 03/025726 A1
`
`(51) International Patent Classification7:
`1/28, 1/30, 1/32, 11/30, H04N 7/173
`
`G06F 1/26,
`
`(21) International Application Number:
`
`PCT/USO2/27014
`
`(22) International Filing Date: 23 August 2002 (23.08.2002)
`
`(US). VASILEVSKY, Alexander [US/US]; 5 Gooseneck
`Lane, Westford, MA 01886 (US). WATLINGTON,
`John [US/US]; 4 Pinewood Rd., Acton, Ma 01720 (US).
`LIVELY, David, F. [US/US]; 6 Cranberry Lane, Hudson,
`MA 01749 (US). KOKOVIDIS, Georgios [US/US]; 2
`Bemis Ave., Waltham, Ma 02453 (US).
`
`(25) Filing Language:
`
`(26) Publication Language:
`
`(30) Priority Data:
`60/323,618
`60/350,431
`60/372,490
`
`20 September 2001 (20.09.2001)
`19 January 2002 (19.01.2002)
`12 April 2002 (12.04.2002)
`
`US
`US
`US
`
`(71) Applicant (for all designated States except US): UCEN-
`TRIC HOLDINGS, INC. [US/US]; 2 Clock Tower Place,
`Suite # 350, Maynard, MA 01754 (US).
`
`(72) Inventors; and
`(7S) Inventors/Applicants U’or US only): SPARRELL, Carl-
`ton, J. [US/US]; 3A Wadden Ct., Marblehead, MA 01945
`
`English
`
`(74)
`
`Agent: RADKE, Terrance, J.; Lucash Gesmer & Upde—
`grove LLP, 40 Broad Street, Boston, MA 02109 (US).
`
`English
`
`(81)
`
`Designated States (national): AE, AG, AL, AM, AT, AU,
`AZ, BA, BB, BG, BR, BY, BZ, CA, CH, CN, CO, CR, CU,
`CZ, DE, DK, DM, DZ, EC, EE, 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, NO, NZ, OM, PH, PL, PT, RO, RU, SD, SE, SG,
`SI, SK, SL, TJ, TM, TN, TR, TT, TZ, UA, UG, US, UZ,
`VC, VN, YU, ZA, ZM, ZW.
`
`(84)
`
`Designated States (regional): ARIPO patent (GH, GM,
`KE, LS, MW, MZ, SD, SL, SZ, TZ, UG, ZM, ZW),
`Eurasian patent (AM, AZ, BY, KG, KZ, MD, RU, TJ, TM),
`European patent (AT, BE, BG, CH, CY, CZ, DE, DK, EE,
`ES, FI, FR, GB, GR, IE, IT, LU, MC, NL, PT, SE, SK,
`
`[Continued on next page]
`
`(54) Title: CENTRALIZED RESOURCE MANAGER WITH PASSIVE SENSING SYSTEM
`
`SERVER
`
`RESOURE
`MANAGER
`
`
`
`
`
`
`
`
`9i,.,.__f.,1.
`
`IRREMOTE
`CONTROL DEVICE
`
`03/025726A1
`
`(57) Abstract: A centralized resource manager (300) for distributed networks manages resources available on the network, such as
`network bandwidth, CPU allocation, TV tuners (48), MPEG encoders (114), disk bandwidth, and input/output devices. The cen—
`tralized resource manager (300) also allocates the resources of network clients (46) and a network—associated media server (14), in
`response to requests for media services via the distributed network. The centralized resource manager may include means for discov—
`ering when devices are added or removed from the network; a current, IR, or electromagnetic Field sensing system for determining
`O when Video devices are turned off so that resources associated with any device not in use may be reallocated elsewhere; or a power
`a switching system (307) for controlling the ON or OFF state of such devices so that resources associated with any device in the OFF
`state may be reallocated elsewhere.
`
`SONY - Ex.-1019
`
`1
`
`Sony Corporation - Petitioner
`
`SONY - Ex.-1019
`Sony Corporation - Petitioner
`
`1
`
`

`

`W0 03/025726 A1
`
`|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
`
`TR), OAPI patent (BF, BJ, CF, CG, CI, CM, GA, GN, GQ,
`GW, ML, MR, NE, SN, TD, TG).
`
`Published:
`
`7 with international search report
`
`For two-letter codes and other abbreviations, refer to the ”Guid-
`ance Notes on Codes andAbbreviations ” appearing at the begin-
`ning ofeach regular issue ofthe PCT Gazette.
`
`2
`
`

`

`W0 03/025726
`
`PCT/US02/27014
`
`CENTRALIZED RESOURCE MANAGER WITH PASSIVE SENSING SYSTEM
`
`5
`
`10
`
`PRIORITY CLAIM
`
`The present patent application claims priority of the following co-pen’ding,
`
`commonly owned patent applications:
`
`60/323,618 filed September 20, 2001 (Atty. Dkt. UCN-016);
`
`60/350,431 filed January 19, 2002 (Atty. Dkt. UCN-019); and
`
`60/372,490 filed April 12, 2002 (Atty. Dkt. UCN-O32).
`
`INCORPORATION BY REFERENCE
`
`The present application for United States Patent claims the benefit of and
`
`15
`
`incorporates herein by reference the contents of the following commonly owned
`
`US. Patent Applications:
`
`09/365,726 filed August 3, 1999, entitled “Multi—Service In-Home Network
`
`With an Open Interface”;
`
`09/809,770 (Atty. Dkt. UCN-006) filed March 16, 2001, entitled “Home
`
`20
`
`Area Network Including Arrangement for Distributing Television Programming
`
`Over Local Cable”;
`
`60/ 193,813, filed March 31, 2000, entitled “Home Area Network”;
`
`60/313,209 (Atty. Dkt. UCN-011), filed August 17, 2001, entitled
`
`“Delivering Multimedia Over Home Area Networks”;
`
`‘
`
`25
`
`60/313,228, filed August 17, 2001, entitled “Web Services Provisioning
`
`Architecture”;
`
`60/327,627 (Atty. Dkt. UCN-012), filed October 5, 2001, entitled “Home
`
`Area Network Centralized Video Recorder”;
`
`3
`
`

`

`W0 03/025726
`
`PCT/US02/27014
`
`60/345,966 (Atty. Dkt. UCN-017), filed November 7, 2001, entitled “Digital
`
`Video Recording System Supporting Concurrent Playback Using Advanced
`
`Program Information";
`
`10/017,675 (Atty. Dkt. UCN-018) filed December 15, 2001, entitled
`
`5
`
`“Centralized Digital Video Recording and Playback System Accessible To Multiple
`
`Reproduction And Control Units Via A Home Area Network”;
`
`10/032,218 (Atty. Dkt. UCN-015) filed December 21, 2001, entitled
`“Digital Video Recording and Reproduction System And Method Suitable For Live-
`
`Pause Playback Utilizing Intelligent Buffer Memory Allocation”;
`
`10
`
`60/323,618 (Atty. Dkt. UCN-016) filed September 20, 2001, entitled
`
`“Home Network Platform, Architecture and System”;
`
`60/350,431 (Atty. Dkt. UCN-019) filed January 18, 2002, entitled “Home
`
`Area Network Traffic Management with a Networked Personal Video Recorder”;
`
`60/350,431 (Atty. Dkt. UCN-032) filed April 11, 2002, entitled “Centralized
`
`15
`
`Resource Manager.
`
`FIELD OF THE INVENTION
`
`The present invention relates generally to home networks having multiple
`
`digital content storage, access and/or display elements, and in particular, relates
`
`20
`
`to a centralized resource manager that utilizes a passive sensing mechanism to
`
`control, allocate and othenNise manage distributed network resources in such
`
`home networks.
`
`25
`
`BACKGROUND OF THE INVENTION
`
`The concept of linking multiple digital entertainment devices in a home
`
`network infrastructure has become widely accepted. It is now possible to
`
`interconnect a plurality of these devices -- including televisions and video
`
`recording devices, audio recording and playback devices, personal computers,
`
`30
`
`and telephony devices —- in a network having sufficient bandwidth to distribute
`
`4
`
`

`

`W0 03/025726
`
`PCT/US02/27014
`
`media content "(e.g., movies, audio/stereo) and data throughout a home, as
`desired by the individual users, so that the resources of the devices may be
`
`shared. However, the sharing of these multiple devices in a home-based
`
`network presents new problems in allocating and managing the resources of the
`
`various devices in an efficient manner.
`
`Members of the Home Audio Video Interactive (HAVi) alliance have
`
`developed a protocol for dealing with distributed devices across a bus
`
`architecture (typically IEEE .1394 or FireWire), using concepts of resource
`
`management and reservation. Under the HAVi protocol, certain devices will
`
`10
`
`allow partial or total reservation of their resources. These devices include their
`
`own local resource manager component. A device wishing to reserve resources
`
`will communicate with the local resource manager associated with that device.
`
`If
`
`another device has reserved these resources, the device requesting these
`
`resources may negotiate with the resource holder by communicating messages
`
`15
`
`through the local resource manager of the device in question.
`
`However, the HAVi methodology is limited in several ways. First, 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
`
`20
`
`requests. Second, only devices on the network providing local resource
`
`managers may be reserved“ There is no proxy device for reserving the resources
`
`of “dumb” devices (i.e., devices having no local resource manager associated
`
`therewith) on the network. Third, the distributed nature results in added
`
`complexity for each device that must support a local resource manager.
`
`25
`
`30
`
`UPnP and Jini are similar resource discovery and control tools. Both of
`
`these lack any robust resource management tools. They are also implemented
`
`in a manner similar to HAVi, in that all devices are responsible for supporting the
`
`protocol, and support distributed, not centralized, interaction.
`
`'
`
`In addition, Tivo, ReplayTV, and others have developed personal video
`
`recording (PVR) products, which allow a user to digitally store television
`
`5
`
`

`

`W0 03/025726
`
`PCT/US02/27014
`
`programs and other media content for later viewing. Each of these products
`
`supports the reservation of a tuner to support a scheduled recording of television
`
`shows. However, neither supports distributed networks or distributed resource
`
`management.
`
`Accordingly, there exists a need for devices and systems that support
`
`distributed networks and centralized management of distributed network
`
`FGSOU I’CES.
`
`10
`
`SUMMARY OF THE INVENTION
`
`The present invention overcomes the disadvantages of prior art systems,
`
`by providing a centralized resource manager, rather than relying ‘on a plurality of
`
`local resource managers. The invention requires only one device to act as a
`
`centralized resource manager, enables the centralized resource manager to
`
`15
`
`assign 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.
`
`The centralized resource manager of the invention can be linked with a ‘
`
`media server and each client device in the distributed network. The centralized
`
`20
`
`resource manager identifies, assigns, and resen/es available network resources in
`
`response to user requests for processing media content so that the functionality
`
`of the distributed network is centralized, in a manner which most efficiently uses
`
`the resources of the distributed network. Managed resources can include,
`
`among others, network bandwidth, CPU allocation, TV tuners, MPEG encoders
`
`25
`
`and decoders, disk bandwidth, applications, and input/output devices.
`
`In a home-networking environment, a centralized resource manager
`
`allocates network resources in the following manner.
`
`In one embodiment,
`
`requests are made to the centralized resource manager in response to requests
`
`received from a user for viewing or recording television programming material,
`
`30
`
`or from agent processes acting on behalf of the user, such as an agent process
`
`using user profile or history information to predict that a user that has watched,
`
`6
`
`

`

`W0 03/025726
`
`PCT/US02/27014
`
`for example, several James Bond titles in the past would likely wish to record
`
`“Thunderball” and automatically schedule that recording on the user’s behalf.
`
`When a request is received from a user or agent process for viewing or recording
`
`television programming material, which may include viewing or recording
`
`television programming material available at a scheduled future time and
`
`channel, the centralized resource manager implements a reservation protocol
`
`(e.g., least—cost algorithm) to define a pipeline or session, using the available
`network resources embodied in the media server and client devices, to fulfill the
`
`user’s request. The centralized resource manager identifies available network
`
`10
`
`resources that match the requirements imposed by the user request using a
`
`scheduling algorithm to determine the availability of such network resources
`
`when the program will be viewed or recorded.
`
`Once an audio-video pipeline has been defined from the available network
`
`resources, these network resources are assigned and reserved for the
`
`15
`
`appropriate time, and a reservation identifier is returned to the scheduling
`
`application. The reservation is stored in a reservation table for use by the
`
`centralized resource manager in connection with any future user requests. The
`reservation identifier may include identification of the specific resources
`
`assigned, which would allow the requesting application to communicate with,
`
`20
`
`configure, and control the assigned resources.
`
`In another aspect of the invention, the audio—video pipeline can be
`
`constructed using a least cost algorithm to minimize the use of network
`
`bandwidth.
`
`In a further aspect of the present invention, in response to the user
`
`scheduling an event, the centralized resource manager checks to see if a disk
`
`25
`
`storage device in the network has sufficient disk space to record the media
`
`program.
`
`If the disk space is insufficient, the centralized resource manager
`
`searches for any files that may be deleted. The user may be alerted by
`
`displaying a message on the television screen or alerted when there are
`
`insufficient network resources to process the user’s current request.
`
`7
`
`

`

`W0 03/025726
`
`PCT/US02/27014
`
`In another aspect of the invention, the centralized resource manager can
`
`include an interface to a service provider that allows the service provider to
`
`reserve resources in response to the service provider scheduling an event.
`
`In a
`
`further aspect of the invention, the centralized resource manager communicates
`
`with a service provider Network Operation Center over a WAN interface when the
`
`service provider wishes to reserve resources for events such as pushing of
`
`special content or software upgrades.
`
`The centralized resource manager can also include sensing systems that
`
`are operable to determine when devices are added or removed from the
`
`10
`
`15
`
`network. These means may include a current, infrared (IR), or electro-magnetic
`
`field (EMF) sensing systems for detecting when video devices are turned off so
`
`that the network resources associated with that video device may be reallocated.
`
`The IR sensing system is operative to detect and process signals from a typical
`
`IR remote control device, and thereby determine the on/off state of the
`
`corresponding video device, so that resources associated with that device can be
`
`automatically reallocated.
`
`The centralized resource manager can also include a power switching
`
`system that is operable to control the on/off state of devices attached to the
`
`network. .This system may include the ability to plug devices into a switched
`
`.20
`
`power supply allowing the centralized resource manager to determine the
`
`powering on and off of the devices such that network resources associated with
`
`these devices may be automatically reallocated when the devices are determined
`
`to be in an OFF state. A typical IR or radio-frequency (RF) remote control device
`
`can be used to allow the user to command turning on and off of any device
`
`25
`
`equipped with a power switching system.
`
`The present invention may be implemented in a single network that uses
`
`video clients, audio clients, PC, and other devices. Various networking protocols
`
`and architectures can be used, including wireless LANs.
`
`8
`
`

`

`W0 03/025726
`
`PCT/US02/27014
`
`BRIEF DESCRIPTION OF THE DRAWINGS
`
`These and other features and advantages of the present invention will
`
`become apparent to those skilled in the art from the description below, with
`reference to the following drawing figures, in which:
`FIG. 1 generally illustrates a home network having a centralized resource
`
`manager (CRM) in accordance with the present invention.
`
`FIG. 2 shows another example of a network using the CRM of the present
`
`invention.
`
`10
`
`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.
`
`15
`
`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
`
`20
`
`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.
`
`25
`
`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.
`
`9
`
`

`

`W0 03/025726
`
`PCT/US02/27014
`
`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
`
`electro—magnetic field sensing system is used to detect the ON or OFF status of a
`
`television set.
`
`FIG. 16 shows further detail of the embodiment of FIG 15.
`
`FIG. 17 shows further detail of the embodiment of FIG 15.
`
`FIG. 18 illustrates another aspect of the present invention in which a
`
`power switch is used to control the ON or OFF status of a television set to
`
`10
`
`facilitate the automatic reallocation of resources.
`
`DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS
`
`Overview: The present invention is directed to a centralized resource
`
`15
`
`manager (CRM) that can be linked to a plurality of networked devices in a
`
`distributed network. One such network could be a home network having digital
`
`entertainment, computing, and communication devices. Examples of network
`
`services include audio and video processing (e.g., recording audio and/or video
`
`content for storage or real—time use), distributing audio and/or video content for
`
`20
`
`real-time presentation to a user (e.g., listening to a stereo system or viewing and
`
`listening via a television set), and data and graphics processing (e.g., creation,
`
`modification, display, storage, or rendering of data or graphics by using ,a PC or
`
`other devices or applications).
`
`Illustrative descriptions of distributed home
`
`networks are set forth below.
`
`‘
`
`25
`
`30
`
`In accordance with known network practice, each of the devices or
`
`'functional systems in the network can have resources that can be used by the
`
`functional system in conjunction with the services it provides.
`
`In the following
`
`discussion, network devices or functional systems are divided into two broad
`
`categories: client devices and atomic devices. A client device is any functional
`
`system that includes a local resource manager that provides a mechanism for
`
`control of resources useable by that client device. Such resources can be local
`
`10
`
`10
`
`

`

`W0 03/025726
`
`PCT/US02/27014
`
`resources, i.e.,‘ integral to the client device, and/or remote resources, e.g.,
`
`resources non-integral to the client device but available thereto via a server. An
`
`atomic device is any functional system that does not include a local resource
`
`manager.
`
`In accordance with the invention, while local resource managers exercise
`
`control over the set of resources useable by their respective client devices, the
`
`centralized resource manager controls not only these resources, but also the
`
`resources of atomic devices (i.e., proxy control) and the resources of the
`
`distributed network as a whole. Any conflict in the exercise of control over
`
`10
`
`resources between the centralized resource manager and the respective local
`
`resource manager can be resolved in favor of the centralized resource manager.
`
`In response to a user or agent process request to provide a service, e.g.,
`
`a media processing service such as recording a movie distributed by an external
`
`provider, the centralized resource manager exercises master control over the
`
`15
`
`network resources by identifying network resources that are available to fulfill
`
`the user (or agent process) request, assigning specific network resources frdm
`
`the available network resources to define a media pipeline or session that fulfills
`
`the user request, and reserving the network resources defining the media
`
`pipeline to fulfill the user (or agent process) request. The reserved network
`
`20
`
`resources can be used immediately or scheduled for use at a future date. Once
`
`the reserved network resources have been used to fulfill the user or agent
`
`process request, the centralized resource manager frees these network
`
`resources, changing their status from “reserved” to “available”.
`
`Exemplary Architectures: Referring to FIG. 1, a distributed network 10 is
`
`25
`
`30
`
`shown that embodies the present invention of a centralized resource manager
`
`12, which is contained within a media server 14. This centralized resource
`
`manager 12 is used in a distributed home network 10, and more specifically, in
`
`connection with home networked personal video recording and media
`
`distribution equipment. The centralized resource manager 12 also supports
`
`other client and atomic devices and services, such as PCs, telephones, network
`
`11
`
`11
`
`

`

`W0 03/025726
`
`PCT/US02/27014
`
`attached storage, webpads, and PDAs, interlinked with the home—based
`
`distributed network 10.
`
`In FIG. 1, the distributed home network 10 includes a
`
`LAN 16, which interlinks televisions 18, 20, 22, personal computers 24, 26, audio
`
`recording and playback devices 28, 30 and a standard telephone 32. Utilizing a
`
`wireless local area network (WLAN) capability 34, the distributed home network
`
`10 is also shown to support links to a remote television 36, a webpad 38, a
`
`laptop computer 40 and a PDA 42.
`
`10
`
`15
`
`The centralized resource manager 12 of FIG. 1 is responsible for
`
`identifying, managing and reserving network resources for client and/or atomic
`
`devices comprising the distributed home network 10. The centralized resource
`
`manager 12 can exercise master control of current network resoUrces, and can
`
`expand the network resources by the addition of client and/or atomic devices to
`
`the distributed home network 10. Representative examples of network resources
`for the distributed home network 10 depicted in FIG. 1 include network
`
`bandwidth, CPU allocation, disk bandwidth, TV tuners, MPEG encoders and I/O
`
`devices. Representative examples of various client devices include set-top boxes
`
`(STB5) 44, 46, 48 for video clients and STBs 50, 52 for audio clients. Other
`
`devices can similarly be employed.
`
`Typically, the centralized resource manager 12 is located in a gateway
`
`20
`
`device that manages the LAN and WAN links of the distributed home netWork 10,
`
`although one skilled in the art will understand that the foregoing description does
`
`not limit the present invention.
`
`In the embodiment shown in FIG. 1, the media
`
`server 14, which includes the centralized resource manager 12, is used for
`
`storing and serving audio, video and data content across the distributed home
`
`25
`
`network 10.
`
`‘
`
`Another example of a distributed home network utilizing the centralized
`
`resource manager 12 is illustrated in FIG. 2.
`
`In particular, FIG. 2 illustrates a
`
`home-based distributed network that includes three televisions 102, 104, 106.
`
`One television 102 is connected to a media server 108. The media server 108 is
`
`30
`
`capable of rendering graphics, decoding MPEG2, blending the content for display,
`
`10
`
`12
`
`12
`
`

`

`W0 03/025726
`
`PCT/US02/27014
`
`tuning in CATV channels (analog or digital) and MPEG2 encoding audio-video
`
`streams, i.e., the media server 108 functions as a client device. The media
`
`server 108 also includes a disk storage device 110 capable of storing and
`
`retrieving MPEG2 files. A second TV 104 is connected to a video client device
`
`112 capable of rendering graphics, decoding MPEG2 video and blending the
`
`content for display. A third television 106 is connected to a client device 114
`
`capable of rendering graphics, decoding MPEG2 video, blending the content for
`display, tuning in one CATV channel 120 (analog or digital) and MPEG2 encoding
`
`of analog content.
`
`10
`
`15
`
`The distributed network 116 comprises a typical 75-ohm coaxial cable
`
`used to deliver analog and digital cable channels through splitters to televisions,
`
`VCRs, etc. A LAN functionality is superimposed over the coax using frequency
`
`division multiplexing (e.g., using frequencies above or below the CATV channels
`
`for a general purpose data link).
`
`In this example, this network is Ethernet-over-
`
`coax, but other solutions exist, such as IEEE 1394 over coax, or HPNA over coax.
`
`In some topologies, a filter 118 may be required to prevent the data network
`
`frequencies from reaching outside the home.
`
`Examples of Operation: A method of controlling audio—video network
`
`resources of a distributed network by means of a centralized resource manager
`
`20
`
`will now be described. Consider an evening of family television viewing. Earlier
`
`in the day, Dad programmed a client device to record the hockey game (media
`
`content) at 8:00 PM on channel 150 (the user request). Dad used a graphical
`user interface (GUI) to navigate to the Electronic Program Guide (EPG)
`
`application of the client device and selected the game to record. The centralized
`
`25
`
`resource manager includes a scheduling application that requests a reservation
`
`of an audio—video pipeline or session with the resource requirements shown in
`
`FIG. 3, i.e., as defined by the user request.
`
`Referring now to FIG. 3, which shows a DCATV Tuner 200 and a disk
`
`storage medium 110, the resource requirements can be described in the
`
`30
`
`following manner. Since the hockey game is on a digital channel, the request is
`
`11
`
`13
`
`13
`
`

`

`W0 03/025726
`
`PCT/US02/27014
`
`made for a digital-capable tuner 200. Further requirements may be made on
`
`this tuner, such as it has an associated Conditional Access module enabling that
`
`tuner to tune to the appropriate channel. The reservation also requires access to
`
`the disk 110 to record the hockey game (such as by writing to a disk file). This
`
`requires two types of reservation: disk bandwidth and disk capacity.
`
`The centralized resource manager 12 will searchrthe resource database to
`
`identify available network resources that match the resource requirements
`
`imposed by the user request.
`
`In the system described, there is one disk 110
`
`(and more specifically one partition for video reported to the centralized resource
`
`manager 12) and three tuners.
`
`In this example, all three tuners have the same
`
`capabilities, and are distinguished only by their location in the distributed
`
`network. The centralized resource manager 12 implements a resource protocol,
`
`e.g., a least—cost algorithm, for constructing the media session or pipeline, i.e.,
`
`identify available network resources, assign available network resources to fulfill
`
`the request, and reserve the assigned network resources. Using one of the two
`tuners associated with the media server 108, the media pipeline can be
`
`constructed without using network bandwidth. By using the tuner in one of the
`
`client devices 112, 114, in contrast, the centralized resource manager 12 would
`
`need to reserve network bandwidth. There is no cost difference between the
`
`10
`
`15
`
`20
`
`two local tuners associated with the media server 108, so the lower number one
`
`is chosen.
`
`The centralized resource manager 12 checks the disk storage device 110
`
`for disk space both when the user schedules the recording and shortly before the
`
`recording event. If insufficient disk space is available when the user schedules
`
`25
`
`30
`
`the event, the centralized resource manager 12 checks to see if the disk storage
`
`deVice 110 includes any “delete-able” files.
`
`If all the files on the disk storage
`
`device 110 are marked as “do not delete”, the user will be alerted that the user
`
`request cannot be fulfilled (scheduled) due to insufficient recording space on the
`
`disk storage device 110.
`
`If sufficient disk space is available (or there are
`
`deleteable files), disk space will be reserved at the time of the request by the
`
`12
`
`14
`
`14
`
`

`

`W0 03/025726
`
`PCT/US02/27014
`
`centralized resource manager 12. However, disk space will not be created (by
`
`deleting files) until the time the recording is scheduled to begin. ‘
`
`The centralized resource manager 12 also reserves disk bandwidth for the
`
`recording at the time the recording is scheduled. Upon successful reservation of
`
`the required network resources, the reservation is stored in a network resource
`
`reservation table for use in comparison against future user (or agent process)
`
`requests. Reservation of network resources to fulfill any request, i.e., the media
`
`pipeline or session, is communicated back to the scheduling application with a
`
`reservation id for the specific event.
`
`10
`
`At 7:30, the children want to watch a show in the family room. This
`
`television 106 is associated with the client device 114 with the MPEG2 encoder
`
`206. The show they want to watch is on analog channel. They select this
`
`program from the EPG and the scheduling application contacts the centralized
`
`resource manager 12 to request network resources. FIG. 4 illUstrates the
`
`15
`
`resulting situation.
`
`As shown in FIG. 4, the end of the pipeline or session is the video display
`
`of television 106. More specifically, the requested media pipeline needs to
`
`terminate with the display on the family room set 106. The video
`
`compression/decompression functionality supported by the distributed network is
`
`20
`
`MPEGZ. The media pipeline needs to decode MPEG2 by means of an MPEG2
`
`decoder 208 prior to video display. Live-pause functionality is requested, so a
`
`network resource requirement imposed by the user request includes elastic
`
`recording to the disk storage device 110. Prior to reCording on the disk storage
`
`device 110, the video needs to be encoded with an MPEG2 encoder 206. The
`
`25
`
`channel requested is available in the analog spectrum, so an analog tuner 204 is
`
`required.
`
`Note that with the exception of the video output display provided by the
`
`television set 106, the requested pipeline is not limited by the location in the
`
`distributed network where the network resources are located. The centralized
`
`30
`
`resource manager will use resource protocols, e.g., least cost-of—bandwidth
`
`13
`
`15
`
`15
`
`

`

`W0 03/025726
`
`PCT/US02/27014
`
`algorithms, to determine which network resources are assigned to fulfill the user
`
`request.
`
`Bandwidth requirements for un-encoded video are high, so the MPEG2
`
`decoder 208 chosen is the decoder in the client device 114 (see FIG. 2) attached
`
`locally to the family room television 106. Similarly, the MPEG2 encoder 206
`
`needs to be local to the analog tuner 204. There are two available tuners on the
`
`system; one in the media server 108 next to the living room television 102, and
`one in the family room in the client device 114. While the tuner in the family
`
`room is local to the set 106, the video content needs to be written to the disk
`
`104
`
`storage device 110 in the media server 108. The least-cost algorithm leads the
`
`centralized resource manager 12 to assign the tuner/encoder pair in the media
`
`server 108 to the media pipeline, thereby eliminating the requirement to write
`
`encoded data twice across the distributed network. This method preserves more
`
`network bandwidth for other uses such as data transfers between PCs linked to
`
`15
`
`the distributed network.
`
`It should be obvious to those skilled in the art that
`
`algorithms other than least-cost can be used to assign the network resources to
`
`fulfill a user (or agent process) request.
`
`Once the centralized resource manager 12 has successfully mapped the
`
`requested media pipeline to available network resources, the instantiated graph
`
`20
`
`is returned to the scheduling application, and the assigned resources are marked
`
`as reserved (indefinitely). The centralized resource manager 12 has assigned
`
`one other resource to the graph, as shown in FIG. 5. Referring now to FIG. 5, it
`
`will be understood that the LAN connection is required to connect the resources
`
`of the media server 108 to the resources of the client device 114. The LAN 116
`
`is a managed network resource, and for this pipeline bandwidth is reserved for
`
`the video content.
`
`At 7:45, Mom wants to watch a program in the kitchen. The television
`
`104 in the kitchen is connected to the decode-only video client device 112 (see
`
`FIG.