10 Timers
24.0113GPPPoint-to-Point (PP) Short Message Service (SMS) support on mobile radio interfaceRelease 17TS
10.1 Timers when the MS is not using EPS services with control plane CIoT EPS optimization and not using 5GS services with control plane CIoT 5GS optimization
The present document places the following requirements on the timers described in the present document:
– timer TR1M shall be greater than 35 seconds and less than 45 seconds;
– the value of timer TRAM shall be greater than 25 seconds and less than 35 seconds;
– timer TR2M shall be greater than 12 seconds and less than 20 seconds.
10.2 Timers when the MS is using EPS services with control plane CIoT EPS optimization or using 5GS services with control plane CIoT 5GS optimization
For timer TR2M and TRAM, requirements remain the same as described in subclause 10.1.
For timer TR1M, the requirement is as follows:
– if an MS is in NB-S1 mode (see 3GPP TS 24.301 [10]) or NB-N1 mode (see 3GPP TS 24.501 [15]):
– timer TR1M shall be greater than 35+360 seconds and less than 45+360 seconds; and
– if an MS supports CE mode B and operates in WB-S1 mode in either CE mode A or CE mode B (see 3GPP TS 24.301 [10]), or operates in WB-N1 mode in either CE mode A or CE mode B (see 3GPP TS 24.501 [15]):
– timer TR1M shall be greater than 195 seconds and less than 205 seconds;
Timer TC1* typically varies with the length of the CP‑DATA:
– if an MS is in NB-S1 mode or NB-N1 mode, then for the first transmission of the CP-DATA the value of timer TC1* needs to be increased by 240 seconds from the normal value used based on the length of the CP‑DATA and for the CP-DATA retransmissions the value of timer TC1* needs to be increased by 40 seconds from normal value value; and
– if an MS supports CE mode B and operates in WB-S1 mode in either CE mode A or CE mode B, or operates in WB-N1 mode in either CE mode A or CE mode B, then the value of timer TC1* needs to be increased by 40 seconds from the normal value used based on the length of the CP‑DATA.
Annex A (informative):
Arrow diagrams
Arrow diagram A1:
The diagram shows CS MO‑message transfer by means of interlayer service primitives and the actual messages being transferred between the layer entities.
Arrow diagram A2:
The diagram shows CS MT‑messaging by means of interlayer service primitives and the actual messages being transferred between the layer entities in A/Gb mode.
Arrow diagram A5:
The diagram shows GPRS MO‑message transfer by means of interlayer service primitives and the actual messages being transferred between the layer entities.
– MNSMS‑primitives indicate services provided by CM to SM‑RL.
– LLSMS‑primitives indicate services provided by LLC to CM.
– CP‑DATA is the CM‑message carrying SM‑RP data units.
– CP‑ACK acknowledge CP‑DATA reception on CM.
Arrow diagram A6:
The diagram shows GPRS MT‑message transfer by means of interlayer service primitives and the actual messages being transferred between the layer entities in A/Gb mode.
– MNSMS‑primitives indicate services provided by CM to SM‑RL.
– LLSMS‑primitives indicate services provided by LLC to CM.
– CP‑DATA is the CM‑message carrying SM‑RP data units.
– CP‑ACK acknowledge CP‑DATA reception on CM.
Arrow diagram A7:
The diagram shows Iu mode PS MO‑message transfer by means of interlayer service primitives and the actual messages being transferred between the layer entities.
– MNSMS‑primitives indicate services provided by CM to SM‑RL.
– PMMSMS‑primitives indicate services provided by GMM to CM.
– CP‑DATA is the CM‑message carrying SM‑RP data units.
– CP‑ACK acknowledge CP‑DATA reception on CM.
Arrow diagram A8:
The diagram shows Iu mode PS MT‑messaging by means of interlayer service primitives and the actual messages being transferred between the layer entities.
– MNSMS‑primitives indicate services provided by CM to SM‑RL.
– PMMSMS‑primitives indicate services provided by GMM to CM.
– CP‑DATA is the CM‑message carrying SM‑RP data units.
– CP‑ACK acknowledge CP‑DATA reception on CM.
NOTE: Diagrams for supporting SMS through the EPS are not provided.
Arrow diagram A9:
The diagram shows if packet-switched service is used, S1 mode EPS MO‑message transfer by means of interlayer service primitives and the actual messages being transferred between the layer entities.
– MNSMS‑primitives indicate services provided by CM to SM‑RL.
– EMMSMS‑primitives indicate services provided by EMM to CM.
– CP‑DATA is the CM‑message carrying SM‑RP data units.
– CP‑ACK acknowledges CP‑DATA reception on CM.
Arrow diagram A9a:
The diagram shows if packet-switched service is used and the UE is using EPS services with control plane CIoT EPS optimization, S1 mode EPS MO‑message transfer by means of interlayer service primitives and the actual messages being transferred between the layer entities.
– MNSMS‑primitives indicate services provided by CM to SM‑RL.
– EMMSMS‑primitives indicate services provided by EMM to CM.
– CP‑DATA is the CM‑message carrying SM‑RP data units.
– CP‑ACK acknowledges CP‑DATA reception on CM.
Arrow diagram A10:
The diagram shows if packet-switched service is used, S1 mode EPS MT‑messaging by means of interlayer service primitives and the actual messages being transferred between the layer entities.
– MNSMS‑primitives indicate services provided by CM to SM‑RL.
– EMMSMS‑primitives indicate services provided by EMM to CM.
– CP‑DATA is the CM‑message carrying SM‑RP data units.
– CP‑ACK acknowledges CP‑DATA reception on CM.
Mobile Originated Messaging on CM-sublayer
Arrow diagram A1
Mobile Terminated Messaging on CM-sublayer
Arrow diagram A2
GPRS Mobile Originated Messaging on CM-sublayer in A/Gb mode
Arrow diagram A5
GPRS Mobile Terminated Messaging on CM-sublayer in A/Gb mode
Arrow diagram A6
GPRS Mobile Originated Messaging on CM-sublayer in Iu mode
NOTE: Service Request Procedure may not be initiated
Arrow diagram A7
GPRS Mobile Terminated Messaging on CM-sublayer in Iu mode
Arrow diagram A8
LTE Mobile Originated Messaging on CM-sublayer in S1 mode if packet-switched service is used
NOTE: Service Request Procedure may not be initiated if RRC connection already exists
Arrow diagram A9
LTE Mobile Originated Messaging on CM-sublayer in S1 mode if packet-switched service is used and the UE is using EPS services with control plane CIoT EPS optimization
NOTE: Service Request Procedure may not be initiated if RRC connection already exists
Arrow diagram A9a
LTE Mobile Terminated Messaging on CM-sublayer in S1 mode if packet-switched service is used
Arrow diagram A10
Annex B (normative):
SDL‑description of the CM‑layer