Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 24.501  Word version:  17.5.0

Top   Top   Up   Prev   Next
1…   3…   4…   4.4…   4.4.3…   4.5…   4.5.3…   4.6…   4.7…   4.9…   4.15…   5…   5.2…   5.3…   5.3.2…   5.3.7…   5.3.19…   5.4…   5.4.1.3…   5.4.2…   5.4.4…   5.4.5…   5.4.6…   5.5…   5.5.1.2.4   5.5.1.2.5…   5.5.1.3…   5.5.1.3.4   5.5.1.3.5…   5.5.2…   5.6…   5.6.2…   6…   6.1.4…   6.2…   6.3…   6.3.2…   6.3.3…   6.4…   6.4.1.4…   6.4.2…   6.5…   7…   8…   8.2.9…   8.3…   9…   9.11.2…   9.11.2.10…   9.11.3…   9.11.3.4…   9.11.3.8…   9.11.3.14…   9.11.3.18C…   9.11.3.29…   9.11.3.33…   9.11.3.39…   9.11.3.45…   9.11.3.50…   9.11.3.53A…   9.11.3.68…   9.11.3.75…   9.11.4…   9.11.4.10…   9.11.4.13…   9.11.4.16…   9.11.4.30…   9.12   10…   A…   B…   C…   D…   D.6…   D.6.3…

 

10  List of system parametersWord‑p. 818

10.1  GeneralWord‑p. 818

The description of timers in the following tables should be considered a brief summary. The precise details are found in clauses 4 to 6, which should be considered the definitive descriptions.

10.2  Timers of 5GS mobility managementWord‑p. 818

Timers of 5GS mobility management are shown in Table 10.2.1 and Table 10.2.2.
TIMER NUM. TIMER VALUE STATE CAUSE OF START NORMAL STOP ON EXPIRY
T3502Default 12 min.
NOTE 1
5GMM-DEREGISTERED
5GMM-REGISTERED
At registration failure and the attempt counter is equal to 5Transmission of REGISTRATION REQUEST messageInitiation of the registration procedure, if still required
T351015s
NOTE 7
NOTE 8
In WB-N1/CE mode, 85s
5GMM-REGISTERED-INITIATEDTransmission of REGISTRATION REQUEST messageREGISTRATION ACCEPT message received or REGISTRATION REJECT message receivedStart T3511 or T3502 as specified in subclause 5.5.1.2.7 if T3510 expired during registration procedure for initial registration.
Start T3511 or T3502 as specified in subclause 5.5.1.3.7 if T3510 expired during the registration procedure for mobility and periodic registration update
T351110s5GMM-DEREGISTERED.ATTEMPTING-REGISTRATION 5GMM-REGISTERED.ATTEMPTING-REGISTRATION-UPDATE
5GMM-REGISTERED.NORMAL-SERVICE or 5GMM-REGISTERED.NON-ALLOWED-SERVICE
At registration failure due to lower layer failure, T3510 timeout or registration rejected with other 5GMM cause values than those treated in subclause 5.5.1.2.5 for initial registration or subclause 5.5.1.3.5 for mobility and periodic registration Transmission of REGISTRATION REQUEST message5GMM-CONNECTED mode entered (NOTE 5)Retransmission of the REGISTRATION REQUEST, if still required
T3512Default 54 min
NOTE 1
NOTE 2
5GMM-REGISTEREDIn 5GMM-REGISTERED, when 5GMM-CONNECTED mode is left and if the NW does not indicate support for strictly periodic registration timer as specified in subclause 5.3.7.
If the network indicates support for strictly periodic registration timer, T3512 is started after the successful completion of registration update procedure. T3512 is restarted if it expires in 5GMM-CONNECTED mode as specified in subclause 5.3.7.
When entering state 5GMM-DEREGISTERED
When entering 5GMM-CONNECTED mode if the NW does not indicate support for strictly periodic registration timer as specified in subclause 5.3.7.
In 5GMM-IDLE mode, Initiation of the periodic registration procedure if the UE is not registered for emergency services.
In 5GMM-CONNECTED mode, restart the timer T3512.
Locally deregister if the UE is registered for emergency services
T351630s
NOTE 7
NOTE 8
In WB-N1/CE mode, 48s
5GMM-REGISTERED-INITIATED
5GMM-REGISTERED
5GMM-DEREGISTERED-INITIATED
5GMM-SERVICE-REQUEST-INITIATED
RAND and RES* stored as a result of an 5G authentication challengeSECURITY MODE COMMAND received SERVICE REJECT received REGISTRATION ACCEPT received AUTHENTICATION REJECT received AUTHENTICATION FAILURE sent 5GMM-DEREGISTERED, 5GMM-NULL or 5GMM-IDLE mode enteredDelete the stored RAND and RES*
T3517 (a) 5s for case h) in subclause 5.6.1.1; or
(b) 15s for cases other than h) in subclause 5.6.1.1
NOTE 7
NOTE 8
NOTE 10
In WB-N1/CE mode, 61s
5GMM-SERVICE-REQUEST-INITIATEDTransmission of SERVICE REQUEST message, or CONTROL PLANE SERVICE REQUEST message
  1. Indication from the lower layers that the UE has changed to S1 mode or E-UTRA connected to 5GCN for case h) in subclause 5.6.1.1; or
  2. SERVICE ACCEPT message received, or
