TestRegistration Failed when changing the UeID

I am trying to use my own ueID in the TestRegistration.
With an architecture of AWS, Python Flask,
I was able to pass my ueID as simulating UEs as AWS Lambda.
When I passed ueID to the flask server on the same VM as free5gc implemented, I run this command: os.system('./test.sh {} {}' .format('TestRegistration', ueID))
And set it as the environment variable in test.sh with: export ueID=$2
Which runs successfully when I print the ueID in registration_test.go with getting the environment variables with: var ueID string = os.Getenv("ueID"), it is also success when I run some self-made function inside registration_test.go as passing the variable back to AWS to do other things.

But when I change the value of “imsi-2089300007487” in this command
ue := test.NewRanUeContext(ueID, 1, security.AlgCiphering128NEA0, security.AlgIntegrity128NIA2)
I also change the servingPlmnId while my environment is based on ChungHua Telecom as 46692

After doing all these settings, the ueID sure did pass over to the server, but the test will failed as the picture below, is it possible that I need to change every Supi in every file?

After switching back to “imsi-2089300007487” the test will pass, but sometimes the kernel will panic while deleting the DNN.

The environment settings:
free5gc server:

  • EC2
    • t2.xlarge: 4 vCPUs, Memory 16 GiB, Hard Drive 160 GB as EBS

Fu Jen Catholic University
Department of Information Management
William Lin
[email protected]

Hello,
I have the same issues.
I am trying to add 2 UE with different 2 ueID in the TestRegistration and add another the snssai as well but the test fail.
I tried to edit 2089300007487 in all functions and in other files but i get error.
Did you manage to solve the problem?

Thanks

Hi @katreenallord, still trying I will update if I solved it.

Hi williamlin0504,
Your error is “NAS message integrity check failded”.
Here will check NAS mac is same or not, and NAS mac is calculated by other keys.
One of keys is Kamf which is derived from supi.
Due to you change the supi in the file. However, the supi in the DB is may still old one. This may occur this error you encountered.
I think you can try to delete the mongoDB and test again.

Hi @Jim, thanks I will try it and report here.