Content for TS 33.128 Word version: 18.6.0

0… 4… 5… 5.7… 6… 6.2.2.2A… 6.2.3… 6.2.3.2.7… 6.2.3.3… 6.2.4… 6.3… 6.3.2.2A… 6.3.3… 6.3.3.2… 6.3.3.2.4… 6.3.3.2A… 7… 7.3… 7.3.3… 7.3.3.2.21… 7.3.3.2.42… 7.3.3.2.63… 7.3.4… 7.4… 7.4.3.8… 7.5… 7.6… 7.7… 7.7.4… 7.8… 7.8.4… 7.9… 7.10… 7.10.4… 7.11… 7.12… 7.13… 7.13.3… 7.13.3.4… 7.14… 7.15… 8… A… D… E… M…

8.1 General 8.2 Simple types 8.3 Identifier Types 8.3.1 General 8.3.2 User identifier lists 8.3.2.1 Type: UserIdentifiers 8.3.2.2 Sequence Of user identifier types 8.3.2.3 Type: EPSSubscriberIDs 8.3.2.4 Type: FiveGSSubscriberID 8.3.3 Simple Types for Identifiers 8.3.4 Type: SUPI 8.3.5 Type: SUCI 8.3.6 Type: PEI 8.3.7 Type: GPSI 8.3.8 Type: GUTI 8.3.9 Type: FiveGGUTI 8.3.10 Type: EPS5GGUTI 8.3.11 Type: NonIMEISVPEI 8.4 Complex types 8.4.1 Type: HandoverCause 8.4.2 Type: EMM5GMMStatus 8.4.3 Type: ForbiddenAreaInformation 8.4.4 Type: ForbiddenLAInformation 8.4.5 Type: RATRestrictionItem 8.4.6 Type: LTEV2XServiceAuthorization 8.4.7 Type: NRV2XServiceAuthorization 8.4.8 Type: RRCEstablishmentCause 8.4.9 Type: ConnectedENGNB 8.4.10 Type: PLMNSupportItem 8.5 Enumerations 8.5.1 Enumeration: EMMRegStatus 8.5.2 Enumeration: FiveGMMRegStatus 8.5.3 Enumeration: SMSOverNASIndicator 8.5.4 Enumeration: CSGMembershipIndication 8.5.5 Enumeration: EPSAttachType 8.5.6 Enumeration: EPSAttachResult 8.5.7 Enumeration: EPSSMSServiceStatus 8.5.8 Enumeration: EstablishmentCause 8.5.9 Enumeration: TraceRecordType 8.5.10 Enumeration: TraceDirection
...

8 Common Parameter Definitions p. 369

8.1 General p. 369

The following sub-clauses contain definitions for Types defined in the attached ASN.1 documents that are used by multiple POIs and therefore cannot be placed in a single clause above.

Common parameters that are present within the Location structure are defined in clause 7.3.3.2.

8.2 Simple types p. 370

Table 8.2-1: Common Simple Types for LI reporting

