Tech-invite3GPPspaceIETFspace
21222324252627282931323334353637384‑5x

Content for  TS 33.128  Word version:  18.7.0

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

 

6.3  4Gp. 120

6.3.1  Generalp. 120

The present document allows three options for EPC LI stage 3 interfaces for 4G / LTE:
For implementations that include EPS/5GS interworking, Option A shall be used.
In all cases, the present document specifies the stage 3 for the LI_HI1, LI_HI2 and LI_HI3 interfaces.
Up

6.3.2  LI at MMEp. 120

6.3.2.1  Provisioning over LI_X1p. 120

The IRI-POI present in the MME is provisioned over LI_X1 by the LIPF using the X1 protocol as described in clause 5.2.2.
The POI in the MME shall support the following target identifier formats:
Table 6.3.2-0A shows the minimum details of the LI_X1 ActivateTask message used for provisioning the IRI-POI in the MME.
ETSI TS 103 221-1 [7] field name Description M/C/O
XIDXID assigned by LIPF.M
TargetIdentifiersOne of the target identifiers listed in the paragraph above.M
DeliveryType Set to "X2Only". M
ListOfDIDs Delivery endpoints for LI_X2 for the IRI-POI in the MME. These delivery endpoints are configured using the CreateDestination message as described in ETSI TS 103 221-1 [7] clause 6.3.1 prior to the task activation.M
TaskDetailsExtensions/ IdentifierAssociationExtensionsThis field shall be included if the IRI-POI is required to generate MMEIdentifierAssociation records (see clause 6.3.2.2.1). If the field is absent, MMEIdentifierAssociation records shall not be generated.C
ListOfServiceTypes Shall be included when the task should only intercept specific CSP service types as described in clause 5.2.4. This parameter is defined in ETSI TS 103 221-1 [7] clause 6.2.1.2, Table 4.C
Field Name Description M/C/O
EventsGeneratedOne of the following values:
  • IdentifierAssociation
  • All
See clause 6.3.2.2.1 for the interpretation of this field.
M
Up

6.3.2.2  Generation of xIRI over LI_X2p. 121

6.3.2.2.1  Generalp. 121
If the MME receives one or more cell IDs in an S1 message (as specified in TS 36.413), the POI associated with the MME shall report all of them.
The IRI-POI in the MME shall only generate xIRI containing the MMEIdentifierAssociation record in the following scenarios:
  • IdentifierAssociation: MMEIdentifierAssociation and Tracking Area/EPS Location Update (see clause 12.2.1.2 of TS 33.107) records shall be generated. No other record types shall be generated for that target.
  • All: All MME record types shall be generated.
When Option A specified in clause 6.3.1 is used:
  • The IRI-POI present in the MME shall send the xIRIs over LI_X2 for each of the events listed in clause 6.3.2.3 of TS 33.127, the details of which are described in the following clauses.
  • In addition to the xIRI events listed in clause 6.3.2.3 of TS 33.127, the MME shall support xIRI generation in case of SMS over NAS as specified in clause 18.2.4 of TS 33.107. For records related to SMS over NAS in EPS:
    • The IRI-POI present in the MME 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, 15.2 and B.9 of TS 33.108.
    • As the LIID may be not available at the MME but is mandatory in EpsHI2Operations.EpsIRIContent according to TS 33.108 Annex B.9, its value in the lawfulInterceptionIdentifier field of the encoded PDU shall be set to the fixed string "LIIDNotPresent".
When Option B specified in clause 6.3.1 is used:
  • The IRI-POI present in the MME shall send the xIRIs over LI_X2 for each of the events listed in clause 12.2.1.1 of TS 33.107, the details of which are specified in clause 12.2.3 of the same TS, and in case of SMS over NAS as specified in clause 18.2.4 of TS 33.107.
  • For all records except MMEIdentifierAssociation (see clause 6.3.2.2.2), the IRI-POI present in the MME 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, 15.2 and B.9 of TS 33.108.
  • As the LIID may be not available at the MME but is mandatory in EpsHI2Operations.EpsIRIContent according to TS 33.108 Annex B.9, its value in the lawfulInterceptionIdentifier field of the encoded PDU shall be set to the fixed string "LIIDNotPresent".
  • In addition to the xIRI events listed in TS 33.107, the MME shall support xIRI containing the MMEIdentiferAssociation record in clause 6.3.2.2.2.
