Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 33.128  Word version:  18.7.0

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

 

6.2.3  LI for SMF/UPFp. 73

6.2.3.1  Provisioning over LI_X1p. 73

6.2.3.1.1  Generalp. 73
If the warrant is for IRI and CC, then the IRI-POI and the CC-TF in the SMF shall be provisioned in accordance with clause 6.2.3.1.2, the MDF2 shall be provisioned in accordance with clause 6.2.3.1.3, and the MDF3 shall be provisioned in accordance with clause 6.2.3.1.4.
If the warrant is for IRI only, the IRI-POI in the SMF shall be provisioned in accordance with clause 6.2.3.1.2 and the MDF2 shall be provisioned in accordance with clause 6.2.3.1.3.
If approach 1 described in clause 6.2.3.9 is used for packet header information reporting, the IRI-TF in the SMF shall be provisioned in accordance with clause 6.2.3.1.2 and the MDF2 shall be provisioned in accordance with clause 6.2.3.1.3. If approach 2 described in clause 6.2.3.9 is used for packet header information reporting, the CC-TF in the SMF shall be provisioned in accordance with clause 6.2.3.1.2, the MDF2 shall be provisioned in accordance with clause 6.2.3.1.3, and the MDF3 shall be provisioned in accordance with clause 6.2.3.1.4.
If the SMF is part of a combined SMF+PGW-C, the requirements in clause 6.3.3 shall apply.
Up
6.2.3.1.2  Provisioning of the IRI-POI, IRI-TF and CC-TF in the SMFp. 73
The IRI-POI, IRI-TF and CC-TF present in the SMF are provisioned over LI_X1 by the LIPF using the X1 protocol as described in clause 5.2.2.
The POI/TF in the SMF shall support the following target identifier formats in the ETSI TS 103 221-1 [7] messages (or equivalent if ETSI TS 103 221-1 [7] is not used):
  • SUPIIMSI.
  • SUPINAI.
  • PEIIMEI.
  • PEIIMEISV.
  • GPSIMSISDN.
  • GPSINAI.
Table 6.2.3-0A shows the minimum details of the LI_X1 ActivateTask message used for provisioning the IRI-POI, in the SMF.
ETSI TS 103 221-1 [7] field name Description M/C/O
XIDXID 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
TargetIdentifiersOne 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
To enable packet header information reporting, parameters specified in Table 6.2.3.9.2-1: PDHRReportingExtensions parameters shall be provided as the TaskDetailsExtensions/HeaderReporting field of the LI_X1 provisioning message.
Up
6.2.3.1.3  Provisioning of the MDF2p. 74
The MDF2 listed as the delivery endpoint for xIRI generated by the IRI-POI in the SMF or the IRI-POI in the UPF shall be provisioned over LI_X1 by the LIPF using the X1 protocol as described in clause 5.2.2. Table 6.2.3-0B shows the minimum details of the LI_X1 ActivateTask message used for provisioning the MDF2.
The MDF2 shall support the following target identifier formats in the ETSI TS 103 221-1 [7] messages (or equivalent if ETSI TS 103 221-1 [7] is not used):
  • SUPIIMSI.
  • SUPINAI.
  • PEIIMEI.
  • PEIIMEISV.
  • GPSIMSISDN.
  • GPSINAI.
ETSI TS 103 221-1 [7] field name Description M/C/O
XIDXID assigned by LIPF.M
TargetIdentifiersOne 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
ETSI TS 103 221-1 [7] field name Description M/C/O
LIIDLawful Intercept ID associated with the task.M
DeliveryType Set to "HI2Only". M
ListOfDIDsDetails 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
Up
6.2.3.1.4  Provisioning of the MDF3p. 75
The MDF3 listed as the delivery endpoint for the xCC generated by the CC-POI in the UPF shall be provisioned over LI_X1 by the LIPF using the X1 protocol as described in clause 5.2.2. Table 6.2.3-0D shows the minimum details of the LI_X1 ActivateTask message used for provisioning the MDF3. If packet header information reporting is authorised and approach 2 described in clause 6.2.3.9.1 is used, the endpoint for the MDF3 shall be the MDF2 over LI_MDF.
The MDF3 shall support the following target identifier formats in the ETSI TS 103 221-1 [7] messages (or equivalent if ETSI TS 103 221-1 [7] is not used):
  • SUPIIMSI.
  • SUPINAI.
  • PEIIMEI.
  • PEIIMEISV.
  • GPSIMSISDN.
  • GPSINAI.
ETSI TS 103 221-1 [7] field name Description M/C/O
XIDXID assigned by LIPF.M
TargetIdentifiersOne 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
ETSI TS 103 221-1 [7] field name Description M/C/O
LIIDLawful Intercept ID associated with the task.M
DeliveryType Set to "HI3Only". M
ListOfDIDsDetails 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
Up

6.2.3.2  Generation of xIRI at IRI-POI in SMF over LI_X2p. 76

