LTE NR co-existance by Rashed97 · Pull Request #444 · herlesupreeth/docker_open5gs

Rashed97 · 2025-03-27T20:39:21Z

No description provided.

These shouldn't be hardcoded, but rather use the IP addresses declared in .env

Rework the MySQL container: - Change the mysql_init.sh to be bind mounted: This allows dynamic changes to the script without having to recompile the container. - Change the way the container data is first set up: The current process depends on the container being started the first time with an empty docker volume, since the docker volume will then implement a "copy on first use" method to populate itself with data. This data is in the docker image from the initial compilation, as installing mysql-server also initializes the data directory. If for some reason, the docker volume is not "empty", then the generic MySQL data directory from the image is never copied into it, resulting in an invalid data directory. This adds checks to ensure that the data directory is present, and if not, then initialize one before trying to use it. - Change the permission setting: The current usermod -d call doesn't guarantee that the data directory is owned by mysql:mysql, and therefore leaves open the possibility for the data directory to fail to be used by the MySQL daemon. This occurs when migrating the volume from one machine to another. Adding the chown -R call ensures that the owner is set properly. - Don't use mysql restart Some edge cases exist where restart doesn't actually stop any running mysql instances. Use stop and start instead, and also add a kill call to ensure that all running mysql instances are fully killed before we make changes.

- Don't use pkill or kill with database processes. These could lead to database corruption - Make sure to gracefully shutdown the database daemon/services when the script recieves a terminate or interrupt command - Ensure that mysqld_safe doesn't take over the PID so that interrupt or terminate signals reach the script - Change the image to use ENTRYPOINT to ensure that signals reach it - Add health check: Docker will ping the mysql database service every 30sec to ensure it's still up

Currently the P-CSCF can handle LTE-LTE and NR-NR communications. Cross-technology communications are still a work in progress.

Using the PANI header, we can determine what interface this UE should register via. TODO: - Implement detection for additional network types (ex. for IWLAN) - Add some sort of database store for network access type, to be used in the mt config, as P-CSCF cannot query the network type from the device before starting a call

…disabled

MT is currently broken due to the lack of a PANI header. This needs to be reconfigured to read out of a database that has updated values that are written during UE registeration.

Precursor to moving the N5 code to it's own configs

This allows us to have entirely different routes to select from depending on the technology, versus having to do switching in the middle of the routes.

This completes the changes required for dynamic N5 and Rx route selection. This adds the following: - A table to store subscribers and their registration tech - A table to store contact subscribers for contact aors - An HTTP endpoint in S-CSCF to query for a IMPI given a public identity (ex. MSISDN) - Proper retrieval of the IMPI in MO and MT routes - Routing based on the registration tech retrieved from the table given an IMPI

Required after the route config file split

Rashed97 · 2025-03-27T20:39:56Z

@herlesupreeth I've rebased the LTE/NR coex branch here. Let me know if you want any additional changes to it before merging.

herlesupreeth · 2025-03-28T07:38:12Z

Awesome!! Thanks a ton for your huge effort again. Really like the additions to srsRAN :) . I will review this MR over weekend and merge

herlesupreeth

Left a minor comment. Thanks again for this nice contribution.

herlesupreeth · 2025-03-30T12:18:13Z

 ##!define WITH_DEBUG
 #!define WITH_NAT
-##!define WITH_NATPING
+#!define WITH_NATPING


please revert this change. I prefer NATPING to be disabled

herlesupreeth · 2025-04-02T17:39:22Z

Have you tested 5G calling with this change? I am getting following crash on pcscf upon deploying


Deploying component: 'pcscf'
mysqld is alive
 0(59) INFO: rtimer [rtimer_mod.c:307]: stm_t_param(): created rtimer name=NATPING interval=5 mode=1
 0(59) INFO: rtimer [rtimer_mod.c:307]: stm_t_param(): created rtimer name=NRF_NFM interval=5 mode=1
 0(59) INFO: pv [pv_shv.c:61]: shvar_init_locks(): locks array size 16
 0(59) INFO: <core> [core/tcp_main.c:5241]: init_tcp(): using epoll_lt as the io watch method (auto detected)
loading modules under config path: /usr/lib64/kamailio/modules_k/:/usr/lib64/kamailio/modules/:/usr/lib/kamailio/modules_k/:/usr/lib/kamailio/modules/:/usr/lib/x86_64-linux-gnu/kamailio/modules/:/usr/local/lib64/kamailio/modules
Listening on 
             udp: 172.22.0.21 [172.22.0.21]:5060
             tcp: 172.22.0.21 [172.22.0.21]:5060
