Content for  TS 29.502  Word version:  18.5.0

6.1.6.3.1  Introduction  p. 261

6.1.6.3.2  Simple data types  p. 261

Type Name	Type Definition	Description
ProcedureTransactionId	integer	Unsigned integer representing a Procedure Transaction Identity, within the range 0 to 255, as specified in TS 24.007.
EpsBearerId	integer	Integer identifying an EPS bearer, within the range 0 to 15, as specified in clause 11.2.3.1.5, bits 5 to 8, of TS 24.007.
EpsPdnCnxContainer	string	String with format "byte" as defined in OpenAPI Specification [15], i.e. base64-encoded characters, encoding the UeEpsPdnConnection IE specified in Table 7.3.1-2 or Table 7.3.6-2 of TS 29.274 for the N26 interface.
EpsBearerContainer	string	String with format "byte" as defined in OpenAPI Specification [15], i.e. base64-encoded characters, encoding the Bearer Context IE specified in Table 7.3.2-2 of TS 29.274.
Teid	string	4-octet GTP tunnel endpoint identifier, as defined in TS 29.274, in hexadecimal representation. Each character in the string shall take a value of "0" to "9" or "a" to "f" or "A" to "F" and shall represent 4 bits. The most significant character representing the 4 most significant bits of the TEID shall appear first in the string, and the character representing the 4 least significant bit of the TEID shall appear last in the string. Pattern: "^[A-Fa-f0-9]{8}" Example: A GTP TEID 0x5BD60076 shall be encoded as "5BD60076".
EpsBearerContextStatus	string	EPS bearer context status, as defined in octets 3 and 4 of the EPS bearer context status IE in clause 9.9.2.1 of TS 24.301, in hexadecimal representation. Each character in the string shall take a value of "0" to "9" or "a" to "f" or "A" to "F" and shall represent 4 bits. The most significant character representing the 4 most significant bits of the EPS bearer context status shall appear first in the string, and the character representing the 4 least significant bit of the EPS bearer context status shall appear last in the string. Pattern: '^[A-Fa-f0-9]{4}$' Example: An EPS bearer context status IE where only the EBIs 2, 5, 6 and 9 are active shall be encoded as "6402".
DrbId	integer	Unsigned integer representing a Data Radio Bearer Identity, within the range 1 to 32, as specified in clause 9.3.1.53 of TS 38.413.
AdditionalTnlNb	integer	Unsigned integer, within the range 1 to 3, indicating whether this is the first, second or third additional indirect data forwarding tunnel for multi-connectivity.
ForwardingBearerContainer	string	String with format "byte" as defined in OpenAPI Specification [15], i.e. base64-encoded characters, encoding the Bearer Context IE within Context Acknowledge specified in Table 7.3.7-2 of TS 29.274.
SecondaryRatUsageDataReportContainer	string	String with format "byte" as defined in OpenAPI Specification [15], i.e. base64-encoded characters, encoding the Secondary RAT Usage Data Report IE within Forward Relocation Complete Acknowledge specified in Table 7.3.4-1 of TS 29.274 (starting from octet 1).

6.1.6.3.3  Enumeration: UpCnxState  p. 262

