US8385718B1 - Process for programming actions of resources in a domestic communication network - Google Patents

Process for programming actions of resources in a domestic communication network Download PDF

Info

Publication number
US8385718B1
US8385718B1 US09/719,182 US71918299A US8385718B1 US 8385718 B1 US8385718 B1 US 8385718B1 US 71918299 A US71918299 A US 71918299A US 8385718 B1 US8385718 B1 US 8385718B1
Authority
US
United States
Prior art keywords
action
manager
preprogrammed
resources
process according
Prior art date
Legal status (The legal status 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 status listed.)
Expired - Fee Related
Application number
US09/719,182
Other languages
English (en)
Inventor
Fabienne Coez
Nicolas Fannechère
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
InterDigital CE Patent Holdings SAS
Original Assignee
Thomson Licensing SAS
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 Thomson Licensing SAS filed Critical Thomson Licensing SAS
Assigned to THOMSON MULTIMEDIA reassignment THOMSON MULTIMEDIA ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: COEZ, FABIENNE, FANNECHERE, NICOLAS
Application granted granted Critical
Publication of US8385718B1 publication Critical patent/US8385718B1/en
Anticipated expiration legal-status Critical
Assigned to THOMSON LICENSING reassignment THOMSON LICENSING CHANGE OF NAME (SEE DOCUMENT FOR DETAILS). Assignors: THOMSON LICENSING S.A.
Assigned to INTERDIGITAL CE PATENT HOLDINGS reassignment INTERDIGITAL CE PATENT HOLDINGS ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: THOMSON LICENSING
Assigned to THOMSON LICENSING S.A. reassignment THOMSON LICENSING S.A. ASSIGNMENT OF ASSIGNORS INTEREST (SEE DOCUMENT FOR DETAILS). Assignors: THOMSON MULTIMEDIA S.A.
Expired - Fee Related legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/40—Bus networks
    • H04L12/40052—High-speed IEEE 1394 serial bus
    • H04L12/40117—Interconnection of audio or video/imaging devices
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04B—TRANSMISSION
    • H04B1/00—Details of transmission systems, not covered by a single one of groups H04B3/00 - H04B13/00; Details of transmission systems not characterised by the medium used for transmission
    • H04B1/06—Receivers
    • H04B1/16—Circuits
    • H04B1/20—Circuits for coupling gramophone pick-up, recorder output, or microphone to receiver
    • H04B1/205—Circuits for coupling gramophone pick-up, recorder output, or microphone to receiver with control bus for exchanging commands between units
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2803—Home automation networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2803—Home automation networks
    • H04L12/2805—Home Audio Video Interoperability [HAVI] networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2803—Home automation networks
    • H04L12/2807—Exchanging configuration information on appliance services in a home automation network
    • H04L12/2814—Exchanging control software or macros for controlling appliance services in a home automation network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2803—Home automation networks
    • H04L12/2807—Exchanging configuration information on appliance services in a home automation network
    • H04L12/2809—Exchanging configuration information on appliance services in a home automation network indicating that an appliance service is present in a home automation network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2803—Home automation networks
    • H04L2012/2847—Home automation networks characterised by the type of home appliance used
    • H04L2012/2849—Audio/video appliances

