search

aligungr / UERANSIM

Open source 5G UE and RAN (gNodeB) implementation.
GNU General Public License v3.0
758 stars 316 forks source link

Multiple nr-ue / "deregister switch-off" can result in ghost imsi #508

Open elrandira opened 2 years ago

elrandira commented 2 years ago

Hi,

while testing multiple attach/detach procedure, I end up with the following issue. Sometimes, calling nr-ue on an IMSI that was previously "deregister switch-off" may result in a ghost imsi staying in the data of nr-cli -d command. This "ghost" imsi when alone is not recognized by the nr-cli command and in some rare occasion, when I re-attach the IMSI, nr-cli command will still not recognize the IMSI.

Some logs: `sivlog@moonshot-siv-06:~/UERANSIM_3-2-6/build$

setup gnb

UERANSIM v3.2.6 [2022-04-05 09:19:41.033] [sctp] [info] Trying to establish SCTP connection... () [2022-04-05 09:19:41.035] [sctp] [info] SCTP connection established () [2022-04-05 09:19:41.035] [sctp] [debug] SCTP association setup ascId[66] [2022-04-05 09:19:41.036] [ngap] [debug] Sending NG Setup Request [2022-04-05 09:19:41.777] [ngap] [debug] NG Setup Response received [2022-04-05 09:19:41.777] [ngap] [info] NG Setup procedure is successful

call nr-ue -c profile_robot.yaml -n 2 -i 208900000001001

[2022-04-05 09:19:54.056] [rrc] [debug] UE[1] new signal detected [2022-04-05 09:19:54.057] [rrc] [info] RRC Setup for UE[1] [2022-04-05 09:19:54.057] [ngap] [debug] Initial NAS message received from UE[1] [2022-04-05 09:19:54.383] [ngap] [debug] Initial Context Setup Request received [2022-04-05 09:19:55.982] [ngap] [info] PDU session resource(s) setup for UE[1] count[1] [2022-04-05 09:19:57.057] [rrc] [debug] UE[2] new signal detected [2022-04-05 09:19:57.058] [rrc] [info] RRC Setup for UE[2] [2022-04-05 09:19:57.059] [ngap] [debug] Initial NAS message received from UE[2] [2022-04-05 09:19:57.478] [ngap] [debug] Initial Context Setup Request received [2022-04-05 09:19:58.680] [ngap] [info] PDU session resource(s) setup for UE[2] count[1]

sivlog@moonshot-siv-06:~/UERANSIM_3-2-6/build$ ./nr-cli -d UERANSIM-gnb-208-90-4 imsi-208900000001001 imsi-208900000001002

first switch off on 208900000001002

sivlog@moonshot-siv-06:~/UERANSIM_3-2-6/build$ ./nr-cli imsi-208900000001002 -e "deregister switch-off" De-registration procedure triggered. UE device will be switched off. [2022-04-05 09:20:38.479] [ngap] [debug] UE Context Release Command received [2022-04-05 09:20:38.479] [rrc] [info] Releasing RRC connection for UE[1] [2022-04-05 09:20:41.053] [rls] [debug] UE[1] signal lost

IMSI is still visible

sivlog@moonshot-siv-06:~/UERANSIM_3-2-6/build$ ./nr-cli -d UERANSIM-gnb-208-90-4 imsi-208900000001001 imsi-208900000001002

call nr-ue -c profile_robot.yaml -i 208900000001002

sivlog@moonshot-siv-06:~/UERANSIM_3-2-6/build$ [2022-04-05 09:20:53.735] [rrc] [debug] UE[3] new signal detected [2022-04-05 09:20:53.736] [rrc] [info] RRC Setup for UE[3] [2022-04-05 09:20:53.737] [ngap] [debug] Initial NAS message received from UE[3] [2022-04-05 09:20:54.281] [ngap] [debug] Initial Context Setup Request received

IMSI is visible twice

sivlog@moonshot-siv-06:~/UERANSIM_3-2-6/build$ ./nr-cli -d UERANSIM-gnb-208-90-4 imsi-208900000001001 imsi-208900000001002 imsi-208900000001002

This time status is accessible

sivlog@moonshot-siv-06:~/UERANSIM_3-2-6/build$ ./nr-cli imsi-208900000001002 -e status cm-state: CM-CONNECTED rm-state: RM-REGISTERED mm-state: MM-REGISTERED/NORMAL-SERVICE 5u-state: 5U1-UPDATED sim-inserted: true selected-plmn: 208/90 current-cell: 1 current-plmn: 208/90 current-tac: 1 last-tai: null stored-suci: no-identity stored-guti: no-identity has-emergency: false

sivlog@moonshot-siv-06:~/UERANSIM_3-2-6/build$ ./nr-cli -d UERANSIM-gnb-208-90-4 imsi-208900000001001 imsi-208900000001002 imsi-208900000001002

second switch off on 208900000001002

sivlog@moonshot-siv-06:~/UERANSIM_3-2-6/build$ ./nr-cli imsi-208900000001002 -e "deregister switch-off" De-registration procedure triggered. UE device will be switched off. [2022-04-05 09:21:37.733] [ngap] [debug] UE Context Release Command received [2022-04-05 09:21:37.733] [rrc] [info] Releasing RRC connection for UE[3] [2022-04-05 09:21:39.657] [rls] [debug] UE[3] signal lost

2nd call of nr-ue -c profile_robot.yaml -i 208900000001002

[2022-04-05 09:22:00.295] [rrc] [debug] UE[4] new signal detected [2022-04-05 09:22:00.297] [rrc] [info] RRC Setup for UE[4] [2022-04-05 09:22:00.297] [ngap] [debug] Initial NAS message received from UE[4] [2022-04-05 09:22:00.677] [ngap] [debug] Initial Context Setup Request received [2022-04-05 09:22:02.279] [ngap] [info] PDU session resource(s) setup for UE[4] count[1]

IMSI is still visible twice

sivlog@moonshot-siv-06:~/UERANSIM_3-2-6/build$ ./nr-cli -d UERANSIM-gnb-208-90-4 imsi-208900000001001 imsi-208900000001002 imsi-208900000001002

third switch off on 208900000001002

sivlog@moonshot-siv-06:~/UERANSIM_3-2-6/build$ ./nr-cli imsi-208900000001002 -e "deregister switch-off" De-registration procedure triggered. UE device will be switched off. [2022-04-05 09:29:48.975] [ngap] [debug] UE Context Release Command received [2022-04-05 09:29:48.976] [rrc] [info] Releasing RRC connection for UE[4] [2022-04-05 09:29:50.908] [rls] [debug] UE[4] signal lost

one copy of the IMSI is still visible

sivlog@moonshot-siv-06:~/UERANSIM_3-2-6/build$ ./nr-cli -d UERANSIM-gnb-208-90-4 imsi-208900000001001 imsi-208900000001002

sivlog@moonshot-siv-06:~/UERANSIM_3-2-6/build$ ./nr-cli imsi-208900000001002 -e "deregister switch-off" ERROR: Node not found: imsi-208900000001002 `

noormohammedli commented 2 years ago

Hello @elrandira,

From where did you get this comment "deregister switch-off"? Is there any lecture or tutorial on this? I want to leave the user register but I need to turn the tunnel TUN interface[uesimtun0, 60.60.0.1] with the IP address on or off.

Do you have an idea about this?

Thanks, Noor

elrandira commented 2 years ago

Hi noor,

i think there are some mention on the wiki. You can as well launch the nr-cli, select a registered user and type "commands" or look at the source code.

From memory, "deregister switch-off" completely deregisters the user while "deregister normal" triggers a deregister followed by a register procedure. I think there are 4 deregister options maybe you will find the one you are looking for

zbh888 commented 1 year ago

Hello @elrandira , did you figure that out?

elrandira commented 1 year ago

Hi @zbh888, no never and since I left the company I was working for when this happened :)

zbh888 commented 1 year ago

Hi @zbh888, no never and since I left the company I was working for when this happened :)

I gave up on this :)