Up
6.3.2.2.2  MME identifier associationp. 122
The IRI-POI present in the MME shall generate an xIRI containing an MMEIdentifierAssociation record when the IRI-POI present in the MME detects a new identifier association for a UE matching one of the target identifiers provided via LI_X1. Generation of this record is subject to this record type being enabled for a specific target (see clause 6.3.2.2.1).
Field name Type Cardi­nality Description M/C/O
iMSIIMSI1IMSI associated with the procedure. (see NOTE 1).M
iMEIIMEI0..1IMEI used in the procedure, if available (see NOTE 1).C
mSISDNMSISDN0..1MSISDN used in the procedure, if available (see NOTE 1).C
gUTIGUTI1LTE GUTI used in the procedure.M
locationLocation1Location information available when identifier association occurs.
Shall include all location information for the target UE available at the MME encoded as one of the following:
  • as a Location.fourGLocationInfo.ePSLocationInformation parameter.
  • as a Location.fourGLocationInfo.ePSUserLocationInformation parameter.
When Dual Connectivity is activated, the additionalCellIDs parameter (Location.fourGLocationInfo.ePSLocationInformation.mMELocationInformation.additionalCellIDs) shall also be populated, see clause 7.3.3.
If available, other parameters reportable via Location shall be included
M
tAIListTAIList0..1List of tracking areas associated with the registration area within which the UE is current registered. (see NOTE 2).C
NOTE 1:
IMSI shall always be provided, in addition to the warrant target identifier if different to IMSI. Other identifiers shall be provided if available.
NOTE 1:
List shall be included each time there is a change to the registration area.
The IRI-POI present in the MME generating an xIRI containing an MMEIdentifierAssociation 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).
When transmitting the xIRI, the IRI-POI present in the MME shall set the payload format to 2, and provide the payload as a BER-encoded TS33128Payloads.XIRIPayloads structure.
Up
6.3.2.2.3  Attachp. 122
The IRI-POI in the MME shall generate an xIRI containing an MMEAttach record when the IRI-POI present in the MME detects that a UE matching one of the target identifiers provided via LI_X1 has successfully attached to EPS. Accordingly, the IRI-POI in the MME generates the xIRI when the following event is detected:
  • MME sends an S1: ATTACH ACCEPT message to the target UE and the UE EPS Mobility Management (EMM) state within the MME is changed to EMM-REGISTERED.
Field name Type Cardi­nality Description M/C/O
attachTypeEPSAttachType1Specifies the type of EPS Attach, see clause 9.9.3.11 of TS 24.301. This is derived from the information received from the UE in the Attach Request message.M
attachResultEPSAttachResult1Specifies the result of the attach procedure, see clause 9.9.3.10 of TS 24.301.M
iMSIIMSI1IMSI associated with the registration.M
iMEIIMEI0..1IMEI associated with the registration, if available.C
mSISDNMSISDN0..1mSISDN associated with the registration, if available.C
gUTIGUTI0..1GUTI provided as outcome of initial attach or used in other cases, see clause 5.5.1.2.4 of TS 24.301.M
locationLocation0..1Location information determined by the network during the registration or known at the MME, if available.
Shall include all location information for the target UE available at the MME encoded as one of the following:
  • as a Location.fourGLocationInfo.ePSLocationInformation parameter.
  • as a Location.fourGLocationInfo.ePSUserLocationInformation parameter.
