WO2012004424A1 - Método y sistema de gestión de topologías de red en redes domésticas - Google Patents
Método y sistema de gestión de topologías de red en redes domésticas Download PDFInfo
- Publication number
- WO2012004424A1 WO2012004424A1 PCT/ES2010/070470 ES2010070470W WO2012004424A1 WO 2012004424 A1 WO2012004424 A1 WO 2012004424A1 ES 2010070470 W ES2010070470 W ES 2010070470W WO 2012004424 A1 WO2012004424 A1 WO 2012004424A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- network topology
- information
- network
- devices
- management module
- Prior art date
Links
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/12—Discovery or management of network topologies
-
- 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
- H04L12/283—Processing of data at an internetworking point of a home automation network
- H04L12/2836—Protocol conversion between an external network and a home network
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y04—INFORMATION OR COMMUNICATION TECHNOLOGIES HAVING AN IMPACT ON OTHER TECHNOLOGY AREAS
- Y04S—SYSTEMS INTEGRATING TECHNOLOGIES RELATED TO POWER NETWORK OPERATION, COMMUNICATION OR INFORMATION TECHNOLOGIES FOR IMPROVING THE ELECTRICAL POWER GENERATION, TRANSMISSION, DISTRIBUTION, MANAGEMENT OR USAGE, i.e. SMART GRIDS
- Y04S40/00—Systems for electrical power generation, transmission, distribution or end-user application management characterised by the use of communication or information technologies, or communication or information technology specific aspects supporting them
Definitions
- the present invention refers to a method and management system of network topologies in home networks.
- the field of application of the invention is the management of networks, specifically the management of customer networks and more specifically the management of the digital home.
- BBF Broadband Forum
- TRO-69 a standards of the Broadband Forum
- PD-174 a standards of the Broadband Forum
- HGI Home Gateway Initiative
- UPnP UPnP
- Samba home automation specific protocols
- HGI Home Gateway Initiative
- Cisco Magic Network which implements some management features in the home network. This solution is based on the existence of a PC in the home network, and has been developed using a protocol designed by Cisco ⁇ .
- Cisco Network Magic uses home network management protocols (HNAP) to Manage devices and provide a software development kit for users to create their own HNAP management applications. It is a protocol that allows programming, configuration, management and reporting on the network.
- HNAP home network management protocols
- Protocols such as UPnP, Samba or specific home automation protocols cannot interoperate with remote administration protocols (for example, TR-069). Apart from that, different types of devices need different tools for their management, that is, there is no unified tool to access the most common types of devices in the home.
- the invention consists of a method and a system for managing network topologies in home networks.
- This invention will facilitate the management of the home network for both the end user and the operator, both when configuring the service and when executing it as it provides the mechanisms to other tools to discover, view and manage the devices connected in the home in an easy and efficient way.
- the basic concept of the invention is to have a functional element in the home network, more specifically on the residential catwalk, which is capable of performing the following tasks:
- ⁇ Invoke devices for example, configuration operations, update their information, access to their services, etc.
- An example could be a local application that allows displaying and managing home devices, or a TR-069 proxy that is capable of communicating the network topology to a remote auto-configuration server, ACS.
- the invention comprises on the one hand a network topology management system in home networks where.
- the aforementioned system is integrated into a runtime environment available on devices that connect to a home network.
- an interface publishing service for the correct operation of the invention it will be necessary to have an interface publishing service.
- said system comprises:
- a network topology management module comprising means for coordinating the rest of the system modules, means for detecting devices connected to the home network through an interaction with at least one protocol adapter and means for storage and information management of a home network topology through an interaction with a data management module;
- a local device management module which comprises providing at least one interface for the network topology management module to establish communication with the devices connected to the home network and which additionally comprises means for notifying changes in the topology of the network. home network to the network topology management module;
- a data management module comprising a database of the network topology that stores the topology of the home network, means of managing said database and additionally comprising a data management interface for communicating with the module network topology management;
- At least one network topology management module of device types comprising a mapping management interface whereby, the network topology management module obtains information from the devices connected to the home network.
- This module will be, in a preferred embodiment, selected from a UPnP module, a non-IP home automation module and an IP module that exclusively supports IP protocols.
- a notification module that sends notifications to external modules to the system that have previously subscribed to such notifications when changes in the network topology occur through an NTM event capture interface, provided by the network topology management module;
- Y • at least one protocol adapter comprising a conventional interface for communicating with devices connected to the home network.
- protocol adapters will be selected in a preferred embodiment from a UPnP protocol adapter that handles UPnP devices via an UPnP protocol, a home automation protocol adapter that manages non-IP home automation devices through a home automation proxy that employs standard protocols and an IP protocol adapter, which manages IP devices, which exclusively support IP protocols, through an ARP protocol.
- the network topology management module provides the following interfaces to modules or entities external to the system:
- an NTM description interface which comprises obtaining from the modules external to the system a list of devices detected in the home network and information stored on them in the network topology database;
- the local device management module provides the following interfaces to the system:
- protocol adapters provide the system with the following interfaces:
- an AP publication capture interface implemented by the local topology management module to receive notifications of changes in the devices sent from the at least one protocol adapter
- the present invention also describes a network topology management method in home networks for the previously defined system comprising the following phases:
- the detected device in another preferred embodiment in the phase of checking what type of device has been detected and storing the information related to said device, can be a new physical, virtual device or it can be a device that had already been previously detected regardless of whether It was physical or virtual.
- said phase comprises the following subphases:
- the device detected is a virtual device, it comprises the following subphases:
- phase of verifying by the data management module that the device has not been previously detected when it is obtained that the device is already previously detected, it comprises the following phases:
- the information gathering phase of the device comprises the following steps:
- the phase of requesting the execution of services offered by the devices connected to the home network comprises the following steps:
- the at least one device type topology management module when the at least one device type topology management module is started for the first time, it registers a mapping management interface in the system in which the type of device it manages is specified, said type being of device selected from UPnP device, IP device and non-IP home automation device.
- the network topology management module registers a network topology management interface in the system by means of which the internal and external elements to the system invoke said system.
- the notification module registers a notification interface in the system by which it notifies the modules external to the system of changes in the network topology.
- said database comprises the following information for each device of the detected home network:
- device type information said information being selected among IP devices, UPnP devices and non-IP home automation devices;
- each memory location of the virtual device list comprises at least the following information:
- device status information said information being selected from enabled, disabled and error;
- information of the type of virtual device with said information being selected between devices IP, UPnP devices and non-IP home automation devices;
- Manufacturer information comprising the name of the manufacturer
- model information comprising the device model name
- model number information which includes the device model number
- additional information comprising a list of additional parameters about the device; and, - a list of services offered by the device.
- each memory location of the list of services comprises at least the following information:
- the information stored in the network topology database is obtained and stored based on at least:
- a basic configuration information file comprising a list of properties of the devices in the home network, a list of values to be established in the network topology for each device and a procedure to obtain basic information common to all devices registered in the network topology database;
- Additional rule-based configuration information file stored in a field called additional information, which comprises a list of rules and defines a procedure for obtaining specific additional information from each device registered in the network topology database.
- the virtual device subtype when said device is of the UPnP type, is selected from a media player, a media server and a wireless network camera.
- the virtual device subtype when said device is home automation type, is selected from an intelligent meter, an intelligent connector and a switch.
- the virtual device subtype is IP when said device is of type IP.
- Figure 2.- Shows the schema of the basic information configuration file.
- Figure 3. Shows the scheme of the configuration file of the additional information.
- Figure 4.- Shows the flow diagram of the network topology management algorithm.
- Figure 5. Shows the scheme of how the information is stored in the database related to the physical devices of the network topology.
- Figure 6. Shows the scheme of how the information is stored in the database related to the virtual devices of the network topology.
- Figure 7.- Shows the scheme of how the information is stored in the database related to the services offered by the devices of the network topology.
- Figure 8.- Shows the sequence diagram of the device detection.
- Figure 9. Shows the sequence diagram of obtaining information from the devices.
- Figure 10. Shows the sequence diagram of the request of the services offered by the devices. DESCRIPTION OF AN EXAMPLE OF REALIZATION OF THE
- FIG 1 shows the main functional block scheme of the home network topology manager (1).
- the different modules that comprise it communicate with each other through known interfaces, and there are also interfaces with external entities (2) that make use of the functionalities provided by the home network topology manager.
- the execution environment of the invention provided by an Interface Publishing Service, so that the different modules can publish their interfaces in the system so that other external modules or entities (2) can make requests or receive notifications.
- the network topology manager module (3) is the main module of the system. It acts as coordinator of the rest of the modules of the system allowing the discovery, storage and management of the information of the network topology.
- This element (3) is only the core and implements the most generic logic to coordinate the rest of the modules, but to manage a specific type of device, you need the help of the device type modules (4,5, 6).
- NTM module (3) executes the following steps:
- the NTM module (3) acts as follows: when a notification is received indicating the discovery of a new device, it obtains the device identifier and type of the notification itself and searches the system for a module that implements the management interface NTM mapping that is capable of dealing with such devices. This interface is provided by the device type modules (4,5,6). Thanks to this interface, the NTM module obtains from the specific device type modules (4,5,6) the set of device data already transformed into the generic format to be stored in the network topology. Finally, this information will be stored in the network topology using the data management module (7).
- the NTM module also provides interfaces that allow other external entities (2) to access network topology information, obtain information about a device, invoke some action on a device, etc.
- external entities interested in such operations could be a local application that shows the end user of the network topology in a graphical user interface, or a TR069 Proxy that could convert the topology information in a TR069 tree and send it to an ACS, so that a remote operator can know in real time the network topology of the end user and be able to handle it.
- NTM (3) are as follows:
- NTM description interface this interface is used by external entities (2) to obtain the list of found devices and the information that is stored about them in the network topology.
- NTM device control interface this interface allows external entities to invoke services offered by the devices in order to control them.
- NTM event capture interface this is the interface that external entities need to implement and register in the system to be notified about the existence of new devices and changes in the information stored of existing ones.
- the device type modules (4,5,6) implement the specific logic that the NTM module (3) needs to deal with each specific type of device, such as knowing what type of information is obtained from a device of each type when It is discovered, how to treat this information and how to store it in the network topology.
- All this logic is separated from the NTM module so that the system is extensible and said NTM module may be able to deal with new types of devices in the future without modifying the logic of the NTM module itself.
- the system has provided three types of devices, but this list could be extended for a specific application.
- Such devices are: UPnP devices, non-IP home automation devices and IP devices that are not compatible with any other type of specific protocol.
- the NTM mapping management interface When one of the device type modules (4,5,6) starts, it registers its implementation of the NTM mapping management interface with a property that indicates the type of device it can manage. In this way, the NTM module can identify it and use it when such a device appears on the network.
- Basic configuration information file specifies how to obtain the basic information of the discovered device. This basic information is common to all devices.
- Additional configuration information file stores how to obtain additional information that may also be of interest, usually specific to each type of device.
- the additional information configuration file defines the information that is stored in the "Additional information" field of the device information.
- a “rule” (22) can be of one of three types:
- the data management module (7) is capable of managing the internal database that stores the network topology.
- the model information of a DLM level (virtual devices only) is also translated into an NTM model with physical and virtual devices, which groups virtual devices into physical devices based on IP and MAC addresses.
- a multimedia disk can be considered as an IP (virtual) device and as an UPnP (virtual) device, and both are grouped together on the same physical device.
- This block is accessed only through the NTM module (3) to obtain information about the devices stored in the network topology database and update the network topology with information of new devices that have been discovered or to update the information of an existing device.
- the data management module When the data management module starts, it registers its NTM data management interface in the system. This interface allows the NTM module to use all its functionality.
- the device can be a "device already detected” (52) in the case of an existing device type with the same UUID (50) or serial number (51), or a "new virtual device "(49) if the device type was not previously detected for that physical device (48).
- the MAC address has not been previously stored (41), its IP address is compared with the IP addresses of the devices already discovered (42). If the IP address of the device is not the same as the IP addresses of the devices already discovered (or the IP address is empty in the case of home automation devices) the UUID (53) or the serial number (54 ) to know if it is a "device already detected” (52) (usually home automation devices or on a computer with several network interfaces) or a "New device” (44). If the IP address matches an existing one (42) and the MAC address is empty (45) a "New device" (44) is created and the IP address of the device previously detected is deleted because it was bad or old.
- the IP address is deleted on the device previously detected as in the previous case, and then it is found out if it is of a "New device” (44) or, if it is a virtual device of the same type that exists (43), compare its UUID (53) and serial number (54) to know if it is a "device already detected” (52) or a "New device” (44).
- the notification module (8) is used by the NTM module (3) to notify the external entities (2) registered in the system of possible changes in the network topology, for example, a new device appears or disappears in the network, or when changes occur in the status of a device.
- the notification module (8) searches the system for all implementations of the NTM event listener interface and invokes it, so that any entity running this interface will be notified of changes in the network topology.
- the notification module (8) starts it registers its NTM notification interface in the system.
- the local device management module DLM (9) is in charge of the discovery of the existing devices in the home network, and the notification of such discoveries to the NTM module (3). It also allows the NTM module (3) to obtain information about the discovered devices and manage all the devices in the network topology.
- the local device management module (9) offers an abstract and generic interface to the NTM module (3) that allows working with different types of devices in a similar and easy way, making the NTM module you do not need to know the specific management problems of the different types of devices, especially in relation to the protocol of communication that is used to discover and manage a specific type of device.
- the local device management module (9) hides all this complexity through specific protocol adapters (10,11,12) that are able to discover and manage different types of devices (such as IP devices, UPnP devices, devices home automation, etc.).
- the interfaces exposed by this block are the following:
- ⁇ DLM publications capture interface this is the interface that other components need to use if they wish to be notified of devices discovered or disconnected from the network.
- DLM description interface this interface provides detailed information about the devices found, and allows other components to access this information.
- DLM control interface this interface is used to invoke actions provided by devices connected to the network.
- the protocol adapters (10,11,12) implement specific protocols to be able to communicate with a specific type of device. When they discover a new type of device of the type that is in the home network, they are notified to the local device management module (9). They are accessed through said local management module to obtain some information about a specific device or to invoke any service provided by said device.
- UPnP Protocol Adapter (11), to manage UPnP devices using the UPnP protocol.
- Domestic automation adapter (12) to manage non-IP devices through a home automation proxy, which must use standard protocols, for example ZWave or Zigbee, to communicate with home automation devices.
- IP protocol adapter (10) to discover IP devices in general that are not compatible with any other type of specific protocol. These devices are discovered through the ARP protocol.
- the protocol adapters expose the following interfaces:
- PA publications capture interface this interface must be applied to any entity that needs notifications of changes in the devices through the protocol adapter, such as the local device management module (9).
- PA layer description interface this interface is applied to any entity that needs to obtain information directly from the network devices, such as the local device management module (9).
- Layer control interface this interface applies to any entity that needs to invoke methods on network devices, such as the local device management module (9).
- ⁇ Layer event interface if the network devices have status variables that must be notified to any entity when they change, this interface must be applied to that entity, such as the local device management module (9).
- FIGS 5, 6 and 7 illustrate how network topology information is stored in the system.
- the "network topology” (60) is structured in a set of devices physical, "Device” node (61), for example, a PC, a MediaPlayer, an Ethernet disk, etc.
- Each physical device (62) contains the following information:
- a PC may have an UPnP media server and an UPnP media player.
- each virtual device, "virtual device” node (70) has the following information:
- device subtype (76) that stores the device subtype of the virtual device. These are the device subtypes intended for each "device type” in a preferred embodiment, but this list could be extended for a specific application:
- a “device subtype” selected from a media player, a media server and a wireless network camera.
- a “device subtype” selected from an intelligent meter, an intelligent connector and a switch.
- serial number node (80) that stores the serial number of the device.
- UDN UDN node (81) that stores the UDN of the device when it is an UPnP device.
- a "additional information” node which stores a list of "names” and “values” (84) of the devices, which can be used to extend the topology when necessary.
- the devices usually publish some generic parameters, stored in the "Information” node (72), but they can also publish additional specific parameters. These parameters are different depending on the type of device and subtype, and can be used or not by the NTM module depending on the use cases that must be applied.
- This node stores an extensible list of all these specific parameters.
- each "service” (85) contains the following information:
- the main functionality provided by the invention is to be able to manage the topology of the home network. This functionality consists of three different stages that are related to each other.
- the discovery of devices is always the first stage, the devices have to be discovered in order to be managed. This stage also includes the storage of the device information in the network topology, and the notification to the external entities subscribed about the discovery of devices.
- a new event is sent (101) by the corresponding protocol adapter (10,11,12) to the local management module of devices (9). At the same time, this event is forwarded (102) to the NTM module (3).
- the NTM module (3) searches for a device type module (5) that is capable of managing this type of device. When found, the NTM module asks the device type module (5) for basic device information (103).
- the device types module (5) obtains the necessary information from the devices: basic data (106,107), supported protocols (110,111) and published services (114,115) of the devices making requests: get basic data of the device (104,105), get protocol information (108,109) and get the device services (112,113) all of them using the local device management module (9), which in turn obtains this information by invoking analogous methods of the corresponding protocol adapter (10,11, 12).
- the device type module (5) has obtained all this information, returns it to the NTM module (116).
- the NTM module stores (117) this information in the network topology using the data management module (7).
- the data management module (7) checks if the device has been previously detected (118), if it was previously detected, updates the device data in the network topology network, and if you have not yet detected it, create a new device in the network topology and store your information and notify the NTM module (119).
- the NTM module (3) notifies (120) external entities (2) registered to events through the notification module (8).
- the notification module (8) sends to the NTM module (3) a return notification (121) of the previously sent notification (120) and a return event message (122) is sent from the previously sent event (101) ) to the protocol adapters (10,11,12).
- an external device (2) wants information (130) of a device, it uses the NTM description interface provided by the NTM module (3) to obtain it.
- the NTM module obtains (131) the requested information from the network topology database through the data management interface provided by the module data management (8) and forwarded (132,133) to the external entity (2).
- Figure 10 shows the sequence diagram of how external entities (2) can invoke actions on a device.
- the NTM device control interface provided by the NTM module (3) will be invoked (135), which in turn uses (136) the DLM control interface provided by the local device management module (9), and said local device management module will use (137) the PA layer control interface provided by the corresponding protocol adapter (10,11,12) to invoke said method .
- this response is forwarded (138,139,140) to the external entity.
Landscapes
- Engineering & Computer Science (AREA)
- Automation & Control Theory (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Multimedia (AREA)
- Computing Systems (AREA)
- Small-Scale Networks (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
Description
Claims
Priority Applications (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
EP10854366.1A EP2592781A1 (en) | 2010-07-08 | 2010-07-08 | Method and system for managing network topologies in home networks |
PCT/ES2010/070470 WO2012004424A1 (es) | 2010-07-08 | 2010-07-08 | Método y sistema de gestión de topologías de red en redes domésticas |
BR112013000207A BR112013000207A2 (pt) | 2010-07-08 | 2010-07-08 | sistema de gerenciamento de topologia de rede em redes domésticas e método de gerenciamento de topologia de rede em redes domésticas |
Applications Claiming Priority (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
PCT/ES2010/070470 WO2012004424A1 (es) | 2010-07-08 | 2010-07-08 | Método y sistema de gestión de topologías de red en redes domésticas |
Publications (1)
Publication Number | Publication Date |
---|---|
WO2012004424A1 true WO2012004424A1 (es) | 2012-01-12 |
Family
ID=45440789
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/ES2010/070470 WO2012004424A1 (es) | 2010-07-08 | 2010-07-08 | Método y sistema de gestión de topologías de red en redes domésticas |
Country Status (3)
Country | Link |
---|---|
EP (1) | EP2592781A1 (es) |
BR (1) | BR112013000207A2 (es) |
WO (1) | WO2012004424A1 (es) |
Families Citing this family (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO2014191353A1 (en) * | 2013-05-30 | 2014-12-04 | Thomson Licensing | Networked data processing apparatus |
JP5650816B1 (ja) * | 2013-07-17 | 2015-01-07 | 三菱電機株式会社 | 通信システム、通信装置、通信方法、及び、プログラム |
WO2018145267A1 (zh) * | 2017-02-08 | 2018-08-16 | 华为技术有限公司 | 一种转发器入网识别方法、sdn控制器及转发器 |
CN114363237A (zh) * | 2021-12-22 | 2022-04-15 | 苏州迈科网络安全技术股份有限公司 | 家庭组网设备网络拓扑识别方法、装置、终端及存储介质 |
-
2010
- 2010-07-08 BR BR112013000207A patent/BR112013000207A2/pt not_active IP Right Cessation
- 2010-07-08 WO PCT/ES2010/070470 patent/WO2012004424A1/es active Application Filing
- 2010-07-08 EP EP10854366.1A patent/EP2592781A1/en not_active Withdrawn
Non-Patent Citations (3)
Title |
---|
"All ProjectLeaflets Initial and Final leaflets", CELTIC CALL, vol. 4, 2007, pages 17 - 18, XP008175133 * |
"Next Generation Home. Project Information. Celtic", 17 March 2010 (2010-03-17), XP055111736, Retrieved from the Internet <URL:http://www.celticplus.eu/pub/Project-leaflets/Webquality/GENIO-Leaflet_lq.pdf> [retrieved on 20110309] * |
A. H. CERVANTES ET AL., OSGI IN A NUTSHELL, 2 November 2004 (2004-11-02), XP055111741 * |
Also Published As
Publication number | Publication date |
---|---|
BR112013000207A2 (pt) | 2019-09-24 |
EP2592781A1 (en) | 2013-05-15 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP3172859B1 (en) | Interworking light weight machine-to-machine protocol with device management protocol | |
Datta et al. | A lightweight framework for efficient M2M device management in oneM2M architecture | |
JP5996660B2 (ja) | ルータを通じた仮想化された可視性の提供 | |
JP2018506868A (ja) | モノのインターネット(IoT)デバイスのための接続性モジュール | |
BR112015032501B1 (pt) | Meio legível em computador não transitório, método para enviar e receber mensagens entre dispositivos em uma rede em malha e dispositivo eletrônico | |
KR100867988B1 (ko) | 센서노드 주소 관리 데이터 구조를 포함하는 데이터가 기록된 컴퓨터로 읽을 수 있는 기록매체 및 그 방법 | |
EP1307998A2 (en) | Server-based multi-standard home network bridging | |
CN104883266A (zh) | 网络配置访问方法及装置 | |
WO2012004424A1 (es) | Método y sistema de gestión de topologías de red en redes domésticas | |
Navarro et al. | An integrated network and data management system for heterogeneous WSNs | |
JP4799005B2 (ja) | 情報処理装置 | |
Žitnik et al. | Architecture of standard-based, interoperable and extensible IoT platform | |
EP3025475B1 (en) | Xmpp based upnp device architecture for cloud computing in a network environment | |
BR102014003580B1 (pt) | Método para habilitar a arquitetura hierárquica de gateways para gerenciamento de dispositivos | |
Hussain et al. | Management and plug and play of sensor networks using SNMP | |
Schuster et al. | Global-scale federated access to smart objects using xmpp | |
Saito et al. | Development of echonet lite-compliant home appliances control system using pucc protocols from smart devices | |
JP4515489B2 (ja) | 情報管理装置及び情報管理方法 | |
WO2015059128A1 (en) | A forwarder selection protocol for a network and a respective cpe device | |
CN113381875B (zh) | 用于获取配置数据的方法 | |
Ishikawa et al. | Overlay networking protocols and device metadata for controlling and managing home networks and appliances | |
JP2015046716A (ja) | 通信ノード及びネットワークシステム及び機器制御方法 | |
Agyemang et al. | Resource-oriented architecture toward efficient device management and service enablement | |
JP5731964B2 (ja) | 機器管理システム、機器管理方法および機器管理プログラム | |
Tsunoda et al. | Dynamically updatable UPnP service for device role management |
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: 10854366 Country of ref document: EP Kind code of ref document: A1 |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2010854366 Country of ref document: EP |
|
NENP | Non-entry into the national phase |
Ref country code: DE |
|
REG | Reference to national code |
Ref country code: BR Ref legal event code: B01A Ref document number: 112013000207 Country of ref document: BR |
|
ENP | Entry into the national phase |
Ref document number: 112013000207 Country of ref document: BR Kind code of ref document: A2 Effective date: 20130104 |