@@ -825,7 +825,7 @@ An NMS is a product controlling at least partially connected devices with networ
NMS can be composed of several components or can implement additional functions that are outside the scope of the present standards.
One example of this type of aggregate product design would be an implementation where the operating system acts as an abstraction layer for the system(s) that host the NMS, or the networking interfaces.
### 4.6.1 Home network deployment
### 4.6.1 (UC-1-HOME) Home network deployment
@@ -850,7 +850,7 @@ Metrics from the managed elements within the home network can be forwarded to th
In many deployments, the NMS provides actual configuration control and visualization of the collected metric data with an additional service or alternate piece of software.
That is mostly a browser, but sometimes also other possibilities are deployed, such as a command-line interface.
@@ -881,7 +881,7 @@ While many small businesses can perform the credential cleanup on former employe
Additionally, entities within this context may store and work with extremely personal and sensitive data, such as a medical facility's patient records or a bank that needs to secure financial data.
The type of deployment and actions of the service requesting users are not important to the NMS, except to the degree that the NMS must ensure that the system has the features, hardware, and security to match operational needs.
@@ -904,7 +904,7 @@ Alternatively, even at telecommunications scale, NMS can even provide its own ce
The following two use cases in sub-chapters consider such deployment and other complex deployments primarily by focusing two approaches.
#### 4.6.4.1 Logical network deployment without physical hardware
#### 4.6.4.1 (UC-4-SDN) Logical network deployment without physical hardware
A traditional simple network design has a single device listening on incoming connections from public network facing port and allows selected traffic to pass through to subnets behind the device.
A mesh network can be a set of these devices, physical or virtual, where multiple subnetworks are interconnected together, and the routing design is many-to-many instead of point-to-point.
@@ -918,7 +918,7 @@ Mesh network routing can be made more accurate, if the services are listed as ro
Combining the known locations of services and subjects connectivity grants, a custom routing table can be calculated for each subject.
This custom routing table can be enforced on network side by added layer of control, that either provisions configuration changes to connected nodes firewalls, or provides other mechanisms to assert the authority of the connection.
#### 4.6.4.2 Physical network deployment with RDPS
#### 4.6.4.2 (UC-5-HYBRID) Physical network deployment with RDPS
When almost everything can be software, the minimum still remains: the user needs to have some form of User Equipment to be able to connect.
This Network Interface can be a radio in the cellphone, a WiFi Access Point in the living room, or a router with SFP+ ports serving the local datacenter.
@@ -958,7 +958,7 @@ Some links can be through dedicated IP/MPLS tunnels, while some could be impleme
While system updates are critical for the product, the installation is fully independent and no functionality is relying on the RDPS connectivity. The system updates can be delivered with a removable medium, if no connectivity to software repositories is available.
### 4.6.5 IoT network with monitoring data collection
### 4.6.5 (UC-6-IOT) IoT network with monitoring data collection
@@ -982,7 +982,7 @@ Beyond collecting data from connected devices and preparing data metrics, the NM
1. Establishes trust between the system and the devices.
2. Maintain an inventory of devices that are part of the managed network.
### 4.6.6 ICT Network Elements
### 4.6.6 (UC-7-ICT) ICT Network Elements
The ICT Element management is an enterprise-focused system to control and manage the configuration of the connected enterprise application on the ICT Elements.
An ICT Element can encompass anything from routers, modems, switches up to mobile devices, tablets, smart phones, laptops, desktop PCs to servers.
@@ -1044,7 +1044,7 @@ ICT Elements can have four managing entities at the same time as illustrated in
In all cases user respectively application rights are managed and controlled, as the device management remains subject of the enterprise NMS, as the ICT elements are and remain in ownership of the enterprise.
### 4.6.7 Server and host fleet lifecycle management
### 4.6.7 (UC-8-FLEET) Server and host fleet lifecycle management
<mark>Editor's Note: A figure illustrating a management hub controlling a fleet of hosts, with optional proxies and an upstream content source, should be added.</mark>
@@ -1089,11 +1089,14 @@ When requirements are divided into low-medium-high categories, the categories ar
Medium requirement level shall implement also requirments listed in low level.
High requirement level shall implement all requirements in the defined set of requirements.
Use-cases **UC-4-SDN**, **UC-5-HYBRID** and **UC-7-FLEET** are not listed in the table below.
These use-case categories shall be evaluated based on the target audience if it is one of **UC-1-HOME**, **UC-2-ENTER** or **UC-3-TELCO**.