If available, other parameters reportable via Location shall be included.
C
ePSTAIListTAIList0..1List of tracking areas associated with the registration area within which the UE is currently registered, see clause 9.9.3.33 of TS 24.301. (see NOTE)C
sMSServiceStatusEPSSMSServiceStatus0..1Indicates the availability of SMS Services. Shall be provided if present in the ATTACH ACCEPT.C
oldGUTIGUTI0..1Old GUTI used in the registration, if available.C
eMM5GRegStatusEMM5GMMStatus0..1UE Status, if provided in the REGISTRATION REQUEST message, see clause 9.11.3.56 of TS 24.501.C
pagingRestrictionIndicatorPagingRestrictionIndicator0..1Indicates if paging is restricted or the type of paging allowed. Include if sent in the Attach Request message. Encoded per clause 9.9.3.66 of TS 24.301, omitting the first two octets.C
rATTypeRATType0..1RAT Type shall be present if known by the MME. RAT Type is determined by the MME during the attach procedure. See clause 4.3.5.3 of TS 23.401.C
rRCEstablishmentCauseEPSRRCEstablishmentCause0..1Indicates the reason for UE RRC Connection Establishment. This parameter shall be populated with information provided by the serving RAN during NAS establishment in the Initial UE Message. See clause 9.2.1.3a of TS 36.413.C
s1InformationS1Information0..1 Provides application layer related information for the serving Global RAN Node provided by the eNB node to the serving MME during S1 setup. This parameter shall be populated using information from the S1 SETUP REQUEST and S1 SETUP RESPONSE. See clauses 9.1.8.4 and 9.1.8.5 of TS 36.413.C
nASTransportInitialInformationEPSNASTransportInitialInformation0..1Provides information related to the NAS Transport setup for the target UE over the S1 interface. Shall be included when received by the MME per TS 36.413. This parameter is only conditional for backward compatibility. See clause 9.1.7.1 of TS 36.413.C
equivalentPLMNListPLMNList0..1 Provides a list of equivalent PLMNs in the Attach Accept message. See clauses 8.2.1.1 and 8.2.1.8 of TS 24.301.C
ePSUENetworkCapabilityEPSUENetworkCapability0..1Shall contain the target UE network capability information octets sent in the Attach Request message, omitting the first two octets. Defined in clause 9.9.3.34 of TS 24.301.C
initialRANUEContextSetupEPSRANUEContext0..1Provides information sent in the INITIAL CONTEXT SETUP message from the MME to the RAN for a target. See clause 9.1.4.1 of TS 36.413.C
mUSIMUERequestTypeMUSIMUERequestType0..1Indicates a MUSIM UE has requested release of NAS signalling or has rejected paging. Include if sent in the REGISTRATION REQUEST message. Encoded per UE Request Type omitting the first two octets. See clause 9.9.3.65 of TS 24.301.C
ePSNetworkPolicyEPSNetworkPolicy0..1Indicates network policy information to the UE during attach or tracking area update procedures. Include if present in the ATTACH ACCEPT message. Encoded per Network policy type. See clause 9.9.3.52 of TS 24.301.C
NOTE:
List shall be included each time there is a change to the registration area.
Up
6.3.2.2.4  Detachp. 124
The IRI-POI in the MME shall generate an xIRI containing an MMEDetach record when the IRI-POI present in the MME detects that a UE matching one of the target identifiers provided via LI_X1 has deregistered from the EPS. Accordingly, the IRI-POI in the MME generates the xIRI when any of the following events is detected:
  • For network initiated de-registration, when the MME receives the S1: DETACH ACCEPT message from the target UE, when the MME receives an S3: DETACH NOTIFICATION about the target UE from the SGSN or when implicit deregistration timer expires; and in all cases the UE EMM state within the MME is changed to EMM-DEREGISTERED.
  • For UE initiated de-registration, when the MME sends the S1: DETACH ACCEPT message to the target UE or when the MME receives the S1: DETACH REQUEST message from the target UE with deregistration type value of "switch off"; and in both cases the UE EMM state within the MME is changed to EMM-DEREGISTERED.
Field name Type Cardi­nality Description M/C/O
deregistrationDirectionMMEDirection1Indicates whether the deregistration was initiated by the network or by the UE.M
detachTypeEPSDetachType1 Indicates the type of detach as determined by the direction of the detach request and the value of the DetachType information element, see Table 6.3.2-4.M
iMSI1IMSI IMSI associated with the detach.M
iMEI0..1IMEIIMEI associated with the detach, if available.C
mSISDN0..1mSISDNmSISDN associated with the detach, if available.C
gUTI0..1GUTIGUTI associated with the detach, if available.C
causeEMMCause0..1Indicates the EMM cause value for network-initiated detach, see clause 9.9.3.9 of TS 24.301.C
locationLocation0..1Location information determined by the network during the deregistration or known at the MME, if available.
Shall include all location information for the target UE available at the MME encoded as one of the following:
  • as a Location.fourGLocationInfo.ePSLocationInformation parameter.
  • as a Location.fourGLocationInfo.ePSUserLocationInformation parameter.