6.2.3.2.1  Generalp. 76
The IRI-POI present in the SMF shall send the xIRIs over LI_X2 for each of the events listed in clause 6.2.3.3 of TS 33.127, the details of which are described in the following clauses. In the case where the SMF is part of a combined SMF+PGW-C, the details of the events are specified in clause 6.3.3.2. The IRI-POI present in the SMF shall also send a SeparatedLocationReporting xIRI (as described in clause 7.3.4.1) when the IRI-POI provisioned in the H-SMF detects that the V-SMF has sent location data via the HsmfUpdateData service operation to the H-SMF that does not otherwise trigger an existing SMF record type.
As specified in clause 5.6.1 of TS 23.501, a PDU session may support either a single-access PDU Connectivity Service (referred to as a single-access PDU Session) or a multi-access PDU Connectivity Service (referred to as a Multi-Access PDU (MA PDU) session).
The details of the messages for single-access PDU sessions are provided below in clauses 6.2.3.2.2, 6.2.3.2.3, 6.2.3.2.4, 6.2.3.2.5 and 6.2.3.2.6.
The details of the messages for multi-access PDU sessions are provided below in clauses 6.2.3.2.7 and 6.2.3.2.8.
Up
6.2.3.2.2  PDU session establishmentp. 76
The IRI-POI in the SMF shall generate an xIRI containing an SMFPDUSessionEstablishment record when the IRI-POI present in the SMF detects that a single-access PDU session has been established for the target UE. The IRI-POI present in the SMF shall generate the xIRI for the following events:
  • For a non-roaming scenario, the SMF (or for a roaming scenario, V-SMF in the VPLMN), sends the N1 NAS message (via AMF) PDU SESSION ESTABLISHMENT ACCEPT to the UE and the 5G Session Management (5GSM) state within the SMF is changed to PDU SESSION ACTIVE (see clauses 6.1.3.3 and 6.4.1 of TS 24.501).
  • For a home-routed roaming scenario, the SMF in the HPLMN (i.e. H-SMF) sends the N16: Nsmf_PDU_Session_Create Response message with n1SmInfoToUe IE containing the PDU SESSION ESTABLISHMENT ACCEPT (see clauses 5.2.1, 5.2.2.7, 5.2.3, 6.1.2.4, and 6.1.6.4 of TS 29.502).
