Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Control Plane architecture abstracts the cloud interfaces for internal CCSP architecture. It makes internal common components like TR-069 PA to be agnostic to those cloud interfaces by using a set of normalized actions.
This component is intended to be responsible for all normalized actions listed below. This component does not provide interface for servicing normalized actions, rather it depends on functional components to expose APIs on CCSP message bus.

...

You may refer to Component Registrar SFS, SDS, and CCSP High Level Architecture Specification for function prototypes related to Message Bus APIs.

TR-069 PA must follow follows transaction control mechanism defined by CCSP Architecture specification based on session ID. For details please refer section 7 Session Integrity in

In case normalized action call on external namespaces that do not have counterpart internal namespaces or say PA cannot get such mapping information from CR, TR-069 PA must be able to route calls to default namespace handler which could be Application Environment Manager through private interface per CCSP Component Registrar specification.

...

As you can see from figure 1, when TR-069 PA receives a request from ACS, it resolves namespace with CR, and makes a normalized action invocation over message bus into target functional component. Once TR-069 PA receives response or error from functional component, it construct CWMP SOAP message back to ACS.

Figure 2 demonstrates the data flow. It shows how TR-069 PA receives a RPC request from TR-069 ACS and converts it to one or more normalized action calls into functional component(s).

 

Image Removed


Image Added

Figure 2 TR-069 PA SetParameterValues data flow


Image RemovedImage Added

Figure 3 TR-069 PA GetParameterNames data flow

...

data flow

...

GetParameterNames(“Device.”). PA needs to find out all owning FCs on local and remote sub-systems, and make GetParameterNames normalized action calls. Once it gets results, PA needs to filter out un-supported and invisible namespaces (no matter partial or full names) and send back to ACS.