[go: up one dir, main page]

WO2012070960A1 - Concentrateur pour réseaux de capteurs et compteurs distants, prenant en charge diverses technologies d'accès réseau, avec stratégies de récupération automatique et sécurité d'accès aux capteurs - Google Patents

Concentrateur pour réseaux de capteurs et compteurs distants, prenant en charge diverses technologies d'accès réseau, avec stratégies de récupération automatique et sécurité d'accès aux capteurs Download PDF

Info

Publication number
WO2012070960A1
WO2012070960A1 PCT/PT2011/000011 PT2011000011W WO2012070960A1 WO 2012070960 A1 WO2012070960 A1 WO 2012070960A1 PT 2011000011 W PT2011000011 W PT 2011000011W WO 2012070960 A1 WO2012070960 A1 WO 2012070960A1
Authority
WO
WIPO (PCT)
Prior art keywords
sensor
network
concentrator
layer
remote
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/PT2011/000011
Other languages
English (en)
Portuguese (pt)
Inventor
Luís Miguel RIBEIRO TEIXEIRA
Mirones Victor Manuel Gutierres
Inês DE FREITAS OLIVEIRA
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
PORTUGAL TELECOM INOVACAO SA
Original Assignee
PORTUGAL TELECOM INOVACAO SA
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 PORTUGAL TELECOM INOVACAO SA filed Critical PORTUGAL TELECOM INOVACAO SA
Publication of WO2012070960A1 publication Critical patent/WO2012070960A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

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/283—Processing of data at an internetworking point of 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/2823—Reporting information sensed by appliance or service execution status of appliance services in a home automation network
    • H04L12/2825—Reporting to a device located outside the home and the home network
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/12—Applying verification of the received information
    • 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
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L2463/00—Additional details relating to network architectures or network communication protocols for network security covered by H04L63/00
    • H04L2463/121—Timestamp

