WO2010071319A2 - Système d'automatisation de construction et procédé d'automatisation de construction faisant appel à ce dernier - Google Patents

Système d'automatisation de construction et procédé d'automatisation de construction faisant appel à ce dernier Download PDF

Info

Publication number
WO2010071319A2
WO2010071319A2 PCT/KR2009/007374 KR2009007374W WO2010071319A2 WO 2010071319 A2 WO2010071319 A2 WO 2010071319A2 KR 2009007374 W KR2009007374 W KR 2009007374W WO 2010071319 A2 WO2010071319 A2 WO 2010071319A2
Authority
WO
WIPO (PCT)
Prior art keywords
request
protocol
building
building device
response
Prior art date
Application number
PCT/KR2009/007374
Other languages
English (en)
Korean (ko)
Other versions
WO2010071319A3 (fr
Inventor
백운학
안평길
김지훈
Original Assignee
삼성에스디에스 주식회사
이광철
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 삼성에스디에스 주식회사, 이광철 filed Critical 삼성에스디에스 주식회사
Publication of WO2010071319A2 publication Critical patent/WO2010071319A2/fr
Publication of WO2010071319A3 publication Critical patent/WO2010071319A3/fr

Links

Images

Classifications

    • 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/01—Protocols
    • H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F15/00—Digital computers in general; Data processing equipment in general
    • G06F15/16—Combinations of two or more digital computers each having at least an arithmetic unit, a program unit and a register, e.g. for a simultaneous processing of several programs
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/08—Protocols for interworking; Protocol conversion

Definitions

  • the present invention relates to a building automation system and a building automation method using the same, and more particularly, to a building automation system supporting mutual compatibility of two or more building devices using different protocols and a building automation method using the same.
  • BAS Building Automation System
  • CCMS Central Control Management System
  • DDC Direct Digital Controller
  • Local Devices Local Devices
  • Building automation system comprises a first building device for communicating using the BACnet protocol; A second building device in communication using a first non-backnet protocol; And a virtual standard support device that makes the first building device compatible with the second building device compatible with each other.
  • the first building device communicates with at least one first object using a BACnet protocol
  • the second building device uses at least one second object with a BACnet protocol.
  • the virtual standard support device converts the first non-backnet protocol into the backnet protocol to transmit information to the first building device, and converts the backnet protocol into the first non-backnetnet protocol.
  • Information may be transmitted to a second building device to make the first and second building devices compatible with each other.
  • the virtual standard support device is further configured to receive a request from the first building device, convert the received request into a first non-backnet protocol used by the second building device, and switch to the first backnet protocol. The requested request to the second building device.
  • the virtual standard support device may include a router that receives a request from the first building device, identifies a destination of the received request, and routes the determined destination to a controller in charge of the identified destination; A first controller that receives the request from the router and interprets and sends the request; And a gateway for converting a request received from the first controller to the first non-backnet protocol and transmitting the converted request to the second building device.
  • the gateway receives the processed response from the second building device, converts the received response into the backnet protocol, and transmits the response to the first controller, and the first controller sends a routing of the response to the router. Requesting, the router may send the response to the first building automation device.
  • the gateway may support at least one of TCP, UDP, Serial, and OPC.
  • the building automation system may further include a database storing information on protocols used by the first and second building devices, information on the first and second objects, and the like; And an agent for providing information stored in the database to the virtual standard support device.
  • the agent may initialize the router and the first controller based on the information stored in the database.
  • the building automation system may further include a third building device that communicates with the plurality of third objects using a second non-vacant protocol.
  • the virtual standard support device may make the second and third building devices compatible with each other, or the first building device and the third building device.
  • the virtual standard support device may further include a router that receives a request from the first building device, identifies a destination of the received request, and routes the determined destination to a controller in charge of the confirmed destination; A second controller that receives the request from the router and interprets and sends the request; And a gateway for converting the request received from the second controller to the second non-backnet protocol and transmitting the converted request to the third building device.
  • the virtual standard support device may include: a gateway configured to transmit a request received from the second building device to a backnet protocol; A router that receives a request converted from the gateway to the backnet protocol, identifies a destination of the received request, and routes it to a controller in charge of the confirmed destination; And a second controller configured to receive, interpret, and transmit the request from the router, wherein the gateway converts the request received from the second controller into a second non-Vannet protocol and converts the converted request into a third Send to building device.
  • the gateway receives the processed response from the third building device, converts the response to the backnet protocol, sends the converted response to the second controller, and the second controller sends the response to the router.
  • Request routing for a response the router routes the response to the first controller, the first controller sends the received response to the gateway, and the gateway sends the response to the first non-backnet protocol Switch to transmit to the second building device.
  • a building automation method comprising: receiving a request from a first building device communicating using a BACnet protocol; Confirming the destination of the request to perform routing; Sending the request to a gateway to process the request; And converting the request into a non-backnet protocol and transmitting it to a second building device that communicates using the non-backnet protocol.
  • the building automation method also includes receiving a processed response from the second building device; Converting the received response to the backnet protocol; And transmitting the response converted to the backnet protocol to the first building device.
  • a building automation method includes: receiving a request from a first building device communicating using a first BACnet protocol; Converting the first non-backnet protocol to a backnet protocol; Confirming the destination of the request converted to the backnet protocol and performing routing; Sending the request to a gateway to process the request; Converting the request to a second non-bagnet protocol and transmitting it to a second building device in communication using the second non-bagnet protocol.
  • the building automation method also includes receiving a processed response from the second building device; Converting the received response to the backnet protocol; Confirming the destination of the response converted to the backnet protocol and performing routing; Sending the response to the gateway to process the response; And converting the response into the first non-backnet protocol and transmitting it to the first building device.
  • two or more buildings using different protocols may be converted into a backnet protocol or a backnet protocol through a virtual standard support device. It can support interoperability of devices.
  • FIG. 1 is a conceptual diagram schematically showing the configuration of a building automation system according to an embodiment of the present invention.
  • FIG. 2 is a block diagram of the virtual standard support device shown in FIG. 1.
  • FIG. 3 is a block diagram illustrating a communication process between a first building device and a second building device.
  • FIG. 4 is a flowchart illustrating a communication process illustrated in FIG. 3.
  • FIG. 5 is a block diagram illustrating a communication process between a second building device and a third building device according to another embodiment of the present invention.
  • FIG. 6 is a flowchart illustrating a communication process of FIG. 5.
  • FIG. 1 is a conceptual diagram schematically showing the configuration of a building automation system according to an embodiment of the present invention
  • Figure 2 is a block diagram of a virtual standard support apparatus shown in FIG.
  • the building automation system 400 includes a first building device 100, a second building device 200, and a virtual standard support device 300.
  • the first building device 100 includes a first central monitoring computer MMI1, a first network controller NC, and a plurality of direct digital controllers DDC1 and DDC2. It includes at least one.
  • control information devices DDC1 and DDC2 are included in the first building device 100
  • a greater number of control information devices may be included, and the control information devices may be mutually different. Can be connected in a subordinate relationship.
  • the plurality of control information devices may be connected to the first central monitoring computer MMI1 or other high level servers (not shown) through the first network controller NC1.
  • the control information devices DDC1 and DDC2 receive information from an object in a building, such as a sensor, a valve, or a damper, and transmit the information to the first central monitoring computer MMI1 through the first network controller NC1. Therefore, the first building device 100 may automatically control the objects.
  • the first building device 100 communicates between the control information devices DDC1 and DDC2 and the first central monitoring computer MMI1 using its own protocol.
  • the first protocol of the first building device 100 may be a BACnet protocol.
  • the second building device 200 includes at least one of the second central monitoring computer MMI2, the second network controller NC2, and the plurality of control information devices DDC3 and DDC4. Since the configuration of the second building device 200 is similar to that of the first building device 100, a description of the configuration of the second building device 200 is omitted. As an example of the present invention, the second building device 200 communicates between the control information devices DDC3 and DDC4 and the second central monitoring computer MMI2 using a non-backnet protocol.
  • the virtual standard support device 300 serves to make the first and second building devices 100 and 200 compatible with each other. That is, the virtual standard support device 300 converts the request message transmitted through the backnet protocol of the first building device 100 into the non-backnetnet protocol of the second building device 200 and provides it to the second building device 200. In response, the response message transmitted through the non-backnet protocol of the second building device 200 is converted into the backnet protocol and provided to the first building device 100.
  • a virtual standard device is a non-backnetnet protocol. It can function to make building and non-backnet protocol building compatible. That is, when the non-backnet protocol building device ⁇ intends to transmit a request message to the building device ⁇ using another non-backnet protocol through the virtual standard device, the virtual standard device may operate as follows.
  • the virtual standard device knows which building device ⁇ wants to send a message to after converting the message from building device ⁇ into the backnet protocol format. For example, to send a message to building device ⁇ , the request message is converted back to the protocol used in building device ⁇ and forwarded to building device ⁇ .
  • the virtual standard support device 300 may include a virtual network controller (VNC) 311 including a router, a virtual advanced application controller (VAAC) 312, 332, and 342. , Gateway 313, database 321, and agent 322.
  • VNC virtual network controller
  • VAAC virtual advanced application controller
  • the first building device 100 uses the backnet protocol
  • the VNC 311 requests from the first building device 100 (shown in FIG. 1) to the second building device.
  • the VNC 311 checks the destination of the received request message and determines which VAAC to go to and routes it.
  • VAAC 312, 332, 342 is assigned to each device
  • VAAC 312 is assigned to the second building device
  • VAAC 332 is assigned to the fourth building device
  • VAAC 342 Assume that is in the fifth building device.
  • the fourth building device is at least one of a central monitoring computer MMI1, a network controller NC, and a plurality of direct digital controllers DDC1, DDC2.
  • the fifth building device is at least one of a central monitoring computer MMI1, a network controller NC1, and a plurality of direct digital controllers DDC1, DDC2.
  • the VNC 311 confirms that the received destination device is the second building device, and transmits (ie, routes) the message to the VAAC 312 corresponding to the second building device.
  • the VAAC 312 receives the request message from the VNC 311, interprets the request message, and sends it to the gateway 313.
  • the VAAC 312 transmits a reply directly to the VAAC 312 if the message requested from the VNC 311 determines which service is requested and can be immediately determined, but if it is necessary to obtain data from the device.
  • the request message is transmitted to the gateway 313.
  • the service that can be immediately determined can be immediately answered without asking the device to be requested whether the device to be requested is read, written, or both read and write. Do.
  • the data is transmitted to the gateway 313 since such data needs to be obtained from the corresponding device.
  • services supported by the BACnet protocol include Read Value, Write Value, Read Value Batch, Write Value Batch, Register Object, Delete Object, Alarm Notification, Alarm Response, Alarm Summary, Target Query, Target Response, and Time Synchronization.
  • the VAAC 312 when a service request comes from a device supporting a backnet protocol or a non-backnet protocol, determines whether such a service is supported, and if it can be answered immediately (e.g. And the like, but the request message is transmitted to the gateway 313.
  • the gateway 313 converts the request message composed of the backnet protocol into the non-backnet protocol (i.e., the protocol used in the second building device), and converts the converted request message into the second building device 200 (shown in FIG. 1). send.
  • the non-backnet protocol i.e., the protocol used in the second building device
  • the gateway 313 may transmit a message converted to a non-backnet protocol in various ways, for example, TCP, UDP, Serial, or OPC.
  • TCP Transmission Control Protocol
  • UDP User Datagram Protocol
  • Serial or OPC
  • Such TCP, UDP, Serial, or OPC and the like are exemplary and not limited thereto.
  • the gateway 313 receives a response message consisting of the non-backnet protocol processed from the second building device 200, converts the received response message into a backnet protocol, and sends it to the VAAC 312.
  • the VAAC 312 requests the VNC 311 to route the response message, and the VNC 311 sends a response message composed of a backnet protocol to the first building device 100 (shown in FIG. 1).
  • the gateway 313 includes a means for protocol conversion of devices using the non-backnet protocol (hereinafter referred to as "driver"), thereby providing compatibility between the device using the backnet protocol and the device using the non-backnet protocol. It can be simple. In other words, by allowing the gateway 313 to provide a driver of a device using a non-backnet protocol in advance, compatibility between devices using different protocols can be easily implemented.
  • driver protocol conversion of devices using the non-backnet protocol
  • the database 321 may include information about protocols used by the first and second building devices 100 and 200, and information about the first and second objects included in the first and second building devices, respectively.
  • attribute information of the VNC 311 and the VAAC 312 are stored.
  • the attribute information of the VNC 311 and the VAAC 312 may include not only the network address of the backnet required for the device to communicate with, but also various parameter values required for the communication. For example, information about packet size, or whether segmentation is supported or not is included.
  • Agent 322 initializes VNC 311 and VAAC 312, 332, 342 based on the information stored in database 321.
  • the first building device is described as one and the second building device is described as one, but each of these buildings may include a plurality of devices. If it includes a plurality of devices, VAAC is provided with the corresponding number.
  • the device may be, for example, HAVC (Heating, Ventilation, Air Conditioning), lighting device, sensor, etc., each device may have at least one point of control. Points are responsible for measuring and controlling the actual data on the device, and the state of the point can be detected either as numerical or as status data (e.g. binary or analog form) indicating the situation at the site.
  • HAVC Heating, Ventilation, Air Conditioning
  • FIG. 3 is a block diagram illustrating communication between the first building automation device and the second building automation device
  • FIG. 4 is a flowchart illustrating the communication process illustrated in FIG. 3.
  • the VNC 311 receives a request message made of a backnet protocol from the first building device 100 (S401).
  • the VNC 311 checks and routes the destination of the received request message (S402).
  • information about the destination of the request message may be compared with information previously stored in the routing table, and the routing may be performed to match the previously stored information.
  • the routing table may be a VAAC list corresponding one to one to the device.
  • the VAAC 312 receives the request message from the VNC 311, and interprets the request message to determine whether the service is a supported service (S403). As a result of the determination, if the service is supported, the request message is transmitted to the gateway 313 (S404). However, if the service does not support an error is returned (S405). The gateway 313 converts the request message composed of the backnet protocol to the non-backnet protocol and transmits the converted request message to the second building device 200 (S406).
  • the gateway 313 receives a response message composed of the non-backnet protocol processed from the second building device 200 (S407).
  • the gateway 313 converts the received response message into a backnet protocol and transmits the result to the VAAC 312 (S408).
  • the VAAC 312 requests the VNC 311 to route the response message, and the VNC 311 transmits the response message composed of the backnet protocol to the first building device 100 (S409).
  • the first building device 100 using the backnet protocol and the second building device 200 using the non-backnet protocol may be mutually compatible through the virtual standard support device.
  • FIG. 5 is a block diagram illustrating communication between a second building device and a third building device according to another embodiment of the present invention
  • FIG. 6 is a flowchart illustrating a communication process of FIG. 5.
  • the gateway 313 receives a request message made up of a first non-backnet protocol from the second building device 200 (S601).
  • the gateway 313 converts the request message to the backnet protocol and transmits the converted request message to the VAAC 312 (S602).
  • the VAAC 312 transmits a request message to the VNC 311, and the VNC 311 checks and routes the destination of the request message (S603).
  • the request message is routed to the VAAC 314 corresponding to the third building device 500, the VAAC 314 receives the request message from the VNC 311, and the request message.
  • the service is determined to determine whether the service is supported (S604). As a result of the determination, if the service is supported, the request message is transmitted to the gateway 313 (S606). However, if the service does not support, an error is returned (S605).
  • the gateway 313 converts the request message composed of the backnet protocol to the second non-backnet protocol and transmits the converted request message back to the third building device 500 (S607).
  • the gateway 313 receives a response message composed of the second non-backnet protocol processed from the third building device 500 (S608).
  • the gateway 313 converts the received response message into a backnet protocol and transmits it to the VAAC 314 (S609).
  • the VAAC 314 requests the VNC 311 to route the response message, and the VNC 311 routes the response message composed of the backnet protocol to the corresponding destination (that is, the VAAC 312) (S610).
  • the VAAC 312 receives a response message from the VNC 311 and transmits the received response message to the gateway 313 (S611).
  • the gateway 313 converts the received response message back to the first non-backnet protocol and transmits it to the second building device 200 (S612).
  • the second building device 200 using the first non-bagnet protocol and the third building device 400 using the second non-bagnet protocol may be mutually compatible through the virtual standard support device 300.

Landscapes

  • Engineering & Computer Science (AREA)
  • Signal Processing (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Hardware Design (AREA)
  • Computer Security & Cryptography (AREA)
  • General Engineering & Computer Science (AREA)
  • Health & Medical Sciences (AREA)
  • Computing Systems (AREA)
  • General Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • General Physics & Mathematics (AREA)
  • Physics & Mathematics (AREA)
  • Software Systems (AREA)
  • Computer And Data Communications (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Communication Control (AREA)

Abstract

La présente invention concerne un système d'automatisation de construction ainsi qu'un procédé d'automatisation de construction faisant appel à ce dernier et consistant à recevoir un message de demande en provenance d'un premier dispositif de construction qui communique au moyen d'un protocole BACnet, à vérifier la destination du message de demande et à réaliser un routage, puis à transmettre le message de demande à une passerelle en vue du traitement dudit message de demande. La passerelle convertit le message de demande en un protocole non BACnet et transmet le message de demande converti à un second dispositif de construction qui communique au moyen d'un protocole non BACnet. Par la suite, la passerelle reçoit un message de réponse en provenance du second dispositif de construction, convertit le message de réponse reçu en protocole BACnet, et transmet le message de réponse converti au premier dispositif de construction. La mise en oeuvre de ce procédé permet d'établir une compatibilité entre les deux dispositifs de construction qui utilisent des protocoles différents.
PCT/KR2009/007374 2008-12-17 2009-12-10 Système d'automatisation de construction et procédé d'automatisation de construction faisant appel à ce dernier WO2010071319A2 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
KR1020080128597A KR101002561B1 (ko) 2008-12-17 2008-12-17 빌딩 자동화 시스템 및 이를 이용한 빌딩 자동화 방법
KR10-2008-0128597 2008-12-17

Publications (2)

Publication Number Publication Date
WO2010071319A2 true WO2010071319A2 (fr) 2010-06-24
WO2010071319A3 WO2010071319A3 (fr) 2010-09-10

Family

ID=42269212

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2009/007374 WO2010071319A2 (fr) 2008-12-17 2009-12-10 Système d'automatisation de construction et procédé d'automatisation de construction faisant appel à ce dernier

Country Status (2)

Country Link
KR (1) KR101002561B1 (fr)
WO (1) WO2010071319A2 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140344427A1 (en) * 2013-05-20 2014-11-20 Trane International Inc. Device and method for automatic switching of communication protocol of network devices based on user action
CN110741605A (zh) * 2017-06-21 2020-01-31 西门子瑞士有限公司 用于隔离BACnet/IP建筑物自动化网络中的设备通信的系统和方法

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR101937203B1 (ko) * 2012-02-22 2019-04-09 엘지전자 주식회사 설비 관제 시스템 및 이의 운전 방법

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20070072260A (ko) * 2005-12-31 2007-07-04 엘지전자 주식회사 빌딩제어시스템 및 그 동작방법
KR20080070439A (ko) * 2007-01-26 2008-07-30 엘지전자 주식회사 멀티에어컨의 제어시스템 및 제어방법

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20070072260A (ko) * 2005-12-31 2007-07-04 엘지전자 주식회사 빌딩제어시스템 및 그 동작방법
KR20080070439A (ko) * 2007-01-26 2008-07-30 엘지전자 주식회사 멀티에어컨의 제어시스템 및 제어방법

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20140344427A1 (en) * 2013-05-20 2014-11-20 Trane International Inc. Device and method for automatic switching of communication protocol of network devices based on user action
US9762445B2 (en) * 2013-05-20 2017-09-12 Trane International Inc. Device and method for automatic switching of communication protocol of network devices based on user action
US10326659B2 (en) 2013-05-20 2019-06-18 Trane International Inc. Device and method for automatic switching of communication protocol of network devices based on user action
CN110741605A (zh) * 2017-06-21 2020-01-31 西门子瑞士有限公司 用于隔离BACnet/IP建筑物自动化网络中的设备通信的系统和方法

Also Published As

Publication number Publication date
KR20100070009A (ko) 2010-06-25
WO2010071319A3 (fr) 2010-09-10
KR101002561B1 (ko) 2010-12-17

Similar Documents

Publication Publication Date Title
CN101610513B (zh) 无线通信系统、无线lan连接装置和中继装置
WO2012067382A2 (fr) Procédé permettant d'établir une connexion réseau, procédé permettant une connexion à un réseau et groupe de communication sans fil qui applique ces procédés
WO2010041914A2 (fr) Procédé et appareil de résolution de collision d'adresses ip dans un service d'accès à distance
WO2012096438A2 (fr) Procédé de transmission de message de poussée
WO2011099690A2 (fr) Procédé et appareil pour utiliser un service de dispositif de réseau domestique sur la base d'un accès à distance
WO2015020502A1 (fr) Technique de découverte de service dans un réseau de communication sans fil pour former un groupe p2p
KR20100072360A (ko) 네트워크 시스템
EP2665977A2 (fr) Système de commande central et procédé destiné à définir un point de commande associé à ce système
WO2010071319A2 (fr) Système d'automatisation de construction et procédé d'automatisation de construction faisant appel à ce dernier
WO2015152435A1 (fr) Système de réseau à couche de division basée sdn
EP3182679A1 (fr) Appareil, système et procédé de synchronisation d'informations
WO2022114612A1 (fr) Dispositif de passerelle pour communication de données de protocole de communication hétérogène et procédé pour son réglage
EP3442174A1 (fr) Dispositif de relais de capteur et système de relais de capteur
WO2018117301A1 (fr) Passerelle ido permettant de fournir simultanément des services ido locaux et mondiaux
WO2013109012A1 (fr) Appareil et procédé permettant à un terminal de gérer un service fourni depuis un serveur
JP4534719B2 (ja) ゲートウェイ装置
WO2020171307A1 (fr) Système de gestion de tableaux de commutation à l'aide d'un réseau en anneau
WO2015099241A1 (fr) Système de réseau d'usine
JP2001186196A (ja) インターネットによる通信が可能な電話通信装置と主電話制御装置
WO2014061997A1 (fr) Appareil et procédé pour la prise en charge d'un accès à plusieurs hôtes
WO2013085089A1 (fr) Procédé d'utilisation de ressource de réseau de communication dans un environnement de nuage m2m et système correspondant
WO2011027978A2 (fr) Passerelle de l'ubiquité pour ville de l'ubiquité, et système et procédé de traitement de message la comprenant
WO2015093770A1 (fr) Système de réseau m2m, passerelle m2m, et procédé d'installation de module logiciel dans une passerelle m2m, pour exécuter une transmission de données avec un dispositif
WO2020105765A1 (fr) Procédé et système de liaison à une plateforme m2m à l'aide d'une communication lora
WO2012169724A1 (fr) Dispositif d'information et procédé permettant à un terminal d'y accéder

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: 09833597

Country of ref document: EP

Kind code of ref document: A2

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 09833597

Country of ref document: EP

Kind code of ref document: A2