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.6.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.2.2A Definitions for MME message Types  6.3.2.2A.1 Simple data types  6.3.2.2A.2 Type: EPSHandoverType  6.3.2.2A.3 Type: ERABContextList  6.3.2.2A.4 Type: ERABContext  6.3.2.2A.5 Type: ERABReleaseList  6.3.2.2A.6 Type: ERABError  6.3.2.2A.7 Type: EPSRANCause  6.3.2.2A.8 Type: EPSHandoverRestrictionList  6.3.2.2A.9 Type: EPSCSGInfo  6.3.2.2A.10 Type: EPSProSeAuthorization  6.3.2.2A.11 Type: EPSSubscriptionBasedUEDifferentiationIndication  6.3.2.2A.12 Type: S1Information  6.3.2.2A.13 Type: MMEServedGUMMEIList  6.3.2.2A.14 Type: MMEServedGUMMEI  6.3.2.2A.15 Type: EPSNASTransportInitialInformation  6.3.2.2A.16 Type: BBFTunnelInformation  6.3.2.2A.17 Type: LTENTNTAIInformation  6.3.2.2A.18 Type: EPSRANUEContext  6.3.2.2A.19 Enumeration: EPSCSFallbackIndicator  6.3.2.3 Generation of IRI over LI_HI2  6.3.2.3.1 General  6.3.2.3.2 Option A  6.3.2.3.3 Option B and Option C 
...

 

6.3.2.2A  Definitions for MME message Types  p. 127

