Extending network security to locally connected edge devices

By introducing security keys and certificates between network nodes and edge devices, establishing secure channels, and managing routing information, security issues during edge devices are solved, and communication security is significantly improved.

CN114026824BActive Publication Date: 2024-11-12LANDIS GYR TECH INC
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202080049116.8
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Priority Date
2019-05-06
Filing Date
2020-05-05
Publication Date
2024-11-12
Estimated Expiration
2040-05-05

AI Technical Summary

Technical Problem

In existing networks, local connections between edge devices and network nodes are vulnerable to attacks, resulting in compromised network security and lack of effective security controls.

Method used

By introducing security keys and security certificates between network nodes and edge devices, a secure channel is established, and the network manager manages routing information and network addresses, ensuring that edge devices can communicate securely with other devices in the network.

Benefits of technology

It significantly improves the communication security between network nodes and edge devices, reduces the vulnerability of local connections, and allows edge devices to interact with other devices securely like network nodes, enhancing the security of the entire network.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114026824B_ABST
    Figure CN114026824B_ABST
Patent Text Reader

Abstract

In some embodiments, a secure local connection is provided by extending network security to a local connection between a network node of the network and an edge device attached to the network node. The edge device attached to the network node communicates with a network manager of the network to obtain a security key and a security certificate for the edge device. Using the security key and the security certificate, the edge device is able to establish a secure channel between the network node and the edge device via the local connection. The edge device further communicates with the network manager to exchange routing information and obtain a network address for the edge device. The edge device is then able to communicate with other network nodes in the network through the network node using the security key, security certificate, and network address.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to U.S. Provisional Application No. 62 / 843,764, filed on May 6, 2019, entitled “Extending Network Security to Locally Connected Edge Devices,” which is incorporated herein in its entirety by this reference. Technical Field

[0003] The present disclosure relates generally to data communications, and more particularly to protecting communications within a network endpoint by protecting communications via a local connection to an edge device. Background Art

[0004] A network allows nodes in the network to communicate with each other. For example, a metering network can be used to communicate between a resource provider and a device that monitors and controls a resource such as electricity in a home or other location. A computer network allows computing devices to exchange data with each other. The network links between nodes are typically secure, so that communications between network nodes can be protected from various attacks.

[0005] Network nodes are sometimes attached to edge devices (e.g., meter network radios are attached to meter devices) via local connections, such as USB connections. These local connections often exist without any security controls and are therefore vulnerable to attack. Further, if edge devices are allowed to communicate with other network nodes on the network, the local connections between edge devices and network nodes become vulnerable targets. If the local connections are not secure, the security of the network will be compromised. Therefore, it is important to protect the local connections between network nodes and their corresponding edge devices. Summary of the invention

[0006] Disclosed are systems and methods for providing secure local connections by extending the security of the network to local connections between network nodes in the network and edge devices attached to the network nodes. In one example, an edge device attached to a network node communicates with a network manager of the network to obtain a security key and a security certificate for the edge device. Using the security key and the security certificate, the edge device can establish a secure channel between the network node and the edge device via the local connection. The edge device further communicates with the network manager to exchange routing information and obtain a network address for the edge device. The edge device can then communicate with other network nodes in the network through the network node using the security key, security certificate, and network address.

[0007] In another example, a method includes: authenticating, by an edge device connected to a network node of a network through a local connection, the edge device to a network manager of the network; and receiving, by the edge device, a device certificate and a network key issued by the network manager based on the authentication. The method further includes: creating, by the edge device and the network node, a secure channel between the edge device and the network node using the device certificates and the network key of the network node and the edge device; establishing, by the edge device, a data link with the network; and communicating, by the edge device, with other devices on the network via the network node and based on the data link.

[0008] In an additional example, a system includes: a network manager configured to manage communications between network devices of a network; and an endpoint device connected to the network manager through the network and managed by the network manager. The network devices include network nodes and edge devices. The endpoint device includes a network node connected to the network and configured to communicate with the network manager and other network devices. The network node has a first network address. The endpoint device further includes an edge device, which is connected to the network node via a local connection and is configured to communicate with the network node via the local connection. The edge device is configured to: communicate with the network manager to obtain a security key and a security certificate of the edge device; establish a secure channel between the network node and the edge device via a local connection using the security key and the security certificate; communicate with the network manager to exchange routing information and obtain a second network address for the edge device; and communicate with another network device in the network using the security key, the security certificate, and the second network address.

