Update _3gpp-common-trace.yang (3390db97) · Commits · SA5 – Management & Orchestration and Charging / Management and Orchestration APIs

yang-models/_3gpp-common-trace.yang

+206 −91

Original line number	Diff line number	Diff line
		@@ -13,7 +13,7 @@ module _3gpp-common-trace {
		contact "https://www.3gpp.org/DynaReport/TSG-WG--S5--officials.htm?Itemid=464";

		description "Trace handling
		Copyright 2024, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI,
		Copyright 2025, 3GPP Organizational Partners (ARIB, ATIS, CCSA, ETSI, TSDSI,
		TTA, TTC). All rights reserved.";
		reference "3GPP TS 28.623
		Generic Network Resource Model (NRM)
		@@ -25,6 +25,7 @@ module _3gpp-common-trace {
		Integration Reference Point (IRP);
		Information Service (IS)" ;

		revision 2025-02-06 { reference "CR-XXXX" ; }
		revision 2024-11-05 { reference "CR-0470" ; }
		revision 2024-10-06 { reference "CR-0459"; }
		revision 2024-08-06 { reference "CR-0376 CR-0378 CR-0420"; }
		@@ -576,12 +577,10 @@ module _3gpp-common-trace {
		enum GNB_CU_UP;
		enum GNB_DU;
		}
		description "Specifies in which type of ManagedFunction the trace should
		description "Specifies the network element types where the trace should
		be activated. The attribute is applicable only for Trace with
		Signalling Based Trace activation. In case this attribute is not used,
		it carries a null semantic";
		reference "Clause 5.4 of 3GPP TS 32.422 for additional details on the
		allowed values";
		Signalling Based Trace activation. ";
		reference "Clause 5.4 of 3GPP TS 32.422";
		}

		leaf traceDepth {
		@@ -596,71 +595,166 @@ module _3gpp-common-trace {
		enum VENDORMAXIMUM;
		}
		default MAXIMUM;
		description "Specifies how detailed information should be recorded in the
		Network Element. The Trace Depth is a paremeter for Trace Session level,
		i.e., the Trace Depth is the same for all of the NEs to be traced in
		the same Trace Session.
		The attribute is applicable only for Trace, otherwise it carries a null
		semantic.";
		description "It specifies the trace depth. The attribute is applicable only for Trace.";
		reference "Clause 5.3 of 3GPP TS 32.422";
		}

		leaf triggeringEvents {
		list triggeringEvents {
		key idx;
		description "It specifies the triggering event parameter of the trace
		session. The attribute is applicable only for Trace.";
		reference "Clause 5.1 of 3GPP TS 32.422";
		leaf idx { type unit32; }

		leaf-list MSC_SERVER {
		type enumeration {
		enum MO_MT_CALLS;
		enum MO_MT_SMS;
		enum LU_IMSIattach_IMSIdetach;
		enum HANDOVER;
		enum SS;
		}
		}

		leaf-list SGSN {
		type enumeration {
		enum PDPcontext;
		enum MO_MT_SMS;
		enum RAU_GPRSattach_GPRSdetach;
		MBMScontext;
		}
		}


		leaf-list MGW {
		type enumeration {
		enum CONTEXT
		}
		}

		leaf-list GGSN {
		type enumeration {
		enum PDPcontext;
		enum MBMScontext;
		enum CONTEXT;
		enum SIPsession_StandaloneTransaction;
		}
		}

		leaf-list IMS {
		type enumeration {
		enum SIPsession_StandaloenTransaction;
		}
		}

		leaf-list BM_SC {
		type enumeration {
		enum MBMSactivation;
		}
		}

		leaf-list MME {
		type enumeration {
		enum UEinitiatedPDNconnectivityRequest;
		enum ServiceRequest;
		enum InitialAttach_TAU_Detach;
		enum UEinitiatedPDNdisconnection;
		enum UEInitiatedPDNdisconnection;
		enum BearerActivationModificationDeletion;
		enum Handover;
		}
		}


		leaf-list SGW {
		type enumeration {
		enum PDNconnectionCreation;
		enum PDNconnectionTermination;
		enum Registration;
		enum UEderegistration;
		enum NetworkDeregistration;
		enum UEMobilityFromEPC;
		enum UEMobilityToEPC;
		enum PDUsessionEstablishment;
		enum PDUsessionModification;
		enum PDUsessionRelease;
		enum PDUsessionUPactivationDeactivation;
		enum MobilityBtw3gppAndN3gppTo5GC;
		enum MobilityFromEpc;
		enum AMpolicy;
		enum SMpolicy;
		enum Authorization;
		enum BDTpolicy;
		enum N4Session;
		enum UEauthentication;
		enum EventExposure;
		enum PFDmanagement;
		enum ParameterProvision;
		enum Trigger;
		enum NFmanagement;
		enum NFdiscovery;
		enum NSSelection;
		enum NSSAI;
		enum SMservice;
		enum UEcontext;
		enum SubscriberData;
		enum BearerActivationModificationDeletion;
		}
		}
		description "It specifies the triggering event parameter of the trace
		session. The attribute is applicable only for Trace. In case this
		attribute is not used, it carries a null semantic.

		See the clause 5.1 of 3GPP TS 32.422 for additional details on the
		allowed values.";
		leaf-list PGW {
		type enumeration {
		enum PDNconnectionCreation;
		enum PDNconnectionTermination;
		enum BearerActivationModificationDeletion;
		}
		}

		leaf-list AMF {
		type enumeration {
		enum X;
		enum Y;
		}
		}

		leaf-list SMF {
		type enumeration {
		enum X;
		enum Y;
		}
		}

		leaf-list PCF {
		type enumeration {
		enum X;
		enum Y;
		}
		}

		leaf-list UPF {
		type enumeration {
		enum X;
		enum Y;
		}
		}

		leaf-list AUSF {
		type enumeration {
		enum X;
		enum Y;
		}
		}

		leaf-list NEF {
		type enumeration {
		enum X;
		enum Y;
		}
		}

		leaf-list NRF {
		type enumeration {
		enum X;
		enum Y;
		}
		}

		leaf-list NSSF {
		type enumeration {
		enum X;
		enum Y;
		}
		}

		leaf-list SMSF {
		type enumeration {
		enum X;
		enum Y;
		}
		}

		leaf-list UDM {
		type enumeration {
		enum X;
		enum Y;
		}
		}








		}
		}

		@@ -1665,13 +1759,20 @@ module _3gpp-common-trace {
		attribute is applicable for both Trace and MDT. This attribute
		includes the ID type of the target as an enumeration and the ID value.

		The traceTarget shall be public ID in case of a Management Based
		Activation is done to an ScscfFunction. The traceTarget shall be
		cell only in case of the UTRAN cell traffic trace function.
		The traceTarget shall be PUBLIC_ID in case of a Management Based
		Activation is done to an SCSCFFunction (Serving Call Session Control Function)
		or PCSCFFunction (Proxy Call Session Control Function).
		The traceTarget shall be UTRAN_CELL only in case of the UTRAN cell traffic
		trace function.

		The traceTarget shall be E-UtranCell only in case of E-UTRAN cell
		traffic trace function.The traceTarget shall be either IMSI or
		IMEI(SV) if the Trace Session is activated to any of the following
		The traceTarget shall be E_UTRAN_CELL only in case of E-UTRAN cell
		traffic trace function.

		The traceTarget shall be NG_RAN_CELL only in case of NR cell
		traffic trace function.

		The traceTarget shall be either IMSI, IMEI or
		IMEISV if the Trace Session is activated to any of the following
		ManagedEntity(ies):
		- HssFunction
		- MscServerFunction
		@@ -1680,28 +1781,42 @@ module _3gpp-common-trace {
		- BmscFunction
		- RncFunction
		- MmeFunction
		- ServingGWFunction
		- PGWFunction

		The traceTarget shall be either SUPI or IMEISV if the Trace Session
		is activated to any of the followed ManagedEntity(ies):
		- AFFunction
		- AMFFunction
		- AUSFFunction
		- NEFFunction
		- NRFFunction
		- NSSFFunction
		- PCSCFFunction
		- SMFFunction
		- UPFFunction
		- UDMFunction

		In case of signalling based MDT, the traceTarget attribute should
		be able to carry PUBLIC_ID, IMSI, IMEI, IMEISV or SUPI.

		In case of management based Immediate MDT, the traceTarget attribute
		shall be null value.

		The traceTarget shall be IMSI if the Trace Session is activated to a
		ManagedEntity playing a role of ServinGWFunction.
		In case of management based Logged MDT, the traceTarge attribute
		shall carry an eNB or gNB or an RNC. The Logged MDT should be
		initiated on the specified eNB/gNB/RNC in traceTarget.

		In case of signaling based Trace/MDT, the traceTarget attribute shall
		be able to carry (IMSI or IMEI(SV)or SUPI), the areaScope attribute
		shall be able to carry a list of (cell or E-UtranCell or NRCellDU or
		TA/LA/RA).
		In case of RLF reporting, or RCEF reporting, the traceTarget attribute
		shall be null value.

		In case of management based Immediate MDT, the traceTarget attribute
		shall be null value, the areaScope attribute shall carry a list of
		(Utrancell or E-UtranCell or NRCellDU).

		In case of management based Logged MDT, the traceTarget attribute
		shall carry an eBs or a RNC or gNBs. The Logged MDT should be initiated
		on the specified eNB or RNC or gNB in traceTarget. The areaScope
		attribute shall carry a list of (Utrancell or E-UtranCell or NRCellDU or
		TA/LA/RA).

		In case of RLF reporting, or RCEF reporting, the traceTarget
		attribute shall be null value, the areaScope attribute shall carry
		one or list of eNBs/gNBs";
		In case of signalling based 5GC UE level measurements collection, the
		traceTarget attribute shall be able to carry IMEISV or SUPI.

		In case of management based 5GC UE level measurements collection, the
		traceTarget attribute shall be to carry the corresponding Measured UE
		Identifier as defined by the bullet g) of the 5GC UE level measurements
		(see TS 28.559) when the traceJob is craeted at the subject ManagedEntity";
		reference "3GPP TS 32.422";
		}