Type name	Type definition	Description
CSGID	INTEGER	Closed Subscriber Group Identifier derived from CSG-ID defined in clause 7.3.79 of TS 29.272.
IPv4Address	OCTET STRING (SIZE (4))	The IPv4 address being reported in binary representation.
IPv6Address	OCTET STRING (SIZE (16))	The IPv6 address being reported in binary representation.
MCC	NumericString (SIZE (3))	Mobile Country Code.
MNC	NumericString (SIZE (2..3))	Mobile Network Code.
MUSIMUERequestType	OCTET STRING (SIZE(1))	Indicates the reason the UE has requested the release of NAS Signalling or rejected paging. Encoded per UE Request Type omitting the first two octets. See clause 9.9.3.65 of TS 24.301.
NID	UTF8String (SIZE(11))	This represents the Network Identifier, which together with a PLMN ID is used to identify an SNPN. See clause 12.7.1 of TS 23.003. Encoded as per clause 5.4.3 of TS 29.571.
PagingRestrictionIndicator	OCTET STRING (SIZE(1..33))	Indicates the paging restriction requested by the UE or applied by the network for a UE. Derived from the Paging Restriction defined in clause 9.9.3.66 of TS 24.301 and clause 9.11.3.77 of TS 24.501.
RAC	OCTET STRING (SIZE (2))	Routing Area Code identifying a routing area within a location area. Defined in clause 4.2 of TS 23.003.
RATFrequencySelectionPriority	INTEGER (1..256)	Indicates the RAT/Frequency priority to define camp priorities in Idle mode and inter-RAT/inter-freqency priorities for handover in Active mode. See clause 9.3.1.61 of TS 38.413 and clause 9.2.1.39 of TS 36.413.
RATRestrictionInformation	BIT STRING (SIZE(8,…))	Indicates a list of RATs that are restricted. When used in EPS records, this IE is encoded as specified in clause 9.2.1.22 of TS 36.413. When used in 5GS records, this IE is encoded as specified in clause 9.3.1.85 of TS 38.413.
SAC	OCTET STRING (SIZE (2))	The Service Area Code (SAC) together with the PLMN-Id and the LAC constitute the Service Area Identifier. The SAC is defined by the operator and set in the RNC via O&M. Defined in clause 12.5 of TS 23.003.
TAC	OCTET STRING (SIZE(2..3))	The tracking area code being reported. Given in the format specified in clause 9.3.3.10 of TS 38.413.
Timestamp	GeneralizedTime	Unless otherwised specified, the timestamp shall be given qualified with time zone information (i.e. as UTC or offset from UTC, not using the local time format).
TimeZone	UTF8String	String containing the contents defined in TS 29.571, Table 5.2.2-1.

Table 8.2-2 contains the details for types that consist only of a SEQUENCE OF or SET OF.

Table 8.2-2: Details of SEQUENCE OF Types

Type name	Definition	Cardinality	Description
TAIList	SEQUENCE OF TAI	0..MAX	Contains a list of TAIs
PLMNList	SEQUENCE OF PLMNID	1..MAX	Contains a list of PLMNs
ForbiddenTACs	SEQUENCE OF TAC	1..MAX	Contains a list of TACs.
ForbiddenLACs	SEQUENCE OF LAC	1..MAX	Contains a list of LACs
RATRestrictions	SEQUENCE OF RATRestrictionItem	1..MAX	Contains a list of RAT Restrictions.
ConnectedENGNBList	SEQUENCE OF ConnectedENGNB	1..MAX	Contains a list of connected en-gNBs.
PLMNSupportList	SEQUENCE OF PLMNSupportItem	1..MAX	Contains a list of supported PLMNs. Derived from the PLMN Support List IE defined in clause 9.2.6.2 of TS 38.413. Also can be used to report the Served PLMNs portion of the Served GUMMEIs IE of the S1 SETUP Response defined in clause 9.1.8.5 of TS 36.413.

Table 8.2-3 contains the details for Types that use the ExternalASNType.

Table 8.2-3: Details for ExtenalASNType

Type name	Definition	Cardinality	Description
TraceActivation	ExternalASNType	1	Information related to a trace session activation provided from the core to the RAN node. The ExternalASNType.encodedASNValue.alignedPER choice shall be used when populating this type and it shall be populated with the contents of the Trace Activation IE as described in the tables for the records that use this Type.

8.3 Identifier Types p. 371

8.3.1 General p. 371

The following subclauses contain definitions for the identifiers used in the attached ASN.1 documents.

8.3.2 User identifier lists p. 371

8.3.2.1 Type: UserIdentifiers p. 371

As there are often multiple identifiers that may be known at an NF or by the MDF, a single type capable of reporting multiple User Identifiers was defined.

Table 8.3.2.1-1: Structure of the UserIdentifiers type