6.3.2.2A.1  Simple data types  p. 127
Type name Type definition Description
MMEUES1APIDINTEGER (0..4294967295)Identity that the MME uses to uniquely identify the target UE over the S1 Interface. See clause 9.2.3.3 of TS 36.413.
RANUES1APIDINTEGER (0.. 16777215)Identity that the eNB uses to uniquely identify the target UE over the S1 Interface. See clause 9.2.3.4 of TS 36.413.
EPSUENetworkCapabilityOCTET STRING (SIZE(2..13))Contains the target UE network capability information encoded per clause 9.9.3.34 of TS 24.301, omitting the first two octets.
EPSUERadioCapabilityOCTET STRINGIndicates the radio capabilities of the UE. Encoded per clause 9.2.1.27 of TS 36.413.
EPSNetworkPolicyOCTET STRING (SIZE(1))Indicates network policy information to the UE. Encoded per clause 9.9.3.52 of TS 24.301.
Up
6.3.2.2A.2  Type: EPSHandoverType  p. 127
The EPSHandoverType provides information about the type of handover being performed in EPS. Defined in clause 9.2.1.13 of TS 36.413.
Table 6.3.2.2A.2-1 contains the details of the EPSHandoverType type.
Field name Type Cardi­nality Description M/C/O
eSHandoverTypeExternalASNType1Indicates the type of handover. The ExternalASNType.encodedASNValue.alignedPER choice shall be used when populating this type and it shall be populated with the contents of the the Cause IE from clause 9.2.1.13 of TS 36.413.M
Up
6.3.2.2A.3  Type: ERABContextList  p. 127
Table 6.3.2.2A.3-1 contains the details for the ERABContextList type.
Type name Definition Cardi­nality Description
ERABContextListSEQUENCE OF ERABContext1..MAXContains a list of E-RAB Contexts.
Up
6.3.2.2A.4  Type: ERABContext  p. 128
Table 6.3.2.2A.4-1 contains the details for the ERABContext type.
Field name Type Cardi­nality Description M/C/O
eRABIDEPSBearerID1This element uniquely identifies a radio access bearer for a particular UE, which makes the E-RAB ID unique over one S1 connection. Derived from the E-RAB ID IE, see clause 9.2.1.2 of TS 36.413.M
eRABQoSParametersERABQoSParameters0..1The QOS parameters to be assigned to an E-RAB. Derived from the E-RAB Level QoS Parameters defined in clause 9.2.1.15 of TS 36.418 [38]. Shall be present if present in the messages for the procedure that triggered the xIRI or known at the NF context.C
transportLayerAddressIPAddr0..1The local IP Address assigned to the UE for the E-RAB. See clause 9.2.2.1 of TS 36.418 [38]. Shall be present if present in the messages for the procedure that triggered the xIRI or known at the NF context.C
uLGTPTEIDFTEID0..1The uplink tunnel information for the E-RAB. See clause 9.2.2.2 of TS 36.418 [38]. Shall be present if present in the messages for the procedure that triggered the xIRI or known at the NF context.C
dLGTPTEIDFTEID0..1The downlink tunnel information for the E-RAB. See clause 9.2.2.2 of TS 36.418 [38]. Shall be present if present in the messages for the procedure that triggered the xIRI or known at the NF context.C
Up
6.3.2.2A.5  Type: ERABReleaseList  p. 128
Table 6.3.2.2A.5-1 contains the details for the ERABReleaseList type.
Type name Definition Cardi­nality Description
ERABReleaseListSEQUENCE OF ERABError1..MAXContains a list of E-RABs that are released along with the cause.
Up
6.3.2.2A.6  Type: ERABError  p. 128
Table 6.3.2.2A.6-1 contains the details for the ERABErrortype.
Field name Type Cardi­nality Description M/C/O
eRABIDEPSBearerID1This element uniquely identifies a radio access bearer for a particular UE, which makes the E-RAB ID unique over one S1 connection. Derived from the E-RAB ID IE, see clause 9.2.1.2 of TS 36.413.M
causeEPSRANCause1Indicates the cause of the E-RAB release. Derived from the Cause IE from clause 9.2.1.3 of TS 36.413.M
Up
6.3.2.2A.7  Type: EPSRANCause  p. 129
Field name Type Cardi­nality Description M/C/O
ePSRANCauseExternalASNType1Indicates the cause for the procedure indicated by the RAN or MME. The ExternalASNType.encodedASNValue.alignedPER choice shall be used when populating this type and it shall be populated with the contents of the the Cause IE from clause 9.2.1.3 of TS 36.413.M
Up
6.3.2.2A.8  Type: EPSHandoverRestrictionList  p. 129
This IE is derived from the Handover Restriction List IE defined in clause 9.2.1.22 of TS 36.413. This information describes roaming or access restrictions for subsequent mobility of a UE.
Table 6.3.2.2A.8-1 contains the details for the EPSHandoverRestrictionList.
Field name Type Cardi­nality Description M/C/O
ePSHandoverRestrictionListExternalASNType1Indicates roaming or access restrictions for subsequent mobility of a UE. The ExternalASNType.encodedASNValue.alignedPER choice shall be used when populating this type and it shall be populated with the contents of the the Handover Restriction List IE defined in clause 9.2.1.22 of TS 36.413.M
Up
6.3.2.2A.9  Type: EPSCSGInfo  p. 129
Table 6.3.2.2A.9-1 contains the details for the EPSCSGInfo type.
Field name Type Cardi­nality Description M/C/O
cSGIDCSGID0..1Indicates the CSG being described.C
cSGMembershipStatusCSGMembershipIndication0..1Indicates the user's membership status for the indicated CSG. Shall be included if known at the NF where the POI is located.C
Up
6.3.2.2A.10  Type: EPSProSeAuthorization  p. 129
Table 6.3.2.2A.10-1 contains the details for the EPSProSeAuthorization type.
Field name Type Cardi­nality Description M/C/O
ePSProSeAuthorizationExternalASNReference0..1Indicates EPS ProSe Authorizations for a UE. The ExternalASNType.encodedASNValue.alignedPER choice shall be used when populating this type and it shall be populated with the contents of the the ProSe Authorized IE defined in clause 9.2.1.99 of TS 36.413.C
Up
6.3.2.2A.11  Type: EPSSubscriptionBasedUEDifferentiationIndication  p. 130
Table 6.3.2.2A.11-1 contains the details for the EPSSubscriptionBasedUEDifferentiationIndication type. This information is derived from the Subscription Based UE Differentiation Information IE defined in clause 9.2.1.140 of TS 36.413.
Field name Type Cardi­nality Description M/C/O
ePSSubscriptionBasedUEDifferentiationIndicationExternalASNReference0..1Indicates subscription based UE differentiation information for a UE. Shall be present when the Subscription Based UE Differentiation Information IE defined in clause 9.2.1.140 of TS 36.413 is present in messages exchanged as part of the procedure that triggered the generation of the xIRI.C
Up
6.3.2.2A.12  Type: S1Information  p. 130
Table 6.3.2.2A.12-1 contains the details for the S1Information type. This information is derived from the S1 SETUP REQUEST and S1 SETUP RESPONSE. See clauses 9.1.8.4 and 9.1.8.5 of TS 36.413.
Field name Type Cardi­nality Description M/C/O
globalRANNodeIDGlobalRANNodeID0..1The ID of the RAN Node from which the message was received. Shall be present if known at the NF where the POI is located.C
rANNodeNameRANNodeName0..1The RAN Node Name for the the RAN Node from which the message was received. Shall be present if known at the NF where the POI is located.C
supportedTAListSupportedTAList0..1The list of TAIs supported by the RAN Node. Shall be present if known at the NF where the POI is located.C
cSGIDListCSGIDList0..1A list of the closed subscriber groups supported by the RAN Node. Shall be present if known at the NF where the POI is located.C
connectedENGNBListConnectedENGNBList0..1A list of the en-gNBs connected to the RAN Node. Shall be present if known at the NF where the POI is located.C
mMEServedGUMMEIListMMEServedGUMMEIList0..1A list of the GUMMEIs served by the MME. Shall be present if known at the NF where the POI is located.C
iABSupportedBOOLEAN0..1Indicates whether the MME supports IAB Nodes. Shall be present if known at the NF where the POI is located.C
Up
6.3.2.2A.13  Type: MMEServedGUMMEIList  p. 130
Table 6.3.2.2A.13-1 contains the details for the MMEServedGUMMEIList type. This information is derived from the Served GUMMEI List IE of the S1 SETUP RESPONSE. See clause 9.1.8.5 of TS 36.413.
Field name Type Cardi­nality Description M/C/O
mMEServedGUMMEIListMMEServedGUMMEI1..MAXA list of the GUMMEIs supported by the MME.M
Up
6.3.2.2A.14  Type: MMEServedGUMMEI  p. 131
Table 6.3.2.2A.14-1 contains the details for the MMEServedGUMMEI type. This information is derived from the Served GUMMEI List IE of the S1 SETUP RESPONSE. See clause 9.1.8.5 of TS 36.413.
Field name Type Cardi­nality Description M/C/O
servedPLMNsPLMNSupportList1A list of PLMNs served by the MME for the GUMMEI.M
Up
6.3.2.2A.15  Type: EPSNASTransportInitialInformation  p. 131
Table 6.3.2.2A.15-1 contains the details for the EPSNASTransportInitialInformation type. This information is derived from information present in the INITIAL UE MESSAGE defined in clause 9.1.7.1 of TS 36.413.
Field name Type Cardi­nality Description M/C/O
rANUES1APIDRANUES1APID1Identity that the MME receives from the eNB uniquely identifying the target UE with the eNB. See clause 9.2.3.4 of TS 36.413.M
relayNodeIndicatorBOOLEAN0..1Indicates whether the UE is acting as a Relay Node. See clause 9.2.1.79 of TS 36.413. Shall be present if the Relay Node Indicator IE is present in the INITIAL UE MESSAGE.C
bBFTunnelInformationBBFTunnelInformation0..1Indicates HeNB's Local IP Address and, when appropriate UPD Port Numebrs, assigned by the broadband access provider. Derived from the Tunnel Information for BBF IE defined in clause 9.1.7.1 of TS 36.413. Shall be present if present in the message that triggered the event or known at the NF where the POI is located.C
eDTSessionBOOLEAN0..1Indicates that the session is EDT capable. Shall be present if present in the message that triggered the event or known at the NF where the POI is located.C
iABNodeIndicationBOOLEAN0..1Indicates that the UE is capable of acting as an IAB Node. Shall be present if present in the message that triggered the event or known at the NF where the POI is located.C
lTENTNTAIInformationLTENTNTAIInformation0..1Contains information on the PLMN, broadcast TAC and TAC information derived from the UE location in the case of NTN access. Shall be present if the LTE NTN TAI Information (see clause 9.2.3.56 of TS 36.413) is present in the message that triggered the event or known at the NF where the POI is located.C
Up
6.3.2.2A.16  Type: BBFTunnelInformation  p. 131
Table 6.3.2.2A.16-1 contains the details for the BBFTunnelInformation type. This information is derived from information present in the Tunnel Information IE defined in clause 9.2.2.3 of TS 36.413.
Field name Type Cardi­nality Description M/C/O
hENBTransportLayerAddressIPAddr1Indicates the transport layer address of the HeNB.M
uDPPortNumberPortNumber0..1UDP Port Numbers if NAT/NAPT is deployed in the BBF access network. Shall be present if present in the Tunnel Information IE used to populate this record.C
Up
6.3.2.2A.17  Type: LTENTNTAIInformation  p. 132
Table 6.3.2.2A.17-1 contains the details for the LTENTNTAIInformation type. This information is derived from information present in the LTE NTN TAI Information IE defined in see clause 9.2.3.56 of TS 36.413.
Field name Type Cardi­nality Description M/C/O
pLMNPLMN1Indicates the serving PLMN for the UE.M
tACListInLTENTNTACList1Includes all TACs broadcast in the cell for the UE's serving PLMN.M
uETACTAC0..1Contains the TAC information derived from the TAC serving the UE's actual location. Shall be present if known.C
Up
6.3.2.2A.18  Type: EPSRANUEContext  p. 132
Table 6.3.2.2A.18-1 contains the details for the EPSRANUEContext type. This information is derived from information present in the INITIAL UE CONTEXT SETUP REQUEST IE defined in clause 9.1.4.1 of TS 36.413.
Field name Type Cardi­nality Description M/C/O
mMEUES1APIDMMEUES1APID0..1Identity that the MME uses to uniquely identify the target UE over the S1 Interface. See clause 9.2.3.3 of TS 36.413. This is correlated to the IMSI known in the UE context at the MME. Include when sent during the procedure being reported or when known at the NF.C
rANUES1APIDRANUES1APID0..1Identity that the MME receives from the eNB uniquely identifying the target UE with the eNB. See clause 9.2.3.4 of TS 36.413. Include when sent during the procedure being reported or when known at the NF.C
eRABSetupRequestERABContextList0..1Contains a list of any E-RABs requested for setup. See clause 9.1.4.1 of TS 36.413. Include when sent during the procedure being reported or when known at the NF.C
handoverRestrictionListEPSHandoverRestrictionList0..1Provides information on the PLMNs and RAT Type combinations the UE is able to use for reselection. See clause 9.2.1.22 of TS 36.413. Include when sent during the procedure being reported or when known at the NF.C
uERadioCapabilityEPSUERadioCapability0..1Indicates the radio capabilities of the UE. See clause 9.2.1.27 of TS 36.413. Include when sent during the procedure being reported or when known at the NF.C
rATFrequencySelectionPriorityRATFrequencySelectionPriority0..1Indicates the RAT/Frequency priority to define camp priorities in Idle mode and inter-RAT/inter-freqency priorities for handover in Active mode. Encoded per clause 9.2.1.39 of TS 36.413.C
cSFallbackIndicatorEPSCSFallbackIndicator0..1Indicates that a fallback to the CS domain is required and the type of fallback requested. See clause 9.2.3.21 of TS 36.413. C
proSeAuthorizedEPSProSeAuthorization0..1Provides information on the authorization status of the UE to use proximity services. Include when sent during the procedure being reported or when known at the NF. Derived from the value of the ProSe Authorized IE defined in clause 9.2.1.99 of TS 36.413.C
lTEV2XServicesAuthorizedLTEV2XServiceAuthorization0..1Provides information on the authorization status of the UE to use V2X services over LTE. Include when sent during the procedure being reported or when known at the NF. Derived from the value of the V2X Services Authorized IE defined in clause 9.2.1.120 of TS 36.413.C
aerialUESubscriptionAerialUESubscriptionIndicator0..1Provides information on the authorization status of the UE to use aerial UE service. Include when sent during the procedure being reported or when known at the NF. Derived from the value of the aerial UE subscription information IE defined in clause 9.2.1.136 of TS 36.413.C
subscriptionBasedUEDifferentiationIndicationEPSSubscriptionBasedUEDifferentiationIndication0..1Provides information on the periodic communication subscription for a UE. Include when sent during the procedure being reported or when known at the NF. Derived from the value of the Subscription Based UE Differentiation Information IE defined in clause 9.2.1.140 of TS 36.413.C
iABAuthorizedIndicatorIABAuthorizedIndicator0..1Provides information on the authorization of a UE to act as an IAB node. Include when during the procedure being reported or when known at the NF. Derived from the value of the IAB Authorized IE defined in clause 9.2.1.146 of TS 36.413.C
nRV2XServicesAuthorizationNRV2XServicesAuthorization0..1Provides information on the authorization status of the UE to use V2X services over NR. Include when sent during the procedure being reported or when known at the NF. Derived from the value of the V2X Services Authorized IE defined in clause 9.2.1.148 of TS 36.413.C
Up
6.3.2.2A.19  Enumeration: EPSCSFallbackIndicator  p. 133
The EPSCSFallbackIndicator indicates that a fallback to the CS domain is required and the type of fallback requested. Derived from the enumerations in clause 9.2.3.21 of TS 36.413.
Table 6.3.2.2A.19-1 contains the details of the EPSCSFallbackIndicator type.
Enumeration value Description
cSFallbackRequired (1)Fallback to the CS domain is required.
cSFallbackHighPriority (2)A high priority fallback to the CS domain is required.
Up

