WO2006014955A2

WO2006014955A2 - State machine for scheduled recording

Info

Publication number: WO2006014955A2
Application number: PCT/US2005/026490
Authority: WO
Inventors: Yue Ma; Dennis Bushmitch
Original assignee: Matsushita Electric Industrial Co., Ltd.
Priority date: 2004-07-27
Filing date: 2005-07-27
Publication date: 2006-02-09
Also published as: WO2006014955A3

Abstract

A scheduled recording service (12) for reporting status (33) of a recording device (16A) includes a rule set which defines different operating states for the recording device in relation to a recording task. A task status function is adapted to receive status information (33) for a particular recording task from the recording device (16A) and is operable to determine a current operating state (34) for the particular recording task (32) in accordance with the rule set. A reporting function is in data communication with the task status function and is operable to expose properties associated with the particular record task based on the current operating state.

Description

STATE MACHINE FOR SCHEDULED RECORDING

CROSS-REFERENCE TO RELATED APPLICATIONS [0001] This application claims the benefit of U.S. Provisional Application No. 60/591 ,422 filed on July 27, 2004. The disclosure of the above application is incorporated herein by reference.

FIELD OF THE INVENTION

[0002] The present invention relates to a method and system for providing status information for scheduled recordings.

BACKGROUND OF THE INVENTION

[0003] Vendors of various technologies are working together to achieve device-to-device interoperability. Forums have been created to enable the emergence of easily connected devices and simplify the implementation of home and corporate networks. These forums are currently working on standards to achieve this interoperability. The standards include methods and systems that facilitate a common communication scheme between a variety of electronic devices. [0004] It is foreseen that various types of recording devices can be connected to the network. The recording devices can be capable of recording selected television programs or music content. A central service known as scheduled recording service can be implemented according to the standards and manage all life cycles of recordings. The scheduled recording service call allow a user to control and access information about the recording devices on the network. The scheduled recording service a system and method to facilitate a common communication scheme between various recording devices, to determine an informative status of the recording device, and to allow a user to act on the status of the recording device.

SUMMARY OF THE INVENTION [0005] In accordance with the present invention, a scheduled recording service is provided for reporting status of a recording device. The scheduled recording service includes a rule set which defines different operating states for the recording device in relation to a recording task; a task status function adapted to receive status information for a particular recording task from the recording device and operable to determine a current operating state for the particular recording task in accordance with the rule set; and a reporting function that exposes properties associated with the particular record task based on the current operating state. [0006] Further areas of applicability of the present invention will become apparent from the detailed description provided hereinafter. It should be understood that the detailed description and specific examples, while indicating the preferred embodiment of the invention, are intended for purposes of illustration only and are not intended to limit the scope of the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

[0007] The present invention will become more fully understood from the detailed description and the accompanying drawings, wherein:

[0008] Figure 1 is an illustration of an exemplary network environment operating in accordance with Universal Plug and Play protocol including a scheduled recording service according to the present invention;

[0009] Figure 2 is a dataflow diagram illustrating functions and dataflow of the scheduled recording service according to the present invention;

[0010] Figure 3 is a sequence diagram illustrating an exemplary sequence of steps performed by the system;

[0011] Figure 4 is a state diagram illustrating a first embodiment of record task states;

[0012] Figure 5 is a state diagram illustrating a first embodiment of record schedule states; [0013] Figure 6 is a state diagram illustrating a second embodiment of record task states; [0014] Figure 7 is a state diagram illustrating a second embodiment of record schedule states;

[0015] Figure 8 is a state diagram illustrating a third embodiment of record task states; and [0016] Figure 9 is a state diagram illustrating a third embodiment of record schedule states.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS [0017] Figure 1 depicts an exemplary system 10 for scheduling and reporting recording events according to the present invention. The system is generally comprised of at least one requesting device 14 interconnected by a network 18 to a plurality of recording devices 16. Each recording device 16 may include a schedule recording service 12 as further described below. It is also envisioned that the schedule recording service may reside upon other network devices in the network environment. In an exemplary embodiment, the devices communicate in accordance with the Universal Plug and Play (UPnP) protocol. In this embodiment, the requesting device is understood to be a control point. While the following description is provided with reference to UPnP, it is readily understood the broader aspects of the present invention are applicable to devices communicating in accordance with other plug-n-play protocols and/or service oriented architectures.

