XID

XID assigned by LIPF.

M

TargetIdentifiers

One of the target identifiers listed in the paragraph above.

M

DeliveryType

Set to "X2Only".

M

ListOfDIDs

Delivery endpoints for LI_X2 for the IRI-POI in the AMF. These delivery endpoints are configured using the CreateDestination message as described in ETSI TS 103 221-1 [7] clause 6.3.1 prior to the task activation.

M

TaskDetailsExtensions/

IdentifierAssociationExtensions

This field shall be included if the IRI POI is required to generate AMFIdentifierAssociation records (see clause 6.2.2.2.1). If the field is absent, AMFIdentifierAssociation records shall not be generated.

C

ListOfServiceTypes

Shall be included when the explicit identification of specific CSP service types to be intercepted by the task as described in clause 5.2.4 is required. This parameter is defined in ETSI TS 103 221-1 [7], clause 6.2.1.2, table 4.

C

EventsGenerated

One of the following values:

– IdentifierAssociation

– All

See clause 6.2.2.2.1 for the interpretation of this field.

M

registrationType

Specifies the type of registration, see TS 24.501 [13] clause 9.11.3.7. This is derived from the information received from the UE in the REGISTRATION REQUEST message.

M

registrationResult

Specifies the result of registration, see TS 24.501 [13] clause 9.11.3.6.

M

slice

Provide, if available, one or more of the following:

– allowed NSSAI (see TS 24.501 [13] clause 9.11.3.37).

– configured NSSAI (see TS 24.501 [13] clause 9.11.3.37).

– rejected NSSAI (see TS 24.501 [13] clause 9.11.3.46).

This is derived from the information sent to the UE in the REGISTRATION ACCEPT message.

C

sUPI

SUPI associated with the registration (see clause 6.2.2.4).

M

sUCI

SUCI used in the registration, if available.

C

pEI

PEI provided by the UE during the registration, if available.

C

gPSI

GPSI obtained in the registration, if available as part of the subscription profile.

C

gUTI

5G-GUTI provided as outcome of initial registration or used in other cases, see TS 24.501 [13] clause 5.5.1.2.2.

M

location

Location information determined by the network during the registration, if available.

Encoded as a userLocation parameter (location>locationInfo>userLocation) and, when Dual Connectivity is activated, as an additionalCellIDs parameter (location>locationInfo>additionalCellIDs), see Annex A.

C

non3GPPAccessEndpoint

UE’s local IP address used to reach the N3IWF, TNGF or TWIF, if available. IP addresses are given as 4 octets (for IPv4) or 16 octets (for IPv6) with the most significant octet first (network byte order).

C

fiveGSTAIList

List of tracking areas associated with the registration area within which the UE is current registered, see TS 24.501 [13] clause 9.11.3.9 (see NOTE)

C

sMSoverNASIndicator

Indicates whether SMS over NAS is supported. Provide, if included in registrationResult, see TS 24.501 [13] clause 9.11.3.6.

C

oldGUTI

GUTI or 5G-GUTI, if provided in the REGISTRATION REQUEST message, see TS 24.501 [13] clause 5.5.1.2.2.

C

eMM5GRegStatus

UE Status, if provided in the REGISTRATION REQUEST message, see TS 24.501 [13] clause 9.11.3.56.

C

nonIMEISVPEI

MACAddress or EUI-64 used as UE equipment identity if IMEI or IMEISV based PEI is not available. Provide if known, see TS 24.501 [13] clause 8.2.26.4.

C

mACRestIndicator

Indicates whether the non-IMEISV PEI MACAddress can be used as an equipment identifier. Required if non-IMEISVPEI is used, see TS 24.501 [13] clause 9.11.3.4.

C

pagingRestrictionIndicator

Indicates if paging is restricted or the type of paging allowed. Include if sent in the REGISTRATION REQUEST message. Encoded per TS 24.501 [13] clause 9.11.3.77.2, omitting the first two octets.

C

NOTE: List shall be included each time there is a change to the registration area.

deregistrationDirection

Indicates whether the deregistration was initiated by the network or by the UE.

M

accessType

Indicates the access for which the deregistration is handled, see TS 24.501 [13] clause 9.11.3.20.

M

sUPI

SUPI associated with the deregistration (see clause 6.2.2.4), if available.

C

sUCI

SUCI used in the deregistration, if available (see NOTE).

C

pEI

PEI used in the deregistration, if available (see NOTE).

C

gPSI

GPSI associated to the deregistration, if available as part of the subscription profile.

C

gUTI

5G-GUTI used in the deregistration, if available, see TS 24.501 [13] clause 5.5.2.2.1 (see NOTE).

C

cause

Indicates the 5GMM cause value for network-initiated deregistration, see TS 24.501 [13] clause 9.11.3.2.

C

location

Location information determined by the network during the deregistration, if available.

Encoded as a userLocation parameter (location>locationInfo>userLocation), see Annex A.

C

switchOffIndicator

Indicates whether the deregistration type is normal or switch off, if available, see TS 24.501 [13] clause 9.1.3.20.1.

C

reRegRequiredIndicator

Indicates whether UE re-registration is required in the DEREGISTRATION REQUEST message, if available, see TS 24.501 [13] clause 9.1.3.20.1.

C

NOTE: At least one among SUCI, PEI and GUTI shall be provided.

sUPI

SUPI associated with the location update (see clause 6.2.2.4).

M

sUCI

SUCI associated with the location update, if available, see TS 24.501 [13].

C

pEI

PEI associated with the location update, if available.

C

gPSI

GPSI associated with the location update, if available as part of the subscription profile.

C

gUTI

5G-GUTI associated with the location update, if available, see TS 24.501 [13].

C

location

Updated location information determined by the network.

Depending on the service or message type from which the location information is extracted, it may be encoded in several forms (Annex A):

1) as a userLocation parameter (location>locationInfo>userLocation) in the case the information is obtained from an NGAP message, except the LOCATION REPORT message (see TS 38.413 [23]);

2) as a locationInfo parameter (location>locationInfo) in the case the information is obtained from a ProvideLocInfo (TS 29.518 [22] clause 6.4.6.2.6);

3) as a locationPresenceReport parameter (location>locationPresenceReport) in the case the information is obtained from an AmfEventReport (TS 29.518 [22] clause 6.2.6.2.5) with event type Location-Report or Presence-In-AOI-Report;

4) as a positionInfo parameter (location>positioningInfo>positionInfo) in the case the information is obtained from a ProvidePosInfo (TS 29.518 [22] clause 6.4.6.2.3) or a NotifiedPosInfo (TS 29.518 [22] clause 6.4.6.2.4).

M

sMSoverNASIndicator

No longer used in present version of this specification.

C

oldGUTI

No longer used in present version of this specification.

C

registrationResult

Specifies the result of registration, see TS 24.501 [13] clause 9.11.3.6.

M

registrationType

Specifies the type of registration, see TS 24.501 [13] clause 9.11.3.7, if available.

C

slice

Provide, if available, one or more of the following:

– allowed NSSAI (see TS 24.501 [13] clause 9.11.3.37).

– configured NSSAI (see TS 24.501 [13] clause 9.11.3.37).

C

sUPI

SUPI associated with the target UE.

M

sUCI

SUCI used in the registration, if available.

C

pEI

PEI associated with the target UE, if available.

C

gPSI

GPSI associated with the target UE, if available.

C

gUTI

Latest 5G-GUTI assigned to the target UE by the AMF.

M

location

Location information associated with the access type for the target UE, if available.

Encoded as a userLocation parameter (location>locationInfo>userLocation) and, when Dual Connectivity is activated, as an additionalCellIDs parameter (location>locationInfo>additionalCellIDs), see Annex A.

C

non3GPPAccessEndpoint

UE’s local IP address used to reach the N3IWF, TNGF or TWIF, if available. IP addresses are given as 4 octets (for IPv4) or 16 octets (for IPv6) with the most significant octet first (network byte order).

C

timeOfRegistration

Time at which the last registration occurred, if available. This is the time stamp when the REGISTRATION ACCEPT message was sent to the UE or (when applicable) when the REGISTRATION COMPLETE was received from the UE.

Shall be given qualified with time zone information (i.e. as UTC or offset from UTC, not as local time).

C

fiveGSTAIList

List of tracking areas associated with the target UE for the access type.

C

sMSoverNASIndicator

Indicates whether SMS over NAS is supported. Provide, if included in the UE Context.

C

oldGUTI

Latest GUTI or 5G-GUTI received from the target UE if different than the latest GUTI assigned by the AMF and the target UE has not acknowledged the latest GUTI assignment.

C

eMM5GRegStatus

UE Status, if this parameter can be derived from information available in the UE Context at the AMF.

C

NOTE: The values of the parameters in the table above are derived from the UE Context at the AMF, see TS 23.502 clause 5.2.2.2.2.

failedprocedureType

Specifies the procedure which failed at the AMF.

M

failureCause

Provides the value of the 5GSM or 5GMM cause, see TS 24.501 [13] clauses 9.11.3.2 and 9.11.4.2.

M

requestedSlice

Slice requested for the procedure, if available, given as a NSSAI (a list of S-NSSAI values as described in TS 24.501 [13] clause 9.11.3.37).

C

sUPI

SUPI associated with the procedure, if available (see NOTE).

C

sUCI

SUCI used in the procedure, if applicable and if available (see NOTE).

C

pEI

PEI used in the procedure, if available (see NOTE).

C

gPSI

GPSI used in the procedure, if available (see NOTE).

C

gUTI

5G-GUTI used in the procedure, if available, see TS 24.501 [13] clause 9.11.3.4 (see NOTE).

C

location

Location information determined during the procedure, if available.

Encoded as a userLocation parameter (location>locationInfo>userLocation), see Annex A.

C

NOTE: At least one identity shall be provided, the others shall be provided if available.

sUPI

SUPI associated with the procedure (see NOTE 1).

M

sUCI

SUCI used in the procedure, if applicable and if available.

C

pEI

PEI used in the procedure, if available (see NOTE 1).

C

gPSI

GPSI used in the procedure, if available (see NOTE 1).

C

gUTI

5G-GUTI used in the procedure, see TS 24.501 [13] clause 9.11.3.4.

M

location

Location information available when identifier association occurs.

Encoded as a userLocation parameter (location>locationInfo>userLocation) and, when Dual Connectivity is activated, as an additionalCellIDs parameter (location>locationInfo>additionalCellIDs), see Annex A.

M

fiveGSTAIList

List of tracking areas associated with the registration area within which the UE is current registered, see TS 24.501 [13], clause 9.11.3.9. (see NOTE 2)

C

NOTE 1: SUPI shall always be provided, in addition to the warrant target identifier if different to SUPI. Other identifiers shall be provided if available.

NOTE 2: List shall be included each time there is a change to the registration area.

sUPI

SUPI associated with the procedure (see NOTE 1 in table 6.2.2-6).

M

sUCI

SUCI used in the procedure, if applicable and if available.

C

pEI

PEI used in the procedure, if available (see NOTE 1 in table 6.2.2-6).

C

gPSI

GPSI used in the procedure, if available (see NOTE 1 in table 6.2.2-6).

C

gUTI

5G-GUTI used in the procedure, see TS 24.501 [13] clause 9.11.3.4.

C

nRPPaMessage

Any UE associated NRPPa message exchanged between the LMF and NG-RAN via AMF.

C

lPPMessage

Any LPP message exchanged between the LMF and the target UE via AMF.

C

lcsCorrelationId

LCS correlation ID (see TS 29.572 [24] clause 6.1.6.3.2) related to a location session, found in the Namf_CommunicationN1N2MessageTransfer and corresponding Namf_Communication_N2InfoNotify or Namf_CommunicationN1MessageNotify. All the AMFPositioningInfoTransfer records related to the same location session have the same lcsCorrelationId.

M