If the Npcf_SMPolicyControl_Create response received from the PCF for the target UE in response to Npcf_SMPolicyControl_Create request includes PCC rules in which the traffic control policy data contains either a routeToLocs IE or trafficSteeringPolIdDl IE and/or trafficSteeringPolIdUl IE, then the SMF shall include those PCC rules in the xIRI. These PCC rules correspond to policies that influence the target UE's traffic flows (see clause 5.5.3 of TS 29.513).
Field name Type Cardi­nality Description M/C/O
sUPISUPI0..1SUPI 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
sUPIUnauthen­ticatedSUPIUnauthen­ticatedIndication0..1 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
pEIPEI0..1PEI associated with the PDU session, if available (see NOTE).C
gPSIGPSI0..1GPSI associated with the PDU session, if available (see NOTE).C
pDUSessionIDPDUSessionID1PDU Session ID. See clause 9.4 of TS 24.501.M
gTPTunnelIDFTEID1Contains 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 clause 9.3.4.1 of TS 38.413), as defined in clause 8.2.3 of TS 29.244. Non-GTP encapsulation is for further study.M
pDUSessionTypePDUSessionType1Identifies selected PDU session type, see clause 9.11.4.11 of TS 24.501.M
sNSSAISNSSAI0..1Slice identifiers associated with the PDU session, if available. See clause 28.4.2 of TS 23.003 and clause 5.15.2 of TS 23.501.C
uEEndpointSEQUENCE OF UEEndpointAddress0..MAXUE endpoint address(es) assigned to the PDU Session, if available (see clause 5.21 of TS 29.244).C
non3GPPAccessEndpointUEEndpointAddress0..1UE'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
locationLocation0..1Location information provided by the AMF or present in the context at the SMF, if available.C
dNNDNN1Data Network Name requested by the target UE, as defined in clause 9A of TS 23.003 and described in clause 4.3.2.2 of TS 23.502. Shall be given in dotted-label presentation format as described in clause 9.1 of TS 23.003.M
aMFIDAMFID0..1Identifier of the AMF associated with the target UE, as defined in clause 2.10.1 of TS 23.003 if available.C
hSMFURIHSMFURI0..1URI of the Nsmf_PDUSession service of the selected H-SMF, if available. See clause 6.1.6.2.2 of TS 29.502.C
requestTypeFiveGSMRequestType1Type of request as described in clause 9.11.3.47 of TS 24.501 provided within the Nsmf_PDU_Session_CreateSMContext Request (TS 29.502) 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 clause 6.4.1.2 of TS 24.501 shall be reported. M
accessTypeFiveGSMRequestType1Access type associated with the session (i.e. 3GPP or non-3GPP access) if provided by the AMF (see clause 9.11.2.1A of TS 24.501).C
rATTypeRATType0..1RAT Type associated with the access if provided by the AMF as part of session establishment (see clause 4.3.2 of TS 23.502). Values given as per clause 5.4.3.2 of TS 29.571.C
sMPDUDNRequestSMPDUDNRequest0..1Contents of the SM PDU DN Request container, if available, as described in clause 9.11.4.15 of TS 24.501.C
uEEPSPDNConnectionUEEPSPDNConnection0..1This 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 clause 6.1.6.2.2 of TS 29.502).C
ePS5GSComboInfoEPS5GSComboInfo0..1 Provides detailed information about PDN Connections associated with the reported PDU Session. 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
selectedDNNDNN0..1Shall 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 clause 9.1 of TS 23.003.C
servingNetworkSMFServingNetwork0..1 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 clauses 6.1.6.2.2, 6.1.6.2.9 and 6.1.6.2.39 of TS 29.502).C
oldPDUSessionIDPDUSessionID0..1 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 clauses 6.1.6.2.2, 6.1.6.2.9 and 6.1.6.2.39 of TS 29.502).C
handoverStateHandoverState0..1Indicates 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 clause 6.1.6.2.3 of TS 29.502).C
gTPTunnelInfoGTPTunnelInfo1 Contains the information for the User Plane GTP Tunnels for the PDU Session (see clauses 6.1.6.2.2, 6.1.6.2.9 and 6.1.6.2.39 of TS 29.502). See Table 6.2.3-1B.M
pCCRulesPCCRuleSet0..1 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 originated 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
ePSPDNConnectionEstablishmentEPSPDNConnectionEstablishment0..1 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
satelliteBackhaulCategorySBIType0..1 Indicates that a satellite backhaul is used towards 5G AN and the corresponding backhaul category, if available. Encoded according to clause 5.4.3.39 of TS 29.571. The SBIReference for this parameter shall be populated with 'TS29571_CommonData.yaml#/­components/schemas/­SatelliteBackhaulCategory'. C
gEOSatelliteIDGEOSatelliteID0..1Indicates the satellite ID if satellite backhaul category is GEO, if available. Encoded according to clause 5.4.2 of TS 29.571.C
NOTE:
At least one of the SUPI, PEI or GPSI fields shall be present.
Field name Type Cardi­nality Description M/C/O
ePSInterworkingIndicationEPSInterworkingIndication1Indicates whether and how the PDU Session may be moved to EPS. Shall be derived from the EpsInterworkingIndication associated with the PDU Session at the SMF+PGW-C (see clause 6.1.6.3.11 of TS 29.502).M
ePSSubscriberIDsEPSSubscriberIDs1Includes 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 clause 7.2.1 of TS 29.274 and clause 4.11.1 of TS 23.502.M
ePSPdnCnxInfoEPSPDNCnxInfo0..1Shall 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 clause 6.1.6.2.31 of TS 29.502.C
ePSBearerInfoEPSBearerInfo0..1Shall 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 clause 6.1.6.2.4 of TS 29.502.C
Field name Type Cardi­nality Description M/C/O
fiveGSGTPTunnelsFiveGSGTPTunnels0..1 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
ePSGTPTunnelsEPSGTPTunnels0..1 Shall include the information for the User Plane GTP Tunnels for the bearer context if present in the Request or Response (see clauses 7.2.2, 7.2.4 and 8.15 of TS 29.274) or known at the context at the SGW or PGW (see clause 5.6.4 of TS 23.401) when the xIRI message is used to report PDN Connection related events. See Table 6.3.3-6.C
Field name Type Cardi­nality Description M/C/O
uLNGUUPTunnelInformationFTEID0..1Shall include the F-TEID for the UPF endpoint of the NG-U transport bearer (see clause 9.3.4.1 of TS 38.413).C
additionalULNGUUPTunnelInformationFTEIDList0..1Shall include the F-TEID for the UPF endpoint of any additional NG-U transport bearers (see clause 9.3.4.1 of TS 38.413).C
dLRANTunnelInformationDLRANTunnelInformation0..1 Shall include the RAN tunnel and QOS Flow information for the PDU Session (see clause 6.1.6.2.39 of TS 29.502 and clause 9.3.4.1 of TS 38.413). See Table 6.2.3-1D.C
Field name Type Cardi­nality Description M/C/O
dLQOSFlowTunnelInformationQOSFlowTunnelInformation0..1Shall include the F-TEID NG-RAN endpoint of the NG-U transport bearer together with associated QoS flows (see clause 9.3.4.2 of TS 38.413 and clause 6.1.6.2.39 of TS 29.502).C
additionalDLQOSFlowTunnelInformationQOSFlowTunnelInformationList0..1Shall include the F-TEID NG-RAN endpoint of any additional NG-U transport bearers together with associated QoS flows (see clause 9.3.4.2 of TS 38.413 and clause 6.1.6.2.39 of TS 29.502).C
redundantDLQOSFlowTunnelInformationQOSFlowTunnelInformationList0..1Shall include the F-TEID NG-RAN endpoint of redundant NG-U transport bearers together with associated QoS flows (see clause 9.3.4.2 of TS 38.413 and clause 6.1.6.2.39 of TS 29.502).C
additionalredundantDLQOSFlowTunnelInformationQOSFlowTunnelInformationList0..1Shall include the F-TEID NG-RAN endpoint of any additional redundant NG-U transport bearers together with associated QoS flows (see clause 9.3.4.2 of TS 38.413 and clause 6.1.6.2.39 of TS 29.502).C
Each PCC rule for traffic influence has the payload defined in Table 6.2.3-1E.
Field Name Description M/C/O
pCCRuleIDPolicy rule identifier. This IE is defined in TS 29.512, Table 5.6.2.6-1.M
appIdIdentifies an application (NOTE 1), if available. This IE is defined in TS 29.512, Table 5.6.2.6-1 (NOTE 1).C
pFDPacket flow description (PFD) associated with the appId, if available. It is defined in TS 29.551 Table 5.6.2.5-1 (NOTE 1).C
flowInfosA 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, Table 5.6.2.6-1 (NOTE 1). FlowInfos may be IP flow or Ethernet flow. IP flow is specified in clause 5.3.8 of TS 29.214. Ethernet Flow is specified in TS 29.514 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, 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, Table 5.6.2.9-1. C
maxAllowedUpLatIndicates 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, Table 5.6.2.9-1, if available.C
routeToLocsA 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, Table 5.6.2.9-1 (NOTE 2).C
trafficSteeringPolIdDlTraffic steering policy for downlink traffic at the SMF, if available. This IE is defined in TS 29.512, Table 5.6.2.9-1 (NOTE 2).C
trafficSteeringPolIdUlTraffic steering policy for uplink traffic at the SMF, if available. This IE is defined in TS 29.512, Table 5.6.2.9-1 (NOTE 2).C
deprecatedSourceDNAINo longer used in present version of this specificationO
deprecatedTargetDNAINo longer used in present version of this specificationO
deprecatedDNAIChangeTypeNo longer used in present version of this specificationO
deprecatedSourceUEIPAddressNo longer used in present version of this specificationO
deprecatedTargetUEIPAddressNo longer used in present version of this specificationO
eASIPReplaceInfosContains EAS IP replacement information for a Source and a Target EAS, if available. This IE is defined in TS 29.571, 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.
Up
6.2.3.2.3  PDU session modificationp. 81
The IRI-POI in the SMF shall generate an xIRI containing an SMFPDUSessionModification record when the IRI-POI present in the SMF detects that a single-access PDU session has been modified for the target UE. The IRI-POI present in the SMF shall generate the xIRI for the following events:
  • For a non-roaming scenario, the SMF (or for a roaming scenario, V-SMF in the VPLMN), receives the N1 NAS message (via AMF) PDU SESSION MODIFICATION COMPLETE from the UE and the 5GSM state within the SMF is returned to PDU SESSION ACTIVE (see clauses 6.1.3.3, 6.3.2 and 6.4.2 of TS 24.501). This applies to the following two cases:
  • For a non-roaming scenario, the SMF (or for a roaming scenario, V-SMF in the VPLMN), sends the N1 NAS message (via AMF) PDU SESSION ESTABLISHMENT ACCEPT to the UE and the 5GSM state within the SMF remains in the PDU SESSION ACTIVE (see clauses 6.1.3.3 and 6.4.1 of TS 24.501). This applies to the following case:
  • For a non-roaming scenario, the SMF (or for a roaming scenario, V-SMF in the VPLMN), sends the Nsmf_PDUSession_UpdateSMContext response to the AMF when the PDU session modified or SM context is changed. In this case, the Nsmf_PDUSession_UpdateSMContext response may not have an embedded NAS message. This applies to the following case:
  • For a non-roaming scenario, the SMF (or for a roaming scenario, V-SMF in the VPLMN) receives the N4: PFCP Session Establishment Response when a PFCP session is established on a new UPF (or V-UPF in a roaming case) within the existing SM Context without a following Nsmf_PDUSession_Update_Context message being sent to the AMF. This applies to the following case:
  • For a non-roaming scenario, the SMF (or for a roaming scenario, V-SMF in the VPLMN) receives the N4: PFCP Session Modification Response when a new tunnel Identifier (local or remote) is added to the PDU session or removed from the PDU session without a following Nsmf_PDUSession_Update_Context message being sent to the AMF. This applies to the following case:
  • For a non-roaming scenario, the SMF (or for a roaming scenario, V-SMF in the VPLMN) receives the N4: PFCP Session Deletion Response when a PFCP session is deleted from an SM Context that remains active. This applies to the following case:
  • For a home-routed roaming scenario, the SMF in the HPLMN (i.e. H-SMF) receives the N16: Nsmf_PDU_Session_Update Response message with n1SmInfoFromUe IE containing the PDU SESSION MODIFICATION COMPLETE (see clauses 5.2.1, 5.2.2.8, 5.2.3, and 6.1.6.4 of TS 29.502). This applies to the following three cases:
  • For a home-routed roaming scenario, the SMF in the HPLMN (i.e. H-SMF) sends the N16: Nsmf_PDU_Session_Create Response message with n1SmInfoToUe IE containing the PDU SESSION ESTABLISHMENT ACCEPT (see clauses 5.2.1, 5.2.2.8, 5.2.3, and 6.1.6.4 of TS 29.502) while it had received a N16 Nsmf_PDU_Session_Create Request message with an existing PDU Session Id with access type being changed. This applies to the following case:
    • Handover from one access type to another access type happens (e.g. 3GPP to non-3GPP); see clauses 4.9.2.3 and 4.9.2.4 of TS 23.502) where the V-SMF is used for the PDU session on the new access type only.
  • For a home-routed roaming scenario, the SMF in the HPLMN (i.e. H-SMF) sends the N16: Nsmf_PDU_Session_Update Response message with n1SmInfoToUe IE containing the PDU SESSION ESTABLISHMENT ACCEPT (see TS 29.502) while it had received a N16 Nsmf_PDU_Session_Update Request message with an existing PDU Session Id with access type being changed. This applies to the following case:
    • Handover from one access type to another access type happens (e.g. 3GPP to non-3GPP) where the same V-SMF is used for the PDU session on both access types.
  • For a non-roaming scenario, SMF sends a Nsmf_EventExposure_Notify request to the NEF or AF for the target UE for the event "UP Path Change" related to a corresponding subscription from AF (see clause 4.2.2 of TS 29.508).
  • For a non-roaming scenario, SMF sends a Nsmf_EventExposure_AppRelocationInfo response to the NEF or AF for the target UE in response to Nsmf_EventExposure_AppRelocationInfo request sent by NEF or AF to SMF (see clause 4.2.5 of TS 29.508).
  • For a non-roaming scenario, SMF receives a Nnef_PFDManagement_Fetch response from the NEF for the target UE in response to Nnef_PFDManagement_Fetch request sent by SMF to NEF (see clause 4.2.2 of TS 29.551).
If the Npcf_SMPolicyControlUpdateNotify response sent to the PCF for the target UE in response to an Npcf_SMPolicyControlUpdateNotify request includes PCC rules in which the traffic control policy data contains either a routeToLocs IE or trafficSteeringPolIdDl IE and/or trafficSteeringPolIdUl IE, then the SMF shall include those PCC rules in the xIRI. These PCC rules correspond to policies that influence the target UE's traffic flows (see clause 5.5.3 of TS 29.513).
Field name Type Cardi­nality Description M/C/O
sUPISUPI0..1SUPI 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
sUPIUnauthen­ticatedSUPIUnauthen­ticatedIndication0..1 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
pEIPEI0..1PEI associated with the PDU session, if available.C
gPSIGPSI0..1GPSI associated with the PDU session, if available.C
sNSSAISNSSAI0..1Slice identifier associated with the PDU session, if available. See clause 28.4.2 of TS 23.003 and clause 5.15.2 of TS 23.501.C
non3GPPAccessEndpointUEEndpointAddress0..1UE'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
locationLocation0..1Location information provided by the AMF or present in the context at the SMF, if available.C
requestTypeFiveGSMRequestType0..1Type of request as described in clause 9.11.3.47 of TS 24.501, if available.C
accessTypeAccessType0..1Access type associated with the session (i.e. 3GPP or non-3GPP access) if provided by the AMF (see clause 9.11.2.1A of TS 24.501).C
rATTypeRATType0..1RAT type associated with the access, if available. Values given as per clause 5.4.3.2 of TS 29.571.C
pDUSessionIDPDUSessionID0..1PDU Session ID, see clause 9.4 of TS 24.501. Shall be provided. This parameter is conditional only for backwards compatibility.C
ePS5GSComboInfoEPS5GSComboInfo0..1 Provides detailed information about PDN Connections associated with the reported PDU Session. 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
uEEndpointUEEndpointAddress0..1UE IP address(es) assigned to the PDU Session, if available (see clause 5.21 of TS 29.244).C
servingNetworkSMFServingNetwork0..1 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 clauses 6.1.6.2.3, 6.1.6.2.11 and 6.1.6.2.39 of TS 29.502).C
handoverStateHandoverState0..1Indicates 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 clause 6.1.6.2.3 of TS 29.502).C
gTPTunnelInfoGTPTunnelInfo1 Contains the information for the User Plane GTP Tunnels for the PDU Session (see clauses 6.1.6.2.2, 6.1.6.2.9 and 6.1.6.2.39 of TS 29.502). See Table 6.2.3-1B.M
pCCRulesPCCRuleSet0..1 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 originated 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
ePSPDNConnectionModificationEPSPDNConnectionModification0..1 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
uPPathChangeUPPathChange0..1Notification of the UPPathChange event. This IE is defined in TS 29.508, if available, see Table 5.6.2.5-1.C
pFDDataForAppPFDDataForApp0..1Represents the packet flow descriptions (PFDs) for an application identifier (AppId), if available. This IE is defined in TS 29.551 Table 5.6.2.2-1.C
satelliteBackhaulCategorySBIType0..1 Indicates that a satellite backhaul is used towards 5G AN and the corresponding backhaul category, if available. Encoded according to clause 5.4.3.39 of TS 29.571. The SBIReference for this parameter shall be populated with 'TS29571_CommonData.yaml#/­components/schemas/­SatelliteBackhaulCategory'. C
gEOSatelliteIDGEOSatelliteID0..1Indicates the satellite ID if satellite backhaul category is GEO, if available. Encoded according to clause 5.4.2 of TS 29.571.C
Field name Type Cardi­nality Description M/C/O
sourceDNAIDNAI0..1Source DNAI, if the DNAI has changed. DNAI represents the location of applications towards which the traffic routing should apply, if available.C
targetDNAIDNAI0..1Target DNAI if the DNAI has changed.C
dNAIChangeTypeDNAIChangeType0..1 Type of a DNAI change. Possible values are "early", "late" and "earlyAndLate" notification of UP path reconfiguration, if available. C
sourceUEIPAddressIPAddress0..1The IPv4 Address of the served UE for the source DNAI, if available.C
targetUEIPAddressIPAddress0..1The IPv4 Address of the served UE for the target DNAI, if available.C
sourceTrafficRoutingRouteToLocation0..1N6 traffic routing information for the source DNAI, if available.C
targetTrafficRoutingRouteToLocation0..1N6 traffic routing information for the target DNAI, if available.C
mACAddressMACAddress0..1The MAC address of the served UE, if available.C
Field Name Description M/C/O
appIdIdentifier of an application.M
pFDsPFDs for an application identifier, if available. PFD is defined in TS 29.551 Table 5.6.2.5-1.C
Field Name Description M/C/O
pFDIdPFD identifier.M
pFDflowDescriptionRepresents a set of 3-tuple with protocol, server IP address and server port for UL/DL application traffic, if available.C
uRLsRepresents a set of URL, if available.C
domainNamesRepresents a set of FQDN, if available.C
dnProtocolIndicates the additional protocol and protocol field for domain names to be matched, if available. This IE is defined in TS 29.122 Table 5.14.2.2.4-1.C
Up
6.2.3.2.4  PDU session releasep. 85
The IRI-POI in the SMF shall generate an xIRI containing an SMFPDUSessionRelease record when the IRI-POI present in the SMF detects that a single-access PDU session has been released. The IRI-POI present in the SMF shall generate the xIRI for the following events:
  • For a non-roaming scenario, the SMF (or for a roaming scenario, V-SMF in the VPLMN), receives the N1 NAS message (via AMF) PDU SESSION RELEASE COMPLETE from the UE and the 5GSM state within the SMF is changed to PDU SESSION INACTIVE (see clauses 6.1.3.3 and 6.4.3 of TS 24.501). This applies to the following two cases:
  • For a non-roaming scenario, the SMF (or for a roaming scenario, V-SMF in the VPLMN), receives the N1 NAS message (via AMF) STATUS from the UE with the cause values listed in clause 6.5.3 of TS 24.501 and the 5GSM state within the SMF is changed to PDU SESSION INACTIVE. One of the cases where this applies is of UE finding that the PDU session ID received in a PDU SESSION MODIFICATION COMMAND is invalid.
  • For a non-roaming scenario, the SMF (or for a roaming scenario, the V-SMF in the VPLMN) sends the Nsmf_PDUSession_ReleaseSMContext Response to the AMF (see clause 5.2.2.4 of TS 29.502). This applies to the case where the PDU session is released without any N1 or N2 messages (e.g. AMF initiates the PDU session release when it finds that the PDU session is no longer associated with the UE, see clause 4.2.2.4 of TS 23.502).
  • For a non-roaming scenario, the SMF (or for a roaming scenarios, V-SMF in the VPLMN) sends Nsmf_PDUSession_SMContextStatusNotify (see clause 6.1.6.2.8 of TS 29.502) with RELEASED in the ResourceStatus IE (see clause 6.1.6.3.1 of TS 29.502) to the AMF. This applies to the case where PDU session release is neither initiated by a NAS message nor by Nsmf_PDUSessionReleaseSMContext Request message (see clause 5.2.2.5 of TS 29.502).
  • For a home-routed roaming scenario, the SMF in the HPLMN (i.e. H-SMF) receives the N16: Nsmf_PDU_Session_Update Response message with n1SmInfoFromUe IE containing the PDU SESSION RELEASE COMPLETE (see clauses 5.2.1, 5.2.2.8, 5.2.3, and 6.1.6.4 of TS 29.502) from the V-SMF. This applies to the following three cases:
  • For a roaming scenario, H-SMF in the HPLMN sends the Nsmf_PDUSession_Release Response to the V-SMF (see clause 5.2.2.9 of TS 29.502). This applies to the case where the PDU session is released without any N1 or N2 messages (e.g. AMF in the VPLMN initiates the PDU session release when it finds that the PDU session is no longer associated with the UE, see clause 4.3.4.3 of TS 23.502).
  • For a roaming scenario, H-SMF in the HPLMN sends a Nsmf_PDUSession_StatusNotify (see clause 6.1.6.2.17 of TS 29.502) with RELEASED in the ResourceStatus IE (see clause 6.1.6.3.1 of TS 29.502) to the V-SMF. This applies to the case where PDU session release is neither initiated by a NAS message nor by Nsmf_PDUSessionRelease Request message (see clause 5.2.2.9 of TS 29.502).
Field name Type Cardi­nality Description M/C/O
sUPISUPI1SUPI associated with the PDU session.M
pEIPEI0..1PEI associated with the PDU session if available.C
gPSIGPSI0..1GPSI associated with the PDU session if available.C
pDUSessionIDPDUSessionID1PDU Session ID as assigned by the AMF.M
timeOfFirstPacketTimestamp0..1Time of first packet for the PDU session.C
timeOfLastPacketTimestamp0..1Time of last packet for the PDU session.C
uplinkVolumeINTEGER0..1Number of uplink octets for the PDU session.C
downlinkVolumeINTEGER0..1Number of downlink octets for the PDU session.C
locationLocation0..1Location information, if available.C
causeSMFErrorCodes0..1Indicates the NF Service Consumer cause for the requested PDU session release (see clause 6.1.6.3.8 of TS 29.502 for enumerated cause information). Include if known.C
ePS5GSComboInfoEPS5GSComboInfo0..1 Provides detailed information about PDN Connections associated with the reported PDU Session. This parameter may include the additional IEs in Table 6.2.3-1A, when available.C
nGAPCauseNGAPCauseInt0..1Indicates the NGAP cause for the requested SM context release (see clause 6.1.6.2.6 of TS 29.502). Shall be derived as described in clause 5.4.4.12 of TS 29.571.C
fiveGMMCauseFiveGMMCause0..1Indicates the 5GMM cause for a PDU Session released due to any 5GMM failure (see clause 6.1.6.2.6 of TS 29.502). Shall be sent as an integer derived as described in clause 5.4.2 of TS 29.571.C
pCCRuleIDsPCCRuleIDSet0..1PCC 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
ePSPDNConnectionReleaseEPSPDNConnectionRelease0..1 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
Up
6.2.3.2.5  Start of interception with an established PDU sessionp. 86
The IRI-POI in the SMF shall generate an xIRI containing an SMFStartOf­Interception­WithEstablished­PDUSession record when the IRI-POI present in the SMF detects that a single-access PDU session has already been established for the target UE when interception starts.
In a non-roaming scenario, the IRI-POI in the SMF (or in a roaming scenario, the IRI-POI in the V-SMF in the VPLMN) shall generate the xIRI containing the SMFStartOf­Interception­WithEstablished­PDUSession record when it detects that a new interception for a UE is activated (i.e. provisioned by the LIPF) for the following case:
  • The 5GSM state within the SMF for that UE is 5GSM: PDU SESSION ACTIVE or PDU SESSION MODIFICATION PENDING.
In a home-routed roaming scenario, the IRI-POI in the H-SMF shall generate the xIRI containing the SMFStartOf­Interception­WithEstablished­PDUSession record when it detects that a new interception for a UE is activated (i.e. provisioned by the LIPF) for the following case:
  • The H-SMF had not sent a Nsmf_PDU_Session_Update Request (n1SmInfoToUe: PDU SESSION RELEASE COMMAND) to the V-SMF for a PDU session and H-SMF had previously sent a Nsmf_PDU_Session_Create Response (n1SmInfoToUE: PDU SESSION ESTABLISHMENT ACCEPT) to the V-SMF for that PDU session.
The IRI-POI in the SMF shall generate the xIRI containing the SMFStartOf­Interception­WithEstablished­PDUSession record for each of the PDU sessions (that meets the above criteria) associated with the newly identified target UEs.
Field name Type Cardi­nality Description M/C/O
sUPISUPI0..1SUPI 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
sUPIUnauthen­ticatedSUPIUnauthen­ticatedIndication0..1 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
pEIPEI0..1PEI associated with the PDU session, if available.C
gPSIGPSI0..1GPSI associated with the PDU session, if available.C
pDUSessionIDPDUSessionID1PDU Session ID as assigned by the AMF, as defined in clause 11.2.3.1b of TS 24.007.M
gTPTunnelIDFTEID1Contains 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 clause 9.3.4.1 of TS 38.413), as defined in clause 8.2.3 of TS 29.244. Non-GTP encapsulation is for further study.M
sNSSAISNSSAI0..1Slice identifier associated with the PDU session, if available. See clause 28.4.2 of TS 23.003 and clause 5.15.2 of TS 23.501.C
pDUSessionTypePDUSessionType1Identifies selected PDU session type, see clause 9.11.4.11 of TS 24.501.M
uEEndpointSEQUENCE OF UEEndpointAddress0..NUE 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 clause 5.21 of TS 29.244).C
non3GPPAccessEndpointUEEndpointAddress0..1UE'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
locationLocation0..1Location information provided by the AMF at session establishment or present in the context at the SMF, if available.C
dNNDNN1Data Network Name associated with the target traffic, as defined in clause 9A of TS 23.003 and described in clause 4.3.2.2 of TS 23.502. Shall be given in dotted-label presentation format as described in clause 9.1 of TS 23.003.M
aMFIDAMFID0..1Identifier of the AMF associated with the target UE, as defined in clause 2.10.1 of TS 23.003, if available.C
hSMFURIHSMFURI0..1URI of the Nsmf_PDUSession service of the selected H-SMF, if available. See clause 6.1.6.2.2 of TS 29.502.C
requestTypeFiveGSMRequestType1Type of request as initially set within the PDU SESSION ESTABLISHMENT as described in clause 9.11.3.47 of TS 24.501.
If the initial value is no longer available the request type shall be set to "existing PDU session".
M
accessTypeAccessType0..1Access type associated with the session (i.e. 3GPP or non-3GPP access) if provided by the AMF (see clause 9.11.2.1A of TS 24.501).C
rATTypeRATType0..1RAT type associated with the access if provided by the AMF as part of session establishment (see clause 4.3.2 of TS 23.502). Values given as per clause 5.4.3.2 of TS 29.571.C
sMPDUDNRequestSMPDUDNRequest0..1Contents of the SM PDU DN request container, if available, as described in clause 9.11.4.15 of TS 24.501.C
timeOfSessionEstablishmentTimestamp0..1Time 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
ePS5GSComboInfoEPS5GSComboInfo0..1 Provides detailed information about PDN Connections associated with the reported PDU Session. 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
uEEPSPDNConnectionUEEPSPDNConnection0..1This 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 clause 6.1.6.2.2 of TS 29.502).C
servingNetworkSMFServingNetwork0..1Indicates 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 clause 6.1.6.2.39 of TS 29.502).C
gTPTunnelInfoGTPTunnelInfo1 Contains the information for the User Plane GTP Tunnels for the PDU Session (see clauses 6.1.6.2.2, 6.1.6.2.9 and 6.1.6.2.39 of TS 29.502). See Table 6.2.3-1B.M
pCCRulesPCCRuleSet0..1 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 originated 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
ePSStartOfInterceptionWithEstablishedPDNConnectionEPSStartOfInterceptionWithEstablishedPDNConnection0..1 Provides details about PDN Connections when the SMFStartOf­Interception­WithEstablished­PDUSession 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
pFDDataForAppsPFDDataForApps0..1Represents a set of associations between application identifier and packet flow descriptions (PFDs), if available.C
satelliteBackhaulCategorySBIType0..1 Indicates that a satellite backhaul is used towards 5G AN and the corresponding backhaul category, if available. Encoded according to clause 5.4.3.39 of TS 29.571. The SBIReference for this parameter shall be populated with 'TS29571_CommonData.yaml#/­components/schemas/­SatelliteBackhaulCategory'. C
gEOSatelliteIDGEOSatelliteID0..1Indicates the satellite ID if satellite backhaul category is GEO, if available. Encoded according to clause 5.4.2 of TS 29.571.C
The IRI-POI present in the SMF generating an xIRI containing a SMFStartOfInterception­WithEstablishedPDUSession record shall set the Payload Direction field in the PDU header to not applicable (Direction Value 5, see ETSI TS 103 221-2 [8] clause 5.2.6).
Up
6.2.3.2.6  SMF unsuccessful procedurep. 88
The IRI-POI in the SMF shall generate an xIRI containing an SMFUnsuccessfulProcedure record when the IRI-POI present in the SMF detects an unsuccessful procedure or error condition for a UE matching one of the target identifiers provided via LI_X1.
Accordingly, the IRI-POI in the SMF generates the xIRI when one of the following events are detected:
  • SMF sends a PDU SESSION ESTABLISHMENT REJECT message to the target UE.
  • SMF sends a PDU SESSION MODIFICATION REJECT message to the target UE.
  • SMF sends a PDU SESSION RELEASE REJECT message to the target UE.
  • SMF receives a PDU SESSION MODIFICATION COMMAND REJECT message from the target UE.
  • An ongoing SM procedure is aborted at the SMF, due to e.g. a 5GSM STATUS message sent from or received by the SMF.
Field name Type Cardi­nality Description M/C/O
failedProcedureTypeSMFFailedProcedureType1Specifies the procedure which failed or is aborted at the SMF.M
failureCauseFiveGSMCause1Provides the value of the 5GSM cause, see clause 9.11.4.2 of TS 24.501. 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
initiatorInitiator1Specifies whether the network (SMF) or the UE is initiating the rejection or indicating the failure.M
requestedSliceNSSAI0..1Slice requested for the procedure, if available, given as a NSSAI (a list of S-NSSAI values as described in clause 9.11.3.37 of TS 24.501).C
sUPISUPI0..1SUPI associated with the procedure, if available (see NOTE).C
sUPIUnauthenticatedSUPIUnauthenticatedIndication0..1 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
pEIPEI0..1PEI used in the procedure, if available (see NOTE).C
gPSIGPSI0..1GPSI used in the procedure, if available (see NOTE).C
pDUSessionIDPDUSessionID0..1PDU Session ID. See clause 9.4 of TS 24.501, if available.C
uEEndpointSEQUENCE OF UEEndpointAddress0..MAXUE endpoint address(es) if available.C
non3GPPAccessEndpointUEEndpointAddress0..1UE's local IP address used to reach the N3IWF, TNGF or TWIF, if available.C
dNNDNN0..1Data Network Name associated with the target traffic, as defined in clause 9A of TS 23.003 and described in clause 4.3.2.2 of TS 23.501, if available. Shall be given in dotted-label presentation format as described in clause 9.1 of TS 23.003.C
aMFIDAMFID0..1Identifier of the AMF associated with the target UE, as defined in clause 2.10.1 of TS 23.003 when available.C
hSMFURIHSMFURI0..1URI of the Nsmf_PDUSession service of the selected H-SMF, if available. See clause 6.1.6.2.2 of TS 29.502.C
requestTypeFiveGSMRequestType0..1Type of request as described in clause 9.11.3.47 of TS 24.501, 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
accessTypeAccessType0..1Access type associated with the session (i.e. 3GPP or non-3GPP access) if provided by the AMF (see clause 9.11.2.1A of TS 24.501).C
rATTypeRATType0..1RAT Type associated with the access if provided by the AMF as part of session establishment (see clause 4.3.2 of TS 23.502). Values given as per clause 5.4.3.2 of TS 29.571.C
sMPDUDNRequestSMPDUDNRequest0..1Contents of the SM PDU DN Request container, if available, as described in clause 9.11.4.15 of TS 24.501.C
locationLocation0..1Location information provided by the AMF or present in the context at the SMF, if available.C
NOTE:
At least one identity shall be provided, the others shall be provided if available.
Up

Up   Top   ToC