[0018] In operation, the control point (CP) 14 communicates requests for scheduling recordings. The scheduled recording service (SRS) 12 sets up a record schedule based on the request. A record schedule can include any number of related or non-related programs to be recorded. For example, a record schedule can include the recording of a television episode at a particular time for a specified number of weeks. Individual record tasks are created based on the record schedule. In the above mentioned example, the record task can be an individual episode. Each record task created is designated a start time and an end time.

[0019] CP 14 further communicates requests for exposure of properties pertaining to record schedules and/or record tasks. SRS 12 determines states and properties for record tasks and/or record schedules and provides the states and properties to the CP 14. Recording devices 16A-16N record media content and communicate their recording status to the SRS 12.

[0020] Referring to Figures 1 and 2, Figure 2 is a dataflow diagram including the functions and dataflow of the SRS 12 according to the present invention. The SRS 12 includes a task status function 20, a schedule status function 21 , and a reporting function 22. The task status function 20 is receptive of scheduled start times 23 and end times 24 for record tasks and status information 25. The start times 23 and end times 24 can be received from other functions within the SRS 12. The status information can be received from recording devices 16A-16N. Status information 25 can include recording errors and recording successes.

[0021] Task status function 20 determines a current operating state for each record task. As will be described in more detail below, the record task state is determined from status information 25, start times 23, end times 24, and a predefined rule set. The rule set defines the transitions between the different operating states. Task status function 20 further determines properties to be exposed for each record task according to the determined operating state and status information 25. Record task properties 26 are provided to the schedule status function 21 and the reporting function 22.

[0022] The schedule status function 21 is receptive of record task properties 26. Schedule status function 21 determines a current operating state for each record schedule based on record task properties 26. As will be described in more detail below, the record schedule state is determined from a rule set and a status property for each record task associated with the record schedule. Schedule status function 21 determines properties to be exposed for each record schedule according to the determined operating state and status properties 26 of the associated record tasks. Record schedule properties 27 are provided to the reporting function 22. [0023] Once the SRS 12 determines the current state and properties for record tasks and/or record schedules, the reporting function 22 can expose property data 29 based on an initiated request 28. In the exemplary embodiment, the request can be received from the CP 14. Reporting function 22 provides record task properties 26 and record schedule properties 27 to the device or function initiating the request. Property data 29 can include a record schedule state, a record task state, a record schedule status, a record task status, a record schedule error list, and a record task error list.

[0024] Referring to Figure 3, a sequence diagram illustrating the sequence of events that may occur when exposing properties of a record schedule and/or record task to a user interacting with a control point 14 is shown. In step 30, a user initiates a request to record a program or a series of programs to CP 14. In step 31 , CP 14 sends a request to SRS 12 to set up a record schedule pertaining to the user's request. SRS 12 creates and schedules record tasks associated with the record schedule in step 32. Recording device 16A sends recording status information to SRS 12 in step 33. Status information can be sent any number of times during the recording period. SRS 12 continually determines a record task state and/or a record schedule state in step 34. SRS 12 continually determines properties of the record task and/or record schedule based on the status information and state in step 35.

[0025] At any time after scheduling a recording, a user of the system may initiate a request for status of the scheduled recording in step 36. Upon request by the user, CP 14 sends a request for a status update pertaining to the record schedule and/or record tasks in step 37. The SRS 12 provides the properties to CP 14 in step 38. The CP 14 may then display the properties to the user requesting the status update in step 39.

[0026] Referring to Figure 4, a first embodiment of a state diagram illustrating states of a record task is shown. A record task can be in any one of the following states: an idle state 40, an active state 42, a fully recorded state 44, a partially recorded state 48, and a not recorded state 46. A record task begins in an idle state 40 and remains in the idle state 40 until a recording start time arrives. A record task transitions to an active state 42 after the recording start time arrives. The record task remains in the active state until the end time arrives. Once the end time arrives, a record task can transition to a fully recorded state 44, a not recorded state 46 or a partially recorded state 48. By default (not shown in Figure 4), any record task in the idle state 40 or the active state 42 can transition to the not recorded state 46 directly if a fatal error occurs.