userIdentifiers

List of identifiers, including the target identifier, associated with the target UE registration stored in the AMF context. See TS 29.518 [22] clause 6.1.2.2.5.

M

aMFUENGAPID

Identity that the AMF uses to uniquely identify the target UE over the NG Interface. See TS 38.413 [23] clause 9.3.1.1. This is correlated to the SUPI known in the UE AMF context.

M

rANUENGAPID

Identity that the AMF receives from the NG-RAN node uniquely identifying the target UE with the NG-RAN Node. See TS 38.413 [23] clause 9.3.3.2.

M

handoverType

Identifies the type of handover indicated by the source RAN node to the AMF. See TS 38.413 [23] clause 9.3.1.22.

M

targetToSourceContainer

Provides radio related information about the gaining NG-RAN node. See TS 38.413 [23] clause 9.3.1.21.

M

userIdentifiers

List of user identifiers associated with the target UE registration stored in the AMF context. See TS 29.518 [22] clause 6.1.2.2.5.

M

aMFUENGAPID

Identity that the AMF uses to uniquely identify the target UE over the NG Interface, See TS 38.413 [23] clause 9.3.1.1. This is correlated to the SUPI known in the UE AMF context.

M

rANUENGAPID

Identity that the AMF receives from the NG-RAN node uniquely identifying the target UE within the NG-RAN Node. See TS 38.413 [23] clause 9.3.3.2.

M

handoverType

Identifies the type of handover indicated by the AMF to gaining RAN Node as seen in the HANDOVER REQUEST message. See TS 38.413 [23] clause 9.3.1.22.

M

handoverCause

Indicates the cause of handover as seen in the HANDOVER REQUEST message from AMF to gaining RAN node. See TS 38.413 [23] clause 9.3.1.2.

M

pDUSessionResourceInformation

Indicates the PDU Session to be transferred and Handover Command Transfer information as seen in the HANDOVER REQUEST and confirmed in the HANDOVER REQUEST ACKNOWLEDGE message. See TS 38.413 [23] clauses 9.3.1.50 and 9.3.4.10.

M

mobilityRestrictionList

Provides roaming or access restrictions related to mobility from AMF to gaining RAN Node. Include if sent in HANDOVER REQUEST. See TS 38.413 [23] clause 9.3.1.85.

C

locationReportingRequestType

Indicates the type of location reporting requested in the HANDOVER REQUEST. Include if in HANDOVER REQUEST message. See TS 38.413 [23] clause 9.3.1.65.

C

targetToSourceContainer

Provides radio related information from gaining to losing NG-RAN node that the AMF receives from the gaining RAN Node in the HANDOVER REQUEST ACKNOWLEDGE message. See TS 38.413 [23] clause 9.3.1.21.

M

nPNAccessInformation

Globally identifies the secondary NG-RAN node CAG Cells. Include if sent in the HANDOVER REQUEST ACKNOWLEDGE message from gaining RAN node to AMF. See TS 38.413 [23] clause 9.3.3.46.

C

rANSourceToTargetContainer

Provides radio related information via the AMF in the HANDOVER REQUEST from source to gaining NG-RAN node. See TS 38.413 [23] clause 9.3.1.21.

M

userIdentifiers

List of identifiers, including the target identifier, associated with the target UE registration stored in the AMF context. See TS 29.518 [22] clause 6.1.6.2.25.

M

gUTI

Current 5G-GUTI associated with the UE context. If the AMF includes a new 5G-GUTI as a part of the configuration update, this parameter shall be set to the new GUTI and the oldGUTI parameter shall be populated, see TS 24.501 [13] clause 8.2.19.3.

M

oldGUTI

Old 5G-GUTI associated with the UE context. If the AMF includes a new 5G-GUTI as a part of the configuration update, this parameter shall be set to the old GUTI.

C

fiveGSTAIList

List of tracking areas associated with the registration area within which the UE is current registered, see TS 24.501 [13] clause 9.11.3.9. Shall be included each time there is a change to the registration area and omitted if the registration area does not change.

C

slice

Provide, if available, one or more of the following:

– allowed NSSAI (see TS 24.501 [13] clause 9.11.3.37).

– configured NSSAI (see TS 24.501 [13] clause 9.11.3.37).

– rejected NSSAI (see TS 24.501 [13] clause 9.11.3.46).

This is derived from the information sent to the UE in the CONFIGURATION UPDATE COMMAND message.

C

serviceAreaList

Includes a list of allowed service areas or non-allowed service areas, encoded per TS 24.501 [13] clause 9.11.3.49, omitting the first two octets. Shall be included if present in the CONFIGURATION UPDATE COMMAND message, see TS 24.501 [13] clause 8.2.19.

C

registrationResult

Specifies the result of registration, see TS 24.501 [13] clause 9.11.3.6. Shall be included if present in the CONFIGURATION UPDATE COMMAND message, see TS 24.501 [13] clause 8.2.19.

C

sMSoverNASIndicator

Indicates whether SMS over NAS is supported. Shall be present if the SMS indication is present in the CONFIGURATION UPDATE COMMAND message, see TS 24.501 [13] clause 8.2.19.

C

AMFRegistration

REPORT

AMFDeregistration

REPORT

AMFLocationUpdate

REPORT

AMFStartOfInterceptionWithRegisteredUE

REPORT

AMFUnsuccessfulProcedure

REPORT

AMFIdentifierAssociation

REPORT

AMFPositioningInfoTransfer

REPORT

AMFRANHandoverCommand

REPORT

AMFRANHandoverRequest

REPORT

AMFUEConfigurationUpdate

REPORT

sUPI

SUPI associated with detected association event.

M

fiveGGUTI

5G-GUTI shall be provided. Encoded as per TS 24.501 [13] figure 9.11.3.4.1, omitting the first four octets.

M

timeStamp

Time at which the identifier association event occurred.

Shall be given qualified with time zone information (i.e. as UTC or offset from UTC, not as local time).

M

tAI

Last known TAI associated with the SUPI. Encoded as per TS 24.501 [13] clause 9.11.3.8, omitting the first octet.

M

nCGI

Last known nCGI(s) available when identifier association event detected. Given as a sequence of PLMNID (encoded as per TS 38.413 [23] clause 9.3.3.5) and NCI (encoded as per TS 38.413 [23] clause 9.3.1.7).

M

nCGITime

ueLocationTimestamp(s) of nCGIs if available in AMF as per TS 29 .571 [17] clause 5.4.4.9.

If ueLocationTimestamp(s) is not available, shall be populated with timeStamp(s) of when last known nCGI(s), were obtained and stored by the AMF.

M

sUCI

SUCI shall be provided when event is triggered by association of a SUCI to a SUPI. Encoded as per TS 24.501 [13] clause 9.11.3.4, omitting the first 3 octets.

C

pEI

PEI, (see NOTE 1).

C

fiveGSTAIList

List of tracking areas associated with the registration area within which the UE is current registered, see TS 24.501 [13], clause 9.11.3.9. (see NOTE 2)

C

gPSI

GPSI, (see NOTE 1).

C

NOTE 1: Shall be provided in first association record to ICF after PEI or GPSI is available and following any change of PEI or GPSI.

NOTE 2: As a minimum, list of tracking areas shall be included in the first association event for each SUPI registered (per UE session) with the AMF and additionally whenever the TAI list changes due to a change in registration area.

sUPI

SUPI associated with detected de-association event.

M

fiveGGUTI

5G-GUTI shall be provided. Encoded as per TS 24.501 [13] figure 9.11.3.4.1, omitting the first four octets.

M

timeStamp

Time at which the identifier de-association event occurred.

Shall be given qualified with time zone information (i.e. as UTC or offset from UTC, not as local time).

M

nCGI

Last known nCGI(s) available when identifier de-association event detected. Given as a sequence of PLMNID (encoded as per TS 38.413 [23] clause 9.3.3.5) and NCI (encoded as per TS 38.413 [23] clause 9.3.1.7).

M

nCGITime

ueLocationTimestamp(s) of nCGIs if available in AMF as per TS 29 .571 [17] clause 5.4.4.9.

If ueLocationTimestamp(s) is not available, shall be populated with timeStamp(s) of when last known nCGI(s), were obtained and stored by the AMF.

M

XID

XID assigned by LIPF. If the CC-TF or IRI-TF is also being tasked for the same interception, the same XID shall be used.

M

TargetIdentifiers

One or more of the target identifiers listed in the paragraph above.

M

DeliveryType

Set to “X2Only”, “X3Only” or “X2andX3” as needed to meet the requirements of the warrant. (NOTE: "X2Only" for IRI-POI, IRI-TF and "X3Only" for CC-TF can also be used).

M

TaskDetailsExtensions/

HeaderReporting

Header reporting-specific tag to be carried in the TaskDetailsExtensions field of ETSI TS 103 221-1 [7]. See table 6.2.3.9.2-1. Unless there is a CSP/LEA agreement to not report packet header information, this field shall be present to enable packet header information reporting.

C

ListOfDIDs

Delivery endpoints of LI_X2 or LI_X3. These delivery endpoints shall be configured using the CreateDestination message as described in ETSI TS 103 221-1 [7] clause 6.3.1 prior to first use.

M

ListOfServiceTypes

Shall be included when the task should only intercept specific CSP service types as described in clause 5.2.4. This parameter is defined in ETSI TS 103 221-1 [7], clause 6.2.1.2, table 4.

C

XID

XID assigned by LIPF.

M

TargetIdentifiers

One or more of the target identifiers listed in the paragraph above.

M

DeliveryType

Set to “X2Only”, “X3Only” or “X2andX3” as needed to meet the requirements of the warrant. (Ignored by the MDF2).

M

TaskDetailsExtensions/

HeaderReporting

Header reporting-specific tag to be carried in the TaskDetailsExtensions field of ETSI TS 103 221-1 [7]. See table 6.2.3.9.2-1. Unless there is a CSP/LEA agreement to not report packet header information, this field shall be present to enable packet header information reporting.

C

ListOfDIDs

Delivery endpoints of LI_HI2. These delivery endpoints shall be configured using the CreateDestination message as described in ETSI TS 103 221-1 [7] clause 6.3.1 prior to first use.

M

ListOfMediationDetails

Sequence of Mediation Details, See table 6.2.3-0C.

M

LIID

Lawful Intercept ID associated with the task.

M

DeliveryType

Set to "HI2Only".

M

ListOfDIDs

Details of where to send the IRI for this LIID. Shall be included if deviation from the ListofDIDs in the ActivateTask message is necessary. If included, the ListOfDIDs in the Mediation Details shall be used instead of any delivery destinations authorised by the ListOfDIDs field in the ActivateTask Message.

C

ServiceScoping

Shall be included to Identify the service(s) and associated service-related delivery settings for this LIID. May include more than one instance of this parameter to allow for different combinations of subparameters associated with a single LIID. This parameter is defined in ETSI TS 103 221-1 [7] Annex C table C.2.

C

MediationDetailsExtensions/

HeaderReporting

Header reporting-specific tag to be carried in the MediationDetailsExtensions field of ETSI TS 103 221-1 [7]. See table 6.2.3.9.2-1. This field shall be included if deviation from the taskDetails HeaderReporting TaskDetailsExtensions is required. If included, the details shall be used instead of the HeaderReporting instructions specified in the HeaderReporting field in the TaskDetails structure.

C

XID

XID assigned by LIPF.

M

TargetIdentifiers

One or more of the target identifiers listed in the paragraph above.

M

DeliveryType

Set to “X2Only”, “X3Only” or “X2andX3” as needed to meet the requirements of the warrant.

M

TaskDetailsExtensions/

HeaderReporting

Header reporting-specific tag to be carried in the TaskDetailsExtensions field of ETSI TS 103 221-1 [7]. See table 6.2.3.9.2-1. Unless there is a CSP/LEA agreement to not report packet header information, this field shall be present to enable packet header information reporting is.