[0009] These illustrative aspects and features are not mentioned to limit or define the present invention but to provide examples to aid in understanding the inventive concepts disclosed in the present application.Other aspects, advantages and features of the present invention will become apparent after reviewing the entire application. BRIEF DESCRIPTION OF THE DRAWINGS

[0010] These and other features, aspects and advantages of the present disclosure will be better understood when the following detailed description is read with reference to the accompanying drawings, in which:

[0011] Figure 1 is a diagram illustrating an example of a network that extends network security over local connections between network nodes and edge devices according to some embodiments of the present disclosure;

[0012] Figure 2 is a flow chart illustrating an example of a process for extending network security to a local connection between a network node and an edge device according to some embodiments of the present disclosure;

[0013] Figure 3is a diagram illustrating an example of a mesh network having extended network security for local connections between communication modules and metering modules within endpoints of the mesh network according to some embodiments of the present disclosure;

[0014] Figure 4 is a diagram illustrating message exchanges between a network management device and an endpoint and between a network card and an edge device in an endpoint; and

[0015] Figure 5 is a diagram depicting an example of an endpoint suitable for implementing aspects of the techniques and technologies presented herein. DETAILED DESCRIPTION

[0016] Systems and methods for protecting local connections between network nodes in a network and edge devices attached to the network nodes are provided. Network security mechanisms such as security keys and security certificates are extended to the edge devices across the local connections between the network nodes and the edge devices. Using these security certificates and security keys, the edge devices are able to securely interact with other devices on the network as if the edge devices were network nodes in the network. As a result, communications between network nodes and edge devices, as well as communications between edge devices and other network devices, are as securely protected as the rest of the communications on the network.

[0017] In one example, a network includes a plurality of network nodes that communicate with each other through the network. The network may be a mesh network, a Wi-Fi network, a cellular network, a power line carrier network, or any other wired or wireless network. The network further includes a network manager, which is configured to manage security aspects of the network, such as security keys and security certificates, among other aspects. When an edge device is attached to a network node via a local connection (such as a USB connection, an RS232 serial port connection, a peer-to-peer 900MhzRF connection, a Bluetooth connection, or a digital chip-to-chip connection), the network node announces the network to the edge device. The edge device contacts the network manager to obtain a security key for the network and a security certificate for the edge device. Using the security key and security certificate, a secure channel is established between the network node and the edge device, wherein the communication between the network node and the edge device is transmitted over the secure channel.

[0018] In order for the edge device to communicate with other network nodes or devices on the network, the edge device associates itself with the network by communicating with the network manager to exchange routing information and obtain a network address (such as an Internet Protocol (IP) address, a local area network (LAN) address, or a combination thereof). After obtaining the network address and setting the routing information, the edge device can be treated as a node on the network and can communicate securely with other network nodes or devices on the network through the network node to which the edge device is connected. In this way, the network node acts as a network router for routing network traffic directed to or from the edge device.

[0019] By extending network security to the local connection between the network node and the edge device attached to the network node, the vulnerability of the network and the local connection is significantly reduced or even eliminated. Therefore, the security of communication via the local connection and the security of communication in the network are significantly increased. Further, only minor changes need to be made to the network nodes to support secure local connection communications (e.g., changing the routing information in the network node so that traffic directed to the edge device can be delivered to the edge device). In addition, the technology described herein can be applied to a variety of networks and local connections.

[0020] These illustrative examples are given to introduce the reader to the general subject matter discussed herein and are not intended to limit the scope of the disclosed concepts.The following section describes various additional aspects and examples with reference to the drawings, in which like numerals indicate like elements.