Definitions

  • the invention relates to a process for programming actions of resources, that is to say of facilities of devices, in a domestic communication network, in particular a network which includes an IEEE 1394-1995 serial bus.
  • a user ought to have the possibility of programming an action to be performed by one of the devices from any device possessing a display.
  • any recording device for example a video recorder, from any television set or other display means linked to the network.
  • the invention relates to a process for programming actions of resources in a network of domestic devices, characterized in that it includes the steps of:
  • the client application selects a preprogrammed action manager situated in a device other than the client application itself.
  • the process includes the step of storage by each resource involved of its agenda with respect to the action.
  • the verification step comprises a request of the preprogrammed actions manager from each resource involved aimed at ascertaining the availability of the resources involved by way of their respective agendas.
  • the preprogrammed actions manager performs the following tasks:
  • FIG. 1 is a diagram of part of a domestic network representing the manner of operation according to the first exemplary embodiment
  • FIG. 2 is a diagram of part of a domestic network representing the manner of operation according to the second exemplary embodiment
  • FIG. 3 is a schematic representing data exchanges according to the first exemplary embodiment
  • FIG. 4 is a schematic representing data exchanges according to the second exemplary embodiment.
  • the present description relates to a domestic network based on a serial bus conforming to IEEE 1394-1995, as well as on the architecture referred to as the ‘HAVi’ architecture, defined in the document ‘The HAVi Architecture—Specification of the Home Audio/Video interoperability Architecture’ dated 11 May 1998, version 0.8, published on 15 May 1998 on the Internet sites of the Sony, Hitachi, Toshiba, Philips and Sharp companies.
  • a new version of the HAVi document (version 1.0beta+) has been published between the priority date and the date of filing of the present patent application.
  • the first patent application relates to the implementation of registries of objects or of resources in the devices connected to the network, this registry maintaining an up-to-date list of resources or software modules available at local level in a device, whilst the second patent application concerns a resource manager which manages the resource reservation for resources available locally and participates in resolving conflicts of access to—or of reservation of—these resources.
  • an application may require access to public resources.
  • public resources is understood within the present context to mean facilities of devices other than the device in which the application is being executed, but which are potentially accessible by this application.
  • An application can itself be a resource.
  • the registries mentioned above maintain an up-to-date list of the public resources available, and an application can determine which these resources are by despatching a request at the level of its local registry, which can propagate this request to the other registries.
  • the designation ‘software module’ (to use the terminology of the HAVi document) denotes applications, resources and services of a device.
  • the target is for example the recording facility of a digital recording device (digital video recorder, DVD, etc) whilst a resource involved is a tuner.
  • Other resources may be required: for example a transcoder, required to translate the format of the data into the format of the recording device, an access control service for authorizing access to secure programmes, etc.
  • the target does or does not accept the action requested by the application.
  • the target When programming this action, the target must identify the resources required for the accomplishment of the action and reserve them for the requisite period of time.
  • the target and the resources involved must synchronize themselves. The consequence of this is that information relating to the preprogrammed action has to be stored in the network. According to the first exemplary embodiment, it is the target which stores this information and executes the action, whilst, according to a second embodiment, it is another module which will be responsible for these functions.
  • a preprogrammed action can be defined by a certain number of items of information, collected in a particular data structure filled in by the application programming the action and stored by the target resource.
  • the type of the action depends on the nature of the target.
  • the action can be ‘RECORD’ or ‘READ’ for a resource having a mass memory facility, or ‘SELECT_SERVICE’ for a digital television demultiplexer.
  • the parameters which depend on the action to be performed, serve to define the action in a more specific manner at the level of each resource.
  • a parameter can be an event or a service within the meaning of the DVB digital video broadcast standard.
  • the parameters will comprise an identifier of the type of parameter, followed by the value of the parameter.
  • Certain devices of the network may not include processing means for providing a service of this level.
  • a recording device may not accept parameters after a ‘RECORD’ command, since it is not itself able to control a tuner, whilst a more complex device, having this possibility, will be able to accept a command of the type ‘RECORD service X’.
  • the date, the start and end times and the periodicity of the action are conventional information.
  • the identifier of the target resource is required so that an application can modify an already-programmed action. This field is not required if the target stores the preprogrammed action directly (i.e. if this resource is itself the main resource of a programmed action).
  • an application wishes to ascertain which programmed action is associated with a given resource, it will ask this resource for the identifiers of each of the programmed actions in which this resource is involved. The application will then be able to consult the data structure of the programmed action which it has chosen, then will be able to modify it (this application may for example be that of a user interface, possibly controlled by a user other than the one who programmed the action which will be modified).
  • the identifiers of the resources involved are used, according to the first exemplary embodiment, by the target.
  • the list allows the target to request information relating to the resources involved, for example by way of the registries, or by transmitting messages to them directly.
  • the user data include for example in plain text the motive for the action, this possibly being important in the case of conflict with an action programmed earlier. In this case, when the conflict must be resolved by a user, typically the one programming the most recent action, these data may afford him indications as to the importance of the action.
  • the resources involved contacted by the target resource will themselves also have to store some of the content of the above data structure: the information relating to the time and, possibly, the type of action, the parameters and the user data.
  • the first exemplary embodiment is illustrated by FIG. 1 .
  • the network part represented by this figure comprises five devices.
  • Device 1 is a television set, located in a kitchen and comprising an application 2 (for example a user interface allowing the programming of all the devices of the network).
  • Device 3 is also a television set, this time situated in the bedroom and furnished with an application 4 , similar to the application 2 .
  • the device 5 is a digital satellite television decoder comprising a tuner resource 6 and a resource manager 7
  • the device 8 is a DVD-type digital recording device, in this regard comprising the recording resource 9 and a resource manager 10 .
  • the device 11 is for example another decoder, which possesses a facility for transcoding the audio/video data coded according to a first format (that of the decoder 5 ) into a second format (that of the recording device 8 ).
  • the device 11 consequently possesses a transcoding resource 12 and a resource manager 13 .
  • the various devices, which can comprise software modules other than those illustrated, are linked by a serial bus 14 , for example an IEEE 1394-1995 bus.
  • the target resource in the present case the recording function of the device 8 , itself incorporates an application capable of managing the recording action.
  • a user wishes to record a transmission on a service X, at 20.30, on 12 Dec. 1999, for a duration of two hours.
  • a single resource of tuner type and a single resource of transcoding type exist in the network, the user could, in a network where several resources of the same type coexist, choose from among several resources of the same type of the network that which he prefers to participate in the execution of the action.
  • the target resource 9 When the target resource 9 receives the programmed action from the application 2 , it performs an auto-reservation with the local resource manager 10 , by proceeding in the manner described in the second patent application mentioned at the start of this description. Moreover, it performs the reservation of the resources involved (tuner 6 , transcoder 12 ) with the remote resource managers (managers 7 , 13 respectively). Each resource manager stores the data relating to the reservation of the resources associated therewith (that is to say of the resources having the same execution platform as this resource manager).
  • the target transmits a confirmation message to the application 2 from which the action originated.
  • each resource manager advises the target which programmed the first action by an appropriate message.
  • each resource manager stores the identifier or the address of the software module which has made a reservation.
  • the preprogrammed action will nevertheless be executed, since all the information relating to the action is stored at the level of the target.
  • a user can modify or delete the preprogrammed action from another application, such as the application 4 .
  • the application 4 wants to access all the programmed actions concerning a given resource (which is found by way of the local registry of the application), the resource contacted by the application can give the identifiers of the main resources of each of the programmed actions in which it is involved. The entire data structure describing the programmed action can thereafter be retrieved by contacting each main resource directly.
  • connection manager or ‘SM’ standing for ‘Stream Manager’ according to the terminology of the HAVi document.
  • a resource can be designated under the terms function component manager (‘FCM’ according to the HAVi terminology).
  • FCM function component manager
  • the architecture can then be represented by the diagram of FIG. 3 , where an application transmits an action programming to the application programming interface forming part of the target.
  • resources other than FCMs exist within the HAVi framework.
  • DCM Downlink Control Manager
  • another type of resource exists, referred to as the ‘DCM’ standing for ‘Device Control Manager’ or alternatively device control manager.
  • an FCM is the software representation of a function of a device
  • a DCM is the software representation of a device and can incorporate several FCMs in this regard.
  • a DCM is then an intermediary between a main application making a reservation and one or more FCMs contained in the DCM.
  • the second exemplary embodiment is illustrated by FIG. 2 . It is assumed here that resources do not incorporate applications capable of managing the preprogrammed actions as in the first exemplary embodiment. One will speak in this case of ‘passive resources’. The latter may however store some of these data (for example the timetables for the actions which they must perform and possibly parameters and user data), as indicated in the first exemplary embodiment.
  • the client application 15 initiating the programming of the action is as in the first example an interface localized within a television set 16 .
  • the recording device 17 includes the digital recording resource 18 , another resource 19 , and a resource manager 20 .
  • the device 5 is identical to that of FIG. 1 .
  • the device 17 also includes a preprogrammed actions manager 21 (‘PAM’).
  • PAM preprogrammed actions manager 21
  • This actions manager 21 is a service within the meaning of the HAVi document and makes all the reservations required for the accomplishment of the action.
  • the preprogrammed actions manager manages the preprogrammed actions
  • the resource manager manages the reservations corresponding to the actions and any conflicts which may ensue.
  • These two functions can be incoporated into one and the same software object, as indicated in FIG. 2 .
  • the separate representation of the PAM and of the RM is used simply for the sake of consistency with the first exemplary embodiment, where these functions were implemented by distinct objects.
  • the actions manager 21 manages the passive resources of the device 17 , and also of the device 5 .
  • the implementation of a preprogrammed action according to the second exemplary embodiment involves:
  • a transcoder required to translate the format of the data into the format of the recording device, an access control service for authorizing access to secure programmes, etc.
  • the preprogrammed actions manager does or does not accept the action requested by the client application.
  • the latter has previously identified the resources required for the accomplishment of the action, the commands to be performed at the start time of the action and the connections required between the various resources which need to be established before the start time of the action.
  • the PAM stores all these data of the action, and returns an identifier of the action to the client application.
  • each resource involved stores its own agenda as to the actions to be performed. This agenda includes in particular the timetables of the reservations, but not the commands and connections related to the actions. This would necessitate too much memory room.
  • each resource can inform other PAMs instigating actions of its availability or unavailability for these actions.
  • the PAM Before accepting or rejecting a request for action, the PAM interrogates each resource so as to ascertain whether it is available between the start and end times of the action. At the start time of the action, if all the resources are present, the PAM reserves the resources (here, this entails reservation proper, as compared with simple agenda indications programmed previously), establishes the necessary connections and instigates the commands. The establishing of the connections is requested of the local software module referred to as the connections manager (or ‘SM’ or ‘Stream Manager’ according to the terminology of the HAVi document).
  • the connections manager or ‘SM’ or ‘Stream Manager’ according to the terminology of the HAVi document.
  • a preprogrammed action can be defined by a number of information items, collected in a particular data structure filled in by the application programming the action and stored according to the second exemplary embodiment by the preprogrammed actions manager.
  • an application wants to ascertain which preprogrammed action is associated with a given resource, it can consult all the programmed actions which are recorded in a PAM. It could also request from the resource the identifiers of each of the preprogrammed actions in which this resource is involved. It can therefore retrieve the identifier of the PAM which maintains the data of a given preprogrammed action.
  • An application also has the possibility of cancelling a preprogrammed action, or of modifying such an action, at the PAM in charge of this action.
  • the identifiers of the resources involved are used according to the second exemplary embodiment by the PAM.
  • the list enables the PAM to request information relating to the resources involved, for example by way of the registries, or by transmitting messages directly to them.
  • the PAM distributes the preprogrammed action to the device control managers (DCM—see hereinbelow) of the resources involved, with all the parameters required for each resource.
  • DCM device control managers
  • the resources are capable of honoring the request, they advise the PAM of this, the latter returning an identifier of the action to the client application to signal to it that the action has been taken on board.
  • the PAM refuses the preprogrammed action, transmitting an appropriate message to the client application.
  • the PAM advises the client application which programmed the action by an appropriate message.
  • each PAM stores the identifier or the address of the application which has made a reservation.
  • a resource can be designated under the terms function component manager (‘FCM’ according to the HAVi terminology).
  • FCM function component manager
  • the architecture can then be represented by the diagram of FIG. 3 , where an application transmits an action programming to the application programming interface forming part of the target.
  • DCM Downlink Control Manager
  • FCM Function of a device
  • DCM Device Control Manager
  • a DCM is then an intermediary between a main application making a reservation and one or more FCMs contained in the DCM.
  • FIG. 4 is a simplified diagram of the principle of the second embodiment.
  • an application addresses itself to the preprogrammed actions manager, which is necessarily present in the device comprising the target resource.
  • the application acts through the programming interface of the actions manager, which in turn acts through the programming interface of the target.
  • the device comprising the manager and the target is either a device with full facilities (‘FAV’), or a device with intermediate facilities (‘IAV’).

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Automation & Control Theory (AREA)
  • Multimedia (AREA)
  • Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)
  • Computer And Data Communications (AREA)
  • Small-Scale Networks (AREA)
  • Selective Calling Equipment (AREA)
