Content for TS 33.128 Word version: 18.6.0

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

6.3.3.2.4 PDU Session Release message reporting PDU session release, PDN Connection release 6.3.3.2.5 SMF Start of Interception with Already Established PDU Session message reporting Start of Interception with Already Established PDU Session or Start of Interception with Already Established PDN Connection 6.3.3.2.6 MA PDU Session Establishment message reporting MA PDU session establishment or PDN Connection establishment as part of an MA PDU Session 6.3.3.2.7 MA PDU Session Modification message reporting MA PDU session modification, modification of a PDN Connection associated to MA PDU session or inter-system handover 6.3.3.2.8 MA PDU Session Release message reporting MA PDU session release or the release of a PDN Connection associated to an MA PDU session 6.3.3.2.9 SMF Start of Interception with Already Established MA PDU Session message reporting Start of Interception with Already Established MA PDU Session or Start of Interception with Already Established PDN Connection associated to an MA PDU Session
...

6.3.3.2.4 PDU Session Release message reporting PDU session release, PDN Connection release p. 147

The IRI-POI in the SMF+PGW-C shall generate an xIRI containing an SMFPDUSessionRelease record (see clause 6.2.3.2.4) when the IRI-POI present in the SMF+PGW-C detects that a single-access PDU Session or PDN Connection has been released for the target UE. The IRI-POI present in the SMF+PGW-C shall generate the xIRI for the following events:

The SMF+PGW-C releases an existing PDN Connection in the target UE context of the SMF+PGW-C (see clause 5.7.4 of TS 23.401).
The SMF+PGW-C releases an existing PDU Session context or SM Context for the target UE (see clause 5.2.2.4 of TS 29.502 and clause 5.2.2.9).

When the SMFPDUSessionRelease record (see clause 6.2.3.2.4) is used to report the release of a PDN Connection:

The ePSPDNConnectionRelease field shall be populated with the information in Table 6.3.3-13.
If there is no SUPI associated to the SM context for the target UE, the SUPI field of the SMFPDUSessionRelease record shall be populated with the value of the IMSI from the target UE context.
If there is no PDU Session ID present in the PCO of the request or response messages or associated to the context for the PDN connection, the pDUSessionID field of the SMFPDUSessionRelease record shall be populated with the EBI of the default bearer for the PDN Connection.
If there is no 5G UP tunnel present in the context associated to the PDN Connection, the gTPTunnelID field of the SMFPDUSessionRelease record shall be populated with the F-TEID for the PGW S5 or S8 interface for the default bearer of the PDN Connection.

Table 6.3.3-13: Payload for ePSPDNConnectionRelease field

Field Name	Description	M/C/O
ePSSubscriberIDs	EPS Subscriber Identities associated with the PDN connection (e.g. as provided by the MME or SGW in the associated network message or as associated with the PDN connection in the context known at the NF). The IMSI shall be present except for unauthenticated emergency .	M
iMSIUnauthenticated	Shall be present if an IMSI is present in the ePSSubscriberIDs and set to "true" if the IMSI has not been authenticated, or "false" if it has been authenticated.	C
defaultBearerID	Shall contain the EPS Bearer Identity of the default bearer associated with the PDN connection.	M
location	Location information present in the network message (see clause 8.21 of TS 29.274) or known in the context at the SGW or PGW.	C
gTPTunnelInfo	Contains the information for the Control Plane GTP Tunnels present in the network message or known in the context at the SGW or PGW. See Table 6.2.3-1B. If the gTPTunnelInfo received in the network message is different than the gTPTunnelInfo in the context for the PDN Connection, this message shall be populated with the new information.	C
rANNASCause	Shall be present if the RAN/NAS Release Cause is present in the delete session request (see clause 7.2.9 of TS 29.274).	C
pDNConnectionType	Identifies selected PDN session type, see clause 8.34 of TS 29.274.	M
indicationFlags	Shall be included if the Indication Flags field is present in the network message (see clauses 7.2.3, 7.2.4, 7.2.7, 7.2.8, 7.2.9, 7.2.10, 7.2.15 and 7.2.16 of TS 29.274). The value of this parameter shall be set to the value of the Indication IE (see clause 8.12 of TS 29.274) starting with octet 5.	C
scopeIndication	This flag shall be present and set to True, if the request corresponds to TAU/RAU/Handover with SGW change/SRNS Relocation Cancel Using S4 with SGW change, Inter RAT handover Cancel procedure with SGW change, S1 Based handover Cancel procedure with SGW change. If this parameter is absent, it shall be interpreted as False.	C
bearersDeleted	Shall include a list of the Bearers to be deleted if the event that resulted in the generation of the message included a Delete Bearer Request or Response. (see clauses 7.2.9 and 7.2.10 of TS 29.274). See Table 6.3.3-10	C

