Attendees

LIN MENG  (CMCC)

@henry YU (Huawei)

@Denise Provencher (Fujitsu)

Xin Miao (Fujitsu)

Chuanyu Chen  (Huawei)

@Hesam Rahimi(Huawei)

Swaminathan Seetharaman (Wipro)

Seshu Kumar Mudiganti (Huawei)

Shankaranarayanan Puzhavakath Narayanan (AT&T)

Zhang Min (CMCC)

Agenda

1, Updates of the slides

2, Continue the discussion on the IETF Model, have a basic consensus on the model.

Notes and Actions

1, Add a note that the architecture should allow non-IETF models to the implementation models.
2, Add slide 7 to illustrate that IETF Trans group is also working on TSCI Data model which is a Yang module, will be released this year. When we are talking about the standard interface, it is the Restconf or Yang module. So after the release of TSCI Data model, it can support TSCI standard interface which is carrying the data model schema. For ONAP internal trans NSSMF implementation, we can define the TSCI Model in A&AI model based on the adequate Information model, we don't need to wait for the Yang module definition.
-->This will cause two call flows in NSSMF adaptor. Henry to discuss with Seshu offline.
-->Need TOSCA Template for TSCI model. Need to evaluate whether the data model need enhancement in SDC. Henry and Lin disucss offline.

3, Implementation models are what to be supported in A&AI ,these are the implementation that only should be concerned by NSSMF module itself. They are technology specific. all the resources are abstracted as topologies, hierarchically.

4, How to model fronthaul? should the transport slice includes fronthaul, midhaul and backhaul, or the RAN subnet internally be spit into two subnet, one is the fronthaul, the other is the RAN elements.
Trans slice can be consumed by RAN (for fronthaul) and Core (for backhaul)connection.

-->Need to have a scenario or topology that cover three domain interaction.and provide the interactions So that Trans can define what kind of Nodes and the relation with RAN and Core. Swami and Chuanyu Take this.

Recording