Field name	Type	Cardinality	Description	M/C/O
fiveGSSubscriberIDs	FiveGSSubscriberIDs	0..1	Contains the list of 5GS identifiers for a user. Shall be present when any 5GS identifiers are known at the NF where the POI is locater or at the MDF.	C
ePSSubscriberIDs	EPSSubscriberIDs	0..1	Contains the list of EPS identifiers for a user. Shall be present when any EPS identifiers are known at the NF where the POI is locater or at the MDF.	C

8.3.2.2 Sequence Of user identifier types p. 371

Table 8.3.2.2-1 contains the details for types that consist only of a SEQUENCE OF or SET OF.

Table 8.3.2.2-1: Details of SEQUENCE OF Types

Type name	Definition	Cardinality	Description
FiveGSSubscriberIDs	SEQUENCE OF FiveGSSubscriberID	1..MAX	Contains the list of 5GS identifiers for a user. Shall be present when any 5GS identifiers are known at the NF where the POI is locater or at the MDF.
EPSSubscriberIDs	SEQUENCE OF EPSSubscriberID	1..MAX	Contains the list of EPS identifiers for a user. Shall be present when any EPS identifiers are known at the NF where the POI is locater or at the MDF.

8.3.2.3 Type: EPSSubscriberIDs p. 372

Table 8.3.2.3-1: Structure of the EPSSubscriberIDs type

Field name	Type	Cardinality	Description	M/C/O
iMSI	IMSI	0..1	Shall be present when the IMSI is known.	C
mSISDN	MSISDN	0..1	Shall be present when the MSISDN is known.	C
iMEI	IMEI	0..1	Shall be present when the IMEI is known.	C

8.3.2.4 Type: FiveGSSubscriberID p. 372

Table 8.3.2.4-1: Definition of Choices for FiveGSSubscriberID

CHOICE	Type	Description
sUPI	SUPI	Chosen when the identifier being reported is a SUPI.
sUCI	SUCI	Chosen when the identifier being reported is a SUCI.
pEI	PEI	Chosen when the identifier being reported is a PEI.
gPSI	GPSI	Chosen when the identifier being reported is a GPSI.

8.3.3 Simple Types for Identifiers p. 373

Table 8.3-1: Common Simple Types for Identifiers

Type name	Type definition	Description
AMFPointer	INTEGER (0..63)	Derived from the AMF Pointer defined in clause 2.10.1 of TS 23.003.
AMFRegionID	INTEGER (0..255)	Derived from the AMF Region ID defined in clause 2.10.1 of TS 23.003.
AMFSetID	INTEGER (0..1023)	Derived from the AMF Set ID defined in clause 2.10.1 of TS 23.003.
EUI64	OCTET STRING (SIZE(8))	Derived from an IEEE Extended Unique Identifier (EUI-64), for UEs not supporting any 3GPP access technologies, as defined in IEEE "Guidelines for Use of Extended Unique Identifier (EUI), Organizationally Unique Identifier (OUI), and Company ID (CID)" [127].
FiveGTMSI	INTEGER (0..4294967295)	Derived from the TMSI defined in clause 2.10.1 of TS 23.003.
HomeNetworkIdentifier	UTF8String	Indicates the home network of the subscriber. Shall be populated as described in clause 2.2B of TS 23.003.
HomeNetworkPublicKeyID	OCTET STRING	Identifies the public key used when generating the SUCI. See clause 2.2B of TS 23.003. This parameter shall be encoded as an OCTET STRING with a single octet containing the Home Network Public Key ID described in clause 2.2B of TS 23.003.
IMEI	NumericString(Size(14))	Derived from the International Mobile Equipment Identity defined in clause 6.2.1 of TS 23.003.
IMEISV	NumericString (SIZE(16))	Derived from the International Mobile Equipment Identity and Software Version defined in clause 6.2.2 of TS 23.003.
IMSI	NumericString (SIZE(6..15))	Derived from the International Mobile Subscription Identity defined in clause 2.1 and clause 2.2 of TS 23.003.
MACAddress	OCTET STRING (SIZE(6))	Derived from a MAC address defined in RFC 7042.
MMECode	OCTET STRING (SIZE(1))	Derived from the MME Code defined in clause 2.8.1 of TS 23.003.
MMEGroupID	OCTET STRING (SIZE(2))	Derived from the MME Group ID defined in clause 2.8.1 of TS 23.003.
MSISDN	NumericString (SIZE(1..15))	Derived from the MSISDN defined in clause 3.3 of TS 23.003.
NAI	UTF8String	A network access identifiers as described in RFC 4282.
ProtectionSchemeID	INTEGER (0..15)	Identifies the Protection Scheme used to generate the SUCI. See clause 2.2B of TS 23.003.
RoutingIndicator	INTEGER (0..9999)	The routing indicator for the SUCI. Used with the Home Network Identifier to route network signalling to the correct UDM/AUSF instances. See clause 2.2B of TS 23.003.
SchemeOutput	OCTET STRING	Contains the characters resulting as the output of the permanent identifier with the protection scheme applied. See clause 2.2B of TS 23.003.
SUPIType	INTEGER (1..7)	Indicates the type of SUPI concealed by a SUCI. Shall be populated as described in clause 2.2B of TS 23.003.
TMSI	OCTET STRING (SIZE(4))	Derived from the TMSI defined in clause 2.4 of TS 23.003.

