• State Not Answered
  • Replies 33 replies
  • Subscribers 74 subscribers
  • Views 5653 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 306873
Options

how to change Esim profile for nbiot fall back

bhanu prakash

Hi,

I'm using nrf9160custom board using sdk version 2.0.0
our Esim has 2 profiles one is for LTE and another one is for NB-IoT. Present i have tested tested LTE network and its working fine but i need to work on NB-IoT.

i have no idea how to do fallback for LTE to NB-IoT.

our Esim provider given fallback APDU command.

i have refered below document too but i don't have any how to send AT+CSIM command

https://infocenter.nordicsemi.com/index.jsp?topic=%2Fref_at_commands%2FREF%2Fat_commands%2Faccess_uicc%2Faccess_uicc.html

Thank you

Parents Reply Children
  • 0 in reply to Didrik Rokhaug

    Hi,

    Didrik Rokhaug said:
    Which modem FW version are you using?

    I'm using FW version 1.3.4 

    Didrik Rokhaug said:
    Have you tried to just set the system modem to NB-IoT or LTE-M and NB-IoT, to see if the modem handles it automatically?

    Before we using plastic sim card in that we have implemented he NB-IoT fallback and its working fine but now we are using ESIM instead of plastic sim .Now our ESIM have 2 profiles one is for LTE and another one is NB-IoT. 
    so if i need to using NB-IoT fallback first i have to change the profile. so how i can change the ESIM profile?

    our Esim providers proved APDU command for fallback. i have tried "AT+CSIM" command for fallback but i don't either it changes or not. how i can i check either it change or not?

    if you need i can provide ESIM document for your reference.

    Thank you

  • 0 in reply to bhanu prakash

    Have you tried to just configure your application to use NB-IoT to see if the modem is able to handle the profile switch itself?

  • 0 in reply to Didrik Rokhaug

    Hi,

    yes i have tried that too but its not changing the profile.

    i have tried using AT+CSIM command to change the profile  below is the which im getting while sending the AT+CSIM

    AT+CSIM=14,80C2000009D3070202018110017C
+CSIM: 4,"980A"
OK

AT+CIMI
222013096796817
OK


AT+CSIM=14,80C2000009D3070202018110017D
+CSIM: 4,"9000"
OK

AT+CIMI
204046824953132
OK


AT+CSIM=14,80C2000009D3070202018110017D
%XSIM: 0,10
%CESQ: 38,1,21,3
+CGEV: ME PDN DEACT 0
+CEREG: 0
+CIND: "service",0
+CIND: "roam",0
+CGEV: ME DETACH
+CEREG: 2,"05D7","019C4606",7
%XSIM: 1
CSIM: 4,"980A"
OK

AT+CSIM=14,80C2000009D3070202018110017C
+CSIM: 4,"9000"
OK
+CGEV: RESTR 2,2

    i don't know even its changing or not  please let me know is profile changing or not? 

    Thank you

  • 0 in reply to bhanu prakash

    Based on the log, it looks like you are able to change the IMSI.

    However, it also shows that you are using LTE-M. Is NB-IoT enabled?

    You have also activated some throttling mechanism in the network. One way to activate it is to try to attach too many times per hour, or resetting the device too many times without disconnecting properly from the network first.

    To begin with, it might be a good idea to just verify that you can attach to the NB-IoT network, by only enabling NB-IoT with AT%XSYSTEMMODE=0,1,0,0

  • 0 in reply to Didrik Rokhaug

    Hi

    Didrik Rokhaug said:
    To begin with, it might be a good idea to just verify that you can attach to the NB-IoT network, by only enabling NB-IoT with AT%XSYSTEMMODE=0,1,0,0

    in my code its already configured when LTE not available its automatically changing to nb-iot

    please see the below logs 

    [00:07:39.458,343] <dbg> lte_lc.lte_lc_system_mode_set: Sending AT command to set system mode: AT%XSYSTEMMODE=0,1,0,0
11:28:19.213 -> +CEREG: 2
11:28:20.242 -> [00:08:13.738,037] <dbg> lte_lc.at_handler: +CEREG notification: +CEREG: 2
11:28:20.242 -> 
11:28:20.242 -> [00:08:13.738,128] <err> lte_lc: Could not get tracking area code, error: -22
11:28:20.242 -> [00:08:13.738,189] <err> lte_lc: Failed to parse notification (error -22): +CEREG: 2
11:28:20.242 -> 
11:28:38.644 -> %CESQ: 36,1,7,1
11:28:38.644 -> +CEREG: 2,"C2F0","00273265",9
11:28:38.644 -> LTE cell changed: Cell ID: 2568805, Tracking area: 49904
11:28:39.622 -> [00:08:33.144,134] <dbg> lte_lc.at_handler: +CEREG notification: +CEREG: 2,"C2F0","00273265",9
11:28:39.622 -> 
11:28:41.776 -> %CESQ: 34,1,0,0
11:28:41.962 -> +CSCON: 1
11:28:41.962 -> RRC mode: Connected
11:28:42.149 -> %CESQ: 35,1,5,0
11:28:42.149 -> +CEREG: 2,"C2F0","00273265",9,0,15
11:28:42.196 -> +CSCON: 0
11:28:42.196 -> RRC mode: Idle
11:28:42.616 -> %CESQ: 255,0,255,0
11:28:42.616 -> +CEREG: 2
11:28:42.942 -> [00:08:36.482,147] <dbg> lte_lc.at_handler: +CSCON notification
11:28:42.989 -> [00:08:36.700,225] <dbg> lte_lc.at_handler: +CEREG notification: +CEREG: 2,"C2F0","00273265",9,0,15
11:28:42.989 -> 
11:28:42.989 -> [00:08:36.741,516] <dbg> lte_lc.at_handler: +CSCON notification
11:28:42.989 -> [00:08:37.156,555] <dbg> lte_lc.at_handler: +CEREG notification: +CEREG: 2
11:28:42.989 -> 
11:28:42.989 -> [00:08:37.156,646] <err> lte_lc: Could not get tracking area code, error: -22
11:28:42.989 -> [00:08:37.156,707] <err> lte_lc: Failed to parse notification (error -22): +CEREG: 2
11:28:42.989 -> 
11:28:43.084 -> %CESQ: 37,1,8,1
11:29:00.636 ->

    Thank you

Related
Terms of service