Demo on how to deploy the near-RT RIC, compile and connect the E2 simulator, compile the hello-world go xapp and how use the dms_cli to deploy it: DEMO
Demo of other features
Recording: RIC platform part: link to recording 1 of the meeting RIC xApp project part: link to recording 2 of the meeting
Schedule, see calendar for May-24.
Zoom = Zoom 1 bridge: https://zoom.us/j/9644759813
Note that for the project meeting in two weeks from now, Thoralf will be on holiday (Jun-2 - Jun-10). Release tasks we handle by e-mail.
Near-RT RIC platform (we might change the order of demos in the beginning of the meeting)
- 10 min Deploying the F release (Sandeep & co )
- 10 min RIC-886 Support two SCTP streams in same association for global (support functions) and functional procedures (ric services) (Sandeep Kumar)
- 10 min RIC-888 query interface in nodeb-rnib for querying RAN functions by OID - demo was held on Jul-19 as part of the project meeting (fast forward to minute 00:14:51 in the zoom recording from 2022-07-19
) - RIC-916 new reconnect timer in E2 to reject new connect for x seconds - demo was held on Jun-21 as part of the project meeting (fast forward to minute 00:08:30 in zoom recording from 2022-06-21)
- 10 min RIC-906 time-series (influxdb) wrapper (Mohammad Arif & co)
- 15 min E2APv2.0 support in E2mgr (Subhash Kumar Singh)
- 10 min A1 mediator implementation in golang (Naman Gupta)
- 10 min demo of the xapp-frame-py enhancements for subscription management and others (Erkki) demo was held on Oct-11 as part of the project meeting (fast forward to minute 00:10:30 in zoom recording from 2022-10-11
Near-RT RIC xApp project
- 10 min Traffic Steering xApp (Alexandre Huff)
- 10 Min A1 Mediator Nanobot test Automation + Rest API implementation - Amit & Team
- 10 Min RIC subscription delete
- KPIMON xApp - Amit & team
Please upload slides as attachment to this demo page.
10 Comments
Mohammad Sadegh Ghasrizadeh
Hello, Thanks for the demo.
I followed the steps in the last demo for KPIMON-go xApp but the pod stays in the "ImagePullBackOff" state because of not building the Docker image from the Dockerfile.
Would you please provide instructions to build the Docker image?
Any help would be appreciated.
Thoralf Czichy
If you want to build the KPImon xApp please contact the "ric xapp" project. If you have the docker image, try to "docker pull" the image first (from one of the nodes where Kubernetes is deployed). This should rule out issues in the docker setup.
Qiao Wang
Hello, Thoralf Czichy. Thanks for your demo.
I'm now trying to implement RIC in our lab by following the instructions in the demo. The instruction looks straightforward but I'm stuck in the step for k8s installation. As demonstrated in the guidance, I used ./install_k8s_and_helm.sh However, the outcome of this command didn't seem to be successful. Since I'm not an expert in Linux, this issue makes me frustrated as I am not sure about the right direction to debug.
The execution outcome of this command is very long so I inserted a txt file for your reference. Please could Thoralf or anyone in the community take a look and advise? Thank you in advance.
Thoralf Czichy
Looks like you did not run the script form the root account. The script needs to be run form the root account.
Md Nur Mohammad
Is there any guidance or demo video to connect near-RT RIC and non-RT RIC?
Hyeonmin Yoo
Hello. Thank you for nice demo.
I have a question about e2esimu (gnbe2oransimu) from 12:22. I want to know more detail about that.
Rafael Cavalcanti
Hi Thoralf Czichy ,
The curl command (curl -X GET http://service-ricplt-e2mgr-http-ip:3800/v1/nodeb/states 2>/dev/null|jq) returns empty brackets. Some steps changed in the tutorial above because the project seems to be moved to github, but I think the error I am facing is unrelated. Any guidance to solve this issue?
Salam Romimaa
Thanks for your Demo Dear Thoralf Czichy.
Rafael Cavalcanti
Hi Salam, did you manage to reproduce the steps in the demo?
nicola.adami.1@studenti.unipd.it
Hi everybody,
I have an issue during the registration phase in the RIC Platform, suddenly the communication shut down.
Below the output:
Starting KPM processor simJSON Test
kpm0
kpm0.9
kpm2
kpm3
ret is 0
kpm4
kpm5
kpm6
<E2SM-KPM-RANfunction-Description>
<ranFunction-Name>
<ranFunction-ShortName>ORAN-E2SM-KPM</ranFunction-ShortName>
<ranFunction-E2SM-OID>OID123</ranFunction-E2SM-OID>
<ranFunction-Description>KPM monitor</ranFunction-Description>
<ranFunction-Instance>1</ranFunction-Instance>
</ranFunction-Name>
<e2SM-KPM-RANfunction-Item>
<ric-EventTriggerStyle-List>
<RIC-EventTriggerStyle-List>
<ric-EventTriggerStyle-Type>1</ric-EventTriggerStyle-Type>
<ric-EventTriggerStyle-Name>Periodic report</ric-EventTriggerStyle-Name>
<ric-EventTriggerFormat-Type>5</ric-EventTriggerFormat-Type>
</RIC-EventTriggerStyle-List>
</ric-EventTriggerStyle-List>
<ric-ReportStyle-List>
<RIC-ReportStyle-List>
<ric-ReportStyle-Type>1</ric-ReportStyle-Type>
<ric-ReportStyle-Name>O-DU Measurement Container for the 5GC connected deployment</ric-ReportStyle-Name>
<ric-IndicationHeaderFormat-Type>1</ric-IndicationHeaderFormat-Type>
<ric-IndicationMessageFormat-Type>1</ric-IndicationMessageFormat-Type>
</RIC-ReportStyle-List>
<RIC-ReportStyle-List>
<ric-ReportStyle-Type>2</ric-ReportStyle-Type>
<ric-ReportStyle-Name>O-DU Measurement Container for the EPC connected deployment</ric-ReportStyle-Name>
<ric-IndicationHeaderFormat-Type>1</ric-IndicationHeaderFormat-Type>
<ric-IndicationMessageFormat-Type>1</ric-IndicationMessageFormat-Type>
</RIC-ReportStyle-List>
<RIC-ReportStyle-List>
<ric-ReportStyle-Type>3</ric-ReportStyle-Type>
<ric-ReportStyle-Name>O-CU-CP Measurement Container for the 5GC connected deployment</ric-ReportStyle-Name>
<ric-IndicationHeaderFormat-Type>1</ric-IndicationHeaderFormat-Type>
<ric-IndicationMessageFormat-Type>1</ric-IndicationMessageFormat-Type>
</RIC-ReportStyle-List>
<RIC-ReportStyle-List>
<ric-ReportStyle-Type>4</ric-ReportStyle-Type>
<ric-ReportStyle-Name>O-CU-CP Measurement Container for the EPC connected deployment</ric-ReportStyle-Name>
<ric-IndicationHeaderFormat-Type>1</ric-IndicationHeaderFormat-Type>
<ric-IndicationMessageFormat-Type>1</ric-IndicationMessageFormat-Type>
</RIC-ReportStyle-List>
<RIC-ReportStyle-List>
<ric-ReportStyle-Type>5</ric-ReportStyle-Type>
<ric-ReportStyle-Name>O-CU-UP Measurement Container for the 5GC connected deployment</ric-ReportStyle-Name>
<ric-IndicationHeaderFormat-Type>1</ric-IndicationHeaderFormat-Type>
<ric-IndicationMessageFormat-Type>1</ric-IndicationMessageFormat-Type>
</RIC-ReportStyle-List>
<RIC-ReportStyle-List>
<ric-ReportStyle-Type>6</ric-ReportStyle-Type>
<ric-ReportStyle-Name>O-CU-UP Measurement Container for the EPC connected deployment</ric-ReportStyle-Name>
<ric-IndicationHeaderFormat-Type>1</ric-IndicationHeaderFormat-Type>
<ric-IndicationMessageFormat-Type>1</ric-IndicationMessageFormat-Type>
</RIC-ReportStyle-List>
</ric-ReportStyle-List>
</e2SM-KPM-RANfunction-Item>
</E2SM-KPM-RANfunction-Description>
er encded is 489
after encoding message
here is encoded message �ORAN-E2SM-KPM
this is the char array �ORAN-E2SM-KPM
!!!lenth of ranfuncdesc is 15
value of this index is 32
value of this index is 192
value of this index is 79
value of this index is 82
value of this index is 65
value of this index is 78
value of this index is 45
value of this index is 77
value of this index is 0
value of this index is 32
value of this index is 102
%%about to register e2sm func desc for 0
%%about to register callback for subscription for func_id 0
Start E2 Agent (E2 Simulator
After reading input options
[SCTP] Binding client socket to source port 36422
[SCTP] Connecting to server at 10.96.161.72:36422 ...
[SCTP] Connection established
After starting client
client_fd value is 3
looping through ran func
about to call setup request encode
After generating e2setup req
<E2AP-PDU>
<initiatingMessage>
<procedureCode>1</procedureCode>
<criticality><reject/></criticality>
<value>
<E2setupRequest>
<protocolIEs>
<E2setupRequestIEs>
<id>49</id>
<criticality><reject/></criticality>
<value>
<TransactionID>1</TransactionID>
</value>
</E2setupRequestIEs>
<E2setupRequestIEs>
<id>3</id>
<criticality><reject/></criticality>
<value>
<GlobalE2node-ID>
<gNB>
<global-gNB-ID>
<plmn-id>37 34 37</plmn-id>
<gnb-id>
<gnb-ID>
10110101110001100111011110001
</gnb-ID>
</gnb-id>
</global-gNB-ID>
</gNB>
</GlobalE2node-ID>
</value>
</E2setupRequestIEs>
<E2setupRequestIEs>
<id>10</id>
<criticality><reject/></criticality>
<value>
<RANfunctions-List>
<ProtocolIE-SingleContainer>
<id>8</id>
<criticality><reject/></criticality>
<value>
<RANfunction-Item>
<ranFunctionID>0</ranFunctionID>
<ranFunctionDefinition>
20 C0 4F 52 41 4E 2D 45 32 53 4D 2D 4B 50 4D 00
00 05 4F 49 44 31 32 33 05 00 4B 50 4D 20 6D 6F
6E 69 74 6F 72 08 AB BE FC B0 ED C6 A4 00 60 00
01 01 07 00 50 65 72 69 6F 64 69 63 20 72 65 70
6F 72 74 01 05 14 01 01 1D 00 4F 2D 44 55 20 4D
65 61 73 75 72 65 6D 65 6E 74 20 43 6F 6E 74 61
69 6E 65 72 20 66 6F 72 20 74 68 65 20 35 47 43
20 63 6F 6E 6E 65 63 74 65 64 20 64 65 70 6C 6F
79 6D 65 6E 74 01 01 01 01 00 01 02 1D 00 4F 2D
44 55 20 4D 65 61 73 75 72 65 6D 65 6E 74 20 43
6F 6E 74 61 69 6E 65 72 20 66 6F 72 20 74 68 65
20 45 50 43 20 63 6F 6E 6E 65 63 74 65 64 20 64
65 70 6C 6F 79 6D 65 6E 74 01 01 01 01 00 01 03
1E 80 4F 2D 43 55 2D 43 50 20 4D 65 61 73 75 72
65 6D 65 6E 74 20 43 6F 6E 74 61 69 6E 65 72 20
66 6F 72 20 74 68 65 20 35 47 43 20 63 6F 6E 6E
65 63 74 65 64 20 64 65 70 6C 6F 79 6D 65 6E 74
01 01 01 01 00 01 04 1E 80 4F 2D 43 55 2D 43 50
20 4D 65 61 73 75 72 65 6D 65 6E 74 20 43 6F 6E
74 61 69 6E 65 72 20 66 6F 72 20 74 68 65 20 45
50 43 20 63 6F 6E 6E 65 63 74 65 64 20 64 65 70
6C 6F 79 6D 65 6E 74 01 01 01 01 00 01 05 1E 80
4F 2D 43 55 2D 55 50 20 4D 65 61 73 75 72 65 6D
65 6E 74 20 43 6F 6E 74 61 69 6E 65 72 20 66 6F
72 20 74 68 65 20 35 47 43 20 63 6F 6E 6E 65 63
74 65 64 20 64 65 70 6C 6F 79 6D 65 6E 74 01 01
01 01 00 01 06 1E 80 4F 2D 43 55 2D 55 50 20 4D
65 61 73 75 72 65 6D 65 6E 74 20 43 6F 6E 74 61
69 6E 65 72 20 66 6F 72 20 74 68 65 20 45 50 43
20 63 6F 6E 6E 65 63 74 65 64 20 64 65 70 6C 6F
79 6D 65 6E 74 01 01 01 01
</ranFunctionDefinition>
<ranFunctionRevision>2</ranFunctionRevision>
<ranFunctionOID>OID123</ranFunctionOID>
</RANfunction-Item>
</value>
</ProtocolIE-SingleContainer>
</RANfunctions-List>
</value>
</E2setupRequestIEs>
<E2setupRequestIEs>
<id>50</id>
<criticality><reject/></criticality>
<value>
<E2nodeComponentConfigAddition-List>
<ProtocolIE-SingleContainer>
<id>51</id>
<criticality><reject/></criticality>
<value>
<E2nodeComponentConfigAddition-Item>
<e2nodeComponentInterfaceType><ng/></e2nodeComponentInterfaceType>
<e2nodeComponentID>
<e2nodeComponentInterfaceTypeNG>
<amf-name>nginterf</amf-name>
</e2nodeComponentInterfaceTypeNG>
</e2nodeComponentID>
<e2nodeComponentConfiguration>
<e2nodeComponentRequestPart>72 65 71 70 61 72 74</e2nodeComponentRequestPart>
<e2nodeComponentResponsePart>72 65 73 70 61 72 74</e2nodeComponentResponsePart>
</e2nodeComponentConfiguration>
</E2nodeComponentConfigAddition-Item>
</value>
</ProtocolIE-SingleContainer>
</E2nodeComponentConfigAddition-List>
</value>
</E2setupRequestIEs>
</protocolIEs>
</E2setupRequest>
</value>
</initiatingMessage>
</E2AP-PDU>
After XER Encoding
error length 0
error buf
er encded is 581
in sctp send data func
data.len is 581after getting sent_len
[SCTP] Sent E2-SETUP-REQUEST
about to call E2ResetRequest encode
[E2AP] Created E2ResetRequest
before
<E2AP-PDU>
<initiatingMessage>
<procedureCode>3</procedureCode>
<criticality><reject/></criticality>
<value>
<ResetRequest>
<protocolIEs>
<ResetRequestIEs>
<id>49</id>
<criticality><ignore/></criticality>
<value>
<TransactionID>1</TransactionID>
</value>
</ResetRequestIEs>
<ResetRequestIEs>
<id>1</id>
<criticality><ignore/></criticality>
<value>
<Cause>
<e2Node><e2node-component-unknown/></e2Node>
</Cause>
</value>
</ResetRequestIEs>
</protocolIEs>
</ResetRequest>
</value>
</initiatingMessage>
</E2AP-PDU>
after
error length 0
error buf
er encoded is 18
in sctp send data func
data.len is 18after getting sent_len
[SCTP] Sent E2ResetRequest
[SCTP] Waiting for SCTP data
receive data1
receive data2
receive data3
[SCTP] Connection closed by remote peer