[0027] If the record task completed successfully, the record task transitions to the fully recorded state 44. If the record task failed due to conflict or error, the record task transitions to the not recorded state 46. If the record task is complete but only partially recorded, the record task transitions to the partially recorded state 48. The partially recorded state 48 only applies to recording devices that support partial recording. If a device does not support partial recording, the final states will be simply fully recorded 44 or not recorded 46. Fully recorded state 44, partially recorded state 48, and not recorded state 46 are considered final states indicating the amount recorded. Once a record task has reached a final state, it may not transition to any other state.

[0028] Once the task status function determines the state, the reporting function exposes properties associated with the record task and record task state. State properties indicate the current state of the record task and can be IDLE, ACTIVE, FULLY RECORDED, PARTIALLY RECORDED and NOT RECORDED. Status properties provide a description of the primary reason why the state has been reached and more detailed information about each state. The status property can be a numerical value and/or short description. The following table illustrates an exemplary list of status properties that can be associated with the above mentioned states.

Table 1

[0029] The number 0 for success can be exposed in the idle state 40, the active state 42, and the fully recorded state 44. Success indicates when the record task is recording or has completed recording with no errors reported. The numbers 1-9 can be exposed under certain circumstances while in the idle state 40, the active state 42, the partially recorded state 48, and the not recorded state 46. The number 1 can be exposed when the specified contents to be recorded are copy protected. The numbers 2-5 relate to potential errors with the media used to record. The number 2 can be exposed when the specified removable media is not inserted into the recording device. The number 3 can be exposed when the specified removable media is write protected. The number 4 can be exposed when the specified media does not have sufficient capacity to store the contents to be recorded. The number 5 can be exposed when the there exists some other error with the removable media inserted into the recording device.

[0030] The number 6 for resource error can be exposed when an error related to the recording device 16A (Figure 1 ) exists. The number 7 for conflicted can be exposed when another record task is scheduled to record at the same time on the same recording device 16A (Figure 1 ). The number 8 for disabled can be exposed when the record task has been disabled by the CP 14 or recording device 16A (Figure 1 ). The number 9 can be exposed when another error exists pertaining to a specific recording device 16A (Figure 1). As can be appreciated, the following list is not exclusive. Additional status properties may be added to accommodate the needs of various recording devices.

[0031] The CP 14 of Figure 1 may act upon a record task to change the values of the status properties while in a particular state. The status property of a record task, however, can not be changed directly by the CP 14. CP 14 may invoke some actions that cause the status of the SRS to change. For example, if the status property exposed is 8 for disabled, the CP 14 can enable the record task. The property changes to 0 for success if there are no conflicts or errors. If the status property is 7 for conflicted, the CP 14 may change the priority of the record task to make it be the "winner" among conflicting tasks. Consequently, the status changes to 0 for success.

[0032] An error list property is provided for situations when more than one error exists for a record task. The error list provides a listing of any errors that occurred while recording. Errors can be exposed via numerical values and/or descriptions corresponding to the numerical values. More than one concurrent error can be exposed in a comma separated variable (CSV) format. The following table illustrates an exemplary list of errors that can be associated with the error list attribute.

Table 2

This list is not exclusive. As can be appreciated, the error list properties can include additional errors pertaining to the media, recording device, or scheduling of a record task. The error list properties do not have to match the status properties. However, during active recording, the value in status properties can be treated as primary information or a summary of those exposed in the error list property. The status property is a single value whereas error list property is multiple values. For example, a record task is in the active state the status property is 7 and the associated error list property can be "7,5."

[0033] Referring to Figure 5, a first embodiment of a state diagram illustrating states of a record schedule is shown. The state of a particular record schedule can be determined from record tasks associated with the record schedule. Record schedule states can be: an idle state 50, an active state 52, a fully recorded state 54, a partially recorded state 56, and a not recorded state 58. A record schedule begins in an idle state 50 and remains in that state while there is at least one planned record task remaining to begin. A record schedule transitions to an active state 52 when at least one record task status property indicates ACTIVE. The record task remains in the active state 52 while at least one record task status property is ACTIVE. If at least one planned record task remains and no record task status properties indicate ACTIVE, the record schedule transitions back to the idle state 50. From the active state 52, record schedule can transition to a fully recorded state 54, a partially recorded state 56, or a not recorded state 58.