When Dual Connectivity is activated, the additionalCellIDs parameter (Location.fourGLocationInfo.ePSLocationInformation.mMELocationInformation.additionalCellIDs) shall also be populated, see clause 7.3.3.
If available, other parameters reportable via Location shall be included.
C
switchOffIndicatorSwitchOffIndicator0..1 If Bit 4 of the Detach type information element sent in the Detach Request is set to 0, this parameter shall be set to "normalDetach". If Bit 4 of the Detach type information element sent in the Detach Request is set to 1, this parameter shall be set to "switchOff". See clause 9.9.3.7 of TS 24.301. This parameter is conditional only for backwards compatibility. C
Type of detach value Direction detachType value
001UE→networkePSDetach
010UE→networkiMSIDetach
011UE→networkcombinedEPSIMSIDetach
110UE→networkreserved
111UE→networkreserved
Any OtherUE→networkcombinedEPSIMSIDetach
001network→UEreAttachRequired
010network→UEreAttachNotRequired
011network→UEiMSIDetach
110network→UEreserved
111network→UEreserved
Any Othernetwork→UEreAttachNotRequired
The IRI-POI in the MME shall populate the ePSDetachType field with the values listed in Table 6.3.2-4 based on the Detach Type sent in the Detach Request message (see clause 9.9.3.7 of TS 24.301) and the direction of the Detach Request associated to the event that triggered the generation of the xIRI.
If the Detach Request message associated to the event that triggered the generation of the xIRI has the EMM Cause field populated, the IRI-POI in the MME shall set the value of the cause field of the MMEDetach record to the integer value of the EMM Cause, see clause 9.9.3.9 of TS 24.301.
Up
6.3.2.2.5  Tracking Area/EPS Location updatep. 125
When the reporting of location information is authorised, the IRI-POI in the MME shall generate an xIRI containing an MMELocationUpdate record each time the IRI-POI present in an MME detects that the target UE location is updated due to target UE mobility or as a part of an MME service procedure. The generation of such separate xIRI is not required if the updated UE location information is obtained as a part of a procedure producing some other xIRIs (e.g. mobility registration). In that case the location information is included into the respective xIRI.
In addition to the Tracking Area Update described in clause 5.3.3 of TS 23.401, the UE mobility events resulting in generation of an MMELocationUpdate xIRI include the S1 Path Switch Request (intra E-UTRAN handover X2 based handover procedure described in clause 5.5.1.1 of TS 23.401) and the S1 Handover Notify (Intra E-UTRAN S1 based handover procedure described in clause 5.5.1.2 of TS 23.401).
The MMELocationUpdate xIRI is also generated when the MME receives an E-UTRAN S1AP ERAB Modification Indication message as a result of Dual Connectivity activation/release for the target UE, as described in clause 10 of TS 37.340.
Based on regulatory requirements and operator policy, the location information obtained by the MME from E-UTRAN or the E-SMLC in the course of some service operations may result in the generation of the MMELocationUpdate xIRI record. Additionally, the IRI-POI in the MME shall capture the location information in the scenarios described in clause 4.4.2 of TS 23.271. Also, in the case of Mobile Originated LCS service invoked by the target, the location information may be derived from the Location Service Response sent to the target UE via the MME (see clause 9.2.6 of TS 23.271).
Optionally, based on regulatory and operator policy, other MME messages that do not generate separate xIRI but carry location information such as emergency services or LCS may trigger the generation of an MMELocationUpdate xIRI record.
The MMELocationUpdate record is also used by LARF to deliver location acquisition responses to MDF2, as described in clause 7.3.5.6. For the responses to location acquisition requests initiated by LARF, as described in TS 33.127 the MMELocationUpdate xIRIs shall not be generated.
Field Name Description M/C/O
iMSIiMSI associated with the location update.M
iMEIiMEI associated with the location update, if available.C
mSISDNmSISDN associated with the location update, if available as part of the subscription profile.C
gUTIGUTI assigned during the location update, if available, see TS 24.301.C
locationUpdated location information determined by the network. Depending on the service or message type from which the location information is extracted, it may be encoded in several forms (Annex A).M
oldGUTIGUTI used to initiate the location update, if available, see TS 24.301.C
sMSServiceStatusIndicates the availability of SMS Services. Shall be provided if present in the TRACKING AREA UPDATE ACCEPT.C
Up
6.3.2.2.6  Start of interception with EPS attached UEp. 126
The IRI-POI in the MME shall generate an xIRI containing an MMEStartOfInterceptionWithEPSAttachedUE record when the IRI-POI present in the MME detects that interception is activated on a UE that has already attached to the EPS. A UE is considered already attached to the EPS when the EMM state for that UE is EMM-REGISTERED. Therefore, the IRI-POI present in the MME shall generate the xIRI MMEStartOfInterceptionWithEPSAttachedUE record when it detects that a new interception for a UE is activated (i.e. provisioned by the LIPF) and the EPS mobility management state within the MME for that UE is EMM-REGISTERED.
Field name Type Cardi­nality Description M/C/O
attachTypeEPSAttachType1Specifies the type of EPS Attach, see clause 9.9.3.11 of TS 24.301. This is derived from the information stored in the UE Context at the MME, see clause 5.7.2 of TS 23.401.M
attachResultEPSAttachResult1Specifies the result of the attach procedure, see clause 9.9.3.10 of TS 24.301. This is derived from the information stored in the UE Context at the MME, see clause 5.7.2 of TS 23.401.M
iMSIIMSI1IMSI associated with the target UE Context at the MME, see clause 5.7.2 of TS 23.401.M
iMEIIMEI0..1IMEI associated with the target UE Context at the MME, if available, see clause 5.7.2 of TS 23.401.C
mSISDNMSISDN0..1mSISDN associated with the target UE Context at the MME, if available.C
gUTIGUTI0..1Current GUTI associated with the target UE context at the MME, if available, see clause 5.7.2 of TS 23.401.C
locationLocation0..1Location information stored in the UE Context at the MME, if available, see clause 5.7.2 of TS 23.401.
Shall include all location information for the target UE available at the MME encoded as one of the following:
  • as a Location.fourGLocationInfo.ePSLocationInformation parameter.
  • as a Location.fourGLocationInfo.ePSUserLocationInformation parameter.