C

ListOfDIDs

Delivery endpoints of LI_HI3 or LI_MDF. These delivery endpoints shall be configured using the CreateDestination message as described in ETSI TS 103 221-1 [7] clause 6.3.1 prior to first use.

M

ListOfMediationDetails

Sequence of Mediation Details, see table 6.2.3-0E.

M

LIID

Lawful Intercept ID associated with the task.

M

DeliveryType

Set to "HI3Only".

M

ListOfDIDs

Details of where to send the CC for this LIID. Shall be included if deviation from the ListofDIDs in the ActivateTask message is necessary. If included, the ListOfDIDs in the Mediation Details shall be used instead of any delivery destinations authorised by the ListOfDIDs field in the ActivateTask Message.

C

ServiceScoping

Shall be included to Identify the service(s) and associated service-related delivery settings for this LIID. May include more than one instance of this parameter to allow for different combinations of subparameters associated with a single LIID. This parameter is defined in ETSI TS 103 221-1 [7] Annex C table C.2.

C

MediationDetailsExtensions/

HeaderReporting

Header reporting-specific tag to be carried in the MediationDetailsExtensions field of ETSI TS 103 221-1 [7]. See table 6.2.3.9.2-1. This field shall be included if deviation from the taskDetails HeaderReporting TaskDetailsExtensions is required. If included, the details shall be used instead of the HeaderReporting instructions specified in the HeaderReporting field in the TaskDetails structure.

C

sUPI

SUPI associated with the PDU session (e.g. as provided by the AMF in the associated Nsmf_PDU_Session_CreateSMContext service operation). Shall be present except for PEI-only unauthenticated emergency sessions (see NOTE).

C

sUPIUnauthenticated

Shall be present if a SUPI is present in the message and set to “true” if the SUPI has not been authenticated, or “false” if it has been authenticated.

C

pEI

PEI associated with the PDU session if available (see NOTE).

C

gPSI

GPSI associated with the PDU session if available (see NOTE).

C

pDUSessionID

PDU Session ID See TS 24.501 [13] clause 9.4.

M

gTPTunnelID

Contains the F-TEID identifying the UPF endpoint of the GTP tunnel used to encapsulate the traffic derived from the UL NG-U UP TNL Information (see TS 38.413 clause 9.3.4.1), as defined in TS 29.244 [15] clause 8.2.3. Non-GTP encapsulation is for further study.

M

pDUSessionType

Identifies selected PDU session type, see TS 24.501 [13] clause 9.11.4.11.

M

sNSSAI

Slice identifiers associated with the PDU session, if available. See TS 23.003 [19] clause 28.4.2 and TS 23.501 [2] clause 5.15.2.

C

uEEndpoint

UE endpoint address(es) assigned to the PDU Session if available (see TS 29.244 [15] clause 5.21).

C

non3GPPAccessEndpoint

UE’s local IP address used to reach the N3IWF, TNGF or TWIF, if available. IP addresses are given as 4 octets (for IPv4) or 16 octets (for IPv6) with the most significant octet first (network byte order).

C

location

Location information provided by the AMF or present in the context at the SMF, if available.

C

dNN

Data Network Name requested by the target UE, as defined in TS 23.003[19] clause 9A and described in TS 23.502 [4] clause 4.3.2.2. Shall be given in dotted-label presentation format as described in TS 23.003 [19] clause 9.1.

M

aMFID

Identifier of the AMF associated with the target UE, as defined in TS 23.003 [19] clause 2.10.1 if available.

C

hSMFURI

URI of the Nsmf_PDUSession service of the selected H-SMF, if available. See TS 29.502 [16] clause 6.1.6.2.2.

C

requestType

Type of request as described in TS 24.501 [13] clause 9.11.3.47 provided within the Nsmf_PDU_Session_CreateSMContext Request (TS 29.502 [16]) message shall be reported.

In the case where the network does not support Multi Access (MA) PDU sessions, but receives a MA PDU session request, a request type of “Initial request” shall be reported.

In the case where the network does not provide a request type value for a non-MA PDU session, a request type of “initial request”, according to TS 24.501 [13] clause 6.4.1.2 shall be reported.

M

accessType

Access type associated with the session (i.e. 3GPP or non-3GPP access) if provided by the AMF (see TS 24.501 [13] clause 9.11.2.1A).

C

rATType

RAT Type associated with the access if provided by the AMF as part of session establishment (see TS 23.502 [4] clause 4.3.2). Values given as per TS 29.571 [17] clause 5.4.3.2.

C

sMPDUDNRequest

Contents of the SM PDU DN Request container, if available, as described in TS 24.501 [13] clause 9.11.4.15.

C

uEEPSPDNConnection

This IE shall be present, if available, during an EPS to 5GS Idle mode mobility or handover using the N26 interface. If present, it shall contain the EPS bearer context(s) information present in the uEEPSPDNConnection parameter of the intercepted SmContextCreateData message. (see TS 29.502 [16] clause 6.1.6.2.2).

C

ePS5GSComboInfo

Provides detailed information about PDN associated with PDU Sessions when the SMFPDUSessionEstablishment xIRI message is used to report PDU Session Establishment (see clause 6.3.3.2.2). Shall be included if the AMF has selected a SMF+PGW-C to serve the PDU session. This parameter shall include the additional IEs in Table 6.2.3-1A, if present.

C

selectedDNN

Shall be present if a DNN other than the UE requested DNN is selected for the PDU Session. Shall be given in dotted-label presentation format as described in TS 23.003 [19] clause 9.1.

C

servingNetwork

PLMN ID of the serving core network operator, and, for a Non-Public Network (NPN), the NID that together with the PLMN ID identifies the NPN. Shall be present if this IE is in the SMContextCreateData or PDUSessionCreateData message sent to the SMF or the PDU Session Context or SM Context at the SMF (see TS 29.502 [16] clauses 6.1.6.2.2, 6.1.6.2.9 and 6.1.6.2.39).

C

oldPDUSessionID

Shall be present if this IE is in the SMContextCreateData or PDUSessionCreateData message sent to the SMF or the PDU Session Context or SM Context at the SMF (see TS 29.502 [16] clauses 6.1.6.2.2, 6.1.6.2.9 and 6.1.6.2.39).

C

handoverState

Indicates whether the PDU Session Establishment being reported was due to a handover. Shall be present if this IE is in the SMContextCreatedData sent by the SMF (see TS 29.502 [16] clause 6.1.6.2.3).

C

gTPTunnelInfo

Contains the information for the User Plane GTP Tunnels for the PDU Session (see TS 29.502 [16] clauses 6.1.6.2.2, 6.1.6.2.9 and 6.1.6.2.39). See Table 6.2.3-1B.

M

pCCRules

Set of PCC rules related to traffic influence. Each PCC rule influences the routing of a given traffic flow. If several flows are concerned, then several PCC rules shall be handled by the SMF. Traffic influence policies are orginated by an AF. PCF translates these rules into PCC rules for traffic influence. The payload of a PCC rule for traffic influence is defined in Table 6.2.3-1E.

C

ePSPDNConnectionEstablishment

Provides details about PDN Connections when the SMFPDUSessionEstablishment xIRI message is used to report PDN Connection establishment. See Table 6.3.3-1 and clause 6.3.3.2.2.

C

NOTE: At least one of the SUPI, PEI or GPSI fields shall be present.

ePSSubscriberIDs

Includes the Subscriber Identities associated with the EPS PDN Connection in the UE Context sent from the MME to the AMF or known in the context at the SMF+PGW-C.See TS 29.274 [87] clause 7.2.1 and TS 23.502 [4] clause 4.11.1.

M

ePSPdnCnxInfo

Shall be present if there are any EPS PDN connections associated to the PDU Session in the SM Context or PDU Session Context at the SMF+PGW-C. Contains information about the EPS PDN connection associated with the PDU Session. See TS 29.502 [16] clause 6.1.6.2.31.

C

ePSBearerInfo

Shall be present if there are any EPS Bearers associated to the PDU Session in the SM Context or PDU Session Context at the SMF+PGW-C. Contains information about the EPS Bearer context(s) associated with the PDU Session. See TS 29.502 [16] clause 6.1.6.2.4.

C

fiveGSGTPTunnels

Shall include the 5GS GTP Tunnels (See Table 6.2.3-1C)when the xIRI message is used to report PDU Session related events.

C

ePSGTPTunnels

Shall include the information for the User Plane GTP Tunnels for the bearer context if present in the Request or Response (see TS 29.274 [87] clauses 7.2.2, 7.2.4 and 8.15) or known at the context at the SGW or PGW (see TS 23.401 [50] clause 5.6.4) when the xIRI message is used to report PDN Connection related events. See Table 6.3.3-6.

C

uLNGUUPTunnelInformation

Shall include the F-TEID for the UPF endpoint of the NG-U transport bearer (See TS 38.413 [23] clause 9.3.4.1).

C

additionalULNGUUPTunnelInformation

Shall include the F-TEID for the UPF endpoint of any additional NG-U transport bearers (See TS 38.413 [23] clause 9.3.4.1).

C

dLRANTunnelInformation

Shall include the RAN tunnel and QOS Flow information for the PDU Session (See TS 29.502 [16] clause 6.1.6.2.39 and TS 38.413 [23] clause 9.3.4.1). See Table 6.2.3-1D.

C

dLQOSFlowTunnelInformation

Shall include the F-TEID NG-RAN endpoint of the NG-U transport bearer together with associated QoS flows (See TS 38.413 [23] clause 9.3.4.2 and TS 29.502 [16] clause 6.1.6.2.39).

C

additionalDLQOSFlowTunnelInformation

Shall include the F-TEID NG-RAN endpoint of any additional NG-U transport bearers together with associated QoS flows (See TS 38.413 [23] clause 9.3.4.2 and TS 29.502 [16] clause 6.1.6.2.39).

C

redundantDLQOSFlowTunnelInformation

Shall include the F-TEID NG-RAN endpoint of redundant NG-U transport bearers together with associated QoS flows (See TS 38.413 [23] clause 9.3.4.2 and TS 29.502 [16] clause 6.1.6.2.39).

C

additionalredundantDLQOSFlowTunnelInformation

Shall include the F-TEID NG-RAN endpoint of any additional redundant NG-U transport bearers together with associated QoS flows (See TS 38.413 [23] clause 9.3.4.2 and TS 29.502 [16] clause 6.1.6.2.39).

C

pCCRuleID

Policy rule identifier. This IE is defined in TS 29.512 [89], table 5.6.2.6-1.

M

appId

Identifies an application (NOTE 1), if available. This IE is defined in TS 29.512 [89], table 5.6.2.6-1 (NOTE 1).

C

pFD

Packet flow description (PFD) associated with the appId, if available. It is defined in TS 29.551 [96] table 5.6.2.5-1 (NOTE 1).

C

flowInfos

A set of flow information, if available. A flow information is an Ethernet or IP flow packet filter information (NOTE 1). This IE is defined in TS 29.512 [89], table 5.6.2.6-1 (NOTE 1). FlowInfos may be IP flow or Ethernet flow. IP flow is specified in TS 29.214, section 5.3.8 [92]. Ethernet Flow is specified in TS 29.514 [91] Table 5.6.2.17-1.

C

appReloc

Indicates that the application cannot be relocated once a location of the application is selected by the 5GC when it is included and set to "true". The default value is "false".

C

simConnInd

Indication of simultaneous connectivity temporarily maintained for the source and target PSA (PDU Session Anchor). If it is included and set to "true", temporary simultaneous connectivity should be kept. The default value "false" applies, if the IE is not present. This IE is defined in TS 29.512 [89], table 5.6.2.9-1.

C

simConnTerm