8.3.4 Type: SUPI p. 373

The SUPI type is derived from the data present in the Subscription Permanent Identifier type defined in clause 2.2A of TS 23.003.

Table 8.3.4-1 contains the details for the SUPI type.

Table 8.3.4-1: Definition of Choices for SUPI

CHOICE	Type	Description
iMSI	IMSI	Chosen when the SUPI contains an IMSI.
nAI	NAI	Chosen when the SUPI contains an NAI.

8.3.5 Type: SUCI p. 374

The SUCI type is derived from the data present in the Subscription Concealed Identifier type defined in clause 2.2B of TS 23.003.

Table 8.3.5-1 contains the details for the SUCI type.

Table 8.3.5-1: Definition of SUCI type

Field name	Type	Cardinality	Description	M/C/O
mCC	MCC	1	The mobile country code identifying the country of the home network for the subscriber. If the SUPI Type is not 0, the MCC shall be populated with '000' and ignored.	M
mNC	MNC	1	The mobile network code identifying the PLMN of the home network of the subscriber. If the SUPI Type is not 0, the MNC shall be populated with '000' and ignored.	M
routingIndicator	RoutingIndicator	1	The routing indicator for the SUCI.	M
protectionSchemeID	ProtectionSchemeID	1	The protection scheme ID used to generate the SUCI.	M
homeNetworkPublicKeyID	HomeNetworkPublicKeyID	1	Identifies the key used for SUPI protection.	M
schemeOutput	SchemeOutput	1	Contains the characters resulting as the output of the permanent identifier with the protection scheme applied.	M
routingIndicatorLength	INTEGER (1..4)	0..1	Shall be included if the length of the routing indicator is different from the number of meaningful digits given in the routingIndicator field.	C
sUPIType	SUPIType	0..1	Indicates the type of SUPI concealed in the SUCI. See clause 2.2B of TS 23.003. Shall be present if present in the SUCI being reported. If this parameter is not present, the SUPI Type may be assumed to be IMSI.	C
homeNetworkIdentifier	HomeNetworkIdentifier	0..1	Identifies the home network of the subscriber. See clause 2.2B of TS 23.003. Shall be present unless the SUPI Type is 0 and the MCC and MNC fields are populated.	C

8.3.6 Type: PEI p. 374

The PEI type is derived from the data present in the Permanent Equipment Identifier type defined in clause 6.4 of TS 23.003.

Table 8.3.6-1 contains the details for the PEI type.

Table 8.3.6-1: Definition of Choices for PEI

