WO2006014955A2 - Machine d'etat pour enregistrements programmes - Google Patents

Machine d'etat pour enregistrements programmes Download PDF

Info

Publication number
WO2006014955A2
WO2006014955A2 PCT/US2005/026490 US2005026490W WO2006014955A2 WO 2006014955 A2 WO2006014955 A2 WO 2006014955A2 US 2005026490 W US2005026490 W US 2005026490W WO 2006014955 A2 WO2006014955 A2 WO 2006014955A2
Authority
WO
WIPO (PCT)
Prior art keywords
state
recording
schedule
record
task
Prior art date
Application number
PCT/US2005/026490
Other languages
English (en)
Other versions
WO2006014955A3 (fr
Inventor
Yue Ma
Dennis Bushmitch
Original Assignee
Matsushita Electric Industrial Co., Ltd.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Matsushita Electric Industrial Co., Ltd. filed Critical Matsushita Electric Industrial Co., Ltd.
Publication of WO2006014955A2 publication Critical patent/WO2006014955A2/fr
Publication of WO2006014955A3 publication Critical patent/WO2006014955A3/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04N—PICTORIAL COMMUNICATION, e.g. TELEVISION
    • H04N5/00—Details of television systems
    • H04N5/76—Television signal recording
    • H04N5/78—Television signal recording using magnetic recording
    • H04N5/782—Television signal recording using magnetic recording on tape

Definitions

  • the present invention relates to a method and system for providing status information for scheduled recordings.
  • the standards include methods and systems that facilitate a common communication scheme between a variety of electronic devices.
  • 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.
  • a scheduled recording service 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.
  • 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
  • Figure 2 is a dataflow diagram illustrating functions and dataflow of the scheduled recording service according to the present invention.
  • Figure 3 is a sequence diagram illustrating an exemplary sequence of steps performed by the system
  • Figure 4 is a state diagram illustrating a first embodiment of record task states
  • Figure 5 is a state diagram illustrating a first embodiment of record schedule states
  • Figure 6 is a state diagram illustrating a second embodiment of record task states
  • Figure 7 is a state diagram illustrating a second embodiment of record schedule states
  • 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.
  • FIG. 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.
  • the devices communicate in accordance with the Universal Plug and Play (UPnP) protocol.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • FIG. 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.
  • a user initiates a request to record a program or a series of programs to CP 14.
  • 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.
  • a user of the system may initiate a request for status of the scheduled recording in step 36.
  • 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.
  • 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.
  • a record task can transition to a fully recorded state 44, a not recorded state 46 or a partially recorded state 48.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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).
  • the following list is not exclusive. Additional status properties may be added to accommodate the needs of various recording devices.
  • 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 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.
  • 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.
  • CSV comma separated variable
  • 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.
  • 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.”
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • FIG. 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • FIG. 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.
  • 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.
  • the record schedule transitions 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • FIG. 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.

Landscapes

  • Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Signal Processing (AREA)
  • Signal Processing For Digital Recording And Reproducing (AREA)
  • Debugging And Monitoring (AREA)

Abstract

L'invention concerne un service d'enregistrements programmés permettant de faire un rapport d'un état de dispositif d'enregistrement, qui met en oeuvre un ensemble de règles définissant différents états de fonctionnement pour ledit dispositif d'enregistrement en relation avec une tâche d'enregistrement. Une fonction d'état de tâche est conçue pour recevoir des informations d'état pour une tâche d'enregistrement particulière du dispositif d'enregistrement et fonctionne afin de déterminer l'état de fonctionnement courant pour la tâche d'enregistrement particulière en fonction de l'ensemble de règles. Une fonction de rapport communique par données avec la fonction d'état de tâche et fonctionne afin d'exposer les propriétés associées à la tâche d'enregistrement particulière en fonction de l'état de fonctionnement courant.
PCT/US2005/026490 2004-07-27 2005-07-27 Machine d'etat pour enregistrements programmes WO2006014955A2 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US59142204P 2004-07-27 2004-07-27
US60/591,422 2004-07-27

Publications (2)

Publication Number Publication Date
WO2006014955A2 true WO2006014955A2 (fr) 2006-02-09
WO2006014955A3 WO2006014955A3 (fr) 2006-05-18

Family

ID=35787770

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2005/026490 WO2006014955A2 (fr) 2004-07-27 2005-07-27 Machine d'etat pour enregistrements programmes

Country Status (1)