Indication of the minimum time interval to be considered for inactivity of the traffic routed via the source PSA during the edge re-location procedure. It may be included when the "simConnInd" attribute is set to true. This IE is defined in TS 29.512 [89], table 5.6.2.9-1.

C

maxAllowedUpLat

Indicates the target user plane latency in units of milliseconds used by SMF to decide whether edge relocation is needed to ensure that the user plane latency does not exceed the value. This IE is defined in TS 29.512 [89], table 5.6.2.9-1, if available.

C

routeToLocs

A set of traffic routes, if available. A traffic route provides information to route to/from a DNAI. This IE is defined in TS 29.512 [89], table 5.6.2.9-1 (NOTE 2).

C

trafficSteeringPolIdDl

Traffic steering policy for downlink traffic at the SMF, if available. This IE is defined in TS 29.512 [89], table 5.6.2.9-1 (NOTE 2).

C

trafficSteeringPolIdUl

Traffic steering policy for uplink traffic at the SMF, if available. This IE is defined in TS 29.512 [89], table 5.6.2.9-1 (NOTE 2).

C

sourceDNAI

No longer used in present version of this specification

O

targetDNAI

No longer used in present version of this specification

O

dNAIChangeType

No longer used in present version of this specification

O

sourceUEIPAddress

No longer used in present version of this specification

O

targetUEIPAddress

No longer used in present version of this specification

O

eASIPReplaceInfos

Contains EAS IP replacement information for a Source and a Target EAS, if available. This IE is defined in TS 29.571 [17], table 5.4.4.79.

C

NOTE 1: Either appId/pFD or flowInfos shall be supplied.

NOTE 2: TrafficSteeringPolIdDl attribute and/or trafficSteeringPolIdUl attribute and routeToLocs attribute are mutually exclusive.

sUPI

SUPI associated with the PDU session (e.g. as provided by the AMF in the associated Nsmf_PDU_Session_CreateSMContext service operation). Shall be present except for PEI-only unauthenticated emergency sessions.

C

sUPIUnauthenticated

Shall be present if a SUPI is present in the message and set to “true” if the SUPI was not authenticated, or “false” if it has been authenticated.

C

pEI

PEI associated with the PDU session if available.

C

gPSI

GPSI associated with the PDU session if available.

C

sNSSAI

Slice identifier associated with the PDU session, if available. See TS 23.003 [19] clause 28.4.2 and TS 23.501 [2] clause 5.15.2.

C

non3GPPAccessEndpoint

UE’s local IP address used to reach the N3IWF, TNGF or TWIF, if available. IP addresses are given as 4 octets (for IPv4) or 16 octets (for IPv6) with the most significant octet first (network byte order).

C

location

Location information provided by the AMF or present in the context at the SMF, if available.

C

requestType

Type of request as described in TS 24.501 [13] clause 9.11.3.47 if available.

C

accessType

Access type associated with the session (i.e. 3GPP or non-3GPP access) if provided by the AMF (see TS 24.501 [13] clause 9.11.2.1A).

C

rATType

RAT type associated with the access, if available. Values given as per TS 29.571 [17] clause 5.4.3.2.

C

pDUSessionID

PDU Session ID See TS 24.501 [13] clause 9.4. This parameter is conditional only for backwards compatibility.

C

ePS5GSComboInfo

Provides detailed information about PDN Connections associated with PDU Sessions when the SMFPDUSessionEstablishment xIRI message is used to report PDU Session Establishment (see clause 6.3.3.2.2). Shall be included when the AMF has selected a SMF+PGW-C to serve the PDU session. This parameter may include the additional IEs in Table 6.2.3-1A, when available.

C

uEEndpoint

UE IP address(es) assigned to the PDU Session if available (See TS 29.244 [15] clause 5.21).

C

servingNetwork

Shall be present if this IE is in the SMContextUpdateData, HsmfUpdateData or message sent to the SMF or the PDU Session Context or SM Context at the SMF (see TS 29.502 [16] clauses 6.1.6.2.3, 6.1.6.2.11 and 6.1.6.2.39).

C

handoverState

Indicates whether the PDU Session Modification being reported was due to a handover. Shall be present if this IE is in the SMContextUpdatedData or sent by the SMF (see TS 29.502 [16] clause 6.1.6.2.3).

C

gTPTunnelInfo

Contains the information for the User Plane GTP Tunnels for the PDU Session (see TS 29.502 [16] clauses 6.1.6.2.2, 6.1.6.2.9 and 6.1.6.2.39). See Table 6.2.3-1B.

M

pCCRules

Set of PCC rules related to traffic influence. Each PCC rule influences the routing of a given traffic flow. If several flows are concerned, then several PCC rules shall be handled by the SMF. Traffic influence policies are orginated by an AF. PCF translates these rules into PCC rules for traffic influence, if available. The payload of a PCC rule for traffic influence is defined in Table 6.2.3-1E.

C

ePSPDNConnectionModification

Provides details about PDN Connections when the SMFPDUSessionModification xIRI message is used to report PDN Connection Modification. See Table 6.3.3-8 and clause 6.3.3.2.3.

C

uPPathChange

Notification of the UPPathChange event. This IE is defined in TS 29.508 [90], if available, Table 5.6.2.5-1.

C

pFDDataForApp

Represents the packet flow descriptions (PFDs) for an application identifier (AppId), if available. This IE is defined in TS 29.551 [96], Table 5.6.2.2-1.

C

sourceDNAI

Source DNAI, if the DNAI has changed. DNAI represents the location of applications towards which the traffic routing should apply, if available.

C

targetDNAI

Target DNAI if the DNAI has changed.

C

dNAIChangeType

Type of a DNAI change. Possible values are “early”, “late” and “earlyAndLate” notification of UP path reconfiguration, if available.

C

sourceUEIPAddress

The IPv4 Address of the served UE for the source DNAI, if available.

C

targetUEIPAddress

The IPv4 Address of the served UE for the target DNAI, if available.

C

sourceTrafficRouting

N6 traffic routing information for the source DNAI, if available.

C

targetTrafficRouting

N6 traffic routing information for the target DNAI, if available.

C

mACAddress

The MAC address of the served UE, if available.

C

appId

Identifier of an application.

M

pFDs

PFDs for an application identifier, if available. PFD is defined in TS 29.551 [96], Table 5.6.2.5-1.

C

pFDId

PFD identifier.

M

pFDflowDescription

Represents a set of 3-tuple with protocol, server IP address and server port for UL/DL application traffic, if available.

C

uRLs

Represents a set of URL, if available.

C

domainNames

Represents a set of FQDN, if available.

C

dnProtocol

Indicates the additional protocol and protocol field for domain names to be matched, if available. This IE is defined in 29.122 [63], Table 5.14.2.2.4-1.

C

sUPI

SUPI associated with the PDU session.

M

pEI

PEI associated with the PDU session if available.

C

gPSI

GPSI associated with the PDU session if available.

C

pDUSessionID

PDU Session ID as assigned by the AMF.

M

timeOfFirstPacket

Time of first packet for the PDU session.

C

timeOfLastPacket

Time of last packet for the PDU session.

C

uplinkVolume

Number of uplink octets for the PDU session.

C

downlinkVolume

Number of downlink octets for the PDU session.

C

location

Location information, if available.

C

cause

Indicates the NF Service Consumer cause for the requested PDU session release (see TS 29.502 [16] clause 6.1.6.3.8 for enumerated cause information). Include if known.

C

ePS5GSComboInfo

Provides detailed information about PDN Connections associated with PDU Sessions when the SMFPDUSessionEstablishment xIRI message is used to report PDU Session Establishment (see clause 6.3.3.2.2). This parameter may include the additional IEs in Table 6.2.3-1A, when available.

C

nGAPCause

Indicates the NGAP cause for the requested SM context release (see TS 29.502 [16] clause 6.1.6.2.6). Shall be derived as described in TS 29.571 [17] clause 5.4.4.12.

C

fiveGMMCause

Indicates the 5GMM cause for a PDU Session released due to any 5GMM failure (see 29.502 [16] clause 6.1.6.2.6). Shall be sent as an integer derived as described in TS 29.571 [17] clause 5.4.2.

C

pCCRuleIDs

PCC rule IDs of the PCC rules related to traffic influence that are associated to the PDU session and active at the time the PDU session is released.

C

ePSPDNConnectionRelease

Provides details about PDN Connections when the SMFPDUSessionRelease xIRI message is used to report PDN Connection Release. See Table 6.3.3-13 and clause 6.3.3.2.4.

C

sUPI

SUPI associated with the PDU session (e.g. as provided by the AMF in the associated Nsmf_PDU_Session_CreateSMContext service operation). Shall be present except for PEI-only unauthenticated emergency sessions.

C

sUPIUnauthenticated

Shall be present if a SUPI is present in the message and set to “true” if the SUPI has not been authenticated, or “false” if it has been authenticated.

C

pEI

PEI associated with the PDU session if available.

C

gPSI

GPSI associated with the PDU session if available.

C

pDUSessionID

PDU Session ID as assigned by the AMF, as defined in TS 24.007 [14] clause 11.2.3.1b.

M

gTPTunnelID

Contains the F-TEID identifying the UPF endpoint of the GTP tunnel used to encapsulate the traffic derived from the UL NG-U UP TNL Information (see TS 38.413 clause 9.3.4.1), as defined in TS 29.244 [15] clause 8.2.3. Non-GTP encapsulation is for further study.

M

pDUSessionType

Identifies selected PDU session type, see TS 24.501 [13] clause 9.11.4.11.

M

sNSSAI

Slice identifier associated with the PDU session, if available. See TS 23.003 [19] clause 28.4.2 and TS 23.501 [2] clause 5.15.2.

C

uEEndpoint

UE endpoint address(es) if available. IP addresses are given as 4 octets (for IPv4) or 16 octets (for IPv6) with the most significant octet first (network byte order). MAC addresses are given as 6 octets with the most significant octet first (see TS 29.244 [15] clause 5.21).

C

non3GPPAccessEndpoint

UE’s local IP address used to reach the N3IWF, TNGF or TWIF, if available. IP addresses are given as 4 octets (for IPv4) or 16 octets (for IPv6) with the most significant octet first (network byte order).

C

location

Location information provided by the AMF at session establishment or present in the context at the SMF, if available.

C

dNN

Data Network Name associated with the target traffic, as defined in TS 23.003 [19] clause 9A and described in TS 23.502 [4] clause 4.3.2.2. Shall be given in dotted-label presentation format as described in TS 23.003 [19] clause 9.1.

M

aMFID

Identifier of the AMF associated with the target UE, as defined in TS 23.003 [19] clause 2.10.1, if available.

C

hSMFURI

URI of the Nsmf_PDUSession service of the selected H-SMF, if available. See TS 29.502 [16] clause 6.1.6.2.2.

C

requestType

Type of request as initially set within the PDU SESSION ESTABLISHMENT as described in TS 24.501 [13] clause 9.11.3.47.
If the initial value is no longer available the request type shall be set to “existing PDU session”.

M

accessType

Access type associated with the session (i.e. 3GPP or non-3GPP access) if provided by the AMF (see TS 24.501 [13] clause 9.11.2.1A).

C

rATType

RAT type associated with the access if provided by the AMF as part of session establishment (see TS 23.502 [4] clause 4.3.2). Values given as per TS 29.571 [17] clause 5.4.3.2.

C

sMPDUDNRequest

Contents of the SM PDU DN request container, if available, as described in TS 24.501 [13] clause 9.11.4.15.

C

timeOfSessionEstablishment

Time at which the session establishment occurred, if available. Shall be given qualified with time zone information (i.e. as UTC or offset from UTC, not as local time).

C

ePS5GSComboInfo

Provides detailed information about PDN Connections associated with PDU Sessions when the SMFPDUSessionEstablishment xIRI message is used to report PDU Session Establishment (see clause 6.3.3.2.2). Shall be included when the AMF has selected a SMF+PGW-C to serve the PDU session. This parameter may include the additional IEs in table 6.2.3-1A, if available.