6.3.3.2.5 SMF Start of Interception with Already Established PDU Session message reporting Start of Interception with Already Established PDU Session or Start of Interception with Already Established PDN Connection p. 148

The IRI-POI in the SMF+PGW-C shall generate an xIRI containing an SMFStartOfInterceptionWithEstablishedPDUSession record (see clause 6.2.3.2.5) when the IRI-POI present in the SMF+PGW-C detects that a single-access PDU Session or PDN Connection has already been established for the target UE when interception starts. The IRI-POI present in the SMF+PGW-C shall generate the xIRI for the following events:

The SMF+PGW-C has an existing PDN Connection in the target UE context of the SMF+PGW-C (see clause 5.7.4 of TS 23.401).
The SMF+PGW-C has an existing PDU Session context or SM Context for the target UE (see clause 5.2.2.2 of TS 29.502 and clause 5.2.2.7).

When the SMFStartOfInterceptionWithEstablishedPDUSession record (see clause 6.2.3.2.5) is used to report an existing PDN Connection:

The ePSStartOfInterceptionWithEstablishedPDNConnection field shall be populated with the information in Table 6.3.3-14.
If there is no SUPI associated to the SM context for the target UE, the SUPI field of the SMFStartOfInterceptionWithEstablishedPDUSession record shall be populated with the value of the IMSI from the target UE context.
If there is no PDU Session ID associated to the context for the PDN connection, the pDUSessionID field of the SMFStartOfInterceptionWithEstablishedPDUSession record shall be populated with the EBI of the default bearer for the PDN Connection.
If there is no 5G UP tunnel present in the context associated to the PDN Connection, the gTPTunnelID field of the SMFStartOfInterceptionWithEstablishedPDNConnection record shall be populated with the F-TEID for the PGW S5 or S8 interface for the default bearer of the PDN Connection.

Table 6.3.3-14: Payload for ePSStartOfInterceptionWithEstablishedPDNConnection field

Field Name	Description	M/C/O
ePSSubscriberIDs	EPS Subscriber Identities associated with the PDN connection (as associated with the PDN connection in the context known at the NF). The IMSI shall be present except for unauthenticated emergency sessions.	M
iMSIUnauthenticated	Shall be present if an IMSI is present in the ePSSubscriberIDs and set to "true" if the IMSI has not been authenticated, or "false" if it has been authenticated.	C
defaultBearerID	Shall contain the EPS Bearer Identity of the default bearer associated with the PDN connection.	M
gTPTunnelInfo	Contains the information for the Control Plane GTP Tunnels known in the context at the SGW or PGW. See Table 6.2.3-1B.	C
pDNConnectionType	Identifies selected PDN session type, see clause 8.34 of TS 29.274.	M
uEEndpoints	UE endpoint address(es) if available. Derived from the PDN Address portion of the PDN Address Allocation parameter (see clause 8.14 of TS 29.274) associated to the PDN Connection in the context known at the NF (see clauses 5.7.3 and 5.7.4 of TS 23.401).	C
non3GPPAccessEndpoint	UE's local IP address used to reach the ePDG, if known at the context at the SGW or PGW.	C
location	Location information known in the context at the SGW or PGW.	C
additionalLocation	Additional location information known in the context at the SGW or PGW, or known at the MDF.	C
aPN	Access Point Name associated with the PDN known at the context at the SGW or PGW (see clause 5.6.4 of TS 23.401), as defined in clause 9.1 of TS 23.003.	M
requestType	Type of request as derived from the Request Type described in clause 9.9.4.14 of TS 24.301 and clause 10.5.6.17 of TS 24.008, if available.	C
accessType	Access type associated with the PDN connection (i.e. 3GPP or non-3GPP access).	C
rATType	RAT Type associated with the PDN connection. Shall be present if known at the context at the SGW or PGW (see clause 5.6.4 of TS 23.401).	C
protocolConfigurationOptions	Shall be present the Protocol Configuration, Additional Protocol Configuration Options or extended Protocol Configuration Options are known in the context at the SGW or PGW. See Table 6.3.3-4.	C
servingNetwork	Shall be present if this IE is in the context for the PDN connection at the SGW/PGW.	C
bearerContexts	Shall include a list of the Bearer Contexts present in the UE Context (see clauses 5.7.3 and 5.7.4 of TS 23.401). See Table 6.3.3-2.	M

