Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 24.501  Word version:  18.0.1

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…

 

6  Elementary procedures for 5GS session managementp. 469

6.1  Overviewp. 469

6.1.1  Generalp. 469

This clause describes the procedures used for 5GS session management (5GSM) performed over an N1 NAS signalling connection.
The main function of the 5GSM sublayer is to support the PDU session handling in the UE and in the SMF (transferred via the AMF).
The 5GSM comprises procedures for:
  • the authentication and authorization, establishment, modification and release of PDU sessions; and
  • request for performing handover of an existing PDU session between 3GPP access and non-3GPP access, or to transfer an existing PDN connection in the EPS to the 5GS.
Each PDU session represents a PDU session established between the UE and an SMF. PDU sessions can remain established even if the radio and network resources constituting the corresponding PDU session between the UE and the SMF are temporarily released.
5GSM procedures can be performed only if a 5GMM context has been established between the UE and the AMF, and the secure exchange of NAS messages has been initiated by the AMF by use of the 5GMM procedures described in clause 5. Once the UE is successfully registered to a PLMN, a PDU session can be established. If no 5GMM context has been established, the 5GMM sublayer has to initiate the establishment of a 5GMM context by use of the 5GMM procedures as described in clause 5.
The UE can request the network to modify or release PDU sessions. The network can fulfil such a request from the UE by modifying a PDU session or releasing a PDU session using network-requested procedures (see subclause 6.3).
Up

6.1.2  Types of 5GSM proceduresp. 469

Three types of 5GSM procedures can be distinguished:
  1. Procedures related to PDU sessions:
    These procedures are initiated by the network and are used for authentication and authorization or manipulation of PDU sessions:
    1. PDU authentication and authorization;
    2. network-requested PDU session modification; and
    3. network-requested PDU session release.
    This procedure is initiated by the UE and to request for establishment of PDU sessions or to perform handover of an existing PDU session between 3GPP access and non-3GPP access, or to transfer an existing PDN connection in the EPS to the 5GS:
    UE-requested PDU session establishment.
  2. Transaction related procedures:
    These procedures are initiated by the UE to request for handling of PDU sessions, i.e. to modify a PDU session, or to release a PDU session:
    1. UE-requested PDU session modification; and
    2. UE-requested PDU session release.
    This procedure is initiated by the 5G ProSe UE-to-network relay UE and is used for the manipulation of PDU sessions:
    • remote UE report.
    A successful transaction related procedure initiated by the UE triggers the network to execute one of the following procedures related to PDU session; network-requested PDU session modification procedure or network-requested PDU session release procedure. The UE treats the start of the procedure related to the PDU session as completion of the transaction related procedure.
  3. Common procedure:
    The following 5GSM procedure can be related to a PDU session or to a procedure transaction:
    5GSM status procedure.
Up

6.1.3  5GSM sublayer statesp. 470

6.1.3.1  Generalp. 470

In the following subclauses, the possible states of a PDU session in the UE and the network side are described.

6.1.3.2  5GSM sublayer states in the UEp. 470

6.1.3.2.1  Overviewp. 470
In the following subclauses, the possible 5GSM sublayer states of the UE are described and shown in Figure 6.1.3.2.1.1.
Reproduction of 3GPP TS 24.501, Fig. 6.1.3.2.1.1: The 5GSM sublayer states for PDU session handling in the UE (overview)
Up
6.1.3.2.2  PDU SESSION INACTIVEp. 471
No PDU session exists.
6.1.3.2.3  PDU SESSION ACTIVE PENDINGp. 471
The UE has initiated a PDU session establishment procedure towards the network and is waiting for a response from the network.
6.1.3.2.4  PDU SESSION ACTIVEp. 471
The PDU session is active in the UE.
6.1.3.2.5  PDU SESSION INACTIVE PENDINGp. 471
The UE has initiated a PDU session release procedure towards the network and is waiting for a response from the network.
6.1.3.2.6  PDU SESSION MODIFICATION PENDINGp. 471
The UE has initiated a PDU session modification procedure towards the network and is waiting for a response from the network.
6.1.3.2.7  PROCEDURE TRANSACTION INACTIVEp. 471
No procedure transaction exists.
6.1.3.2.8  PROCEDURE TRANSACTION PENDINGp. 471
The UE has initiated a procedure transaction towards the network.
Reproduction of 3GPP TS 24.501, Fig. 6.1.3.2.8.1: The procedure transaction states in the UE (overview)
Up

6.1.3.3  5GSM sublayer states in the network sidep. 472

6.1.3.3.1  Overviewp. 472
In the following subclauses, the possible 5GSM sublayer states of the network are described and shown in Figure 6.1.3.3.1.1.
Reproduction of 3GPP TS 24.501, Fig. 6.1.3.3.1.1: The 5GSM sublayer states for PDU session handling in the network (overview)
Up
6.1.3.3.2  PDU SESSION INACTIVEp. 472
No PDU session exists.
6.1.3.3.3  PDU SESSION ACTIVEp. 472
The PDU session is active in the network.
6.1.3.3.4  PDU SESSION INACTIVE PENDINGp. 472
The network has initiated a PDU session release procedure towards the UE and is waiting for a response from the UE.
6.1.3.3.5  PDU SESSION MODIFICATION PENDINGp. 473
The network has initiated a PDU session modification procedure towards the UE and is waiting for a response from the UE.
6.1.3.3.6  PROCEDURE TRANSACTION INACTIVEp. 473
No procedure transaction exists.
6.1.3.3.7  PROCEDURE TRANSACTION PENDINGp. 473
The network has initiated a procedure transaction towards the UE.
Reproduction of 3GPP TS 24.501, Fig. 6.1.3.3.7.1: The procedure transaction states in the network (overview)
Up

Up   Top   ToC