CHOICE	Type	Description
iMEI	IMEI	Chosen when the PEI contains an IMEI.
iMEISV	IMEISV	Chosen when the PEI contains an IMEISV.
mACAddress	MACAddress	Chosen when the PEI contains a MAC Address.
eUI64	EUI64	Chosen when the PEI contains an EUI64.

8.3.7 Type: GPSI p. 374

The GPSI type is derived from the data present in the Generic Public Subscription Identifier type defined in clause 28.8 of TS 23.003.

Table 8.3.7-1 contains the details for the GPSI type.

Table 8.3.7-1: Definition of Choices for GPSI

CHOICE	Type	Description
mSISDN	MSISDN	Chosen when the GPSI type is MSISDN.
nAI	NAI	Chosen when the GPSI type is External Identifier.

8.3.8 Type: GUTI p. 375

The GUTI type is derived from the data present in the Globally Unique Temporary User Identity type defined in clause 2.8 of TS 23.003.

Table 8.3.8-1 contains the details for the GUTI type.

Table 8.3.8-1: Definition of GUTI type

Field name	Type	Cardinality	Description	M/C/O
mCC	MNC	1	The mobile country code identifying the country of the home network for the subscriber.	M
mNC	MNC	1	The mobile network code identifying the PLMN of the home network of the subscriber.	M
mMEGroupID	MMEGroupID	1	The identifier for the MME Group.	M
mMECode	MMECode	1	Identifies the MME that issued the GUTI.	M
mTMSI	TMSI	1	The temporary Identifier for the UE to uniquely identify it within the MME.	M

8.3.9 Type: FiveGGUTI p. 375

The FiveGGUTI type is derived from the data present in the 5G Globally Unique Temporary User Identity type defined in clause 2.10 of TS 23.003.

Table 8.3.9-1 contains the details for the FiveGGUTI type.

Table 8.3.9-1: Definition of FiveGGUTI type

Field name	Type	Cardinality	Description	M/C/O
mCC	MNC	1	The mobile country code identifying the country of the home network for the subscriber.	M
mNC	MNC	1	The mobile network code identifying the PLMN of the home network of the subscriber.	M
aMFRegionID	AMFRegionID	1	The identifier for the AMF Region.	M
aMFSetID	AMFSetID	1	Identifies the AMF Set the AMF belongs to.	M
aMFPointer	AMFPointer	1	Identifies the AMF.	M
fiveGTMSI	FiveGTMSI	1	The temporary Identifier for the UE to uniquely identify it within the AMF.	M

8.3.10 Type: EPS5GGUTI p. 375

The EPS5GGUTI type is used when a parameter may be either a GUTI or a 5G-GUTI.

Table 8.3.10-1 contains the details for the EPS5GGUTI type.

Table 8.3.10-1: Definition of Choices for EPS5GGUTI

CHOICE	Type	Description
gUTI	GUTI	Chosen when the field contains a GUTI.
fiveGGUTI	FiveGGUTI	Chosen when the field contains a 5G-GUTI.

8.3.11 Type: NonIMEISVPEI p. 376

The NonIMEISVPEI type is used when IMEI or IMEISV based PEI is not available.

Table 8.3.11-1 contains the details for the NonIMEISVPEI type.

Table 8.3.11-1: Definition of Choices for NonIMEISVPEI

CHOICE	Type	Description
mACAddress	MACAddress	Chosen when the field contains a GUTI.
eUI64	FiveGGUTI	Chosen when the field contains a 5G-GUTI.

8.4 Complex types p. 376

8.4.1 Type: HandoverCause p. 376

The HandoverCause type is derived from the Cause type defined in clause 9.3.1.2 of TS 38.413.

Table 8.4.1-1 contains the details for the HandoverCause type.

Table 8.4.1-1: Choices for HandoverCause type