Country Link
WO (1) WO2006014955A2 (fr)

Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5206736A (en) * 1990-09-28 1993-04-27 Xerox Corporation Font storage management and control
US5274772A (en) * 1989-06-28 1993-12-28 International Business Machines Corporation Data processing systems having means for selectively combining records into signal blocks for recording in a record medium
US5293566A (en) * 1990-08-28 1994-03-08 Matsushita Electric Industrial Co., Ltd. Information recording and reproducing apparatus
US6052145A (en) * 1995-01-05 2000-04-18 Gemstar Development Corporation System and method for controlling the broadcast and recording of television programs and for distributing information to be displayed on a television screen
US20020174433A1 (en) * 2001-03-22 2002-11-21 Baumgartner Joseph P. Personal video recorder systems and methods
US20030067554A1 (en) * 2000-09-25 2003-04-10 Klarfeld Kenneth A. System and method for personalized TV
US20050086635A1 (en) * 2003-10-20 2005-04-21 Pegasus Technologies, Inc. Visual programming system and method

Patent Citations (7)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US5274772A (en) * 1989-06-28 1993-12-28 International Business Machines Corporation Data processing systems having means for selectively combining records into signal blocks for recording in a record medium
US5293566A (en) * 1990-08-28 1994-03-08 Matsushita Electric Industrial Co., Ltd. Information recording and reproducing apparatus
US5206736A (en) * 1990-09-28 1993-04-27 Xerox Corporation Font storage management and control
US6052145A (en) * 1995-01-05 2000-04-18 Gemstar Development Corporation System and method for controlling the broadcast and recording of television programs and for distributing information to be displayed on a television screen
US20030067554A1 (en) * 2000-09-25 2003-04-10 Klarfeld Kenneth A. System and method for personalized TV
US20020174433A1 (en) * 2001-03-22 2002-11-21 Baumgartner Joseph P. Personal video recorder systems and methods
US20050086635A1 (en) * 2003-10-20 2005-04-21 Pegasus Technologies, Inc. Visual programming system and method

Also Published As

Publication number Publication date
WO2006014955A3 (fr) 2006-05-18

Similar Documents

Publication Publication Date Title
US7454199B2 (en) System and method for temporary application component deletion and reload on a wireless device
EP1160665B1 (fr) Méthode, appareil et dispositif d'enregistrement pour traitement d'information
US20100262960A1 (en) Communication Terminal
US8640150B2 (en) Information processing terminal, information processing method, and program product
US20230004381A1 (en) Software version rollback method, apparatus, and system
EP0758466A1 (fr) Procede permettant de fournir a un dispositif principal des informations de capacites de dispositif asservi
JP2004227143A (ja) 情報処理装置および情報処理方法
CN1696910B (zh) 用于对软件打补丁的方法和系统
EP1881675A1 (fr) Système et procédé de gestion d'une pluralité de services web
CN101526983A (zh) 许可管理系统以及许可管理方法
CN112199106B (zh) 一种跨版本升级方法、装置及电子设备
WO2006014955A2 (fr) Machine d'etat pour enregistrements programmes
CN110308914B (zh) 升级处理方法、装置、设备、系统及计算机可读存储介质
CN101931552B (zh) 管理装置
CN107562440B (zh) 一种eeprom版本更新方法及装置
CN112214502B (zh) 一种联盟链的用户合约部署方法、装置、系统及存储介质
US8117053B2 (en) Claims based factory pattern for creating objects
US7171465B1 (en) Method for determining a server computer which carried out a process most recently, and high availability computer system
JP3145992B2 (ja) 交換制御サービス論理の競合制御方式及び競合制御方法
JP3961301B2 (ja) デジタル機器、タスク管理方法及びそのプログラム
JP4666231B2 (ja) アプリケーション競合管理システム及びその方法並びにそれを用いた情報処理端末
KR20070088889A (ko) 네트워크 상에서의 데이터 백업 방법
US7984433B2 (en) Program distribution method and computer system
CN107800677A (zh) 用于提供自适应连接服务的装置和方法
JP3775608B2 (ja) ソフトウェアの定義パラメタ設定方法

Legal Events

Date Code Title Description
AK Designated states

Kind code of ref document: A2

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

AL Designated countries for regional patents

Kind code of ref document: A2

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

NENP Non-entry into the national phase in:

Ref country code: DE

121 Ep: the epo has been informed by wipo that ep was designated in this application
122 Ep: pct application non-entry in european phase