WO2007109551A2 - Automatisation de dispositif par commande de dispositif réseauté doté de services d'assistance web pour une pile de dispositifs - Google Patents

Automatisation de dispositif par commande de dispositif réseauté doté de services d'assistance web pour une pile de dispositifs Download PDF

Info

Publication number
WO2007109551A2
WO2007109551A2 PCT/US2007/064188 US2007064188W WO2007109551A2 WO 2007109551 A2 WO2007109551 A2 WO 2007109551A2 US 2007064188 W US2007064188 W US 2007064188W WO 2007109551 A2 WO2007109551 A2 WO 2007109551A2
Authority
WO
WIPO (PCT)
Prior art keywords
automation
web services
devices
protocol
client
Prior art date
Application number
PCT/US2007/064188
Other languages
English (en)
Other versions
WO2007109551A3 (fr
Inventor
Seale Moorer
Eric Eichensehr
Original Assignee
Exceptional Innovation, Llc
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Priority claimed from US11/686,846 external-priority patent/US7587464B2/en
Application filed by Exceptional Innovation, Llc filed Critical Exceptional Innovation, Llc
Publication of WO2007109551A2 publication Critical patent/WO2007109551A2/fr
Publication of WO2007109551A3 publication Critical patent/WO2007109551A3/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2803—Home automation networks
    • H04L12/2816—Controlling appliance services of a home automation network by calling their functionalities
    • H04L12/2818—Controlling appliance services of a home automation network by calling their functionalities from a device located outside both the home and the home network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L12/00—Data switching networks
    • H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
    • H04L12/2803—Home automation networks
    • H04L12/2816—Controlling appliance services of a home automation network by calling their functionalities
    • H04L12/282—Controlling appliance services of a home automation network by calling their functionalities based on user interaction within the home
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04M—TELEPHONIC COMMUNICATION
    • H04M11/00—Telephonic communication systems specially adapted for combination with other electrical systems
    • H04M11/02—Telephonic communication systems specially adapted for combination with other electrical systems with bell or annunciator systems
    • H04M11/025—Door telephones

Definitions

  • the invention is directed to multiple device control and convergence, and more particularly to multiple device addressing, discovery, description, control, eventing, and convergence in a Web Service environment of automations components that are for use in an automation environment.
  • CD/DVD player Household, academic and/or business spaces now more commonly have more than one audio or video device such as CD/DVD player, portable MP3 player, tuner, preamp, power amp, speakers, VCR, DVR, computers running media players or connected to some other source of audio or video (e.g., Internet radio, satellite radio and the like), etc.
  • a CD/DVD player from one company comes with its own remote control and an amplifier by an entirely different company comes with its own remote control.
  • the same space may have a PC with its keyboard and mouse, and yet another company's portable MP3 player with its own control switches.
  • each audio device While each audio device is doing precisely what it was designed to do, each operates completely independent from the others with the possible exception of the portable MP3 player that may be connected to a PC for synchronization. As a result, a user ends up going from one keypad to another or juggling a series of remote controls in order to control the devices.
  • these audio/video and similar devices are not designed to communicate with each other or their communication is very limited, access to these audio/video devices is limited by their physical locations. For example, it is difficult to play an MP3 file saved in a PC hard disk drive in one room or area (a child's bedroom) on speakers located in another room or area (an entertainment room). Thus, in order for a user to enjoy music of his or her choice whenever and wherever he or she wants, each room needs to be equipped with all the necessary audio/video equipment and digital audio/video content.
  • the audio/video devices are not designed to communicate with other devices (e.g., TV, lighting, security system, etc.).
  • other devices e.g., TV, lighting, security system, etc.
  • the user in order to watch a movie, the user must turn on a TV, a DVD player and an audio amplifier by using three different remote controls. Then the user must set the TV to receive a video signal from the DVD player, set the audio amplifier to receive an audio signal from the DVD player and use another control unit to adjust the lighting of the room.
  • Even when a user utilizes a universal remote as is known in the art, the result is a plurality of devices that are separately operated and are operated separately from a single universal remote. These devices do not converge as described above because the devices lack any ability to easily connect and effectively communicate with each other.
  • the invention meets the foregoing needs using an automation specific IP based automation protocol, which results in a significant increase in discovery and communications between devices and other advantages apparent from the discussion herein.
  • a process of operating an automation system in a Web Service environment includes the steps of providing at least one automation client and at least one automation device, the at least one automation client and the at least one automation device configured with a web services for devices stack protocol, connecting a network including at least one server with the web services for devices to the at least one automation client and the at least one automation device, and transmitting automation-based control and communication between the at least one automation client and at least one automation device, wherein the at least one automation client includes one of a TV, a personal computer, a personal digital assistant, a control panel, and a game controller and the at least one automation device includes an audio system, a video system, an intercom system, a lighting system, a security system, and a HVAC system.
  • the web services for devices stack protocol may include a logical interface with the at least one automation client, and the web services for devices stack protocol may include a web service for each at least one automation device.
  • the web services for devices stack protocol may include a services tier that provides communication via at least one of HTTP and UDP wherein the communication via HTTP and UDP may include information contained in SOAP packets.
  • the web services for devices stack protocol may include a service provider configured as a generic host for web services.
  • the web services for devices stack protocol further may include an automation device bridge configured to translate commands for the automation devices.
  • the web services for devices stack protocol further may include a component configured to host multiple services, and a controller configured to communicate with the at least one automation device.
  • the controller may be configured to send feedback from the at least one automation device to the at least one automation client.
  • the web services for devices stack protocol may be configured to communicate with the at least one automation device in a native format and the native format may include at least one of HTTP, TCP, UDP, and serial protocols.
  • the web services for devices protocol may be configured to discover the at least one automation client and the discovery may include one of multicast announcements, multicast query requests, and unicast responses.
  • the web services for devices protocol may be configured for description and the description may include at least one of WS-Metadata exchange, web services description language, and simple object access protocol/XML protocol.
  • the web services for devices protocol may be configured for eventing and wherein the eventing may include at least one of web services description language for detailed events, a configuration for automation client subscription to events, and a configuration for the at least one automation device to push events to the at least one automation client.
  • a machine-readable medium including instructions stored therewith, which, when executed by a processor cause the processor to establish an automation system in a Web Service environment
  • the machine- reachable medium including instructions for providing automation-based control and communication between at least one automation client and at least one automation device, the at least one automation client and the at least one automation device configured with a web services for devices stack protocol configured to the at least one automation client and at least one automation device, and instructions for configuring a network including at least one server to be connected to the at least one automation client and the at least one automation device with the web services for devices
  • the at least one automation client includes one of a TV, a personal computer, a personal digital assistant, a control panel, and a game controller and the at least one automation device inlcludes an audio system, a video system, an intercom system, a lighting system, a security system, and a HVAC system.
  • the web services for devices stack protocol may include a logical interface with the at least one automation client, and the web services for devices stack protocol may include a web service for each at least one automation device.
  • the web services for devices stack protocol may include a services tier that provides communication via at least one of HTTP and UDP wherein the communication via HTTP and UDP may include information contained in SOAP packets.
  • the web services for devices stack protocol may include a service provider configured as a generic host for web services.
  • the web services for devices stack protocol further may include an automation device bridge configured to translate commands for the automation devices.
  • the web services for devices stack protocol further may include a component configured to host multiple services, and a controller configured to communicate with the at least one automation device.
  • the controller may be configured to send feedback from the at least one automation device to the at least one automation client.
  • the web services for devices stack protocol may be configured to communicate with the at least one automation device in a native format and the native format may include at least one of HTTP, TCP, UDP, and serial protocols.
  • the web services for devices protocol may be configured to discover the at least one automation client and the discovery may include one of multicast announcements, multicast query requests, and unicast responses.
  • the web services for devices protocol may be configured for description and the description may include at least one of WS-Metadata exchange, web services description language, and simple object access protocol/XML protocol.
  • the web services for devices protocol may be configured for eventing and wherein the eventing may include at least one of web services description language for detailed events, a configuration for automation client subscription to events, and a configuration for the at least one automation device to push events to the at least one automation client.
  • an automation system operating in a Web Service for Devices environment includes at least one automation client and at least one automation device, the at least one automation client and the at least one automation device configured with a web services for devices stack protocol configured to provide automation-based control and communication between the at least one automation client and at least one automation device, and a network including at least one server configured to be connected to the at least one automation client and the at least one automation device with the web services for devices, wherein the at least one automation client may include one of a TV, a personal computer, a personal digital assistant, a control panel, and a game controller and the at least one automation device may include an audio system, a video system, an intercom system, a lighting system, a security system, and a HVAC system.
  • the web services for devices stack protocol may include a logical interface with the at least one automation client, and the web services for devices stack protocol may include a web service for each at least one automation device.
  • the web services for devices stack protocol may include a services tier that provides communication via at least one of HTTP and UDP wherein the communication via HTTP and UDP may include information contained in SOAP packets.
  • the web services for devices stack protocol may include a service provider configured as a generic host for web services.
  • the web services for devices stack protocol further may include an automation device bridge configured to translate commands for the automation devices.
  • the web services for devices stack protocol further may include a component configured to host multiple services, and a controller configured to communicate with the at least one automation device.
  • the controller may be configured to send feedback from the at least one automation device to the at least one automation client.
  • the web services for devices stack protocol may be configured to communicate with the at least one automation device in a native format and the native format may include at least one of HTTP, TCP, UDP, and serial protocols.
  • the web services for devices protocol may be configured to discover the at least one automation client and the discovery may include one of multicast announcements, multicast query requests, and unicast responses.
  • the web services for devices protocol may be configured for description and the description may include at least one of WS-Metadata exchange, web services description language, and simple object access protocol/XML protocol.
  • the web services for devices protocol may be configured for eventing and wherein the eventing may include at least one of web services description language for detailed events, a configuration for automation client subscription to events, and a configuration for the at least one automation device to push events to the at least one automation client.
  • FIG. 2 schematically shows the web services for devices stack for use in the convergence solution of Fig. 1 , constructed according to principles of the invention;
  • Fig. 3 shows a device bridge constructed according to the principles of the invention;
  • FIG. 4 shows a controller operating according to the principles of the invention.
  • Fig. 5 shows a device life cycle operating according to the principles of the invention.
  • Fig. 1 schematically shows an overview of a convergence solution according to an embodiment of the invention.
  • the convergence solution may be a combination of hardware and software.
  • the hardware may include a server 10 connected to a network 12 (e.g. IP based wired or wireless network such as an Ethernet network) and may possibly be connected to the internet 14, devices 102 (e.g. audio 20, video 22, intercom 24, lighting 26, security system 28, HVAC 38, and the like) and clients 104 (e.g.
  • a network 12 e.g. IP based wired or wireless network such as an Ethernet network
  • devices 102 e.g. audio 20, video 22, intercom 24, lighting 26, security system 28, HVAC 38, and the like
  • clients 104 e.g.
  • the clients 104 may include a remote control 39 or a remote control may be configured to be a client 104.
  • the server 10 may be any type of computer, such as a PC connected to the network 12.
  • the clients 104 such as clients 30, 32, 34, 36 may provide a user with control over the devices 102 such as devices 20, 22, 24, 26, 28, 38.
  • the software i.e., application
  • the software enables the hardware such as the server 10, devices 102, and clients 104 to communicate with each other despite their different proprietary languages and communication protocols, and may provide the user with control over most or all the hardware from a single client.
  • the application may utilize at least one portion of the hardware to send commands to the devices 102 and receive feedback from them.
  • the application may integrate centralized device control into a PC based media environment (e.g., Microsoft Media CenterTM environment) that may store, organize and play digital media content.
  • the user may use the same remote control 39 to listen to music, watch and record television, enjoy family photographs and home movies, as well as adjust the lighting, secure the home, adjust the temperature, distribute music throughout the house, check surveillance cameras and the like.
  • the application may be implemented with Web Services.
  • Web Services use standard Internet protocol (IP) and are based on standard XML-related technologies such as SOAP (Simple Object Access Protocol) for communications and WSDL (Web Services Device Language) to describe interfaces.
  • SOAP Simple Object Access Protocol
  • WSDL Web Services Device Language
  • the devices implemented with Web Service for Device (WSD) become black boxes on the network, providing services to any application, on any platform, written in any language.
  • the server 10 or the PC 32 is running a SideShowTM enabled operating system such as Microsoft Windows VistaTM
  • the devices may be configured as a SideShowTM device or "gadget.”
  • a SideShowTM device or gadget may communicate with any client or device implemented with WSD in the network via protocols according to SideShowTM XML communication specifications.
  • the server 10 or the PC 32 using Microsoft Windows VistaTM may be running a SideShowTM gadget application running on the Microsoft Windows VistaTM computer providing a user interface rendering for the device that communicates with automation control devices via WSD technology.
  • the WSD technology may be implemented using Device Profile for Web Services (DPWS).
  • DPWS Device Profile for Web Services
  • the DPWS may be used to define how various devices may be able to use Web Services in conjunction with the convergence solution noted above.
  • the DPWS further may allow and/or ensure interoperability between the various devices 102 and the clients 104 and the like.
  • the DPWS may allow for support of resource constrained devices within the convergence solution shown in Fig. 1.
  • One benefit of DPWS is its ability to enable device and service discovery within the convergence solution of Fig. 1.
  • the DPWS may allow for and support rich eventing, an end point, and may be built on standards and WS specifications. More specifically, the end point may provide device/host metadata.
  • the DPWS specifications may include HTTP, WSDL, SOAP, WS-Discovery, WS-Addressing, WS-Eventing, WS- metadata, transfer, and the like.
  • Fig. 2 schematically shows the Web Services for Devices (WSD) Stack for use in the convergence solution of Fig. 1 , constructed according to the principles in the invention.
  • the WSD stack as referenced herein refers to the protocol architecture.
  • Fig. 2 shows the WSD Stack 200.
  • the WSD stack 200 of the invention is a particular automation software implementation of a Web Services computer networking protocol suite. The individual protocols are designed with a single purpose in mind. Because each protocol module may only communicate with two others, the modules are commonly imagined as layers in a stack of protocols. The lowest protocol always deals with "low- level," physical interaction of the hardware. Every higher layer adds more features.
  • the WSD Stack 200 allows and enables the discovery of devices in a network, such as the convergence solution of Fig. 1 and the devices on the network in a light weight, simple fashion. Using the WSD Stack 200, a device 102 in the network is able to send a message to determine what services are available enabling discovery of the device 102.
  • the WSD Stack 200 is the software that may be used to process protocols.
  • the WSD Stack 200 is required to use a specific set of protocols.
  • the WSD Stack 200 leverages Web Services for Devices to create a powerful, extensible system that may communicate with a wide variety of devices 102 described in g reater detail above.
  • the WSD Stack is shown schematically at a high level.
  • the WSD Stack 200 in Fig. 2 shows the communication to and from clients 104 at the top of the diagram via a logical interface and the various hardware devices 102 arranged at the very bottom of Fig. 2.
  • the logical interface initially communicates with and through the WSD Stack 200 via a Hyper Text Transfer Protocol (HTTP) or a User Datagram Protocol (UDP) as indicated by reference numeral 201 .
  • HTTP Hyper Text Transfer Protocol
  • UDP User Datagram Protocol
  • the HTTP enables data transfer and display of web pages and the like as is well known in the art.
  • the UDP enables a direct way to send and receive datagrams on an IP network as is well known in the art.
  • the clients 104 interface via the logical interface through one or both of the HTTP and UDP layers 201 to a service provider 202.
  • communication from the client 104 to the service provider 202 may be via the HTTP or UDP information and the communication may be contained in SOAP packets.
  • the service provider 202 may be configured as a large, generic host for web services.
  • the service provider 202 may host one or more components 205 therein.
  • a component 205 may have the ability to host multiple services. However, the component 205 may limit the relationship between a service and a device to a one-to-one relationship.
  • a further part of the component 205 is the web service 203.
  • the web service 203 exists for each device 204.
  • the web service 203 may be configured as a generic web service based on the device category. For example, a thermostat has a corresponding web service based on the HVAC category for example only.
  • Each web service 203 may be configured with a device bridge 204.
  • the device bridge 204 may be configured to essentially translate commands by the physical devices 102. Accordingly, each device bridge 204 may be specific to the specific make of the physical device 102.
  • the service provider 203 may further include a controller 206.
  • the controller 206 may be arranged to communicate with the devices 102.
  • the controller 206 may be configured to have a ratio of one controller per component 205.
  • the controller 206 may include the ability to send feedback from the devices 102 to the component 204.
  • the component 204 may then route the feedback to the appropriate web service 203.
  • this arrangement provides the ability for feedback from the devices 102 to various clients 104.
  • the service provider 202 next may communicate to the various physical devices 102 via one or more of a plurality of different communications protocol 207.
  • the communications protocol with the devices 102 may include any type of native or proprietary format.
  • Such native or proprietary formats may be sent via Hyper Text Transfer Protocol (HTTP), transmission control protocol (TCP), user datagram protocol (UDP), or serial protocols.
  • HTTP Hyper Text Transfer Protocol
  • TCP transmission control protocol
  • UDP user datagram protocol
  • serial protocols provides one or two way serial communication as is well known in the art.
  • the WSD Stack 200 creates a powerful and extensible system based on web services for devices.
  • the WSD Stack 200 may communicate with a wide variety of devices 102 as discussed in detail with respect to Fig. 1 above.
  • Using the WSD Stack 200 allows network components to become “black box” components. This allows the various clients 104 and devices 102 to communicate in a clearly defined way without needing to know how they are accomplishing their various tasks. Using the WSD Stack 200 allows components to be implemented on any application running on any platform and written in any language. In essence, when the WSD Stack 200 is implemented, the network location and communications are handled by the platform, allowing application developers to focus solely on application problems. It should be noted that various modifications to the WSD Stack 200 are contemplated by the invention.
  • Fig. 3 shows a device bridge constructed according to the principles of the invention.
  • each service also contains a device bridge that translates any events to code needed by a specific device. This allows the application to communicate to the actual devices (or their corresponding controllers) in their native format. For this reason, each Web Service is depicted as containing a block of device- specific code (the bridge), that is, code that allows us to bridge non-standard devices to Web Service standards.
  • Fig. 4 shows a controller operating according to the principles of the invention.
  • the Controller allows for programmatic communication with a physical device.
  • the Controller sends commands that have come down through the Web Service/Device Bridge to the devices themselves.
  • a controller receives a command from a Web Service, it sends it to the correct device.
  • a Controller receives feedback or a message to return, it passes it back to the Component, which is responsible for routing the message back to the correct Web Service.
  • a Controller can serve multiple Web Services. However, there is only one Controller per Component.
  • Fig. 5 shows a device life cycle operating according to the principles of the invention.
  • Fig. 5 shows the various portions of the life cycle of a device networking using the WSD Stack 200 described above and shown in Fig. 2 in a device 102 as shown in Fig. 1 above.
  • Discovery 302 as used in conjunction with the WSD Stack 200 may use the WS-Discovery specification.
  • the WS-Discovery specification may include multicast announcements, multicast query requests such as probe and probe match, and unicast responses.
  • a device 102 may probe a client 104 using the discovery networking life cycle 302 to receive a probe match from the client 104.
  • discovery of the device 102 by one or more clients 104 is straight forward and essentially automatic. More specifically, a device 102 may announce its presence as it is connected to the network 12. This announcement may be through a sending out of a hello or bye message by device 102 on to the network 12. Additionally, the device 102 may respond to a client 104 request including various probe and resolve type requests.
  • a probe request may include the ability to identify a device or service within the client 104 or device 102.
  • the resolve request may include the ability to locate a device 102 or service end point. The result is the ability to get or obtain information via metadata exchange during the discovery 302 process.
  • the next step in the networking life cycle of the WSD Stack 200 process includes the step of description 304.
  • the step of description 304 may include a metadata exchange. This metadata exchange may be a response to a "get request.”
  • the description step 304 may thus include the WS-Metadata exchange protocol and may moreover include the WSDL or SOAP/XML information exchange.
  • the WSDL Web Services Description Language
  • the SOAP may be used in combination with the SOAP and XML schema to provide web services.
  • a device connecting to the network 12 may read the WSDL to determine what functions are available on the network 12, clients 104 and the like.
  • the SOAP Simple Object Access Protocol
  • control 306 The next step in the networking life cycle shown in Fig. 5 is the step of control 306.
  • control over a device 102 may be exercised by sending messages to the device 102 and/or services hosted by the device 102.
  • the control 306 may be defined by the WSDL and XML schema. This definition of control 306 may ensure a common base line for interoperability.
  • the eventing step 308 may include the WSD Stack 200 web service- eventing and may again use the SOAP/XML schema.
  • the eventing 308 may allow for a rich eventing model. This model may allow for detailed events through WSDL.
  • the eventing 308 may allow a client to subscribe to various events.
  • the eventing 308 may allow for the device 102 to push events to the clients 104.
  • the application as described above may be implemented with Web Services for Devices and in particular the above noted WSD Stack 200.
  • the Web Services for Devices and in particular the above noted WSD Stack 200.
  • WSD Services for Devices
  • IP Internet protocol
  • SOAP Simple Object Access Protocol
  • WSDL Web Services Device Language
  • the methods described herein are intended for operation with dedicated hardware implementations including, but not limited to, semiconductors, application specific integrated circuits, programmable logic arrays, and other hardware devices constructed to implement the methods and modules described herein.
  • various embodiments of the invention described herein are intended for operation with as software programs running on a computer processor.
  • alternative software implementations including, but not limited to, distributed processing or component/object distributed processing, parallel processing, virtual machine processing, any future enhancements, or any future protocol can also be used to implement the methods described herein.
  • a tangible storage medium such as: a magnetic medium such as a disk or tape; a magneto-optical or optical medium such as a disk; or a solid state medium such as a memory card or other package that houses one or more read-only (non-volatile) memories, random access memories, or other re-writable (volatile) memories.
  • a digital file attachment to email or other self-contained information archive or set of archives is considered a distribution medium equivalent to a tangible storage medium.
  • the invention is considered to include a tangible storage medium or distribution medium, as listed herein and including art-recognized equivalents and successor media, in which the software implementations herein are stored.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Automation & Control Theory (AREA)
  • Two-Way Televisions, Distribution Of Moving Picture Or The Like (AREA)
  • Selective Calling Equipment (AREA)

Abstract

L'invention concerne un système d'automatisation et un procédé destiné à faire fonctionner un système d'automatisation dans un environnement Service d'assistance Web comprenant au moins un client d'automatisation et au moins un dispositif d'automatisation, ledit client d'automatisation et ledit dispositif d'automatisation étant configurés avec un protocole en pile de services d'assistance Web pour dispositifs. Ce procédé consiste à connecter un réseau, comprenant au moins un serveur avec les services d'assistance Web pour dispositifs, audit dispositif client d'automatisation et audit dispositif d'automatisation, et à transmettre la commande sur la base d'une automatisation et la communication entre ledit client d'automatisation et ledit dispositif d'automatisation. Ledit dispositif d'automatisation comprend un téléviseur, un ordinateur personnel, un assistant numérique personnel, un panneau de commande ou bien un contrôleur de jeu. Ledit dispositif d'automatisation comprend un système audio, un système vidéo, un système intercom, un système d'éclairage, un système de sécurité et un système HVAC.
PCT/US2007/064188 2006-03-16 2007-03-16 Automatisation de dispositif par commande de dispositif réseauté doté de services d'assistance web pour une pile de dispositifs WO2007109551A2 (fr)

Applications Claiming Priority (18)

Application Number Priority Date Filing Date Title
US78259606P 2006-03-16 2006-03-16
US78259806P 2006-03-16 2006-03-16
US78263506P 2006-03-16 2006-03-16
US78259506P 2006-03-16 2006-03-16
US78260006P 2006-03-16 2006-03-16
US78259906P 2006-03-16 2006-03-16
US78263406P 2006-03-16 2006-03-16
US78273406P 2006-03-16 2006-03-16
US60/782,598 2006-03-16
US60/782,596 2006-03-16
US60/782,634 2006-03-16
US60/782,599 2006-03-16
US60/782,600 2006-03-16
US60/782,635 2006-03-16
US60/782,595 2006-03-16
US60/782,734 2006-03-16
US11/686,846 US7587464B2 (en) 2006-03-16 2007-03-15 Device automation using networked device control having a web services for devices stack
US11/686,846 2007-03-15

Publications (2)

Publication Number Publication Date
WO2007109551A2 true WO2007109551A2 (fr) 2007-09-27
WO2007109551A3 WO2007109551A3 (fr) 2008-10-09

Family

ID=38523191

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2007/064188 WO2007109551A2 (fr) 2006-03-16 2007-03-16 Automatisation de dispositif par commande de dispositif réseauté doté de services d'assistance web pour une pile de dispositifs

Country Status (1)

Country Link
WO (1) WO2007109551A2 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8234363B1 (en) 2009-09-18 2012-07-31 Kuo-Hua Kuo Dynamic object management protocol
TWI507010B (zh) * 2010-12-17 2015-11-01 Panasonic Corp 通訊系統及集合住宅用對講機系統

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20040267876A1 (en) * 2003-06-30 2004-12-30 Microsoft Corporation Ad-hoc service discovery protocol
US20050198304A1 (en) * 2004-01-15 2005-09-08 Ian Oliver System and method for access point translation of web service content
US7380250B2 (en) * 2001-03-16 2008-05-27 Microsoft Corporation Method and system for interacting with devices having different capabilities

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7380250B2 (en) * 2001-03-16 2008-05-27 Microsoft Corporation Method and system for interacting with devices having different capabilities
US20040267876A1 (en) * 2003-06-30 2004-12-30 Microsoft Corporation Ad-hoc service discovery protocol
US20050198304A1 (en) * 2004-01-15 2005-09-08 Ian Oliver System and method for access point translation of web service content

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8234363B1 (en) 2009-09-18 2012-07-31 Kuo-Hua Kuo Dynamic object management protocol
TWI507010B (zh) * 2010-12-17 2015-11-01 Panasonic Corp 通訊系統及集合住宅用對講機系統

Also Published As

Publication number Publication date
WO2007109551A3 (fr) 2008-10-09

Similar Documents

Publication Publication Date Title
US7587464B2 (en) Device automation using networked device control having a web services for devices stack
US7590703B2 (en) Set top box for convergence and automation system
US7509402B2 (en) Automation control system having a configuration tool and two-way ethernet communication for web service messaging, discovery, description, and eventing that is controllable with a touch-screen display
US8271881B2 (en) Touch screen for convergence and automation system
US8495187B2 (en) Apparatus and method for coordinately managing media content
EP2341716B1 (fr) Support audiovisuel à pièces multiples
US8725845B2 (en) Automation control system having a configuration tool
CN100362826C (zh) 网络共享内容的方法与接收装置及源装置
CN101129051B (zh) 用于在UPnP AV网络中提供“通用的‘跟我来’”功能的系统和方法
US8209398B2 (en) Internet protocol based media streaming solution
US8316140B2 (en) Method for controlling a device in a network of distributed stations, and network station
US7962130B2 (en) Portable device for convergence and automation solution
KR20010033849A (ko) 오디오 비디오 네트워크
KR20010033878A (ko) 장치 제어 기능이 있는 가정용 오디오/비디오 네트워크
KR20010033877A (ko) 가정용 오디오/비디오 네트워크
KR20010033879A (ko) 오디오/비디오 네트워크 및 이에 관련된 제어 방법
JP2008520029A (ja) コンテンツを追跡する方法、装置及びソフトウェア
CN102263782A (zh) 信息处理装置、信息处理方法和信息处理系统
WO2004061647A2 (fr) Interface d'application de dispositifs en reseau
US20020087964A1 (en) System and method for enhanced HAVi based device implementation
JP2008525878A (ja) Ｘｈｔネットワーク内で故障情報を提供する装置、システム及びその方法
JP2008165646A (ja) 再生装置および再生装置の制御方法
US20080098441A1 (en) Method and apparatus for managing services provided by devices in home network
WO2007109551A2 (fr) Automatisation de dispositif par commande de dispositif réseauté doté de services d'assistance web pour une pile de dispositifs
KR101782884B1 (ko) 콘텐츠 공유를 위한 콘텐츠 정보 제공 장치 및 방법

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 07758709

Country of ref document: EP

Kind code of ref document: A2

NENP Non-entry into the national phase in:

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 07758709

Country of ref document: EP

Kind code of ref document: A2