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.3.3.2 Generation of xIRI over LI_X2  6.3.3.2.1 General  6.3.3.2.2 PDU Session Establishment message reporting PDU session establishment or PDN Connection establishment  6.3.3.2.3 PDU Session Modification message reporting PDU session modification, PDN Connection modification or inter-system handover 
...

 

6.3.3.2  Generation of xIRI over LI_X2  p. 144

6.3.3.2.1  General  p. 144
When Option A specified in clause 6.3.1 is used:
When Option B specified in clause 6.3.1 is used:
  • The IRI-POI present in the SGW/PGW and ePDG shall send the xIRIs over LI_X2 for each of the events listed in clause 12.2.1.2 of TS 33.107, the details of which are specified in clause 12.2.3 of the same TS.
  • The IRI-POI present in the SGW/PGW and ePDG shall set the payload format to EpsHI2Operations.EpsIRIContent (value 14), see clause 5.3 and ETSI TS 103 221-2 [8] clause 5.4. The payload field shall contain an EpsHI2Operations.EpsIRIContent structure encoded according to clauses 10.5 and B.9 of TS 33.108.
  • As the LIID may not be available at the SGW/PGW and ePDG but is mandatory in EpsHI2Operations.­EpsIRIContent according to TS 33.108 Annex B.9, its value in the lawfulInterception­Identifier field of the encoded PDU shall be set to the fixed string "LIIDNotPresent".