C

uEEPSPDNConnection

This IE shall be present, if available, during an EPS to 5GS Idle mode mobility or handover using the N26 interface. If present, it shall contain the EPS bearer context(s) information present in the uEEPSPDNConnection parameter of the intercepted SmContextCreateData message. (see TS 29.502 [16] clause 6.1.6.2.2).

C

servingNetwork

Indicates the serving core network operator PLMN, and for an SNPN, the NID. Shall be present if present in the PDU Session Context or SM Context at the SMF (see TS 29.502 [16] clause 6.1.6.2.39).

C

gTPTunnelInfo

Contains the information for the User Plane GTP Tunnels for the PDU Session (see TS 29.502 [16] clauses 6.1.6.2.2, 6.1.6.2.9 and 6.1.6.2.39). See Table 6.2.3-1B.

M

pCCRules

Set of PCC rules related to traffic influence. Each PCC rule influences the routing of a given traffic flow. If several flows are concerned, then several PCC rules shall be handled by the SMF. Traffic influence policies are orginated by an AF. PCF translates these rules into PCC rules for traffic influence. The payload of a PCC rule for traffic influence is defined in Table 6.2.3-1E.

C

ePSStartOfInterceptionWithEstablishedPDNConnection

Provides details about PDN Connections when the SMFStartOfInterceptionWithEstablishedPDUSession xIRI message is used to report the start of interception on a target who already has existing PDN Connections. See Table 6.3.3-14 and clause 6.3.3.2.5.

C

pFDDataForApps

Represents a set of associations between application identifier and packet flow descriptions (PFDs), if available.

C

failedProcedureType

Specifies the procedure which failed or is aborted at the SMF.

M

failureCause

Provides the value of the 5GSM cause, see TS 24.501 [13] clause 9.11.4.2. In case the procedure is aborted due to a 5GSM STATUS message, the 5GSM cause is the one included in the 5GSM status message.

M

requestedSlice

Slice requested for the procedure, if available, given as a NSSAI (a list of S-NSSAI values as described in TS 24.501 [13] clause 9.11.3.37).

C

initiator

Specifies whether the network (SMF) or the UE is initiating the rejection or indicating the failure.

M

sUPI

SUPI associated with the procedure, if available (see NOTE).

C

sUPIUnauthenticated

Shall be present if a SUPI is present in the message and set to “true” if the SUPI has not been authenticated, or “false” if it has been authenticated.

C

pEI

PEI used in the procedure, if available (see NOTE).

C

gPSI

GPSI used in the procedure, if available (see NOTE).

C

pDUSessionID

PDU Session ID See clause 9.4 of TS 24.501 [13], if available.

C

uEEndpoint

UE endpoint address(es) if available.

C

non3GPPAccessEndpoint

UE’s local IP address used to reach the N3IWF, TNGF or TWIF, if available.

C

location

Location information provided by the AMF or present in the context at the SMF, if available.

C

dNN

Data Network Name associated with the target traffic, as defined in TS 23.003 [19] clause 9A and described in TS 23.501 [2] clause 4.3.2.2, if available. Shall be given in dotted-label presentation format as described in TS 23.003 [19] clause 9.1.

C

aMFID

Identifier of the AMF associated with the target UE, as defined in TS 23.003 [19] clause 2.10.1 when available.

C

hSMFURI

URI of the Nsmf_PDUSession service of the selected H-SMF, if available. See TS 29.502 [16] clause 6.1.6.2.2.

C

requestType

Type of request as described in TS 24.501 [13] clause 9.11.3.47, if available.

Otherwise depending on the REJECT event the following request type shall be reported:
PDU SESSION ESTABLISHMENT REJECT: The request type shall be set to the one reported within the PDU SESSION ESTABLISHMENT or if there hasn’t been one reported or is no longer available it should be set to "initial request".
PDU SESSION MODIFICATION REJECT: "modification request”.
PDU SESSION RELEASE REJECT: no request type shall be set.
PDU SESSION MODIFICATION COMMAND REJECT: "modification request”.

C

accessType

Access type associated with the session (i.e. 3GPP or non-3GPP access) if provided by the AMF (see TS 24.501 [13] clause 9.11.2.1A).

C

rATType

RAT Type associated with the access if provided by the AMF as part of session establishment (see TS 23.502 [4] clause 4.3.2). Values given as per TS 29.571 [17] clause 5.4.3.2.

C

sMPDUDNRequest

Contents of the SM PDU DN Request container, if available, as described in TS 24.501 [13] clause 9.11.4.15.

C

NOTE: At least one identity shall be provided, the others shall be provided if available.

sUPI

SUPI associated with the PDU session (e.g. as provided by the AMF in the associated Nsmf_PDU_Session_CreateSMContext service operation). Shall be present except for PEI-only unauthenticated emergency sessions (see NOTE).

C

sUPIUnauthenticated

Shall be present if a SUPI is present in the message and set to “true” if the SUPI has not been authenticated, or “false” if it has been authenticated.

C

pEI

PEI associated with the PDU session if available (see NOTE).

C

gPSI

GPSI associated with the PDU session if available (see NOTE).

C

pDUSessionID

PDU Session ID See clause 9.4 of TS 24.501 [13]. Identifies a new PDU session.

M

pDUSessionType

Identifies selected PDU session type, see TS 24.501 [13] clause 9.11.4.11.

M

accessInfo

Identifies the access(es) associated with the PDU session including the information for each specific access (see table 6.2.3-5B)

M

sNSSAI

Slice identifiers associated with the PDU session, if available. See TS 23.003 [19] clause 28.4.2 and TS 23.501 [2] clause 5.15.2.

C

uEEndpoint

UE endpoint address(es) assigned to the PDU Session if available (see TS 29.244 [15] clause 5.21).

C

location

Location information provided by the AMF or present in the context at the SMF, if available.

C

dNN

Data Network Name requested by the target UE, as defined in TS 23.003 [19] clause 9A and described in TS 23.502 [4] clause 4.3.2.2. Shall be given in dotted-label presentation format as described in TS 23.003 [19] clause 9.1.

M

aMFID

Identifier of the AMF associated with the target UE, as defined in TS 23.003 [19] clause 2.10.1 when available.

C

hSMFURI

URI of the Nsmf_PDUSession service of the selected H-SMF, if available. See TS 29.502 [16] clause 6.1.6.2.2.

C

requestType

Type of request as described in TS 24.501 [13] clause 9.11.3.47 provided within the Nsmf_PDU_Session_CreateSMContext Request (TS 29.502 [16]) message shall be reported.

In the case where the network does not provide a request type value for a MA PDU session and the network does support MA PDU sessions, the request type shall be set to “MA PDU request” according to TS 24.501 [13] clause 6.4.1.2.

M

sMPDUDNRequest

Contents of the SM PDU DN Request container, if available, as described in TS 24.501 [13] clause 9.11.4.15.

C

servingNetwork

PLMN ID of the serving core network operator, and, for a Non-Public Network (NPN), the NID that together with the PLMN ID identifies the NPN.

M

oldPDUSessionID

The old PDU Session ID received from the UE. See TS 23.502 [4] clauses 4.3.2.2.1 and 4.3.5.2 and TS 24.501 [13] clause 6.4.1.2. Shall be present if this IE is in the SMContextCreateData or PDUSessionCreateData message sent to the SMF or the PDU Session Context or SM Context at the SMF (see TS 29.502 [16] clauses 6.1.6.2.2, 6.1.6.2.9 and 6.1.6.2.39).

C

mAUpgradeIndication

Indicates whether the PDU session is allowed to be upgraded to MA-Confirmed MA PDU session (see TS 23.502 [4] clause 4.22.3). Include if known.

C

ePSPDNCnxInfo

Indicates if the PDU session may be moved to EPS during its lifetime (see TS 29.502 [16] clause 6.1.6.2.31). Include if known.

C

mAAcceptedIndication

Indicates that a request to establish an MA PDU session was accepted or if a single access PDU session request was upgraded into a MA PDU session (see TS 23.502 [4] clauses 4.22.2 and 4.22.3).

It shall be set as follows:

– true: MA-Confirmed MA PDU session was established

– false: single access MA-Upgrade-Allowed MA PDU session was established that may be upgraded to an MA-Confirmed MA PDU session.

M

aTSSSContainer

Identifies the steering, switching, and splitting features for the MA-Confirmed MA PDU session. Also indicates whether MPTCP or ATSSS-LL is to be used for ATSSS. See TS 24.501[13] clause 9.11.4.22.

C

uEEPSPDNConnection

This IE shall be present, if available, during an EPS to 5GS Idle mode mobility or handover using the N26 interface. If present, it shall contain the EPS bearer context(s) information present in the uEEPSPDNConnection parameter of the intercepted SmContextCreateData message. (see TS 29.502 [16] clause 6.1.6.2.2).

C

ePS5GSComboInfo

Provides detailed information about PDN Connections and PDU Sessions during EPS to 5GS idle mode mobility or handover using the N26 interface. Shall be included if the AMF has selected a SMF+PGW-C to serve the PDU session. This parameter shall include the additional IEs in Table 6.2.3-1A, if present.

C

selectedDNN

Shall be present if a DNN other than the UE requested DNN is selected for the PDU Session. Shall be given in dotted-label presentation format as described in TS 23.003 [19] clause 9.1.

C

handoverState

Indicates whether the PDU Session Establishment being reported was due to a handover. Shall be present if this IE is in the SMContextCreatedData sent by the SMF (see TS 29.502 [16] clause 6.1.6.2.3).

C

pCCRules

Set of PCC rules related to traffic influence. Each PCC rule influences the routing of a given traffic flow. If several flows are concerned, then several PCC rules shall be handled by the SMF. Traffic influence policies are orginated by an AF. PCF translates these rules into PCC rules for traffic influence. The payload of a PCC rule for traffic influence is defined in Table 6.2.3-1E.

C

ePSPDNConnectionEstablishment

Provides details about PDN Connections when the SMFMAPDUSessionEstablishment xIRI message is used to report PDN Connection establishment. See table 6.3.3-1 and clause 6.3.3.2.2.

C

NOTE: At least one of the SUPI, PEI or GPSI fields shall be present.

accessType

Access type associated with the session (i.e. 3GPP or non-3GPP access) as provided by the AMF (see TS 24.501 [13] clause 9.11.2.1A).

M

rATType

RAT Type associated with the access as provided by the AMF as part of session establishment (see TS 23.502 [4] clause 4.3.2). Values given as per TS 29.571 [17] clause 5.4.3.2.

C

gTPTunnelID

Contains the F-TEID identifying the GTP tunnel used to encapsulate the traffic, as defined in TS 29.244 [15] clause 8.2.3. Non-GTP encapsulation is for further study.

M

non3GPPAccessEndpoint

UE’s local IP address used to reach the N3IWF, TNGF or TWIF, if available. IP addresses are given as 4 octets (for IPv4) or 16 octets (for IPv6) with the most significant octet first (network byte order).

C

establishmentStatus

Indicates whether the access type is established or released.

M

aNTypeToReactivate

Indicates the Access Network Type for which the UP connection is requested to be re-activated, for an MA PDU session. Applicable to session modification reporting.

C

gTPTunnelInfo

Contains the information for the User Plane GTP Tunnels for the PDU Session (see TS 29.502 [16] clauses 6.1.6.2.2, 6.1.6.2.9 and 6.1.6.2.39). See Table 6.2.3-1B.

M

sUPI

SUPI associated with the PDU session (e.g. as provided by the AMF in the associated Nsmf_PDU_Session_CreateSMContext service operation). Shall be present except for PEI-only unauthenticated emergency sessions.

C

sUPIUnauthenticated

Shall be present if a SUPI is present in the message, and set to “true” if the SUPI was not authenticated, or “false” if it has been authenticated.