When Dual Connectivity is activated, the additionalCellIDs parameter (Location.fourGLocationInfo.ePSLocationInformation.mMELocationInformation.additionalCellIDs) shall also be populated, see clause 7.3.3. If available, other parameters reportable via Location shall be included.
C
ePSTAIListTAIList0..1List of tracking areas associated with the registration area within which the UE is currently registered, see clause 9.9.3.33 of TS 24.301 and clause 5.7.2 of TS 23.401.C
sMSServiceStatusEPSSMSServiceStatus0..1Indicates the availability of SMS Services. Shall be provided if present in the UE Context at the MME, see clause 5.7.2 of TS 23.401.C
eMM5GRegStatusEMM5GMMStatus0..1UE Status, if present in the UE Context at the MME, see clause 9.11.3.56 of TS 24.501.C
pagingRestrictionIndicatorPagingRestrictionIndicator0..1Indicates if paging is restricted or the type of paging allowed. Shall be included if known at the NF context. Encoded per clause 9.9.3.66 of TS 24.301, omitting the first two octets.C
rATTypeRATType0..1RAT Type shall be present if known by the MME. RAT Type is determined by the MME during the attach procedure. Shall be included if known at the NF context. See clause 4.3.5.3 of TS 23.401.C
rRCEstablishmentCauseEPSRRCEstablishmentCause0..1Indicates the reason for UE RRC Connection Establishment. Shall be included if known at the NF context. See clause 9.2.1.3a of TS 36.413.C
s1InformationS1Information0..1 Provides application layer related information for the serving Global RAN Node provided by the eNB node to the serving MME during S1 setup. Shall be included if known at the NF context. See clauses 9.1.8.4 and 9.1.8.5 of TS 36.413.C
nASTransportInitialInformationEPSNASTransportInitialInformation0..1Provides information related to the NAS Transport setup for the target UE over the S1 interface. Shall be included when received by the MME per TS 36.413. This parameter is only conditional for backward compatibility. See clause 9.1.7.1 of TS 36.413.C
equivalentPLMNListPLMNList 0..1 Provides a list of equivalent PLMNs. Shall be included if known at the NF. See clauses 8.2.1.1 and 8.2.1.8 of TS 24.301.C
ePSUENetworkCapabilityEPSUENetworkCapability0..1Shall contain the target UE network capability information Shall be included if known at the NF context. Encoded per clause 9.9.3.34 of TS 24.301 ommitting the first two octets.C
initialRANUEContextSetupEPSRANUEContext0..1Provides information about the RAN context for the UE as known at the MME. Shall be included if known at the NF context. See clause 9.1.4.1 of TS 36.413.C
ePSNetworkPolicyEPSNetworkPolicy0..1Indicates network policy information to the UE during attach or tracking area update procedures. Shall be included if known at the NF context. Encoded per Network policy type. See clause 9.9.3.52 of TS 24.301.C
The IRI-POI present in the MME generating an xIRI containing an MMEStartOfInterceptionWithEPSAttachedUE record shall set the Payload Direction field in the PDU header to not applicable (see ETSI TS 103 221-2 [8] clause 5.2.6).
Up
6.3.2.2.7  MME unsuccessful procedurep. 128
The IRI-POI in the MME shall generate an xIRI containing an MMEUnsuccessfulProcedure record when the IRI-POI present in the MME detects an unsuccessful procedure for a UE matching one of the target identifiers provided via LI_X1.
Accordingly, the IRI-POI in the MME generates the xIRI when any of the following events is detected:
  • MME sends a reject to any EMM request message to the target UE and the UE EPS Mobility Management (EMM) within the MME is changed to EMM-DEREGISTERED.
  • MME aborts a registration procedure before the UE EPS Mobility Management (EMM) state within the MME is changed to EMM-REGISTERED.
  • MME sends a reject to any ESM request message to the target UE.
