Versions Compared

Old Version 159

changes.mady.by.user Thoralf Czichy

Saved on

compared with

New Version 160

changes.mady.by.user Thoralf Czichy

Saved on

Key

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

...

UTC-timeevery 2nd Tuesday, check from calendar

https://zoom.us/j/9644759813

New York (EDT / UTC-5)every 2nd Tuesday, check from calendar+1 669 900 6833 // +1 646 558 8656 // 855 880 1246 (Toll Free) // 877 369 0926 (Toll Free)
Paris (CEST / UTC+1)every 2nd Tuesday, check from calendar+33 7 5678 4048 // +33 1 8288 0188 // 805 082 588 (Toll Free)
Beijing (CST / UTC+8)every 2nd Tuesday, check from calendar+86 10 87833177 // +86 10 53876330 // 400 616 8835 (Toll Free) // 400 669 9381 (Toll Free)
Tokyo (JST / UTC+9) every 2nd Tuesday, check from calendar+81 524 564 439 // +81 3 4578 1488 // 0 800 100 5040 (Toll Free)
Helsinki  (EEST / UTC+2)every 2nd Tuesday, check from calendar

+358 341092129

Other international numbersWorld Time Zone Map

International numbers available: https://zoom.us/u/acyy3hylQi


2020-09-01

Recording: TODO near_rt_ricplatform_and_ricapp_meeting_2020_09_01.mp4

  1. S1+S2 team any news?
    1. Rahul progressing on RIC-95. Thoralf will help with testing as E2 simulator is needed.
    2. Subhash interested in picking up items on near-RT RIC platform. Thoralf to send information package.
    3. Double-check progress on E2 simulator in simulator project. Action item-Matti: check with Ron. Make sure to to add copyright and license statement.
    4. RIC-372 (sdlpy now supports notifications) now done.
  2. H1 team any news?
    1. RIC-109 (helm/k8s upgrade) Working on Non NFS based cluster storage on k8s
    2. RIC-509: HCL to present output/status of RIC-509.
      1. analysed com-pylog project on sonarcloud using our a/c
      2. Matti noted that xApp's MC xapp has done the same. Always needs to involve LF support case. HCL to include Matti in discussion.
    3. RIC-360: Go lang based code changes in progress
    4. RIC-150: (e2e benchmarking) Working on the Bouncer xAPP Implementation. "successfully built the e2apv1sim code manually in the LAB and run the e2sim binary. The e2sim sending the E2 setup request message to RIC terminator. The RIC terminator received the E2 setup message and it is not sending the response to e2sim. Because, in decode part of E2 setup request message in RIC, some parameters(RANfunction_Item) are not handled in RIC side and it's giving the decode error."
    5. RIC-149 (testing): Started fixing up the health check of ric component testsuites with few missing keywords and missing riccomponent_interface.robot files. As we confirmed with Bharath and Dave we are proceeding to fix the healthcheck and e2e testsuites related issues. Status: In progress Issue: Currently working on this while adding a1mediator interface.robot file " <tpl ($content).AsConfig $>: error calling tpl: Error during tpl function execution for "a1mediator.robot". Due to this some component related files are not mounted to nanobot pod. 
  3. alarms implemented in Cherry → check status with owners of sub user stories in
    Jira
    serverORAN Jira
    serverId5ec52304-b77c-3ce7-af6a-112cb13e6008
    keyRIC-56
    (check with owners of 585 203 and 204). Contact Nune
  4. to discuss this reply to Jinri's request: https://lists.o-ran-sc.org/g/main/message/812
    1. reply: " from near-RT RIC side we work with: (1) Akraino REC as the Akraino blueprint that we integrate RIC with (2) Nokia investigating if we can provide a wireshark dissector for E2AP (pending discussion with O-RAN alliance) (3) We're using the VESPA (Prometheus to VES adapter) project.
  5. Anything to demo on Thursday? Matti (50/50)?
  6. RICAPP agenda: RICAPP Meetings.

...