C

pEI

PEI associated with the PDU session if available.

C

gPSI

GPSI associated with the PDU session if available.

C

pDUSessionID

PDU Session ID, see TS 24.501 [13] clause 9.4.

M

accessInfo

Identifies the access(es) associated with the PDU session including the information for each specific access (see table 6.2.3-5B) being modified.

C

sNSSAI

Slice identifier associated with the PDU session, if available. See TS 23.003 [19] clause 28.4.2 and TS 23.501 [2] clause 5.15.2.

C

location

Location information provided by the AMF or present in the context at the SMF, if available.

C

requestType

For both a UE- as well as a network-requested PDU session, the POI (SMF) shall set the request type parameter to "modification request".

C

servingNetwork

PLMN ID of the serving core network operator, and, for a Non-Public Network (NPN), the NID that together with the PLMN ID identifies the NPN.

M

oldPDUSessionID

The old PDU Session ID received from the UE. See TS 23.502 [4] clauses 4.3.2.2.1 and 4.3.5.2 and TS 24.501 [13] clause 6.4.1.2. Shall be present if this IE is in the SMContextCreateData or PDUSessionCreateData message sent to the SMF or the PDU Session Context or SM Context at the SMF (see TS 29.502 [16] clauses 6.1.6.2.2, 6.1.6.2.9 and 6.1.6.2.39).

C

mAUpgradeIndication

Indicates whether the PDU session is allowed to be upgraded to MA PDU session (see TS 23.502 [4] clause 4.22.3). Include if known.

C

ePSPDNCnxInfo

Indicates if the PDU session may be moved to EPS during its lifetime (see TS 29.502 [16] clause 6.1.6.2.31). Include if known.

C

mAAcceptedIndication

Indicates that a request to establish an MA PDU session was accepted or if a single access PDU session request was upgraded into a MA PDU session (see clauses 4.22.2 and 4.22.3 of TS 23.502 [4]).

It shall be set as follows:

– true: MA-Confirmed MA PDU session was established

– false: single access MA-Upgrade-Allowed MA PDU session was established that may be upgraded to an MA-Confirmed MA PDU session.

M

aTSSSContainer

Identifies the steering, switching, and splitting features for the MA-Confirmed MA PDU session. Also indicates whether MPTCP or ATSSS-LL is to be used for ATSSS. See clause 9.11.4.22 of TS 24.501 [13].

C

uEEPSPDNConnection

This IE shall be present, if available, during an EPS to 5GS Idle mode mobility or handover using the N26 interface. If present, it shall contain the EPS bearer context(s) information present in the uEEPSPDNConnection parameter of the intercepted SmContextCreateData message (see TS 29.502 [16] clause 6.1.6.2.2).

C

ePS5GSComboInfo

Provides detailed information about PDN Connections and PDU Sessions during EPS to 5GS idle mode mobility or handover using the N26 interface. Shall be included if the AMF has selected a SMF+PGW-C to serve the PDU session. This parameter shall include the additional IEs in Table 6.2.3-1A, if present.

C

handoverState

Indicates whether the PDU Session Establishment being reported was due to a handover. Shall be present if this IE is in the SMContextCreatedData sent by the SMF (see TS 29.502 [16] clause 6.1.6.2.3).

C

pCCRules

Set of PCC rules related to traffic influence. Each PCC rule influences the routing of a given traffic flow. If several flows are concerned, then several PCC rules shall be handled by the SMF. Traffic influence policies are orginated by an AF. PCF translates these rules into PCC rules for traffic influence. The payload of a PCC rule for traffic influence is defined in Table 6.2.3-1E.

C

uPPathChange

Notification of the UPPathChange event, if available. This IE is defined in TS 29.508 [90], Table 5.6.2.5-1.

C

pFDDataForApp

Represents the packet flow descriptions (PFDs) for an application identifier (AppId), if available. This IE is defined in TS 29.551 [96], Table 5.6.2.2-1.

C

ePSPDNConnectionModification

Provides details about PDN Connections when the SMFMAPDUSessionModification xIRI message is used to report PDN Connection Establishment or Modification. See table 6.3.3-8 and clause 6.3.3.2.3.

C

sUPI

SUPI associated with the PDU session.

M

pEI

PEI associated with the PDU session if available.

C

gPSI

GPSI associated with the PDU session if available.

C

pDUSessionID

PDU Session ID as assigned by the AMF.

M

timeOfFirstPacket

Time of first packet for the PDU session.

C

timeOfLastPacket

Time of last packet for the PDU session.

C

uplinkVolume

Number of uplink octets for the PDU session.

C

downlinkVolume

Number of downlink octets for the PDU session.

C

location

Location information, if available.

C

cause

Indicates the NF Service Consumer cause for the requested PDU session release (see TS 29.502 [16] clause 6.1.6.3.8 for enumerated cause information). Include if known.

C

nGAPCause

Indicates the NGAP cause for the requested SM context release (see TS 29.502 [16] clause 6.1.6.2.6). Shall be derived as described in TS 29.571 [17] clause 5.4.4.12.

C

fiveGMMCause

Indicates the 5GMM cause for a PDU Session released due to any 5GMM failure (see 29.502 [16] clause 6.1.6.2.6). Shall be sent as an integer derived as described in TS 29.571 [17] clause 5.4.2.

C

pCCRulesIDs

PCC rule IDs of the PCC rules related to traffic influence that are associated to the PDU session and active at the time the PDU session is released.

C

ePSPDNConnectionRelease

Provides details about PDN Connections when the SMFMAPDUSessionRelease xIRI message is used to report PDN Connection Release. See table 6.3.3-13 and clause 6.3.3.2.4.

C

sUPI

SUPI associated with the PDU session (e.g. as provided by the AMF in the associated Nsmf_PDU_Session_CreateSMContext service operation). Shall be present except for PEI-only unauthenticated emergency sessions.

C

sUPIUnauthenticated

Shall be present if a SUPI is present in the message and set to “true” if the SUPI has not been authenticated, or “false” if it has been authenticated.

C

pEI

PEI associated with the PDU session if available.

C

gPSI

GPSI associated with the PDU session if available.

C

pDUSessionID

PDU Session ID as assigned by the AMF, as defined in TS 24.007 [14] clause 11.2.3.1b.

M

pDUSessionType

Identifies selected PDU session type, see TS 24.501 [13] clause 9.11.4.11.

M

accessInfo

Identifies the access(es) associated with the PDU session including the information for each specific access (see table 6.2.3-5B).

M

sNSSAI

Slice identifier associated with the PDU session, if available. See TS 23.003 [19] clause 28.4.2 and TS 23.501 [2] clause 5.15.2.

C

uEEndpoint

UE endpoint address(es) if available. IP addresses are given as 4 octets (for IPv4) or 16 octets (for IPv6) with the most significant octet first (network byte order). MAC addresses are given as 6 octets with the most significant octet first (see TS 29.244 [15] clause 5.21).

C

location

Location information provided by the AMF at session establishment or present in the context at the SMF, if available.

C

dNN

Data Network Name associated with the target traffic, as defined in TS 23.003 [19] clause 9A and described in TS 23.502 [4] clause 4.3.2.2. Shall be given in dotted-label presentation format as described in TS 23.003 [19] clause 9.1.

M

aMFID

Identifier of the AMF associated with the target UE, as defined in TS 23.003 [19] clause 2.10.1, if available.

C

hSMFURI

URI of the Nsmf_PDUSession service of the selected H-SMF, if available. See TS 29.502 [16] clause 6.1.6.2.2.

C

requestType

Type of request as initially set within PDU SESSION ESTABLISHMENT as described in TS 24.501 [13] clause 9.11.3.47.

If the initial value is no longer available the request type shall be set to “existing PDU session”.

C

sMPDUDNRequest

Contents of the SM PDU DN request container, if available, as described in TS 24.501 [13] clause 9.11.4.15.

C

servingNetwork

PLMN ID of the serving core network operator, and, for a Non-Public Network (NPN), the NID that together with the PLMN ID identifies the NPN.

M

oldPDUSessionID

The old PDU Session ID received from the UE. See TS 23.502 [4] clauses 4.3.2.2.1 and 4.3.5.2 and TS 24.501 [13] clause 6.4.1.2. Include if known.

C

mAUpgradeIndication

Indicates whether the PDU session is allowed to be upgraded to MA PDU session (see TS 23.502 [4] clause 4.22.3). Include if known.

C

ePSPDNCnxInfo

Indicates if the PDU session may be moved to EPS during its lifetime (see TS 29.502 [16] clause 6.1.6.2.31). Include if known.

C

mAAcceptedIndication

Indicates that a request to establish an MA PDU session was accepted or if a single access PDU session request was upgraded into an MA PDU session (see TS 23.502 [4] clauses 4.22.2 and 4.22.3).

It shall be set as follows:

– true: MA-Confirmed MA PDU session was established.

– false: single access MA-Upgrade-Allowed MA PDU session was established that may be upgraded to an MA-Confirmed MA PDU session.

M

aTSSSContainer

Identifies the steering, switching, and splitting features for the MA-Confirmed MA PDU session. Also indicates whether MPTCP or ATSSS-LL is to be used for ATSSS. See TS 24.501 [13] clause 9.11.4.22.

C

ePS5GSComboInfo

Provides detailed information about PDN Connections and PDU Sessions during EPS to 5GS idle mode mobility or handover using the N26 interface. Shall be included when the AMF has selected a SMF+PGW-C to serve the PDU session. This parameter may include the additional IEs in table 6.2.3-1A, if available.

C

uEEPSPDNConnection

This IE shall be present, if available, during an EPS to 5GS Idle mode mobility or handover using the N26 interface. If present, it shall contain the EPS bearer context(s) information present in the uEEPSPDNConnection parameter of the intercepted SmContextCreateData message. (see TS 29.502 [16] clause 6.1.6.2.2).

C

pCCRules

Set of PCC rules related to traffic influence. Each PCC rule influences the routing of a given traffic flow. If several flows are concerned, then several PCC rules shall be handled by the SMF. Traffic influence policies are orginated by an AF. PCF translates these rules into PCC rules for traffic influence. The payload of a PCC rule for traffic influence is defined in Table 6.2.3-1E.

C

pFDDataForApps

Represents a set of associations between application identifier and packet flow descriptions (PFDs), if available.

C

ePSStartOfInterceptionWithEstablishedPDNConnection

Provides details about PDN Connections when the SMFStartOfInterceptionWithEstablishedMAPDUSession xIRI message is used to report the start of interception on a target who already has existing PDN Connections. See table 6.3.3-14 and clause 6.3.3.2.5.

C

failedProcedureType

Specifies the procedure which failed or is aborted at the SMF.

M

failureCause

Provides the value of the 5GSM cause, see TS 24.501 [13], clause 9.11.4.2. In case the procedure is aborted due to a 5GSM STATUS message, the 5GSM cause is the one included in the 5GSM status message.

M

requestedSlice

Slice requested for the procedure, if available, given as a NSSAI (a list of S-NSSAI values as described in TS 24.501 [13] clause 9.11.3.37).

C

initiator

Specifies whether the network (SMF) or the UE is initiating the rejection or indicating the failure.

M

sUPI

SUPI associated with the procedure, if available (see NOTE).

C

sUPIUnauthenticated

Shall be present if a SUPI is present in the message and set to “true” if the SUPI has not been authenticated, or “false” if it has been authenticated.

C

pEI

PEI used in the procedure, if available (see NOTE).

C

gPSI

GPSI used in the procedure, if available (see NOTE).

C

pDUSessionID

PDU Session ID, see TS 24.501 [13] clause 9.4, if available.

C

accessInfo

Identifies the access(es) associated with the PDU session including the information for each specific access (see table 6.2.3-5B).

M

uEEndpoint