Unsuccessful attach attempts shall be reported only if the target UE has been successfully authenticated.
Field name Type Cardi­nality Description M/C/O
failedprocedureTypeMMEFailedProcedureType1Specifies the procedure which failed at the MME.M
failureCauseMMEFailureCause1 Provides the value of the ESM or EMM cause, see clauses 9.9.3.9 and 9.9.4.4 of TS 24.301. M
iMSIIMSI0..1IMSI associated with the procedure, if available (see NOTE).C
iMEIIMEI0..1IMEI associated with the procedure, if available.C
mSISDNMSISDN0..1mSISDN associated with the procedure, if available.C
gUTIGUTI0..1GUTI provided used in the procedure, if available.C
locationLocation0..1Location information determined by the network during the procedure or known at the MME, if available.
Shall include all location information for the target UE available at the MME encoded as one of the following:
  • as a Location.fourGLocationInfo.ePSLocationInformation parameter.
  • as a Location.fourGLocationInfo.ePSUserLocationInformation parameter.
When Dual Connectivity is activated, the additionalCellIDs parameter (Location.fourGLocationInfo.ePSLocationInformation.mMELocationInformation.additionalCellIDs) shall also be populated, see clause 7.3.3.
If available, other parameters reportable via Location shall be included.
C
NOTE:
At least one identity shall be provided, the others shall be provided if available.
Up
6.3.2.2.8  Positioning info transferp. 128
The IRI-POI present in the MME shall generate an xIRI containing an MMEPositioningInfoTransfer when the IRI-POI present in the MME detects one of the following events:
  • a LPPa (see TS 36.455) message related to a target UE has been exchanged between the E-SMLC and the eNB via the MME.
  • a LPP (see TS 37.355) message related to a target UE has been exchanged between the E-SMLC and the target UE via the MME.
Accordingly, the IRI-POI in MME generates the xIRI when any of the following events is detected:
  • MME receives an SLs CONNECTION ORIENTED INFORMATION message (see TS 29.171) from E-SMLC to request the transfer of a LPPa request to the serving eNB for a target UE as part of a UE associated LPPa positioning activity. The LPPa request may be E-CID MEASUREMENT INITIATION REQUEST or OTDOA INFORMATION REQUEST.
  • MME sends an SLs CONNECTION ORIENTED INFORMATION message to the E-SMLC to forward the LPPa response or report received from the eNB for a target UE. The LPPa response or report may be E-CID MEASUREMENT INITIATION RESPONSE, E-CID MEASUREMENT REPORT or OTDOA INFORMATION RESPONSE.
  • MME receives an SLs CONNECTION ORIENTED INFORMATION message from E-SMLC to request the transfer of a LPP request to the target UE.
  • MME sends an SLs CONNECTION ORIENTED INFORMATION message to E-SMLC to forward a LPP message received from the target UE.
Field Name Description M/C/O
iMSIIMSI associated with the location update.M
iMEIIMEI associated with the location update, if available.C
mSISDNMSISDN associated with the location update, if available as part of the subscription profile.C
gUTIGUTI assigned during the location update, if available, see TS 24.301.C
lPPaMessageAny UE associated LPPa message exchanged between the LMF and eNB via MME.C
lPPMessageAny LPP message exchanged between the E-SMLC and the target UE via MME.C
mMELCSCorrelationIdMMELCSCorrelationId is made of Correlation Id, described in clause 7.4.28 of TS 29.171, related to a location session, found in the SLs CONNECTION ORIENTED INFORMATION sent by E-SMLC to MME and corresponding SLs CONNECTION ORIENTED INFORMATION sent by MME to E-SMLC. All the MMEPositioningInfoTransfer records related to the same location session have the same CorrelationId. M
Up
6.3.2.2.9  Handoversp. 129
6.3.2.2.9.1  Generalp. 129
The present clause provides the LI requirements for S1 interface-based handovers which occur for a target UE. Such handovers may be intra EPS (inter-eNB), 5GS to EPS (inter-system), EPS to 5GS (inter-system), EPS to UTRA (inter-system) or EPS to GERA (inter-system).
The following xIRI records are used to report handover related events between the MME and RAN nodes for the target UE when the delivery of location information is not restricted by service scoping:
  • EPSRANHandoverCommand.
  • EPSRANHandoverRequest.