CHOICE	Type	Description
radioNetwork	CauseRadioNetwork	Chosen when the cause indicated is one of the Radio Network Layer Causes.
transport	CauseTransport	Chosen when the cause indicated is one of the Transport Layer Causes.
nas	CauseNas	Chosen when the cause indicated is one of the NAS Causes.
protocol	CauseProtocol	Chosen when the cause indicated is one of the Protocol Causes.
misc	CauseMisc	Chosen when the cause indicated is one of the Miscellaneous Causes.

8.4.2 Type: EMM5GMMStatus p. 376

Indicates the registration status of the UE in both EPS and 5GS as known at the NF where the POI is located. This type is derived from the UE status IE defined in clause 9.11.3.56 of TS 24.501.

Table 8.4.2-1: Definition of type EMM5GMMStatus

Field name	Type	Cardinality	Description	M/C/O
eMMRegStatus	EMMREGStatus	0..1	Indicates the EPS registration status of the UE as known at the NF where the POI is located. Shall be present if the EPS registration status is known.	C
fiveGMMStatus	FiveGMMStatus	0..1	Indicates the 5GS registration status of the UE as known at the NF where the POI is located. Shall be present if the 5GS registration status is known.	C

8.4.3 Type: ForbiddenAreaInformation p. 376

Contains a list of TACs that are forbidden.

Table 8.4.3-1: Structure of the ForbiddenAreaInformation type

Field name	Type	Cardinality	Description	M/C/O
pLMNIdentity	PLMNID	1	Contains the PLMN for which the forbidden area information applies.	M
forbiddenTACs	ForbiddenTACs	1	Contains the list of forbidden TACs.	M

8.4.4 Type: ForbiddenLAInformation p. 377

Contains a list of LACs that are forbidden.

Table 8.4.4-1: Structure of the ForbiddenAreaInformation type

Field name	Type	Cardinality	Description	M/C/O
pLMNIdentity	PLMNID	1	Contains the PLMN for which the forbidden area information applies.	M
forbiddenLACs	ForbiddenLACs	1	Contains the list of forbidden LACs.	M

8.4.5 Type: RATRestrictionItem p. 377

Contains a list of RAT Restrictions.

Table 8.4.5-1: Structure of the RATRestrictionItem type

Field name	Type	Cardinality	Description	M/C/O
pLMNIdentity	PLMNID	1	Contains the PLMN for which the RAT restriction applies.	M
rATRestrictionInformation	RATRestrictionInformation	1	Contains RAT Restriction.	M

8.4.6 Type: LTEV2XServiceAuthorization p. 377

Table 8.4.6-1 contains the details for the LTEV2XServiceAuthorization type.

Table 8.4.6-1: Structure of the LTEV2XServiceAuthorization type

Field name	Type	Cardinality	Description	M/C/O
v2XVehicleUEAuthorizationIndicator	V2XUEAuthorizationIndicator	0..1	Indicates the UE is authorised to act as a V2X vehicle UE.	C
v2XPedestrianUEAuthorizationIndicator	V2XUEAuthorizationIndicator	0..1	Indicates the UE is authorised to act as a V2X pedestrian UE.	C

8.4.7 Type: NRV2XServiceAuthorization p. 377

Table 8.4.7-1 contains the details for the NRV2XServiceAuthorization type.

Table 8.4.7-1: Structure of the NRV2XServiceAuthorization type

Field name	Type	Cardinality	Description	M/C/O
v2XVehicleUEAuthorizationIndicator	V2XUEAuthorizationIndicator	0..1	Indicates the UE is authorised to act as a V2X vehicle UE.	C
v2XPedestrianUEAuthorizationIndicator	V2XUEAuthorizationIndicator	0..1	Indicates the UE is authorised to act as a V2X pedestrian UE.	C

8.4.8 Type: RRCEstablishmentCause p. 377

The RRCEstablishmentCause type is derived from the RRC Establishment Cause type defined in clause 9.3.1.111 of TS 38.413. and the RRC Establishment Cause type defined in clause 9.2.1.3a of TS 36.413.

