Kindly confirm modem details, BIP ,Refresh command support etc. as mentioned in sheet. -- Kindly let me know whether the question from the operator is clear
Kindly confirm modem details, BIP ,Refresh command support etc. as mentioned in sheet. -- Kindly let me know whether the question from the operator is clear
Hi,
We have support for generic SIM access. This includes sending APDUs, opening logical channels etc. Common SIM functions such as SIM toolkit and Bearer Intependent Protol (BIP) are supported.
You also list http/https, and TLS; which we also have support for in an application space.
Kind regards,
Håkon
Hi
Is there an open repository that demonstrates SIM-TOOLKIT over BIP?
Many thanks
Ohad
Dear Hakon,
Many thanks for this answer.
Are you an employee of Nordic?
Do you know if there is any support for the SIM-TOOLKIT by Nordic?
It is possible?
Ohad.
Hi,
Ohad Gal said:Do you know if there is any support for the SIM-TOOLKIT by Nordic?
Yes, sim toolkit is supported, but we do not have any specific sample that shows this exact usage.
The closest is the at_client, which enables the AT command set, as described in this document:
https://infocenter.nordicsemi.com/topic/ref_at_commands/REF/at_commands/intro.html?cp=2_1
Generic SIM access can be done via this AT command: https://infocenter.nordicsemi.com/topic/ref_at_commands/REF/at_commands/mob_termination_ctrl_status/csim.html?cp=2_1_4_9
What specific functionality do you need?
Kind regards,
Håkon
Hi,
With TELIT modem 3G network - there are the commands "at#stia=2,1" and "at#stta=1" that open the BIP channel and allows the SIM Card Provider to connect to the SIM and configure the cellular providers (for example to switch between AT&T and VERISON).
This is the capability we need, that is, to open the connection for a few minutes every 1 week or so, and allow the SIM provider (we use Webbing), to update as needed the IMSI
Many thanks,
Ohad.
Hi Ohad,
Yes, we support SIM provisioning from those vendors, but it is not via a AT command, but rather a carrier library:
Kind regards,
Håkon
Hi,
looks simple I think...
just call lwm2m_carrier_init() and then lwm2m_carrier_run()
but in the limitations it says: "The application should not use the NB-IoT LTE mode"
could you tell me the roadmap here? since we really need the CAT-M<-->NBIOT fallback capability
it means we can't integrate this until NB-IoT is supported...
Many thanks
Ohad.
Hi,
looks simple I think...
just call lwm2m_carrier_init() and then lwm2m_carrier_run()
but in the limitations it says: "The application should not use the NB-IoT LTE mode"
could you tell me the roadmap here? since we really need the CAT-M<-->NBIOT fallback capability
it means we can't integrate this until NB-IoT is supported...
Many thanks
Ohad.
Hi,
Unfortunately, that is not something I can answer.
If you contact your regional sales manager, he might know more about if/when that is to be certified.
If you do not have the contact details of your local RSM, please send me a direct message with your location, and I will provide you with the contact details.
Kind regards,
Håkon