[0034] A record schedule transitions to the fully recorded state 54 once no planned recording remains and all record task status properties indicate FULLY RECORDED. A record schedule transitions to the not recorded state 58 once no planned recording remains and all record task status properties indicate NOT RECORDED. A record schedule can transition to a partially recorded state once no planned recording remains and at least one record task status property indicates PARTIALLY RECORDED or at least one, but not all, record task status properties indicate NOT RECORDED. Fully recorded state 54, partially recorded state 56 and not recorded state 58 are considered final states indicating the amount recorded. Once a record schedule has transitioned to a final state, it may not transition to any other state.

[0035] For record schedules pertaining to a series of programs, a desired maximum number of recordings can be added to the rule set. The record schedule remains in the idle state 50 or the active state 52 until the desired maximum number of recordings is met. Before the desired maximum number of recordings is met, even if no record tasks currently exist, future planned recording will be created, and the record schedule remains in the idle state 50.

[0036] Similar to the record tasks, properties associated with the record schedules and record schedule states can be exposed. State properties can be IDLE, ACTIVE, FULLY RECORDED, PARTIALLY RECORDED and NOT RECORDED. Status properties can be exposed via a numerical value and/or a short description similar to the status properties of record tasks (see Table 1 ). As can be appreciated, the status properties list may be extended to include status reports defined by a vendor of a recording device. If the record schedule is in the idle state 50, the active state 52, the not recorded state 58, or the partially recorded state 56, the status property can indicate errors with scheduled recording. If the state is fully recorded 54, the status property can indicate 0 for success of the scheduled recording. If the state is partially recorded 56 or not recorded 58, the status property for the record schedule is set to the status property of the record task causing the record schedule to transition to the state. If there exists multiple record task errors, status attribute is set to 9 for other error. Each record task associated with the record schedule can then be viewed to determine individual status and error list properties. [0037] The CP 14 of Figure 1 may act upon a record schedule to change the behavior of the schedule, however, the values of the state and status properties can not be directly changed by the CP 14. For example, if the CP 14 disables a record schedule, the current state of the schedule does not change. However, status property reports 8 for disabled. Moreover, all record tasks associated with the record schedule are disabled and their individual status properties are set accordingly.

[0038] Referring to Figure 6, a second embodiment of a state diagram for a record task is shown. The second embodiment replaces the active state 42 of the first embodiment in Figure 3 with an active idle state 60 and an active recording state 62. In Figure 6, a record task begins in the idle state 40 and remains in the idle state 40 until a recording start time arrives. The record task transitions to the active idle state 60 after the recording start time arrives. Active recording indicates the device is physically recording contents on a media whereas active idle indicates the device should be recording but is actually not recording. The record task transitions from the active idle state 60 to the active recording state 62 when actual recording of the record task begins. The record task can transition back and forth between the active idle state 60 and the active recording state 62 when the task is disabled/enabled by the CP 14, or when conflicts and conflict resolutions occur for concurrent record tasks.

[0039] Once the end time arrives and the record task is in the active idle state 60, the record task will transition from the active idle state 60 to the partially recorded state 48 or the not recorded state 46 depending on the status information of the record task. If the record task is in the active recording state 62 when the end time arrives, a record task can transition to a fully recorded state 44, a not recorded state 46, or a partially recorded state 48. If the record task completed successfully, the record task transitions to the fully recorded state 44. If the record task failed due to conflict or error, the record task transitions to a not recorded state 46. If the record task is complete but only partially recorded, the record task transitions to a partially recorded state 48.

[0040] Similar to the first embodiment of the record task diagram, a reporting function exposes properties associated with the record task and record task state. State properties can be: IDLE, ACTIVE IDLE, ACTIVE RECORDING, FULLY RECORDED, PARTIALLY RECORDED and NOT RECORDED. Status properties can include status numbers and descriptions listed in Table 1. If the record task is in the idle state 40, the active idle state 60, the not recorded state 46, or the partially recorded state 48, the status property can indicate errors with scheduled recording. If the state is fully recorded 44 or active recording 62, the status property can indicate 0 for success of the scheduled recording. As can be appreciated, the status properties list may be extended to include status properties defined by a vendor of a recording device. Error list properties can include the errors listed in Table 2. As can be appreciated, the error list may be extended to include errors defined by a vendor of a recording device.

