switching between different cellular carriers

[chahn-ds]

Hi,

I have a product which will be available for Verizon, T-Mobile, and AT&T.  I will have one firmware for all 3.  Do I need to set anything special for any of these carriers for these to work properly?  I realize they all have different APNs, but aside from that do I need to do anything special?  I've already tested T-Mobile and AT&T SIMs, and they works fine aside from the differences in the APNs.  

Just want to make sure before I release the firmware to production.  Don't want any surprises.

Thanks,

Chris

[Sigurd]

Hi,

I guess this was answered here:  RE: Verizon APN - do I leave it blank? 

[chahn-ds]

Hi, my original question was if there is anything I need to be concerned about aside from the different APNs.  It doesn’t seem that way, but I wanted Nordic to verify this.  Thanks.

[Hakon]

You need to also include the lwm2m carrier library when using these networks;

It is mandatory to include the LwM2M carrier library in any AT&T, T-Mobile, or Verizon certified products.

[chahn-ds]

Thanks Hakon,

LwM2M usage confuses me.  Is it for FOTA download?  I was planning on downloading new cellular modem firmware via https similar to the “full modem update” sample code.  Do I need to be able to download  cellular firmware 2 ways?   I’ve been speaking with T-Mobile and they never mentioned I needed this. Maybe they just forgot.

I just don’t know enough about how LwM2M operates with carriers.  Google searching has not helped.  Is this something that is enabled all the time?  For example, could I get LwM2M events when I’m operating normally in my device or do I somehow tell the network I’m ready for events?  I’m not sure how to integrate this into the device flow since I’m not really sure what it’s supposed to do.

Thanks for any advice,

Chris

[Hakon]

Don't think so. What makes you think you need two ways? You can check the LWM2M carrier sample in the SDK, it has support for download client.