Up
6.3.3.2.2  PDU Session Establishment message reporting PDU session establishment or PDN Connection establishment  p. 145
The IRI-POI in the SMF+PGW-C shall generate an xIRI containing an SMFPDUSessionEstablishment record (see clause 6.2.3.2.2) when the IRI-POI present in the SMF+PGW-C detects that a single-access PDU Session or PDN Connection has been established for the target UE. The IRI-POI present in the SMF+PGW-C shall generate the xIRI for the following events:
When the SMFPDUSessionEstablishment record (see clause 6.2.3.2.2) 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 SMFPDUSessionEstablishment 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 SMFPDUSessionEstablishment 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 SMFPDUSessionEstablishment record shall be populated with the F-TEID for the PGW S5 or S8 interface for the default bearer of the PDN Connection.
Field Name Description M/C/O
ePSSubscriberIDsEPS Subscriber Identities associated with the PDN connection (e.g. as provided by the MME or SGW in the associated Create Session Request 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
defaultBearerIDShall contain the EPS Bearer Identity of the default bearer associated with the PDN connection.M
defaultBearerIDShall 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 present in the Create Session Request or known in the context at the SGW or PGW. See Table 6.2.3-1B.C
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) present in the Create Session Request or the IP Address 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
pDNConnectionTypeIdentifies selected PDN session type, see clause 8.34 of TS 29.274.M
non3GPPAccessEndpointUE's local IP address used to reach the ePDG, if present in the Create Session Request (see clause 7.2.1 of TS 29.274) or known at the context at the SGW or PGW.C
locationLocation information present in the Create Session Request (see clause 7.2.1 of TS 29.274) or known in the context at the SGW or PGW.C
additionalLocationAdditional location information present in the Create Session Request, known in the context at the SGW or PGW, or known at the MDF.C
aPN Access Point Name associated with the PDN connection present in the Create Session Request (see clauses 7.2.1 and 8.6 of TS 29.274) or 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
requestTypeType 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
accessTypeAccess type associated with the PDN connection (i.e. 3GPP or non-3GPP access). Shall be set to nonThreeGPPAccess by the ePDG or by the PGW when the Create Session Request for the PDN connection is received from an ePDG. Shall be set to threeGPPAccess by the SGW or by the PGW when the Create Session Request for the PDN connection is received from an SGW.C
rATTypeRAT Type associated with the PDN connection. Shall be present if included in the Create Session Request (see clause 7.2.1 of TS 29.274) or known at the context at the SGW or PGW (see clause 5.6.4 of TS 23.401).C
protocolConfigurationOptions Shall be present if the Create Session Request or the Create Session Response (see clause 7.2.2 of TS 29.274 and clause 7.2.3) contains the Protocol Configuration, Additional Protocol Configuration Options or extended Protocol Configuration Options IE. See Table 6.3.3-4.C
servingNetworkShall be present if this IE is in the Create Session Request or the context for the PDN connection at the SGW/PGW.C
sMPDUDNRequestContents of the SM PDU DN Request container, if available, as described in clause 9.11.4.15 of TS 24.501.C
bearerContextsCreated Shall include a list of the Bearer Contexts created sent in the Create Session Response message (see clause 7.2.2 of TS 29.274). See Table 6.3.3-2.M
bearerContextsMarkedForRemoval Shall include a list of the Bearer Contexts to be removed sent in the Create Session Response message (see clause 7.2.2 of TS 29.274). See Table 6.3.3-3.C
indicationFlagsShall be included if the Indication Flags field is present in the Create Session Request (see clause 7.2.1 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
handoverIndication Shall be present if the Handover Indication is set to 1 in the Create Session Request (see clauses 7.2.1 and 8.12 of TS 29.274).C
nBIFOMSupport Shall be present if the NBIFOM Support Indication is set to 1 in the Create Session Request (see clauses 7.2.1 and 8.12 of TS 29.274).C
fiveGSInterworkingInfo Shall be present if the 5GS Interworking Indication is present in the Create Session Request (see clauses 7.2.1 and 8.12 of TS 29.274). See Table 6.3.3-5.C
cSRMFI Shall be present if the Create Session Request Message Forwarded Indication (CSRMFI) is present in the Create Session Request (see clauses 7.2.1 and 8.12 of TS 29.274). Indicates the Create Session Request message has been forwarded by a PGW.C
restorationOfPDNConnectionsSupport Shall be present if the Restoration of PDN connection after an PGW-C/SMF Change Support Indication is present in the Create Session Request (see clauses 7.2.1 and 8.12 of TS 29.274).C
pGWChangeIndication Shall be present if the PGW Change Indication is present in the Create Session Request (see clauses 7.2.1 and 8.12 of TS 29.274).C
pGWRNSI Shall be present if the PGW Redirection due to mismatch with Network Slice subscribed by the UE Support Indication is present in the Create Session Request (see clauses 7.2.1 and 8.12 of TS 29.274).C
Field Name Description M/C/O
ePSBearerID Shall include the EPS bearer ID for the EPS Bearer (See clauses 7.2.2 and 7.2.4 of TS 29.274).M
cause Shall indicate whether the bearer handling was successful and if not, it gives information on the reason (see clauses 7.2.2 and 7.2.4 of TS 29.274). Sent as an integer cause value (see TS 29.274 Table 8.4-1)M
gTPTunnelInfo Contains 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). See Table 6.2.3-1B.C
bearerQOS Shall include the QOS information for the bearer if present in the Request or Response (see clauses 7.2.2, 7.2.15 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). See Table 6.3.3-7.C
protocolConfigurationOptions Shall be present if the Bearer Context reported (see clauses 7.2.2, 7.2.3, and 7.2.4 of TS 29.274) contains the Protocol Configuration, Additional Protocol Configuration Options or extended Protocol Configuration Options IE. See Table 6.3.3-4.C
Field Name Description M/C/O
ePSBearerID Shall include the EPS bearer ID for the EPS Bearer (See clause 7.2.2 of TS 29.274, 7.2.8 and 7.2.10).M
cause Shall indicate whether the bearer handling was successful and if not, it gives information on the reason (see clause 7.2.2 of TS 29.274, 7.2.8 and 7.2.10).M
Field Name Description M/C/O
requestPCOShall be present if the Protocol Configuration Options IE is present in the request message. The value of this parameter shall contain a copy of the value field of the PCO IE of the request message (see clause 8.13 of TS 29.274 starting with octet 5).C
requestAPCOShall be present if the Additional Protocol Configuration Options IE is present in the request message. The value of this parameter shall contain a copy of the value field of the PCO IE of the request message (see clause 8.94 of TS 29.274 starting with octet 5).C
requestEPCOShall be present if the Extended Protocol Configuration Options IE is present in the request message. The value of this parameter shall contain a copy of the value field of the PCO IE of the request message (see clause 8.128 of TS 29.274 starting with octet 5).C
responsePCOShall be present if the Protocol Configuration Options IE is present in the response message. The value of this parameter shall contain a copy of the value field of the PCO IE of the response message (see clause 8.13 of TS 29.274 starting with octet 5).C
responseAPCOShall be present if the Additional Protocol Configuration Options IE is present in the response message. The value of this parameter shall contain a copy of the value field of the PCO IE of the response message (see clause 8.94 of TS 29.274 starting with octet 5).C
responseEPCOShall be present if the Extended Protocol Configuration Options IE is present in the response message. The value of this parameter shall contain a copy of the value field of the PCO IE of the response message (see clause 8.128 of TS 29.274 starting with octet 5).C
Field Name Description M/C/O
fiveGSInterworkingIndicator Shall be set toTRUE if the 5GSIWKI flag in the Indication IE of the request or response is set to 1. Indicates that the UE supports N1 mode and the PDN connection is not restricted from interworking by the 5GS user subscription. See clauses 7.2.1 and 8.12 of TS 29.274.M
fiveGSInterworkingWithoutN26 Shall be set to TRUE if the 5GS Interworking without N26 Indication flag in the Indication IE of the request or response is set to 1. If the 5GS Interworking without N26 Indication flag in the Indication IE of the request or response is set to 0 or not present, this parameter shall be set to FALSE. See TS clauses 7.2.1 and 8.12 of 29.274 [87].M
fiveGCNotRestrictedSupport Shall be set to True if the 5GCNRS (5GC Not Restricted Support) flag in the Indication IE of the request or response is set to 1. If the 5GCNRS flag in the Indication IE of the request or response is set to 0 or not present, this parameter shall be set to FALSE. See clauses 7.2.1 and 8.12 of TS 29.274.M
Field Name Description M/C/O
controlPlaneSenderFTEID Shall include the Sender F-TEID for the control plane if present in the Request or response (See clause 7.2.1 of TS 29.274, 7.2.2, 7.2.3, 7.2.4, 7.2.7, 7.2.8, 7.2.15, 7.2.16) or known in the context at the SGW or PGW.C
controlPlanePGWS5S8FTEID Shall include the PGW F-TEID for the control plane if present in the Request or response (See clause 7.2.1 of TS 29.274, 7.2.2, 7.2.3, 7.2.4, 7.2.7, 7.2.8, 7.2.15, 7.2.16) or known in the context at the SGW or PGW.C
s1UeNodeBFTEID Shall include the F-TEID for the eNodeB S1-U interface for the bearer if present in the Request or response (See clause 7.2.1 of TS 29.274, 7.2.2, 7.2.3, 7.2.4, 7.2.7, 7.2.8, 7.2.15, 7.2.16) or known in the context at the SGW or PGW.C
s5S8SGWFTEID Shall include the F-TEID for the SGW S5 or S8 interface for the bearer if present in the Request or response (See clause 7.2.1 of TS 29.274, 7.2.2, 7.2.3, 7.2.4, 7.2.7, 7.2.8, 7.2.15, 7.2.16) or known in the context at the SGW or PGW.C
s5S8PGWFTEID Shall include the F-TEID for the PGW S5 or S8 interface for the bearer if present in the Request or response (See clause 7.2.1 of TS 29.274, 7.2.2, 7.2.3, 7.2.4, 7.2.7, 7.2.8, 7.2.15, 7.2.16) or known in the context at the SGW or PGW.C
s2bUePDGFTEID Shall include the F-TEID for the ePDG on the S2b-U interface for the bearer if present in the Request or response (See clause 7.2.1 of TS 29.274, 7.2.2, 7.2.3, 7.2.4, 7.2.7, 7.2.8, 7.2.15, 7.2.16) or known in the context at the PGW or ePDG.C
s2aUePDGFTEID Shall include the F-TEID for the ePDG on the S2a-U interface for the bearer if present in the Request or response (See clause 7.2.1 of TS 29.274, 7.2.2, 7.2.3, 7.2.4, 7.2.7, 7.2.8, 7.2.15, 7.2.16) or known in the context at the PGW or ePDG.C
Field Name Description M/C/O
qCI Shall include the QCI for the bearer if present in the Request or response (See clause 7.2.1 of TS 29.274, 7.2.2, 7.2.3 and 7.2.15), or known in the context at the SGW or PGW.C
maximumUplinkBitRate Shall include the maximum uplink bitrate encoded as kilobits per second in binary value (see clause 8.15 of TS 29.274) if present in the Request or response (See clause 7.2.1 of TS 29.274, 7.2.2, 7.2.3 and 7.2.15), or known in the context at the SGW or PGW.C
maximumDownlinkBitRate Shall include the maximum downlink bitrate encoded as kilobits per second in binary value (see clause 8.15 of TS 29.274) if present in the Request or response (See clause 7.2.1 of TS 29.274, 7.2.2, 7.2.3 and 7.2.15), or known in the context at the SGW or PGW.C
guaranteedUplinkBitRate Shall include the guaranteed uplink bitrate encoded as kilobits per second in binary value (see clause 8.15 of TS 29.274) if present in the Request or response (See clause 7.2.1 of TS 29.274, 7.2.2, 7.2.3 and 7.2.15), or known in the context at the SGW or PGW.C
guaranteedDownlinkBitRate Shall include the guaranteed downlink bitrate encoded as kilobits per second in binary value (see clause 8.15 of TS 29.274) if present in the Request or response (See clause 7.2.1 of TS 29.274, 7.2.2, 7.2.3 and 7.2.15), or known in the context at the SGW or PGW.C
priorityLevel Shall include the priority level assigned to the bearer as an integer value (see clause 8.15 of TS 29.274) if present in the Request or response (See clause 7.2.1 of TS 29.274, 7.2.2, 7.2.3 and 7.2.15), or known in the context at the SGW or PGW.C
Up
6.3.3.2.3  PDU Session Modification message reporting PDU session modification, PDN Connection modification or inter-system handover  p. 149
The IRI-POI in the SMF+PGW-C shall generate an xIRI containing an SMFPDUSessionModification record (see clause 6.2.3.2.3) when the IRI-POI present in the SMF+PGW-C detects that a single-access PDU Session or PDN Connection has been modified for the target UE. The IRI-POI present in the SMF+PGW-C shall generate the xIRI for the following events:
When the SMFPDUSessionModification record (see clause 6.2.3.2.3) 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 SMFPDUSessionModification 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 SMFPDUSessionModification 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 SMFPDUSessionModification record shall be populated with the F-TEID for the PGW S5 or S8 interface for the default bearer of the PDN Connection.
Field name Type Cardi­nality Description M/C/O
ePSSubscriberIDsEPSSubscriberIDs1EPS 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
iMSIUnauthen­ticatedIMSIUnauthen­ticatedIndication0..1 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
defaultBearerIDEPSBearerID1Shall contain the EPS Bearer Identity of the default bearer associated with the PDN connection.M
gTPTunnelInfoGTPTunnelInfo0..1 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
pDNConnectionTypePDNConnectionType1Identifies selected PDN session type, see clause 8.34 of TS 29.274.M
uEEndpointsSEQUENCE OF UEEndpointAddress0..MAX 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) present in the network message or the IP Address 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
non3GPPAccessEndpointUEEndpointAddress0..1 UE's local IP address used to reach the ePDG, if present in the network message (see clauses 7.2.4, 7.2.7 and 7.2.16 of TS 29.274) or known at the context at the SGW or PGW.C
locationLocation0..1Location 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
additionalLocationLocation0..1Additional location information present in the network message, known in the context at the SGW or PGW, or known at the MDF.C
aPNAPN1Access Point Name associated with the PDN connection present in the network message (see clause 8.6 of TS 29.274) or 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
requestTypeEPSPDNConnectionRequestType0..1Type 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
accessTypeAccessType0..1Access type associated with the PDN connection (i.e. 3GPP or non-3GPP access).C
rATTypeRATType0..1 RAT Type associated with the PDN connection. Shall be present if included 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) or known at the context at the SGW or PGW (see clause 5.6.4 of TS 23.401).C
protocolConfigurationOptionsPDNProtocolConfigurationOptions0..1 Shall be present if the network message (see TS 29.274) contains the Protocol Configuration Options, Additional Protocol Configuration Options or extended Protocol Configuration Options IE. See Table 6.3.3-4.C
servingNetworkSMFServingNetwork0..1Shall be present if this IE is in the network message or the context for the PDN connection at the SGW/PGW.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
bearerContextsCreatedSEQUENCE OF EPSBearerContextCreated0..MAX Shall include a list of the Bearer Contexts created if the event that resulted in the generation of the message was the activation of a dedicated Bearer. Shall contain the contents of the Bearer Context field of the Create Bearer Response message (see clause 7.2.4 of TS 29.274). See Table 6.3.3-2.C
bearerContextsModifiedSEQUENCE OF EPSBearerContextModified1..MAXIf the event that resulted in the generation of the message was the modification of an existing bearer, shall be populated from the contents of the Bearer Contexts Modified field of the Modify Bearer Response message (see clause 7.2.8 of TS 29.274) or the Bearer Contexts within the Update Bearer Response message (see clause 7.2.16 of TS 29.274).
If the event that resulted in the generation of the message was the establishment or release of a dedicated bearer context, then this field shall be populated with the information for the default bearer.
See Table 6.3.3-9.		M
bearerContextsMarkedForRemovalSEQUENCE OF EPSBearerContextForRemoval0..MAX Shall include a list of the Bearer Contexts to be removed if the event that resulted in the generation of the message included the removal of an existing bearer. (see clause 7.2.8 of TS 29.274 and 7.2.10). See Table 6.3.3-3.C
bearersDeletedSEQUENCE OF EPSBearersDeleted 0..MAX 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-10C
indicationFlagsPDNConnectionIndicationFlags0..1 Shall be included if the Indication Fla eporte 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
handoverIndicationPDNHandoverIndication0..1 Shall be present if the Handover Indication is set to 1 in the Modify Bearer Request (see clauses 7.2.7 and 8.12 of TS 29.274).C
nBIFOMSupportPDNNBIFOMSupport0..1 Shall be present if the NBIFOM Support Indication is set to 1 in the message that triggered the generation of the xIRI or known at the context (see clauses 7.2.1, 7.2.7 and 8.12 of TS 29.274).C
fiveGSInterworkingInfoFiveGSInterworkingInfo0..1 Shall be present if the 5GS Interworking Indication is present in the Create Session Request (see clauses 7.2.1 and 8.12 of TS 29.274). See Table 6.3.3-5.C
cSRMFICSRMFI0..1 Shall be present if the Create Session Request Message Forwarded Indication (CSRMFI) is present in the Create Session Request (see clauses 7.2.1 and 8.12 of TS 29.274). Indicates the Create Session Request message has been forwarded by a PGW.C
restorationOfPDNConnectionsSupportRestorationOfPDNConnectionsSupport0..1 Shall be present if the Restoration of PDN connection after an PGW-C/SMF Change Support Indication is present in the message that triggered the generation of the xIRI or known at the context (see clauses 7.2.1, 7.2.7 and 8.12 of TS 29.274).C
pGWChangeIndicationPGWChangeIndication0..1 Shall be present if the PGW Change Indication is present in the Create Session Request (see clauses 7.2.1 and 8.12 of TS 29.274).C
pGWRNSIPGWRNSI0..1 Shall be present if the PGW Redirection due to mismatch with Network Slice subscribed by the UE Support Indication is present in the Create Session Request (see clauses 7.2.1 and 8.12 of TS 29.274).C
Field name Type Cardi­nality Description M/C/O
ePSBearerIDEPSBearerID1 Shall include the EPS bearer ID for the EPS Bearer (See clauses 7.2.7, 7.2.8, 7.2.15 and 7.2.16 of TS 29.274).M
causeEPSBearerModificationCauseValue1 Shall indicate whether the bearer handling was successful and if not, it gives information on the reason (See clauses 7.2.7, 7.2.8, 7.2.15 and 7.2.16 of TS 29.274). Sent as an integer cause value (see TS 29.274 Table 8.4-1)M
gTPTunnelInfoGTPTunnelInfo0..1 Contains the information for the User Plane GTP Tunnels for the bearer context if present in the Request or Response (see clauses 7.2.7, 7.2.8, 7.2.15, 7.2.16 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). See Table 6.2.3-1B.C
bearerQOSEPSBearerQOS0..1 Shall include the QOS information for the bearer if present in the Request or Response (see clauses 7.2.7, 7.2.8, 7.2.15, 7.2.16 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). See Table 6.3.3-7.C
protocolConfigurationOptionsPDNProtocolConfigurationOptions0..1 Shall be present if the Bearer Context reported (see clauses 7.2.7, 7.2.8, 7.2.15, 7.2.16 and 8.15 of TS 29.274) contains the Protocol Configuration, Additional Protocol Configuration Options or extended Protocol Configuration Options IE. See Table 6.3.3-4.C
linkedEPSBearerIDsSEQUENCE OF EPSBearerID0..MAXShall be present if there are any linked EPS bearers. If the bearer context bei eporte dis is the default bearer, then this list shall be populated with all dedicated bearers linked to that default bearer. If the bearer being reported is a dedicated bearer, then this field shall be populated with the default bearer.C
Field name Type Cardi­nality Description M/C/O
linkedEPSBearerIDEPSBearerID0..1Shall include the EBI for the default bearer associated with the PDN being disconnected if all bearers belonging to a PDN connection are being released (See clause 7.2.9 of TS 29.274).C
ePSBearerIDsSEQUENCE OF EPSBearerID0..MAXShall include a list of the EPS Bearer IDs to be deleted if only some of the EPS Bearers belonging to a PDN Connection are being released (see clause 7.2.9 of TS 29.274).C
protocolConfigurationOptionsPDNProtocolConfigurationOptions0..1 Shall be present if the Delete Bearer Request or Response reported (see clauses 7.2.9 of TS 29.274) contains the Protocol Configuration, Additional Protocol Configuration Options or extended Protocol Configuration Options IE. See Table 6.3.3-4.C
causeEPSBearerDeletionCauseValue0..1Shall indicate the reason the EPS Bearers are being deleted (See clause 7.2.9 of TS 29.274). Sent as an integer cause value (see TS 29.274 Table 8.4-1)C
deleteBearerResponseEPSDeleteBearerResponse1 Shall contain information from the Delete Bearer Response (See clause 7.2.10 of TS 29.274). See Table 6.3.3-11.M
Field name Type Cardi­nality Description M/C/O
causeEPSBearerDeletionCauseValue1Indicates whether the bearers requested for deletion were successfully deleted (See clause 7.2.10 of TS 29.274).M
linkedEPSBearerIDEPSBearerID0..1Shall include the EBI for the default bearer associated with the PDN being disconnected if all bearers belonging to a PDN connection are being released (See clause 7.2.10 of TS 29.274).C
bearerContextsSEQUENCE OF EPSDeleteBearerContext0..MAX Shall include a list of the EPS Bearer Contexts requested for deletion along with details on whether they were successfully deleted. Shall be included if only some of the EPS Bearers belonging to a PDN Connection are being released (see clause 7.2.10 of TS 29.274). See Table 6.3.3-12.C
protocolConfigurationOptionsPDNProtocolConfigurationOptions0..1 Shall be present if the Delete Bearer Request or Response reported (see clauses 7.2.9 of TS 29.274) contains the Protocol Configuration, Additional Protocol Configuration Options or extended Protocol Configuration Options IE. See Table 6.3.3-4.C
Field name Type Cardi­nality Description M/C/O
causeEPSBearerDeletionCauseValue1Indicates whether the bearers requested for deletion were successfully deleted (See clause 7.2.10 of TS 29.274).M
ePSBearerIDEPSBearerID1Shall include the EBI for the bearer (See clause 7.2.10 of TS 29.274).M
protocolConfigurationOptionsPDNProtocolConfigurationOptions 0..1 Shall be present if the Delete Bearer Request or Response reported (see clauses 7.2.9 of TS 29.274) contains the Protocol Configuration, Additional Protocol Configuration Options or extended Protocol Configuration Options IE. See Table 6.3.3-4.C
rANNASCauseEPSRANNASCause0..1Shall be present if the RAN/NAS Release Cause is present in the delete session response bearer context (see clause 7.2.10 of TS 29.274). Shall be sent as an Octet String encoded as specified in clause 8.103 of TS 29.274.C
Up

Up   Top   ToC