6.3.3.2.6 MA PDU Session Establishment message reporting MA PDU session establishment or PDN Connection establishment as part of an MA PDU Session p. 149

The IRI-POI in the SMF+PGW-C shall generate an xIRI containing an SMFMAPDUSessionEstablishment record (see clause 6.2.3.2.7) when the IRI-POI present in the SMF+PGW-C detects that a PDN Connection has been established for the target UE and associated to a multi-access PDU Session. The IRI-POI present in the SMF+PGW-C shall generate the xIRI for the following events:

The SMF+PGW-C creates a new PDN Connection in the target UE context of the SMF+PGW-C (see clause 5.7.4 of TS 23.401) and it is associated to an MA PDU session as described in clause 4.22.2.3 of TS 23.502.
The SMF+PGW-C creates a new multi-access PDU Session context or SM Context for the target UE (see clause 5.2.2.2 of TS 29.502 and clause 5.2.2.7).

When the SMFMAPDUSessionEstablishment record (see clause 6.2.3.2.7) is used to report the creation of a new PDN Connection:

The ePSPDNConnectionEstablishment field shall be populated with the information in Table 6.3.3-1.
If there is no SUPI associated to the SM context for the target UE, the SUPI field of the SMFMAPDUSessionEstablishment record shall be populated with the value of the IMSI from the target UE context.
If there is no PDU Session ID present in the PCO of the request or response messages or associated to the context for the PDN connection, the pDUSessionID field of the SMFMAPDUSessionEstablishment record shall be populated with the EBI of the default bearer for the PDN Connection.
If there is no 5G UP tunnel present in the context associated to the PDN Connection, the gTPTunnelID field of the SMFMAPDUSessionEstablishment record shall be populated with the F-TEID for the PGW S5 or S8 interface for the default bearer of the PDN Connection.

6.3.3.2.7 MA PDU Session Modification message reporting MA PDU session modification, modification of a PDN Connection associated to MA PDU session or inter-system handover p. 150

The IRI-POI in the SMF+PGW-C shall generate an xIRI containing an SMFMAPDUSessionModification record (see clause 6.2.3.2.7) when the IRI-POI present in the SMF+PGW-C detects that an MA PDU Session or PDN Connection associated to an MA PDU Session has been modified for the target UE. The IRI-POI present in the SMF+PGW-C shall generate the xIRI for the following events:

The SMF+PGW-C modifies an existing PDN Connection associated to an MA PDU Session in the target UE context of the SMF+PGW-C (see clause 5.7.4 of TS 23.401).
The SMF+PGW-C modifies an existing MA PDU Session context or SM Context for the target UE (see clause 5.2.2.3 of TS 29.502 and clause 5.2.2.8).
The SMF+PGW-C transfers the 3GPP Access Leg of an existing MA PDU Session to EPS (see clause 4.22.6 of TS 23.502).
The SMF+PGW-C transfers an existing PDN Connection associated to an MA PDU Session to 5GS (see clause 4.22.6 of TS 23.502).

When the SMFMAPDUSessionModification record (see clause 6.2.3.2.7) is used to report the modification of a PDN Connection:

The ePSPDNConnectionModification field shall be populated with the information in Table 6.3.3-8.
If there is no SUPI associated to the SM context for the target UE, the SUPI field of the SMFMAPDUSessionModification record shall be populated with the value of the IMSI from the target UE context.
If there is no PDU Session ID present in the PCO of the request or response messages or associated to the context for the PDN connection, the pDUSessionID field of the SMFMAPDUSessionModification record shall be populated with the EBI of the default bearer for the PDN Connection.
If there is no 5G UP tunnel present in the context associated to the PDN Connection, the gTPTunnelID field of the SMFMAPDUSessionModification record shall be populated with the F-TEID for the PGW S5 or S8 interface for the default bearer of the PDN Connection.

6.3.3.2.8 MA PDU Session Release message reporting MA PDU session release or the release of a PDN Connection associated to an MA PDU session p. 150

The IRI-POI in the SMF+PGW-C shall generate an xIRI containing an SMFMAPDUSessionRelease record (see clause 6.2.3.2.7) when the IRI-POI present in the SMF+PGW-C detects that an MA PDU Session or PDN Connection associated to an MA PDU Session has been released for the target UE. The IRI-POI present in the SMF+PGW-C shall generate the xIRI for the following events:

The SMF+PGW-C releases an existing PDN Connection associated to an MA PDU Session in the target UE context of the SMF+PGW-C (see clause 5.7.4 of TS 23.401).
The SMF+PGW-C releases an existing MA PDU Session context or SM Context for the target UE (see clause 5.2.2.4 of TS 29.502 and clause 5.2.2.9).

When the SMFMAPDUSessionRelease record (see clause 6.2.3.2.7) is used to report the release of a PDN Connection:

The ePSPDNConnectionRelease field shall be populated with the information in Table 6.3.3-13.
If there is no SUPI associated to the SM context for the target UE, the SUPI field of the SMFMAPDUSessionRelease record shall be populated with the value of the IMSI from the target UE context.
If there is no PDU Session ID present in the PCO of the request or response messages or associated to the context for the PDN connection, the pDUSessionID field of the SMFMAPDUSessionRelease record shall be populated with the EBI of the default bearer for the PDN Connection.
If there is no 5G UP tunnel present in the context associated to the PDN Connection, the gTPTunnelID field of the SMFMAPDUSessionRelease record shall be populated with the F-TEID for the PGW S5 or S8 interface for the default bearer of the PDN Connection.

6.3.3.2.9 SMF Start of Interception with Already Established MA PDU Session message reporting Start of Interception with Already Established MA PDU Session or Start of Interception with Already Established PDN Connection associated to an MA PDU Session p. 151

The IRI-POI in the SMF+PGW-C shall generate an xIRI containing an SMFStartOfInterceptionWithEstablishedMAPDUSession record (see clause 6.2.3.2.7) when the IRI-POI present in the SMF+PGW-C detects that an MA PDU Session or PDN Connection associated to an MA PDU Session has already been established for the target UE when interception starts. The IRI-POI present in the SMF+PGW-C shall generate the xIRI for the following events:

The SMF+PGW-C has an existing PDN Connection associated to an MA PDU Session in the target UE context of the SMF+PGW-C (see clause 5.7.4 of TS 23.401).
The SMF+PGW-C has an existing MA PDU Session context or SM Context for the target UE (see clause 5.2.2.2 of TS 29.502 and clause 5.2.2.7).

When the SMFStartOfInterceptionWithEstablishedMAPDUSession record (see clause 6.2.3.2.7) is used to report an existing PDN Connection:

The ePSStartOfInterceptionWithEstablishedPDNConnection field shall be populated with the information in Table 6.3.3-14.
If there is no SUPI associated to the SM context for the target UE, the SUPI field of the SMFStartOfInterceptionWithEstablishedMAPDUSession record shall be populated with the value of the IMSI from the target UE context.
If there is no PDU Session ID associated to the context for the PDN connection, the pDUSessionID field of the SMFStartOfInterceptionWithEstablishedMAPDUSession record shall be populated with the EBI of the default bearer for the PDN Connection.
If there is no 5G UP tunnel present in the context associated to the PDN Connection, the gTPTunnelID field of the SMFStartOfInterceptionWithEstablishedMAPDUSession record shall be populated with the F-TEID for the PGW S5 or S8 interface for the default bearer of the PDN Connection.