...

PandM Overview

P&M PandM is a CCSP component that implements core provisioning and management functionality of the device.  Its primary role is to respond to commands from other CCSP components that need to set or query variables pertaining to core CCSP functionality. Its interface to other components uses the CCSP Message Bus interface and is based around a data model derived from  TR-181 (TR-157, TR-143) along with CCSP specific extensions.

Figure 1 P&M PandM Overview

P&M PandM module tracks any changes in the system for the attributes configured by service provider and sends notifications to CCSP components that have requested these specific notifications. Any changes to these attributes will be reported to service provider using the appropriate Protocol Agent (PA).

...

PandM Component Definitions

...

PandM Architecture

This is the architecture of P&M PandM component:

Figure 2 P&M PandM Architecture Overview

P&M PandM consist three layers:

1) Access Layer

...

• Goal is to support a large number of data model objects for good scalability
• Data Model Management Layer loads all data model access APIs through a pre-defined XML file which contains description of data model objects and parameters.
• The data model implementation in shared library interfaces HAL Integration (backend) Layer by calling backend integration APIs.

3) P&M PandM HAL Integration (backend) Layer, a.k.a, component specific HAL

...

Functional Structure

CCSP Message Bus APIs

P&M PandM DBUS object path is “/com/cisco/spvtg/ccsp/pam”.

P&M PandM supports following CCSP Message Bus APIs:

...

CCSP Message Bus APIs required from other components

P&M PandM requires following CCSP Message Bus APIs.

...

9) setParameterValues

10) getParameterNames

...

PandM System Flow

Parameter set/get flow in

...

PandM

Figure 3 Parameter Get Flow

...

Figure 4 Parameter Set Flow

...

PandM boot-up flow

Figure 5 P&M PandM boot-up flow

Instance Number Operation Flow

Object instance number is used to uniquely identify the object, even across reboots. It is a special value P&M PandM has to maintain, though it is not shown as a parameter. Instance number is generated when a new object is added, or during initialization, if no existing instance number is found. Generated instance number is saved in persistent configuration. Once the object is removed, the instance number is usually not reused.

...

• CCSP: Common Component Software Platform
• P&MPandM: Provisioning and Management
• PA: Protocol Agent
• CR: Component Registrar
• PSM: Persistent Storage Manager
• TDM: Test and Diagnostics Manager