Network Functions

Network Functions (NF) are self-contained entities that facilitate the end user need to understand the underlying device structure when managing or provisioning. For example, a NF could be composed of a standalone SBC, or could be composed as an active-standby HA pair. To the end user their only concern is to target the NF identifier, and SDM will manage and ensure commands are delivered to the appropriate device.

Managing NFs

Users interact with NFs via REST.

• The NF Identifier (NF-ID) can be used in REST requests to target the required NF. There is no need to specify the active-standby naming convention previously used in the SOAP API.
• When adding a standalone SBC or an HA SBC NF, the response returns an NF identifier that can be used in subsequent REST API requests that target that specific NF.
• When adding an NF, the end user specifies the NF name. For convenience, NF names should describe what the NF represents.
• End users can also use the getInventory/deviceMgmt/devices to map NF names to their IDs.
• Configuration provisioning for a specific device is made possible by targeting the NF-ID that the devices belong too. SDM will manage communications to the active or standby behind the scenes. The end user does not need to understand which device is active or standby or if a switch over took place; SDM handles this.