Ulrich Herberg, Ph.D.
München, Bayern, Deutschland
2314 Follower:innen
500+ Kontakte
Info
- GM of the new eBay development center in Berlin, starting a new organization from…
Berufserfahrung
Ausbildung
Veröffentlichungen
-
Lightweight On-demand Ad hoc Distance-vector Routing - Next Generation (LOADng): Protocol, extension, and applicability
Computer Networks, Elsevier, Volume 126
This paper studies the routing protocol “Lightweight On-demand Ad hoc Distance-vector Routing Protocol – Next Generation (LOADng)”, designed to enable efficient, scalable and secure routing in low power and lossy networks. As a reactive protocol, it does not maintain a routing table for all destinations in the network, but initiates a route discovery to a destination only when there is data to be sent to that destination to reduce routing overhead and memory consumption. Designed with a modular…
This paper studies the routing protocol “Lightweight On-demand Ad hoc Distance-vector Routing Protocol – Next Generation (LOADng)”, designed to enable efficient, scalable and secure routing in low power and lossy networks. As a reactive protocol, it does not maintain a routing table for all destinations in the network, but initiates a route discovery to a destination only when there is data to be sent to that destination to reduce routing overhead and memory consumption. Designed with a modular approach, LOADng can be extended with additional components for adapting the protocol to different topologies, traffic, and data-link layer characteristics. This paper studies several such additional components for extending LOADng: support for smart route requests and expanding ring search, an extension permitting maintaining collection trees, a fast rerouting extension. All those extensions are examined from the aspects of specification, interoperability with other mechanisms, security vulnerabilities, performance and applicability. A general framework is also proposed to secure the routing protocol.
-
RFC8245: Rules for Designing Protocols Using the Generalized Packet/Message Format from RFC 5444
IETF
RFC 5444 specifies a generalized Mobile Ad Hoc Network (MANET)
packet/message format and describes an intended use for multiplexed
MANET routing protocol messages; this use is mandated by RFC 5498
when using the MANET port or protocol number that it specifies. This
document updates RFC 5444 by providing rules and recommendations for
how the multiplexer operates and how protocols can use the
packet/message format. In particular, the mandatory rules prohibit…RFC 5444 specifies a generalized Mobile Ad Hoc Network (MANET)
packet/message format and describes an intended use for multiplexed
MANET routing protocol messages; this use is mandated by RFC 5498
when using the MANET port or protocol number that it specifies. This
document updates RFC 5444 by providing rules and recommendations for
how the multiplexer operates and how protocols can use the
packet/message format. In particular, the mandatory rules prohibit a
number of uses that have been suggested in various proposals and that
would have led to interoperability problems, to the impediment of
protocol extension development, and/or to an inability to use
optional generic parsers. -
RFC8116: Security Threats to the Optimized Link State Routing Protocol Version 2 (OLSRv2)
IETF
This document analyzes common security threats to the Optimized Link
State Routing Protocol version 2 (OLSRv2) and describes their
potential impacts on Mobile Ad Hoc Network (MANET) operations. It
also analyzes which of these security vulnerabilities can be
mitigated when using the mandatory-to-implement security mechanisms
for OLSRv2 and how the vulnerabilities are mitigated. -
SPOT: A smartphone-based platform to tackle heterogeneity in smart-home IoT systems
Proceedings of the 2016 IEEE 3rd World Forum on Internet of Things (WF-IoT)
The recent advancements of IoT technologies, including broad penetration of Internet-connected smart appliances such as remotely controllable LED lights, thermostats, have changed the way we interact with the appliances in our homes and perform our daily activities. However, the significant heterogeneity in the emerging IoT devices has led to fragmented smart-home systems in which each single appliance vendor provides proprietary solution for appliance specific connectivity and user experience.…
The recent advancements of IoT technologies, including broad penetration of Internet-connected smart appliances such as remotely controllable LED lights, thermostats, have changed the way we interact with the appliances in our homes and perform our daily activities. However, the significant heterogeneity in the emerging IoT devices has led to fragmented smart-home systems in which each single appliance vendor provides proprietary solution for appliance specific connectivity and user experience. To address this challenge, we present SPOT, a smartphone-based platform for multi-vendor smart-home appliances. SPOT consists of several novel mechanisms, including open device driver models using XML, which allow vendor-independent, user-driven device driver implementation and unified appliance control. To validate the flexibility and generality of our approach, we have built a SPOT prototype on Android platform that supports 8 real IoT devices in the market from different vendors.
-
RFC7985: Security Threats to Simplified Multicast Forwarding (SMF)
IETF
This document analyzes security threats to Simplified Multicast Forwarding (SMF), including vulnerabilities of duplicate packet detection and relay set selection mechanisms. This document is not intended to propose solutions to the threats described. In addition, this document updates RFC 7186 regarding threats to the relay set selection mechanisms using the Mobile Ad Hoc Network (MANET) Neighborhood Discovery Protocol (NHDP) (RFC 6130).
-
SPOT: a smartphone-based control app with a device-agnostic and adaptive user-interface for IoT devices
Proceedings of the 2016 ACM International Joint Conference on Pervasive and Ubiquitous Computing: Adjunct
The recent progress of IoT technologies, including broad penetration of smart appliances such as remotely controllable lights, thermostats and cameras, have changed the way we interact with the appliances in our homes and perform our daily activities. However, the significant heterogeneity in the emerging IoT devices has led to fragmented smart-home systems in which each single appliance vendor provides proprietary solution for appliance specific connectivity and user experience. One of the…
The recent progress of IoT technologies, including broad penetration of smart appliances such as remotely controllable lights, thermostats and cameras, have changed the way we interact with the appliances in our homes and perform our daily activities. However, the significant heterogeneity in the emerging IoT devices has led to fragmented smart-home systems in which each single appliance vendor provides proprietary solution for appliance specific connectivity and user experience. One of the desired solutions in smart-home systems is to have a unified smartphone app that can control any arbitrary IoT appliances. In this extended abstract we focus on the design of such an app only from the user interaction viewpoint. In particular, we present SPOT app, a smartphone-based platform for multi-vendor smart-home appliances, that features an adaptive and device-agnostic user interface enabled by a novel device driver mechanism. To validate the flexibility and feasibility of our design, we have built a SPOT prototype based on 8 real IoT devices and present the quality of generating such adaptive graphical user interface by the measure of screen smoothness in the prototyped android app.
-
RFC7939: Definition of Managed Objects for the Neighborhood Discovery Protocol
IETF
This document replaces RFC 6779; it contains revisions and extensions to the original document. It defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes objects for configuring parameters of the Neighborhood Discovery Protocol (NHDP) process on a router. The extensions described in this document add objects and values to support the NHDP optimization specified in RFC 7466. The MIB module…
This document replaces RFC 6779; it contains revisions and extensions to the original document. It defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes objects for configuring parameters of the Neighborhood Discovery Protocol (NHDP) process on a router. The extensions described in this document add objects and values to support the NHDP optimization specified in RFC 7466. The MIB module defined in this document, denoted NHDP-MIB, also reports state, performance information, and notifications about NHDP. This additional state and performance information is useful to troubleshoot problems and performance issues during neighbor discovery.
-
RFC7547: Management of Networks with Constrained Devices: Problem Statement and Requirements
IETF
This document provides a problem statement, deployment and management topology options, as well as requirements addressing the different use cases of the management of networks where constrained devices are involved.
-
Depth First Forwarding for Unreliable Networks: Extensions and Applications
IEEE Internet of Things Journal, IEEE Communications Society, Volume 2, Issue 3
This paper introduces extensions and applications of depth-first forwarding (DFF)-a data forwarding mechanism for use in unreliable networks such as sensor networks and Mobile Ad hoc NETworks with limited computational power and storage, low-capacity channels, device mobility, etc. Routing protocols for these networks try to balance conflicting requirements of being reactive to topology and channel variation while also being frugal in resource requirements-but when the underlying topology…
This paper introduces extensions and applications of depth-first forwarding (DFF)-a data forwarding mechanism for use in unreliable networks such as sensor networks and Mobile Ad hoc NETworks with limited computational power and storage, low-capacity channels, device mobility, etc. Routing protocols for these networks try to balance conflicting requirements of being reactive to topology and channel variation while also being frugal in resource requirements-but when the underlying topology changes, routing protocols require time to re converge, during which data delivery failure may occur. DFF was developed to alleviate this situation: it reacts rapidly to local data delivery failures and attempts to successfully deliver data while giving a routing protocol time to recover from such a failure. An extension of DFF, denoted as DFF++, is proposed in this paper, in order to optimize the performance of DFF by way of introducing a more efficient search ordering. This paper also studies the applicability of DFF to three major routing protocols for the Internet of Things (IoT), including the Lightweight On-demand Ad hoc Distance-vector Routing Protocol-Next Generation (LOADng), the optimized link state routing protocol version 2 (OLSRv2), and the IPv6 routing protocol for low-power and lossy networks (RPL), and presents the performance of these protocols, with and without DFF, in lossy and unreliable networks.
-
On the Practicality of Detecting Anomalies with Encrypted Traffic in AMI
IEEE SmartGridComm 2014
** Winner of the SmartGridComm 2014 Best Paper Award **
Encryption is a key ingredient in the preservation of the confidentiality of network communications but can also be at odds with the mission of Intrusion Detection Systems (IDSes) to monitor traffic. This affects Advanced Metering Infrastructures (AMIs) too where the scale of the network and the sensitivity of communication make deploying IDSes along with encryption solutions mandatory. In this paper, we study four different…** Winner of the SmartGridComm 2014 Best Paper Award **
Encryption is a key ingredient in the preservation of the confidentiality of network communications but can also be at odds with the mission of Intrusion Detection Systems (IDSes) to monitor traffic. This affects Advanced Metering Infrastructures (AMIs) too where the scale of the network and the sensitivity of communication make deploying IDSes along with encryption solutions mandatory. In this paper, we study four different approaches for reconciling the twin goals of confidentiality and
monitoring by investigating their practical use on a set of real-world packet-level traces collected at an operational AMI network.
Andere Autor:innenVeröffentlichung anzeigen -
OpenADR 2.0 Deployment Architectures: Options and Implications
Proceedings of the 2014 IEEE International Conference on Smart Grid Communications (SmartGridComm)
OpenADR 2.0, an internationally-recognized standard for Automated Demand Response (ADR), defines the interaction between an ADR server and client, but does not specify all the possible multi-tier deployment architectures that are valid relative to the standard's specification. In this paper, we analyze the properties of a number of OpenADR-based architectures that have been proposed for deployment by ADR vendors, in terms of interoperability (compliance with the standard), scalability…
OpenADR 2.0, an internationally-recognized standard for Automated Demand Response (ADR), defines the interaction between an ADR server and client, but does not specify all the possible multi-tier deployment architectures that are valid relative to the standard's specification. In this paper, we analyze the properties of a number of OpenADR-based architectures that have been proposed for deployment by ADR vendors, in terms of interoperability (compliance with the standard), scalability, complexity, and security, with the goal of helping utilities and third party DR aggregators make informed decisions about their planned ADR deployments to ensure high performing, future-proof, and secure DR services.
-
RFC7181: The Optimized Link State Routing Protocol Version 2
IETF
This specification describes version 2 of the Optimized Link State Routing (OLSRv2) protocol for Mobile Ad hoc NETworks (MANETs).
Andere Autor:innenVeröffentlichung anzeigen -
RFC7182: Integrity Check Value and Timestamp TLV Definitions for Mobile Ad Hoc Networks (MANETs)
IETF
This document revises, extends, and replaces RFC 6622. It describes
general and flexible TLVs for representing cryptographic Integrity
Check Values (ICVs) and timestamps, using the generalized Mobile Ad
Hoc Network (MANET) packet/message format defined in RFC 5444. It
defines two Packet TLVs, two Message TLVs, and two Address Block TLVs
for affixing ICVs and timestamps to a packet, a message, and one or
more addresses, respectively.Andere Autor:innenVeröffentlichung anzeigen -
RFC7183: Integrity Protection for the Neighborhood Discovery Protocol (NHDP) and Optimized Link State Routing Protocol Version 2 (OLSRv2)
IETF
This document specifies integrity and replay protection for the MANET Neighborhood Discovery Protocol (NHDP) and the Optimized Link State Routing Protocol version 2 (OLSRv2). This protection is achieved by using an HMAC-SHA-256 Integrity Check Value (ICV) TLV and a timestamp TLV based on POSIX time.
The mechanism in this specification can also be used for other protocols that use the generalized packet/message format described in RFC 5444.
This document updates RFC 6130 and RFC…This document specifies integrity and replay protection for the MANET Neighborhood Discovery Protocol (NHDP) and the Optimized Link State Routing Protocol version 2 (OLSRv2). This protection is achieved by using an HMAC-SHA-256 Integrity Check Value (ICV) TLV and a timestamp TLV based on POSIX time.
The mechanism in this specification can also be used for other protocols that use the generalized packet/message format described in RFC 5444.
This document updates RFC 6130 and RFC xxxx by mandating the implementation of this integrity and replay protection in NHDP and OLSRv2.Andere Autor:innenVeröffentlichung anzeigen -
RFC7184: Definition of Managed Objects for the Optimized Link State Routing Protocol Version 2
IETF
This document defines the Management Information Base (MIB) module
for configuring and managing the Optimized Link State Routing
Protocol version 2 (OLSRv2). The OLSRv2-MIB module is structured
into configuration information, state information, performance
information, and notifications. This additional state and
performance information is useful for troubleshooting problems and
performance issues of the routing protocol. Two levels of compliance
…This document defines the Management Information Base (MIB) module
for configuring and managing the Optimized Link State Routing
Protocol version 2 (OLSRv2). The OLSRv2-MIB module is structured
into configuration information, state information, performance
information, and notifications. This additional state and
performance information is useful for troubleshooting problems and
performance issues of the routing protocol. Two levels of compliance
allow this MIB module to be deployed on constrained routers.Andere Autor:innenVeröffentlichung anzeigen -
RFC7186: Security Threats for the Neighborhood Discovery Protocol (NHDP)
IETF
This document analyzes common security threats of the Neighborhood Discovery Protocol (NHDP), and describes their potential impacts on MANET routing protocols using NHDP. This document is not intended to propose solutions to the threats described.
Andere Autor:innenVeröffentlichung anzeigen -
Depth First Forwarding for Low Power and Lossy Networks: Application and Extension
Proceedings of the IEEE World Forum on Internet of Things 2014
-
Enhancing Demand Response Signal Verification in Automated Demand Response Systems
Proceedings of the 5th Innovative Smart Grid Technologies Conference (ISGT)
-
A Depth First Forwarding (DFF) Extension for the LOADng Routing Protocol
Proceedings of the First International Symposium on Computing and Networking (CANDAR)
-
OpenADR 2.0b Specification
OpenADR Alliance
OpenADR 2.0b is an international standard for automated Demand Response.
Andere Autor:innen -
RFC6971: Depth-First Forwarding (DFF) in Unreliable Networks
IETF
This document specifies the Depth-First Forwarding (DFF) protocol for
IPv6 networks, a data-forwarding mechanism that can increase
reliability of data delivery in networks with dynamic topology and/or
lossy links. The protocol operates entirely on the forwarding plane
but may interact with the routing plane. DFF forwards data packets
using a mechanism similar to a "depth-first search" for the
destination of a packet. The routing plane may be informed…This document specifies the Depth-First Forwarding (DFF) protocol for
IPv6 networks, a data-forwarding mechanism that can increase
reliability of data delivery in networks with dynamic topology and/or
lossy links. The protocol operates entirely on the forwarding plane
but may interact with the routing plane. DFF forwards data packets
using a mechanism similar to a "depth-first search" for the
destination of a packet. The routing plane may be informed of
failures to deliver a packet or loops. This document specifies the
DFF mechanism both for IPv6 networks (as specified in RFC 2460) and
for "mesh-under" Low-Power Wireless Personal Area Networks (LoWPANs),
as specified in RFC 4944. The design of DFF assumes that the
underlying link layer provides means to detect if a packet has been
successfully delivered to the Next Hop or not. It is applicable for
networks with little traffic and is used for unicast transmissions
only.Andere Autor:innenVeröffentlichung anzeigen -
RFC6779: Definition of Managed Objects for the Neighborhood Discovery Protocol
The Internet Engineering Task Force
This document defines a portion of the Management Information Base
(MIB) for use with network management protocols in the Internet
community. In particular, it describes objects for configuring
parameters of the Neighborhood Discovery Protocol (NHDP) process on a
router. The MIB module defined in this document, denoted NHDP-MIB,
also reports state, performance information, and notifications about
NHDP. This additional state and performance information is…This document defines a portion of the Management Information Base
(MIB) for use with network management protocols in the Internet
community. In particular, it describes objects for configuring
parameters of the Neighborhood Discovery Protocol (NHDP) process on a
router. The MIB module defined in this document, denoted NHDP-MIB,
also reports state, performance information, and notifications about
NHDP. This additional state and performance information is useful to
troubleshoot problems and performance issues during neighbor
discovery.Andere Autor:innenVeröffentlichung anzeigen -
RFC6622: Integrity Check Value and Timestamp TLV Definitions for Mobile Ad Hoc Networks (MANETs)
The Internet Engineering Task Force
This document describes general and flexible TLVs for representing cryptographic Integrity Check Values (ICVs) (i.e., digital signatures or Message Authentication Codes (MACs)) as well as timestamps, using the generalized Mobile Ad Hoc Network (MANET) packet/message format defined in RFC 5444. It defines two Packet TLVs, two Message TLVs, and two Address Block TLVs for affixing ICVs and timestamps to a packet, a message, and an address, respectively.
Andere Autor:innenVeröffentlichung anzeigen -
A Comparative Performance Study of the Routing Protocols LOAD and RPL with Bi-Directional Traffic in Low-power and Lossy Networks (LLN)
Proceedings of the 8th ACM International Symposium on Performance Evaluation of Wireless Ad Hoc, Sensor, and Ubiquitous Networks (PE-WASUN)
-
A Critical Evaluation of the 'IPv6 Routing Protocol for Low Power and Lossy Networks' (RPL)
Proceedings of the 7th IEEE International Conference on Wireless and Mobile Computing, Networking and Communications (WiMob)
-
Delay Tolerant Networking with OLSRv2
Proceedings of the 9th IEEE/IFIP International Conference on Embedded and Ubiquitous Computing (EUC)
-
Performance Analysis of SNMP in OLSRv2-routed MANETs
Proceedings of the 7th International Conference on Network and Services Management (CNSM)
-
Vulnerability Analysis of the Simple Multicast Forwarding (SMF) Protocol for Mobile Ad Hoc Networks
Proceedings of the IEEE International Conference on Cyber, Physical, and Social Computing (CPSCom)
-
Some Considerations on Routing In Particular and Lossy Environments
Proceedings of the 1st Interconnecting Smart Objects with the Internet Workshop
-
Study of Multipoint-to-Point and Broadcast Traffic Performance in the 'IPv6 Routing Protocol for Low Power and Lossy Networks' (RPL)
Journal of Ambient Intelligence and Humanized Computing, Springer, ISSN 1868-5137, Volume 2, Number 4
Recent trends in Wireless Sensor Networks (WSNs) have suggested converging to such being
IPv6-based. To this effect, the Internet Engineering Task Force has chartered a Working Group
to develop a routing protocol specification, enabling IPv6-based multi-hop Wireless Sensor
Networks. This routing protocol, denoted “IPv6 Routing Protocol for Low Power and Lossy
Networks” (RPL), has been under development for approximately a year, and this paper takes
a critical look at the state of…Recent trends in Wireless Sensor Networks (WSNs) have suggested converging to such being
IPv6-based. To this effect, the Internet Engineering Task Force has chartered a Working Group
to develop a routing protocol specification, enabling IPv6-based multi-hop Wireless Sensor
Networks. This routing protocol, denoted “IPv6 Routing Protocol for Low Power and Lossy
Networks” (RPL), has been under development for approximately a year, and this paper takes
a critical look at the state of advancement hereof: it provides a brief algorithmic description
of the protocol, and discusses areas where – in the authors view – further efforts are required
in order for the protocol to become a viable candidate for general use in WSNs. Among these
areas is the lack of a proper broadcast mechanism. This paper suggests several such broadcast
mechanisms, all aiming at (i) exploiting the existing routing state of RPL, while (ii) requiring
no additional state maintenance, and studies the performance of RPL and of these suggested
mechanisms. -
Comparative Study of RPL-Enabled Optimized Broadcast in Wireless Sensor Networks
Proceedings of the 6th International Conference on Intelligent Sensors, Sensor Networks and Information Processing (ISSNIP)
-
Yet Another Autoconf Proposal (YAAP) for Mobile Ad hoc NETworks
Proceedings of the 6th International Conference on Mobile Ad-hoc and Sensor Networks (MSN)
-
MANET Network Management and Performance Monitoring for NHDP and OLSRv2
Proceedings of the 6th International Conference on Network and Services Management (CNSM)
-
Multipoint-to-Point and Broadcast in RPL
Proceedings of the 1st International Symposium on Frontiers in Ubiquitous Computing, Networking and Applications (NeoFUSION)
-
Router and Link Admittance Control in the Optimized Link State Routing Protocol version 2 (OLSRv2)"
Proceedings of the 4th International Conference on Network and System Security (NSS)
-
Digital Signatures for Admittance Control in the Optimized Link State Routing Protocol version 2
Proceedings of the International Conference on Internet Technology and Applications (iTAP)
-
Vulnerability Analysis of the Optimized Link State Routing Protocol version 2 (OLSRv2)
Proceedings of the International Conference on Wireless Communications, Networking and Information Security (WCNIS)
-
Development Framework for Supporting Java NS2 Routing Protocols
Proceedings of the International Workshop on Future Engineering, Applications and Services (FEAS)
-
Performance Evaluation of using a Dynamic Shortest Path Algorithm in OLSRv2
Proceedings of the 8th Annual Conference on Communication Networks and Services Research (CNSR)
-
Security Issues in the Optimized Link State Routing Protocol version 2
International Journal of Network Security & Its Applications, special issue April
Ad hoc networks have left the confines of research: community ad hoc networks,
such as the FunkFeuer network in Vienna or the FreiFunk network in Berlin,
have exceeded the size of several hundred routers each. Both these networks
run the Optimized Link State Routing Protocol (OLSR), which itself does not
provide security protection of the network integrity. Certain assumptions and
legal requirements for these networks require to design specific security solutions,
but also…Ad hoc networks have left the confines of research: community ad hoc networks,
such as the FunkFeuer network in Vienna or the FreiFunk network in Berlin,
have exceeded the size of several hundred routers each. Both these networks
run the Optimized Link State Routing Protocol (OLSR), which itself does not
provide security protection of the network integrity. Certain assumptions and
legal requirements for these networks require to design specific security solutions,
but also allow to create simpler security mechanisms than for the general case
of ad hoc networks.
This paper presents a security mechanism for router and link admittance
control, focused on such ad hoc networks based on the successor of OLSR, called
OLSRv2. Digitally signing OLSRv2 control messages allows recipient routers
to choose to admit or exclude the originating router for when populating linkstate
databases, calculating Multi-Point Relay (MPR) sets etc. By additionally
embedding signatures for each advertised link, recipient routers can also control
admittance of each advertised link in the message, rendering an OLSRv2 network
resilient to both identity-spoofing and link-spoofing attacks. The impact
of adding a link-admittance control mechanism to OLSRv2 is studied, both in
terms of additional control-traffic overhead and additional in-router processing
resources, using several cryptographic algorithms, such as RSA and Elliptic
Curve Cryptography for very short signatures.
In addition to the router and admittance control, this paper proposes a
simple key acquisition and distribution mechanism for use in the specific kind
of ad hoc networks, based on X.509 Public Key Infrastructure (PKI). Using an
X.509 extension, each certificate can be bound to an IP subnet, assuring that
each router advertises only its allocated subnet, alleviating certain man-in-themiddle
attacks. -
IP Links in Multihop Ad Hoc Wireless Networks?
Proceedings of the 18th International Conference on Software, Telecommunications and Computer Networks (SoftCOM)
-
JOLSRv2: An OLSRv2 implementation in Java
Proceedings of the 4th OLSR Interop Workshop
Patente
-
Residential and small and medium business demand response
Ausgestellt am US US20150206084 A1
A method of residential or small and medium business (SMB) demand response (DR) coordination may include receiving a DR event notification from a DR server. The DR event notification may include DR event information pertaining to a DR event and curtailment information. The method may also include communicating a notification acknowledgement to the DR server. The notification acknowledgement may indicate reception of the DR event notification. The method may include displaying a curtailment…
A method of residential or small and medium business (SMB) demand response (DR) coordination may include receiving a DR event notification from a DR server. The DR event notification may include DR event information pertaining to a DR event and curtailment information. The method may also include communicating a notification acknowledgement to the DR server. The notification acknowledgement may indicate reception of the DR event notification. The method may include displaying a curtailment request pertaining to the DR event. The curtailment request may be based on the curtailment information included in the DR event notification and may include some portion of the DR event information. The method may also include receiving a user input including a DR event participation confirmation or a DR event participation refusal. The method may further include communicating a participation signal representative of at least a portion of the user input to the DR server.
Andere Erfinder:innenPatent anzeigen -
Dynamic device drivers
Ausgestellt am US US9703570B2
A method includes receiving a driver model for a device. The driver model includes a list of variables associated with the device and one or more characteristics of the variables. The method includes determining whether the driver model is format-compliant and validating syntax of the driver model based at least partially on a driver template that is accessible to a third party. In response to the driver model being format-compliant and the syntax being valid, the method includes generating a…
A method includes receiving a driver model for a device. The driver model includes a list of variables associated with the device and one or more characteristics of the variables. The method includes determining whether the driver model is format-compliant and validating syntax of the driver model based at least partially on a driver template that is accessible to a third party. In response to the driver model being format-compliant and the syntax being valid, the method includes generating a verified file that is representative of the driver model. The verified file is formatted to dynamically load into a device application module during operation and to dynamically support the device. The method includes communicating the verified file to a user apparatus and adding an integrity check value thereto. In response to the driver model being format-noncompliant or the syntax being invalid, the method includes communicating an error message.
Andere Erfinder:innenPatent anzeigen -
Device configuration for secure communication
Ausgestellt am US US20150319142 A1
A method including generating a mapping in response to an enrollment message received from a customer device. The enrollment message includes a device identification number (device ID) of the customer device. The mapping includes a one-time password (OTP) encrypted using the device ID. The method includes generating a quick response (QR) code including a uniform resource locator (URL), a provider certificate (CRT), and certificate signing request (CSR) content. The method includes receiving a…
A method including generating a mapping in response to an enrollment message received from a customer device. The enrollment message includes a device identification number (device ID) of the customer device. The mapping includes a one-time password (OTP) encrypted using the device ID. The method includes generating a quick response (QR) code including a uniform resource locator (URL), a provider certificate (CRT), and certificate signing request (CSR) content. The method includes receiving a confirmation message at a website identified by the URL. The confirmation message includes a generated public key, a CSR, and a decrypted OTP. The method includes verifying the decrypted OTP against the mapping and communicating one or more application configuration settings. The method includes securely communicating information using the one or more application configuration settings, a provider public key, a provider private key, the generated public key, and a generated private key.
Andere Erfinder:innenPatent anzeigen -
Data distribution path verification
Ausgestellt am US 9,032,213
A method may include receiving data and first path-metadata. The first path-metadata may include a first entity identifier. The first entity identifier may be associated with a first receiving entity that receives the data and the first path-metadata from an originating entity. The first path-metadata may also include a first digital signature associated with the originating entity. The method may further include receiving second path-metadata that may include the first path-metadata and a…
A method may include receiving data and first path-metadata. The first path-metadata may include a first entity identifier. The first entity identifier may be associated with a first receiving entity that receives the data and the first path-metadata from an originating entity. The first path-metadata may also include a first digital signature associated with the originating entity. The method may further include receiving second path-metadata that may include the first path-metadata and a second entity identifier associated with a second receiving entity. The second path-metadata may also include a second digital signature associated with the first receiving entity. The method may additionally include verifying that the data was communicated by the originating entity to the first receiving entity and from the first receiving entity to the second receiving entity based on the first path-metadata, the second path-metadata, the first digital signature, and the second digital signature.
Andere Erfinder:innenPatent anzeigen -
Duplicate packet suppression
Ausgestellt am US US8792360 B2
According to an aspect of an embodiment, a method of managing packets in a communication network including multiple communication nodes is described. The method may include receiving a packet including a packet header. The packet header may include a packet identifier uniquely identifying the packet. The method may also include determining a packet type of the packet received by a first communication node based on the packet identifier. The method may also include dropping the packet when the…
According to an aspect of an embodiment, a method of managing packets in a communication network including multiple communication nodes is described. The method may include receiving a packet including a packet header. The packet header may include a packet identifier uniquely identifying the packet. The method may also include determining a packet type of the packet received by a first communication node based on the packet identifier. The method may also include dropping the packet when the packet is determined to be a duplicate packet or routing the packet to a neighbor communication node in a manner that prevents the packet from being caught in a loop when the packet is determined to be a returned packet or a new packet.
Andere Erfinder:innenPatent anzeigen -
Demand response event dissemination system and method
Angemeldet am US US20150052188 A1
A method may include receiving peer data describing a set of peer clients associated with a demand response application server and describing how the peer clients communicate with one another. The peer data may be configured so that a subset of the peer clients directly communicate with the demand response application server and the demand response application server does not directly communicate with each of the peer clients. The method may also include receiving announcement data describing…
A method may include receiving peer data describing a set of peer clients associated with a demand response application server and describing how the peer clients communicate with one another. The peer data may be configured so that a subset of the peer clients directly communicate with the demand response application server and the demand response application server does not directly communicate with each of the peer clients. The method may also include receiving announcement data describing an event specified by the demand response application server and determining event response data responsive to the announcement data. The method may also include identifying, from the set of peer clients specified by the demand response application server, a set of recipient peer clients to receive the event response data.
Andere Erfinder:innenPatent anzeigen