Here below a simple script shows the AT#CEDRXS functionalities. The test is performed using
a network simulator but the same can be applied on live network.
AT+CEREG?
+CEREG: 0,1
OK
AT+COPS?
+COPS: 0,0,"Test 001 01",8 The module is registered to CAT M test network
OK
AT#RFSTS
#RFSTS: "001 01",1575,-85,-65,-3.0,0001,00,,256,3,0,0000100,"001012345678901","Test
001 01",3,3,720,3240,249
OK
AT#CEDRXS? eDRX is disabled on all access technologies
#CEDRXS: 2,0,"0000","0000"
#CEDRXS: 4,0,"0000","0000"
#CEDRXS: 5,0,"0000","0000"
OK
AT#CEDRXS=1,4 eDRX enabled without specifying timings
OK
A TAU (Tracking Area Update) is triggered, values negotiation with the network starts;
the procedure is fast but we suggest to wait about 2s before proceed with next step
AT#CEDRXS?
#CEDRXS: 2,0,"0000","0000"
#CEDRXS: 4,1,"0000","0000",1,"0010","0000"
#CEDRXS: 5,0,"0000","0000"
OK
The network returns the follwing eDRX timings for the CAT M connection:
<NW_prov_eDRX> : 0010=20,48s
<NW_prov_PagTimeWindow> : 0000=1,28s
AT#CEDRXS=0,4 eDRX disabled, TAU is triggered
OK
AT#CEDRXS?
#CEDRXS: 2,0,"0000","0000"
#CEDRXS: 4,0,"0000","0000"
#CEDRXS: 5,0,"0000","0000"
OK