SERVICE REJECT message received for cases other than h) in subclause 5.6.1.1
see subclause 5.6.1.4.2
Abort the procedure
T351960s
NOTE 7
NOTE 8
In WB-N1/CE mode, 90s
5GMM-REGISTERED-INITIATED
5GMM-REGISTERED
5GMM-DEREGISTERED-INITIATED
5GMM-SERVICE-REQUEST-INITIATED (NOTE 6)
Transmission of IDENTITY RESPONSE message, REGISTRATION REQUEST message, or DEREGISTRATION REQUEST message with freshly generated SUCIREGISTRATION ACCEPT message with new 5G-GUTI received
CONFIGURATION UPDATE COMMAND message with new 5G-GUTI received DEREGISTRATION ACCEPT message
Delete stored SUCI
T352015s
NOTE 7
NOTE 8
In WB-N1/CE mode, 33s
5GMM-REGISTERED-INITIATED
5GMM-REGISTERED
5GMM-DEREGISTERED-INITIATED
5GMM-SERVICE-REQUEST-INITIATED
Transmission of AUTHENTICATION FAILURE message with any of the 5GMM cause #20, #21, #26 or #71
Transmission of AUTHENTICATION RESPONSE message with an EAP-response message after detection of an error as described in subclause 5.4.1.2.2.4
AUTHENTICATION REQUEST message received or AUTHENTICATION REJECT message received
or
SECURITY MODE COMMAND message received
when entering 5GMM-IDLE mode
indication of transmission failure of AUTHENTICATION FAILURE message from lower layers
On first expiry during a 5G AKA based primary authentication and key agreement procedure, the UE should consider the network as false and follow item g of subclause 5.4.1.3.7, if the UE is not registered for emergency services.
On first expiry during a 5G AKA based primary authentication and key agreement procedure, the UE will follow subclause 5.4.1.3.7 under "For items c, d, e and f:", if the UE is registered for emergency services.
On first expiry during an EAP based primary authentication and key agreement procedure, the UE should consider the network as false and follow item e of subclause 5.4.1.2.4.5, if the UE is not registered for emergency services.
On first expiry during an EAP based primary authentication and key agreement procedure, the UE will follow subclause 5.4.1.2.4.5 under "For item e:", if the UE is registered for emergency services
T352115s
NOTE 7
NOTE 8
In WB-N1/CE mode, 45s
5GMM-DEREGISTERED-INITIATED Transmission of DEREGISTRATION REQUEST message when de-registration procedure is not due to a "switch off" DEREGISTRATION ACCEPT message receivedRetransmission of DEREGISTRATION REQUEST message
T3525Default 60s
NOTE 3
NOTE 7
NOTE 8
In WB-N1/CE mode, default 120s
5GMM-REGISTERED.NORMAL-SERVICE or 5GMM-REGISTERED.NON-ALLOWED-SERVICET3517 expires and service request attempt counter is greater than or equal to 5When entering state other than 5GMM-REGISTERED.NORMAL-SERVICE state or 5GMM-REGISTERED.NON-ALLOWED-SERVICE,
or
UE camped on a new PLMN other than the PLMN on which timer started,
or User-plane resources established with the network
The UE may initiate service request procedure
T354010s
NOTE 7 (applicable to case f) in subclause 5.3.1.3)
NOTE 8
In WB-N1/CE mode, 34s (applicable to case f) in subclause 5.3.1.3)
NOTE 11
5GMM-DEREGISTERED
5GMM-REGISTERED
REGISTRATION REJECT message or DEREGISTRATION REQUEST message received with any of the 5GMM cause #3, #6, #7, #11, #12, #13, #15, #27, #31, #62, #72, #73, #74, #75 or #76 SERVICE REJECT message received with any of the 5GMM cause #3, #6, #7, #11, #12, #13, #15, #27, #72, #73, #74, #75 or #76. REGISTRATION ACCEPT message received as described in subclause 5.3.1.3 case b) and case h) SERVICE ACCEPT message received as described in subclause 5.3.1.3 case f) AUTHENTICATION REJECT message received N1 NAS signalling connection released PDU sessions have been set up except for the case the UE has set Request type to "NAS signalling connection release" in the UE request type IE in the REGISTRATION REQUEST message as described in subclause 5.3.1.3 case b) Other use cases see subclause 5.3.1.3 Release the NAS signalling connection for the cases a), b), f) and g) as described in subclause 5.3.1.3
5GMM-REGISTEREDCONFIGURATION UPDATE COMMAND message received as described in subclause 5.3.1.3 case e) and h) SERVICE ACCEPT message received as described in subclause 5.3.1.3 case i) N1 NAS signalling connection released Other use cases see subclause 5.3.1.3Release the NAS signalling connection for the case e) and perform a new registration procedure as described in subclause 5.5.1.3.2
Release the NAS signalling connection for the case h) and i) as described in subclause 5.3.1.3
5GMM-DEREGISTERED
5GMM-DEREGISTERED.NORMAL-SERVICE
5GMM-REGISTERED.NON-ALLOWED-SERVICE
REGISTRATION REJECT message received with the 5GMM cause #9 or #10 SERVICE REJECT message received with the 5GMM cause #9, #10 or #28 Release the NAS signalling connection for the cases c) and d) as described in subclause 5.3.1.3 and initiation of the registration procedure as specified in subclause 5.5.1.2.2 or 5.5.1.3.2
Non-3GPP de-registration timerDefault 54 min.
NOTE 1
NOTE 2
NOTE 4
All 5GMM state over non-3GPP access except 5GMM-DEREGISTERED over non-3GPP accessEntering 5GMM-IDLE mode over non-3GPP accessN1 NAS signalling connection over non-3GPP access established or when entering state 5GMM-DEREGISTERED over non-3GPP accessImplicitly de-register the UE for non-3GPP access on 1st expiry
T3526NOTE 95GMM-DEREGISTERED 5GMM-REGISTERED Rejected S-NSSAI with rejection cause "maximum number of UEs per network slice reached" received. NoneRemove the S-NSSAI in the rejected NSSAI for the maximum number of UEs reached associated with the T3526 timer.
NOTE 1:
The value of this timer is provided by the network operator during the registration procedure.
NOTE 2:
The default value of this timer is used if the network does not indicate a value in the REGISTRATION ACCEPT message and the UE does not have a stored value for this timer.
NOTE 3:
The value of this timer is UE implementation specific, with a minimum value of 60 seconds if not in NB-N1 mode and if not in WB-N1/CE mode.
NOTE 4:
If the T3346 value received in the mobility management messages is greater than the value of the non-3GPP de-registration timer, the UE sets the non-3GPP de-registration timer value to be 4 minutes greater than the value of timer T3346.
NOTE 5:
The conditions for which this applies are described in subclause 5.5.1.3.7.
NOTE 6:
The conditions for which this applies to the 5GMM-SERVICE-REQUEST-INITIATED state are described in subclause 5.4.1.3.7 case c) and case d).
NOTE 7:
In NB-N1 mode, the timer value shall be calculated as described in subclause 4.17.
NOTE 8:
In WB-N1 mode, if the UE supports CE mode B and operates in either CE mode A or CE mode B, then the timer value is as described in this table for the case of WB-N1/CE mode (see subclause 4.19).
NOTE 9:
The value of this timer is provided by the network operator during the registration procedure or the generic UE configuration update procedure along with the rejected S-NSSAI with rejection cause "maximum number of UEs per network slice reached". The default value of this timer is implementation specific with a minimum value of 12 minutes and used if the network does not provide a value in the REGISTRATION ACCEPT message, the REGISTRATION REJECT message, or the CONFIGURATION UPDATE COMMAND message along with the rejected S-NSSAI with rejection cause "maximum number of UEs per network slice reached".
NOTE 10:
Based on implementation, the timer may be set to a value between 250ms and 15s when the MUSIM-capable UE indicates "NAS signalling connection release" in the UE request type IE of the SERVICE REQUEST message or CONTROL PLANE SERVICE REQUEST message.
NOTE 11:
Based on implementation, the timer may be set to a value between 250ms and 10s when the MUSIM capable UE not in NB-N1 mode or WB-N1 mode indicated "NAS signalling connection release" or "Rejection of paging" in the UE request type IE of the SERVICE REQUEST message or CONTROL PLANE SERVICE REQUEST message; or indicated "NAS signalling connection release" in the UE request type IE of the REGISTRATION REQUEST message.
TIMER NUM. TIMER VALUE STATE CAUSE OF START NORMAL STOP ON EXPIRY
T3513
NOTE 7
NOTE 9
NOTE 45GMM-REGISTEREDPaging procedure initiatedPaging procedure completed as specified in subclause 5.6.2.2.1Network dependent
T3522
NOTE 6
NOTE 8
6s
In WB-N1/CE mode, 24s
5GMM-DEREGISTERED-INITIATEDTransmission of DEREGISTRATION REQUEST messageDEREGISTRATION ACCEPT message receivedRetransmission of DEREGISTRATION REQUEST message
T3550
NOTE 6
NOTE 8
6s
In WB-N1/CE mode, 18s
5GMM-COMMON-PROCEDURE-INITIATEDTransmission of REGISTRATION ACCEPT message as specified in subclause 5.5.1.2.4 and 5.5.1.3.4REGISTRATION COMPLETE message receivedRetransmission of REGISTRATION ACCEPT message
T3555
NOTE 6
NOTE 8
6s
In WB-N1/CE mode, 24s
5GMM-REGISTERED Transmission of CONFIGURATION UPDATE COMMAND message with "acknowledgement requested" set in the Acknowldgement bit of the Configuration update indication IE CONFIGURATION UPDATE COMPLETE message receivedRetransmission of CONFIGURATION UPDATE COMMAND message
T3560
NOTE 6
NOTE 8
6s
In WB-N1/CE mode, 24s
5GMM-COMMON-PROCEDURE-INITIATEDTransmission of AUTHENTICATION REQUEST message Transmission of SECURITY MODE COMMAND messageAUTHENTICATION RESPONSE message received AUTHENTICATION FAILURE message received SECURITY MODE COMPLETE message received SECURITY MODE REJECT message receivedRetransmission of AUTHENTICATION REQUEST message or SECURITY MODE COMMAND message
T3565
NOTE 6
NOTE 8
6s
In WB-N1/CE mode, 24s
5GMM-REGISTEREDTransmission of NOTIFICATION messageSERVICE REQUEST message received CONTROL PLANE SERVICE REQUEST message received NOTIFICATION RESPONSE message received REGISTRATION REQUEST Message received DEREGISTRATION REQUEST message received NGAP UE context resume request message as specified in TS 38.413 receivedRetransmission of NOTIFICATION message
T3570
NOTE 6
NOTE 8
6s
In WB-N1/CE mode, 24s
5GMM-COMMON-PROCEDURE-INITIATEDTransmission of IDENTITY REQUEST messageIDENTITY RESPONSE message receivedRetransmission of IDENTITY REQUEST message
T3575
NOTE 6
NOTE 8
15s
In WB-N1/CE mode, 60s
5GMM-REGISTEREDTransmission of NETWORK SLICE-SPECIFIC AUTHENTICATION COMMAND messageNETWORK SLICE-SPECIFIC AUTHENTICATION COMPLETE message receivedRetransmission of NETWORK SLICE-SPECIFIC AUTHENTICATION COMMAND message
Active timerNOTE 10All except 5GMM-DEREGISTEREDEntering 5GMM-IDLE mode after indicating MICO mode activation to the UE with an active timer value.N1 NAS signalling connection establishedActivate MICO mode for the UE.
Implicit de-registration timerNOTE 2All except 5GMM-DEREGISTEREDThe mobile reachable timer expires while the network is in 5GMM-IDLE mode
Entering 5GMM-IDLE mode over 3GPP access if the MICO mode is activated and strictly periodic monitoring timer is not running
The strictly periodic monitoring timer expires while the network is in 5GMM-IDLE mode
N1 NAS signalling connection establishedImplicitly de-register the UE on 1st expiry
Mobile reachable timerNOTE 1 All except 5GMM-DEREGISTEREDEntering 5GMM-IDLE modeN1 NAS signalling connection establishedNetwork dependent, but typically paging is halted on 1st expiry, and start implicit de-registration timer, if the UE is not registered for emergency services.
Implicitly de-register the UE which is registered for emergency services
Non-3GPP implicit de-registration timerNOTE 3All except 5GMM-DEREGISTEREDEntering 5GMM-IDLE mode over non-3GPP accessN1 NAS signalling connection over non-3GPP access establishedImplicitly de-register the UE for non-3GPP access on 1s expiry
Strictly periodic monitoring timerNOTE 5All except 5GMM-DEREGISTEREDAt the successful completion of registration update procedure if strictly periodic registration timer indication is supported as specified in subclause 5.3.7.Entering 5GMM-DEREGISTERED.In 5GMM-IDLE mode, start implicit de-registration timer as specified in subclause 5.3.7.
In 5GMM-CONNECTED mode, Strictly periodic monitoring timer is started again as specified in subclause 5.3.7.
NOTE 1:
The default value of this timer is 4 minutes greater than the value of timer T3512. If the UE is registered for emergency services, the value of this timer is set equal to the value of timer T3512. If the T3346 value provided in the mobility management messages is greater than the value of the timer T3512, the AMF sets the mobile reachable timer and the implicit de-registration timer such that the sum of the timer values is greater than the value of timer T3346.
NOTE 2:
The value of this timer is network dependent. If MICO is activated, the default value of this timer is 4 minutes greater than the value of timer T3512.
NOTE 3:
The value of this timer is network dependent. The default value of this timer is 4 minutes greater than the non-3GPP de-registration timer. If the T3346 value provided in the mobility management messages is greater than the value of the non-3GPP de-registration timer, the AMF sets the non-3GPP implicit de-registration timer value to be 8 minutes greater than the value of timer T3346.
NOTE 4:
The value of this timer is network dependent.
NOTE 5:
The value of this timer is the same as the value of timer T3512.
NOTE 6:
In NB-N1 mode, the timer value shall be calculated as described in subclause 4.17.
NOTE 7:
In NB-N1 mode, the timer value shall be calculated by using an NAS timer value which is network dependent.
NOTE 8:
In WB-N1 mode, if the UE supports CE mode B and operates in either CE mode A or CE mode B, then the timer value is as described in this table for the case of WB-N1/CE mode (see subclause 4.19).
NOTE 9:
In WB-N1 mode, if the UE supports CE mode B, then the timer value shall be calculated by using an NAS timer value which value is network dependent.
NOTE 10:
If the AMF includes timer T3324 in the REGISTRATION ACCEPT message and if the UE is not registered for emergency services, the value of this timer is equal to the value of timer T3324.
Up