Table 8.4.8-1 contains the details for the RRCEstablishmentCause type.

Table 8.4.8-1: Choices for RRCEstablishmentCause type

CHOICE	Type	Description
ePCEstablishmentCause	EstablishmentCause	Chosen when the UE is connecting to EPC.
fiveGCEstablishmentCause	EstablishmentCause	Chosen when the UE is connecting to 5GC.

8.4.9 Type: ConnectedENGNB p. 378

Table 8.4.9-1 contains the details for the ConnectedENGNB type. Derived from the Connected en-gNB List type defined in clause 9.1.8.4 of TS 36.413.

Table 8.4.9-1: Structure of the ConnectedENGNB type

Field name	Type	Cardinality	Description	M/C/O
eNGNBID	GNbID	1	The gNBID of the connected en-gNB.	M
supportedTAList	TACList	1	A list of TACs supported by the conneceted en-gNB.	M
broadcastPLMN	PLMNList	1	A list of the PLMNs broadcast by the connected en-gNB.	M

8.4.10 Type: PLMNSupportItem p. 378

Contains a PLMN and possibly a NID along with an onboarding support indication.

Table 8.4.10-1: Structure of the PLMNSupportItem type

Field name	Type	Cardinality	Description	M/C/O
pLMNIdentity	PLMNID	1	Contains the identity of the PLMN being described.	M
nPNSupport	NID	0..1	Contains the NID. Shall be present if the context being reported is for an NPN.	C
onBoardingSupport	BOOLEAN	0..1	Indicates whether the PLMN supports onboarding.	C

8.5 Enumerations p. 378

8.5.1 Enumeration: EMMRegStatus p. 378

The EMMRegStatus type is derived from the EMM registration status portion of the UE status IE defined in clause 9.11.3.56 of TS 24.501.

Table 8.5.1-1 contains the details for the EMMRegStatus type.

Table 8.5.1-1: Enumeration for the EMMRegStatus type

Enumeration	Description
uEEMMRegistered(1)	UE is in EMM-REGISTERED state
uENotEMMRegistered(2)	UE is not in EMM-REGISTERED state

8.5.2 Enumeration: FiveGMMRegStatus p. 378

The FiveGMMRegStatus type is derived from the 5GMM registration status portion of the UE status IE defined in clause 9.11.3.56 of TS 24.501.

Table 8.5.2-1 contains the details for the FiveGMMRegStatus type.

Table 8.5.2-1: Enumeration for the FiveGMMRegStatus type

Enumeration	Description
uE5GMMRegistered(1)	UE is in 5GMM-REGISTERED state
uENot5GMMRegistered(2)	UE is not in 5GMM-REGISTERED state

8.5.3 Enumeration: SMSOverNASIndicator p. 379

The SMSOverNASIndicator type is derived from the SMS over NAS transport allowed portion of the 5GS registration result IE defined in clause 9.11.3.6.1 of TS 24.501.

Table 8.5.3-1 contains the details for the SMSOverNASIndicator type.

Table 8.5.3-1: Enumeration for the SMSOverNASIndicator type

Enumeration	Description
sMSOverNASNotAllowed(1)	SMS over NAS not allowed
sMSOverNASAllowed(2)	SMS over NAS allowed

8.5.4 Enumeration: CSGMembershipIndication p. 379

The CSGMembershipIndication indicates whether the user is a member of a CSG.

Table 8.5.4-1 contains the details for the CSGMembershipIndication type.

Table 8.5.4-1: Enumeration for the CSGMembershipIndication type

Enumeration	Description
notCSGMember(1)	The user is not a member of the indicated CSG.
cSGMember(2)	The user is a member of the indicated CSG.

8.5.5 Enumeration: EPSAttachType p. 379

The EPSAttachType provides information on the attach type used by the UE. Derived from the enumerations in clause 9.9.3.11 of TS 24.301.

Table 8.5.5-1 contains the details of the EPSAttachType type.