US09/719,182 1998-06-08 1999-06-08 Process for programming actions of resources in a domestic communication network Expired - Fee Related US8385718B1 (en)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
FR9807187 1998-06-08
FR9807187A FR2779596B1 (fr) 1998-06-08 1998-06-08 Procede de programmation d'actions de ressources dans un reseau de communication domestique
PCT/FR1999/001357 WO1999065189A1 (fr) 1998-06-08 1999-06-08 Procede de progammation d'actions de ressources dans un reseau de communication domestique

Publications (1)

Publication Number Publication Date
US8385718B1 true US8385718B1 (en) 2013-02-26

Family

ID=9527141

Family Applications (1)

Application Number Title Priority Date Filing Date
US09/719,182 Expired - Fee Related US8385718B1 (en) 1998-06-08 1999-06-08 Process for programming actions of resources in a domestic communication network

Country Status (11)

Country Link
US (1) US8385718B1 (fr)
EP (1) EP1095486B1 (fr)
JP (1) JP4647097B2 (fr)
KR (1) KR100689115B1 (fr)
CN (1) CN1166121C (fr)
AU (1) AU4268699A (fr)
DE (1) DE69930663T2 (fr)
ES (1) ES2260942T3 (fr)
FR (1) FR2779596B1 (fr)
PL (1) PL344692A1 (fr)
WO (1) WO1999065189A1 (fr)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
MXPA02011023A (es) * 2000-05-12 2003-03-10 Thomson Licensing Sa Aparato y metodo para la interoperabilidad mejorada de dispositivos.