[0041] Referring to Figure 7, a second embodiment of a state diagram illustrating states of a record schedule is shown. The second embodiment replaces the active state 52 of the first embodiment in Figure 4 with an active idle state 64 and an active recording state 66. All record tasks associated with a record schedule are evaluated to determine the proper state of the record schedule. In Figure 7, a record schedule begins in the idle state 50. The record schedule transitions from the idle state 50 to the active recording state 66 when . at least one record task status property indicates ACTIVE RECORDING. If at least one record task status property indicates ACTIVE IDLE and no record task status properties indicate ACTIVE RECORDING, the record schedule transitions from the idle state 50 to the active idle state 64. If one record task status property becomes ACTIVE RECORDING, the record schedule transition from the active idle state 64 to the active recording state 66. If all record task status properties become ACTIVE IDLE, the record schedule transitions from the active recording state 66 to the active idle state 64. If at least one planned record task remains for the record schedule that does not indicate ACTIVE RECORDING or ACTIVE IDLE but indicates IDLE, the record schedule transitions from either the active recording state 66 or the active idle state 64 back to the idle state 50.

[0042] Once all planned record tasks associated with the record schedule have completed, the record schedule transitions from either the active idle state 64 or the active recording state 66 to the fully recorded state 54, the partially recorded state 56, or the not recorded state 58. The record schedule transitions to a fully recorded state 54 when status properties for all record tasks associated with the record schedule indicate FULLY RECORDED. The record schedule transitions to the not recoded state 58 when all record tasks status properties indicate NOT RECORDED. The record schedule transitions to the partially recorded state 56 when at least one record task status property indicates PARTIALLY RECORDED or at least one, but not all, record tasks status properties indicate NOT RECORDED.

[0043] Similar to the first embodiment of the record schedule state diagram, a reporting function exposes properties associated with the record schedule and record schedule state. State properties can be: IDLE, ACTIVE IDLE, ACTIVE RECORDING, FULLY RECORDED, PARTIALLY RECORDED and NOT RECORDED. Status properties can include the status numbers and descriptions listed in Table 1. As can be appreciated, the status properties list may be extended to include status reports defined by a vendor of a recording device. If the record schedule is in the idle state 50, the active idle state 64, the not recorded state 58, or the partially recorded state 56, the status property can indicate errors with scheduled recording. If the state is active recording 66 or fully recorded 54, the status property can indicate 0 for success of the scheduled recording. If the state is partially recorded 56 or not recorded 58, the status property for the record schedule is set to the status property of the record task causing the record schedule to transition to the state. If there exists multiple record task errors, status attribute is set to 9 for other error. Each record task associated with the record schedule can then be viewed to determine individual status and error list properties.

[0044] Referring to Figure 8, a third embodiment of a state diagram illustrating states of a record task is shown. The state diagram includes: an idle state 68, an activated state 70, an actively recording state 72, a stopped state 74, and a finished state 76. In Figure 8, a record task begins in the idle state 68. The record task transitions from the idle state 68 to the activated state 70 once a record task time arrives. The record task transitions from the activated state 70 to the actively recording state 72 once all conditions for recording are satisfied. If not all conditions for recording are satisfied, the record task will continue to be in the activated state 70 until the condition is satisfied or the end time arrives. If the end time arrives and all conditions for recording are not satisfied, record task transitions to the finished state 76. When in the actively recording state 72, if a non-fatal error occurs or CP 14 (Figure 1) modifies the record task that causes it to suspend active recording, the record task transitions from the actively recording state 72 to the stopped state 74. If the non-fatal error is remedied or the CP 14 (Figure 1) modifies the status, the record task transitions back to the actively recording state 72.. If the record end time arrives or a fatal error occurs, the record task transitions from either the actively recording state 72 or the stopped state 74 to the finished state 76.

