@@ -84,7 +84,7 @@ The implementing regulation [\[i.11\]](#_ref_i.11) (ANNEX I, Class I, 6.) define
This quotation is not to be used as a source of the truth, as the definition might change. Refer to the source for the latest description.
This quotation is not to be used as a source of the truth, as the definition might change. Refer to the source for the latest description.
The NMS is defined in the implmeneting regulation [\[i.11\]](#_ref_i.11) in Annex I, Class I (6) and is not restricted to only systems that are IP connected. The scope covers all connected elements in the network, that are somehow managed. This includes, but is not limited to, Mobile Device Management systems and Software Defined Networking.
The NMS is defined in the implmeneting regulation [\[i.11\]](#_ref_i.11) in Annex I, Class I (6) and is not restricted to only systems that are IP connected. The scope covers all connected elements in the network, that are managed. This includes, but is not limited to, Mobile Device Management systems and Software Defined Networking.
Bluetooth consumer devices are usually not managed by an NMS, however, if they are capable, a NMS management could control them too, as Bluetooth is just a communication media and can be used also for management traffic. Such, NMS’s often control more than just network configuration - e.g., MDM systems.
Bluetooth consumer devices are usually not managed by an NMS, however, if they are capable, a NMS management could control them too, as Bluetooth is just a communication media and can be used also for management traffic. Such, NMS’s often control more than just network configuration - e.g., MDM systems.
@@ -184,9 +184,10 @@ For the purposes of the present document, the following abbreviations apply:
## 4.3 Product overview and architecture
## 4.3 Product overview and architecture
Network management systems are often deployed <mark>in a star pattern, where all command and control functionality is focused on a centralised set of services, that are providing all required functionality</mark>.
Network management systems are commonly deployed using centralized management services that provide command, control, monitoring, and administration functions.
Depending on the connected element design and degree of autonomy, the element can often operate fully without constant connectivity to an NMS. In larger network deployments and without adjustments in routing or other operation parameters, the connectivity to the NMS can erode over time.
Depending on the design and autonomy of the managed elements, some elements may continue limited operation when connectivity to the network management system is unavailable.
In larger deployments, network design and operational parameters can affect the reliability and scalability of connectivity between managed elements and the network management system.
