ANI Applied in IoT Network Management

When Anima ANI was designed, IoT scenarios were under consideration. For example, one big reason of introducing CBOR encoding in GRASP and choosing CoAP for secure bootstrapping is for the effiecency of transporting packets over lossy IoT networks. This document discusses applying GRASP and ACP into a specific IoT scenario for some network management functions. The characterstics of the scenario is: Low-power wireless field area network dedicated for industrial usage (e.g. 6LoWPAN-based electronic metering network). The topology is mesh. It is natrual for a wireless local network. IPv6 addressing, which is beneficial for auto-configuration L3 routing is enabled (e.g. RPL). Nodes are extremelly resource constraind. (E.g., one typical hardware model only has 128Kbytes RAM and 512Kbytes ROM. ) Gateway is normally a resource rich device, which acts as a management server to the nodes. Normally nodes don't need to communicate with any other entities beyond the gateway. However, some of the ANI designs are not specifically optimized for IoT scenarios: Most of the GRASP messages (except M_Discovery and M_Flood) are over TCP, which is considered as a heavy burden on radio resources for many IoT LLNs. Since GRASP is based on TCP, it lacks reliable transport and fragmentation mechanisms by itself. VRF-based ACP is not applicapable for most of the small IoT devices. This document discusses choosing GRASP as the management protocol over the other two candicates, which are IETF Core technologies and OMA LWM2M technologies. And also discusses a potential lightweight ACP.

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in when they appear in ALL CAPS. When these words are not in ALL CAPS (such as "should" or "Should"), they have their usual English meanings, and are not to be interpreted as key words. This document use the key words defined in . The following additional terms are used throughout this document: IoT: Internet of Things BR: Bord Router CMD: Command ACK: Acknowledgement PLC: Power Line Communication LLN: Low-Power and Lossy Network RF: Radio Frequency TCP: Transport Controll Protocol RPL: IPv6 Routing Protocol for Low-Power and Lossy Networks .

Fig 1. Reference Scenario for Wireless Field Area IoT Networks As Fig 1 depicted, the BR is the root of the wireless network and act as a management server. Each node connects to the BR.

Some IoT network management standardization work has been initialed in the IETF Core working group. describes a network management interface for constrained devices and networks, called CoAP Management Interface (CoMI), which is used to access data resources specified in YANG, or SMIv2 converted to YANG; relevant YANG library for CoMI server and CBOR encoding of data modeled with YANG are also defined. In a nutshell, these work items can be considered as some adaption and optimization of Netconf/YANG technologies for IoT environment. Netconf/YANG mechanisms are capabal of manuplating data orgnized in a sophisticated tree structure. These capabilities are necessary and poweful in managing various device configurations, especially for the sophisticated devices such as router. However, they might be too heavy for an extremly resource constrained device as discribed above. There is neither enough space for storing the programs in ROM, nor running the codes in RAM.

OMA had issued the LWM2M specification, which is also designed for IoT network management. LWM2M also chooses CoAP as the management protocol, but it doesn't choose YANG for data model, rather, it defined some OMA Objects. OMA objects less complete than YANG modeled data; the objects are flat rather than being orgnized as a tree structure. But OMA objects contain also some advanced features such as access control of each object. Plus the CoAP implementation, the LWM2M solution is still not ideal for the targeted scenarios in terms of ROM/RAM ocuppation.

According to , most of the IoT commands are more like "Signallings" rather than traditional "Configurations". It is reasonable because the IoT nodes need to auto-configure themselves as much as possible to gain maximum effiecency. Relying on a centralized server configuring each node is a big challenge to the lossy wireless links and might probably cause significant delay of deployment. Thus, we might need a different approach to consider IoT management than just simply re-using Netconf/YANG in a different context (e.g. CoAP).

This section discusses potential GRASP extention to fulfill the IoT management requirements.

Since TCP requires three times handshake, which would consume too much radio resource, thus it is not acceptable in LLNs. Then UDP is needed.

For some critical messages, the sender would need to confirm the receiver had got the message, thus, there needs to be a reliable transport mechanism extended in application layer (GRASP).

Since the lack of TCP, GRASP also needs to be enhanced with some a fragmentation mechanism.

This section describes a set of IoT network management commands. These commands are based on a real commercial implementation, however, they are general network management functions that not coupled with any specific services. Thus, these command could be considered as a representative of the general requirements of similar scenarios. 1. NETWORK_HEARTBEAT BR sends heartbeat to node, every node relay to forward, ACK is optional. node can send the ACK if needed. 2. NETWORK_DISMISS CMD from BR to Node: No Options are associated with this CMD. This CMD will be sent in broadcast mode. 3. NODE_REMOVE CMD from BR to Node: the destination IPv6 address will identify the target node to be removed. ACK from Node to BR. 4. NODE_LEFT_REPORT Parent node sends a command to BR that a node connected to it has left. BR sends ACK to the parent node. 5. NETWORK_PARA_CONFIG CMD from BR to Node. BR send RF config to every node, based on broadcast relay, ACK is optional. 6. NODE_STATUS Request. Response. 7. NODE_STATISTICS Request. Response. 8. NODE_LOG Request. Response. 9. NODE_RESET first response then reset, when node received this message. (Editor's Note: More commands to be extended.)

We propose to define three Options as the following. Each of the above mentioned IoT management signallings could be fit into one of the three options as different elements. - IoT Node Status Reporting. (Details TBD.) - Management Commands to IoT Nodes. (Details TBD.) - IoT Network/Node Configuration. (Details TBD.)

TBD.

Some technical design work was contributed by Shoushou Ren. Relative implementation experence was shared by Zongxin Dou, Wanhong Wang and Haiyan Mao. Valuable comments were received from Delei Yu, Sheng Jiang and Chuang Wang. This document was produced using the xml2rfc tool .