The above xIRIs are used to report handover events and information that are not carried in the MMELocationUpdate (clause 6.3.2.2.5) record and shall include the information transferred between the MME and RAN nodes, as a part of handover preparation, resource allocation, and handover notification.
Up
6.3.2.2.9.2  Handover commandp. 129
The IRI-POI in the MME shall generate an xIRI containing an EPSRANHandoverCommand record when the IRI-POI present in the MME detects that the MME has sent a HANDOVER COMMAND message to the source RAN node (old RAN node) in response to a HANDOVER REQUIRED message for the target UE and location information is not restricted by service scoping.
Field name Type Cardi­nality Description M/C/O
userIdentifiersUserIdentifiers1List of identifiers, including the target identifier, associated with the target UE registration stored in the MME context. See clause 5.7.2 of TS 23.401.M
mMEUES1APIDMMEUES1APID1Identity 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.M
eNBUES1APIDRANUES1APID1Identity 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
handoverTypeEPSHandoverType1Identifies the type of handover indicated by the source RAN node to the MME. See clause 9.2.1.3 of TS 36.413.M
eRABsToBeForwardedERABContextList0..1Contains a list of any E-RABs that are subject to forwarding. Shall be present if there are any E-RABs to be forwarded listed in the handover command. See clause 9.1.5.2 of TS 36.413.C
eRABsToReleaseERABReleaseList0..1Contains a list of any E-RABs that are to be released. Shall be present if there are any E-RABs to be released listed in the handover command. See clause 9.1.5.2 of TS 36.413.C
targetToSourceContainersSEQUENCE OF RANTargetToSourceContainer1..MAXProvides radio related information about the gaining RAN node. See clause 9.2.1.57 of TS 36.413.M
Up
6.3.2.2.9.3  Handover requestp. 130
The IRI-POI in the MME shall generate an xIRI containing an EPSRANHandoverRequest record when the IRI-POI in the MME detects that the MME received a HANDOVER REQUEST ACKNOWLEDGE message from the gaining RAN node (new RAN node) for the target UE and location information is not restricted by service scoping.
Field name Type Cardi­nality Description M/C/O
userIdentifiersUserIdentifiers1List of identifiers, including the target identifier, associated with the target UE registration stored in the MME context. See clause 5.7.2 of TS 23.401.M
handoverTypeEPSHandoverType1Identifies the type of handover indicated by the source RAN node to the MME. See clause 9.3.1.22 of TS 36.413.M
handoverCauseEPSRANCause1Indicates the cause of handover as seen in the handover request message from MME to gaining RAN node. See clause 9.2.1.3 of TS 36.413.M
sourceToTargetContainerRANSourceToTargetContainer1Provides radio related information via the MME in the handover request from source to gaining RAN node. See clause 9.2.1.56 of TS 36.413.M
cSGInfoEPSCSGInfo0..1Includes information about the currend CSG ID and membership information present in a handover request. Shall be present if the CSG ID or CSG Membership infor parameters were sent in the handover request. See clause 9.1.5.4 of TS 36.413.C
targetToSourceContainerRANTargetToSourceContainer1Provides radio related information via the MME in the handover request acknowledge from gaining RAN node to the source. See clause 9.2.1.57 of TS 36.413.M
admittedCSGIDCSGID0..1Derived from the CSG Id IE in the handover request acknowledge. See clause 9.1.5.5 of TS 36.413.C
ePSRANUEContextEPSRANUEContext1Includes RAN related information for the UE.M
Up
6.3.2.2.10  Tracep. 131
6.3.2.2.10.1  Generalp. 131
Trace procedures, as defined in TS 32.423, allow for the MME to request trace sessions, including Minimization of Drive Test (MDT) data gathering for a target using UE-associated signalling.
The present clause provides the LI requirements for reporting trace sessions from the IRI-POI in the MME for a target UE.
The following xIRI records are used to report trace related events between the MME and RAN nodes for the target UE when the delivery of location information is not restricted by service scoping:
  • MMERANTraceReport