Definitions

  • CGW Concentrator Gateway
  • the present invention applies intelligent sensor networks and remote meter systems and is a multi-purpose control system that acts as a hub for sensor networks, including support for a plurality of different access technologies available, such as UMTS / GPRS, ADSL and GPON, supported on the operator network to access a central management system.
  • the present invention ensures complete transparency for the technology used, and it is possible to switch between technologies whenever a particular connection fails.
  • the invention supports a web interface for local management (remotely accessible). Backup Mechanisms are also made available.
  • the core of the system is a processing unit responsible for completely isolating the sensor transport network or the sensor network.
  • the processing unit has some intelligence, controlling the two-way flow of information and effectively isolating the management plan from the service provider side.
  • the sensor interface layer comprises a variety of protocols and means, allowing transparent access to the sensor network, regardless of the underlying technology / protocol, and facilitating hardware upgrades while keeping said stack intact.
  • the transport network layer comprises low-level controllers to handle the included access methods. Namely, this layer includes drivers for supported access network technologies.
  • the central processing layer concentrates intelligence, dealing with network scanning and recovery options. It has abstract interfaces for both sensor and transport network interface layers, allowing simple control of the integration of new services.
  • the central processing layer defines data models for expected sensor readings and enables conversion of sensor interface layer data to common metrics and structure. This effectively simplifies the addition of new sensor types to the sensor network.
  • the central processing layer provides identification of clients with active services. It usually gathers information from all sensors, with the sensor interface layer filtered for inactive clients, making it possible to distinguish the state of the client.
  • the software stack implements a complete abstraction with the hardware layers, enabling simple upgrades of sensor network technologies and coexistence of multiple sensor types and technologies on the same network, a problem often faced by service providers in rapidly evolving networks.
  • a difficulty for service providers implementing remote measurements is the integrity of the sensor network itself. It should not be possible to connect arbitrary sensors to the network by third parties and tampering with the sensors should be detected and reported to the service provider.
  • the present invention solves this problem by incorporating sensor logging and error checking into their readings with an alarm mechanism that communicates these problems to the service provider's data center.
  • Transport network reliability is ensured by a recovery mechanism implemented in the software stack, which automatically switches between access methods under certain interruption conditions. This also applies to sensor domains.
  • the software stack is modular and exports a complete set of Application Programmer Interfaces (APIs) to multiple subsystems, allowing service providers to build their own applications and services on the platform, reducing time to market for future applications.
  • APIs Application Programmer Interfaces
  • CGW's high-level software architecture matches the hardware architecture specified in the CGW product description. There are three main software layers, aligned with the three fundamental hardware blocks as shown in Figure 1.
  • the sensor interface layer comprises low level controllers for access to the sensor network through different protocols and means. It also implements a hardware abstraction layer, providing a set of well-defined Application Programming Interfaces (APIs) that allow transparent access to the sensor network, regardless of the underlying technology / protocol.
  • APIs Application Programming Interfaces
  • the role of the CGW network side transport network layer corresponds to the role of the CGW sensor side sensor interface layer. It comprises low level controllers to handle the included access methods.
  • the network layer of Transport includes GPON, GPRS / EDGE / UMTS and ADSL controllers. It also defines the APIs that control whether uplinks are active and the status of the various options. The decision to use an uplink, dealing with network scan and recovery options, is the responsibility of the central processing layer using the provided APIs.
  • the central processing layer concentrates all the intelligence of CGW. It includes interfaces to service provider management protocols and provides the platform on which services can be created in CGW. Interfaces to the sensor and transport network interface layers are abstracted to make it easier to handle new service integration.
  • the central processing layer defines data models for expected sensor readings and enables conversion of sensor interface layer data to common metrics and structures. This effectively simplifies the addition of new sensor types to the sensor network, leaving interpretation of the results to the service provider's data center.
  • the central processing layer also collects the information from all customer sensor networks enabling optimized collection management, distinguishing active and non-active customers, and the sensor interface layer should be inhibited for non-active customers.
  • the central processing layer also collects the information from all customer sensor networks enabling optimized collection management, distinguishing active and non-active customers, and the sensor interface layer should be inhibited for non-active customers.
  • the complete configuration of the CGW is accomplished through the central processing layer, by remote access from the service provider's data center or locally by the technician at the installation site.
  • the concentrator for networked sensors and remote counters subject to the invention guarantees a clear and safe separation between the blocks (hardware and software) of the sensor interface layer and the transport network layer.
  • the main purpose of the sensor interface layer is to enable the abstraction of sensor access technology from the rest of the CGW software stack. From a logical perspective, the layer includes the low-level drivers corresponding to the current CGW hardware revision, an internal adaptation, a control and configuration layer and defines APIs for use directly by the central processing layer.
  • the sensor interface layer is shown in figure 2.
  • the sensor interface layer maintains an internal configuration layer, which in turn is configured by the central processing layer.
  • the goal is to maintain an internal configuration of which sensors use a particular technology and what capabilities actually implement, while maintaining generic APIs and providing the appropriate internal checks.
  • An example is the setting of a sensor, when installed, as "read only" and cannot be consulted.
  • the central processing layer attempts to use an API to access the sensor in real time (possible in a scenario where the service provider may issue these requests from the data center without prior knowledge of the underlying technology of a particular sensor)
  • the sensor interface layer itself emits a signal indicating that the read information is not actual but rather the last known measure.
  • Another purpose of the settings layer is to maintain a database of authorized sensors in the CGW. Although registration of a new sensor is actually accomplished by the central processing layer, the sensor interface layer verifies that certain access is made to an authorized sensor.
  • An example is a customer attempting to connect a sensor to the existing network.
  • the central processing layer With proper sensor configuration, although authentication at the central processing layer fails, it can be accessed remotely by the service provider with the correct API. In this case, the sensor interface layer emits a signal indicating that, although access is successful, the sensor is not actually part of the service provider's network.
  • the CGW will support by default the controllers for the following communication protocols: Power Line Communication (PLC), Zigbee, Wi-Fi, RS 232 and RS 585. Controllers for sensor domains are also integrated and may differ from access network drivers. Other drivers may be added in the near future.
  • PLC Power Line Communication
  • Zigbee Zigbee
  • Wi-Fi Wireless Fidelity
  • the sensor interface layer is compatible with ⁇ and incorporates drivers for client network (s) network interfaces and supports isolation mechanisms that enable different domains or sensor networks to be supported by supporting different clients.
  • s client network
  • the transport network layer is responsible for presenting a unified network interface to the central processing layer. Similar to the role of the sensor interface layer for the sensor side of the CGW, the transport network layer includes all the controllers needed to handle the choices of network uplinks present in a given CGW hardware version. See figure 3.
  • the transport network layer will maintain the current state of each option, opting for alternatives in the event of a breach of a higher priority choice.
  • the transport network layer is compatible with
  • the central processing layer is the entry point for all CG functionality. Provides a system management and configuration interface for the service provider data center and authorized local users.
  • the authentication block of sensors and hardware abstraction handles software transactions with the sensor interface layer.
  • the network access and control block handles transactions between the central processing layer and the transport network layer.
  • the central processing layer is shown in figure 4.
  • a well-defined set of APIs are exported to control the core functionality of the central processing layer for use by service applications and services. This is a logical space for building services and applications on top of the basic CGW software stack.
  • CGW core services are built on top of these APIs, but the service provider is free to create their own applications and services, taking advantage of the underlying software stack and the provided APIs.
  • the central processing layer includes a service scheduler to handle multiple concurrent service requests, and automated services that require CGW read or communication initiation.
  • a service scheduler to handle multiple concurrent service requests, and automated services that require CGW read or communication initiation.
  • the system management and configuration block controls the configuration of the CGW software stack and the CGW hardware itself.
  • CGW's central configuration consists of key and value data structures that reflect the hardware configuration of CGW.
  • the block provides a web server for local configuration by authorized technicians and remote by the service provider's data center if the service provider wants to create its own management infrastructure. Alternatively, management can be done using management interfaces running on the central transport network, readily accessible by service providers.
  • CGW allows configuration of local accounts accessible via the local management web interface. These accounts can be set with different privileges, restricting access to specific services and applications.
  • the system management and configuration block is shown in figure 5.
  • the service provider configures parameters such as which uplink interfaces are connected, connection priorities and recovery strategies, which services are currently which services are currently active, etc.
  • the data structures of the management and system configuration block are dynamic, allowing to extend the allowed configurations. Adding a new service to CGW, the service configuration must be inserted into this block, which provides a unified configuration platform for all services in CGW.
  • This block handles logging, authentication, and all data requests to and from the sensor. It is shown in figure 6.
  • this block enables a interface between the sensor interface layer with services and applications running on CGW.
  • an electricity meter with a PLC interface is added to a sensor network, it will be configured in the system management and configuration block with the type "electricity" and "PLC" access.
  • a global service configured in CGW to look up the values of all sensors would issue a request for this sensor, and the sensor abstraction and hardware abstraction block would route the request through the correct APIs to use the PLC interface.
  • the block would use a different API to access the information. In both cases the service request would be the same, and the hardware would be completely abstracted from the service.
  • This block is also responsible for placing timestamps on all data to synchronize with the service provider's time reference.
  • a service is configured on all devices to automatically synchronize the local clock with an NTP server running in the service provider's data center at regular intervals. Local time is maintained by a Real Time Clock (RTC) on the board chip.
  • RTC Real Time Clock
  • This block configures uplink connections with the transport network.
  • Its main purpose is to establish connections to the transport network using transport network layer APIs, and to perform connection status checking routines, optionally signaling the management block and system configuration in situations of abnormal behavior.
  • the user application infrastructure is an ecosystem where all non-core functionality runs. from CGW.
  • Registration of each application or service in the management and system configuration block is essential to ensure consistency in the software stack and to provide a unified control and management interface to the service provider.
  • Additional services and applications may be added by the service provider using the available APls.
  • the service provider may thereby have direct access to any sensor in the sensor network served by the CGW. Orders can be placed from the data center via the management and control interface or locally via the embedded management web interface.
  • Usage scenarios would simply serve to collect measurements from the sensor network at the end of the month for billing purposes.
  • the periodicity of this process may vary as the requirements for collecting this information differ: the periodicity is configurable (specified for each counter) using a wide range (less than one second daily, etc); can still be requested (anytime).
  • This service encourages CGW to start reading on a pre-configured group of sensors at specified intervals.
  • Readings are stored in the CGW's persistent memory, which can be accessed even after power outages or other critical errors.
  • the service may further be configured to initiate communications with the management interface in the service provider's data center after each reading, and report the readings directly.
  • a usage scenario would be to monitor readings once every hour to analyze consumption trends in a day or a week, helping consumers to choose the most cost-effective billing plan.
  • This service sets up a two-way channel between the service provider data center (or local management web interface) and the CGW. Sensors configured by the service will be read at maximum rates allowed by the sensor hardware and readings are immediately sent to the service provider's data center or local web interface.
  • This service is session oriented and due to potentially large amounts of data involved, no permanent storage space is provided in CGW.
  • a typical usage scenario would be where a customer claims a high electricity consumption.
  • the service provider can initiate real-time meter readings and, by telephone or by interacting with home automation applications / services, force the customer to turn appliances on and off and check if a malfunctioning appliance is causing a problem, or if there is no problem at all.
  • Sensor Fault Detection and Reporting
  • This service periodically checks authorized sensors under the influence of the CGW, stores the latest readings and triggers the verification of the sensors.
  • a signal is emitted and the service contacts the data center of the service provider with an alarm indicating the sensor identification and its possible malfunction.
  • a usage scenario is where the consumer tamperes with the sensor and changes readings to lower values.
  • this service would compare the reading with the previous one, verify that it is really inferior and send an alarm to it requesting the intervention of a technician.
  • This service sets thresholds for a sensor, or group of sensors, that automatically alarm if a reading reaches these thresholds. When the alarm is triggered, this service initiates communication with the service provider's data center, and generates reports about the sensor that triggered the alarm and what alarm condition was triggered. ac ivada.
  • a usage scenario is the customer service provider's permission to be notified as soon as a customer service limit is reached. Your service provider may use this service to set the threshold and rely on the remaining active services to eventually trigger the alarm as soon as possible, without additional weight to the system.
  • This service configures encryption in communication between the CGW and the service provider's data center.
  • This service directly encrypts the original data to be transmitted with an asymmetric key algorithm, PGP.
  • Service configuration includes the public key to use in the encryption process. Only the service provider will have access to the private key to decrypt the information.
  • the user of one or more sensor domains has access to their information, with guarantees of isolation and protection of information.