Citations (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4855730A (en) * 1987-05-08 1989-08-08 Rca Licensing Corporation Component audio/video system with timed control of plural peripheral devices
US5065392A (en) * 1990-04-10 1991-11-12 Dsc Communications Corporation Network controller scheduling system and method of operation
EP0535749A2 (fr) 1991-10-04 1993-04-07 D2B Systems Co. Ltd. Système de bus de communication local et appareils utilisés dans un tel système
JPH06261139A (ja) 1993-01-08 1994-09-16 Sony Corp Ａｖ機器制御システム
JPH0856352A (ja) 1994-08-11 1996-02-27 Matsushita Electric Ind Co Ltd ビデオファイルサーバ及び録画制御装置
JPH09233567A (ja) 1996-02-22 1997-09-05 Sharp Corp インテリジェントリモコン装置
US5890003A (en) * 1988-12-09 1999-03-30 Tandem Computers Incorporated Interrupts between asynchronously operating CPUs in fault tolerant computer system
US6018816A (en) * 1997-04-04 2000-01-25 Canon Kabushiki Kaisha Information processing system and method, image processing system and method, information processing apparatus and computer readable memory
US6108739A (en) * 1996-08-29 2000-08-22 Apple Computer, Inc. Method and system for avoiding starvation and deadlocks in a split-response interconnect of a computer system
US6138221A (en) * 1996-12-23 2000-10-24 U.S. Philips Corporation Method and system for supplying streams of data having identical maximum consumption rate in a storage medium
US6298370B1 (en) * 1997-04-04 2001-10-02 Texas Instruments Incorporated Computer operating process allocating tasks between first and second processors at run time based upon current processor load
US20010037423A1 (en) * 1997-06-20 2001-11-01 National Instruments Corporation System and method for coupling peripheral buses through a serial bus using a split bridge implementation
US6353898B1 (en) * 1997-02-21 2002-03-05 Novell, Inc. Resource management in a clustered computer system
US20040133793A1 (en) * 1995-02-13 2004-07-08 Intertrust Technologies Corp. Systems and methods for secure transaction management and electronic rights protection
US6931430B1 (en) * 1998-05-13 2005-08-16 Thomas W. Lynch Maintaining coherency in a symbiotic computing system and method of operation thereof

Patent Citations (15)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US4855730A (en) * 1987-05-08 1989-08-08 Rca Licensing Corporation Component audio/video system with timed control of plural peripheral devices
US5890003A (en) * 1988-12-09 1999-03-30 Tandem Computers Incorporated Interrupts between asynchronously operating CPUs in fault tolerant computer system
US5065392A (en) * 1990-04-10 1991-11-12 Dsc Communications Corporation Network controller scheduling system and method of operation
EP0535749A2 (fr) 1991-10-04 1993-04-07 D2B Systems Co. Ltd. Système de bus de communication local et appareils utilisés dans un tel système
JPH06261139A (ja) 1993-01-08 1994-09-16 Sony Corp Ａｖ機器制御システム
JPH0856352A (ja) 1994-08-11 1996-02-27 Matsushita Electric Ind Co Ltd ビデオファイルサーバ及び録画制御装置
US20040133793A1 (en) * 1995-02-13 2004-07-08 Intertrust Technologies Corp. Systems and methods for secure transaction management and electronic rights protection
JPH09233567A (ja) 1996-02-22 1997-09-05 Sharp Corp インテリジェントリモコン装置
US6108739A (en) * 1996-08-29 2000-08-22 Apple Computer, Inc. Method and system for avoiding starvation and deadlocks in a split-response interconnect of a computer system
US6138221A (en) * 1996-12-23 2000-10-24 U.S. Philips Corporation Method and system for supplying streams of data having identical maximum consumption rate in a storage medium
US6353898B1 (en) * 1997-02-21 2002-03-05 Novell, Inc. Resource management in a clustered computer system
US6018816A (en) * 1997-04-04 2000-01-25 Canon Kabushiki Kaisha Information processing system and method, image processing system and method, information processing apparatus and computer readable memory
US6298370B1 (en) * 1997-04-04 2001-10-02 Texas Instruments Incorporated Computer operating process allocating tasks between first and second processors at run time based upon current processor load
US20010037423A1 (en) * 1997-06-20 2001-11-01 National Instruments Corporation System and method for coupling peripheral buses through a serial bus using a split bridge implementation
US6931430B1 (en) * 1998-05-13 2005-08-16 Thomas W. Lynch Maintaining coherency in a symbiotic computing system and method of operation thereof

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
"Audio Und Video Im Heim-Netzwerk", Funkschau, vol. 63, No. 6, Mar. 8, 1991, pp. 74, 76, 78-79.

Also Published As

Publication number Publication date
EP1095486A1 (fr) 2001-05-02
KR100689115B1 (ko) 2007-03-08
ES2260942T3 (es) 2006-11-01
FR2779596A1 (fr) 1999-12-10
JP2002518718A (ja) 2002-06-25
WO1999065189A1 (fr) 1999-12-16
CN1304607A (zh) 2001-07-18
JP4647097B2 (ja) 2011-03-09
DE69930663T2 (de) 2006-11-09
PL344692A1 (en) 2001-11-19
AU4268699A (en) 1999-12-30
DE69930663D1 (de) 2006-05-18
CN1166121C (zh) 2004-09-08
KR20010052667A (ko) 2001-06-25
EP1095486B1 (fr) 2006-03-29
FR2779596B1 (fr) 2000-07-21

Similar Documents

Publication Publication Date Title
US8607280B2 (en) Resource and capability borrowing
CN100380888C (zh) 控制网络环境内部的自主媒体设备和管理设备之间的数据的流和格式的媒体管理器
US6763391B1 (en) Method and apparatus for managing resource allocation and a bandwidth overflow in a cooperative, distributed computing environment
EP1571803B1 (fr) Méthode de contrôle d'information-disposition, système de reproduction de l'information, et dispositif d'information-disposition
US6600868B2 (en) Information processing system, information processing method, and recording medium
CN100521636C (zh) 在URI中嵌入UPnP AV媒体服务器的对象ID
JP4309087B2 (ja) ネットワーク接続機器およびこれを用いたネットワークシステム
CN100527681C (zh) 管理网络上的内容的方法和设备
CN1825823B (zh) 家庭网络的业务框架
JP2002506552A (ja) 消費者電子システムの機能の管理
US20010026533A1 (en) Method to perform a scheduled action of network devices
US20110185391A1 (en) Systems and methods for connecting networked devices
JP2002518885A (ja) 家庭内ネットワークにおける通信方法、かかる方法を実施するためのネットワーク及び機器
CN101091353A (zh) 在xht网络中提供差错信息的设备、系统和方法
US8385718B1 (en) Process for programming actions of resources in a domestic communication network
WO2000059158A2 (fr) Procede et systeme d'acheminement
JP2003046958A (ja) ビデオデータ格納装置及びビデオデータ取得装置
JP4838935B2 (ja) 通信ネットワーク内でオブジェクトを管理する処理及び装置
WO2000002337A1 (fr) Reservation de largeur de bande
JP2004207864A (ja) 電子番組ガイド画面生成装置、電子番組ガイド画面生成方法、デバイス／機能予約装置、デバイス／機能予約方法、デジタル放送受信システム、プログラム及び記録媒体
MXPA00012221A (en) Method for programming resource actions in a domestic communication network
JP4075552B2 (ja) 放送番組録画予約システム、放送番組録画装置、及び放送番組録画用プログラム
JP2009177673A (ja) テレビ番組リモート録画システム、方法、およびプログラム
CN101060438B (zh) 同步多内容目录服务的方法和内容目录服务系统
MXPA00012213A (en) Domestic system resource access priority management method and device for the implementation thereof

Legal Events

Date Code Title Description
AS Assignment

Owner name: THOMSON MULTIMEDIA, FRANCE

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:COEZ, FABIENNE;FANNECHERE, NICOLAS;SIGNING DATES FROM 20010205 TO 20010211;REEL/FRAME:011619/0073

STCF Information on status: patent grant

Free format text: PATENTED CASE

FPAY Fee payment

Year of fee payment: 4

AS Assignment

Owner name: THOMSON LICENSING, FRANCE

Free format text: CHANGE OF NAME;ASSIGNOR:THOMSON LICENSING S.A.;REEL/FRAME:049605/0842

Effective date: 20050726

Owner name: INTERDIGITAL CE PATENT HOLDINGS, FRANCE

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:THOMSON LICENSING;REEL/FRAME:049606/0001

Effective date: 20180730

AS Assignment

Owner name: THOMSON LICENSING S.A., FRANCE

Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:THOMSON MULTIMEDIA S.A.;REEL/FRAME:050262/0460

Effective date: 20010629

FEPP Fee payment procedure

Free format text: MAINTENANCE FEE REMINDER MAILED (ORIGINAL EVENT CODE: REM.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

LAPS Lapse for failure to pay maintenance fees

Free format text: PATENT EXPIRED FOR FAILURE TO PAY MAINTENANCE FEES (ORIGINAL EVENT CODE: EXP.); ENTITY STATUS OF PATENT OWNER: LARGE ENTITY

STCH Information on status: patent discontinuation

Free format text: PATENT EXPIRED DUE TO NONPAYMENT OF MAINTENANCE FEES UNDER 37 CFR 1.362

FP Lapsed due to failure to pay maintenance fee

Effective date: 20210226