6.3.2.3  Generation of IRI over LI_HI2  p. 133

6.3.2.3.1  General  p. 133
When Option A or Option B specified in clause 6.3.1 are used and an xIRI is received over LI_X2 from the IRI-POI in the MME, the MDF2 shall generate the corresponding IRI message and deliver it over LI_HI2 without undue delay. The IRI message shall contain a copy of the relevant record received in the xIRI over LI_X2.
When Option C specified in clause 6.3.1 is used the MDF2 shall generate IRI messages based on the proprietary information received from the MME and provide it over LI_HI2 without undue delay.
The IRI record may be enriched with any additional information available at the MDF (e.g. additional location information).
The IRI messages shall be delivered over LI_HI2 according to ETSI TS 102 232-7 [10] clause 10. When Option A specified in clause 6.3.1 is used, LI_HI2 shall be realised as described in clause 6.3.2.3.2.
When Option B or Option C specified in clause 6.3.1 is used, LI_HI2 shall be realised as described in clause 6.3.2.3.3.
Up
6.3.2.3.2  Option A  p. 133
The IRI message the MDF2 generates shall contain a copy of the relevant record received in the xIRI over LI_X2 and provide it over LI_HI2 without undue delay.
The timestamp field of the PSHeader structure shall be set to the time at which the MME event was observed (i.e. the timestamp field of the X2 PDU).
The IRI type parameter (see ETSI TS 102 232-1 [9] clause 5.2.10) shall be included and coded according to Table 6.3.2-8.
IRI message IRI type
MMEAttachREPORT
MMEDetachREPORT
MMELocationUpdateREPORT
MMEStartOfInterceptionWithEPSAttachedUEREPORT
MMEUnsuccessfulProcedureREPORT
MMEIdentifierAssociationREPORT
MMEPositioningInfoTransferREPORT
EPSRANHandoverCommandREPORT
EPSRANHandoverRequestREPORT
MMERANTraceReportREPORT
MMEUEServiceAcceptREPORT
These IRI messages shall omit the CIN (see ETSI TS 102 232-1 [9] clause 5.2.4).
The threeGPP33128DefinedIRI field in ETSI TS 102 232-7 [10] clause 15 shall be populated with the BER-encoded IRIPayload.
When an additional warrant is activated on a target UE and the LIPF uses the same XID for the additional warrant, the MDF2 shall be able to generate and deliver the IRI message containing the MMEStartOfInterceptionWithEPSAttachedUE record to the LEMF associated with the additional warrant without receiving a corresponding xIRI. The payload of the MMEStartOfInterceptionWithEPSAttachedUE record is specified in Table 6.3.2-6.
For records related to SMS over NAS in EPS, the process detailed in clause 6.3.2.3.3 shall be used.
Up
6.3.2.3.3  Option B and Option C  p. 134
For all messages except MMEIdentifierAssociation, the IRI messages shall include an IRI payload encoded according to TS 33.108 Annex B.9.
The MDF2 shall encode the correct value of LIID in the IRI message, replacing the value "LIIDNotPresent" given in the xIRI (see clause 6.3.2.2).
For MMEIdentifierAssociation messages, the IRI message shall be encoded as an IRIEvent structure according to Annex B and used to populate the threeGPP33128DefinedIRI field in ETSI TS 102 232-7 [10] clause 15.
Up

Up   Top   ToC