Page Comparison

Use
• PoC  "showcase" use cases:
  
  • Wireless PNF Plug'n'
play
• • Play (device discovery - with simplifications)
Basics for FCAPS
• • Basic FCAPS - eNB and DAS
• Week of June 25th - proposed
ONAP community lab at WINLAB "OWL" with remote access & inter-work with operators' and equipment vendors' labs
Decisions wrt resources, participation, and so on, approx. March 15
Joint with ONAP + ONF (some sort of "officialized" collaboration between ONAP & ONF
and ONAP
is being discussed)

The Broadband forum data model has defined objects and hierarchy using a generic device management principle. The objects could be stacked up as necessary to manage any HeNB/FAP device that provides service - CDMA2k, LTE, UMTS etc. It supports device discovery and management.

Reference:

• https://www.broadband-forum.org/standards-and-software/technical-specifications/technical-reports
• https://www.broadband-forum.org/standards-and-software/technical-specifications/tr-069-files-tools

Adapting the broadband forum defined data model would help shorten the time taken to define a similar generic model in YANG to manage HeNB/FAP type devices. The intent in ONAP is to define a generic data model structure for device management and broadband form has done that work. Defining the BB forum data model in YANG format and writing a translation layer in Netconf for TR069 could accelerate a PoC for HeNB management.

TR181 data model:

The data model definition in this TR contains data model objects for basic device information, protocol stack configuration, network interface, routing, bridging etc. It also defines a baseline profile that specifies a minimum level of data model support. This data model represents Network interfaces and protocol layers modeled as independent data objects that can be stacked into whatever configuration a device might support.

• https://www.broadband-forum.org/technical/download/TR-181_Issue-2_Amendment-5.pdf
  • Page 12: Figure 1 – Device:2 Data Model Structure – Overview
  • Page 13: Figure 2 – Device:2 Data Model Structure – Device Level
  • Page 14: Figure 3 – Device:2 Data Model Structure – Interface Stack and Networking Technologies
  • Page 15: Figure 4 – Device:2 Data Model Structure – Applications and Protocols
  • Page 23: Figure 5 – OSI Layers and Interface Objects
• https://www.broadband-forum.org/cwmp/tr-181-2-5-0.html
  • FaultManagement: https://www.broadband-forum.org/cwmp/tr-181-2-5-0.html#D.Device:2.Device.FaultMgmt.CurrentAlarm.{i}.
  • PerformanceManagement: https://www.broadband-forum.org/cwmp/tr-181-2-5-0.html#D.Device:2.Device.PeriodicStatistics.

TR196 data model:

This TR specifies the Data Model for Femto Access Point (FAP) and management of its various services (CDMA2k, LTE, UMTS, VoIP etc).

• https://www.broadband-forum.org/technical/download/TR-196_Issue-2.pdf
  • Page 14: Figure 1 – General Overall View of the Femtocell System
  • Page 15: Figure 2 – Services.FAPService.{i}.Structure
    
    • Question: How to add 5G?
• https://www.broadband-forum.org/cwmp/tr-196-2-1-0.html
  • See example for RF parameters: https://www.broadband-forum.org/cwmp/tr-196-2-1-0.html#D.FAPService:2.FAPService.{i}.CellConfig.LTE.RAN.RF.

• Architecture
  • Existing implementations vs. future implementation
    https://wiki.onap.org/download/attachments/23265852/ONAP-SDN-R-flows.pptx?api=v2