[0045] Similar to the other embodiments of the record task state diagram, a reporting function exposes properties associated with the record task and record task state. State properties can be: IDLE, ACTIVED, ACTIVELY RECORDING, STOPPED, and FINISHED. If the record task state is finished the reporting function reports RECORDED, PARTIALLY RECORDED or NOT RECORDED in addition to FINISHED. Status properties can include the status numbers and descriptions listed in Table 1. As can be appreciated, the status properties list may be extended to include status properties defined by a vendor of a recording device. The status property number 0 for success of Table 1 can be exposed in the actively recording state 72 and the finished state 76. The status properties 1-9 of Table 1 can be exposed in the activated state 70, the stopped state 74, and the finished state 76. Error list properties can include the errors listed in Table 2. As can be appreciated, the error list may be extended to include errors defined by a vendor of a recording device.

[0046] Referring to Figure 9, a third embodiment of a state diagram pertaining to a record schedule is shown. The state diagram includes: an idle state 78, an activated state 80, an actively recording state 82, a stopped state 84, and a finished state 86. All record tasks associated with a record schedule are evaluated to determine the proper state of the record schedule. In Figure 9, a record schedule begins in the idle state 78. The record schedule transitions from the idle state 78 to the activated state 80 once at least one record task status property indicates ACTIVATED and no record task status properties indicate ACTIVELY RECORDING or STOPPED. The record schedule transitions back to the idle state 78 from the activated state 80 if at least one planned record task exists and no record task status properties indicate ACTIVATED, ACTIVELY RECORDING, or STOPPED. [0047] The record schedule transitions from the activated state 80 to the actively recording state 82 once at least one record task status property indicates ACTIVELY RECORDING. When in the actively recording state 82, if at least one record task is STOPPED and no record task status properties indicate ACTIVELY RECORDING, the record schedule transitions from the actively recording state 82 to the stopped state 84. If at least one record task status property becomes ACTIVELY RECORDING when in the stopped state 84, the record schedule transitions back to the actively recording state 82. If at least one planned record task remains and no record task status properties indicate ACTIVATED, ACTIVELY RECORDING, or STOPPED, the record schedule transitions from the actively recording state 82 to the idle state 78. Once no planned recording remains and all record tasks status properties indicate FINISHED, the record schedule transitions from the actively recording state 82, the activated state 80, or the stopped state 84 to the finished state 86.

[0048] Similar to the other embodiments of the record schedule state diagram, a reporting function exposes properties associated with the record schedule and record schedule state. State properties can be: IDLE, ACTIVED, ACTIVELY RECORDING, STOPPED, and FINISHED. If the record schedule state is finished the reporting function reports RECORDED, PARTIALLY RECORDED or NOT RECORDED in addition to FINISHED.

[0049] Status properties for the record schedule can include the status numbers and descriptions listed in Table 1. As can be appreciated, the status properties list may be extended to include status reports defined by a vendor of a recording device. If the record schedule is in the idle state 78, the actively recording state 82 or the finished state 86, the status property can indicate 0 for success of the scheduled recording. If the record schedule is in the idle state 78, the activate state 80, the stopped state 84, or the finished state 86 the status property can indicate errors with scheduled recording. If there exists multiple record task errors, the status attribute is set to 9 for other error. Each record task associated with the record schedule can then be viewed to determine individual status and error list properties. [0050] The description of the invention is merely exemplary in nature and, thus, variations that do not depart from the gist of the invention are intended to be within the scope of the invention. Such variations are not to be regarded as a departure from the spirit and scope of the invention.

Claims

CLAIMS What is claimed is:

1. A scheduled recording service for reporting status of a recording device, comprising: a rule set which defines different operating states for the recording device in relation to a recording task; a task status function adapted to receive status information for a particular recording task from the recording device and operable to determine a current operating state for the particular recording task in accordance with the rule set; and a reporting function in data communication with the task status function and operable to expose properties associated with the particular record task based on the current operating state, wherein the scheduled recording service operate in accordance with a plug and play protocol.

2. The scheduled recording service of Claim 1 wherein the different operating states include an idle state, an active state, a fully recorded state, a partially recorded state, and a not recorded state.

3. The scheduled recording service of Claim 1 wherein the rule set further defines the requirements which govern transitions between the different operating states.

4. The scheduled recording service of Claim 3 wherein the particular recording task having a start time and an end time, such that the rule set defines requirements which correlate a current time with at least one of the start time and the end time of the particular recording task.

5. The scheduled recording service of Claim 1 wherein the properties associated with a recording task include a list of concurrent errors associated with the recording task.

6. The schedule recording service of Claim 1 wherein the properties associated with a recording task includes a primary reason why the current operating state has been reached.

