Proprietary PSM

Question

Dear Nordic, Could you please advise how to interpret the version in this context? The modem firmware v2.X - is it the version that does not exist right now? If yes, when you are planning to release it? 
 https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.5.0/nrf/samples/cellular/lwm2m_client/sample_description.html#modem-proprietary-psm B est regards, Marcin

tesc · Accepted Answer

Hi, 
 This refers to modem firmware v2.0.0 (and later), which is only available for the nRF9161 SiP , which again is currently available for sampling to selected customers only. 
 For information on future plans and roadmaps, please contact our sales representative for your area. If you do not know who that is, please ask in a private case or private message for us to let you know, or use our sales related questions form for your future plans and roadmap questions or for more information about the nRF9161. 
 Regards, Terje

mjm987 · Answer

Answering my own question... I guess following should work to emulate a "Proprietary PSM" cycle: PSM is not supported by the active network operator if event LTE_LC_EVT_PSM_UPDATE indicates evt->psm_cfg.active_time <= 0 In this case do follwing after transmission work: Do close(server_socket) Execute lte_lc_offline () Sleep until time is reached for next transmission then: Execute lte_lc_normal() Wait (using a semaphore) until event LTE_LC_EVT_NW_REG_STATUS indicates LTE_LC_NW_REG_REGISTERED_HOME or LTE_LC_NW_REG_REGISTERED_ROAMING Then perform a socket connect (ev. getaddrinfo(), socket(), connect(), ev. setsockopt() to set recv timeout etc. And send/recv what you want. In my simple udp tests after initial setup a transmit cycle including socket reconnect and send/recv of a short frame takes ~185 mC at 3.3V whereas a send/recv in a PSM cycle (where no reconnect is needed) takes ~100 mC. During inactive period the supply current is same (12.5 uA using a nrf9160 feather module if all other periphery is set suspended). But unfortunately previous procedure is still not reliable: after going offline for power saving and reactivating by lte_lc_normal(), it often takes long for re-registering to the previously active network operator with silly switching forth and back between operators as seen here: [00:00:28.225,921] main: set_pm_resume: resume [00:00:28.225,860] main: lte_handler: LTE_LC_EVT_MODEM_SLEEP_EXIT [00:00:29.176,483] main: lte_handler: Network registration status: 2 [00:00:29.176,544] main: lte_handler: LTE cell changed: Cell ID: 12902406, Tracking area: 41300 [00:00:29.176,544] main: lte_handler: LTE_LC_EVT_LTE_MODE_UPDATE [00:00:29.258,758] main: lte_handler: RRC mode: Connected [00:00:39.677,673] main: lte_handler: RRC mode: Idle [00:01:08.447,875] main: lte_handler: LTE cell changed: Cell ID: 17154569, Tracking area: 1515 [00:01:08.521,850] main: lte_handler: RRC mode: Connected [00:01:23.481,170] main: lte_handler: RRC mode: Idle [00:01:33.592,498] main: lte_handler: RRC mode: Connected [00:01:36.087,524] main: lte_handler: RRC mode: Idle [00:01:36.138,183] main: lte_handler: LTE cell changed: Cell ID: 12902406, Tracking area: 41300 [00:01:36.220,489] main: lte_handler: RRC mode: Connected [00:01:42.614,715] main: lte_handler: Network registration status: Connected - roaming Does anybody have a better approach? Regards, Matthias

Proprietary PSM

Top Replies