[0021] The features discussed herein are not limited to any particular hardware architecture or configuration. A computing device may include any suitable arrangement of components that provide results conditioned on one or more inputs. Suitable computing devices include multi-purpose computer systems based on microprocessors that access stored software that programs or configures the computing system from a general-purpose computing device to a dedicated computing device that implements one or more aspects of the present subject matter. Any suitable programming, scripting, or other type of language or combination of languages ​​may be used to implement the teachings contained herein with software to be used in programming or configuring a computing device.

[0022] Now referring to the accompanying drawings, Figure 11 is a diagram illustrating an example of an operating environment 100 in which a network 102 supports secure communications between network devices including network nodes and edge devices according to some embodiments of the present disclosure. The network 102 includes a plurality of endpoints 114A-114C (which may be referred to herein individually or collectively as endpoints 114). The endpoints 114 include a network node 116 configured to communicate directly with other network nodes on the network 102. The network node 116 may be a network card, a radio transceiver, or any other type of device that can communicate with other network nodes of the network 102.

[0023] The network 102 may be a radio frequency (RF) mesh network (such as an IEEE 802.15.4 network), a Wi-Fi network, a cellular network, a power line carrier network, or any other wired or wireless network. Correspondingly, the network nodes 116 may be RF radio transceivers, computers, mobile devices, power line network devices, or other types of devices that can communicate directly with other devices on the network 102.

[0024] Endpoints 114 may also include edge devices 118 attached to network nodes 116 via local connections 130. In one example of a mesh network, edge devices 118 may be meters that measure resources such as electricity, gas, or water used at the premises where the meters are installed. In another example of a Wi-Fi network, edge devices 118 may be computers or other devices that are plugged into network nodes 116. Depending on the type of network nodes 116 and edge devices 118, local connections 130 may be USB connections, RS232 serial port connections, peer-to-peer 900Mhz RF connections, Bluetooth connections, digital chip-to-chip connections, or any type of connection.

[0025] As used herein, an "endpoint" 114 includes a network node 116 and (multiple) edge devices 118 that are locally connected to the network node 116. Not all endpoints 114 have locally connected edge devices 118. Some endpoints 114 may have multiple edge devices 118 that are locally connected to the network node 116. Although the edge device 118 and the network node 116 to which it is attached are included in the same endpoint 114, by implementing the techniques presented herein, the edge device 118 appears as an independent network device on the network 102. As such, the network node 116 and the edge device 118 may both be referred to as "network devices" in the following description. In some implementations, the edge device 118 has its own IP address or its own LAN address or a combination of the two. In other implementations, the edge device 118 is configured to operate outside of an IP network and communicate using message access control (MAC) layer messages.

[0026] In order to facilitate secure communication between network devices, the network 102 also includes a network manager 104. The network manager 104 may include a security module 108 to maintain security certificates 110 for network devices and manage network keys 112 used in the network 102. The security module 108 may also be configured to perform various security operations, such as issuing security certificates and network keys to network devices and authenticating network devices when network devices join the network 102, updating and revoking security certificates and network keys when necessary, removing network devices from the network 102, etc. The network manager 104 may also be configured to manage the routing of network traffic. For example, when a new network device joins the network, the network manager 104 may communicate with the new network device to establish routing information and assign a network address to the new network device so that the network 102 can route network traffic directed to the new network device, such as an IP address, a LAN address, or a combination thereof. In some implementations, the network manager 104 is an access point, an authentication server, or a combination of the two of the network 102.

[0027] In some configurations, when the edge device 118 is connected to the network node 116 at the endpoint 114, the edge device 118 contacts the network manager 104 through the network node 116 to obtain a device certificate 120 and a network key 122 for the edge device 118. Using the device certificate 120 and the network key 122 of the edge device 118 and the device certificate and the network key of the network node 116, a secure channel can be established between the network node 116 and the edge device 118 for secure communications via the local connection 130. In other words, the device certificate and the network key created for the network 102 are used in communications via the local connection 130, thereby extending network security to the local connection 130.