10.3  Timers of 5GS session managementWord‑p. 827

Timers of 5GS session management are shown in Table 10.3.1 and Table 10.3.2.
TIMER NUM. TIMER VALUE STATE CAUSE OF START NORMAL STOP ON THE 1st, 2nd, 3rd, 4th EXPIRY (NOTE 1)
T3580
NOTE 4
NOTE 5
16s
In WB-N1/CE mode, 24s
PDU SESSION ACTIVE PENDINGTransmission of PDU SESSION ESTABLISHMENT REQUEST messagePDU SESSION ESTABLISHMENT ACCEPT message received or PDU SESSION ESTABLISHMENT REJECT message received or PDU SESSION ESTABLISHMENT REQUEST received in a DL NAS TRANSPORT message with 5GMM cause #22, #28, #65. #67, #69, #90, #91 or #92Retransmission of PDU SESSION ESTABLISHMENT REQUEST message
T3581
NOTE 4
NOTE 5
16s
In WB-N1/CE mode, 24s
PDU SESSION MODIFICATION PENDINGTransmission of PDU SESSION MODIFICATION REQUEST messagePDU SESSION MODIFICATION COMMAND message with the same PTI is received or PDU SESSION MODIFICATION REJECT message received or PDU SESSION MODIFICATION REQUEST received in a DL NAS TRANSPORT message with 5GMM cause #22, #28. #67, #69, or #90Retransmission of PDU SESSION MODIFICATION REQUEST message
T3582
NOTE 4
NOTE 5
16s
In WB-N1/CE mode, 24s
PDU SESSION INACTIVE PENDINGTransmission of PDU SESSION RELEASE REQUEST messagePDU SESSION RELEASE COMMAND message with the same PTI is received or PDU SESSION RELEASE REJECT message receivedRetransmission of PDU SESSION RELEASE REQUEST message
T3583Default 1 min.
NOTE 2
PDU SESSION ACTIVEUE creates or updates a derived QoS ruleUE deletes the derived QoS rule (see subclause 6.2.5.1.4.5)On 1st expiry: Deletion of the derived QoS rule
T3584NOTE 3PDU SESSION ACTIVE PENDING
PDU SESSION MODIFICATION PENDING
PDU SESSION ACTIVE or PDU SESSION INACTIVE PENDING
PDU SESSION ESTABLISHMENT REJECT, PDU SESSION MODIFICATION REJECT, or PDU SESSION RELEASE COMMAND received with 5GSM cause #67 and with a timer value for T3584
PDU SESSION ESTABLISHMENT REQUEST, or PDU SESSION MODIFICATION REQUEST received in a DL NAS TRANSPORT message with 5GMM cause #67 and with a timer value for T3584 (see subclause 5.4.5.3.3)
PDU SESSION RELEASE COMMAND (see NOTE 6) or PDU SESSION MODIFICATION COMMAND or PDU SESSION AUTHENTICATION COMMAND or DEREGISTRATION REQUEST with the re-registration type "re-registration required" None
T3585NOTE 3PDU SESSION ACTIVE PENDING
PDU SESSION MODIFICATION PENDING
PDU SESSION ACTIVE or PDU SESSION INACTIVE PENDING
PDU SESSION ESTABLISHMENT REJECT, PDU SESSION MODIFICATION REJECT, or PDU SESSION RELEASE COMMAND received with 5GSM cause #69 and with a timer value for T3585
PDU SESSION ESTABLISHMENT REQUEST, or PDU SESSION MODIFICATION REQUEST received in a DL NAS TRANSPORT message with 5GMM cause #69 and with a timer value for T3585(see subclause 5.4.5.3.3)
PDU SESSION RELEASE COMMAND (see NOTE 6) or PDU SESSION MODIFICATION COMMAND or PDU SESSION AUTHENTICATION COMMAND or DEREGISTRATION REQUEST with the re-registration type "re-registration required" None
Back-off timerdefined in TS 24.008
T35xx
NOTE 4
NOTE 5
8s
In WB-N1/CE mode, 16s
PDU SESSION ACTIVEREMOTE UE REPORT sentREMOTE UE REPORT RESPONSE receivedRetransmission of REMOTE UE REPORT
NOTE 1:
Typically, the procedures are aborted on the fifth expiry of the relevant timer. Exceptions are described in the corresponding procedure description.
NOTE 2:
The network may provide the value of this timer applicable to the derived QoS rules of a specific PDU session as RQ timer value in the PDU SESSION ESTABLISHMENT ACCEPT message and PDU SESSION MODIFICATION COMMAND message. The maximum value of the timer is 30 min. If the network indicates a value greater than the maximum value, then the UE shall use the maximum value.
NOTE 3:
The value of this timer is provided by the network.
NOTE 4:
In NB-N1 mode, then the timer value shall be calculated as described in subclause 4.18.
NOTE 5:
In WB-N1 mode, if the UE supports CE mode B and operates in either CE mode A or CE mode B, then the timer value is as described in this Table for the case of WB-N1/CE mode (see subclause 4.20).
NOTE 6:
If the PDU SESSION RELEASE COMMAND message includes the Back-off timer value IE where the timer value indicates neither zero nor deactivated and the 5GSM cause is not #39, the UE then starts the timer with the value provided in the Back-off timer value IE after stopping the existing timer (see subclause 6.3.3.3).
TIMER NUM. TIMER VALUE STATE CAUSE OF START NORMAL STOP ON THE 1st, 2nd, 3rd, 4th EXPIRY (NOTE 1)
T3590
NOTE 3
NOTE 4
15s
In WB-N1/CE mode, 23s
PROCEDURE TRANSACTION PENDINGTransmission of PDU SESSION AUTHENTICATION COMMAND messagePDU SESSION AUTHENTICATION COMPLETE message receivedRetransmission of PDU SESSION AUTHENTICATION COMMAND message
T3591
NOTE 3
NOTE 4
16s
In WB-N1/CE mode, 24s
PDU SESSION MODIFICATION PENDINGTransmission of PDU SESSION MODIFICATION COMMAND messagePDU SESSION MODIFICATION COMPLETE message received or PDU SESSION MODIFICATION COMMAND REJECT message receivedRetransmission of PDU SESSION MODIFICATION COMMAND message
T3592
NOTE 3
NOTE 4
16s
In WB-N1/CE mode, 24s
PDU SESSION INACTIVE PENDINGTransmission of PDU SESSION RELEASE COMMAND messagePDU SESSION RELEASE COMPLETE message received or N1 SM delivery skipped indication receivedRetransmission of PDU SESSION RELEASE COMMAND message
T3593
NOTE 3
NOTE 4
Default 60s (NOTE 2)PDU SESSION MODIFICATION PENDINGReception of PDU SESSION MODIFICATION COMPLETE message for transmitted PDU SESSION MODIFICATION COMMAND message where the PDU SESSION MODIFICATION COMMAND message included 5GSM cause #39PDU SESSION RELEASE REQUEST message receivedNetwork-requested PDU session release procedure performed
NOTE 1:
Typically, the procedures are aborted on the fifth expiry of the relevant timer. Exceptions are described in the corresponding procedure description.
NOTE 2:
If the PDU Session Address Lifetime value is sent to the UE in the PDU SESSION MODIFICATION COMMAND message then timer T3593 shall be started with the same value, otherwise it shall use a default value.
NOTE 3:
In NB-N1 mode, the timer value shall be calculated as described in subclause 4.18.
NOTE 4:
In WB-N1 mode, if the UE supports CE mode B and operates in either CE mode A or CE mode B, then the timer value is as described in this Table for the case of WB-N1/CE mode (see subclause 4.20).
Up

10.4  Timers of Multicast/Broadcast Services |R17|Word‑p. 831


Up   Top   ToC