Internet Engineering Task Force (IETF) M. Ersue, Ed.
Request for Comments: 7548 Nokia Networks
Category: Informational D. Romascanu
ISSN: 2070-1721 Avaya
J. Schoenwaelder
A. Sehgal
Jacobs University Bremen
May 2015
Internet Engineering Task Force (IETF) M. Ersue, Ed.
Request for Comments: 7548 Nokia Networks
Category: Informational D. Romascanu
ISSN: 2070-1721 Avaya
J. Schoenwaelder
A. Sehgal
Jacobs University Bremen
May 2015
Management of Networks with Constrained Devices: Use Cases
设备受限的网络管理：用例
Abstract
摘要
This document discusses use cases concerning the management of networks in which constrained devices are involved. A problem statement, deployment options, and the requirements on the networks with constrained devices can be found in the companion document on "Management of Networks with Constrained Devices: Problem Statement and Requirements" (RFC 7547).
本文档讨论了涉及受约束设备的网络管理的用例。问题陈述、部署选项和设备受限网络的要求可在“设备受限网络的管理：问题陈述和要求”（RFC 7547）的配套文件中找到。
Status of This Memo
关于下段备忘
This document is not an Internet Standards Track specification; it is published for informational purposes.
本文件不是互联网标准跟踪规范；它是为了提供信息而发布的。
This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Not all documents approved by the IESG are a candidate for any level of Internet Standard; see Section 2 of RFC 5741.
本文件是互联网工程任务组（IETF）的产品。它代表了IETF社区的共识。它已经接受了公众审查，并已被互联网工程指导小组（IESG）批准出版。并非IESG批准的所有文件都适用于任何级别的互联网标准；见RFC 5741第2节。
Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc7548.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问http://www.rfc-editor.org/info/rfc7548.
Copyright Notice
版权公告
Copyright (c) 2015 IETF Trust and the persons identified as the document authors. All rights reserved.
版权所有（c）2015 IETF信托基金和确定为文件作者的人员。版权所有。
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License.
本文件受BCP 78和IETF信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。从本文件中提取的代码组件必须包括信托法律条款第4.e节中所述的简化BSD许可证文本，并提供简化BSD许可证中所述的无担保。
Table of Contents
目录
1. Introduction ....................................................3
2. Access Technologies .............................................4
2.1. Constrained Access Technologies ............................4
2.2. Cellular Access Technologies ...............................5
3. Device Life Cycle ...............................................6
3.1. Manufacturing and Initial Testing ..........................6
3.2. Installation and Configuration .............................6
3.3. Operation and Maintenance ..................................7
3.4. Recommissioning and Decommissioning ........................7
4. Use Cases .......................................................8
4.1. Environmental Monitoring ...................................8
4.2. Infrastructure Monitoring ..................................9
4.3. Industrial Applications ...................................10
4.4. Energy Management .........................................12
4.5. Medical Applications ......................................14
4.6. Building Automation .......................................15
4.7. Home Automation ...........................................17
4.8. Transport Applications ....................................18
4.9. Community Network Applications ............................20
4.10. Field Operations .........................................22
5. Security Considerations ........................................23
6. Informative References .........................................24
Acknowledgments ...................................................25
Contributors ......................................................26
Authors' Addresses ................................................26
1. Introduction ....................................................3
2. Access Technologies .............................................4
2.1. Constrained Access Technologies ............................4
2.2. Cellular Access Technologies ...............................5
3. Device Life Cycle ...............................................6
3.1. Manufacturing and Initial Testing ..........................6
3.2. Installation and Configuration .............................6
3.3. Operation and Maintenance ..................................7
3.4. Recommissioning and Decommissioning ........................7
4. Use Cases .......................................................8
4.1. Environmental Monitoring ...................................8
4.2. Infrastructure Monitoring ..................................9
4.3. Industrial Applications ...................................10
4.4. Energy Management .........................................12
4.5. Medical Applications ......................................14
4.6. Building Automation .......................................15
4.7. Home Automation ...........................................17
4.8. Transport Applications ....................................18
4.9. Community Network Applications ............................20
4.10. Field Operations .........................................22
5. Security Considerations ........................................23
6. Informative References .........................................24
Acknowledgments ...................................................25
Contributors ......................................................26
Authors' Addresses ................................................26
Constrained devices (also known as sensors, smart objects, or smart devices) with limited CPU, memory, and power resources can be connected to a network. Such a network of constrained devices itself may be constrained or challenged, e.g., with unreliable or lossy channels, wireless technologies with limited bandwidth and a dynamic topology, needing the service of a gateway or proxy to connect to the Internet. In other scenarios, the constrained devices can be connected to a unconstrained network using off-the-shelf protocol stacks. Constrained devices might be in charge of gathering information in diverse settings including natural ecosystems, buildings, and factories and sending the information to one or more server stations.
CPU、内存和电源资源有限的受约束设备（也称为传感器、智能对象或智能设备）可以连接到网络。这样的受约束设备网络本身可能受到约束或挑战，例如，具有不可靠或有损信道、具有有限带宽和动态拓扑的无线技术，需要网关或代理的服务来连接到因特网。在其他场景中，受约束的设备可以使用现成的协议栈连接到不受约束的网络。受约束的设备可能负责在各种环境中收集信息，包括自然生态系统、建筑物和工厂，并将信息发送到一个或多个服务器站。
Network management is characterized by monitoring network status, detecting faults (and inferring their causes), setting network parameters, and carrying out actions to remove faults, maintain normal operation, and improve network efficiency and application performance. The traditional network management application periodically collects information from a set of managed network elements, it processes the collected data, and it presents the results to the network management users. Constrained devices, however, often have limited power, have low transmission range, and might be unreliable. Such unreliability might arise from device itself (e.g., battery exhausted) or from the channel being constrained (i.e., low-capacity and high-latency). They might also need to work in hostile environments with advanced security requirements or need to be used in harsh environments for a long time without supervision. Due to such constraints, the management of a network with constrained devices offers different types of challenges compared to the management of a traditional IP network.
网络管理的特点是监视网络状态、检测故障（并推断其原因）、设置网络参数、执行操作以消除故障、维持正常运行、提高网络效率和应用程序性能。传统的网络管理应用程序定期从一组被管理的网元收集信息，处理收集的数据，并将结果呈现给网络管理用户。然而，受限制的设备通常功率有限，传输范围小，可能不可靠。这种不可靠性可能由设备本身（例如，电池耗尽）或通道受限（例如，低容量和高延迟）引起。它们可能还需要在具有高级安全要求的敌对环境中工作，或者需要在没有监督的恶劣环境中长时间使用。由于这些限制，与传统IP网络的管理相比，使用受限制设备管理网络带来了不同类型的挑战。
This document aims to understand use cases for the management of a network in which constrained devices are involved. It lists and discusses diverse use cases for management from the network as well as from the application point of view. The list of discussed use cases is not an exhaustive one since other scenarios, currently unknown to the authors, are possible. The application scenarios discussed aim to show where networks of constrained devices are expected to be deployed. For each application scenario, we first briefly describe the characteristics followed by a discussion on how network management can be provided, who is likely going to be responsible for it, and on which time-scale management operations are likely to be carried out.
本文档旨在了解涉及受约束设备的网络管理用例。它列出并讨论了从网络和应用程序角度进行管理的各种用例。讨论的用例列表并非详尽无遗，因为作者目前未知的其他场景是可能的。讨论的应用场景旨在显示受约束设备网络的预期部署位置。对于每个应用场景，我们首先简要描述其特征，然后讨论如何提供网络管理，谁可能负责网络管理，以及可能在哪些时间尺度上执行管理操作。
A problem statement, deployment and management topology options as well as the requirements on the networks with constrained devices can be found in the companion document [RFC7547].
附带文档[RFC7547]中提供了问题说明、部署和管理拓扑选项以及受约束设备网络的要求。
This documents builds on the terminology defined in [RFC7228] and [RFC7547]. [RFC7228] is a base document for the terminology concerning constrained devices and constrained networks. Some use cases specific to IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs) can be found in [RFC6568].
本文件以[RFC7228]和[RFC7547]中定义的术语为基础。[RFC7228]是有关受限设备和受限网络的术语的基础文档。在[RFC6568]中可以找到一些特定于低功耗无线个人区域网络（6LoWPANs）上IPv6的用例。
Besides the management requirements imposed by the different use cases, the access technologies used by constrained devices can impose restrictions and requirements upon the Network Management System (NMS) and protocol of choice.
除了不同用例施加的管理要求外，受约束设备使用的接入技术还可以对网络管理系统（NMS）和所选协议施加限制和要求。
It is possible that some networks of constrained devices might utilize traditional unconstrained access technologies for network access, e.g., local area networks with plenty of capacity. In such scenarios, the constrainedness of the device presents special management restrictions and requirements rather than the access technology utilized.
一些受约束设备的网络可能利用传统的无约束接入技术进行网络接入，例如，具有大量容量的局域网。在这种情况下，设备的约束性提出了特殊的管理限制和要求，而不是所使用的接入技术。
However, in other situations, constrained or cellular access technologies might be used for network access, thereby causing management restrictions and requirements to arise as a result of the underlying access technologies.
然而，在其他情况下，受限或蜂窝接入技术可用于网络接入，从而导致由于底层接入技术而产生管理限制和要求。
A discussion regarding the impact of cellular and constrained access technologies is provided in this section since they impose some special requirements on the management of constrained networks. On the other hand, fixed-line networks (e.g., power-line communications) are not discussed here since tend to be quite static and do not typically impose any special requirements on the management of the network.
本节讨论了蜂窝和受限接入技术的影响，因为它们对受限网络的管理提出了一些特殊要求。另一方面，这里不讨论固定线路网络（例如电力线通信），因为固定线路网络往往是静态的，通常不会对网络的管理提出任何特殊要求。
Due to resource restrictions, embedded devices deployed as sensors and actuators in the various use cases utilize low-power, low-data-rate wireless access technologies such as [IEEE802.15.4], Digital Enhanced Cordless Telecommunication (DECT) Ultra Low Energy (ULE), or Bluetooth Low-Energy (BT-LE) for network connectivity.
由于资源限制，在各种用例中部署为传感器和执行器的嵌入式设备利用低功耗、低数据速率无线接入技术，如[IEEE802.15.4]、数字增强无绳通信（DECT）超低能（ULE）或蓝牙低能（BT-LE）进行网络连接。
In such scenarios, it is important for the NMS to be aware of the restrictions imposed by these access technologies to efficiently manage these constrained devices. Specifically, such low-power, low-
在这种情况下，NMS必须了解这些接入技术施加的限制，以便有效地管理这些受限制的设备。具体来说，就是这样的低功耗、低功耗-
data-rate access technologies typically have small frame sizes. So it would be important for the NMS and management protocol of choice to craft packets in a way that avoids fragmentation and reassembly of packets since this can use valuable memory on constrained devices.
数据速率访问技术通常具有较小的帧大小。因此，NMS和选择的管理协议以避免数据包碎片化和重新组装的方式制作数据包是很重要的，因为这可以在受约束的设备上使用宝贵的内存。
Devices using such access technologies might operate via a gateway that translates between these access technologies and more traditional Internet protocols. A hierarchical approach to device management in such a situation might be useful, wherein the gateway device is in-charge of devices connected to it, while the NMS conducts management operations only to the gateway.
使用这种接入技术的设备可能通过网关运行，网关在这些接入技术和更传统的互联网协议之间转换。在这种情况下，设备管理的分层方法可能有用，其中网关设备负责与其连接的设备，而NMS仅对网关执行管理操作。
Machine-to-machine (M2M) services are increasingly provided by mobile service providers as numerous devices, home appliances, utility meters, cars, video surveillance cameras, and health monitors are connected with mobile broadband technologies. Different applications, e.g., in a home appliance or in-car network, use Bluetooth, Wi-Fi, or ZigBee locally and connect to a cellular module acting as a gateway between the constrained environment and the mobile cellular network.
移动服务提供商越来越多地提供机器对机器（M2M）服务，因为许多设备、家用电器、公用电表、汽车、视频监控摄像机和健康监视器都与移动宽带技术相连接。不同的应用程序（例如，在家用电器或车载网络中）在本地使用蓝牙、Wi-Fi或ZigBee，并连接到蜂窝模块，作为受限环境和移动蜂窝网络之间的网关。
Such a gateway might provide different options for the connectivity of mobile networks and constrained devices:
这种网关可以为移动网络和受约束设备的连接提供不同的选项：
o a smartphone with 3G/4G and WLAN radio might use BT-LE to connect to the devices in a home area network,
o 配备3G/4G和WLAN收音机的智能手机可能会使用BT-LE连接到家庭区域网络中的设备，
o a femtocell might be combined with home gateway functionality acting as a low-power cellular base station connecting smart devices to the application server of a mobile service provider,
o 毫微微蜂窝可以与家庭网关功能相结合，充当将智能设备连接到移动服务提供商的应用服务器的低功率蜂窝基站，
o an embedded cellular module with LTE radio connecting the devices in the car network with the server running the telematics service,
o 带有LTE无线电的嵌入式蜂窝模块，将汽车网络中的设备与运行远程通信服务的服务器连接，
o an M2M gateway connected to the mobile operator network supporting diverse Internet of Things (IoT) connectivity technologies including ZigBee and Constrained Application Protocol (CoAP) over 6LoWPAN over IEEE 802.15.4.
o 连接到移动运营商网络的M2M网关，支持多种物联网（IoT）连接技术，包括ZigBee和受限应用协议（CoAP），覆盖6LoWPAN，覆盖IEEE 802.15.4。
Common to all scenarios above is that they are embedded in a service and connected to a network provided by a mobile service provider. Usually, there is a hierarchical deployment and management topology in place where different parts of the network are managed by different management entities and the count of devices to manage is high (e.g., many thousands). In general, the network is comprised of manifold types and sizes of devices matching to different device
上述所有场景的共同点是，它们嵌入到服务中，并连接到移动服务提供商提供的网络。通常，存在分层部署和管理拓扑，其中网络的不同部分由不同的管理实体管理，并且要管理的设备数量很高（例如，数千台）。通常，网络由多种类型和尺寸的设备组成，这些设备与不同的设备相匹配
classes. As such, the managing entity needs to be prepared to manage devices with diverse capabilities using different communication or management protocols. In the case in which the devices are directly connected to a gateway, they most likely are managed by a management entity integrated with the gateway, which itself is part of the NMS run by the mobile operator. Smartphones or embedded modules connected to a gateway might themselves be in charge of managing the devices on their level. The initial and subsequent configuration of such a device is mainly based on self-configuration and is triggered by the device itself.
上课。因此，管理实体需要准备好使用不同的通信或管理协议来管理具有不同功能的设备。在设备直接连接到网关的情况下，它们很可能由与网关集成的管理实体管理，网关本身是移动运营商运行的NMS的一部分。连接到网关的智能手机或嵌入式模块本身可能负责管理其级别的设备。此类设备的初始和后续配置主要基于自身配置，并由设备本身触发。
The gateway might be in charge of filtering and aggregating the data received from the device as the information sent by the device might be mostly redundant.
网关可能负责过滤和聚合从设备接收的数据，因为设备发送的信息可能大部分是冗余的。
Since constrained devices deployed in a network might go through multiple phases in their lifetime, it is possible for different managers of networks and/or devices to exist during different parts of the device lifetimes. An in-depth discussion regarding the possible device life cycles can be found in [IOT-SEC].
由于部署在网络中的受约束设备可能在其生命周期中经历多个阶段，因此在设备生命周期的不同部分，可能存在不同的网络和/或设备管理器。关于可能的设备生命周期的深入讨论可在[IOT-SEC]中找到。
Typically, the life cycle of a device begins at the manufacturing stage. During this phase, the manufacturer of the device is responsible for the management and configuration of the devices. It is also possible that a certain use case might utilize multiple types of constrained devices (e.g., temperature sensors, lighting controllers, etc.) and these could be manufactured by different entities. As such, during the manufacturing stage, different managers can exist for different devices. Similarly, during the initial testing phase, where device quality-assurance tasks might be performed, the manufacturer remains responsible for the management of devices and networks that might comprise them.
通常，设备的生命周期从制造阶段开始。在此阶段，设备制造商负责设备的管理和配置。某个用例也可能利用多种类型的受约束设备（例如，温度传感器、照明控制器等），这些设备可以由不同的实体制造。因此，在制造阶段，不同的设备可能存在不同的管理者。类似地，在可能执行设备质量保证任务的初始测试阶段，制造商仍然负责管理可能包含它们的设备和网络。
The responsibility of managing the devices must be transferred to the installer during the installation phase. There must exist procedures for transferring management responsibility between the manufacturer and installer. The installer may be the customer or an intermediary contracted to set up the devices and their networks. It is important that the NMS that is utilized allows devices originating at different vendors to be managed, ensuring interoperability between them and the configuration of trust relationships between them as well.
在安装阶段，管理设备的责任必须移交给安装人员。必须有在制造商和安装商之间转移管理责任的程序。安装者可以是客户或签约安装设备及其网络的中介。重要的是，所使用的NMS允许管理来自不同供应商的设备，确保它们之间的互操作性以及它们之间信任关系的配置。
It is possible that the installation and configuration responsibilities might lie with different entities. For example, the installer of a device might only be responsible for cabling a network, physically installing the devices, and ensuring initial network connectivity between them (e.g., configuring IP addresses). Following such an installation, the customer or a subcontractor might actually configure the operation of the device. As such, during installation and configuration multiple parties might be responsible for managing a device and appropriate methods must be available to ensure that this management responsibility is transferred suitably.
安装和配置责任可能由不同的实体承担。例如，设备的安装人员可能只负责连接网络、物理安装设备以及确保它们之间的初始网络连接（例如，配置IP地址）。安装之后，客户或分包商可能会实际配置设备的操作。因此，在安装和配置期间，多方可能负责管理设备，并且必须提供适当的方法以确保适当地转移该管理责任。
At the outset of the operation phase, the operational responsibility of a device and network should be passed on to the customer. It is possible that the customer, however, might contract the maintenance of the devices and network to a subcontractor. In this case, the NMS and management protocol should allow for configuring different levels of access to the devices. Since different maintenance vendors might be used for devices that perform different functions (e.g., HVAC, lighting, etc.), it should also be possible to restrict management access to devices based on the currently responsible manager.
在运行阶段开始时，设备和网络的运行责任应移交给客户。但是，客户可能会将设备和网络的维护工作承包给分包商。在这种情况下，NMS和管理协议应允许配置对设备的不同访问级别。由于不同的维护供应商可能用于执行不同功能的设备（例如，暖通空调、照明等），因此也可以根据当前负责的经理限制对设备的管理访问。
The owner of a device might choose to replace, repurpose, or even decommission it. In each of these cases, either the customer or the contracted maintenance agency must ensure that appropriate steps are taken to meet the end goal.
设备的所有者可能会选择更换、重新调整用途，甚至使其退役。在上述每种情况下，客户或合同维护机构必须确保采取适当步骤以实现最终目标。
In case the devices needs to be replaced, the manager of the network (customer or contractor responsible) must detach the device from the network, remove all appropriate configuration, and discard the device. A new device must then be configured to replace it. The NMS should allow for the transferring of the configuration and replacing an existing device. The management responsibility of the operation/ maintenance manager would end once the device is removed from the network. During the installation of the new replacement device, the same responsibilities would apply as those during the Installation and Configuration phases.
如果需要更换设备，网络经理（负责的客户或承包商）必须将设备与网络分离，移除所有适当的配置，然后丢弃设备。然后必须配置新设备以替换它。NMS应允许传输配置和更换现有设备。一旦设备从网络中移除，操作/维护经理的管理职责将终止。在安装新的更换设备期间，与安装和配置阶段的责任相同。
The device being replaced may not have yet reached end-of-life, and as such, instead of being discarded, it may be installed in a new location. In this case, the management responsibilities are once again resting in the hands of the entities responsible for the Installation and Configuration phases at the new location.
被更换的设备可能尚未达到使用寿命，因此，可以将其安装在新的位置，而不是丢弃。在这种情况下，管理责任再次落在新地点负责安装和配置阶段的实体手中。
If a device is repurposed, then it is possible that the management responsibility for this device changes as well. For example, a device might be moved from one building to another. In this case, the managers responsible for devices and networks in each building could be different. As such, the NMS must not only allow for changing configuration but also the transferring of management responsibilities.
如果重新调整了设备的用途，则该设备的管理责任也可能发生变化。例如，一个设备可能会从一个建筑物移动到另一个建筑物。在这种情况下，负责每个建筑中的设备和网络的经理可能会有所不同。因此，NMS不仅必须允许更改配置，还必须允许管理职责的转移。
In case a device is decommissioned, the management responsibility typically ends at that point.
在设备退役的情况下，管理责任通常在该点结束。
Environmental monitoring applications are characterized by the deployment of a number of sensors to monitor emissions, water quality, or even the movements and habits of wildlife. Other applications in this category include earthquake or tsunami early-warning systems. The sensors often span a large geographic area; they can be mobile; and they are often difficult to replace. Furthermore, the sensors are usually not protected against tampering.
环境监测应用的特点是部署了许多传感器来监测排放物、水质甚至野生动物的活动和习性。这一类的其他应用包括地震或海啸预警系统。传感器通常跨越一个大的地理区域；它们可以是移动的；而且它们往往很难被取代。此外，传感器通常没有防篡改保护。
Management of environmental-monitoring applications is largely concerned with monitoring whether the system is still functional and the roll out of new constrained devices in case the system loses too much of its structure. The constrained devices themselves need to be able to establish connectivity (autoconfiguration), and they need to be able to deal with events such as losing neighbors or being moved to other locations.
环境监测应用程序的管理主要涉及监测系统是否仍能正常工作，以及在系统失去太多结构的情况下推出新的受限设备。受约束的设备本身需要能够建立连接（自动配置），并且需要能够处理诸如失去邻居或被移动到其他位置等事件。
Management responsibility typically rests with the organization running the environmental-monitoring application. Since these monitoring applications must be designed to tolerate a number of failures, the time scale for detecting and recording failures is, for some of these applications, likely measured in hours and repairs might easily take days. In fact, in some scenarios it might be more cost- and time-effective not to repair such devices at all. However, for certain environmental monitoring applications, much tighter time scales may exist and might be enforced by regulations (e.g., monitoring of nuclear radiation).
管理责任通常由运行环境监控应用程序的组织承担。由于这些监控应用程序必须设计为能够容忍大量故障，因此对于其中一些应用程序，检测和记录故障的时间尺度可能以小时为单位，维修可能很容易需要几天。事实上，在某些情况下，根本不修复此类设备可能更具成本效益和时间效益。然而，对于某些环境监测应用，可能存在更严格的时间尺度，并可能通过法规强制执行（例如，核辐射监测）。
Since many applications of environmental-monitoring sensors are likely to be in areas that are important to safety (flood monitoring, nuclear radiation monitoring, etc.), it is important for management protocols and NMSs to ensure appropriate security protections. These protections include not only access control, integrity, and
由于环境监测传感器的许多应用可能位于对安全至关重要的领域（洪水监测、核辐射监测等），因此管理协议和NMS必须确保适当的安全保护。这些保护不仅包括访问控制、完整性和安全性
availability of data, but also provide appropriate mechanisms that can deal with situations that might be categorized as emergencies or when tampering with sensors/data might be detected.
数据的可用性，但也提供适当的机制，可以处理可能被归类为紧急情况或可能检测到篡改传感器/数据的情况。
Infrastructure monitoring is concerned with the monitoring of infrastructures such as bridges, railway tracks, or (offshore) windmills. The primary goal is usually to detect any events or changes of the structural conditions that can impact the risk and safety of the infrastructure being monitored. Another secondary goal is to schedule repair and maintenance activities in a cost-effective manner.
基础设施监测涉及基础设施的监测，如桥梁、铁路轨道或（海上）风车。主要目标通常是检测可能影响所监测基础设施风险和安全的任何事件或结构条件变化。另一个次要目标是以经济高效的方式安排维修和维护活动。
The infrastructure to monitor might be in a factory or spread over a wider area (but difficult to access). As such, the network in use might be based on a combination of fixed and wireless technologies, which use robust networking equipment and support reliable communication via application-layer transactions. It is likely that constrained devices in such a network are mainly C2 devices [RFC7228] and have to be controlled centrally by an application running on a server. In case such a distributed network is widely spread, the wireless devices might use diverse long-distance wireless technologies such as Worldwide Interoperability for Microwave Access (WiMAX) or 3G/LTE. In cases, where an in-building network is involved, the network can be based on Ethernet or wireless technologies suitable for in-building use.
要监控的基础设施可能在工厂中，也可能分布在更大的区域（但难以访问）。因此，所使用的网络可以基于固定和无线技术的组合，其使用健壮的网络设备并支持通过应用层事务的可靠通信。这种网络中受约束的设备可能主要是C2设备[RFC7228]，必须由运行在服务器上的应用程序集中控制。在这种分布式网络被广泛传播的情况下，无线设备可以使用多种远程无线技术，例如全球微波接入互操作性（WiMAX）或3G/LTE。在涉及建筑内网络的情况下，网络可以基于适合建筑内使用的以太网或无线技术。
The management of infrastructure monitoring applications is primarily concerned with the monitoring of the functioning of the system. Infrastructure monitoring devices are typically rolled out and installed by dedicated experts, and updates are rare since the infrastructure itself does not change often. However, monitoring devices are often deployed in unsupervised environments; hence, special attention must be given to protecting the devices from being modified.
基础设施监控应用程序的管理主要涉及系统功能的监控。基础设施监控设备通常由专门的专家推出和安装，由于基础设施本身不经常更改，因此很少进行更新。然而，监测设备通常部署在无监督的环境中；因此，必须特别注意保护装置不被修改。
Management responsibility typically rests with the organization owning the infrastructure or responsible for its operation. The time scale for detecting and recording failures is likely measured in hours and repairs might easily take days. However, certain events (e.g., natural disasters) may require that status information be obtained much more quickly and that replacements of failed sensors can be rolled out quickly (or redundant sensors are activated quickly). In case the devices are difficult to access, a self-healing feature on the device might become necessary. Since infrastructure monitoring is closely related to ensuring safety,
管理责任通常由拥有基础设施或负责其运营的组织承担。检测和记录故障的时间尺度可能以小时为单位，维修可能很容易需要几天。但是，某些事件（如自然灾害）可能需要更快地获取状态信息，并快速推出故障传感器的更换件（或快速激活冗余传感器）。如果设备难以访问，则可能需要设备上的自愈功能。由于基础设施监测与确保安全密切相关，
management protocols and systems must provide appropriate security protections to ensure confidentiality, integrity, and availability of data.
管理协议和系统必须提供适当的安全保护，以确保数据的机密性、完整性和可用性。
Industrial Applications and smart manufacturing refer to tasks such as networked control and monitoring of manufacturing equipment, asset and situation management, or manufacturing process control. For the management of a factory, it is becoming essential to implement smart capabilities. From an engineering standpoint, industrial applications are intelligent systems enabling rapid manufacturing of new products, dynamic response to product demands, and real-time optimization of manufacturing production and supply-chain networks. Potential industrial applications (e.g., for smart factories and smart manufacturing) are:
工业应用和智能制造是指制造设备的网络控制和监控、资产和状况管理或制造过程控制等任务。对于工厂的管理而言，实施智能功能变得至关重要。从工程的角度来看，工业应用是智能系统，能够快速制造新产品，动态响应产品需求，实时优化制造生产和供应链网络。潜在的工业应用（例如，智能工厂和智能制造）包括：
o Digital control systems with embedded, automated process controls; operator tools; and service information systems optimizing plant operations and safety.
o 具有嵌入式自动化过程控制的数字控制系统；操作员工具；和服务信息系统，优化电厂运行和安全。
o Asset management using predictive maintenance tools, statistical evaluation, and measurements maximizing plant reliability.
o 使用预测性维护工具、统计评估和测量进行资产管理，最大限度地提高电厂可靠性。
o Smart sensors detecting anomalies to avoid abnormal or catastrophic events.
o 智能传感器检测异常，以避免异常或灾难性事件。
o Smart systems integrated within the industrial energy-management system and externally with the smart grid enabling real-time energy optimization.
o 智能系统集成在工业能源管理系统内，外部与智能电网集成，实现实时能源优化。
Management of Industrial Applications and smart manufacturing may, in some situations, involve Building Automation tasks such as control of energy, HVAC, lighting, or access control. Interacting with management systems from other application areas might be important in some cases (e.g., environmental monitoring for electric energy production, energy management for dynamically scaling manufacturing, vehicular networks for mobile asset tracking). Management of constrained devices and networks may not only refer to the management of their network connectivity. Since the capabilities of constrained devices are limited, it is quite possible that a management system would even be required to configure, monitor, and operate the primary functions for which a constrained device is utilized, besides managing its network connectivity.
在某些情况下，工业应用和智能制造的管理可能涉及楼宇自动化任务，如能源控制、HVAC、照明或访问控制。在某些情况下，与其他应用领域的管理系统交互可能很重要（例如，电能生产的环境监测、动态缩放制造的能源管理、移动资产跟踪的车辆网络）。受约束设备和网络的管理可能不仅仅指对其网络连接的管理。由于受约束设备的能力有限，除了管理其网络连接外，很可能还需要管理系统来配置、监控和操作受约束设备所使用的主要功能。
Sensor networks are an essential technology used for smart manufacturing. Measurements, automated controls, plant optimization, health and safety management, and other functions are provided by a
传感器网络是用于智能制造的关键技术。测量、自动控制、工厂优化、健康和安全管理以及其他功能由
large number of networked sectors. Data interoperability and seamless exchange of product, process, and project data are enabled through interoperable data systems used by collaborating divisions or business systems. Intelligent automation and learning systems are vital to smart manufacturing, but they must be effectively integrated with the decision environment. The NMS utilized must ensure timely delivery of sensor data to the control unit so it may take appropriate decisions. Similarly, the relaying of commands must also be monitored and managed to ensure optimal functioning. Wireless sensor networks (WSNs) have been developed for machinery Condition-based Maintenance (CBM) as they offer significant cost savings and enable new functionalities. Inaccessible locations, rotating machinery, hazardous areas, and mobile assets can be reached with wireless sensors. Today, WSNs can provide wireless link reliability, real-time capabilities, and quality-of-service and they can enable industrial and related wireless sense and control applications.
大量联网的部门。通过协作部门或业务系统使用的可互操作数据系统，实现产品、流程和项目数据的数据互操作性和无缝交换。智能自动化和学习系统对智能制造至关重要，但它们必须与决策环境有效集成。所使用的NMS必须确保及时将传感器数据传送到控制单元，以便其做出适当的决定。同样，还必须监控和管理命令的中继，以确保最佳功能。无线传感器网络（WSN）是为基于机械状态的维修（CBM）而开发的，因为它们可以显著节约成本并实现新功能。无线传感器可以到达无法到达的位置、旋转机械、危险区域和移动资产。如今，无线传感器网络可以提供无线链路可靠性、实时能力和服务质量，并且可以实现工业和相关的无线传感和控制应用。
Management of industrial and factory applications is largely focused on monitoring whether the system is still functional, real-time continuous performance monitoring, and optimization as necessary. The factory network might be part of a campus network or connected to the Internet. The constrained devices in such a network need to be able to establish configuration themselves (autoconfiguration) and might need to deal with error conditions as much as possible locally. Access control has to be provided with multi-level administrative access and security. Support and diagnostics can be provided through remote monitoring access centralized outside of the factory.
工业和工厂应用程序的管理主要集中于监控系统是否仍然正常工作、实时连续性能监控以及必要时的优化。工厂网络可能是校园网的一部分，也可能连接到Internet。这种网络中受约束的设备需要能够自行建立配置（自动配置），并且可能需要在本地尽可能多地处理错误情况。访问控制必须具有多级管理访问和安全性。可通过工厂外集中的远程监控访问提供支持和诊断。
Factory-automation tasks require that continuous monitoring be used to optimize production. Groups of manufacturing and monitoring devices could be defined to establish relationships between them. To ensure timely optimization of processes, commands from the NMS must arrive at all destination within an appropriate duration. This duration could change based on the manufacturing task being performed. Installation and operation of factory networks have different requirements. During the installation phase, many networks, usually distributed along different parts of the factory/ assembly line, coexist without a connection to a common backbone. A specialized installation tool is typically used to configure the functions of different types of devices, in different factory locations, in a secure manner. At the end of the installation phase, interoperability between these stand-alone networks and devices must be enabled. During the operation phase, these stand-alone networks are connected to a common backbone so that they may retrieve control information from and send commands to appropriate devices.
工厂自动化任务要求使用连续监控来优化生产。可以定义制造和监控设备组，以建立它们之间的关系。为了确保及时优化流程，来自NMS的命令必须在适当的时间内到达所有目的地。此持续时间可能会根据正在执行的制造任务而变化。工厂网络的安装和运行有不同的要求。在安装阶段，许多网络（通常分布在工厂/装配线的不同部分）共存，没有连接到公共主干网。专用安装工具通常用于以安全的方式在不同的工厂位置配置不同类型设备的功能。在安装阶段结束时，必须启用这些独立网络和设备之间的互操作性。在运行阶段，这些独立网络连接到公共主干网，以便它们可以从适当的设备检索控制信息并向适当的设备发送命令。
Management responsibility is typically owned by the organization running the industrial application. Since the monitoring applications must handle a potentially large number of failures, the time scale for detecting and recording failures is, for some of these applications, likely measured in minutes. However, for certain industrial applications, much tighter time scales may exist, e.g., in real-time, which might be enforced by the manufacturing process or the use of critical material. Management protocols and NMSs must ensure appropriate access control since different users of industrial control systems will have varying levels of permissions. For example, while supervisors might be allowed to change production parameters, they should not be allowed to modify the functional configuration of devices like a technician should. It is also important to ensure integrity and availability of data since malfunctions can potentially become safety issues. This also implies that management systems must be able to react to situations that may pose dangers to worker safety.
管理职责通常由运行工业应用程序的组织负责。由于监控应用程序必须处理潜在的大量故障，因此对于其中一些应用程序，检测和记录故障的时间尺度可能以分钟为单位。然而，对于某些工业应用，可能存在更严格的时间尺度，例如实时，这可能由制造过程或关键材料的使用强制执行。管理协议和NMS必须确保适当的访问控制，因为工业控制系统的不同用户将拥有不同级别的权限。例如，虽然可能允许主管更改生产参数，但不应允许他们像技术人员那样修改设备的功能配置。确保数据的完整性和可用性也很重要，因为故障可能会成为安全问题。这也意味着管理系统必须能够对可能危及工人安全的情况作出反应。
The EMAN working group developed an energy-management framework [RFC7326] for devices and device components within or connected to communication networks. This document observes that one of the challenges of energy management is that a power distribution network is responsible for the supply of energy to various devices and components, while a separate communication network is typically used to monitor and control the power distribution network. Devices in the context of energy management can be monitored for parameters like power, energy, demand and power quality. If a device contains batteries, they can be also monitored and managed.
EMAN工作组为通信网络内或连接到通信网络的设备和设备组件开发了能源管理框架[RFC7326]。本文件指出，能源管理的挑战之一是配电网负责向各种设备和组件提供能源，而单独的通信网络通常用于监控配电网。能源管理环境中的设备可以监控功率、能源、需求和电能质量等参数。如果设备包含电池，也可以对其进行监控和管理。
Energy devices differ in complexity and may include basic sensors or switches, specialized electrical meters, or power distribution units (PDU), and subsystems inside the network devices (routers, network switches) or home or industrial appliances. The operators of an energy-management system are either the utility providers or customers that aim to control and reduce the energy consumption and the associated costs. The topology in use differs and the deployment can cover areas from small surfaces (individual homes) to large geographical areas. The EMAN requirements document [RFC6988] discusses the requirements for energy management concerning monitoring and control functions.
能源设备的复杂性不同，可能包括基本传感器或交换机、专用电表或配电装置（PDU）以及网络设备（路由器、网络交换机）或家用或工业设备内的子系统。能源管理系统的运营商是公用事业供应商或客户，旨在控制和降低能源消耗和相关成本。使用的拓扑不同，部署可以覆盖从小表面（单个住宅）到大地理区域的区域。EMAN要求文件[RFC6988]讨论了有关监测和控制功能的能源管理要求。
It is assumed that energy management will apply to a large range of devices of all classes and networks topologies. Specific resource monitoring, like battery utilization and availability, may be specific to devices with lower physical resources (device classes C0 or C1 [RFC7228]).
假设能量管理将应用于所有类别和网络拓扑的大范围设备。特定资源监控，如电池利用率和可用性，可能特定于物理资源较低的设备（设备类别C0或C1[RFC7228]）。
Energy management is especially relevant to the Smart Grid. A Smart Grid is an electrical grid that uses data networks to gather and act on energy and power-related information in an automated fashion with the goal to improve the efficiency, reliability, economics, and sustainability of the production and distribution of electricity.
能源管理与智能电网尤其相关。智能电网是一种电网，它使用数据网络以自动化方式收集和处理能源和电力相关信息，目的是提高发电和配电的效率、可靠性、经济性和可持续性。
Smart Metering is a good example of an energy-management application based on Smart Grid. Different types of possibly wireless small meters all together produce a large amount of data, which is collected by a central entity and processed by an application server, which may be located within the customer's residence or off site in a data center. The communication infrastructure can be provided by a mobile network operator as the meters in urban areas will most likely have a cellular or WiMAX radio. In case the application server is located within the residence, such meters are more likely to use Wi-Fi protocols to interconnect with an existing network.
智能计量是基于智能电网的能源管理应用的一个很好的例子。不同类型的可能是无线的小型电表一起产生大量数据，这些数据由中心实体收集并由应用服务器处理，应用服务器可能位于客户住宅内或数据中心的场外。通信基础设施可由移动网络运营商提供，因为城市地区的电表最有可能配备蜂窝或WiMAX无线电。如果应用服务器位于住宅内，此类电表更有可能使用Wi-Fi协议与现有网络互连。
An Advanced Metering Infrastructure (AMI) network is another example of the Smart Grid that enables an electric utility to retrieve frequent electric usage data from each electric meter installed at a customer's home or business. Unlike Smart Metering, in which case the customer or their agents install appliance-level meters, an AMI is typically managed by the utility providers and could also include other distribution automation devices like transformers and reclosers. Meters in AMI networks typically contain constrained devices that connect to mesh networks with a low-bandwidth radio. Usage data and outage notifications can be sent by these meters to the utility's headend systems, via aggregation points of higher-end router devices that bridge the constrained network to a less constrained network via cellular, WiMAX, or Ethernet. Unlike meters, these higher-end devices might be installed on utility poles owned and operated by a separate entity.
高级计量基础设施（AMI）网络是智能电网的另一个例子，它使电力公司能够从安装在客户家中或企业的每个电表中检索频繁的用电数据。与智能计量不同，在这种情况下，客户或其代理安装设备级仪表，AMI通常由公用事业提供商管理，还可以包括变压器和重合闸等其他配电自动化设备。AMI网络中的仪表通常包含连接到具有低带宽无线电的网状网络的受限设备。这些电表可以通过高端路由器设备的聚合点将使用数据和中断通知发送到公用事业的前端系统，这些设备通过蜂窝、WiMAX或以太网将受约束的网络连接到受约束较少的网络。与电表不同，这些高端设备可能安装在由独立实体拥有和运营的电线杆上。
It thereby becomes important for a management application not only to be able to work with diverse types of devices, but also to work over multiple links that might be operated and managed by separate entities, each having divergent policies for their own devices and network segments. During management operations, like firmware updates, it is important that the management systems perform robustly in order to avoid accidental outages of critical power systems that could be part of AMI networks. In fact, since AMI networks must also report on outages, the management system might have to manage the energy properties of battery-operated AMI devices themselves as well.
因此，对于管理应用程序来说，不仅能够使用不同类型的设备，而且能够在可能由单独实体操作和管理的多个链路上工作变得非常重要，每个实体对其自己的设备和网段具有不同的策略。在管理操作（如固件更新）期间，重要的是管理系统运行稳健，以避免可能是AMI网络一部分的关键电源系统意外停机。事实上，由于AMI网络也必须报告停机情况，因此管理系统可能还必须管理电池供电的AMI设备本身的能量属性。
A management system for home-based Smart Metering solutions is likely to have devices laid out in a simple topology. However, AMI network installations could have thousands of nodes per router, i.e., higher-end device, which organize themselves in an ad hoc manner. As such,
基于家庭的智能计量解决方案的管理系统可能以简单的拓扑结构布置设备。然而，AMI网络安装可能在每个路由器（即高端设备）上有数千个节点，这些节点以一种特殊的方式进行组织。像这样的
a management system for AMI networks will need to discover and operate over complex topologies as well. In some situations, it is possible that the management system might also have to set up and manage the topology of nodes, especially critical routers. Encryption-key management and sharing in both types of networks are also likely to be important for providing confidentiality for all data traffic. In AMI networks, the key may be obtained by a meter only after an end-to-end authentication process based on certificates. The Smart Metering solution could adopt a similar approach or the security may be implied due to the encrypted Wi-Fi networks they become part of.
AMI网络的管理系统也需要在复杂的拓扑结构上发现和运行。在某些情况下，管理系统可能还必须设置和管理节点的拓扑，特别是关键路由器。这两种网络中的加密密钥管理和共享对于为所有数据流量提供机密性也可能很重要。在AMI网络中，只有在基于证书的端到端认证过程之后，电表才能获得密钥。智能计量解决方案可以采用类似的方法，或者由于它们成为加密Wi-Fi网络的一部分，因此可能隐含安全性。
The management of such a network requires end-to-end management of and information exchange through different types of networks. However, as of today, there is no integrated energy-management approach and no common information model available. Specific energy-management applications or network islands use their own management mechanisms.
这种网络的管理需要通过不同类型的网络进行端到端的管理和信息交换。然而，到目前为止，还没有综合能源管理方法和通用信息模型。特定的能源管理应用程序或网络孤岛使用它们自己的管理机制。
Constrained devices can be seen as an enabling technology for advanced and possibly remote health-monitoring and emergency-notification systems, ranging from monitors for blood pressure and heart rate to advanced devices capable of monitoring implanted technologies, such as pacemakers or advanced hearing aids. Medical sensors may not only be attached to human bodies, they might also exist in the infrastructure used by humans such as bathrooms or kitchens. Medical applications will also be used to ensure treatments are being applied properly, and they might guide people losing orientation. Fitness and wellness applications, such as connected scales or wearable heart monitors, encourage consumers to exercise and empower self-monitoring of key fitness indicators. Different applications use Bluetooth, Wi-Fi, or ZigBee connections to access the patient's smartphone or home cellular connection to access the Internet.
受约束设备可被视为先进且可能是远程健康监测和紧急通知系统的一种使能技术，从血压和心率监测器到能够监测植入技术的先进设备，如起搏器或先进助听器。医疗传感器不仅可以连接到人体，还可能存在于人类使用的基础设施中，如浴室或厨房。医疗应用也将被用于确保治疗的正确应用，并且可能会引导人们迷失方向。健身和健康应用，如连接秤或可穿戴心脏监护仪，鼓励消费者锻炼，并增强对关键健身指标的自我监控能力。不同的应用程序使用蓝牙、Wi-Fi或ZigBee连接访问患者的智能手机，或使用家庭蜂窝连接访问互联网。
Constrained devices that are part of medical applications are managed either by the users of those devices or by an organization providing medical (monitoring) services for physicians. In the first case, management must be automatic and/or easy to install and set up by laypeople. In the second case, it can be expected that devices will be controlled by specially trained people. In both cases, however, it is crucial to protect the safety and privacy of the people who use medical devices. Security precautions to protect access (authentication, encryption, integrity protections, etc.) to such devices may be critical to safeguarding the individual. The level of access granted to different users also may need to be regulated. For
作为医疗应用程序一部分的受限设备由这些设备的用户或为医生提供医疗（监测）服务的组织进行管理。在第一种情况下，管理必须是自动的和/或易于由外行安装和设置的。在第二种情况下，可以预期设备将由经过专门培训的人员控制。然而，在这两种情况下，保护医疗设备使用者的安全和隐私至关重要。保护对此类设备的访问（身份验证、加密、完整性保护等）的安全预防措施可能对保护个人安全至关重要。可能还需要对授予不同用户的访问级别进行监管。对于
example, an authorized surgeon or doctor must be allowed to configure all necessary options on the devices; however, a nurse or technician may only be allowed to retrieve data that can assist in diagnosis. Even though the data collected by a heart monitor might be protected, the pure fact that someone carries such a device may need protection. As such, certain medical appliances may not want to participate in discovery and self-configuration protocols in order to remain invisible.
例如，必须允许授权外科医生或医生在设备上配置所有必要的选项；但是，护士或技术人员只能检索有助于诊断的数据。即使心脏监护仪收集的数据可能会受到保护，但有人携带这种设备这一事实可能需要保护。因此，某些医疗设备可能不想参与发现和自我配置协议，以保持不可见。
Many medical devices are likely to be used (and relied upon) to provide data to physicians in critical situations in which the patient might not be able to report such data themselves. Timely delivery of data can be quite important in certain applications like patient-mobility monitoring in nursing homes. Data must reach the physician and/or emergency services within specified limits of time in order to be useful. As such, fault detection of the communication network or the constrained devices becomes a crucial function of the management system that must be carried out with high reliability and, depending on the medical appliance and its application, within seconds.
许多医疗设备可能被用于（并依赖于）在患者无法自行报告此类数据的危急情况下向医生提供数据。在某些应用中，数据的及时传递非常重要，如疗养院中的患者移动监测。数据必须在规定的时间范围内送达医生和/或急救服务部门，以便有用。因此，通信网络或受约束设备的故障检测成为管理系统的关键功能，必须以高可靠性执行，并且取决于医疗器械及其应用，必须在几秒钟内完成。
Building automation comprises the distributed systems designed and deployed to monitor and control the mechanical, electrical, and electronic systems inside buildings with various destinations (e.g., public and private, industrial, institutions, or residential). Advanced Building Automation Systems (BASs) may be deployed concentrating the various functions of safety, environmental control, occupancy, and security. Increasingly, the deployment of the various functional systems is connected to the same communication infrastructure (possibly IP-based), which may involve wired or wireless communication networks inside the building.
楼宇自动化包括设计和部署的分布式系统，用于监测和控制具有不同目的地（例如公共和私人、工业、机构或住宅）的建筑物内的机械、电气和电子系统。可以部署高级楼宇自动化系统（BASs），集中安全、环境控制、占用和安保的各种功能。各种功能系统的部署越来越多地连接到相同的通信基础设施（可能基于IP），这可能涉及建筑物内的有线或无线通信网络。
Building automation requires the deployment of a large number (10 to 100,000) of sensors that monitor the status of devices, parameters inside the building, and controllers with different specialized functionality for areas within the building or the totality of the building. Inter-node distances between neighboring nodes vary from 1 to 20 meters. The NMS must, as a result, be able to manage and monitor a large number of devices, which may be organized in multi-hop meshed networks. Distances between the nodes, and the use of constrained protocols, means that networks of nodes might be segmented. The management of such network segments and nodes in these segments should be possible. Contrary to home automation, in building management the devices are expected to be managed assets and known to a set of commissioning tools and a data storage, such that every connected device has a known origin. This requires the
楼宇自动化需要部署大量（10至100000）传感器，用于监测设备状态、楼宇内参数以及具有不同专门功能的控制器，用于楼宇内区域或整个楼宇。相邻节点之间的节点间距离从1米到20米不等。因此，NMS必须能够管理和监控大量设备，这些设备可以组织在多跳网状网络中。节点之间的距离以及受限协议的使用意味着节点网络可能被分割。应该能够管理这些网段和这些网段中的节点。与家庭自动化相反，在楼宇管理中，设备应为一组调试工具和数据存储器已知的管理资产，以便每个连接的设备都有一个已知的来源。这需要
management system to be able to discover devices on the network and ensure that the expected list of devices is currently matched. Management here includes verifying the presence of the expected devices and detecting the presence of unwanted devices.
管理系统能够发现网络上的设备，并确保当前匹配预期的设备列表。这里的管理包括验证预期设备的存在和检测不需要的设备的存在。
Examples of functions performed by controllers in building automation are regulating the quality, humidity, and temperature of the air inside the building as well as regulating the lighting. Other systems may report the status of the machinery inside the building like elevators or inside the rooms like projectors in meeting rooms. Security cameras and sensors may be deployed and operated on separate dedicated infrastructures connected to the common backbone. The deployment area of a BAS is typically inside one building (or part of it) or several buildings geographically grouped in a campus. A building network can be composed of network segments, where a network segment covers a floor, an area on the floor, or a given functionality (e.g., security cameras). It is possible that the management tasks of different types of some devices might be separated from others (e.g, security cameras might operate and be managed via a network separate from that of the HVAC in a building).
建筑物自动化中控制器执行的功能示例包括调节建筑物内空气的质量、湿度和温度以及调节照明。其他系统可能会报告建筑物内机械的状态，如电梯或会议室中的投影仪。安全摄像头和传感器可以在连接到公共主干的独立专用基础设施上部署和操作。BAS的部署区域通常位于一座建筑物（或其一部分）内，或在校园内地理上分组的多座建筑物内。建筑网络可以由网段组成，其中网段覆盖楼层、楼层上的区域或给定功能（例如，安全摄像头）。不同类型的某些设备的管理任务可能与其他设备分离（例如，安全摄像头可能通过与建筑物内HVAC网络分离的网络进行操作和管理）。
Some of the sensors in BASs (for example, fire alarms or security systems) register, record, and transfer critical alarm information; therefore, they must be resilient to events like loss of power or security attacks. A management system must be able to deal with unintentional segmentation of networks due to power loss or channel unavailability. It must also be able to detect security events. Due to specific operating conditions required from certain devices, there might be a need to certify components and subsystems operating in such constrained conditions based on specific requirements. Also, in some environments, the malfunctioning of a control system (like temperature control) needs to be reported in the shortest possible time. Complex control systems can misbehave, and their critical status reporting and safety algorithms need to be basic and robust and perform even in critical conditions. Providing this monitoring, configuration and notification service is an important task of the management system used in building automation.
BASs中的一些传感器（例如，火灾报警或安全系统）登记、记录和传输关键报警信息；因此，它们必须能够抵御断电或安全攻击等事件。管理系统必须能够处理由于断电或通道不可用而导致的网络意外分割。它还必须能够检测安全事件。由于某些设备需要特定的操作条件，可能需要根据特定要求认证在此类约束条件下运行的组件和子系统。此外，在某些环境中，需要在尽可能短的时间内报告控制系统（如温度控制）的故障。复杂的控制系统可能会出现错误行为，它们的临界状态报告和安全算法需要是基本的、健壮的，甚至在临界条件下也能执行。提供这种监控、配置和通知服务是楼宇自动化管理系统的一项重要任务。
In some cases, building automation solutions are deployed in newly designed buildings; in other cases, it might be over existing infrastructures. In the first case, there is a broader range of possible solutions, which can be planned for the infrastructure of the building. In the second case, the solution needs to be deployed over an existing infrastructure taking into account factors like existing wiring, distance limitations, and the propagation of radio signals over walls and floors, thereby making deployment difficult. As a result, some of the existing WLAN solutions (e.g., [IEEE802.11] or [IEEE802.15]) may be deployed. In mission-critical or security-
在某些情况下，建筑自动化解决方案部署在新设计的建筑中；在其他情况下，它可能会覆盖现有的基础设施。在第一种情况下，可以为建筑物的基础设施规划更广泛的可能解决方案。在第二种情况下，需要在现有基础设施上部署解决方案，同时考虑到现有布线、距离限制以及无线电信号在墙壁和地板上的传播等因素，从而使部署变得困难。因此，可以部署一些现有的WLAN解决方案（例如，[IEEE802.11]或[IEEE802.15]）。在关键任务或安全方面-
sensitive environments and in cases where link failures happen often, topologies that allow for reconfiguration of the network and connection continuity may be required. Some of the sensors deployed in building automation may be very simple constrained devices for which C0 or C1 [RFC7228] may be assumed.
在敏感环境和经常发生链路故障的情况下，可能需要允许重新配置网络和连接连续性的拓扑。楼宇自动化中部署的一些传感器可能是非常简单的受限设备，可以假设为C0或C1[RFC7228]。
For lighting applications, groups of lights must be defined and managed. Commands to a group of light must arrive within 200 ms at all destinations. The installation and operation of a building network has different requirements. During the installation, many stand-alone networks of a few to 100 nodes coexist without a connection to the backbone. During this phase, the nodes are identified with a network identifier related to their physical location. Devices are accessed from an installation tool to connect them to the network in a secure fashion. During installation, the setting of parameters of common values to enable interoperability may be required. During operation, the networks are connected to the backbone while maintaining the network identifier to physical location relation. Network parameters like address and name are stored in the DNS. The names can assist in determining the physical location of the device.
对于照明应用，必须定义和管理灯光组。对一组灯光的命令必须在200毫秒内到达所有目的地。建筑网络的安装和运行有不同的要求。在安装过程中，许多只有几个到100个节点的独立网络共存，而没有与主干网的连接。在此阶段，节点通过与其物理位置相关的网络标识符进行标识。通过安装工具访问设备，以安全方式将其连接到网络。在安装过程中，可能需要设置通用值的参数以实现互操作性。在操作期间，网络连接到主干网，同时保持网络标识符与物理位置的关系。地址和名称等网络参数存储在DNS中。这些名称有助于确定设备的物理位置。
It is also important for a building automation NMS to take safety and security into account. Ensuring privacy and confidentiality of data, such that unauthorized parties do not get access to it, is likely to be important since users' individual behaviors could be potentially understood via their settings. Appropriate security considerations for authorization and access control to the NMS is also important since different users are likely to have varied levels of operational permissions in the system. For example, while end users should be able to control lighting systems, HVAC systems, etc., only qualified technicians should be able to configure parameters that change the fundamental operation of a device. It is also important for devices and the NMS to be able to detect and report any tampering they might find, since these could lead to potential user safety concerns, e.g., if sensors controlling air quality are tampered with such that the levels of carbon monoxide become life threatening. This implies that an NMS should also be able to deal with and appropriately prioritize situations that might potentially lead to safety concerns.
楼宇自动化NMS还必须考虑到安全性。确保数据的隐私性和机密性，使未经授权的方无法访问数据，这可能很重要，因为用户的个人行为可能通过他们的设置被理解。对NMS的授权和访问控制的适当安全考虑也很重要，因为不同的用户可能在系统中拥有不同级别的操作权限。例如，虽然最终用户应该能够控制照明系统、HVAC系统等，但只有合格的技术人员才能配置改变设备基本操作的参数。设备和NMS能够检测并报告其可能发现的任何篡改也很重要，因为这可能会导致潜在的用户安全问题，例如，如果控制空气质量的传感器被篡改，导致一氧化碳水平威胁生命。这意味着NMS还应能够处理可能导致安全问题的情况，并适当确定其优先级。
Home automation includes the control of lighting, heating, ventilation, air conditioning, appliances, entertainment and home security devices to improve convenience, comfort, energy efficiency, and safety. It can be seen as a residential extension of building automation. However, unlike a BAS, the infrastructure in a home is operated in a considerably more ad hoc manner. While in some
家庭自动化包括照明、供暖、通风、空调、家电、娱乐和家庭安全设备的控制，以提高便利性、舒适性、能效和安全性。它可以看作是楼宇自动化的住宅延伸。然而，与BAS不同的是，家庭中的基础设施是以一种非常特别的方式运行的。在某些情况下
installations it is likely that there is no centralized management system akin to a BAS available, in other situations outsourced and cloud-based systems responsible for managing devices in the home might be used.
安装可能没有类似于BAS的集中式管理系统，在其他情况下，可能会使用负责管理家庭设备的外包和基于云的系统。
Home-automation networks need a certain amount of configuration (associating switches or sensors to actuators) that is either provided by electricians deploying home-automation solutions, by third-party home-automation service providers (e.g., small specialized companies or home-automation device manufacturers) or by residents by using the application user interface provided by home-automation devices to configure (parts of) the home-automation solution. Similarly, failures may be reported via suitable interfaces to residents or they might be recorded and made available to services providers in charge of the maintenance of the home-automation infrastructure.
家庭自动化网络需要一定数量的配置（将开关或传感器与执行器关联），这些配置由部署家庭自动化解决方案的电工、第三方家庭自动化服务提供商（如小型专业公司或家庭自动化设备制造商）提供或者由住户使用家庭自动化设备提供的应用程序用户界面来配置（部分）家庭自动化解决方案。类似地，可以通过适当的接口向住户报告故障，也可以记录故障并提供给负责维护家庭自动化基础设施的服务提供商。
The management responsibility either lies with the residents or is outsourced to electricians and/or third parties providing management of home-automation solutions as a service. A varying combination of electricians, service providers, or the residents may be responsible for different aspects of managing the infrastructure. The time scale for failure detection and resolution is, in many cases, likely counted in hours to days.
管理责任要么在于住户，要么外包给电工和/或作为服务提供家庭自动化解决方案管理的第三方。电工、服务提供商或居民的不同组合可能负责管理基础设施的不同方面。在许多情况下，故障检测和解决的时间尺度可能以小时到天为单位。
"Transport application" is a generic term for the integrated application of communications, control, and information processing in a transportation system. "Transport telematics" and "vehicle telematics" are both used as terms for the group of technologies that support transportation systems. Transport applications running on such a transportation system cover all modes of the transport and consider all elements of the transportation system, i.e. the vehicle, the infrastructure, and the driver or user, interacting together dynamically. Examples for transport applications are inter- and intra-vehicular communication, smart traffic control, smart parking, electronic toll-collection systems, logistic and fleet management, vehicle control, and safety and roadside assistance.
“交通应用”是交通系统中通信、控制和信息处理综合应用的通用术语。“运输远程信息处理”和“车辆远程信息处理”都用作支持运输系统的一组技术的术语。在这样的运输系统上运行的运输应用覆盖了运输的所有模式，并考虑运输系统的所有元素，即车辆、基础设施和驾驶员或用户，动态地相互作用。交通应用的示例包括车间和车内通信、智能交通控制、智能停车、电子收费系统、物流和车队管理、车辆控制以及安全和路边援助。
As a distributed system, transport applications require an end-to-end management of different types of networks. It is likely that constrained devices in a network (e.g., a moving in-car network) have to be controlled by an application running on an application server in the network of a service provider. Such a highly distributed network including cellular devices on vehicles is assumed to include a wireless access network using diverse long-distance wireless technologies such as WiMAX, 3G/LTE, or satellite communication, e.g.,
作为一个分布式系统，传输应用程序需要对不同类型的网络进行端到端的管理。网络中受约束的设备（例如，车载移动网络）很可能必须由在服务提供商网络中的应用服务器上运行的应用程序控制。假设这种包括车载蜂窝设备的高度分布式网络包括使用各种远程无线技术（例如WiMAX、3G/LTE或卫星通信）的无线接入网络，例如。，
based on an embedded hardware module. As a result, the management of constrained devices in the transport system might be necessary to plan top-down and might need to use data models obliged from and defined on the application layer. The assumed device classes in use are mainly C2 [RFC7228] devices. In cases, where an in-vehicle network is involved, C1 devices [RFC7228] with limited capabilities and a short-distance constrained radio network, e.g., IEEE 802.15.4 might be used additionally.
基于嵌入式硬件模块。因此，运输系统中受约束设备的管理可能是自上而下规划所必需的，并且可能需要使用应用层强制提供并定义的数据模型。假定使用的设备类别主要是C2[RFC7228]设备。在涉及车内网络的情况下，可另外使用具有有限能力的C1设备[RFC7228]和短距离受限无线电网络，例如IEEE 802.15.4。
All Transport Applications will require an IT infrastructure to run on top of, e.g., in public-transport scenarios like trains, buses, or metro networks infrastructure might be provided, maintained, and operated by third parties like mobile-network or satellite-network operators. However, the management responsibility of the transport application typically rests within the organization running the transport application (in the public-transport scenario, this would typically be the public-transport operator). Different aspects of the infrastructure might also be managed by different entities. For example, the in-car devices are likely to be installed and managed by the manufacturer, while the local government or transportation authority might be responsible for the on-road vehicular communication infrastructure used by these devices. The backend infrastructure is also likely to be maintained by third-party operators. As such, the NMS must be able to deal with different network segments (each being operated and controlled by separate entities) and enable appropriate access control and security.
所有交通应用都需要IT基础设施，例如，在火车、公共汽车或地铁网络等公共交通场景中，基础设施可能由第三方（如移动网络或卫星网络运营商）提供、维护和运营。但是，交通应用程序的管理责任通常由运行交通应用程序的组织承担（在公共交通场景中，这通常是公共交通运营商）。基础设施的不同方面也可能由不同的实体管理。例如，车内设备可能由制造商安装和管理，而地方政府或交通部门可能负责这些设备使用的道路车辆通信基础设施。后端基础设施也可能由第三方运营商维护。因此，NMS必须能够处理不同的网段（每个网段由单独的实体操作和控制），并实现适当的访问控制和安全性。
Depending on the type of application domain (vehicular or stationary) and service being provided, it is important for the NMS to be able to function with different architectures, since different manufacturers might have their own proprietary systems relying on a specific management topology option, as described in [RFC7547]. Moreover, constituents of the network can either be private, belong to individuals or private companies, or be owned by public institutions leading to different legal and organization requirements. Across the entire infrastructure, a variety of constrained devices is likely to be used, and they must be individually managed. The NMS must be able to either work directly with different types of devices or have the ability to interoperate with multiple different systems.
根据应用领域的类型（车辆或固定）和所提供的服务，NMS能够在不同的体系结构下运行是很重要的，因为不同的制造商可能有自己的专有系统，依赖于特定的管理拓扑选项，如[RFC7547]所述。此外，网络的组成部分可以是私人的，属于个人或私人公司，也可以由公共机构所有，从而产生不同的法律和组织要求。在整个基础设施中，可能会使用各种受约束的设备，并且必须对它们进行单独管理。NMS必须能够直接与不同类型的设备一起工作，或者能够与多个不同的系统进行互操作。
The challenges in the management of vehicles in a mobile-transport application are manifold. The up-to-date position of each node in the network should be reported to the corresponding management entities, since the nodes could be moving within or roaming between different networks. Secondly, a variety of troubleshooting information, including sensitive location information, needs to be reported to the management system in order to provide accurate service to the customer. Management systems dealing with mobile
移动交通应用中车辆管理的挑战是多方面的。网络中每个节点的最新位置应报告给相应的管理实体，因为节点可能在不同网络内移动或在不同网络之间漫游。其次，需要向管理系统报告各种故障排除信息，包括敏感位置信息，以便为客户提供准确的服务。处理移动通信的管理系统
nodes could possibly exploit specific patterns in the mobility of the nodes. These patterns emerge due to repetitive vehicular usage in scenarios like people commuting to work and supply vehicles transporting shipments between warehouses, etc. The NMS must also be able to handle partitioned networks, which would arise due to the dynamic nature of traffic resulting in large inter-vehicle gaps in sparsely populated scenarios. Since mobile nodes might roam in remote networks, the NMS should be able to provide operating configuration updates regardless of node location.
节点可能利用节点移动性中的特定模式。这些模式是由于人们通勤上班和供应车辆在仓库之间运输货物等场景中重复使用车辆而产生的。NMS还必须能够处理分区网络，这是由于交通的动态特性导致在人口稀少的情况下车辆之间存在较大的间隙。由于移动节点可能在远程网络中漫游，因此无论节点位置如何，NMS都应该能够提供操作配置更新。
The constrained devices in a moving transport network might be initially configured in a factory, and a reconfiguration might be needed only rarely. New devices might be integrated in an ad hoc manner based on self-management and self-configuration capabilities. Monitoring and data exchange might be necessary via a gateway entity connected to the backend transport infrastructure. The devices and entities in the transport infrastructure need to be monitored more frequently and may be able to communicate with a higher data rate. The connectivity of such entities does not necessarily need to be wireless. The time scale for detecting and recording failures in a moving transport network is likely measured in hours, and repairs might easily take days. It is likely that a self-healing feature would be used locally. On the other hand, failures in fixed transport-application infrastructure (e.g., traffic lights, digital-signage displays) are likely to be measured in minutes so as to avoid untoward traffic incidents. As such, the NMS must be able to deal with differing timeliness requirements based on the type of devices.
移动传输网络中受约束的设备可能最初在工厂中配置，很少需要重新配置。新设备可以基于自我管理和自我配置功能以特别方式集成。可能需要通过连接到后端传输基础设施的网关实体进行监视和数据交换。运输基础设施中的设备和实体需要更频繁地进行监控，并且可能能够以更高的数据速率进行通信。这些实体的连接不一定需要是无线的。在移动的运输网络中检测和记录故障的时间尺度可能以小时为单位，维修可能很容易需要几天。很可能会在本地使用自愈功能。另一方面，固定交通应用基础设施（如交通灯、数字标牌显示器）的故障可能以分钟为单位进行测量，以避免意外交通事故。因此，NMS必须能够处理基于设备类型的不同及时性要求。
Since transport applications of the constrained devices and networks deal with automotive vehicles, malfunctions and misuse can potentially lead to safety concerns as well. As such, besides access control, privacy of user data, and timeliness, management systems should also be able to detect situations that are potentially hazardous to safety. Some of these situations could be automatically mitigated, e.g., traffic lights with incorrect timing, but others might require human intervention, e.g., failed traffic lights. The management system should take appropriate actions in these situations. Maintaining data confidentiality and integrity is also an important security aspect of a management system since tampering (or malfunction) can also lead to potentially dangerous situations.
由于受限设备和网络的运输应用涉及汽车，故障和误用也可能导致安全问题。因此，除了访问控制、用户数据隐私和及时性之外，管理系统还应该能够检测到对安全有潜在危险的情况。其中一些情况可以自动缓解，例如，交通灯的计时不正确，但其他情况可能需要人为干预，例如，交通灯故障。管理体系应在这些情况下采取适当的措施。维护数据的机密性和完整性也是管理系统的一个重要安全方面，因为篡改（或故障）也可能导致潜在的危险情况。
Community networks are comprised of constrained routers in a multi-hop mesh topology, communicating over lossy, and often wireless, channels. While the routers are mostly non-mobile, the topology may be very dynamic because of fluctuations in link quality of the (wireless) channel caused by, e.g., obstacles, or other nearby radio
社区网络由多跳网状拓扑中的受约束路由器组成，通过有损（通常是无线）信道进行通信。虽然路由器大多是非移动的，但由于（无线）信道的链路质量的波动（例如障碍物或附近的其他无线电设备引起的），拓扑结构可能是非常动态的
transmissions. Depending on the routers that are used in the community network, the resources of the routers (memory, CPU) may be more or less constrained -- available resources may range from only a few kilobytes of RAM to several megabytes or more, and CPUs may be small and embedded, or more powerful general-purpose processors. Examples of such community networks are the FunkFeuer network (Vienna, Austria), FreiFunk (Berlin, Germany), Seattle Wireless (Seattle, USA), and AWMN (Athens, Greece). These community networks are public and non-regulated, allowing their users to connect to each other and -- through an uplink to an ISP -- to the Internet. No fee, other than the initial purchase of a wireless router, is charged for these services. Applications of these community networks can be diverse, e.g., location-based services, free Internet access, file sharing between users, distributed chat services, social networking, video sharing, etc.
传输。根据社区网络中使用的路由器，路由器的资源（内存、CPU）可能或多或少受到限制——可用资源的范围可能从几千字节的RAM到几兆字节或更多，CPU可能是小型嵌入式处理器，或更强大的通用处理器。此类社区网络的示例包括FunkFeuer网络（奥地利维也纳）、FreiFunk网络（德国柏林）、西雅图无线网络（美国西雅图）和AWMN网络（希腊雅典）。这些社区网络是公共的、不受监管的，允许他们的用户相互连接，并通过与ISP的上行链路连接到互联网。除了最初购买无线路由器外，这些服务不收取任何费用。这些社区网络的应用可以是多种多样的，例如，基于位置的服务、免费互联网访问、用户之间的文件共享、分布式聊天服务、社交网络、视频共享等。
As an example of a community network, the FunkFeuer network comprises several hundred routers, many of which have several radio interfaces (with omnidirectional and some directed antennas). The routers of the network are small-sized wireless routers, such as the Linksys WRT54GL, available in 2011 for less than 50 euros. Each router, with 16 MB of RAM and 264 MHz of CPU power, is mounted on the rooftop of a user. When a new user wants to connect to the network, they acquire a wireless router, install the appropriate firmware and routing protocol, and mount the router on the rooftop. IP addresses for the router are assigned manually from a list of addresses (because of the lack of autoconfiguration standards for mesh networks in the IETF).
作为社区网络的一个示例，FunkFeuer网络包括数百个路由器，其中许多路由器具有多个无线电接口（具有全向天线和一些定向天线）。该网络的路由器是小型无线路由器，如Linksys WRT54GL，2011年售价不到50欧元。每个路由器都有16MB的RAM和264MHz的CPU电源，安装在用户的屋顶上。当新用户想要连接到网络时，他们会获得一个无线路由器，安装适当的固件和路由协议，并将路由器安装在屋顶上。路由器的IP地址是从地址列表中手动分配的（因为IETF中缺少网状网络的自动配置标准）。
While the routers are non-mobile, fluctuations in link quality require an ad hoc routing protocol that allows for quick convergence to reflect the effective topology of the network (such as Neighborhood Discovery Protocol (NHDP) [RFC6130] and Optimized Link State Routing version 2 (OLSRv2) [RFC7181] developed in the MANET WG). Usually, no human interaction is required for these protocols, as all variable parameters required by the routing protocol are either negotiated in the control traffic exchange or are only of local importance to each router (i.e. do not influence interoperability). However, external management and monitoring of an ad hoc routing protocol may be desirable to optimize parameters of the routing protocol. Such an optimization may lead to a topology that is perceived to be more stable and to a lower control traffic overhead (and therefore to a higher delivery success ratio of data packets, a lower end-to-end delay, and less unnecessary bandwidth and energy use).
虽然路由器是非移动的，但链路质量的波动需要一种允许快速收敛以反映网络有效拓扑的自组织路由协议（如MANET WG中开发的邻域发现协议（NHDP）[RFC6130]和优化链路状态路由版本2（OLSRv2）[RFC7181]）。通常，这些协议不需要人工交互，因为路由协议所需的所有可变参数要么在控制流量交换中协商，要么仅对每个路由器具有局部重要性（即，不影响互操作性）。然而，为了优化路由协议的参数，可能需要对自组织路由协议进行外部管理和监视。这样的优化可导致被认为更稳定的拓扑和更低的控制业务开销（并因此导致更高的数据分组传递成功率、更低的端到端延迟以及更少的不必要带宽和能量使用）。
Different use cases for the management of community networks are possible:
社区网络管理的不同用例是可能的：
o A single NMS, e.g., a border gateway providing connectivity to the Internet, requires managing or monitoring routers in the community network, in order to investigate problems (monitoring) or to improve performance by changing parameters (managing). As the topology of the network is dynamic, constant connectivity of each router towards the management station cannot be guaranteed. Current network management protocols, such as SNMP and Network Configuration Protocol (NETCONF), may be used (e.g., use of interfaces such as the NHDP-MIB [RFC6779]). However, when routers in the community network are constrained, existing protocols may require too many resources in terms of memory and CPU; and more importantly, the bandwidth requirements may exceed the available channel capacity in wireless mesh networks. Moreover, management and monitoring may be unfeasible if the connection between the NMS and the routers is frequently interrupted.
o 单个NMS（例如，提供互联网连接的边界网关）需要管理或监控社区网络中的路由器，以便调查问题（监控）或通过更改参数（管理）提高性能。由于网络的拓扑结构是动态的，因此无法保证每个路由器与管理站的持续连接。可以使用当前的网络管理协议，例如SNMP和网络配置协议（NETCONF）（例如，使用NHDP-MIB[RFC6779]等接口）。然而，当社区网络中的路由器受到限制时，现有协议可能需要太多的内存和CPU资源；更重要的是，带宽需求可能超过无线mesh网络中的可用信道容量。此外，如果NMS和路由器之间的连接经常中断，则管理和监视可能不可行。
o Distributed network monitoring, in which more than one management station monitors or manages other routers. Because connectivity to a server cannot be guaranteed at all times, a distributed approach may provide a higher reliability, at the cost of increased complexity. Currently, no IETF standard exists for distributed monitoring and management.
o 分布式网络监视，其中多个管理站监视或管理其他路由器。由于无法始终保证与服务器的连接，分布式方法可能会以增加复杂性为代价提供更高的可靠性。目前，没有针对分布式监视和管理的IETF标准。
o Monitoring and management of a whole network or a group of routers. Monitoring the performance of a community network may require more information than what can be acquired from a single router using a network management protocol. Statistics, such as topology changes over time, data throughput along certain routing paths, congestion, etc., are of interest for a group of routers (or the routing domain) as a whole. As of 2014, no IETF standard allows for monitoring or managing whole networks instead of single routers.
o 监控和管理整个网络或一组路由器。监视社区网络的性能可能需要比使用网络管理协议从单个路由器获取的信息更多的信息。对于一组路由器（或路由域）作为一个整体来说，诸如拓扑随时间的变化、沿某些路由路径的数据吞吐量、拥塞等统计信息都很重要。截至2014年，没有IETF标准允许监控或管理整个网络，而不是单个路由器。
The challenges of configuring and monitoring networks operated in the field by rescue and security agencies can be different from the other use cases since the requirements and operating conditions of such networks are quite different.
由于救援和安全机构在现场运行的网络的要求和运行条件大不相同，因此配置和监控网络的挑战可能不同于其他用例。
With technology advancements, field networks operated nowadays are becoming large and can consist of a variety of different types of equipment that run different protocols and tools that obviously increase complexity of these mission-critical networks. In many scenarios, configurations are, most likely, manually performed.
随着技术的进步，如今运行的现场网络变得越来越大，可以由运行不同协议和工具的各种不同类型的设备组成，这明显增加了这些关键任务网络的复杂性。在许多情况下，配置很可能是手动执行的。
Furthermore, some legacy and even modern devices do not even support IP networking. A majority of protocols and tools developed by vendors that are being used are proprietary, which makes integration more difficult.
此外，一些传统甚至现代设备甚至不支持IP网络。正在使用的供应商开发的大多数协议和工具都是专有的，这使得集成更加困难。
The main reason for this disjoint operation scenario is that most equipment is developed with specific task requirements in mind, rather than interoperability of the varied equipment types. For example, the operating conditions experienced by high altitude security equipment is significantly different from that used in desert conditions. Similarly, equipment used in fire rescue has different requirements than flood-relief equipment. Furthermore, interoperation of equipment with telecommunication equipment was not an expected outcome or (in some scenarios) may not even be desirable.
这种不相交操作场景的主要原因是，大多数设备的开发都考虑了特定的任务需求，而不是各种设备类型的互操作性。例如，高空安全设备所经历的操作条件与沙漠条件下所使用的操作条件有很大不同。同样，用于火灾救援的设备与洪水救援设备有不同的要求。此外，设备与电信设备的互操作不是预期的结果，或者（在某些情况下）甚至可能不可取。
Currently, field networks operate with a fixed Network Operations Center (NOC) that physically manages the configuration and evaluation of all field devices. Once configured, the devices might be deployed in fixed or mobile scenarios. Any configuration changes required would need to be appropriately encrypted and authenticated to prevent unauthorized access.
目前，现场网络通过固定网络运营中心（NOC）运行，该中心对所有现场设备的配置和评估进行物理管理。一旦配置完毕，这些设备可能会部署在固定或移动场景中。所需的任何配置更改都需要进行适当的加密和身份验证，以防止未经授权的访问。
Hierarchical management of devices is a common requirement in such scenarios since local managers or operators may need to respond to changing conditions within their purview. The level of configuration management available at each hierarchy must also be closely governed.
设备的分层管理是此类场景中的常见要求，因为本地经理或操作员可能需要对其权限范围内不断变化的条件作出响应。每个层次结构中可用的配置管理级别也必须严格管理。
Since many field operation devices are used in hostile environments, a high failure and disconnection rate should be tolerated by the NMS, which must also be able to deal with multiple gateways and disjoint management protocols.
由于许多现场操作设备在恶劣环境中使用，NMS应能容忍高故障率和断开率，还必须能够处理多个网关和不相交的管理协议。
Multi-national field operations involving search, rescue, and security are becoming increasingly common, requiring interoperation of a diverse set of equipment designed with different operating conditions in mind. Furthermore, different intra- and inter-governmental agencies are likely to have a different set of standards, best practices, rules and regulations, and implementation approaches that may contradict or conflict with each other. The NMS should be able to detect these and handle them in an acceptable manner, which may require human intervention.
涉及搜索、救援和安全的多国野战行动正变得越来越普遍，需要根据不同的作战条件设计一套不同的设备进行互操作。此外，不同的政府内部和政府间机构可能有一套不同的标准、最佳做法、规则和条例，以及可能相互矛盾或冲突的实施方法。NMS应该能够检测到并以可接受的方式处理这些问题，这可能需要人工干预。
This document discusses use cases for management of networks with constrained devices. The security considerations described throughout the companion document [RFC7547] apply here as well.
本文档讨论使用受限设备管理网络的用例。随附文档[RFC7547]中描述的安全注意事项也适用于此处。
[RFC6130] Clausen, T., Dearlove, C., and J. Dean, "Mobile Ad Hoc Network (MANET) Neighborhood Discovery Protocol (NHDP)", RFC 6130, DOI 10.17487/RFC6130, April 2011, <http://www.rfc-editor.org/info/rfc6130>.
[RFC6130]Clausen，T.，Dearlove，C.，和J.Dean，“移动自组织网络（MANET）邻域发现协议（NHDP）”，RFC 6130，DOI 10.17487/RFC6130，2011年4月<http://www.rfc-editor.org/info/rfc6130>.
[RFC6568] Kim, E., Kaspar, D., and JP. Vasseur, "Design and Application Spaces for IPv6 over Low-Power Wireless Personal Area Networks (6LoWPANs)", RFC 6568, DOI 10.17487/RFC6568, April 2012, <http://www.rfc-editor.org/info/rfc6568>.
[RFC6568]Kim，E.，Kaspar，D.，和JP。Vasseur，“低功率无线个人区域网络（6LoWPANs）上IPv6的设计和应用空间”，RFC 6568，DOI 10.17487/RFC6568，2012年4月<http://www.rfc-editor.org/info/rfc6568>.
[RFC6779] Herberg, U., Cole, R., and I. Chakeres, "Definition of Managed Objects for the Neighborhood Discovery Protocol", RFC 6779, DOI 10.17487/RFC6779, October 2012, <http://www.rfc-editor.org/info/rfc6779>.
[RFC6779]Herberg，U.，Cole，R.，和I.Chakeres，“邻域发现协议的托管对象定义”，RFC 6779，DOI 10.17487/RFC6779，2012年10月<http://www.rfc-editor.org/info/rfc6779>.
[RFC6988] Quittek, J., Ed., Chandramouli, M., Winter, R., Dietz, T., and B. Claise, "Requirements for Energy Management", RFC 6988, DOI 10.17487/RFC6988, September 2013, <http://www.rfc-editor.org/info/rfc6988>.
[RFC6988]Quitek，J.，Ed.，Chandramouli，M.，Winter，R.，Dietz，T.，和B.Claise，“能源管理要求”，RFC 6988，DOI 10.17487/RFC6988，2013年9月<http://www.rfc-editor.org/info/rfc6988>.
[RFC7181] Clausen, T., Dearlove, C., Jacquet, P., and U. Herberg, "The Optimized Link State Routing Protocol Version 2", RFC 7181, DOI 10.17487/RFC7181, April 2014, <http://www.rfc-editor.org/info/rfc7181>.
[RFC7181]Clausen，T.，Dearlove，C.，Jacquet，P.，和U.Herberg，“优化链路状态路由协议版本2”，RFC 7181，DOI 10.17487/RFC7181，2014年4月<http://www.rfc-editor.org/info/rfc7181>.
[RFC7228] Bormann, C., Ersue, M., and A. Keranen, "Terminology for Constrained-Node Networks", RFC 7228, DOI 10.17487/RFC7228, May 2014, <http://www.rfc-editor.org/info/rfc7228>.
[RFC7228]Bormann，C.，Ersue，M.和A.Keranen，“受限节点网络的术语”，RFC 7228，DOI 10.17487/RFC7228，2014年5月<http://www.rfc-editor.org/info/rfc7228>.
[RFC7326] Parello, J., Claise, B., Schoening, B., and J. Quittek, "Energy Management Framework", RFC 7326, DOI 10.17487/RFC7326, September 2014, <http://www.rfc-editor.org/info/rfc7326>.
[RFC7326]Parello，J.，Claise，B.，Schoining，B.，和J.Quitek，“能源管理框架”，RFC 7326，DOI 10.17487/RFC7326，2014年9月<http://www.rfc-editor.org/info/rfc7326>.
[RFC7547] Ersue, M., Ed., Romascanu, D., Schoenwaelder, J., and U. Herberg, "Management of Networks with Constrained Devices: Problem Statement and Requirements", RFC 7547, DOI 10.17487/RFC7547, May 2015, <http://www.rfc-editor.org/info/rfc7547>.
[RFC7547]Ersue，M.，Ed.，Romascanu，D.，Schoenwaeld，J.，和U.Herberg，“受约束设备的网络管理：问题陈述和要求”，RFC 7547，DOI 10.17487/RFC7547，2015年5月<http://www.rfc-editor.org/info/rfc7547>.
[IOT-SEC] Garcia-Morchon, O., Kumar, S., Keoh, S., Hummen, R., and R. Struik, "Security Considerations in the IP-based Internet of Things", Work in Progress, draft-garcia-core-security-06, September 2013.
[IOT-SEC]加西亚·莫尔肯，O.，库马尔，S.，基奥，S.，胡曼，R.，和R.斯特鲁克，“基于IP的物联网中的安全考虑”，正在进行的工作，草稿-Garcia-core-Security-062013年9月。
[IEEE802.11] IEEE, "Part 11: Wireless LAN Medium Access Control (MAC) and Physical Layer (PHY) Specifications", IEEE Standard 802.11, March 2012, <http://standards.ieee.org/about/get/802/802.11.html>.
[IEEE802.11]IEEE，“第11部分：无线局域网介质访问控制（MAC）和物理层（PHY）规范”，IEEE标准802.11，2012年3月<http://standards.ieee.org/about/get/802/802.11.html>.
[IEEE802.15] IEEE, "WIRELESS PERSONAL AREA NETWORKS (PANs)", IEEE Standard 802.15, 2003-2014, <https://standards.ieee.org/about/get/802/802.15.html>.
[IEEE802.15]IEEE，“无线个人区域网络（PANs）”，IEEE标准802.15，2003-2014<https://standards.ieee.org/about/get/802/802.15.html>.
[IEEE802.15.4] IEEE, "Part 15.4: Low-Rate Wireless Personal Area Networks (LR-WPANs)", IEEE Standard 802.15.4, September 2011, <https://standards.ieee.org/about/get/802/802.15.html>.
[IEEE802.15.4]IEEE，“第15.4部分：低速无线个人区域网络（LR WPAN）”，IEEE标准802.15.4，2011年9月<https://standards.ieee.org/about/get/802/802.15.html>.
Acknowledgments
致谢
The following persons reviewed and provided valuable comments during the creation of this document:
以下人员在本文件编制过程中进行了审查并提出了宝贵意见：
Dominique Barthel, Carsten Bormann, Zhen Cao, Benoit Claise, Bert Greevenbosch, Ulrich Herberg, Ted Lemon, Kathleen Moriarty, James Nguyen, Zach Shelby, Peter van der Stok, and Martin Thomson.
多米尼克·巴特尔、卡斯滕·鲍曼、曹震、贝诺特·克莱斯、伯特·格里文博什、乌尔里希·赫伯格、特德·莱蒙、凯瑟琳·莫里亚蒂、詹姆斯·阮、扎克·谢尔比、彼得·范德斯托克和马丁·汤姆森。
The authors would like to thank the reviewers and the participants on the Coman mailing list for their valuable contributions and comments.
作者要感谢评论员和Coman邮件列表上的参与者，感谢他们的宝贵贡献和评论。
Juergen Schoenwaelder and Anuj Sehgal were partly funded by Flamingo, a Network of Excellence project (ICT-318488) supported by the European Commission under its Seventh Framework Programme.
Juergen Schoenwaeld和Anuj Sehgal的部分资金来自Flamingo，这是一个卓越网络项目（ICT-318488），由欧盟委员会在其第七个框架计划下支持。
Contributors
贡献者
The following persons made significant contributions to and reviewed this document:
以下人员对本文件做出了重大贡献并进行了审查：
o Ulrich Herberg contributed Section 4.9, "Community Network Applications".
o Ulrich Herberg贡献了第4.9节“社区网络应用”。
o Peter van der Stok contributed to Section 4.6, "Building Automation".
o 彼得·范德斯托克对第4.6节“楼宇自动化”做出了贡献。
o Zhen Cao contributed to Section 2.2, "Cellular Access Technologies".
o 曹震对第2.2节“蜂窝接入技术”做出了贡献。
o Gilman Tolle contributed Section 4.4 "Energy Management".
o 吉尔曼·托尔贡献了第4.4节“能源管理”。
o James Nguyen and Ulrich Herberg contributed to Section 4.10 "Field Operations".
o James Nguyen和Ulrich Herberg对第4.10节“现场作业”做出了贡献。
Authors' Addresses
作者地址
Mehmet Ersue (editor) Nokia Networks
Mehmet Ersue（编辑）诺基亚网络
EMail: mehmet.ersue@nokia.com
EMail: mehmet.ersue@nokia.com
Dan Romascanu Avaya
丹·罗马斯卡努·阿瓦亚
EMail: dromasca@avaya.com
EMail: dromasca@avaya.com
Juergen Schoenwaelder Jacobs University Bremen
不莱梅大学
EMail: j.schoenwaelder@jacobs-university.de
EMail: j.schoenwaelder@jacobs-university.de
Anuj Sehgal Jacobs University Bremen
不来梅阿努杰·塞加尔·雅各布斯大学
EMail: s.anuj@jacobs-university.de
EMail: s.anuj@jacobs-university.de