Landscapes

  • Engineering & Computer Science (AREA)
  • Automation & Control Theory (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computing Systems (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Hardware Design (AREA)
  • General Engineering & Computer Science (AREA)
  • Health & Medical Sciences (AREA)
  • General Health & Medical Sciences (AREA)
  • Medical Informatics (AREA)
  • Telephonic Communication Services (AREA)

Abstract

La présente invention concerne un concentrateur pour capteurs en réseau et compteurs distants, prenant en charge diverses technologies d'accès au réseau, avec stratégies de récupération automatique après défaillance et prise en charge de protection d'accès au capteur. Il se caractérise essentiellement en ce qu'il présente une architecture logicielle de pile implémentée dans la passerelle et présentant trois couches logicielles principales: - couche d'interface de capteurs; - couche de réseau de transport; - couche de traitement central; ces couches correspondant à trois blocs matériels principaux.
PCT/PT2011/000011 2010-11-24 2011-04-01 Concentrateur pour réseaux de capteurs et compteurs distants, prenant en charge diverses technologies d'accès réseau, avec stratégies de récupération automatique et sécurité d'accès aux capteurs Ceased WO2012070960A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
PT10540010A PT105400A (pt) 2010-11-24 2010-11-24 Concentrador para redes de sensores e contadores remotos, suportando diversas tecnologias de acesso de rede, com estratégias de recuperação automática e segurança no acesso aos sensores
PT105400 2010-11-24

Publications (1)

Publication Number Publication Date
WO2012070960A1 true WO2012070960A1 (fr) 2012-05-31

Family

ID=44260363

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/PT2011/000011 Ceased WO2012070960A1 (fr) 2010-11-24 2011-04-01 Concentrateur pour réseaux de capteurs et compteurs distants, prenant en charge diverses technologies d'accès réseau, avec stratégies de récupération automatique et sécurité d'accès aux capteurs

Country Status (2)

Country Link
PT (1) PT105400A (fr)
WO (1) WO2012070960A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210360071A1 (en) * 2020-05-15 2021-11-18 Microsoft Technology Licensing, Llc Collecting and providing sensor data based on a sensor definition via a sensor management device

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2008027615A1 (fr) * 2006-08-31 2008-03-06 Sony Ericsson Mobile Communications Ab Passerelle zigbee/ip
WO2008082441A1 (fr) * 2006-12-29 2008-07-10 Prodea Systems, Inc. Inserts et masques d'affichage et interfaces d'utilisateur graphiques pour systèmes multimédia
WO2009067251A1 (fr) * 2007-11-25 2009-05-28 Trilliant Networks, Inc. Optimisation d'acheminement de message et de communication dans un réseau maillé
US20090274104A1 (en) * 2008-05-01 2009-11-05 Honeywell International Inc. Fixed mobile convergence techniques for redundant alarm reporting

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2008027615A1 (fr) * 2006-08-31 2008-03-06 Sony Ericsson Mobile Communications Ab Passerelle zigbee/ip
WO2008082441A1 (fr) * 2006-12-29 2008-07-10 Prodea Systems, Inc. Inserts et masques d'affichage et interfaces d'utilisateur graphiques pour systèmes multimédia
WO2009067251A1 (fr) * 2007-11-25 2009-05-28 Trilliant Networks, Inc. Optimisation d'acheminement de message et de communication dans un réseau maillé
US20090274104A1 (en) * 2008-05-01 2009-11-05 Honeywell International Inc. Fixed mobile convergence techniques for redundant alarm reporting

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20210360071A1 (en) * 2020-05-15 2021-11-18 Microsoft Technology Licensing, Llc Collecting and providing sensor data based on a sensor definition via a sensor management device
US12137153B2 (en) * 2020-05-15 2024-11-05 Microsoft Technology Licensing, Llc Collecting and providing sensor data based on a sensor definition via a sensor management device

Also Published As

Publication number Publication date
PT105400A (pt) 2012-05-24

Similar Documents

Publication Publication Date Title
US20240012390A1 (en) Devices, systems and methods for predicting future consumption values of load(s) in power distribution systems
AU2008222794B2 (en) Energy switch router
US8368555B2 (en) Utility network interface device configured to detect and report abnormal operating condition
US8305232B2 (en) Utility network interface device configured to detect and report abnormal operating condition
BR112013016161B1 (pt) Dispositivo de monitoramento de medição destacável conectável com um medidor de utilidade
CN102216735B (zh) 计量装置、尤其是计能表以及识别篡改的方法
KR102327764B1 (ko) 보안 강화형 스마트 미터링 전력량계
US20130136132A1 (en) Power line communication system and an intelligent meter
Das Wireless communication system for energy meter reading
CN110347232B (zh) 不间断电源通信
BR112013007261B1 (pt) aparelho e método para gerenciamento de dispositivo de serviços públicos
CN100462724C (zh) 电力线通信系统和智能仪表
WO2013063669A1 (fr) Système de contrôle, de mesure et de surveillance du réseau secondaire de distribution d'énergie électrique
Saponara et al. Network architecture, security issues, and hardware implementation of a home area network for smart grid
KR20090120653A (ko) 웹기반 수변전설비 원격감시시스템
BR112014004379B1 (pt) Sistema e método para controlar a operação de pelo menos um aparelho de consumo
Yussof et al. Financial impacts of smart meter security and privacy breach
JP4655562B2 (ja) インテリジェント分電盤
WO2012070960A1 (fr) Concentrateur pour réseaux de capteurs et compteurs distants, prenant en charge diverses technologies d'accès réseau, avec stratégies de récupération automatique et sécurité d'accès aux capteurs
CN103703721B (zh) 用于管理互联网访问连接的家庭系统
CN106650459B (zh) 维护分布式存储系统数据可信的系统及方法
CN214174879U (zh) 面向电厂物联新安全分区的网络安全架构
US20240411332A1 (en) Power management system for device-specific optimization
Cleveland IEC 62351-7: communications and information management technologies-network and system management in power system operations
CN110289686A (zh) 一种总线制模块化物联网智能计量箱

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 11724052

Country of ref document: EP

Kind code of ref document: A1