Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Schedule for R6 (second half of Cherry: Jira usage conventions§6).
  2. demos for demo day (next week Thursday = Sep-24 in 2020-09-24 Cherry R6.1)
  3. Subhash: move on with exact contribution.
    1. [1] Higher abstraction level in xAPP framework SDK (golang) [https://jira.o-ran-sc.org/browse/RIC-366]
      1. We discussed possible abstraction of this on API level. Matti said one person on AT&T side has been working on this before. We need to set up a separate meeting on this: Subhash, Nune, Matti, Neeraj Gupta (HCL), Vaishali (HCL), h_w.park@samsung.com. Identify new capabilities that we can implement on xapp framework side. Focus on things not yet implemented in any xapp frameworks. presentation by  h_w.park@samsung.com on what is planned. Aim for 10am EDT (NewYork) on Monday, Sep-21
      2. RIC-80 is already in progress by Antti teams.
      3. general goal xApps should only rely on E2SM, but do not need to touch E2AP messages (using ASN.1). So, a good abstraction would allow xApp implementation without ever touching an ASN.1 compiler if an E2SM would be defined in something else than ASN.1. We can discuss this further in the Monday meeting.
    2. [2] Support for E2AP RESET procedure  [https://jira.o-ran-sc.org/browse/RIC-383]
    3. [3] Developing version of xAPP [https://jira.o-ran-sc.org/browse/RIC-120]
      1. existing "hello world" is C++, but does more than just saying "Hello world", e.g. has own service model. Additional demo xapps in go/python are welcome. For go see in xapp-framework for Go for some skeleton code.
      2. for example, it would be good to have E2SM support for "hello world" E2SM in the simulator.
  4. Alok RIC-509 works better with Ceph (instead of NFS). Meeting to discuss how to integrate this to be called by Alok.
  5. RICAPP agenda: RICAPP Meetings.

...