Up
6.3.2.2.10.2  MME RAN trace reportp. 131
The IRI-POI in the MME shall generate an xIRI containing an MMERANTraceReport record when the IRI-POI present in the MME has detected any of the following events:
  • MME sent a TRACE START message to a RAN node in response to a Trace Session Activation message for the target.
  • MME received a CELL TRAFFIC TRACE message from the RAN for the target.
  • MME sent MDT or trace data to the trace collection entity for the target.
  • MME sent a deactivate trace message to the RAN for the target.
Field name Type Cardi­nality Description M/C/O
userIdentifiersUserIdentifiers1List of identifiers, including the target identifier, associated with the target UE registration stored in the MME context. See clause 5.7.2 of TS 23.401.M
mMEUES1APIDMMEUES1APID1Identity 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.M
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
traceRecordTypeTraceRecordType1Identifies the type of trace record being generated. This parameter is populated with either Trace Start, Cell Traffic Trace, Trace Data Delivery, or Trace Deactivation.M
traceDirectionTraceDirection1 Identifies which network element is signalling the trace information. This parameter is populated with a choice of either MME or RAN. See clauses 9.1.11 and 9.1.18 of TS 36.413.M
traceActivationInfoTraceActivation0..1Information related to a trace session activation provided from the MME to the NG-RAN node. Shall be populated if the traceRecordType is set to Trace Start. See clause 9.2.1.4 of TS 36.413.C
eUTRANCGIECGI1Identifies the eUTRAN Cell Global Identifier of the cell performing the UE trace. M
globalRANNodeIDGlobalRANNodeID1Uniquely identifies the RAN node to which the TRACE START message is sent. This is derived from the initial S1 Setup exchange between the RAN node and the MME.M
traceCollectionEntityInfoTraceCollectionEntityInfo0..1 Provides information related to the trace collection entity to which the MME sends the MDT or Trace data of the target. Shall be populated if the Trace Record Type is set to Trace Data Delivery. See clauses 9.1.18 and 9.2.2.1 of TS 36.413.C
mMETraceDataXMLType0..1 Includes the trace data (in raw XML format) sent from the MME to the trace collection entity. Shall be present when the MME is the trace collection NE. See clauses 4.18 and 5.2 of TS 32.423.C
locationLocation0..1Provides the current location as known in the UE context at the MME or supplemented by the MDF2.C
Up
6.3.2.2.11  Service Acceptp. 132
The IRI-POI in the MME shall generate an xIRI containing an MMEUEServiceAccept record when the IRI-POI in present in the MME detects that the MME considers a service request procedure initiated by the target to be completed successfully (see clause 5.6.1.4 of TS 24.301).
Field name Type Cardi­nality Description M/C/O
userIdentifiersUserIdentifiers1List of identifiers, including the target identifier, associated with the target UE registration stored in the MME context. See clause 5.7.2 of TS 23.401.M
serviceTypeOCTET STRING (SIZE (1))0..1Indicates the purpose of the service request procedure. Encoded per clause 9.9.3.27 of TS 24.301.C
mTMSITMSI0..1TMSI value associated with the target within the MME context. Shall be included if known. Encoded per 24.501 [13] figure 9.11.3.4.5C
cSFBResponseOCTET STRING (SIZE(1))0..1Indicates whether the target UE accepted circuit switched fallback. Shall be present if the CSFB response IE was present in the request that triggered the procedure reported by the xIRI (see clause 9.9.3.5 of TS 24.301.C
uEEPSBearerContextStatusOCTET STRING (SIZE (2))0..1 Indicates the state of each EPS bearer context at the target UE. Shall be present if the EPS bearer context status IE was present in the request that triggered the procedure reported by the xIRI (see clauses 8.2.15 and 8.2.33 of TS 24.301). Encoded per clause 9.9.2.1 of TS 24.301 ommitting the first two octets.C
uERequestTypeMUSIMUERequestType0..1Indicates the type of request sent by the UE. Shall be present if the UE request type indication IE was present in the request that initiated the procedure being reported by the xIRI. Encoded per clause 9.9.3.65 of TS 24.301.C
pagingRestrictionPagingRestrictionIndicator0..1Indicates the current paging restriction status for the target as known at the MME. Shall be present if the Paging restriction IE was present in the request that initiated the procedure being reported by the xIRI. Encoded per clause 9.9.3.66 of TS 24.301 omitting the first two octets.C
controlPlaneServiceTypeOCTET STRING (SIZE (1))0..1Indicates the purpose of the control plane service request procedure.Shall be present if the request that initiated the procedure being reported by the xIRI was a Control Plane Service Request. Encoded per clause 9.9.3.47 of TS 24.301.C
Up

Up   Top   ToC