WO2009083976A2 - Procédés et système pour le déploiement, la gestion et l'utilisation de dispositifs et de services domestiques numériques - Google Patents

Procédés et système pour le déploiement, la gestion et l'utilisation de dispositifs et de services domestiques numériques Download PDF

Info

Publication number
WO2009083976A2
WO2009083976A2 PCT/IL2008/001689 IL2008001689W WO2009083976A2 WO 2009083976 A2 WO2009083976 A2 WO 2009083976A2 IL 2008001689 W IL2008001689 W IL 2008001689W WO 2009083976 A2 WO2009083976 A2 WO 2009083976A2
Authority
WO
WIPO (PCT)
Prior art keywords
service
services
brick
end user
user accessible
Prior art date
Application number
PCT/IL2008/001689
Other languages
English (en)
Other versions
WO2009083976A3 (fr
Inventor
Dror Bashan
Benny Bloch
Original Assignee
Dror Bashan
Benny Bloch
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 Dror Bashan, Benny Bloch filed Critical Dror Bashan
Priority to EP08867824A priority Critical patent/EP2240838A2/fr
Publication of WO2009083976A2 publication Critical patent/WO2009083976A2/fr
Publication of WO2009083976A3 publication Critical patent/WO2009083976A3/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/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
    • 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/50—Network services
    • H04L67/51—Discovery or management thereof, e.g. service location protocol [SLP] or web services

Definitions

  • the invention relates to methods and system for deploying, managing and using digital technologies, products, devices and services within the home.
  • PCs Personal Computers
  • CE Consumer Electronics
  • the significant barriers include: (i) the installation and configuration complexities; (ii) cost and different commercial aspects; (iii) technological and architectural limitations, including limited interoperability between diverse technologies and products, security concerns and the complexities associated with managing the relatively limited network bandwidth in order to meet the user's quality expectations.
  • the resulting situation is a complex digital home environment that is hard to setup and use.
  • a single end-to-end solution, targeting the entire digital home aspects and functionalities classes is required in order to fulfill the vision of the Digital Home to mass consumers.
  • DH Digital Home
  • Consumers are expecting to experience one transparent home network of interconnected and interoperated devices, and shared content. Where in fact they are facing several separated domains (PCs, broadcast, power-line and mobile) with no interoperability and interconnectivity.
  • PCs, broadcast, power-line and mobile The Digital Home (DH) environment allows consumers to experience simultaneous transport of multiple multimedia streams such as video (movies, TV) and audio (music, voice over IP) over the wireless home LAN. Consumers expect the quality of home media streaming applications to be at the same level as they experience with CE devices, such as their TVs/VCRs, DVD players, etc.
  • CE devices such as their TVs/VCRs, DVD players, etc.
  • the multitude of applications running simultaneously over the wireless LAN raises several challenges related to the deployment of the wireless I.AN, including the need for bandwidth management and QoS-based networking.
  • the Digital Home environment is built one device at a time over a long period of time. Each added device performs a specific and constant task.
  • the continuous need to support new services, media and content types, and the desire to enjoy entertainment everywhere within the house result in piles of stacked boxes spread around the house.
  • Boxes are from different vendors, connected to disparate networks (if at all) and experienced by users as very different. These devices and services are kept isolated, unshared and bound to a local connected device. For example, a Personal Video Recording (PVR) which is connected to a single set-top box and TV set, cannot be utilized by others TV sets, PC desktops or set-tops within the house.
  • PVR Personal Video Recording
  • Each box added to the pile dictates a new and different process to install, configure and maintain, together with its esoteric and proprietary GUI and other commands.
  • Digital home services must be end-to-end easy to install, configure, use and maintain. Consumer widespread adoption of digital home environment depends largely on the overall ease and quality of experience users are facing when integrating the digital home environment.
  • the Digital Home ecosystem consists of consumers, service and content providers, CE equipment and infrastructure vendors. For the digital home environment to gain mass-consumer acceptance, it should be affordable for consumers, create new revenue channels for service and content providers and allow CE equipment and infrastructure vendors to differentiate, focus on their main added value enabling them with fast time to market, flexible cost objectives and sales grow.
  • the OSGi Alliance is an open standards organization founded in March 1999.
  • the Alliance and its members have specified a Java-based service platform that can be remotely managed.
  • the core part of the specifications is a framework that defines an application life cycle model and a service registry. Based on this framework, a large number of OSGi Layers, APIs, and Services have been defined.
  • a digital home open platform system includes: multiple infrastructure devices configured to provide brick services selected from networking services, communication services, storage services, information processing services, application services, entertainment services, control services (home automation) and resource allocation services; wherein at least one infrastructure device is coupled to a home network and is not directly controllable by an end user; and a service builder, coupled to the multiple infrastructure devices and to at least one end user accessible device; wherein the service builder is configured to: receive, via the home network, a final service establishment request for a final service to be provided to the end user; select at least one brick service that should be provided to fulfill the final service establishment request; and request the at least one selected brick services to be fulfilled; wherein the request is sent to at least one device, selected from the multiple infrastructure devices and the at least one end user accessible device, that are capable of providing the at least one selected brick service.
  • a method for managing digital home services, that are provided by multiple infrastructure devices and at least one end user accessible device; wherein the multiple infrastructure devices and the at least one end user accessible device provides brick services that are used to compose a final service includes: receiving, via a home network, a final service establishment request for a final service to be provided to an end user; selecting at least one brick service that should be provided to fulfill the final service establishment request; and requesting the at least one selected brick services to be fulfilled; wherein the request is sent to at least one device, selected from the multiple infrastructure devices and the at least one end user accessible device, that are capable of providing the at least one selected brick service.
  • Figure 1 illustrates the current situation of product and functionality approach of digital technologies within the home, in which every function is implemented via a dedicated device
  • Figure 2 illustrates the solution oriented approach (vs. the current product oriented situation) that views the entire home environment as a whole system, according to an embodiment of the invention
  • Figure 3 illustrates the three layer scheme of the digital home open platform (DHOP) system's services, according to an embodiment of the invention
  • Figure 4 illustrates how end to end final services are composed from cooperative work of one or more devices, according to an embodiment of the invention
  • Figure 5 illustrates the hardware deployment architecture and its location within the layering model, according to an embodiment of the invention
  • Figure 6 is a block diagram of the DHOP Home Server and Computation Nodes according to an embodiment of the invention
  • Figure 7 illustrate the complete picture of the DHOP system within the home environment, according to an embodiment of the invention
  • Figures 8A-8D illustrates the management functions (denoted: home manager) according to an embodiment of the invention, wherein: Fig.8A is a block diagram of the main components of the home manager; Fig. 8B is a flow diagram of a service registration process that takes place at the initialization of a service; Fig. 8C is a flow diagram of the final service establishment process; and Fig. 8D is a flow diagram of services monitor process;
  • Figure 9 is a flow chart of a method 200 of managing the services, according to an embodiment of the invention.
  • Figure 10 illustrates a possible implementation of a device that is connected to the system, its architecture and the standards it should comply;
  • Figure 11 illustrates a possible implementation of the DHOP home manager and its management interfaces with the DHOP complied device.
  • the Digital Home Open Platform is a comprehensive digital home environment, covering the entire home functionalities and services, including: (i) Home Networking; (ii) Home Communication; (iii) Home Entertainment; (iv) Home Gaming; (v) Home Automation and Control; and (vi) Home Maintenance and Support Application (e.g. backup & restore), (vii) security applications (e.g. anti-virus) and update services; (viii) Home General Applications, e.g. productivity (office), health management; and (ix) any other functionality required by consumers within the home although not mentioned here.
  • DHOP Digital Home Open Platform
  • the DH environment typically consists of multiple device classes capable of handling a specific home task.
  • home entertainment including CE devices such as TVs and home theater, CD players, PVRs and Media Centers; Home communication, including phones; PCs and intercom; and Home networking, including routers, switches and residential getaways.
  • CE devices such as TVs and home theater, CD players, PVRs and Media Centers
  • Home communication including phones
  • PCs and intercom including routers, switches and residential getaways.
  • Devices can be interconnected by one or more networks or not connected at all.
  • Legacy (analog) devices may also be connected to the Digital Home environment by special-purpose adapters.
  • the Digital Home Open Platform (DHOP) is an innovative architecture and a new approach for the implementation and the deployment of digital home environments (networking, entertainment, automation and more).
  • the DHOP system is a key factor for digital home environment where different networks (TV, Phone, IP, Power-Line), devices and services should coexist and interoperate in transparent way, and be easy to use for consumers.
  • the DHOP system enables consumers to expand their digital home functionality by adding devices hosting and exposing set of services. New added device and its hosted and exposed services are automatically registered, discovered, configured and ready to use, not requiring any special skill or knowledge from the consumer.
  • the DHOP system views digital home environment as a set of manageable digital services.
  • the DHOP system specification defines two types of services: Final Service, which is a high level service describing users' daily tasks, e.g. "Watching TV" or "Internet Browsing".
  • the second type is Brick Service, which is an atomic building-block service that together with cooperative work of others Brick Services construct a Final Service.
  • the DHOP system has a solution oriented conceptual approach for covering the entire digital home as one appliance that is controlled through single method of operation and with flexibility for supporting scalable platform that enables consumers to easily expand their home with more capabilities and additional functionalities.
  • the DHOP system can be characterized by. (i) Solution Oriented approach vs. Product and Functionality approach; (ii) Centralized Management vs. Distributed Management for the Home Services, Devices and Resources; (iii) Home Services Layers and Categories (Final, Brick, Infrastructure, Frequently-Accessed); and (iv) Centralized Deployment Architecture for the Home Infrastructure Services, Devices and Resources vs. Pile of Boxes distributed across the home. [0057] The DHOP system is based on the following concepts: Service oriented architecture, service layers and hardware deployment architecture. [0058] The DHOP system views digital home environment as a set of manageable digital services. The DHOP system defines two types for digital home services: Final services, representing high level, consumers' daily tasks such as "reading news paper", "performing phone call", "watching a movie” or "playing a game”; and
  • Brick Services representing atomic functionality such as "Display Service”, “TV Tuner” or “Media Center” services.
  • Cooperative work of one or more brick services constructs an end- to-end final service.
  • the Final Service “Watching TV” may be constructed from the following brick services: “setop box”, “TV tuner” and "display service”.
  • Digital Home Services are exposed to the user through DHOP Service Oriented GUI mechanism which exposes only final services. Brick services are totally hidden from users.
  • FIG. 1 illustrates the current situation of the digital home products and functions.
  • every home function is tied to a specific device or group of devices. For example, for phone calls we use the specific phone that receives the call (and hence is ringing). For Internet calls we use a computer connected to the Internet. For watching TV we use a TV set with its dedicated display while for working on PC we use the PC with a different dedicated display.
  • FIG. 1 illustrates the solution oriented approach (vs. the current Product and Functionality approach) that views the entire home environment as a whole system.
  • the DHOP system architecture is based on three layers: [0066] (i) Final Services layer, representing high level, consumers' daily tasks; [0067] (ii) Frequently Accessed Services layer, representing collection of standalone players, controls services and other frequently accessed services; and
  • the DHOP system layering architecture physically and logically decouples Frequently Accessed services (such as players) from infrastructure brick services (such as PVR and TV Tuner).
  • the DHOP system service layering approach enables to share presentation brick services (for example speakers and Display screen) between different final services so any final service can use any presentation brick service regardless of its physical location. For example, the same display brick service can be used once for watching TV (final service) and in other time to work on PC (final service).
  • Another example is a video clip, stored in the home storage service, can be once viewed with media service in display service located in the living room and at another time or in parallel to be viewed by different player service in the bedroom.
  • Brick Service can serve other Brick Services. For example storage Brick Service can share its storage between PVR Brick Service and Media Center Brick Service.
  • Figure 3 Illustrates the three layer scheme of the DHOP system services: End user layer 11 is composed of Final Services 51 representing high level, user related, daily functionalities;
  • Frequently Accessed layer 12 representing services and devices often accessed by end-users (such as players, DVD, control). These services and devices are part of the building blocks of final services, thus considered brick services; and
  • FIG. 13 representing Brick services 52, not requiring end user access, performing specific functionality and serve as building blocks along with the Frequently Accessed layer to construct Final Services 51.
  • Figure 4 illustrates how Final Service 51 is composed from cooperative work of one or more Brick Services 52. This composition is part of a service building process, further described in figure 8B.
  • Figure 5 illustrate the hardware deployment architecture and its location within the layering model that was described above.
  • the layering concept enables 'mix-and-match' flexibility for sharing services and content within the home but cannot account for the many boxes to setup and maintain. This issue is addressed in the DHOP hardware deployment architecture.
  • DHOP specification defines two types of services: Brick Services and Final Services. Brick Services are further classified into two types: Infrastructure Service and Frequently Accessed
  • Infrastructure Services and Frequently Accessed Services differ with the level of direct accessibility and interaction required with the user.
  • Infrastructure Brick Services does not requires direct end-user access (e.g. TV Tuner, PVR, disk storage)
  • DHOP has a centralized architecture in respect to the Infrastructure services and a distributed architecture in respect to the Frequently-Accessed services.
  • the centralized architecture of the digital home infrastructure services is implemented using a flexible Home Server hardware architecture, example for such an architecture is blade computing .
  • Infrastructure services such as networking, TV tuners and Voice over IP are implemented and hosted on Computation Nodes (an example for implementation is blade computer) installed within the DHOP Home Server.
  • a Home Server In a typical installation, a Home Server consists of several pre- installed Computation Nodes, each hosting different infrastructure services that provide the basic functionality of the digital home environment. 3 rd party Computation Nodes based on the DHOP specification may be added in order to expand functionality and capacity. [0085] The Home Server is designed for real plug-n-play experience: after inserting the computation node in a free slot (no tools required), the new computation node will self configure and the new services will be live and running - no lengthy installations, setups, complex configuration and repeated boots.
  • Connectivity between Frequently-Accessed services and Infrastructure services is implemented via wire-line or wireless communication.
  • the DHOP system traces the location of each of the Frequently-Accessed services and ongoing applications in order to optimize home bandwidth utilization and ensure matched QoS for Frequently-Accessed services and Infrastructure services broadcasting or streaming content over the network.
  • FIG. 6 is a block diagram of the DHOP system's platform according to an embodiment of the invention.
  • Each home server 60 includes computation nodes 50 interconnected by an internal communication 55, such as a fully meshed internal high speed backplane (e.g. Gigabit Ethernet or other technology).
  • Each computation node 50 is an independent Self Boot Computer (SBC) with its own controller 53 and may host one or more Brick Services 52, represents infrastructure devices or a home manager 30 that includes all the service management functionalities.
  • SBC Self Boot Computer
  • Inter process communication (IPC) between computation nodes 50, services and service management is implemented over the internal communication 55 using existing standards such as TCP/IP, HTTP, SOAP, XML etc.
  • Home Server 60 can split into several home servers communicating over a home network 56.
  • DHOP system's centralized architecture facilitates Appliance-like level of reliability without scarifying the requirement for easy expandability and scalability.
  • Figure 7 illustrates the complete picture of the DHOP system.
  • the various functionalities of the digital home are aggregated and centralized within the home server 60.
  • Computation Node 50 inside the Home Server is responsible to implement one or more Brick Services 52 representing infrastructure devices or the Home Manager 30 that includes all the system management functionalities (services and devices).
  • Players Brick Services 52" and Control Brick Services 51 ' are standalone devices through which the end user access and control home functionalities (the Final Services). Activating a final service is done using a control brick service or using a menu displayed on a player brick service. [0097] The outcome of the final service (e.g. video stream, TV program) is displayed on a player brick service.
  • the final service e.g. video stream, TV program
  • Infrastructure Brick Services 52 are interconnected using the internal communication (not shown) of Home Server 60, which can use a high bandwidth network and further connected to Player & Control through home network 56.
  • Home network 56 is based on wire and wireless technologies spread around the home and networking Computation Nodes (not shown, such as router, switch) hosted in Home Server 60.
  • the networking Computation Node can bridge between different networking technologies such as Ethernet, Power-Line and Phone line enabling the usage of them all as required.
  • Home Server 60 can host Computation Nodes that bridge between home network 56 and an external network 57 such as PSTN. In such cases external network 57' is connected to the specific Computation Node which then distributes it over the DHOP system to the entire home.
  • Legacy Devices can be connected to the DHOP digital home environment through DHOP system complied Legacy Adapters 54. The
  • Legacy Adapter 54 implements the required functionality for integrating the
  • Legacy Device with the DHOP system environment is a TV screen which can be converted into the DHOP system
  • FIGS 8A-8D illustrates home manager 30 according to an embodiment of the invention, wherein:
  • Fig. ⁇ A is a block diagram of the main components of home manager 30;
  • Fig. 8B is a flow diagram of a service registration process that takes place at the initialization of a service.
  • Fig. 8C is a flow diagram of a final service establishment process
  • Fig. 8D is a flow diagram of a monitoring services and devices.
  • FIG.8A illustrates the main components of home manager 30.
  • Home Manager 30 is an infrastructure layer responsible to activate, control and manage home services.
  • Home Manager 30 is an extension and enhancement of standards such as the Universal Plug and Play
  • Home manager 30 includes the following components: [00110] Service Repository 31 - is a storage that stores information indicative of brick services, such as their description and status. Service
  • Repository 31 provides operations such as service registration and deletion.
  • the service repository is responsible to supply information about available Brick Services and their status.
  • Service builder 32 is in charge of dynamically building of final services out of its building brick services, available and stored in service repository 31.
  • Service editor 33 enables CE vendors and end users to define new Final Services and the relationships between the Brick Services required for their implementation.
  • Home Monitor 34 monitors ongoing status of the all the final services and brick services stored in service repository 31 , their performance and other conditions while active. Home Monitor 34 uses service repository 31 to retrieve the list of services that it monitors. Home Monitor 34 also monitors the status of the computation nodes and it uses computation node repository
  • Home monitor 34 reports to a fault manager 37 in case it detects a problem.
  • Device manager 36 is responsible for the management of computation nodes installed within the Home Server and for the management of Frequently-Accessed devices distributed across the home. Device manager
  • the Computation Node Management Protocol is available for 3 rd parties wishing to manufacture Computation Nodes and add functionality to the digital home environment though the DHOP system.
  • the current state of Computation Node optionally can be displayed on Computation Node's state panel and in case of failure the consumer is notified with a detailed explanation of how to identify the failed Computation Node and actions required for replacing it.
  • Similar auto discovery mechanism exists for Frequently-Accessed devices, the only difference is with the Auto Discovery mechanism which in computation node can be physical sensor that senses insertion and removing of the computation node, while here it is a software one.
  • Device manager 36 reports to a fault manager 37 in case it detects a problem with one of the devices.
  • Fault manager 37 receives problem reports from all the other modules, or at least from home monitor 34 and from device manager 36. Fault manager 37 analyses the problem and choose the way to handle it. [00119] One of its major duties is taking care of redundancy of critical function. Computation Nodes responsible for critical functionality can be deployed in redundant configuration. Fault manager 37 is responsible for transparently managing availability by failover mechanism. [00120] Interface 38 represents the home manager services' interfaces through which the Home Manager services communicate with the other DHOP services and devices located within the Home Server or distributed around the home and connected via the home network. These interfaces are based on communication software standards such ' as UPNP and DLNA with additional functionality for supporting the DHOP platform requirements..
  • FIG. 8B illustrates the flow of the service registration process.
  • Each brick service 52 automatically registers itself within Service Repository 31 of Home Manager 30, by sending a service registration request 71 that includes a description for its inputs and outputs capabilities. This information is used for the dynarriic connectivity of Brick Services to form the requested Final Service functionality.
  • final services are also stored in service repository 31 , either as predefined services, but they can also register when a user selects a new final service to be added, using the Home menu.
  • Another example to final service that registers is - a game. The game is coming implemented on a device that is installed at the home server. The game final service registers it self in the system so end user can access and play it through the access devices.
  • FIG. 8C describes the flow of establishing a Final Service.
  • a final service from the Home Main Menu e.g. "Watch TV”
  • a final service establishment request 73 is sent to Home Manager 30 which forwards it to Service Builder 32.
  • Service Builder 32 examines the Final Service description and sends a message - get service descriptor 74 to service repository 31 for each of the required Brick Services. Once the relevant Brick services were located and allocated, Service Builder 32 concatenates the Brick Services to dynamically establish a Final Service.
  • Services Repository 31 Since Services Repository 31 also maintains services' status and utilization, when Service Builder 32 queries for required Brick Service it will get response only by Brick Services which are actually available to provide the service. [00128] As part of establishing the Final Service, Service Builder 32 can query other brick services for various conditions of specified services or the DHOP system in general, by sending a message - service consulting 75 and receive a service consulting information 76, in response. [00129] For example, when a Final Service involves streaming video over the network, Service Builder 32 can query a QoS brick service for the required bandwidth of the streaming route and if the added stream will not interfere other running services.
  • Service builder 32 activates each of the brick services involved in the final service, by sending them messages: Service setup 77, in the right order. It also sends service repository 31 , a message - allocate services 78 for all the brick services involved in the process, to indicate that these services are occupied for the duration of the final service.
  • Figure 8D illustrates the flow of monitoring computation nodes as well as active Final and Brick services performance and health by periodically sending messages - status and control query 79.
  • Figure 9 is a flow chart of a method 200 of managing digital home services.
  • Method 200 starts by stage 210 of receiving a service registration request of brick and final services, related to infrastructure devices and end user accessible device.
  • the service registration is triggered by an insertion and/or a reset of a computation node that controls brick services, after it starts the brick services it hosts.
  • the service registration is also triggered by connecting, to the home network, new distributed infrastructure devices and user accessible devices.
  • Stage 210 includes receiving service registration requests 71 , via the home network or the home server internal communication.
  • Service registration request 71 includes information describing the registered service
  • Stage 210 further includes storing information indicative of brick service in service repository 31.
  • Brick services can be deleted from the service repository upon receiving a service deletion request that it sent by Home Monitor 34 when it detects unavailability of brick services.
  • the service deletion request can be also sent by device manager 36 when it detects a removal of a computation node.
  • Method 200 further includes stage 215 of receiving final service definition describing the brick services and the relationships between them, required for final service establishment.
  • Method 200 further includes stage 220 of establishing a final service, which must be preceded by a registration of all the brick services related to the requested final service, as described in stage 210 and also preceded by receiving the final service definition as described in stage 215.
  • Stage 220 is triggered by an end user that selects a desired Final
  • Stage 220 includes the following sub-stages: [00144] Sub-stage 221 of receiving, by the service builder, a Final Service establishment request.
  • Sub-stage 221 is followed by sub-stage 222 of selecting the brick services and the devices (which host the brick services) that are involved in the final service.
  • Sub-stage 222 includes requesting service descriptor from the service repository. Conveniently, Sub-stage 222 can also include requesting information from brick services by sending them a service consulting message
  • Sub-stage 222 is followed by sub-stage 223 of requesting the brick services that are involved in the final service, to provide the service, by sending them a service setup message.
  • Stage 220 is further described by figure 8C.
  • Method 200 further includes stage 230 of periodic monitoring computation nodes, accessible devices, final and brick services performance and health by sending them status and control query messages in order to detect unavailability of existing infrastructure devices, end user accessible devices, brick and final services.
  • the periodic monitoring of services and devices starts at the moment they have been registered. Since stage 230 is a background process, it can be executed in parallel to stages 210-223.
  • FIG. 10 illustrates a possible implementation of a device that is connected to the system, its architecture and the standards it should comply:
  • DHOP complied device 80 should fulfill the following requirements: (i) Hardware - reliable HW configuration including elements such as: solid state disk, no fans, etc; (ii) Software - operating systems such as: Embedded Linux, Mobile Linux, Windows CE; and (iii) Networking - networking primary boot does not need device main CPU, support 100M/ 1 G/ 10G connections.
  • OSGI framework 83 is used for: (i) control the solutions that are running within DHOP complied device, one device can run one or more OSGI frameworks; and (ii) manage solution software life cycle, boot, start, stop, run, exit, etc.
  • Solution/ bundle 82 - is the software implementing the device functionality through implementing software services representing brick and final services.
  • UPnP/ DNLA services 81 - is used as building blocks for the DHOP management protocol, supporting operations required for services management (registration, discovery) through which the device functionality is exposed.
  • DHOP management protocol 84 - is described in figure 11.
  • DHOP complied device, is a network device implementing UPnP and DLNA for communication.
  • the device is managed using the OSGI platform.
  • Device functionality is implemented software modules comply with OSGI bundles.
  • the DHOP complied device should have very reliable hardware (no solid disks, no fans) operating with very low noise level (no fans).
  • Infrastructure DHOP complied devices are configured as computation nodes to fit into the home server platform.
  • Figure 11 illustrates a possible implementation of the DHOP home manager and its management interfaces with the DHOP complied device that is described in figure 10.
  • Device management 86 - manages the DHOP complied devices early stage boot (HW and OS) with minimum resources (network before Os boot); OSGI management 87 - manages the OSGI framework running on the DHOP complied device; Solution management 88 - manages the solutions running within an OSGI framework; Service management 89 - manages the device/solution services exposed through the UPnP interface; DHOP management protocol 84 - manages the entire DHOP platform; and External management 91 - Manages interface exposed to service provider. [00162] For a device to be complied with DHOP, it should support additional management features embedded within the DHOP Management Protocol.
  • the DHOP Management Protocol adds more functionality to the UPnP and DLNA, example is A Centric Management concept compared with the distributing management concept of UPnP and DLNA, or hardware management which is not covered by UPnP and DLNA and more.
  • All DHOP complied devices are communicating with the DHOP Home Manager 30 over the DHOP Management protocol 84. This protocol is based on UPnP and DLNA with additional features.
  • DHOP Home Manager 30 exposes also Remote Management protocol to enable remote control for the home functionality.
  • Variations, modifications, and other implementations of what is described herein will occur to those of ordinary skill in the art without departing from the spirit and the scope of the invention as claimed. Accordingly, the invention is to be defined not by the preceding illustrative description but instead by the spirit and scope of the following claims.

Abstract

L'invention concerne un système de plate-forme ouverte domestique numérique comprenant : des dispositifs d'infrastructures multiples configurés pour fournir des services de brique sélectionnés parmi des services de réseau, des services de communication, des services de stockage, des services de traitement d'informations, des services d'application, des services de divertissement, des services de contrôle (domotique) et des services d'attribution de ressources; au moins un dispositif d'infrastructure étant couplé à un réseau domestique et n'étant pas directement contrôlable par un utilisateur final; et un bâtisseur de service, couplé aux dispositifs d'infrastructures multiples et à au moins un dispositif accessible à un utilisateur final; le bâtisseur de service étant configuré pour : recevoir, par l'intermédiaire du réseau domestique, une demande d'établissement de service final pour un service final à fournir à l'utilisateur final; sélectionner au moins un service de brique qui devrait être fourni pour répondre à la demande d'établissement de service final; et demander la réalisation du ou des services de brique sélectionnés; la demande étant envoyée à au moins un dispositif, sélectionné parmi les dispositifs d'infrastructures multiples et le ou les dispositifs accessibles à un utilisateur final, qui sont en mesure de fournir le ou les services de brique sélectionnés.
PCT/IL2008/001689 2007-12-30 2008-12-28 Procédés et système pour le déploiement, la gestion et l'utilisation de dispositifs et de services domestiques numériques WO2009083976A2 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
EP08867824A EP2240838A2 (fr) 2007-12-30 2008-12-28 Procédés et système pour le déploiement, la gestion et l'utilisation de dispositifs et de services domestiques numériques

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US1765207P 2007-12-30 2007-12-30
US61/017,652 2007-12-30

Publications (2)

Publication Number Publication Date
WO2009083976A2 true WO2009083976A2 (fr) 2009-07-09
WO2009083976A3 WO2009083976A3 (fr) 2010-03-11

Family

ID=40824817

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/IL2008/001689 WO2009083976A2 (fr) 2007-12-30 2008-12-28 Procédés et système pour le déploiement, la gestion et l'utilisation de dispositifs et de services domestiques numériques

Country Status (2)

Country Link
EP (1) EP2240838A2 (fr)
WO (1) WO2009083976A2 (fr)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2341662A1 (fr) * 2010-01-05 2011-07-06 Accenture Global Services Limited Gestion de service hiérarchique
CN102355472A (zh) * 2011-06-20 2012-02-15 苏州博康生物医疗科技有限公司 一种基于三网融合的网络服务管理系统的服务管理方法
CN102523116A (zh) * 2011-12-20 2012-06-27 苏州亚安智能科技有限公司 一种运用三网融合技术的网络服务平台的管理方法
CN102546598A (zh) * 2011-12-20 2012-07-04 苏州亚安智能科技有限公司 运用三网融合技术的新型应用平台
WO2013048183A1 (fr) * 2011-09-30 2013-04-04 Samsung Electronics Co., Ltd. Appareil et méthode de gestion intégrale de la maintenance de dispositifs électroniques
WO2014040461A1 (fr) * 2012-09-13 2014-03-20 中兴通讯股份有限公司 Procédé et dispositif de contrôle d'accès

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6012100A (en) * 1997-07-14 2000-01-04 Freegate Corporation System and method of configuring a remotely managed secure network interface
US20020120728A1 (en) * 2000-12-22 2002-08-29 Jason Braatz Method and apparatus for network-enablement of devices using device intelligence and network architecture

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6012100A (en) * 1997-07-14 2000-01-04 Freegate Corporation System and method of configuring a remotely managed secure network interface
US20020120728A1 (en) * 2000-12-22 2002-08-29 Jason Braatz Method and apparatus for network-enablement of devices using device intelligence and network architecture

Cited By (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2341662A1 (fr) * 2010-01-05 2011-07-06 Accenture Global Services Limited Gestion de service hiérarchique
US8484366B2 (en) 2010-01-05 2013-07-09 Accenture Global Services Limited Hierarchical service management
EP2725744A3 (fr) * 2010-01-05 2014-08-13 Accenture Global Services Limited Gestion de service hiérarchique
US9088475B2 (en) 2010-01-05 2015-07-21 Accenture Global Services Limited Hierarchical service management
EP3107244A1 (fr) * 2010-01-05 2016-12-21 Accenture Global Services Limited Gestion de service hiérarchique
CN102355472A (zh) * 2011-06-20 2012-02-15 苏州博康生物医疗科技有限公司 一种基于三网融合的网络服务管理系统的服务管理方法
WO2013048183A1 (fr) * 2011-09-30 2013-04-04 Samsung Electronics Co., Ltd. Appareil et méthode de gestion intégrale de la maintenance de dispositifs électroniques
CN102523116A (zh) * 2011-12-20 2012-06-27 苏州亚安智能科技有限公司 一种运用三网融合技术的网络服务平台的管理方法
CN102546598A (zh) * 2011-12-20 2012-07-04 苏州亚安智能科技有限公司 运用三网融合技术的新型应用平台
WO2014040461A1 (fr) * 2012-09-13 2014-03-20 中兴通讯股份有限公司 Procédé et dispositif de contrôle d'accès
CN103686722A (zh) * 2012-09-13 2014-03-26 中兴通讯股份有限公司 访问控制方法及装置

Also Published As

Publication number Publication date
WO2009083976A3 (fr) 2010-03-11
EP2240838A2 (fr) 2010-10-20

Similar Documents

Publication Publication Date Title
JP4260366B2 (ja) ネットワークにおける機器のアップグレード及び拡張方法
EP1046259B1 (fr) Procede et systeme relatifs a un reseau audio-video
CA2546598C (fr) Procedes et dispositifs permettant l'enregistrement de materiel dans un dispositif reseau
US8713199B2 (en) Method and system for filtering home-network content
US9883251B2 (en) Method and apparatus for managing connection between broadcast receiving device and another device connected by network
KR100647449B1 (ko) 특성 루트를 통해서 소프트웨어 오브젝트들을 제어하기위한 시나리오를 식별하는 호출
KR20150126578A (ko) 범용 웹 애플리케이션을 이용하여 홈 네트워크 장치를 제어하는 방법 및 장치
CN105323628B (zh) 基于dlna跨屏播放的方法及系统、浏览器端装置和播放装置
US10554745B2 (en) Method and apparatus for managing connection between broadcasting reception device and another device which are connected through network
US10211997B2 (en) Method and apparatus for playing back scene using UPnP
EP2240838A2 (fr) Procédés et système pour le déploiement, la gestion et l'utilisation de dispositifs et de services domestiques numériques
CN110830841B (zh) 一种处于不同局域网下的投屏方法、系统及智能装置
KR100461740B1 (ko) 하나 또는 그 이상의 1394 버스를 갖는 네트워크에서의브로드캐스트 디스커버리
EP1351447A1 (fr) Gestion et contrôle d'appareils audio-vidéo en réseau
US20090077215A1 (en) Using a managing device to configure and locally manage multiple managed devices
US8176343B2 (en) Method for providing information for power management of devices on a network
JP4519736B2 (ja) データ伝送システム、データ伝送方法およびメディア装置
JP2007158591A (ja) コンテンツ切替判定システム及び切替指示端末、並びに、コンテンツ切替判定方法
US20050132366A1 (en) Creating virtual device for universal plug and play
KR101329668B1 (ko) 푸쉬 서버를 이용한 콘텐츠 공유 시스템 및 방법
Lai et al. A portable UPnP-based high performance content sharing system for supporting multimedia devices
US8782717B2 (en) Method of restoring AV session and a control point for the same
Kim et al. Provision of the multimedia service framework in the ubiquitous home network
KR20060114785A (ko) 홈네트워크에서의 외부 디바이스 컨텐츠 사용 방법
KR100690125B1 (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: 08867824

Country of ref document: EP

Kind code of ref document: A2

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2008867824

Country of ref document: EP