4.9.21 Test procedure for PDU Session Release

38.508-13GPP5GSPart 1: Common test environmentRelease 17TSUser Equipment (UE) conformance specification

4.9.21.1 Scope

The purpose of this procedure is to release both the PDU session and the user plane resources.

4.9.21.2 Procedure description

4.9.21.2.1 Initial conditions

The UE is in state 3N-A with PDU SESSION ACTIVE as per Table 4.4A.2-3. If this is a UE triggered PDU Session Release, this will be specified in the test case together with the sending of a PDU SESSION RELEASE REQUEST by the UE.

4.9.21.2.2 Procedure sequence

Table 4.9.21.2.2-1: Procedure for PDU Session Release

St

Procedure

Message Sequence

U – S

Message

1

The SS transmits an RRCReconfiguration message and a PDU SESSION RELEASE COMMAND

<–

NR RRC: RRCReconfiguration

5GMM: DL NAS TRANSPORT

5GSM: PDU SESSION RELEASE COMMAND

EXCEPTION: Depending upon UE implementation, step 1A and 2 can occur in any order

1A

The UE transmits a RRCReconfigurationComplete

NR RRC: RRCReconfigurationComplete

2

The UE transmits a PDU SESSION RELEASE COMPLETE message

–>

NR RRC: ULInformationTransfer

5GMM: UL NAS TRANSPORT

5GSM: PDU SESSION RELEASE COMPLETE

4.9.21.3 Specific message contents

The NAS message contents will be as specified in the test case.

Table 4.9.21.3-1: RRCReconfiguration (step 1, Table 4.9.21.2.2-1)

Derivation Path: Table 4.6.1-13.

Information Element

Value/remark

Comment

Condition

RRCReconfiguration ::= SEQUENCE {

criticalExtensions CHOICE {

rrcReconfiguration SEQUENCE {

radioBearerConfig SEQUENCE {

drb-ToReleaseList SEQUENCE (SIZE (1..maxDRB)) OF DRB-Identity {

1 entry

DRB-Identity[1]

DRB-Identity linked to the PDU Session to be released

}

}

nonCriticalExtension SEQUENCE {

masterCellGroup SEQUENCE {

rlc-BearerToReleaseList SEQUENCE (SIZE (1..maxLC-ID)) OF LogicalChannelIdentity {

1 entry

logicalChannelIdentity[1]

Same value as drb-Identity[1] above

}

}

}

}

}

}