Table 8.5.5-1: Enumeration for EPSAttachType

Enumeration value	Description
ePSAttach(1)	The attach type is an EPS attach.
combinedEPSIMSIAttach(2)	The attach type is a combined EPS/IMSI attach.
ePSRLOSAttach(3)	The attach type is an EPS RLOS attach.
ePSEmergencyAttach(4)	The attach type is an EPS Emergency attach.
reserved(5)	The attach type is unknown or using a reserved type.

8.5.6 Enumeration: EPSAttachResult p. 379

The EPSAttachResult provides information on the attach type used by the UE. Derived from the enumerations in clause 9.9.3.10 of TS 24.301.

Table 8.5.6-1 contains the details of the EPSAttachResult type.

Table 8.5.6-1: Enumeration for EPSAttachResult

Enumeration value	Description
ePSOnly(1)	The attach type is an EPS attach.
combinedEPSIMSI(2)	The attach type is a combined EPS/IMSI attach.

8.5.7 Enumeration: EPSSMSServiceStatus p. 380

The EPSSMSServiceStatus provides information on status of SMS Services. Derived from the enumerations in clause 9.9.3.4B of TS 24.301.

Table 8.5.7-1 contains the details of the EPSSMSServiceStatus type.

Table 8.5.7-1: Enumeration for EPSSMSServiceStatus

Enumeration value	Description
sMSServicesNotAvailable(1)	SMS Services ar not available.
sMSServicesNotAvailableInThisPLMN(2)	SMS Services not available for this UE in this PLMN.
networkFailure(3)	SMS Services unavailable due to Network failure.
Congestion(4)	SMS Services unavailable due to congestion.

8.5.8 Enumeration: EstablishmentCause p. 380

The EstablishmentCause provides information on reason RRC was established. Derived from the RRC Establishment Cause type defined in clause 9.3.1.111 of TS 38.413. and the RRC Establishment Cause type defined in clause 9.2.1.3a of TS 36.413.

Table 8.5.8-1 contains the details of the EstablishmentCause type.

Table 8.5.8-1: Enumeration for EstablishmentCause

Enumeration value	Description
emergency(1)	Connection established Emergency connection.
highPriorityAccess(2)	Connection established for a High priority access connection.
mtAccess(3)	Connection established as a result of a page.
moSignalling(4)	Connection established for mobile originated signalling.
moData(5)	Connection established for mobile originated data.
moVoiceCall(6)	Connection established for mobile originated voice call.
moVideoCall(7)	Connection established for mobile originated video call.
moSMS(8)	Connection established for mobile originated SMS.
mpsPriorityAccess(9)	Connection established for MPS Priority Access.
mcsPriorityAccess(10)	Connection established for MCS Priority Access.
notAvailable(11)	Not available.
exceptionData(12)	Exception Data.

8.5.9 Enumeration: TraceRecordType p. 380

The TraceRecordType provides information on the type of Trace record being reported.

Table 8.5.9-1 contains the details of the TraceRecordType type.

Table 8.5.9-1: Enumeration for TraceRecordType

Enumeration value	Description
traceStart(1)	The message being reported is a Trace Start message.
cellTrafficTrace(2)	The message being reported is a Cell Traffic Trace message.
traceDataDelivery(3)	The message being reported is trace data being delivered to the trace collection entity.
traceDeactivation(4)	The message being reported is a Deactivate Trace message.

8.5.10 Enumeration: TraceDirection p. 381

The TraceDirection provides information on the direction of the trace information being reported.

Table 8.5.10-1 contains the details of the TraceDirection type.

Table 8.5.10-1: Enumeration for TraceDirection

Enumeration value	Description
toAMF(1)	Shall be chosen when the message being reported is to the AMF.
fromAMF(2)	Shall be chosen when the message being reported is from the AMF.
toMME(3)	Shall be chosen when the message being reported is to the MME.
fromMME(4)	Shall be chosen when the message being reported is from the MME.