UE endpoint address(es) if available.

C

location

Location information provided by the AMF or present in the context at the SMF, if available.

C

dNN

Data Network Name associated with the target traffic, as defined in TS 23.003 [19] clause 9A and described in TS 23.501 [2] clause 4.3.2.2, if available. Shall be given in dotted-label presentation format as described in TS 23.003 [19] clause 9.1.

C

aMFID

Identifier of the AMF associated with the target UE, as defined in TS 23.003 [19] clause 2.10.1 when available.

C

hSMFURI

URI of the Nsmf_PDUSession service of the selected H-SMF, if available. See TS 29.502 [16] clause 6.1.6.2.2.

C

requestType

Type of request as described in TS 24.501 [13] clause 9.11.3.47, if available.

Otherwise depending on the REJECT event the following request type shall be reported:

PDU SESSION ESTABLISHMENT REJECT: The request type shall be set to the one reported within the PDU SESSION ESTABLISHMENT or if there hasn’t been one reported it should be set to "MA PDU request".

PDU SESSION MODIFICATION REJECT: "modification request”.

PDU SESSION RELEASE REJECT: no request type shall be set.

PDU SESSION MODIFICATION COMMAND REJECT: "modification request”.

C

sMPDUDNRequest

Contents of the SM PDU DN Request container, if available, as described in TS 24.501 [13] clause 9.11.4.15.

C

NOTE: At least one identity shall be provided, the others shall be provided if available.

sUPI

SUPI associated with the PDU session (e.g. as provided by the AMF in the associated Nsmf_PDU_Session_CreateSMContext service operation). Shall be present except for PEI-only unauthenticated emergency sessions.

C

sUPIUnauthenticated

Shall be present if a SUPI is present in the message and set to true if the SUPI was not authenticated, or false if it has been authenticated.

C

pEI

PEI associated with the PDU session if available.

C

gPSI

GPSI associated with the PDU session if available.

C

sNSSAI

Slice identifier associated with the PDU session, if available. See TS 23.003 [19] clause 28.4.2 and TS 23.501 [2] clause 5.15.2.

C

non3GPPAccessEndpoint

UE’s local IP address used to reach the N3IWF, TNGF or TWIF, if available. IP addresses are given as 4 octets (for IPv4) or 16 octets (for IPv6) with the most significant octet first (network byte order).

C

location

Location information provided by the AMF or present in the context at the SMF, if available.

C

requestType

In accordance with the request type as described in TS 24.501 [13] clause 6.4.2.2 and clause 9.11.3.47 a request type of “modification request” shall be reported.

M

accessType

Access type associated with the session (i.e. 3GPP or non-3GPP access) if provided by the AMF (see TS 24.501 [13] clause 9.11.2.1A).

C

rATType

RAT type associated with the access, if available. Values given as per TS 29.571 [17] clause 5.4.3.2.

C

pDUSessionID

PDU Session ID, see TS 24.501 [13] clause 9.4.

M

requestIndication

Indicates the request type for PDU session modification as indicated by the requestIndication sent in the PDU SESSION MODIFICATION REQUEST (see TS 29.502 [16] clause 6.1.6.3.6).

M

aTSSSContainer

Identifies the steering, switching, and splitting features for the MA-Confirmed MA PDU session. Also indicates whether MPTCP or ATSSS-LL is to be used for ATSSS. See TS 24.501 [13] clause 9.11.4.22.

M

uEEndpoint

UE IP address(es) assigned to the PDU Session if available (See TS 29.244 [15] clause 5.21).

C

servingNetwork

Shall be present if this IE is in the SMContextUpdateData, HsmfUpdateData or message sent to the SMF or the PDU Session Context or SM Context at the SMF (see TS 29.502 [16] clauses 6.1.6.2.3, 6.1.6.2.11 and 6.1.6.2.39).

C

handoverState

Indicates whether the PDU Session Modification being reported was due to a handover. Shall be present if this IE is in the SMContextUpdatedData or sent by the SMF (see TS 29.502 [16] clause 6.1.6.2.3).

C

gTPTunnelInfo

Contains the information for the User Plane GTP Tunnels for the PDU Session (see TS 29.502 [16] clauses 6.1.6.2.2, 6.1.6.2.9 and 6.1.6.2.39). See table 6.2.3-1B.

M

ePSPDNConnectionModification

Provides details about PDN Connections when the SMFPDUtoMAPDUSessionModification xIRI message is used to report PDN Connection Modification. See table 6.3.3-8 and clause 6.3.3.2.3.

C

XID

Allocated by the CC-TF as per ETSI TS 103 221-1 [7].

M

TargetIdentifiers

Packet detection criteria as determined by the CC-TF in the SMF, which enables the UPF to isolate target traffic. The CC-POI in the UPF shall support at least the identifier types given in table 6.2.3-7.

NOTE: This value is the target identifier for the CC-POI in the UPF and may be different from the target identifier specified in the warrant.

M

DeliveryType

Set to “X3Only”.

M

ListOfDIDs

Delivery endpoints for LI_X3. These delivery endpoints shall be configured by the CC-TF in the SMF using the CreateDestination message as described in ETSI TS 103 221-1 [7] clause 6.3.1 prior to first use.

M

CorrelationID

Correlation ID to assign to X3 PDUs generated by the CC-POI in the UPF. This field is populated with the same CorrelationID the IRI-POI in the SMF uses for the associated xIRI.

M

ProductID

Shall be set to the XID of the Task Object associated with the interception at the CC-TF. This value shall be used by the CC-POI in the UPF to fill the XID of X3 PDUs.

M

GTP Tunnel ID

3GPP

gtpuTunnelId

F-TEID (see XSD schema)

UE IP Address

ETSI

IPv4Address or IPv6Address

See ETSI TS 103 221-1 [7]

UE TCP/UDP Port

ETSI

TCPPort or UDPPort

See ETSI TS 103 221-1 [7]

PFCP Session ID

3GPP

TargetIdentifierExtension / FSEID

F-SEID (see XSD schema)

PDR ID

3GPP

TargetIdentifierExtension / PDRID

32 bit unsigned integer (see XSD schema)

QER ID

3GPP

TargetIdentifierExtension / QERID

32 bit unsigned integer (see XSD schema)

Network Instance

3GPP

TargetIdentifierExtension / NetworkInstance

Octet string (see XSD schema)

GTP Tunnel Direction

3GPP

TargetIdentifierExtension / GTPTunnelDirection

Enumeration (see XSD schema)

TargetIdentifiers

Updated packet detection criteria as determined by the CC-TF in the SMF.

NOTE: See notes on TargetIdentifiers in table 6.2.3-6.

M

XID

Allocated by the IRI-TF as per ETSI TS 103 221-1 [7].

M

TargetIdentifiers

Packet detection criteria as determined by the IRI-TF in the SMF, which enable the UPF IRI-POI to isolate target traffic. The IRI-POI in the UPF shall support at least the identifier types given in table 6.2.3-7.

NOTE: This value is the target identifier for the IRI-POI in the UPF and may be different from the target identifier specified in the warrant.

M

DeliveryType

Set to “X2Only”.

M

TaskDetailsExtensions/

HeaderReporting

Header reporting-specific tag to be carried in the TaskDetailsExtensions field of ETSI TS 103 221-1 [7]. See table 6.2.3.9.2-1.

M

ListOfDIDs

Delivery endpoints of LI_X2. These delivery endpoints shall be configured by the IRI-TF in the SMF using the CreateDestination message as described in ETSI TS 103 221-1 [7] clause 6.3.1 prior to first use.

M

CorrelationID

Correlation ID to assign for xIRI generated by the IRI-POI in the UPF. This field is populated with the same CorrelationID the IRI-POI in the SMF uses for the associated xIRI.

M

ProductID

Shall be set to the XID of the Task Object associated with the interception at the IRI-TF. This value shall be used by the IRI-POI in the UPF to fill the XID of X2 PDUs.

M

TargetIdentifiers

Updated packet detection criteria as determined by the IRI-TF in the SMF.

NOTE: See notes on TargetIdentifiers in table 6.2.3-6.

M

SMFPDUSessionEstablishment

BEGIN

SMFPDUSessionRelease

END

SMFPDUSessionModification

CONTINUE

SMFStartOfInterceptionWithEstablishedPDUSession

BEGIN

SMFUnsuccessfulProcedure

REPORT

SMFMAPDUSessionEstablishment

BEGIN

SMFMAPDUSessionRelease

END

SMFMAPDUSessionModification

CONTINUE

SMFStartOfInterceptionWithEstablishedMAPDUSession

BEGIN

SMFMAUnsuccessfulProcedure

REPORT

SMFPDUtoMAPDUSessionModification

CONTINUE

PDHeaderReport

REPORT

PDSummaryReport

REPORT

payload

Payload of the GTP-U packet without GTP-U encapsulation. Content shall be supplied according to table 6.2.3-16.

M

qFI

Shall be populated with the QoS Flow Identifier value from the GTP-U header extension (see TS 38.415 [41] clause 5.5.3.3) if present over LI_X3.

C

uPFIPCC

Contains an IPv4 or IPv6 packet

uPFEthernetCC

Contains an Ethernet frame

uPFUnstructuredCC

Contains an unstructured packet

pDHType

This field shall be set to either:

– "PDHR," for packet-by-packet reporting.

– "PDSR," for summarized reporting.

M

pDSRParameters

If pDHType is PDSR, this field shall be set. See table 6.2.3.9.2-2.

C

pDSRTriggerType

This field shall be set to at least one of the following triggers:

a) timer expiry (along with a timer value and unit).

b) packet count (along with a value for the number of packets detected before a summary is to be triggered).

c) byte count (along with a value for the cumulative byte size reached across all packets belonging to the summary before said summary is to be triggered).

Summary reports shall not be cumulative, i.e. each summary report shall describe only the packets contained in its respective range, and each new summary shall start its count (of whichever attribute from the numbered list above applies) from zero, i.e. the information in the (n+1)’th summary report starts immediately after the end of the n’th summary report.

M

useSessionTriggers

If useSessionTriggers is present and set to true, the trigger described in the pDSRTriggerType parameter shall be applied at the session level instead of per-flow.

C

pDUSessionID

The PDU Session ID value 255 shall be used by the sender; the receiver shall ignore the parameter (see NOTE).

M

sourceIPAddress

Shall contain the source address of the packet from the 32-bit “Source Address” field in IPv4, as defined in IETF RFC 791 [34], or from the 128-bit “Source Address” field in IPv6, as defined in IETF RFC 2460 [27].

M

sourcePort

Shall contain the “Source Port” number that indicates an application or service running on top of the transport, if the “Protocol” IP field (see the nextLayerProtocol field below in this table) is one of:

a) Transmission Control Protocol (TCP), IP “Protocol” field decimal “6”; see IETF RFC 793 [28].

b) User Datagram Protocol (UDP), IP “Protocol” field decimal “17”; see IETF RFC 768 [29].

c) Datagram Congestion Control Protocol (DCCP), IP “Protocol” field decimal “33”; see IETF RFC 4340 [30].

d) Stream Control Transmission Protocol (SCTP), IP “Protocol” field decimal “132”; see IETF RFC 4960 [31].

For further details on Layer four protocols, see IANA [32].

C

destinationIPAddress

Shall contain the destination address of the packet from the 32-bit “Destination Address” field in IPv4, as defined in IETF RFC 791 [34], or from the 128-bit “Destination Address” field, as defined in IETF RFC 2460 [27].

M

destinationPort

Shall contain the “Destination Port” number that indicates an application or service running on top of the transport, if the “Protocol” IP field (see the nextLayerProtocol field below in this table) is one of:

e) Transmission Control Protocol (TCP), IP “Protocol” field decimal “6”; see IETF RFC 793 [28].

f) User Datagram Protocol (UDP), IP “Protocol” field decimal “17”; see IETF RFC 768 [29].