[0028] To allow the edge device 118 to communicate as a network device on the network 102, the edge device 118 further communicates with the network manager 104 through the network node 116 to obtain network configuration, routing information, and network addresses. Because the edge device 118 may not have the ability to communicate directly on the network 102, communications between the edge device 118 and other network devices may pass through the network node 116. For example, the edge device 118 may be a metering device configured to measure resources consumed at a certain location and may not be configured with a radio transceiver or communication module. In order for the metering device to transmit measurement data and other data to other meters or head-end systems, the metering device is attached to a radio transceiver that can communicate with other radio transceivers in the network (e.g., in a 900 MHz RF mesh network). Similarly, other metering devices at other locations may be attached to corresponding radios for communication via the mesh network.

[0029] In these scenarios, even though edge device 118 obtains device certificate 120 and network key 122 from network 102, network traffic to and from edge device 118 still passes through network node 116. In other words, network traffic directed to edge device 118 is first received by network node 116 from network 102 and then transmitted to edge device 118 through the secure channel between network node 116 and edge device 118. Likewise, network traffic originating from edge device 118 is first received by network node 116 through the secure channel and then transmitted by network node 116 to a destination in network 102. To accomplish this, routing information for network 102 may specify that edge device 118 is reachable through network node 116. To network 102, network node 116 behaves like a router and other network devices on network 102 can communicate with edge device 118 as normal. Figures 1 to 4 Provides additional details on extending network security to local connections between network nodes and edge devices.

[0030] Figure 2 A flowchart illustrating an example of a process 200 for extending network security to a local connection between a network node 116 and an edge device 118 of an endpoint 114 according to some embodiments of the present disclosure is depicted. One or more devices (e.g., a network node 116 and an edge device 118) implement the process 200 by executing suitable program code. Figure 2 For illustrative purposes, process 200 is described with reference to some of the examples depicted in the various figures. However, other implementations are possible.

[0031] At block 202, the network node 116 joins the network 102 by complying with normal operations and communications defined by the network protocol implemented in the network 102, including, for example, network advertisements, network node authentication, network key exchange, network node association, etc. At block 204, the network node 116 advertises the network 102 to the edge device 118 that has been connected thereto via the local connection 130. The advertisement may include an identification of the network 102 and information about the network, such as supported data rates, security requirements, etc.

[0032] Based on the information contained in the network advertisement, the edge device 118 is able to identify the network manager 104 and communicate with the network manager 104 to authenticate itself at block 206. The network manager 104, when authenticating the edge device 118, can issue a device certificate and send a network key used in the network 102 to the edge device 118. Using the device certificate 120 and the network key 122, the network node 116 and the edge device 118 can create a secure channel between them, thereby protecting communications via the local connection 130.

[0033] At block 208, the edge device 118 associates itself with the network 102, i.e., establishes a data link between the edge device 118 and the network 102. For example, the edge device 118 may obtain configuration data from the network manager 104, exchange routing information with the network manager 104, and obtain a network address from the network manager 104. After the edge device 118 is associated with the network 102, at block 210, the edge device 118 begins communicating with other devices on the network 102.

[0034] Figure 3 A diagram is shown illustrating an example of a secure mesh network 300 with extended network local connections between communication modules and metering modules within endpoints of the mesh network in accordance with some embodiments of the present disclosure. Figure 3 The mesh network 300 shown in FIG. 3 may be associated with a resource distribution network, such as a water distribution network, an electric grid, or a gas distribution network. Endpoints 314A to 314G (which may be individually or collectively referred to herein as endpoints 314) are installed at various locations of the resource distribution network.

[0035] Each endpoint 314 includes a metering module 318 and a communication module 316. The metering module 318 in the endpoint 314 is configured to measure various characteristics associated with the distribution network, such as power consumption, power peak voltage, etc. The metering module 318 can be any type of meter in the public network, such as an electricity meter, a gas meter, a water meter, a steam meter, etc. The communication module 316 in the endpoint 314 is configured to deliver the measurement data obtained by the metering module 318 to the root node 304 via the mesh network 300. The metering module 318 and the communication module 316 are connected by a local connection 330, such as a USB connection, an RS232 serial port connection, a Bluetooth connection, a digital chip-to-chip connection, or a combination thereof. In this example, the metering module 318 is an edge device 118 and the communication module 316 is a network node 116, as described above with reference to FIG. Figure 1 Just as described.

