This page hosts information about discussion calls dedicated to R3+ service modeling.
...
- Service Model Proposal for R4 (Welcome any proposal)
- The role of 3GPP 28.541 in the ONAP service model Andy Mayer Gil Bullard
Past calls
20180919
Agenda
- Documentation status of Service model in Papyrus work
- Cancellation of the following two service IM calls
...
Will start service model discussion for R4 on 10.10.
20180829
Agenda
- Continued discussion about NS onboading or other issues.
- Review Service model in ONAP Information model in Papyrus.
...
Lingli Deng (China Mobile), Gil Bullard (AT&T), Mehmet (Verizon), Thinh Nguyenphu (Nokia), Xu Yang (Huawei), Andy Mayer (AT&T), Hui Deng (Huawei), Emmanuel Sarris (Vodafone) , Maopeng Zhang (ZTE)
Minutes
- Continued discussion about NS onboading or other issues. ?Proposed Approach for ONAP Runtime Support of Network Service Onboarding?
- Agreed ONAP should be evolving as a generic platform offering features as expected by the service providers in its service provisioning
- There is a difference in defining a service from the rest of industry from the perspective of a consumer rather than the implementation modules/system (as a collection of constitute resources, configuration scripts, etc.)
- Agreed to continue discussion on this and welcome Mehmet's presentation on MEF Interlude
- A request to clean up on the wiki workspace for further input to network service descriptor is raised
- Review Service model in ONAP Information model in Papyrus.
- GeneralServiceModelforR3+
- No comments received during the call.
- Service Descriptor
- No comments received during the call. Will seek Kevin's comments offline.
- GeneralServiceModelforR3+
...
1. VFC requirements for NSD (Yan Yang)
2. Resource/Service IM decision on NSD (Xu Yang)
3. NSD Proposal (maopeng zhang)
...