g) Datagram Congestion Control Protocol (DCCP), IP “Protocol” field decimal “33”; see IETF RFC 4340 [30].

h) Stream Control Transmission Protocol (SCTP), IP “Protocol” field decimal “132”; see IETF RFC 4960 [31].

For further details on Layer four protocols, see IANA [32].

C

nextLayerProtocol

Shall contain the contents of the IP “Protocol” field as defined in IETF RFC 791 [34] (bits 72…79 in the IP header), and is one of the assigned Internet protocol numbers defined in IANA [32].

M

iPv6flowLabel

If the IP addresses in the report are IPv6, this field shall contain the 20-bit IPv6 “Flow Label” as defined in:

– IPv6 IETF RFC 2460 [27], and

– IPV6 Flow Label Specification IETF RFC 6437 [33].

C

direction

Shall contain the direction of the intercepted packet, and it indicates either “from target” or “to target.”

M

packetSize

Shall contain the value of the “Total Length” IP header field if IPv4 is used, as defined in IETF RFC 791 [34], or the value of the “Payload Length” field if IPv6 is used, as defined in IETF RFC 2460 [27].

M

NOTE: This is a placeholder value used to fill the pDUSessionID field, given that the UPF does not receive the PDU Session ID used for the session by the SMF, so this information is not available at the UPF. The PDU Session ID can be retrieved by the LEMF from the IRIs generated by the IRI-POI at the SMF and delivered by the MDF2.

pDUSessionID

The PDU Session ID value 255 shall be used; the receiver shall ignore the parameter (see NOTE).

M

sourceIPAddress

Shall contain the source address of the packet from the 32-bit “Source Address” field in IPv4, as defined in IETF RFC 791 [34], or from the 128-bit “Source Address” field in IPv6, as defined in IETF RFC 2460 [27].

M

sourcePort

Shall contain the “Source Port” number that indicates an application or service running on top of the transport, if the “Protocol” IP field (see the nextLayerProtocol field below in this table) is one of:

a) Transmission Control Protocol (TCP), IP “Protocol” field decimal “6”; see IETF RFC 793 [28].

b) User Datagram Protocol (UDP), IP “Protocol” field decimal “17”; see IETF RFC 768 [29].

c) Datagram Congestion Control Protocol (DCCP), IP “Protocol” field decimal “33”; see IETF RFC 4340 [30].

d) Stream Control Transmission Protocol (SCTP), IP “Protocol” field decimal “132”; Stream Control Transmission Protocol [31].

For further details on Layer four protocols, see IANA [32].

C

destinationIPAddress

Shall contain the destination address of the packet from the 32-bit “Destination Address” field in IPv4, as defined in IETF RFC 791 [34], or from the 128-bit “Destination Address” field, as defined in IETF RFC 2460 [27].

M

destinationPort

Shall contain the “Destination Port” number that indicates an application or service running on top of the transport, if the “Protocol” IP field (see the nextLayerProtocol field below in this table) is one of:

a) Transmission Control Protocol (TCP), IP “Protocol” field decimal “6”; see IETF RFC 793 [28].

b) User Datagram Protocol (UDP), IP “Protocol” field decimal “17”; see IETF RFC 768 [29].

c) Datagram Congestion Control Protocol (DCCP), IP “Protocol” field decimal “33”; see IETF RFC 4340 [30].

d) Stream Control Transmission Protocol (SCTP), IP “Protocol” field decimal “132”; Stream Control Transmission Protocol [31].

For further details on Layer four protocols, see IANA [32].

C

nextLayerProtocol

Shall contain the contents of the IP “Protocol” field as defined in IETF RFC 791 [34] (bits 72..79 in the IP header), and is one of the assigned Internet protocol numbers defined in IANA [32].

M

iPv6flowLabel

If the IP addresses in the report are IPv6, this field shall contain the 20-bit IPv6 “Flow Label” as defined in IPv6 IETF RFC 2460 [27] and the IPV6 Flow Label Specification IETF RFC 6437 [33].

C

direction

Shall contain the direction of the intercepted packet, and it indicates either “from target” or “to target.”

M

pDSRSummaryTrigger

Shall contain the trigger that caused the summary report to be generated, which is one of the following:

a) timer expiry.

b) packet count.

c) byte count.

d) start of a flow.

e) end of a flow.

M

firstPacketTimestamp

Shall contain the timestamp that represents the time that the IRI-POI in the UPF detected the first packet in the set represented by this summary.

M

lastPacketTimestamp

Shall contain the timestamp that represents the time that the IRI-POI in the UPF detected the last packet in the set represented by this summary.

M

packetCount

Shall contain the number of packets detected during the creation of this summary.

M

byteCount

Shall contain the number of bytes summed across all packets that belong to this summary. For IPv4 it is the sum of the “Total Length” fields across all packets in the summary as defined in Internet Protocol IETF RFC 791 [34], while for IPv6 it is the sum of the “Payload Length” fields across all packets in the summary as defined in Internet Protocol, Version 6 (IPv6) Specification, IETF RFC 2460 [27].

M

perSessionTrigger

Shall be present and set to true if the trigger that caused the summary report to be generated was applied to the Session. If the trigger that caused the summary report to be generated was applied per flow, this parameter may be omitted but shall be set to false if present.

C

NOTE: This is a placeholder value used to fill the pDUSessionID field, given that the UPF does not receive the PDU Session ID used for the session by the SMF, so this information is not available at the UPF. The PDU Session ID can be retrieved by the LEMF from the IRIs generated by the IRI-POI at the SMF and delivered by the MDF2.

PDUSessionID

Identifier for the PDU session related to task.

M

UDSFRecordID

The recordID used by the parent SMF to store the associated SMF session information in the UDSF.

M

LIStateRecordType

Identifier for the record type which can be "TFLIState" or "POILIState".

M

PDUSessionID

Identifier for the PDU session related to task.

M

XID

XID of the task object associated with the interception at the TF in SMF.

M

CorrelationID

Correlation ID to assign to interception product generated by the POI in the UPF.

M

TriggeredTasks

Collection of information about tasks that the TF in SMF has activated in triggered POIs in UPF due to interception for this PDU session. As a list of TriggeredTask, see table 6.2.3.10.2-3 below.

M

XID

XID of the task object associated with the interception at the triggered.

M

NEID

NEID used in LI_T2/LI_T3 communication by the triggered POI in UPF.

M

PDUSessionID

Identifier for the PDU session related to task.

M

XID

XID of the task object associated with the interception at the POI in SMF.

M

SequenceNumber

Last sequence number used in the generation of xIRI/xCC.

M

CorrelationID

Correlation ID to assign to interception product generated by the POI in the SMF.

M

XID

XID assigned by LIPF.

M

TargetIdentifiers

One of the target identifiers listed in the paragraph above.

M

DeliveryType

Set to “X2Only”.

M

ListOfDIDs

Delivery endpoints for LI_X2 for the IRI-POI in the SMSF. These delivery endpoints are configured using the CreateDestination message as described in ETSI TS 103 221-1 [7] clause 6.3.1 prior to the task activation.

M

TaskDetailsExtensions/

SMSFExtensions

This field shall be included if the delivery of the full TPDU is not authorised. See table 6.2.5-2.

C

ListOfServiceTypes

Shall be included when the task should only intercept specific CSP service types as described in clause 5.2.4. This parameter is defined in ETSI TS 103 221-1 [7], clause 6.2.1.2, table 4.

C

TruncateTPUserData

If included, the truncatedSMSTPDU field of the sMSTPDUData (as described in table 6.2.5-7) structure shall be used when applicable (see text below table). If absent, the sMSTPDU field of the sMSTPDUData structure shall be used.

C

XID

XID assigned by LIPF.

M

TargetIdentifiers

One of the target identifiers listed in clause 6.2.5.1.

M

DeliveryType

Set to “X2Only”. (Ignored by the MDF2).

M

ListOfDIDs

Delivery endpoints for LI_HI2. These delivery endpoints are configured using the CreateDestination message as described in ETSI TS 103 221-1 [7] clause 6.3.1 prior to the task activation.

M

ListOfMediationDetails

Sequence of Mediation Details, see table 6.2.5-4.

M

TaskDetailsExtensions/

SMSFExtensions

This field shall be included if the delivery of the full TPDU is not authorised. See table 6.2.5-2.

C

LIID

Lawful Interception ID associated with the task.

M

DeliveryType

Set to "HI2Only".

M

ListOfDIDs

Details of where to send the IRI for this LIID. Shall be included if deviation from the ListofDIDs in the ActivateTask message is necessary. If included, the ListOfDIDs in the Mediation Details shall be used instead of any delivery destinations specified in the ListOfDIDs field in the ActivateTask Message.

C

ServiceScoping

Shall be included to Identify the service(s) and associated service-related delivery settings for this LIID. May include more than one instance of this parameter to allow for different combinations of sub-parameters associated with a single LIID. This parameter is defined in ETSI TS 103 221-1 [7] Annex C table C.2.

C

originatingSMSParty

Identity of the originating SMS party. See NOTE 2.

M

terminatingSMSParty

Identity of the terminating SMS party. See NOTE 3.

M

direction

Direction of the SMS with respect to the target. See NOTE 4.

M

linkTransferStatus

Indicates whether the SMSF sent the TPDU to the next network element. See NOTE 5.

M

otherMessage

In the event of a server-initiated transfer, indicates whether the server will send another SMS. May be omitted if the transfer is target-initiated. See NOTE 6.

C

location

Location information associated with the target sending or receiving the SMS, if available and authorised. See NOTE 7.

Encoded as a userLocation parameter (location>locationInfo>userLocation), see Annex A.

C

peerNFAddress

Address of the other network function (SMS-GMSC/IWMSC/SMS-Router) involved in the communication of the SMS, if available.

C

peerNFType

Type of the other network function (SMS-GMSC/IWMSC/SMS-Router) involved in the communication of the SMS, if available.

C

sMSTPDUData

See table 6.2.5-7. This is conditional only for backwards compatibility.

C

messageType

See table 6.2.5-8. This is conditional only for backwards compatibility.

C

rPMessageReference

The SM-RL Message Reference of the message per TS 24.011 [46] clause 7.3. This is conditional only for backwards compatibility.

C

location

Location information associated with the target sending or receiving the SMS, if available and authorised. See NOTE 7.

C

sMSTPDUData

SMS TPDU, encoded as per TS 23.040 [18] clause 9.

M

messageType

See table 6.2.5-8.

M

rPMessageReference

The SM-RL Message Reference of the message per TS 24.011 [46] clause 7.3.

M

sMSTPDU

SM-TL PDU encoded per the PDUs defined in TS 23.040 [18] clause 9.2.2. Shall be chosen if the TruncateTPUserData Parameter is absent.

truncatedSMSTPDU

SM-TL PDU encoded per the PDUs defined in TS 23.040 [18] clause 9.2.2 but truncated to remove TP-User-Data (TS 23.040 [18] clause 9.2.3.24). Shall be chosen if the TruncateTPUserData Parameter is set.

deliver

001

RP-DATA (network🡪UE)

00

SMS-DELIVER

deliverReportAck

010

RP-ACK (UE🡪network)

00

SMS-DELIVER-REPORT

deliverReportError

100

RP-ERROR (UE🡪network)

00

SMS-DELIVER-REPORT

statusReport

001

RP-DATA (network🡪UE)

10

SMS-STATUS-REPORT

command

000

RP-DATA (UE🡪network)

10

SMS-COMMAND

submit

000

RP-DATA (UE🡪network)

01

SMS-SUBMIT

submitReportAck

011

RP-ACK (network🡪UE)

01

SMS-SUBMIT-REPORT

submitReportError

101

RP-ERROR (network🡪UE)

01

SMS-SUBMIT-REPORT

reserved

Reserved

11

Reserved