...
Technical Report 317 (TR-317) from the Broadband Forum specifies a "Network Enhanced Residential Gateway" (NERG) that can be used by service providers (SP) to deploy residential broadband services including High Speed Internet access, IPTV and VoIP services. A new device type named BRG (Bridged Residential Gateway) is defined, as well as a functionality split between what it would run and what a virtual function instantiated in the SP's cloud, called vG, will run. This functionality split allows for the introduction of new services not possible with the existing whole-physical residential gateway. It also saves operational cost in that with less changes / truck roll in and to the customer residence would be needed.
...
- ONAP will be used to instantiate, configure and manage the required vCPE service as a cloud service that may be collocated with other subscriber services such as vSTB, cloud DVR and VoD-streaming vCDN.
- SDN is used to configure the connectivity with the first mile network, the IP subscriber management and service edge networking. Potentially in the future, dynamic service chaining to value-add services (e.g. security, parental control, home automation IoT).
...
Once BRG Emulator gets the ACK it is ready to start serving the home network.
Network Function:
...
- Infrastructure instantiation
- General infrastructure instantiation (vDHCP, vDNS, vAAA)
- Specific infrastructure instantiation 1 (vBNG)
- Specific infrastructure instantiation 2 (vG_MUX)
- General infrastructure instantiation (vDHCP, vDNS, vAAA)
- Customer ordering
- New vG ordering, instantiation and activation
- Aspiration goal: Cut service
- Aspiration goal: Per service activation ( connectivity to Internet, IMS VoIP, IPTV)
- Aspiration goal: Wholesale access (future)
- Self-service
- Aspiration goal: Tiered bandwidth
- Aspiration goal: Bandwidth on Demand
- Aspiration goal: Change internet access bandwidth
- Software management
- Aspiration goal: Upgrade service
- Aspiration goal: Upgrade a specific element (VNF) of the service
- Aspiration goal: Delete service
- Scaling
- Aspiration goal: Storage (future)
- New vG ordering, instantiation and activation
- Auto-healing
- Automatic reboot/restart
- Aspiration goal: Rebuild
- Aspiration goal: Migrate/evacuate to different CO Re-architected as DC (future)
- Aspiration goal: Reconnect over an alternative path?
- Infrastructure instantiation
Project Impact:
- Modeling
To be discussed - SDC
Add logic to use the new modeling when designing the service, and then distribute the resulting artifacts. - CLAMP
Framework for policy design and distribution - SO
Add logic to understand the new artifacts; orchestrate/manage changes according to it. - SDNC
Add logic to create the chaining, configuration, healing, etc. - DCAE
Support statistics collection and receipt of events as per the new model; monitor connectivity and livelihood of the BRG_Emulator. - APPC, VF-C, and DCAE
Support more complex control loops. - A&AI
Support the new data model. - Policy
Support new policy related to the service + the connectivity to the BRG_Emulator. - VNF SDK
Support the ONAP VNF guidelines (blend from ECOMP and OPEN-O) - Integration
Integrate, produce test cases, run the tests, verify the use case with the selected VNFs
- Modeling
Work Commitment:
Work Item | ONAP Member |
Modeling | Amdocs, AT&T |
SDC | Amdocs, AT&T |
SO | AT&T |
SDNC | Amdocs, AT&T |
DCAE | AT&T |
APPC | Amdocs, AT&T |
A&AI | Amdocs |
Policy | AT&T |
Multi-VIM | Wind River |
VPP Based VNFs BRG_Emulator, |
VBNG, |
vG_MUX, vG | Intel |
Integration | Amdocs, Integration Team |
Use Case |
Subcommittee | Amdocs, AT&T, Intel, Orange, |
Wind River, more ? Deliverables: Service definition, service detailed requirements, ONAP flow diagrams, service(s) model(s) |
Note: Work commitment items indicate which ONAP Members have expressed interest and commitment to working on individual items. More than one ONAP Member is welcomed to provide support and work on each of the items.
...
- Jun 28, 2017 Meeting: Use Case Walk Through
- Recorded meeting: https://zoom.us/recording/play/DgJBQbqOZaSKHxmOmlDXcU9_zTKNrRAa9Y3TTkCw3T9Hi-ekUBGVmf-ev8uU_TP9
- Yoav walked through the use case flows so that people from different project can understand the details and subsequently identify impact/requirements/issues related to their respective projects. Jun 30, 2017 Meeting: Closed Loop Control
- Recorded meeting: https://zoom.us/recording/play/KG9scmJ1aaeV8ozDWaVhK9wPifYkCaF9qodXsyVOhM8z8Ld9PiKFD3K0IU2zl_rz
- Yoav presented the flow on automatic reboot/restart.
- One question was whether we want to restart VNF or VM. The answer is to restart VM.
- Data collection vG_MUX --> DCAE: What needs to be worked out is the VES version and payload to be supported by vG_MUX. DCAE would like to have sample data from the VNF. Yoav will bring these requirements to Danny Lin.
- Events DCAE --> Policy: The content of the events should be well defined.
- Control Policy --> APPC: The detailed interface definition needs to be worked out.
- Mapping from VNF ID to VM ID: The current flow shows that APPC will query AAI to perform the mapping. Further discussion is needed to decide where to do it: APPC or Policy.Jun 30, 2017 Meeting: Design Time
- Recorded meeting: https://zoom.us/recording/play/T7E79ekw4OaHRZCIf4dXF0Cq0PNVkA9bgyYsG2HKZqDhHCMFVGi6_gA3m_y5HSC0
- Yoav presented the VNF onboarding process
- VxLAN is preferred for the tunnels between BRG and vG MUX. Tunnels from different home networks will share the same VNI but are differentiated using the BRG IP addresses.
- Ron Shacham explained that CLAMP will create a blutprint template that will be used to instantiate a DCAE instance for the use case. CLAMP is not responsible for the development of the DCAE analytics program.
- It is determined that the infrastructure service and per customer service should be created individually.
- Yang Xu from Integration pointed out that VNF address assignment/management (including OAM IP and port IP) needs further discussions. Yoav will update the use case architecture diagram to include OAM IP addresses.
- It is realized that service design is complicated and needs more discussions. Yoav will follow up on these topic and schedule meetings.
- Micheal Lando mentioned that a new version of SDC is being set up in AT&T. Daniel will check whether the community can get access to it.Jul 6, 2017 Meeting: Design Time
- Recorded meeting is here.
- Brian Freeman explained that APPC should query AAI to get the VM ID and then perform VM restart.
- Currently that APPC polls to get the state after sending out restart command. There were discussions on using callback to get state change. Brian suggested that it be put in R2.
- Discussed the mapping between VxLAN tunnel and the VLAN between vG_MUX and vG1.Jul 9: closed loop diagram updated reflecting the discussion
- Jul 12: Important Questions
Discussed a the list of important questions. Refer this page: Use Case Related Important Questions and Answers - Jul 13: Service Model
- Recorded meeting: https://zoom.us/recording/play/hjKRZEbaAk2H2VRnGwKqjb--HEd4mGig96F7t7TSEHUOiPtl8Zh4Cl5UbB2L-zTg
- Gil Bullard presented the first version of service model. He will update his slides based on the discussions and then post them here.
- Jun 28, 2017 Meeting: Use Case Walk Through