Assistance required for free5gc integration with OAI

Q/A
,
#22

Dear Yashih/Team,

Thanks for the suggestions. I will try them out and will get back to you with my findings.

Best regards,
Indranil Saha

#23

Dear Yashih/Team,

Please find the below observations -

  1. Even though I disabled the “search ID” field in OAI NRF, it’s still populating in wireshark capture file.
  2. Warning generated in OAI NRF while other NFs are registering to it:
    [2023-12-19 07:37:39.500] [nrf_app] [warning] Format error in format string PLMN List(MCC, MNC): %d, %s: invalid type specifier
  3. Warning generated in OAI NRF after gNB connection -
    [2023-12-19 07:38:31.903] [nrf_app] [info]
    Handle the first Heartbeat timeout, NF instance ID 9db32579-68af-41c7-8056-d297b35d9be4, current time 1702971479476
    [2023-12-19 07:38:31.909] [nrf_app] [debug] Set NF status to SUSPENDED
    [2023-12-19 07:38:31.912] [nrf_app] [debug] Unsubscribe to the first Heartbeat Timer timeout event (after NF Registration)
  4. Checked UE webconsole and ue.yaml file - in UE webconsole 2 S-NSSAI info present with mutiple DNS configurations (2 for each S-NSSAI), whereas in ue.yaml, all populated S-NSSAI are not configured.
  5. Errors in free5gc log files are as follows -
    2023-12-19T07:39:20.177660175Z [ERRO][UDM][Consumer] unsupported scheme[]
    2023-12-19T07:39:20.177684068Z [ERRO][UDM][Proc] ID[imsi-208930000000003] does not match any UDR
    2023-12-19T07:39:20.341269360Z [ERRO][AMF][Gmm][amf_ue_ngap_id:RU:1,AU:1(3GPP)][supi:SUPI:] UE Security Context is not Available, message type 100

Attached are the log file of free5gc 5gc and issue document.

testapproach7_free5gc 5g core log.txt (18.4 KB)
Issue document_2.docx (341.4 KB)

Best regards,
Indranil Saha

#24

Hi @IndranilSaha09

I’m the collaborator of the free5GC project.
Although we have a plan to upgrade the free5GC to 3GPP rel17, but integrate other 5GC implementation is not in our plan currently.
For your issue, I suggest that you can try to:

  • Implement the proxy server between oai-nrf and free5GC-nf(s), proxy is responsible for transferring the data schema from r17 (OAI) to r15 (free5GC).
  • Update the data models what you used in free5GC, in your case, you can update the free5gc/openapi package first and update the NF registration handler in all of NFs.

Thanks.

#25

Dear @ianchen0119 / Team,

Firstly, Happy New Year !! Wish you all the success in the coming time.

Now, for the above mentioned points, can you also mention any suggestions to which I can refer to for both the tasks - 1) installation of the proxy server, 2) Updation of the data models in free5gc. Is there any documentation or links to follow ? Thanks !

Best regards,
Indranil Saha

#26

Dear Team,

Adding my observation (when OAI NRF is integrated with free5gc NFs) -

After few seconds of getting registered to NRF, the NFs are not sending heartbeat signals and consequently, the error is getting populated in the log of NRF –

[2024-01-02 20:01:34.936] [nrf_app] [info]
Handle the first Heartbeat timeout, NF instance ID 1c932ceb-282c-46c9-851e-2cbdafd4e3ce, current time 1704225648783
[2024-01-02 20:01:34.936] [nrf_app] [debug] Set NF status to SUSPENDED
[2024-01-02 20:01:34.937] [nrf_app] [debug] Unsubscribe to the first Heartbeat Timer timeout event (after NF Registration)

If possible from your end, please review this and revert back with suggestions to rectify this.

Best regards,
Indranil Saha

#27

Hi,
If you have further questions about this topic, please create another topic.
Thanks.

Best regards,

#28