search

srsran / srsRAN_Project

Open source O-RAN 5G CU/DU solution from Software Radio Systems (SRS) https://docs.srsran.com/projects/project
https://www.srsran.com
GNU Affero General Public License v3.0
523 stars 178 forks source link

Problem running the "simple_rc_xapp.py" xApp of o-ran-sc-ric #869

Closed alirezalab134 closed 1 month ago

alirezalab134 commented 1 month ago

Hi. I tried running the example xApp from the oran-sc-ric for ran control (simple_rc_xapp.py), following the "O-RAN NearRT-RIC and xApp" tutorial with only one UE. The sent ASN1 message seems to be received by the srsRAN gnb but it gives an error of "RAN function ID not supported". Here is the gnb.log file where I greped only the E2 line with the following command:

tail -f gnb.log | grep "E2"

Log:

tail: gnb.log: file truncated
2024-10-15T20:36:02.303431 [E2AP    ] [I] Connecting to E2 Agent RIC (192.168.63.10)..
2024-10-15T20:36:02.303500 [SCTP-GW ] [I] E2: Bind to 192.168.63.1:0 was successful
2024-10-15T20:36:02.303811 [E2AP    ] [I] E2 connection established
2024-10-15T20:36:02.391572 [E2      ] [I] Generate RAN function definition for OID: 1.3.6.1.4.1.53148.1.2.2.2
2024-10-15T20:36:02.391865 [E2      ] [I] Added RAN function OID 1.3.6.1.4.1.53148.1.2.2.2 to candidate list under RAN Function ID 2
2024-10-15T20:36:02.399802 [E2-ASN1-PCK] [I] Received PDU of 65 bytes
2024-10-15T20:36:02.399982 [E2      ] [I] Handling E2 PDU of type successfulOutcome
2024-10-15T20:36:02.399993 [E2      ] [I] E2AP msg, "successfulOutcome.E2setupResponse", transaction id=0
2024-10-15T20:36:02.400015 [E2      ] [I] E2 Setup procedure successful.
2024-10-15T20:36:02.400038 [E2      ] [I] Received E2 Setup Response message
2024-10-15T20:36:02.400064 [E2      ] [I] Added supported RAN function with id 2 and OID 1.3.6.1.4.1.53148.1.2.2.2
2024-10-15T20:36:08.612393 [E2SM-KPM] [D] Received RLC metrics: ue=0 DRB1.
2024-10-15T20:36:09.742556 [E2SM-KPM] [D] Received RLC metrics: ue=0 DRB1.
2024-10-15T20:36:10.816896 [E2SM-KPM] [D] Received RLC metrics: ue=0 DRB1.
2024-10-15T20:36:11.878511 [E2SM-KPM] [D] Received RLC metrics: ue=0 DRB1.
2024-10-15T20:36:12.940286 [E2SM-KPM] [D] Received RLC metrics: ue=0 DRB1.
2024-10-15T20:36:14.002804 [E2SM-KPM] [D] Received RLC metrics: ue=0 DRB1.
2024-10-15T20:36:15.086564 [E2SM-KPM] [D] Received RLC metrics: ue=0 DRB1.
2024-10-15T20:36:16.157426 [E2SM-KPM] [D] Received RLC metrics: ue=0 DRB1.
2024-10-15T20:36:17.236117 [E2SM-KPM] [D] Received RLC metrics: ue=0 DRB1.
2024-10-15T20:36:18.333949 [E2SM-KPM] [D] Received RLC metrics: ue=0 DRB1.
2024-10-15T20:36:19.400081 [E2SM-KPM] [D] Received RLC metrics: ue=0 DRB1.
2024-10-15T20:36:19.450789 [E2-ASN1-PCK] [I] Received PDU of 114 bytes
2024-10-15T20:36:19.450868 [E2      ] [I] Handling E2 PDU of type initiatingMessage
2024-10-15T20:36:19.450871 [E2      ] [I] E2AP SDU, "initiatingMessage.RICcontrolRequest"
2024-10-15T20:36:19.450873 [E2      ] [I] Received RIC Control Request
2024-10-15T20:36:19.450889 [E2      ] [E] RAN function ID not supported
2024-10-15T20:36:19.450889 [E2      ] [E] RAN function ID not supported
2024-10-15T20:36:20.456282 [E2SM-KPM] [D] Received RLC metrics: ue=0 DRB1.
2024-10-15T20:36:21.498793 [E2SM-KPM] [D] Received RLC metrics: ue=0 DRB1.
2024-10-15T20:36:22.549333 [E2SM-KPM] [D] Received RLC metrics: ue=0 DRB1.
2024-10-15T20:36:23.632783 [E2SM-KPM] [D] Received RLC metrics: ue=0 DRB1.
2024-10-15T20:36:24.457399 [E2-ASN1-PCK] [I] Received PDU of 114 bytes
2024-10-15T20:36:24.457475 [E2      ] [I] Handling E2 PDU of type initiatingMessage
2024-10-15T20:36:24.457483 [E2      ] [I] E2AP SDU, "initiatingMessage.RICcontrolRequest"
2024-10-15T20:36:24.457487 [E2      ] [I] Received RIC Control Request
2024-10-15T20:36:24.457505 [E2      ] [E] RAN function ID not supported
2024-10-15T20:36:24.457506 [E2      ] [E] RAN function ID not supported
2024-10-15T20:36:24.686003 [E2SM-KPM] [D] Received RLC metrics: ue=0 DRB1.
2024-10-15T20:36:25.751137 [E2SM-KPM] [D] Received RLC metrics: ue=0 DRB1.
2024-10-15T20:36:26.819516 [E2SM-KPM] [D] Received RLC metrics: ue=0 DRB1.
2024-10-15T20:36:27.887692 [E2SM-KPM] [D] Received RLC metrics: ue=0 DRB1.
2024-10-15T20:36:28.944917 [E2SM-KPM] [D] Received RLC metrics: ue=0 DRB1.
2024-10-15T20:36:29.462941 [E2-ASN1-PCK] [I] Received PDU of 114 bytes
2024-10-15T20:36:29.463013 [E2      ] [I] Handling E2 PDU of type initiatingMessage
2024-10-15T20:36:29.463016 [E2      ] [I] E2AP SDU, "initiatingMessage.RICcontrolRequest"
2024-10-15T20:36:29.463019 [E2      ] [I] Received RIC Control Request
2024-10-15T20:36:29.463034 [E2      ] [E] RAN function ID not supported
2024-10-15T20:36:29.463034 [E2      ] [E] RAN function ID not supported
2024-10-15T20:36:30.010045 [E2SM-KPM] [D] Received RLC metrics: ue=0 DRB1.
2024-10-15T20:36:31.059293 [E2SM-KPM] [D] Received RLC metrics: ue=0 DRB1.
2024-10-15T20:36:32.117266 [E2SM-KPM] [D] Received RLC metrics: ue=0 DRB1.
2024-10-15T20:36:33.165675 [E2SM-KPM] [D] Received RLC metrics: ue=0 DRB1.
2024-10-15T20:36:34.215215 [E2SM-KPM] [D] Received RLC metrics: ue=0 DRB1.
2024-10-15T20:36:34.468806 [E2-ASN1-PCK] [I] Received PDU of 114 bytes
2024-10-15T20:36:34.468965 [E2      ] [I] Handling E2 PDU of type initiatingMessage
2024-10-15T20:36:34.468969 [E2      ] [I] E2AP SDU, "initiatingMessage.RICcontrolRequest"
2024-10-15T20:36:34.468973 [E2      ] [I] Received RIC Control Request
2024-10-15T20:36:34.468993 [E2      ] [E] RAN function ID not supported
2024-10-15T20:36:34.468993 [E2      ] [E] RAN function ID not supported
2024-10-15T20:36:35.281191 [E2SM-KPM] [D] Received RLC metrics: ue=0 DRB1.
2024-10-15T20:36:36.336305 [E2SM-KPM] [D] Received RLC metrics: ue=0 DRB1.
2024-10-15T20:36:37.392821 [E2SM-KPM] [D] Received RLC metrics: ue=0 DRB1.
2024-10-15T20:36:38.449745 [E2SM-KPM] [D] Received RLC metrics: ue=0 DRB1.
2024-10-15T20:36:39.475346 [E2-ASN1-PCK] [I] Received PDU of 114 bytes
2024-10-15T20:36:39.475421 [E2      ] [I] Handling E2 PDU of type initiatingMessage
2024-10-15T20:36:39.475427 [E2      ] [I] E2AP SDU, "initiatingMessage.RICcontrolRequest"
2024-10-15T20:36:39.475429 [E2      ] [I] Received RIC Control Request
2024-10-15T20:36:39.475444 [E2      ] [E] RAN function ID not supported
2024-10-15T20:36:39.475444 [E2      ] [E] RAN function ID not supported
2024-10-15T20:36:39.525439 [E2SM-KPM] [D] Received RLC metrics: ue=0 DRB1.
2024-10-15T20:36:40.586060 [E2SM-KPM] [D] Received RLC metrics: ue=0 DRB1.
2024-10-15T20:36:41.656589 [E2SM-KPM] [D] Received RLC metrics: ue=0 DRB1.
2024-10-15T20:36:42.720282 [E2SM-KPM] [D] Received RLC metrics: ue=0 DRB1.
2024-10-15T20:36:43.770883 [E2SM-KPM] [D] Received RLC metrics: ue=0 DRB1.
2024-10-15T20:36:44.481071 [E2-ASN1-PCK] [I] Received PDU of 114 bytes
2024-10-15T20:36:44.481154 [E2      ] [I] Handling E2 PDU of type initiatingMessage
2024-10-15T20:36:44.481157 [E2      ] [I] E2AP SDU, "initiatingMessage.RICcontrolRequest"
2024-10-15T20:36:44.481159 [E2      ] [I] Received RIC Control Request
2024-10-15T20:36:44.481172 [E2      ] [E] RAN function ID not supported
2024-10-15T20:36:44.481172 [E2      ] [E] RAN function ID not supported
2024-10-15T20:36:44.831918 [E2SM-KPM] [D] Received RLC metrics: ue=0 DRB1.
2024-10-15T20:36:45.893390 [E2SM-KPM] [D] Received RLC metrics: ue=0 DRB1.

Issue Description

Problem running the "simple_rc_xapp.py" xApp of o-ran-sc-ric

Setup Details

Running "O-RAN NearRT-RIC and xApp" tutorial with only one UE, but running "docker compose exec python_xapp_runner ./simple_rc_xapp.py" instead of the "kpm_mon_xapp"

Expected Behavior

Start changing RAN functions related to PRBs

Actual Behaviour

The RIC control request is received on the srsRAN but it gives an error of "RAN function ID not supported"

Steps to reproduce the problem

Start running the "O-RAN NearRT-RIC and xApp" tutorial with only one UE. And then run the following sample xApp in the oran-sc-ric

Additional Information

pgawlowicz commented 1 month ago

did you enable rc module in gnb config? add

e2:
  ...
  e2sm_rc_enabled: true            # Enable KPM service module
alirezalab134 commented 1 month ago

I didn't. Thanks it seems that solved the issue.