...
- The recent update in 3GPP NRM w.r.to the definition of endpoints (TS 28.541) was discussed.
- The foll. were proposed as working assumptions for now, until there is more clarity.
- qosProfile and nextHop information shall not contain any values when passed from RAN NSSMF to TN NSSMF (for FH and MH).
- Post meeting note: The above assumption shall also be extended to NSMF in case of BH.
- We will assume P2P links or a uniform split of parameters such as BW across multipoint links.
- The foll. aspects need to be clarified further with IETF folks (from modeling and functional perspective):
- TransportSLAPolicy contains only maxBandwidth, but no attribute for 'guaranteed' bandwidth.
- Interpretation of the attributes such as bandwidth in case of multipoint to multipoint links, whether enhancements to the model is required.
- The foll. points need to be investigated/checked further:
- The split of responsibilities between RAN NSSMF (and NSMF), and TN NSSMF in determining logical interface id, next hop, qosProfile, etc. Role of provisioning by Management System in this.
- Having a set of endpoints in RAN and Core which need to be inter-connected by TN NSSI (from ONAP perspective).
- It was clarified that the current modeling constructs allow an endpoint to be associated to multiple TN NSSIs. This is important to address, for e.g., scenarios wherein RAN NF NSSI is reused but a new TN NSSI is created when creating a new NSI.
- Inputs were sought from ORAN team on expectations from ORAN side for H-release requirements. This shall be discussed further in upcoming meetings.
Reference Links
...