Aliases: 
             *: pcscf.ims.mnc001.mcc001.3gppnetwork.org:*

 0(59) INFO: <core> [main.c:3321]: main(): current open file limits [soft/hard]: [1048576/1048576]
 0(59) ERROR: <core> [core/mem/q_malloc.c:758]: qm_realloc(): qm_realloc(0x725fdec00010, 1024) called from core: core/counters.c: cnt_hash_add(390), module: core; qm_malloc() failed!
 0(59) ERROR: <core> [core/counters.c:857]: register_module_stats(): failed to add statistic core.rcv_replies_482
 0(59) ERROR: kex [core_stats.c:478]: register_core_stats(): failed to register core statistics
 0(59) ERROR: <core> [core/sr_module.c:1051]: init_mod(): Error while initializing module kex (/usr/local/lib64/kamailio/modules/kex.so)
ERROR: error while initializing modules
 0(59) ERROR: ims_ipsec_pcscf [ipsec.c:654]: clean_sa(): Error sending delete SAs command via netlink socket: No data available
 0(59) WARNING: ims_ipsec_pcscf [cmd.c:1397]: ipsec_cleanall(): Error cleaning IPSec Security associations during startup.
 0(59) ERROR: ims_ipsec_pcscf [ipsec.c:703]: clean_policy(): Error sending delete policies command via netlink socket: No data available
 0(59) WARNING: ims_ipsec_pcscf [cmd.c:1401]: ipsec_cleanall(): Error cleaning IPSec Policies during startup.
 0(59) ERROR: ims_ipsec_pcscf [ims_ipsec_pcscf_mod.c:422]: mod_destroy(): Error destroying spi generator

Rashed97 · 2025-04-21T19:45:57Z

@herlesupreeth Apologies for the late reply, I was travelling for work and this kept slipping my mind.

That's actually the exact error that I was facing before that led me to increase the memory size for P-CSCF. I wasn't having it anymore when I last ran my core but I'll try again in the next couple of days when I get home and get some time to spin it up again.

Rashed97 and others added 18 commits March 27, 2025 16:01

Allow customizable metrics port

642f1c0

Expose osmohlr CTRL port for interaction

b09afb2

Use PCSCF_IP and PCF_IP in P-CSCF routing configs

2bcf540

These shouldn't be hardcoded, but rather use the IP addresses declared in .env

[AMF/MME] Allow setting network name via .env

1b635db

Add dynamic PYHSS_BIND_PORT to deploy-all compose file

f1d20e7

[P-CSCF] Enable dual LTE/NR P-CSCF deployment mode

247b289

Currently the P-CSCF can handle LTE-LTE and NR-NR communications. Cross-technology communications are still a work in progress.

[P-CSCF] Fall back to Rx registeration in the 401 handshake if N5 is …

b4194dd

…disabled

[P-CSCF] Add dynamic Rx and N5 selection to MO and MT routes

5cd3fba

MT is currently broken due to the lack of a PANI header. This needs to be reconfigured to read out of a database that has updated values that are written during UE registeration.

[P-CSCF] Rename mo/mt.cfg to mo/mt_Rx.cfg

1f5954c

Precursor to moving the N5 code to it's own configs

[P-CSCF] Move N5 MO/MT routes to seperate config files

846a8f9

This allows us to have entirely different routes to select from depending on the technology, versus having to do switching in the middle of the routes.

[P-CSCF]/[mysql] Increase connection and memory limits

beb5189

Required after the route config file split

[P-CSCF] Cleanup unused MSISDN fetching code

4694af1

Update srsRAN_Project commit, fixing VoNR calling issue

e63a775

[srsran]: Add additional srsran configs for low latency, MIMO and QAM256

334e8bd

herlesupreeth reviewed Mar 30, 2025

View reviewed changes

herlesupreeth mentioned this pull request Jul 3, 2025

About deploy-all.yaml #502

Open

This was referenced Apr 8, 2026

Allow customizable metrics port #642

Merged

Expose osmohlr CTRL port for interaction #643

Closed

Allow setting network name via .env #644

Merged

support Rx and N5 interfaces at the same time #645

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

LTE NR co-existance#444

LTE NR co-existance#444
Rashed97 wants to merge 18 commits into
herlesupreeth:masterfrom
Rashed97:lte_nr_coex2

Rashed97 commented Mar 27, 2025

Uh oh!

Rashed97 commented Mar 27, 2025

Uh oh!

herlesupreeth commented Mar 28, 2025

Uh oh!

herlesupreeth left a comment

Uh oh!

herlesupreeth Mar 30, 2025

Uh oh!

herlesupreeth commented Apr 2, 2025

Uh oh!

Rashed97 commented Apr 21, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

Conversation

Rashed97 commented Mar 27, 2025

Uh oh!

Rashed97 commented Mar 27, 2025

Uh oh!

herlesupreeth commented Mar 28, 2025

Uh oh!

herlesupreeth left a comment

Choose a reason for hiding this comment

Uh oh!

herlesupreeth Mar 30, 2025

Choose a reason for hiding this comment

Uh oh!

herlesupreeth commented Apr 2, 2025

Uh oh!

Rashed97 commented Apr 21, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants