Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑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.2.7 MA PDU sessions  6.2.3.2.7.1 General  6.2.3.2.7.2 MA PDU session establishment  6.2.3.2.7.3 MA PDU session modification  6.2.3.2.7.4 MA PDU session release  6.2.3.2.7.5 Start of interception with an established MA PDU session  6.2.3.2.7.6 SMF MA unsuccessful procedure  6.2.3.2.8 PDU to MA PDU session modification 
...

 

6.2.3.2.7  MA PDU sessions  p. 90
6.2.3.2.7.1  General  p. 90
In the present document, an MA PDU session will include two general types of PDU sessions as defined below:
  • MA-Confirmed: This is an MA PDU session where the UE signals Upgrade Allowed to MA and the network immediately upgrades the session to an MA PDU session or the UE explicitly requests an MA PDU session (using a Request Type of MA PDU).
  • MA-Upgrade-Allowed: This is a PDU session where the UE indicated that upgrade to an MA PDU session is allowed, but the network does not immediately confirm the upgrade. The network may at some later point upgrade the session to an MA PDU session.
An MA-Confirmed MA PDU session may be established over a single access or over multiple accesses. The establishment over multiple accesses may occur concurrently or may occur at different points in time.
An MA-Upgrade-Allowed MA PDU session is established over a single access and nearly all aspects appears to be an ordinary non-MA PDU session with the key difference that the network may upgrade the session to an MA-confirmed MA PDU session.
Up
6.2.3.2.7.2  MA PDU session establishment  p. 91
The IRI-POI in the SMF shall generate an xIRI containing an SMFMAPDUSessionEstablishment record when the IRI-POI present in the SMF detects that a PDU session has been established for the target UE that is an MA PDU session (Request Type set to MA PDU session or upgraded at establishment), or where the upgrade allowed parameter is set to upgrade allowed and session is established as an ordinary PDU session (not upgraded at establishment, but may occur later on). The IRI-POI present in the SMF shall generate the xIRI for the following events:
  • For a non-roaming scenario , the SMF sends the N1 NAS message (via AMF) PDU SESSION ESTABLISHMENT ACCEPT to the UE for a new PDU session 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) in response to a PDU SESSION ESTABLISHMENT REQUEST received along with:
    • PDU Session ID which does not identify an existing PDU session, and
    • Request Type = MA PDU request, or
    • Request Type = initial request and MA PDU session information set to "MA PDU session network upgrade is allowed", with either upgrade occurring at establishment or upgrade does not occur at establishment but may occur later.
  • 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, and 6.1.6 of TS 29.502) for a new PDU session in response to a PDU SESSION ESTABLISHMENT REQUEST received along with:
    • PDU Session ID which does not identify an existing PDU session, and
    • Request Type = MA PDU request, or
    • Request Type = initial request and MA PDU session information set to "MA PDU session network upgrade is allowed", with either upgrade occurring at establishment or upgrade does not occur at establishment but may occur later.
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
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 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. Identifies a new PDU session.M
pDUSessionTypePDUSessionType1Identifies selected PDU session type, see clause 9.11.4.11 of TS 24.501.M
accessInfoSEQUENCE OF AccessInfo1..MAX Identifies the access(es) associated with the PDU session including the information for each specific access (see Table 6.2.3-5B).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
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 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 clause 6.4.1.2 of TS 24.501. 		M
sMPDUDNRequestSMPDUDNRequest0..1Contents of the SM PDU DN Request container, if available, as described in clause 9.11.4.15 of TS 24.501.C
servingNetworkSMFServingNetwork1PLMN 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
oldPDUSessionIDPDUSessionID0..1 The old PDU Session ID received from the UE. See clauses 4.3.2.2.1 and 4.3.5.2 of TS 23.502 and clause 6.4.1.2 of TS 24.501. 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
mAUpgradeIndicationSMFMAUpgradeIndication0..1Indicates whether the PDU session is allowed to be upgraded to MA-Confirmed MA PDU session (see clause 4.22.3 of TS 23.502). Include if known.C
ePSPDNCnxInfoSMFEPSPDNCnxInfo0..1Indicates if the PDU session may be moved to EPS during its lifetime (see clause 6.1.6.2.31 of TS 29.502). Include if known.C
mAAcceptedIndicationSMFMAAcceptedIndication1 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).
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
aTSSSContainerATSSSContainer0..1Identifies 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.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 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
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
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
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 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.
Field name Type Cardi­nality Description M/C/O
accessTypeAccessType1Access type associated with the session (i.e. 3GPP or non-3GPP access) as provided by the AMF (see clause 9.11.2.1A of TS 24.501).M
rATTypeRATType0..1RAT Type associated with the access as 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
gTPTunnelIDFTEID1Contains the F-TEID identifying the GTP tunnel used to encapsulate the traffic, as defined in clause 8.2.3 of TS 29.244. Non-GTP encapsulation is for further study.M
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
establishmentStatusEstablishmentStatus1Indicates whether the access type is established or released.M
aNTypeToReactivateAccessType0..1Indicates 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
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
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
Up
6.2.3.2.7.3  MA PDU session modification  p. 94
The IRI-POI in the SMF shall generate an xIRI containing an SMFMAPDUSessionModification record when the IRI-POI present in the SMF detects that an MA 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 and 6.4.2 of TS 24.501). This applies to the following cases for an MA-Upgrade-Allowed PDU session:
  • 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 in response to a PDU SESSION RELEASE COMMAND message containing an Access type IE identifying a single access to be released of an MA PDU session which was established over both accesses and the 5GSM state within the SMF remains in the PDU SESSION ACTIVE. This applies to the following case:
    • A single access type is released from an MA PDU session, but the MA PDU session continues.
  • 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 cases:
    • Handover from one access type to another access type happens (e.g. 3GPP to non-3GPP) for an MA-Upgrade-Allowed MA PDU session (see clauses 4.9.2.3 and 4.9.2.4 of TS 23.502).
    • MA PDU Session establishment over second access type.
  • 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 of TS 29.502). This applies to the following cases for an MA-Upgrade-Allowed PDU session:
  • 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).
  • 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 message, a response to a PDU SESSION RELEASE COMMAND message containing an Access type IE identifying a single access to be released of an MA PDU session which was established over both accesses and the 5GSM state within the SMF remains in the PDU SESSION ACTIVE. This applies to the following cases:
    • A single access type is released from an MA PDU session, but the MA PDU session continues.
  • 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 of TS 29.502) while it had received an N16 Nsmf_PDU_Session_Create request message with an existing PDU Session Id with access type being changed. This applies to the following cases:
    • Handover from one access type to another access type happens (e.g. 3GPP to non-3GPP) for an MA-Upgrade-Allowed PDU session (see clauses 4.9.2.3 and 4.9.2.4 of TS 23.502). In this case, the V-SMF is used for the PDU session on the new access type only.
    • MA PDU Session establishment over second access type.
  • 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 cases:
    • 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.
    • MA PDU Session establishment over second access type.
For a non-roaming scenario, SMF sends a Npcf_SMPolicyControlUpdateNotify response to the PCF for the target UE in response to an Npcf_SMPolicyControlUpdateNotify request sent by PCF to SMF including PCC rules which traffic control policy data contains either a routeToLocs IE or trafficSteeringPolIdDl IE and/or trafficSteeringPolIdUl IE. 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
sUPIUnauthenticatedSUPIUnauthenticatedIndication0..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
pDUSessionIDPDUSessionID1PDU Session ID, see clause 9.4 of TS 24.501.M
accessInfoSEQUENCE OF AccessInfo0..MAX 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
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
locationLocation0..1Location information provided by the AMF or present in the context at the SMF, if available.C
requestTypeFiveGSMRequestType0..1 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
servingNetworkSMFServingNetwork1PLMN 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
oldPDUSessionIDPDUSessionID0..1 The old PDU Session ID received from the UE. See clauses 4.3.2.2.1 and 4.3.5.2 of TS 23.502 and clause 6.4.1.2 of TS 24.501.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
mAUpgradeIndicationSMFMAUpgradeIndication0..1Indicates whether the PDU session is allowed to be upgraded to MA PDU session (see clause 4.22.3 of TS 23.502). Include if known.C
ePSPDNCnxInfoSMFEPSPDNCnxInfo0..1Indicates if the PDU session may be moved to EPS during its lifetime (see clause 6.1.6.2.31 of TS 29.502). Include if known.C
mAAcceptedIndicationSMFMAAcceptedIndication1 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).
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
aTSSSContainerSMFMAAcceptedIndication1Identifies 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.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 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
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
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
uPPathChangeUPPathChange0..1Notification of the UPPathChange event, if available. This IE is defined in TS 29.508, 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
ePSPDNConnectionModificationEPSPDNConnectionModification0..1 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
Up
6.2.3.2.7.4  MA PDU session release  p. 97
The IRI-POI in the SMF shall generate an xIRI containing an SMFMAPDUSessionRelease record when the IRI-POI present in the SMF detects that an MA 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) for a PDU session that is either MA-Confirmed or MA-Upgrade-Allowed. This applies to the following two cases:
  • 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 V-SMF is changed to PDU SESSION INACTIVE (see clauses 6.1.3.3 and 6.4.3 of TS 24.501) for a PDU session that is either MA-Confirmed or MA-Upgrade-Allowed. This applies to the following two cases:
    • UE initiated PDU session release of a single access for an MA PDU session; (VPLMN considers MA PDU session fully released while HPLMN considers MA PDU session active).
    • Network initiated PDU session release of a single access for an MA PDU session; (VPLMN considers MA PDU session fully released while HPLMN considers MA PDU session active).
  • 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 for a PDU session that is either MA-Confirmed or MA-Upgrade-Allowed. 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) for a PDU session that is either MA-Confirmed or MA-Upgrade-Allowed. This applies to the case where the MA 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 for a PDU session that is either MA-Confirmed or MA-Upgrade-Allowed. This applies to the case where MA PDU session release is neither initiated by a NAS message nor by Nsmf_PDUSessionReleaseContext 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 of TS 29.502) from the V-SMF. This applies to the following three cases for an MA PDU session that is either MA-Confirmed or MA-Upgrade-Allowed:
  • 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) for a PDU session that is either MA-Confirmed or MA-Upgrade-Allowed. This applies to the case where the MA 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 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 for a PDU session that is either MA-Confirmed or MA-Upgrade-Allowed. This applies to the case where MA 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
pDUSessionIDPDUSession1PDU 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
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
pCCRulesIDsPCCRuleIDSet0..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 SMFMAPDUSessionRelease 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.7.5  Start of interception with an established MA PDU session  p. 98
The IRI-POI in the SMF shall generate an xIRI containing an SMFStartOfInterceptionWithEstablishedMAPDUSession record when the IRI-POI present in the SMF detects that a MA 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 SMFStartOfInterceptionWithEstablishedMAPDUSession record when it detects that a new interception for a UE is activated (i.e. provisioned by the LIPF) for the following case for an MA PDU session that is either MA-Confirmed or MA-Upgrade-Allowed:
  • 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 SMFStartOfInterceptionWithEstablishedMAPDUSession record when it detects that a new interception for a UE is activated (i.e. provisioned by the LIPF) for the following case for an MA PDU session that is either MA-Confirmed or MA-Upgrade-Allowed:
  • The H-SMF had not sent an Nsmf_PDU_Session_Update Request (n1SmInfoToUe: PDU SESSION RELEASE COMMAND to release the entire MA PDU session) to the V-SMF for a PDU session and H-SMF had previously sent an 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 SMFStartOfInterception­WithEstablishedMAPDUSession record for each of the MA PDU sessions (that meets the above criteria) associated with the newly identified target UEs.
The IRI-POI present in the SMF generating an xIRI containing a SMFStartOfInterception­WithEstablishedMAPDUSession 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).
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
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 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
pDUSessionTypePDUSessionType1Identifies selected PDU session type, see clause 9.11.4.11 of TS 24.501.M
accessInfoSEQUENCE OF AccessInfo1..MAX Identifies the access(es) associated with the PDU session including the information for each specific access (see Table 6.2.3-5B).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
uEEndpointSEQUENCE OF UEEndpointAddress0..MAXUE 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
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
requestTypeFiveGSMRequestType0..1Type of request as initially set within 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". 		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
servingNetworkSMFServingNetwork1PLMN 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
oldPDUSessionIDPDUSessionID0..1 The old PDU Session ID received from the UE. See clauses 4.3.2.2.1 and 4.3.5.2 of TS 23.502, and clause 6.4.1.2 of TS 24.501. Include if known.C
mAUpgradeIndicationSMFMAUpgradeIndication0..1Indicates whether the PDU session is allowed to be upgraded to MA PDU session (see clause 4.22.3 of TS 23.502). Include if known.C
ePSPDNCnxInfoSMFEPSPDNCnxInfo0..1Indicates if the PDU session may be moved to EPS during its lifetime (see clause 6.1.6.2.31 of TS 29.502). Include if known.C
mAAcceptedIndicationSMFMAAcceptedIndication1 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 clauses 4.22.2 and 4.22.3 of TS 23.502).
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
aTSSSContainerATSSSContainer0..1Identifies 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.C
ePS5GSComboInfoEPS5GSComboInfo0..1 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
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
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
pFDDataForAppsPFDDataForApps0..1Represents a set of associations between application identifier and packet flow descriptions (PFDs), if available.C
ePSStartOfInterceptionWithEstablishedPDNConnectionEPSStartOfInterceptionWithEstablishedPDNConnection0..1 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
Up
6.2.3.2.7.6  SMF MA unsuccessful procedure  p. 102
The IRI-POI in the SMF shall generate an xIRI containing an SMFMAUnsuccessfulProcedure 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 for MA-Confirmed and MA-Upgrade-Allowed MA PDU sessions.
  • SMF sends a PDU SESSION MODIFICATION REJECT message to the target UE for MA-Confirmed and MA-Upgrade-Allowed MA PDU sessions.
  • SMF sends a PDU SESSION RELEASE REJECT message to the target UE for MA-Confirmed and MA-Upgrade-Allowed MA PDU sessions.
  • SMF receives a PDU SESSION MODIFICATION COMMAND REJECT message from the target UE for MA-Confirmed and MA-Upgrade-Allowed MA PDU sessions.
  • An ongoing SM procedure is aborted at the SMF, due to e.g. a 5GSM STATUS message sent from or received by the SMF for MA-Confirmed and MA-Upgrade-Allowed MA PDU sessions.
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
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
initiatorInitiator1Specifies whether the network (SMF) or the UE is initiating the rejection or indicating the failure.M
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
accessInfoSEQUENCE OF AccessInfo1..MAX Identifies the access(es) associated with the PDU session including the information for each specific access (see Table 6.2.3-5B).M
uEEndpointSEQUENCE OF UEEndpointAddress0..MAXUE endpoint address(es) if available.C
locationLocation0..1Location information provided by the AMF or present in the context at the SMF, 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 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
sMPDUDNRequestSMPDUDNRequest0..1Contents of the SM PDU DN Request container, if available, as described in clause 9.11.4.15 of TS 24.501.C
NOTE:
At least one identity shall be provided, the others shall be provided if available.
Up
6.2.3.2.8  PDU to MA PDU session modification  p. 102
The IRI-POI in the SMF shall generate an xIRI containing an SMFPDUtoMAPDUSessionModification record when the IRI-POI present in the SMF detects that an existing PDU session for the target UE has been successfully modified to an MA PDU session using the PDU session modification procedures as described in TS 24.501. A PDU session is considered to be successfully modified to a MA PDU session, when all of the following are true:
  1. The UE is registered to both 3GPP access and non-3GPP access:
    • In the same PLMN (non-roaming UE).
    • In the different PLMNs (roaming UE).
  2. SMF receives the PDU SESSION MODIFICATION REQUEST from the UE (clause 8.2.10 of TS 24.501) that includes one of the following:
    • modification request and includes MA PDU session information IE set to MA PDU session network upgrade allowed.
    • MA PDU request.
  3. SMF sends a PDU SESSION MODIFICATION COMMAND to the UE that includes the ATSSS IE (clause 6.4.2.3 of TS 24.501).
  4. SMF receives the PDU SESSION MODIFICATION COMPLETE from the UE (clause 8.3.10.1 of TS 24.501).
  5. The 5GSM state within the SMF is PDU Session Active.
Once the SMFPDUtoMAPDUSessionModification record has been generated by the IRI-POI in the SMF, the IRI-POI shall follow clause 6.2.3.2.7 of the present document for further reporting for this MA PDU session.
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
sUPIUnauthenticatedSUPIUnauthenticatedIndication0..1Shall 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
requestTypeFiveGSMRequestType1 In accordance with the request type as described in clause 6.4.2.2 of TS 24.501 and clause 9.11.3.47 a request type of "modification request" shall be reported. 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 available. Values given as per clause 5.4.3.2 of TS 29.571.C
pDUSessionIDPDUSessionID1PDU Session ID, see clause 9.4 of TS 24.501.M
requestIndicationRequestIndication1Indicates the request type for PDU session modification as indicated by the requestIndication sent in the PDU SESSION MODIFICATION REQUEST (see clause 6.1.6.3.6 of TS 29.502).M
aTSSSContainerATSSSContainer1Identifies 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.M
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
ePSPDNConnectionModificationEPSPDNConnectionModification0..1 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
Up

Up   Top   ToC