7. The scheduled recording service of Claim 6 wherein the task status function receives the primary reason from the recording device.

8. The scheduled recording service of Claim 1 operates as a service in accordance with a Universal Plug and Play (UPnP) protocol.

9. A schedule recording service for reporting status of a record schedule placed with a recording device, the record schedule being comprised of one or more recording tasks, comprising: a rule set which defines different operating states for a recording task and different schedule states for a record schedule; a task status function adapted to receive status information for the recording tasks associated with the record schedule and operable to determine a current operating state for each of the recording tasks; a schedule status function in data communication with the task status function and operable to determine a current schedule state for the record schedule based on the current operating state of the recording tasks associated with the record schedule; and a reporting function in data communication with the schedule status function and operable to expose properties associated with the record schedule, wherein the schedule recording device operates in accordance with a plug and play protocol.

10. The schedule recording service of Claim 9 wherein the rule set further defines the requirements which govern transitions between the different schedule states and between the different operating states.

11. The schedule recording service of Claim 9 wherein the different schedule states for a record schedule include an idle state, an active state, a fully recorded state, a partially recorded state, and a not recorded state.

12. The schedule recording service of Claim 11 wherein the different operating states for a recording task include an idle state, an active state, a fully recorded state, a partially recorded state, and a not recorded state

13. The scheduled recording service of Claim 12 wherein the current schedule state for the record schedule is set to an active state when at least one recording tasks associated with the record schedule are in an active operating state.

14. The scheduled recording service of Claim 12 wherein the current schedule state for the record schedule is set to an idle state when at least one recording task associated with the record schedule is planned and no existing tasks expose the active state.

15. The scheduled recording service of Claim 12 wherein the current schedule state for the record schedule is set to a partially recorded state when no planned recording tasks remain and at least one recording task is in a partially recorded operating state, or at least one, but not all, is in a not recorded state.

16. The scheduled recording service of Claim 12 wherein the current schedule state for the record schedule is set to a not recorded state when no planned recording tasks remain and all recording tasks are in a not recorded operating state.

17. The scheduled recording service of Claim 12 wherein the current schedule state for the record schedule is set to a fully recorded state when no planned recording tasks remain and all recording tasks are in a fully recorded operating state.

18. The scheduled recording service of Claim 9 wherein the properties associated with a record schedule include a primary reason why the current schedule state has been reached and a list of concurrent errors associated with the record schedule.

19. The scheduled recording service of Claim 9 wherein the different schedule states for a record schedule include an idle state, an active idle state, an active recording state, a fully recorded state, a partially recorded state, and a not recorded state.

20. The scheduled recording service of claim 19 wherein the different operating states for a recording task include an idle state, an active idle state, an active recording state, a fully recorded state, a partially recorded state, and a not recorded state.

21. The scheduled recording service of Claim 20 wherein the current schedule state for the record schedule is set to an active idle state when at least one record task associated with the record schedule is in an active idle operating state and no recording tasks associated with the record schedule are in an active recording operating state.

22. The scheduled recording service of Claim 20 wherein the current schedule state for the record schedule is set to an idle state when at least on record task is planned and no recording tasks associated with the record schedule is in an active idle operating state or an active recording operating state.

23. The scheduled recording service of Claim 20 wherein the current schedule state for the record schedule is set to an active recording state when at least one recording task is in an active recording operating state.

24. The scheduled recording service of Claim 20 wherein the current schedule state for the record schedule is set to a partially recorded state when no planned recording tasks remain and at least one recording task is in a partially recorded operating state, or at least one, but not all, is in a not recorded state.

25. The scheduled recording service of Claim 12 wherein the current schedule state for the record schedule is set to a not recorded state when no planned recording tasks remain and all recording tasks are in a not recorded operating state.

26. The scheduled recording service of Claim 12 wherein the current schedule state for the record schedule is set to a fully recorded state when no planned recording tasks remain and all recording tasks are in a fully recorded operating state.

27. The scheduled recording service of Claim 9 wherein the different operating states for a recording task include an idle state, an activated state, an actively recorded state, a stopped state, and a finished state.

28. The scheduled recording service of Claim 9 operates as a service in accordance with a Universal Plug and Play (UPnP) protocol.