[0036] The communication module 316 in the endpoint 314 transmits the collected data to the root node 304 through the mesh network 300, and the root node 304 can further transmit the collected data to the root node 304 via one or more additional networks ( Figure 3 The root node 304 may be a personal area network (PAN) coordinator, a gateway, or any other device capable of communicating with the head-end system. In some configurations, the root node 304 is also configured as a network manager of the mesh network 300 to manage the security of the mesh network 300, as described above with respect to Figure 1 Just as described.

[0037] For example, the root node 304 may be configured to issue and maintain security certificates and network keys for the communication modules of the endpoints 314 and also for the metering modules that have joined the mesh network 300 through a secure local connection as disclosed herein. The root node 304 may also be configured to authenticate the communication modules and metering modules of the endpoints 314 as they join the mesh network 300, update and revoke security certificates and network keys, remove network devices from the mesh network 300, etc. The root node 304 may also be configured to manage the routing of network traffic and communicate with the communication modules and metering modules to establish routing information, and may assign network addresses, such as IP addresses, LAN addresses, or a combination thereof, to new network devices. It should be noted that the mesh network 300 may include multiple root nodes, each of which may have multiple endpoints associated therewith, as described above.

[0038] Figure 4 A signal flow diagram illustrating an example of a process 400 for extending network security to local connections between edge devices and network nodes that are endpoints to a mesh network 300 is depicted. Figure 4 In the example shown in FIG. 3 , the communication module 316 is a network node and the metering module 318 is an edge device. The root node 304 is configured to perform the functions of a network manager. Depending on the network configuration, other nodes or devices in the mesh network 300 may also be configured as network managers. Figure 4 As shown in FIG. 1 , various messages are exchanged between the root node 304 and the endpoint 314 and between the communication module 316 and the metering module 318 within the endpoint 314 in order to extend network security to the local connection within the endpoint 314 .

[0039] Process 400 includes four phases: communication module joining phase 402, network advertisement phase 404, authentication phase 406, and association phase 408. At communication module joining phase 402, communication module 316 joins network 300 by complying with normal operations and communications defined by the network protocol implemented in network 300. This phase includes exchanging advertisement messages between communication module 316 and root node 304 so that communication module 316 can identify the appropriate network to join. Communication module 316 and root node 304 further exchange messages for authenticating communication module 316 and for associating communication module 316 with network 300.

[0040] After the communication module 316 joins the network 300, the process 400 proceeds to the network announcement phase 404. In this phase, the metering module 318 locally joins the communication module 316 through the local connection 330 instead of the network 300. In this way, the communication module 316 (i.e., the network node) acts as a proxy for the metering module 318 (i.e., the edge device) for the joining process. The communication module 316 sends the announcement message (in Figure 4 PANAD message in the figure) to announce the network to the metering module 318. Unlike the joining process of other types of network devices, the announcement is made via the local connection 330 instead of the network 300. At the authentication stage 406, the metering module 318 communicates with the root node 304 to authenticate itself. Figure 4 In the example shown in , the metering module 318 and the root node 304 exchange messages by complying with the Extensible Authentication Protocol (EAP) Transport Layer Security (TLS) authentication protocol to authenticate the metering module 318 and issue and install a paired master key (PMK) on the metering module 318. The PMK can be a shared secret key for one or more communication sessions and can be used to derive other types of keys in these sessions.

[0041] The metering module 318 and the root node 304 further communicate EAPOL (EAP on LAN) key frames to exchange keys between them. For example, the metering module 318 and the root node 304 can participate in a four-way handshake process to establish a paired transient key (PTK) for encrypting traffic between two network devices and a group transient key (GTK) for decrypting multicast and broadcast traffic. These keys may include a public key shared by multiple devices on the network 300 or a unique key for the metering module 318. Once the keys are established and installed on the metering module 318, network layer security has been extended to the metering module 318 through security certificates and network keys. The communication module 316 and the metering module 318 can communicate with each other via the local connection 330 using their respective network keys, thereby establishing a secure channel between them. Using the established secure channel, the communication module 316 (network node) and the metering module 318 (edge ​​device) can communicate outside the network 300, but in a secure manner using network security cryptographic controls (e.g., encryption, integrity checks, etc.). In some examples, in the absence of a secure channel, the communication between the communication module and the metering module is conducted in plain text without encryption or integrity checks on the communication. As such, in some implementations, communication between the communication module and the metering module is not allowed until a secure channel is established. However, in other implementations, such non-secure communication is allowed to ensure that data from the metering module (edge ​​device) is collected by the communication module (network node) before the secure channel is established.

[0042] At the association phase 408, routing information for the metering module 318 is exchanged and a data link between the metering module 318 and the network 300 is established. The data link indicates that the communication between the metering module 318 and other network devices on the network 300 is always through the communication module 316. In this phase, the metering module 318 sends a message 416 to request information about the network configuration from the root node 304. The root node 304 replies with the network configuration information 418 so that the metering module 318 is properly configured on the network. The communication module 316 further sends a RPL (IPv6 Routing Protocol for Low Power and Lossy Networks) DIO (Destination-Oriented Directed Acyclic Graph Information Object) message 420 to the metering module 318 to remind the metering module 318 to periodically announce itself on the network 300. The RPL DIO message can also be sent from the root node 304 or another node configured as a network manager.

[0043] In response, the metering module 318 sends a RPL destination advertisement object (DAO) message 410 to the root node 304 to propagate its destination information (e.g., the address of the metering module 318) to the network so that other nodes or devices on the network 300 know the current address of the metering module 318 and can determine the route to the metering module. Sending the destination information to the root node 304 allows the root node 304 to maintain the routing information. In other examples, the advertisement is not propagated to the root node and the routing is maintained locally. In either case, the routing will always be through the communication module 316 (network node) to which the metering module 318 (edge ​​device) is connected. After determining the routing information, the metering module 318 can communicate on the network 300. The metering module 318 further requests an IP address from the root node 304 through a Dynamic Host Configuration Protocol Version 6 (DHCPV6) request message 412, and the root node 304 replies with the assigned IP address using a DHCPV6 reply message 414. Once the metering module 318 is assigned an IP address, the metering module 318 is interconnected with other network devices on the network 300 and is reachable by other network devices on the network 300 through IP addressing, including other communication modules 316 and the metering module 318 that have been associated with the network 300 as described above. The metering module 318 can operate similarly to other network devices, except that communication with the metering module 318 occurs through the communication module 316. As such, some communications, such as peer-to-peer communications, cannot be performed between other network devices and the metering module 318. In some cases where the network 300 is a private public network, the metering module 318 is not connected to the public Internet. In other cases where network devices in the network 300 are connected to the public Internet, the metering module 318 can also be connected to the public Internet. In order to prevent undesirable communications, the communication module (i.e., network node) associated with the metering module (i.e., edge device) can be configured to only allow routing from an authorized address list to prevent remote communication or interaction with undesirable devices.

[0044] It should be appreciated that while process 400 is described with a focus on mesh network 300, metering modules, and communication modules, it can be applied to other types of networks, network nodes, edge devices, and local connections. Depending on the type of network and the network protocol employed, the messages communicated between network nodes, edge devices, and root nodes / network managers may be different. Further, while the above discussion focuses on scenarios where metering module 318 operates within an IP network, similar processing can be applied to scenarios where metering module 318 operates outside an IP network and is configured to communicate with MAC layer messages.

[0045] In some cases, such as when a network node leaves a network or a network node joins a network, it is necessary to update the routing information of the network. The movement of network nodes can occur, for example, in network migration, i.e., the migration of devices from one network to another, or in connection with network failures such as power outages. In these cases, the process 400 described above can be performed for those network nodes affected by the migration or power outage. In other words, the network node and its connected edge devices can join a new network or rejoin a network by following the process 400.

[0046] Updates to the security of the network may be performed by sending security updates to the edge device (e.g., key rolling, online certificate revocation, online certificate rolling). Removal of edge-connected devices from the network may be performed by the network manager, for example, removing IP addresses and routing information about the edge device from the network. Note that if a network node connected to an edge device is removed, the edge device is no longer able to receive information from the network and is therefore effectively removed from the network.

[0047] In some cases, it is necessary to revoke the security certificate of a locally connected edge device. For example, if the edge device is compromised, the network manager can be configured to revoke the security certificate of the edge device to protect the security of the network. In one example, the network manager generates new keys and new security certificates for all network devices except the edge device, so that the security certificate for the edge device is revoked. In another example, the network manager can broadcast a message to each other network device on the network to instruct those devices not to communicate with the edge device. The network manager can also revoke the edge device by not issuing a new certificate to the edge device. The network manager can utilize various other mechanisms to revoke the security certificate of the edge device. Note that if a network node connected to the edge device is revoked, the edge device can no longer receive information from the network and is therefore effectively revoked.

[0048] It should be noted that revoking an edge device is different from removing a device from a network. Removing a device from a network may include removing the IP address of the device from the network and routing information associated with the device. As a result, the removed device can no longer communicate with any other device on the network. Revoking a device does not necessarily include removing the IP address and routing information. As such, the revoked device can still communicate to the network or otherwise listen for information. For example, if the revocation of an edge device is performed by revoking a network security certificate for the edge device, the edge device may still have a valid key that allows it to communicate with some nodes on the network, such as listening for broadcast or multicast traffic on the network. As a result, the revoked edge device is not immediately removed from the network. However, note that if the key for the network is updated, the revoked device will no longer have a certificate to receive the updated key. At this point, the revoked device can no longer participate in or listen to network traffic that is protected by encrypted messaging.

[0049] Reference Figure 5 , which shows a diagram depicting an example of an endpoint 314 suitable for implementing various aspects of the techniques and technologies presented herein. The endpoint 314 includes a communication module 316 and a metering module 318 connected by a local connection 330. The two modules can be housed in the same unit on a separate board, so the local connection 330 can be an on-board socket. Alternatively, the modules can be separately housed and the local connection 330 can be a communication cable such as a USB cable or another conductor. Since the two components can be physically separated, the communication module 316 and the metering module 318 can be removed or replaced independently of each other. The functions of the communication module 316 include receiving and sending messages through the network 300. The functions of the metering module 318 include the functions required to manage resources, in particular to allow access to resources and to measure the resources used. The communication module 316 can include a communication device 512 such as an antenna and a radio transceiver. Alternatively, the communication device 512 can be any device that allows wireless or wired communication. The communication module 316 can also include a processor 513 and a memory 514. The communication device 512 is used to receive and send messages through the network 300. Processor 513 controls the functions performed by communication module 316 and processor 513 utilizes memory 514 as needed.

[0050] The metering module 318 may include a processor 521, a memory 522, and a measurement circuit 523. The processor 521 in the metering module 318 controls the functions performed by the metering module 318 and utilizes the memory 522 as necessary. The measurement circuit 523 handles the measurement of the resource and may also handle the recording of the measurements taken. Both the communication module 316 and the metering module 318 may include computer-executable instructions stored in a memory or another type of computer-readable medium, and one or more processors within the module may execute the instructions to provide the functionality described herein.

[0051] General considerations

[0052] Although the subject matter has been described in detail with respect to certain aspects of the subject matter, it will be appreciated that those skilled in the art, having gained an understanding of the foregoing, may readily generate modifications, variations, and equivalents to such aspects. It should be understood, therefore, that the present disclosure is presented for purposes of illustration and not limitation, and does not exclude the inclusion of such modifications, variations, and / or additions to the subject matter that would be readily apparent to one of ordinary skill in the art. For example, although a metering implementation has been used for purposes of illustration, the present invention may extend to any type of network endpoint including a communication module and a second module separate from the communication module.

Claims

1. A network endpoint device, comprising: a network node connected to the network and configured to communicate with the network manager and other network nodes of the network, the network node having a first network address; as well as An edge device connected to a network node via a local connection and configured to communicate with the network node through the local connection, wherein the edge device is configured to: Communicate with the network manager through the network node to obtain the security key and security certificate of the edge device; Establishing a secure channel between the network node and the edge device via a local connection using a security key and a security certificate; communicating with a network manager by the network node to exchange routing information and obtain a second network address for the edge device; as well as The network node communicates with another network node in the network using the security key, the security certificate and the second network address. 2 . The network endpoint device of claim 1 , wherein the first network address and the second network address each comprise one or more of an IP address or a LAN address.

3. The network endpoint device according to claim 1, wherein: The network is a mesh network associated with a resource distribution network; A network node is a communication module of a network endpoint device of a mesh network; and An edge device is a metering module of a network endpoint device configured to measure characteristics associated with a resource distribution network.

4. The network endpoint device of claim 1, wherein the secure channel established between the network node and the edge device via the local connection is further based on a security key and a security certificate of the network node.

5. The network endpoint device of claim 1, wherein the routing information specifies that the edge device is reachable via the network node. The network endpoint device of claim 1 , wherein the first network address and the second network address are different.

7. A method for providing a secure local connection between a network node and an edge device in a network, comprising: authenticating, by an edge device connected to a network node of the network via a local connection, the edge device to a network manager of the network; The edge device receives, through the network node, a device certificate and a network key issued by the network manager based on the authentication; Creating a secure channel between the edge device and the network node using device certificates and network keys of the network node and the edge device by the edge device and the network node; The edge device establishes a data link with the network; as well as The edge device communicates with other devices on the network via the network nodes and based on data links.

8. The method according to claim 7, further comprising: An announcement message is sent by a network node to an edge device to announce the network, wherein a network manager is identified by the edge device based on the announcement message.

9. The method of claim 7, wherein establishing a data link with a network comprises: Get configuration data from the network manager; Exchange routing information with the network manager; as well as Obtain the network address for the edge device from the network manager.

10. The method of claim 9, wherein the network address comprises one or more of an Internet Protocol (IP) address or a Local Area Network (LAN) address.

11. The method of claim 9, wherein the network address for the edge device is different from the network address of the network node.

12. The method according to claim 9, wherein: The network is a mesh network associated with a resource distribution network; A network node is a communication module that is an endpoint of a mesh network; and An edge device is a metering module of an endpoint that is configured to measure characteristics associated with a resource distribution network.

13. A system for providing secure local connectivity between a network node and an edge device in a network, comprising: a network manager configured to manage communications between network devices of the network, the network devices including network nodes and edge devices; Endpoint devices are connected to the network manager through the network and are managed by the network manager. Endpoint devices include: a network node connected to the network and configured to communicate with the network manager and other network devices, the network node having a first network address; and An edge device connected to a network node via a local connection and configured to communicate with the network node through the local connection, wherein the edge device is configured to: Communicate with the network manager through the network node to obtain the security key and security certificate of the edge device; Establishing a secure channel between the network node and the edge device via a local connection using a security key and a security certificate; communicating with a network manager by the network node to exchange routing information and obtain a second network address for the edge device; and The network node communicates with another network device in the network using the security key, the security certificate and the second network address.

14. The system of claim 13, wherein the network address comprises one or more of an Internet Protocol (IP) address or a Local Area Network (LAN) address.

15. The system of claim 13, wherein the first network address and the second network address are different.

16. The system of claim 13, wherein the routing information specifies that the edge device of the endpoint device is reachable via the network node of the endpoint device.

17. The system of claim 13, wherein: The network is a mesh network associated with a resource distribution network; A network node is a communication module of an endpoint device of a mesh network; and An edge device is a metering module of an endpoint device configured to measure characteristics associated with a resource distribution network.

18. The system of claim 13, wherein the network manager is further configured to update the security of the network by removing the edge device from the network, the removing comprising removing a network address and routing information of the edge device from the network.

19. The system of claim 13, wherein the network manager is further configured to revoke a security certificate of the edge device, including one or more of the following: Generate new keys and new security certificates for network devices other than edge devices of the network; broadcasting a message to network devices of the network other than the edge device to instruct the network devices not to communicate with the edge device; or Avoid issuing new certificates to edge devices.