Enumeration value	Description
"ACTIVATED"	A N3 tunnel is established between the 5G-AN and UPF.
"DEACTIVATED"	No N3 tunnel is established between the 5G-AN and UPF.
"ACTIVATING"	A N3 tunnel is being established (the 5G-AN's F-TEID for downlink traffic is not assigned yet).
"SUSPENDED"	A N3 tunnel is suspended between the 5G-AN and UPF.

6.1.6.3.4  Enumeration: HoState  p. 263

Enumeration value	Description
"NONE"	No handover is in progress for the PDU session.
"PREPARING"	A handover is in preparation for the PDU session; see clause 5.2.2.3.4.1.
"PREPARED"	A handover is prepared for the PDU session; see clause 5.2.2.3.4.1.
"COMPLETED"	The handover is completed.
"CANCELLED"	The handover is cancelled.

6.1.6.3.5  Enumeration: RequestType  p. 263

Enumeration value	Description
"INITIAL_REQUEST"	Request to establish a new PDU session.
"EXISTING_PDU_SESSION"	Request referring to an existing PDU session.
"INITIAL_EMERGENCY_REQUEST"	Request to establish a new PDU session for Emergency Services.
"EXISTING_EMERGENCY_PDU_SESSION"	Request referring to an existing PDU session for Emergency Services.
NOTE: Clause 9.11.3.47 of TS 24.501 defines a specific Request type value in NAS PDUs for a MA PDU request. This shall be mapped to the maRequestInd attribute in the Create SM Context Request, Update SM Context Request, Create Request and Update Request. Accordingly, no corresponding value is defined in the RequestType enumeration.

6.1.6.3.6  Enumeration: RequestIndication  p. 263

Enumeration value	Description
"UE_REQ_PDU_SES_MOD"	UE Requested PDU Session Modification
"UE_REQ_PDU_SES_REL"	UE Requested PDU Session Release
"PDU_SES_MOB"	PDU Session Mobility (e.g. between 3GPP and non-3GPP access, or from EPS to 5GS with N26 interface)
"NW_REQ_PDU_SES_AUTH"	Network Requested PDU Session Authentication. This value is used for the procedures with a secondary authorization/ authentication in an Update request initiated by an H-SMF/SMF during e.g. the PDU Session establishment procedure to inform the V-SMF/I-SMF that the H-SMF/SMF decided to initiate the optional PDU Session establishment authentication/authorization procedure (see clause 4.3.2.3 in TS 23.502).
"NW_REQ_PDU_SES_MOD"	Network Requested PDU Session Modification
"NW_REQ_PDU_SES_REL"	Network Requested PDU Session Release
"EBI_ASSIGNMENT_REQ"	EPS Bearer ID Assignment Request or EPS Bearer ID Revocation Request
"REL_DUE_TO_5G_AN_REQUEST"	5G-AN Requested PDU Session Resource Release

6.1.6.3.7  Enumeration: NotificationCause  p. 264

Enumeration value	Description
"QOS_FULFILLED"	The QoS targets are fulfilled again for the GBR QoS flow.
"QOS_NOT_FULFILLED"	The QoS targets are no longer fulfilled for the GBR QoS flow.
"UP_SEC_FULFILLED"	The user plane security enforcement "Preferred" is fulfilled again for the PDU session.
"UP_SEC_NOT_FULFILLED"	The user plane security enforcement "Preferred" is not fulfilled for the PDU session.

6.1.6.3.8  Enumeration: Cause  p. 264

Enumeration value	Description
"REL_DUE_TO_HO"	Release due to Handover
"EPS_FALLBACK"	Mobility due to EPS fallback for IMS voice is on-going.
"REL_DUE_TO_UP_SEC"	Release due to user plane Security requirements that cannot be fulfilled.
"DNN_CONGESTION"	Release due to the DNN based congestion control.
"S_NSSAI_CONGESTION"	Release due to the S-NSSAI based congestion control.
"REL_DUE_TO_REACTIVATION"	Release due to PDU session reactivation.
"5G_AN_NOT_RESPONDING"	The 5G AN did not respond to the request initiated by the network.
"REL_DUE_TO_SLICE_NOT_AVAILABLE"	Release due to the associated S-NSSAI becomes no longer available (e.g. the validity time of the S-NSSAI expires, or the S-NSSAI is decommissioned, etc.).
"REL_DUE_TO_DUPLICATE_SESSION_ID"	Release due to a UE request to establish a new PDU session with an identical PDU session Id.
"PDU_SESSION_STATUS_MISMATCH"	Release due to mismatch of PDU Session status between UE and AMF.
"HO_FAILURE"	Handover preparation failure
"INSUFFICIENT_UP_RESOURCES"	Failure to activate the User Plane connection of a PDU session due to insufficient user plane resources.
"PDU_SESSION_HANDED_OVER"	The PDU session is handed over to another system or access.
"PDU_SESSION_RESUMED"	Resume the user plane connection of the PDU session.
"CN_ASSISTED_RAN_PARAMETER_TUNING"	SMF derived CN assisted RAN parameters tuning.
"ISMF_ CONTEXT_TRANSFER"	The PDU session shall be transferred from old I-SMF to new I-SMF.
"SMF_ CONTEXT_TRANSFER"	The PDU session shall be transferred from old SMF to new SMF.
"REL_DUE_TO_PS_TO_CS_HO"	Release due to 5G SRVCC from NG-RAN to 3GPP UTRAN, as specified in clause 6.5.4 of TS 23.216.
"REL_DUE_TO_SUBSCRIPTION_CHANGE"	PDU session release due to UE subscription changes, triggered by the SMF e.g. due to the removal of subscribed DNNs, or by the AMF e.g. due to ODB changes.
"HO_CANCEL"	Handover cancellation
"REL_DUE_TO_SLICE_NOT_AUTHORIZED"	Release due to Network Slice-Specific Authentication and Authorization failure or revocation.
"PDU_SESSION_HAND_OVER_FAILURE"	Failure to handover PDU session to another access
"DDN_FAILURE_STATUS"	DDN failure status reporting
"REL_DUE_TO_CP_ONLY_NOT_APPLICABLE"	Release due to Control Plane Only indication associated with PDU Session is not applicable any longer
"NOT_SUPPORTED_WITH_ISMF"	PDU session release due to a requested functionality that is not supported for a PDU session with an I-SMF/V-SMF.
"CHANGED_ANCHOR_SMF"	The anchor SMF of the PDU session is changed.
"CHANGED_INTERMEDIATE_SMF"	The intermediate SMF (e.g. I-SMF or V-SMF) is changed.
"TARGET_DNAI_NOTIFICATION"	Notify the target DNAI for I-SMF selection for the current PDU Session, or SMF selection during PDU Session re-establishment for SSC mode 2/3.
"REL_DUE_TO_VPLMN_QOS_FAILURE"	Release due to QoS not complying with VPLMN QoS constraints, i.e. VPLMN QoS constraints are required for the PDU session and the H-SMF provides QoS parameters not complying with VPLMN QoS required by the V-SMF.
"REL_DUE_TO_SMF_NOT_SUPPORT_PSETR"	Release the PDU session due to the (H-)SMF does not support the PSETR feature when the V/I-SMF has failed.
"REL_DUE_TO_SNPN_SNPN_MOBILITY"	Release due to the PDU session is rejected by the new AMF during registration procedure as the continuity of the PDU Session cannot be supported between networks with SNPN-SNPN mobility.
"REL_DUE_TO_NO_HR_AGREEMENT"	Release due to the PDU session is rejected by the new AMF during registration procedure as the continuity of the PDU Session cannot be supported between networks with inter-PLMN mobility where no HR agreement exists.
"REL_DUE_TO_SNSSAI_DENIED"	Release due to the subscriber does not have the necessary subscription to access the SNSSAI.
"REL_DUE_TO_DNN_DENIED"	Release due to the subscriber does not have the necessary subscription to access the DNN.
"REL_DUE_TO_PDUTYPE_DENIED"	Release due to the subscriber does not have the necessary subscription for the requested PDU session type.
"REL_DUE_TO_SSC_DENIED"	Release due to the subscriber does not have the necessary subscription for the requested SSC mode.
"REL_DUE_TO_SUBSCRIPTION_DENIED"	Release due to an error, other than those listed in this table, due to lack of necessary subscription to serve the UE request.
"REL_DUE_TO_DNN_NOT_SUPPORTED"	Release due to the DNN is not supported by the SMF.
"REL_DUE_TO_PDUTYPE_NOT_SUPPORTED"	Release due to the requested PDU session type is not supported by the SMF for the PDN corresponding to the DNN.
"REL_DUE_TO_SSC_NOT_SUPPORTED"	Release due to the requested SSC mode is not supported by the SMF for the PDN corresponding to the DNN.
"REL_DUE_TO_INSUFFICIENT_RESOURCES_SLICE"	Release due to insufficient resources for the specific slice.
"REL_DUE_TO_INSUFFICIENT_RESOURCES_SLICE_DNN"	Release due to insufficient resources for the specific slice and DNN.
"REL_DUE_TO_DNN_CONGESTION"	The SMF has detected congestion for the requested DNN and performs overload control for that DNN which does not allow the PDU session to be established.
"REL_DUE_TO_S_NSSAI_CONGESTION"	The SMF has detected congestion for the requested S-NSSAI and performs overload control for that S-NSSAI which does not allow the PDU session to be established.
"REL_DUE_TO_PEER_NOT_RESPONDING"	No response is received from a remote peer, or the remote peer is known to be not reachable, e.g. to indicate that no response has been received from the H-SMF for a HR PDU session or the SMF for a PDU session with I-SMF.
"REL_DUE_TO_NETWORK_FAILURE"	The request is rejected due to a network problem.
"REL_DUE_TO_UPF_NOT_RESPONDING"	The request is rejected due to no response received from the UPF.
"REL_DUE_TO_NO_EPS_5GS_CONTINUITY"	It is used during an EPS to 5GS Idle mode mobility or handover, if the PDU session does not support seamless session continuity to 5GS.
"REL_DUE_TO_NOT_SUPPORTED_WITH_ISMF"	The request is rejected due to a requested functionality that is not supported for a PDU session with an I-SMF/V-SMF.
"REL_DUE_TO_EXCEEDED_UE_SLICE_DATA_RATE"	The request is rejected due to the maximum bit rate per S-NSSAI per UE is exceeded, when the SMF receives the same application error from the PCF.
"REL_DUE_TO_EXCEEDED_SLICE_DATA_RATE"	The request is rejected due to the maximum bit rate per S-NSSAI is exceeded, when the SMF receives the same application error from the PCF.
"REL_DUE_TO_CONTEXT_NOT_FOUND"	It is used when no context corresponding to the request exists in the SMF.
"REL_DUE_TO_UNSPECIFIED_REASON"	Release due to unspecified reasons.
"REL_DUE_TO_MOB_ACCESS_RESTRICTIONS"	Release due to Mobility Restrictions or Access Restrictions (e.g. CAG restrictions).
"REL_DUE_TO_SLICE_INACTIVITY"	Release due to slice inactivity (i.e. slice-specific inactivity period for the PDU session expires), as specified in clause 5.15.15.3 of TS 23.501 and clause 5.11.2 of TS 29.244.
"REL_DUE_TO_NSI_NOT_AVAILABLE"	Release due to the associated Network Slice Instance is congested or not available, as specified in clause 5.2.16.3.3 of TS 23.502.
"REL_DUE_TO_MBSR_NOT_AUTHORIZED"	Release due to the MBSR authorization status is changed from "authorized" to "not authorized".
"DEACT_DUE_TO_UE_OUT_OF_SLICE_SUPPORT_AREA"	User Plane deactivation due to the UE moving out of the network slice area of support or availability, as specified in clause 4.3.7 of TS 23.502.
"REJECT_DUE_TO_N1_SM_ERROR"	The PDU Session is rejected due to N1 SM Error, e.g. PDU session establishment rejected due to Operator Determined Barring.

6.1.6.3.9  Enumeration: ResourceStatus  p. 268

Enumeration value	Description	Applicability
"RELEASED"	The SM context or PDU session resource is released.
"UNCHANGED"	The status of SM context or PDU session resource is not changed.
"TRANSFERRED"	The SM context shall be transferred.
"UPDATED"	The SM context or PDU session resource context has changed: The access type of PDU session is changed. The anchor SMF (H-SMF or SMF) or intermediate SMF (I-SMF or V-SMF) has changed within the SMF set. The SM context with the I-SMF in the source access needs to be released but without releasing the PDU session in the AMF (see clauses 5.2.2.5.1 and 5.2.2.10.1).	HOFAIL ES3XX DTSSA
"ALT_ANCHOR_SMF"	The V-SMF has established the PDU session towards an alternative H-SMF during PDU session establishment for HR PDU session, as specified in clause 4.3.2.2.2 of TS 23.502, or the I-SMF has established the PDU session towards an alternative SMF during PDU session establishment for a PDU session with I-SMF (see clause 4.23.5.1 of TS 23.502).	AASN

6.1.6.3.10  Enumeration: DnnSelectionMode  p. 269

Enumeration value	Description
"VERIFIED"	UE or network provided DNN is authorized based on the explicitly subscribed DNN, subscription verified
"UE_DNN_NOT_VERIFIED"	UE provided DNN is authorized based on the wildcard DNN, subscription not verified
"NW_DNN_NOT_VERIFIED"	Network provided DNN is authorized based on the wildcard DNN, subscription not verified

6.1.6.3.11  Enumeration: EpsInterworkingIndication  p. 269

Enumeration value	Description
"NONE"	The PDU session cannot be moved EPS. (NOTE)
"WITH_N26"	The PDU session may possibly be moved to EPS, with N26 interface supported during EPS interworking procedures. This may correspond to: a PDU session or an MA-PDU session with a 3GPP access; or a MA PDU Session with a non-3GPP access for a UE registered to the same PLMN over both 3GPP and non-3GPP accesses, i.e. served by the same AMF for both accesses.
"WITHOUT_N26"	The PDU session may possibly be moved to EPS, without N26 interface supported during EPS interworking procedures. This may correspond to: a PDU session or an MA-PDU session with a 3GPP access; or a MA PDU Session with a non-3GPP access for a UE registered to the same PLMN over both 3GPP and non-3GPP accesses, i.e. served by the same AMF for both accesses.
"IWK_NON_3GPP"	The PDU session via non-3GPP access may possibly be moved to EPS.
NOTE: Handover from 5GS to EPC/ePDG (as specified in clause 4.11.4.2 of TS 23.502) shall be considered as allowed if the value of EpsInterworkingIndication is not set to "NONE" and if such handover is allowed based on operator's policy.

6.1.6.3.12  Enumeration: N2SmInfoType  p. 270

Enumeration value	Description
"PDU_RES_SETUP_REQ"	PDU Session Resource Setup Request Transfer
"PDU_RES_SETUP_RSP"	PDU Session Resource Setup Response Transfer
"PDU_RES_SETUP_FAIL"	PDU Session Resource Setup Unsuccessful Transfer
"PDU_RES_REL_CMD"	PDU Session Resource Release Command Transfer
"PDU_RES_REL_RSP"	PDU Session Resource Release Response Transfer
"PDU_RES_MOD_REQ"	PDU Session Resource Modify Request Transfer
"PDU_RES_MOD_RSP"	PDU Session Resource Modify Response Transfer
"PDU_RES_MOD_FAIL"	PDU Session Resource Modify Unsuccessful Transfer
"PDU_RES_NTY"	PDU Session Resource Notify Transfer
"PDU_RES_NTY_REL"	PDU Session Resource Notify Released Transfer
"PDU_RES_MOD_IND"	PDU Session Resource Modify Indication Transfer
"PDU_RES_MOD_CFM"	PDU Session Resource Modify Confirm Transfer
"PATH_SWITCH_REQ"	Path Switch Request Transfer
"PATH_SWITCH_SETUP_FAIL"	Path Switch Request Setup Failed Transfer
"PATH_SWITCH_REQ_ACK"	Path Switch Request Acknowledge Transfer
"PATH_SWITCH_REQ_FAIL"	Path Switch Request Unsuccessful Transfer
"HANDOVER_REQUIRED"	Handover Required Transfer
"HANDOVER_CMD"	Handover Command Transfer
"HANDOVER_PREP_FAIL"	Handover Preparation Unsuccessful Transfer
"HANDOVER_REQ_ACK"	Handover Request Acknowledge Transfer
"HANDOVER_RES_ALLOC_FAIL"	Handover Resource Allocation Unsuccessful Transfer
"SECONDARY_RAT_USAGE"	Secondary RAT Data Usage Report Transfer
"PDU_RES_MOD_IND_FAIL"	PDU Session Resource Modify Indication Unsuccessful Transfer
"UE_CONTEXT_RESUME_REQ"	UE Context Resume Request Transfer
"UE_CONTEXT_RESUME_RSP"	UE Context Resume Response Transfer
"UE_CONTEXT_SUSPEND_REQ	UE Context Suspend Request Transfer

6.1.6.3.13  Enumeration: MaxIntegrityProtectedDataRate  p. 271

Enumeration value	Description
"64_KBPS"	64 kbps
"MAX_UE_RATE"	Full data rate

6.1.6.3.14  Enumeration: MaReleaseIndication |R16|  p. 271

Enumeration value	Description
"REL_MAPDU_OVER_3GPP"	The MA PDU session over 3GPP access is to be released or has been released.
"REL_MAPDU_OVER_N3GPP"	The MA PDU session over Non-3GPP access is to be released or has been released.

6.1.6.3.15  Enumeration: SmContextType |R16|  p. 271

Enumeration value	Description
"EPS_PDN_CONNECTION"	UE EPS PDN Connection.
"SM_CONTEXT"	Complete SM Context (i.e. 5G SM context including EPS context information as defined in clause 6.1.6.2.39)
"AF_COORDINATION_INFO"	AF Coordination Information

6.1.6.3.16  Enumeration: PsaIndication |R16|  p. 271

Enumeration value	Description
"PSA_INSERTED"	A PSA and UL CL or BP has been inserted into the data path of the PDU session.
"PSA_REMOVED"	A PSA and UL CL or BP has been removed from the data path of the PDU session.
"PSA_INSERTED_ONLY"	A PSA has been inserted into the data path of the PDU session and the UL CL or BP is not changed.
"PSA_REMOVED_ONLY"	A PSA has been removed from the data path of the PDU session and the UL CL or BP is not changed.

6.1.6.3.17  Enumeration: N4MessageType |R16|  p. 271

Enumeration value	Description
"PFCP_SES_EST_REQ"	PFCP Session Establishment Request
"PFCP_SES_EST_RSP"	PFCP Session Establishment Response
"PFCP_SES_MOD_REQ"	PFCP Session Modification Request
"PFCP_SES_MOD_RSP"	PFCP Session Modification Response
"PFCP_SES_DEL_REQ"	PFCP Session Deletion Request
"PFCP_SES_DEL_RSP"	PFCP Session Deletion Response
"PFCP_SES_REP_REQ"	PFCP Session Report Request
"PFCP_SES_REP_RSP"	PFCP Session Report Response

6.1.6.3.18  Enumeration: QosFlowAccessType |R16|  p. 272

Enumeration value	Description
"3GPP"	The QoS Flow is only associated with 3GPP access.
"NON_3GPP"	The QoS Flow is only associated with Non-3GPP access.
"3GPP_AND_NON_3GPP"	The QoS Flow is associated with both 3GPP access and Non-3GPP access.

6.1.6.3.19  Enumeration: UnavailableAccessIndication |R16|  p. 272

Enumeration value	Description
"3GA_UNAVAILABLE"	The 3GPP access of the MA PDU session is unavailable.
"N3GA_UNAVAILABLE"	The Non-3GPP access of the MA PDU session is unavailable.

6.1.6.3.20  Enumeration: ProtectionResult |R16|  p. 272

Enumeration value	Description
"PERFORMED"	The security policy indicated as "preferred" is performed
"NOT_PERFORMED"	The security policy indicated as "preferred" is not performed

6.1.6.3.21  Enumeration: QosMonitoringReq |R16|  p. 272

Enumeration value	Description
"UL"	Measurement of UL delay.
"DL"	Measurement of DL delay.
"BOTH"	Measurement of both UL/DL delays.
"NONE"	No measurements are required. This value shall be used to stop on-going UL and/or DL measurements.

6.1.6.3.22  Enumeration: Rsn |R16|  p. 273

Enumeration value	Description
"V1"	V1
"V2"	V2
"NONE"	This value indicates that no RSN value is available (NOTE)
NOTE: This value shall be used in a Create Request if a PDU Session Pair ID was received from the UE without an RSN value.

6.1.6.3.23  Enumeration: SmfSelectionType |R17|  p. 273

Enumeration value	Description
"CURRENT_PDU_SESSION"	I-SMF selection or removal for the current PDU Session.
"NEXT_PDU_SESSION"	SMF selection for the next PDU Session, i.e. the re-established PDU session for SSC mode 2/3.

6.1.6.3.24  Enumeration: PduSessionContextType |R17|  p. 273

Enumeration value	Description
"AF_COORDINATION_INFO"	AF Coordination Information

6.1.6.3.25  Enumeration: PendingUpdateInfo |R18|  p. 273

Enumeration value	Description
"UE_LOCATION"	UE Location
"TIMEZONE"	Timezone
"ACCESS_TYPE"	Access Type
"RAT_TYPE"	Radio Access Type
"AMF_ID"	Serving AMF Identifier

6.1.6.3.26  Enumeration: EstablishmentRejectionCause |R18|  p. 273

Enumeration value	Description
"OPERATOR_DETERMINED_BARRING"	PDU Session Establishment to be rejected due to Operator Determined Barring.

6.1.6.3.27  Enumeration: EcnMarkingReq |R18|  p. 274

Enumeration value	Description	Applicability
UL	ECN marking for L4S for the UL.
DL	ECN marking for L4S for the DL.
BOTH	ECN marking for L4S for the UL and the DL.
STOP	Stop ECN marking for L4S.

6.1.6.3.28  Enumeration: CongestionInfoReq |R18|  p. 274

Enumeration value	Description	Applicability
UL	Indicates to NG-RAN to report the congestion information of the QoS Flow on UL direction.
DL	Indicates to NG-RAN to report the congestion information of the QoS Flow on DL direction.
BOTH	Indicates to NG-RAN to report the congestion information of the QoS Flow on UL and DL directions.
STOP	Indicates to NG-RAN to stop reporting the congestion information of the QoS Flow.

6.1.6.3.29  Enumeration: ActivationStatus |R18|  p. 274

Enumeration value	Description	Applicability
ACTIVE	Indicates that the established QoS Flows status for QoS monitoring for congestion information or for ECN marking for L4S is active.
NOT_ACTIVTE	Indicates that the established QoS Flows status for QoS monitoring for congestion information or for ECN marking for L4S is not active.