Date:
Participants
@Arda Akman (O-RAN)
@Burcu Yargicoglu-Sahin (O-RAN)
Alessandro Gerardo D'Alessandro
Agenda
- Go through the relevant details of the Closed Loop use cases for G-release for integration with O-RAN.
- Briefly discuss scope for H-release.
Notes and Actions
- For the integration and demo with O-RAN, foll. points to be checked and clarified:
- RRM Policy aligned with TS 28.542 v16.5.0
- Base configuration of CU/DU/RU may not be needed at all during slice creation/reuse – this might require some update in SDN-R. We also need to analyze ONAP should pass any other info apart from RRM Policy.
- A1 message contents and exact layout (ONAP action to also check use of A1 adaptor)
- VES 7.2 spec – new message format or old format, to be checked (check with Ben/Marge reg. this).
- For H-release, foll. could be potential candidates. Inputs will be sought from O-RAN community as well as our use case team in ONAP also during the next few weeks.
- Instantiation of RAN NFs, interaction with O-Cloud (first steps)
- Configuration of RAN NFs over standard O1 - will depend on availability of info models from O-RAN
- Slice assurance use cases - this needs to be evaluated further.
- Endpoints and transport connectivity related aspects, for e.g., parameters required to be passed to TN NSSMF (how they shall be determined), MP to MP connection, etc.
- The topic of where RAN config data shall be stored within ONAP was also discussed. This needs to be taken up further within ONAP, as our current understanding is, it will be part of C&PS. Similarly service RAN design should also be analyzed further.
Recording