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 Network Layer Based Interception  6.1 Introduction  6.2 5G  6.2.1 General  6.2.2 LI at AMF  6.2.2.1 Provisioning over LI_X1  6.2.2.2 Generation of xIRI over LI_X2  6.2.2.2.1 General  6.2.2.2.1A Simple data types for AMF  6.2.2.2.2 Registration  6.2.2.2.3 Deregistration  6.2.2.2.4 Location update  6.2.2.2.5 Start of interception with registered UE  6.2.2.2.6 AMF unsuccessful procedure  6.2.2.2.7 AMF identifier association  6.2.2.2.8 Positioning info transfer  6.2.2.2.9 Handovers  6.2.2.2.9.1 General  6.2.2.2.9.2 Handover command  6.2.2.2.9.3 Handover request  6.2.2.2.10 UE Configuration Update  6.2.2.2.11 Trace  6.2.2.2.11.1 General  6.2.2.2.11.2 AMF RAN trace report  6.2.2.2.12 UE policy transfer  6.2.2.2.13 Service Accept 
...

 

6  Network Layer Based Interception  p. 48

6.1  Introduction  p. 48

This clause describes any remaining fields, behaviours or details necessary to implement the required LI interfaces for specific 3GPP-defined network deployments which are not described in clauses 4 and 5.

6.2  5G  p. 48

6.2.1  General  p. 48

This clause describes the LI interfaces specific to LI for 5G networks.

6.2.2  LI at AMF  p. 48

6.2.2.1  Provisioning over LI_X1  p. 48

The IRI-POI present in the AMF is provisioned over LI_X1 by the LIPF using the X1 protocol as described in clause 5.2.2.
The POI in the AMF shall support the following target identifier formats in the ETSI TS 103 221-1 [7] messages (or equivalent if ETSI TS 103 221-1 [7] is not used):
  • SUPIIMSI.
  • SUPINAI.
  • PEIIMEI.
  • PEIIMEISV.
  • GPSIMSISDN.
  • GPSINAI.
Table 6.2.2.1-1 shows the minimum details of the LI_X1 ActivateTask message used for provisioning the IRI-POI in the AMF.
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 AMF. 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 AMFIdentifierAssociation records (see clause 6.2.2.2.1). If the field is absent, AMFIdentifierAssociation records shall not be generated.C
ListOfServiceTypes Shall be included when the explicit identification of specific CSP service types to be intercepted by the task as described in clause 5.2.4 is required. 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.2.2.2.1 for the interpretation of this field. 		M
Up

6.2.2.2  Generation of xIRI over LI_X2  p. 49

6.2.2.2.1  General  p. 49
The IRI-POI present in the AMF shall send the xIRIs over LI_X2 for each of the events listed in clause 6.2.2.4 of TS 33.127, the details of which are described in the following clauses.
If the AMF receives one or more cell IDs in an N2 message (as specified in TS 38.413), the IRI-POI in the AMF shall report all of them.
The IRI-POI in the AMF shall only generate xIRI containing AMFIdentifierAssociation records when the IdentifierAssocationExtensions parameter has been received over LI_X1 (see clause 6.2.2.1). The IRI-POI in the AMF shall generate records according to the value of the EventsGenerated sub-parameter (see Table 6.2.2.1-2) as follows:
  • IdentifierAssociation: AMFIdentifierAssociation and AMFLocationUpdate records shall be generated. No other record types shall be generated for that target.
  • All: All AMF record types shall be generated.
Up
6.2.2.2.1A  Simple data types for AMF  p. 50
Type name Type Description
MUSIMUERequestTypeOCTET STRING (SIZE (1))The purpose of the MUSIMUERequestType type is to indicate a MUSIM UE has requested the network to perform specific requests due to activity on another USIM. Shall contain the UE request type information octet sent in the REGISTRAITON REQUEST message, omitting the first two octets. Encoded per clause 9.9.3.65 of TS 24.301.
RATFrequencySelectionPriorityINTEGER (1..256)This field is used to define local configuration for RRM strategies such as camp priorities in idle mode and control of inter-RAT/inter-frequency handover in Active mode. See clause 5.3.4.3.1 of TS 23.501. Encoded per clause 9.3.1.61 of TS 38.413.
FiveGMMCapabilityOCTET STRING (SIZE (1..13))The purpose of the FiveGMMCapability type is to provide information concerning aspects of the UE related to the 5GCN or interworking with the EPS. Encoded per clause 9.11.3.1 of TS 24.501 omitting the first two octets.
FiveGSUpdateTypeOCTET STRING (SIZE (1))The purpose of the FiveGSUpdateType is to allow the UE to provide additional information to the network when performing a registration procedure. Defined in clause 9.11.3.9A of TS 24.501, omitting the first two octets.
UnavailabilityPeriodDurationOCTET STRING (SIZE (1))The purpose of UnavailabilityPeriodDuration is to indicate the period duration the UE is unavailable, see clause 8.2.6.1 of TS 24.501. Encoded as GPRS Timer 3, see clause 10.5.7.4a of TS 24.008, omitting the first two octets.
Up
6.2.2.2.2  Registration  p. 50
The IRI-POI in the AMF shall generate an xIRI containing an AMFRegistration record when the IRI-POI present in the AMF detects that a UE matching one of the target identifiers provided via LI_X1 has successfully registered to the 5GS via 3GPP NG-RAN or non-3GPP access. Accordingly, the IRI-POI in the AMF generates the xIRI when the following event is detected:
  • AMF sends a N1: REGISTRATION ACCEPT message to the target UE and the UE 5G Mobility Management (5GMM) state for the access type (3GPP NG-RAN or non-3GPP access) within the AMF is changed to 5GMM-REGISTERED.
Field name Type Cardi­nality Description M/C/O
registrationTypeAMFRegistrationType1Specifies the type of registration, see clause 9.11.3.7 of TS 24.501. This is derived from the information received from the UE in the REGISTRATION REQUEST message.M
registrationResultAMFRegistrationResult1Specifies the result of registration, see clause 9.11.3.6 of TS 24.501.M
sliceSlice0..1Provide, if available, one or more of the following:
This is derived from the information sent to the UE in the REGISTRATION ACCEPT message.		C
sUPISUPI1SUPI associated with the registration (see clause 6.2.2.4).M
sUCISUCI0..1SUCI used in the registration, if available.C
pEIPEI0..1PEI provided by the UE during the registration, if available.C
gPSIGPSI0..1GPSI obtained in the registration, if available as part of the subscription profile.C
gUTIFiveGGUTI15G-GUTI provided as outcome of initial registration or used in other cases, see clause 5.5.1.2.2 of TS 24.501.M
locationLocation0..1Location information determined by the network during the registration, if available.
Shall be encoded using the Location.locationInfo.userLocation parameter and, when Dual Connectivity is activated, using the Location.locationInfo.additionalCellIDs parameter. If available, other parameters reportable via Location shall be included. 		C
non3GPPAccessEndpoint UEEndpointAddress0..1UE's local IP address used to reach the N3IWF, TNGF or TWIF, if available. IP addresses are given as 4 octets (for IPv4) or 16 octets (for IPv6) with the most significant octet first (network byte order).C
fiveGSTAIListTAIList0..1List of tracking areas associated with the registration area within which the UE is current registered, see clause 9.11.3.9 of TS 24.501 (see NOTE)C
sMSoverNASIndicator SMSOverNASIndicator0..1Indicates whether SMS over NAS is supported. Provide, if included in registrationResult, see clause 9.11.3.6 of TS 24.501.C
oldGUTIEPS5GGUTI0..1GUTI or 5G-GUTI, if provided in the REGISTRATION REQUEST message, see clause 5.5.1.2.2 of TS 24.501.C
eMM5GRegStatusEMM5GMMStatus0..1UE Status, if provided in the REGISTRATION REQUEST message, see clause 9.11.3.56 of TS 24.501.C
nonIMEISVPEINonIMEISVPEI0..1MACAddress or EUI-64 used as UE equipment identity if IMEI or IMEISV based PEI is not available. Provide if known, see clause 8.2.26.4 of TS 24.501.C
mACRestIndicator MACRestrictionIndicator0..1Indicates whether the non-IMEISV PEI MACAddress can be used as an equipment identifier. Required if non-IMEISVPEI is used, see clause 9.11.3.4 of TS 24.501.C
pagingRestrictionIndicator PagingRestrictionIndicator0..1Indicates if paging is restricted or the type of paging allowed. Shall be included if sent in the REGISTRATION REQUEST message. Encoded per clause 9.11.3.77 of TS 24.501, omitting the first two octets.C
rATTypeRATType0..1RAT Type shall be present if known by the AMF. RAT Type is determined by the AMF during registration. see clause 5.3.2.3 of TS 23.501C
rRCEstablishmentCause RRCEstablishmentCause0..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.3.1.111 of TS 38.413.C
nGInformation NGInformation0..1 Provides application layer related information for the serving Global RAN Node provided by the NG-RAN node to the serving AMF during NG setup. This parameter shall be populated using information from the NG SETUP REQUEST and NG SETUP RESPONSE. see clauses 9.2.6.1 and 9.2.6.2 of TS 38.413.C
nASTransportInitialInformation NASTransportInitialInformation0..1Provides information related to the NAS Transport setup for the target UE over the NG interface. Shall be included when received by the AMF per TS 38.413. This parameter is only conditional for backward compatibility. see clause 9.2.5.1 of TS 38.413.C
equivalentPLMNList PLMNList0..1Provides a list of equivalent PLMNs in the REGISTRATION ACCEPT message. See clause 8.2.7.3 of TS 24.501.C
fiveGMMCapabilityFiveGMMCapability0..1Shall contain the target 5GMM capability information octets sent in the REGISTRATION REQUEST message, omitting the first two octets. Defined in clause 9.11.3.1 of TS 24.501.C
initialRANUEContextSetup InitialRANUEContextSetup0..1Provides information sent in the INITIAL CONTEXT SETUP message from the AMF to the RAN for a target. See clause 9.2.2.1 of TS 38.413.C
mUSIMUERequestType MUSIMUERequestType0..1Indicates a MUSIM UE has requested release of NAS signalling or has rejected paging. Shall be included 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
sORTransparentContainer SORTransparentContainer0..1Provides the list of preferred PLMN/access technology combinations. Included if sent in the NAS N1 message REGISTRATION ACCEPT. Given as a SoR Transparent container encoded per clause 9.11.3.51 of TS 24.501 omitting the first three octets.C
unavailabilityPeriodDurationUnavailabilityPeriodDuration0..1Period duration the UE is unavailable. Include if sent in the REGISTRATION REQUEST message. See clause 8.2.6.1 of TS 24.501. Encoded as GPRS Timer 3, see clause 10.5.7.4a of TS 24.008, omitting the first two octets.C
fiveGSUpdateTypeFiveGSUpdateType0..1Shall contain the target 5GS Update Type information octets if sent in the REGISTRATION REQUEST message. Defined in clause 9.11.3.9A of TS 24.501, omitting the first two octets.C
uEAreaIndicationUEAreaIndication0..1Contains a country, area in a country or international area indication where UE is located, if available. If UE is outside of the area of any known country, i.e. international area, it contains the international area indication without a country. UEAreaIndication is derived from the data present in the UEAreaIndication information element defined in clause 6.1.6.2.42 of TS 29.572.C
establishmentCauseNon3GPPAccessEstablishmentCauseNon3GPPAccess0..1Provides the establishment cause for Non-3GPP access (N3AEC) sent to the AMF by the N3AF on behalf of the target. Encoded per clause 9.2.2 of TS 24.502, omitting the first octet. Shall be included for N3AEC.C
NOTE:
List shall be included each time there is a change to the registration area.
Field name Type Cardi­nality Description M/C/O
CountryUTF8String (SIZE (2))0..1Indicates the country or the area of country where the UE is located. Contains the two-letter ISO 3166 country code in capital ASCII letters, e.g., DE or US.
Shall be encoded as described in TS 29.572 Table 6.1.6.2.42-1.		C
internationalAreaIndicationBOOLEAN0..1Indicates international area.
Set to true if UE is located in international area and set to false (default) if UE is not located in international area.		C
NOTE:
Either country or internationalAreaIndication shall be present.
Up
6.2.2.2.3  Deregistration  p. 52
The IRI-POI in the AMF shall generate an xIRI containing an AMFDeregistration record when the IRI-POI present in the AMF detects that a UE matching one of the target identifiers provided via LI_X1 has deregistered from the 5GS over at least one access type. Accordingly, the IRI-POI in AMF generates the xIRI when any of the following events is detected:
  • For network initiated de-registration, when the AMF receives the N1: DEREGISTRATION ACCEPT message from the target UE or when implicit deregistration timer expires; and in both cases the UE 5GMN state for the access type (3GPP NG-RAN or non-3GPP access) within the AMF is changed to 5GMM-DEREGISTERED.
  • For UE initiated de-registration, when the AMF sends the N1: DEREGISTRATION ACCEPT message to the target UE or when the AMF receives the N1: DEREGISTRATION REQUEST message from the target UE with deregistration type value of "switch off"; and in both cases the UE 5GMN state for the access type (3GPP NG-RAN or non-3GPP access) within the AMF is changed to 5GMM-DEREGISTERED.
  • For network initiated AMF UE relocation, the AMFDeregistration xIRI shall not be sent unless the 5GMM COMMON PROCEDURE INITIATED (see clause 5.1.3.2.3.3 of TS 24.501) results in deregistration.
Field name Type Cardi­nality Description M/C/O
deregistrationDirectionAMFDirection1Indicates whether the deregistration was initiated by the network or by the UE.M
accessTypeAccessType1Indicates the access for which the deregistration is handled, see clause 9.11.3.20 of TS 24.501.M
sUPISUPI0..1SUPI associated with the deregistration (see clause 6.2.2.4), if available (see NOTE).C
sUCISUCI0..1SUCI used in the deregistration, if available (see NOTE).C
pEI0..1PEIPEI used in the deregistration, if available (see NOTE).C
gPSIGPSI0..1GPSI associated to the deregistration, if available as part of the subscription profile (see NOTE).C
gUTIFiveGGUTI0..15G-GUTI used in the deregistration, if available, see clause 5.5.2.2.1 of TS 24.501 (see NOTE).C
causeFiveGMMCause0..1Indicates the 5GMM cause value associated with the deregistration procedure, see clause 9.11.3.2 of TS 24.501. The integer value is mapped from the second octet shown in clause 9.11.3.2 of TS 24.501.C
locationLocation0..1 Shall be encoded using the Location.locationInfo.userLocation parameter. If available, other parameters reportable via Location shall be included.C
switchOffIndicatorSwitchOffIndicator0..1Indicates whether the deregistration type is normal or switch off, if available, see clause 9.11.3.20 of TS 24.501.C
reRegRequiredIndicatorReRegRequiredIndicator0..1Indicates whether UE re-registration is required in the DEREGISTRATION REQUEST message, if available, see clause 9.11.3.20 of TS 24.501.C
unavailabilityPeriodDurationUnavailabilityPeriodDuration0..1Period duration the UE is unavailable. Include if sent in the DEREGISTRATION REQUEST message. See clause 8.2.12.1 of TS 24.501. Encoded as GPRS Timer 3, see clause 10.5.7.4a of TS 24.008, omitting the first two octets.C
NOTE:
At least one among SUPI, SUCI, PEI and GPSI shall be provided.
Up
6.2.2.2.4  Location update  p. 53
The IRI-POI in the AMF shall generate an xIRI containing an AMFLocationUpdate record each time the IRI-POI present in an AMF detects that the target's UE location is updated due to target UE mobility or as a part of an AMF service procedure and the reporting of location information is not restricted by service scoping. 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.
The UE mobility events resulting in generation of an AMFLocationUpdate xIRI include the N2 Path Switch Request (Xn based inter NG-RAN handover procedure described in clause 4.9.1.2 of TS 23.502) and the N2 Handover Notify (Inter NG-RAN node N2 based handover procedure described in clause 4.9.1.3 of TS 23.502).
The AMFLocationUpdate xIRI is also generated when the AMF receives an NG-RAN NGAP PDU Session Resource Modify Indication message as a result of Dual Connectivity activation/release for the target UE, as described in clause 10 of TS 37.340.
Optionally, based on operator policy, other NG-RAN NGAP messages that do not generate separate xIRI but carry location information (e.g. RRC INACTIVE TRANSITION REPORT) may trigger the generation of an xIRI AMFLocationUpdate record.
Additionally, based on regulatory requirements and operator policy, the location information obtained by AMF from NG-RAN or LMF in the course of some service operation (e.g. emergency services, LCS) may generate xIRI AMFLocationUpdate record. The AMF services providing the location information in these cases include the AMF Location Service (ProvideLocInfo, ProvidePosInfo, NotifiedPosInfo and EventNotify service operations) and the AMF Exposure Service (AmfEventReport with LOCATION_REPORT) (see TS 29.518). Additionally, the AMF Communication Service (Namf_Communication_N1MessageNotify service operation) may be monitored to capture the location information in the scenarios described in clause 6.3.1 of TS 23.273. Also, in the case of Mobile Originated LCS service invoked by the target, the location information may be derived from a Nlmf_Location_DetermineLocation Response to AMF (see clause 6.2 of TS 23.273).
The AMFLocationUpdate record is also used by LARF to deliver Location Acquisition responses to MDF2, as described in clause 7.3.5.6. The IRI-POI in the AMF shall not generate the AMFLocationUpdate xIRI when the location is acquired as the result of a LARF request, as described in clause 7.3.5.2 of TS 33.127.
Field name Type Cardi­nality Description M/C/O
sUPISUPI1SUPI associated with the location update (see clause 6.2.2.4).M
sUCISUCI0..1SUCI associated with the location update, if available, see TS 24.501.C
pEIPEI0..1PEI associated with the location update, if available.C
gPSIGPSI0..1GPSI associated with the location update, if available as part of the subscription profile.C
gUTIFiveGGUTI0..15G-GUTI associated with the location update, if available, see TS 24.501.C
locationLocation1Updated 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:
  1. as a Location.locationInfo.userLocation parameter in the case the information is obtained from an NGAP message, except the LOCATION REPORT message (see TS 38.413);
  2. as a Location.locationInfo in the case the information is obtained from a ProvideLocInfo (clause 6.4.6.2.6 of TS 29.518);
  3. as a Location.locationPresenceReport parameter in the case the information is obtained from an AmfEventReport (clause 6.2.6.2.5 of TS 29.518) with event type Location-Report or Presence-In-AOI-Report;
  4. as a Location.positioningInfo.positionInfo parameter in the case the information is obtained from a ProvidePosInfo (clause 6.4.6.2.3 of TS 29.518) or a NotifiedPosInfo (clause 6.4.6.2.4 of TS 29.518).
If available, other parameters reportable via Location shall be included.		M
deprecatedSMSoverNASIndicatorSMSOverNASIndicator0..1No longer used in present version of this specification.C
deprecatedOldGUTIEPS5GGUTI0..1No longer used in present version of this specification.C
uEAreaIndicationUEAreaIndication0..1 Contains a country, area in a country or international area indication where UE is located, if available. If UE is outside of the area of any known country, i.e. international area, it contains the international area indication without a country. See Table 6.2.2.2.2-2 for details on this data type.C
Up
6.2.2.2.5  Start of interception with registered UE  p. 54
The IRI-POI in the AMF shall generate an xIRI containing an AMFStartOfInterceptionWithRegisteredUE record when the IRI-POI present in the AMF detects that interception is activated on a UE that has already been registered in the 5GS (see clause 6.2.2.4 on identity privacy). A UE is considered already registered to the 5GS when the 5GMM state for the access type (3GPP NG-RAN or non-3GPP access) for that UE is 5GMM-REGISTERED. Therefore, the IRI-POI present in the AMF shall generate the xIRI AMFStartOfInterceptionWithRegisteredUE record when it detects that a new interception for a UE is activated (i.e. provisioned by the LIPF) and the 5G mobility management state for the access type (3GPP NG-RAN or non-3GPP access) within the AMF for that UE is 5GMM-REGISTERED. If the UE is registered over both 3GPP NG-RAN and non-3GPP access, the IRI-POI present in the AMF shall generate an xIRI containing an AMFStartOfInterceptionWithRegisteredUE record for each access type.
Field name Type Cardi­nality Description M/C/O
registrationResultAMFRegistrationResult1Specifies the result of registration, see clause 9.11.3.6 of TS 24.501.M
registrationTypeAMFRegistrationType0..1Specifies the type of registration, see clause 9.11.3.7 of TS 24.501, if available.C
sliceSlice0..1Provide, if available, one or more of the following: C
sUPISUPI1SUPI associated with the target UE.M
sUCISUCI0..1SUCI used in the registration, if available.C
pEIPEI0..1PEI associated with the target UE, if available.C
gPSIGPSI0..1GPSI associated with the target UE, if available.C
gUTIFiveGGUTI1Latest 5G-GUTI assigned to the target UE by the AMF.M
locationLocation0..1Location information associated with the access type for the target UE, if available.
Shall be encoded using the Location.locationInfo.userLocation parameter and, when Dual Connectivity is activated, using the Location.locationInfo.additionalCellIDs parameter (see attachment TS33128Payloads.asn). If available, other parameters reportable via Location shall be included.		C
non3GPPAccessEndpointUEEndpointAddress0..1UE's local IP address used to reach the N3IWF, TNGF or TWIF, if available. IP addresses are given as 4 octets (for IPv4) or 16 octets (for IPv6) with the most significant octet first (network byte order).C
timeOfRegistrationTimestamp0..1Time at which the last registration occurred, if available. This is the time stamp when the REGISTRATION ACCEPT message was sent to the UE or (when applicable) when the REGISTRATION COMPLETE was received from the UE.
Shall be given qualified with time zone information (i.e. as UTC or offset from UTC, not as local time).		C
fiveGSTAIListTAIList0..1List of tracking areas associated with the target UE for the access type.C
sMSoverNASIndicatorSMSOverNASIndicator0..1Indicates whether SMS over NAS is supported. Provide, if included in the UE Context.C
oldGUTIEPS5GGUTI0..1Latest GUTI or 5G-GUTI received from the target UE if different than the latest GUTI assigned by the AMF and the target UE has not acknowledged the latest GUTI assignment.C
eMM5GRegStatusEMM5GMMStatus0..1UE Status, if this parameter can be derived from information available in the UE Context at the AMF.C
sORTransparentContainerSORTransparentContainer0..1Provides the list of preferred PLMN/access technology combinations. Included if sent in the NAS N1 message REGISTRATION ACCEPT. Given as a SoR Transparent container encoded per clause 9.11.3.51 of TS 24.501 omitting the first three octets.C
uEPolicyUEPolicy0..1 Content of the N1 NAS message MANAGE UE POLICY COMMAND, as defined in TS 24.501 Table D.5.1.1.1.C
unavailabilityPeriodDurationUnavailabilityPeriodDuration0..1Period duration the UE is unavailable. Include if sent in the REGISTRATION REQUEST. See clause 8.2.6.1 of TS 24.501. Encoded as GPRS Timer 3, see clause 10.5.7.4a of TS 24.008, omitting the first two octets.C
fiveGSUpdateTypeFiveGSUpdateType0..1Shall contain the target 5GS Update Type information octets if sent in the REGISTRATION REQUEST message. Defined in clause 9.11.3.9A of TS 24.501, omitting the first two octets.C
uEAreaIndicationUEAreaIndication0..1 Contains a country, area in a country or international area indication where UE is located, if available. If UE is outside of the area of any known country, i.e. international area, it contains the international area indication without a country. See for details on this data type.C
NOTE:
The values of the parameters in the Table above are derived from the UE Context at the AMF, see clause 5.2.2.2.2 of TS 23.502.
The IRI-POI present in the AMF generating an xIRI containing an AMFStartOfInterceptionWithRegisteredUE 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).
Up
6.2.2.2.6  AMF unsuccessful procedure  p. 56
The IRI-POI in the AMF shall generate an xIRI containing an AMFUnsuccessfulProcedure record when the IRI-POI present in the AMF detects an unsuccessful procedure for a UE matching one of the target identifiers provided via LI_X1.
Accordingly, the IRI-POI in the AMF generates the xIRI when any of the following events is detected:
  • AMF sends a N1: REGISTRATION REJECT message to the target UE and the UE 5G Mobility Management (5GMM) state for the access type (3GPP NG-RAN or non-3GPP access) within the AMF is changed to 5GMM-DEREGISTERED.
  • AMF aborts a registration procedure before the UE 5G Mobility Management (5GMM) state for the access type (3GPP NG-RAN or non-3GPP access) within the AMF is changed to 5GMM-REGISTERED.
  • AMF sends a SERVICE REJECT message to the target UE including a PDU session establishment reject message type.
  • AMF aborts a UE-initiated NAS transport procedure with payload container type IE set to "SMS".
    Unsuccessful registration shall be reported only if the target UE has been successfully authenticated.
Field Name Description M/C/O
failedprocedureTypeSpecifies the procedure which failed at the AMF.M
failureCause Provides the value of the 5GSM or 5GMM cause, see clauses 9.11.3.2 and 9.11.4.2 of TS 24.501. The integer value is mapped from the second octet shown in clauses 9.11.3.2 and 9.11.4.2 of TS 24.501.M
requestedSliceSlice requested for the procedure, if available, given as a NSSAI (a list of S-NSSAI values as described in clause 9.11.3.37 of TS 24.501).C
sUPISUPI associated with the procedure, if available (see NOTE).C
sUCISUCI used in the procedure, if applicable and if available (see NOTE).C
pEIPEI used in the procedure, if available (see NOTE).C
gPSIGPSI used in the procedure, if available (see NOTE).C
gUTI5G-GUTI used in the procedure, if available, see clause 9.11.3.4 of TS 24.501 (see NOTE).C
locationLocation information determined during the procedure, if available.
Shall be encoded using the Location.locationInfo.userLocation parameter. 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.2.2.2.7  AMF identifier association  p. 57
The IRI-POI present in the AMF shall generate an xIRI containing an AMFIdentifierAssociation record when the IRI-POI present in the AMF 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.2.2.2.1).
Field name Type Cardi­nality Description M/C/O
sUPISUPI1SUPI associated with the procedure (see NOTE 1).M
sUCISUCI0..1SUCI used in the procedure, if applicable and if available.C
pEI0..1PEIPEI used in the procedure, if available (see NOTE 1).C
gPSIGPSI0..1GPSI used in the procedure, if available (see NOTE 1).C
gUTIFiveGGUTI15G-GUTI used in the procedure, see clause 9.11.3.4 of TS 24.501.M
locationLocation1Location information available when identifier association occurs.
Shall be encoded using the Location.locationInfo.userLocation parameter (see attachment. If available, other parameters reportable via Location shall be included.		M
fiveGSTAIListTAIList0..1List of tracking areas associated with the registration area within which the UE is current registered, see clause 9.11.3.9 of TS 24.501. (see NOTE 2)C
NOTE 1:
SUPI shall always be provided, in addition to the warrant target identifier if different to SUPI. Other identifiers shall be provided if available.
NOTE 2:
List shall be included each time there is a change to the registration area.
The IRI-POI present in the AMF generating an xIRI containing an AMFIdentifierAssociation 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).
Up
6.2.2.2.8  Positioning info transfer  p. 57
The IRI-POI present in the AMF shall generate an xIRI containing an AMFPositioningInfoTransfer when the IRI-POI present in the AMF detects one of the following events :
  • an NRPPa (see TS 38.455) message related to a target UE has been exchanged between the LMF and NG-RAN via the AMF.
  • a LPP (see TS 37.355) message related to a target UE has been exchanged between the LMF and the target UE via the AMF.
Accordingly, the IRI-POI in AMF generates the xIRI when any of the following events is detected:
  • AMF receives an Namf_Communication_N1N2MessageTransfer (see TS 29.518) from LMF to request the transfer of a NRPPa request to the serving NG-RAN node for a target UE as part of a UE associated NRPPa positioning activity. The NRPPa request may be E-CID MEASUREMENT INITIATION REQUEST or OTDOA INFORMATION REQUEST.
  • AMF sends a Namf_Communication_N2InfoNotify (TS 29.518) to the LMF to forward the NRPPa response or report received from the NG-RAN for a target UE. The NRPPa response or report may be E-CID MEASUREMENT INITIATION RESPONSE, E-CID MEASUREMENT REPORT or OTDOA INFORMATION RESPONSE.
  • AMF receives an Namf_Communication_N1N2MessageTransfer (TS 29.518) from LMF to request the transfer of a LPP message to a target UE as part of a LPP positioning activity.
  • AMF sends an Namf_Communication_N1MessageNotify (TS 29.518) to LMF to forward a LPP message received from the target UE.
Field name Type Cardi­nality Description M/C/O
sUPISUPI1 SUPI associated with the procedure (see NOTE 1 in Table 6.2.2.2.7-1).M
sUCISUCI0..1SUCI used in the procedure, if applicable and if available.C
pEIPEI0..1 PEI used in the procedure, if available (see NOTE 1 in Table 6.2.2.2.7-1).C
gPSI0..1GPSI vGPSI used in the procedure, if available (see NOTE 1 in Table 6.2.2.2.7-1).C
gUTIFiveGGUTI0..15G-GUTI used in the procedure, see clause 9.11.3.4 of TS 24.501.C
nRPPaMessageOCTET STRING0..1Any UE associated NRPPa message exchanged between the LMF and NG-RAN via AMF.C
lPPMessageOCTET STRING0..1Any LPP message exchanged between the LMF and the target UE via AMF.C
lcsCorrelationIdUTF8String (SIZE(1..255))1LCS correlation ID (see clause 6.1.6.3.2 of TS 29.572) related to a location session, found in the Namf_CommunicationN1N2MessageTransfer and corresponding Namf_Communication_N2InfoNotify or Namf_CommunicationN1MessageNotify. All the AMFPositioningInfoTransfer records related to the same location session have the same lcsCorrelationId. M
Up
6.2.2.2.9  Handovers  p. 58
6.2.2.2.9.1  General  p. 58
The present clause provides the LI requirements for NG interface-based handovers which occur for a target UE. Such handovers may be intra 5GS (inter-gNB), 5GS to EPS (inter-system), EPS to 5GS (inter-system), or 5GS to UTRA (inter-system).
The following xIRI records are used to report handover related events between the AMF and RAN nodes for the target UE when the delivery of location information is not restricted by service scoping:
  • AMFRANHandoverCommand.
  • AMFRANHandoverRequest.
The above xIRIs are used to report handover events and information that are not carried in the AMFLocationUpdate (clause 6.2.2.2.4) record and shall include the information transferred between the AMF and RAN nodes, as a part of handover preparation, resource allocation, and handover notification.
Up
6.2.2.2.9.2  Handover command  p. 58
The IRI-POI in the AMF shall generate an xIRI containing an AMFRANHandoverCommand record when the IRI-POI present in the AMF detects that the AMF 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 AMF context. See clause 6.1.6.2.25 of TS 29.518 and clause 4.11.2.2 of TS 23.502.M
aMFUENGAPIDAMFUENGAPID1Identity that the AMF uses to uniquely identify the target UE over the NG Interface. See clause 9.3.3.1 of TS 38.413. This is correlated to the SUPI known in the UE AMF context.M
rANUENGAPIDRANUENGAPID1Identity that the AMF receives from the NG-RAN node uniquely identifying the target UE with the NG-RAN Node. See clause 9.3.3.2 of TS 38.413.M
handoverTypeHandoverType1Identifies the type of handover indicated by the source RAN node to the AMF. See clause 9.3.1.22 of TS 38.413.M
targetToSourceContainerRANTargetToSourceContainer1Provides radio related information about the gaining NG-RAN node. See clause 9.3.1.21 of TS 38.413.M
Up
6.2.2.2.9.3  Handover request  p. 59
The IRI-POI in the AMF shall generate an xIRI containing an AMFRANHandoverRequest record when the IRI-POI in the AMF detects that the AMF received a HANDOVER REQUEST ACKNOWLEDGE message from the target 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 user identifiers associated with the target UE registration stored in the AMF context. See clause 6.1.6.2.25 of TS 29.518 and clause 4.11.2.2 of TS 23.502.M
aMFUENGAPIDAMFUENGAPID1Identity that the AMF uses to uniquely identify the target UE over the NG Interface, See clause 9.3.3.1 of TS 38.413. This is correlated to the SUPI known in the UE AMF context.M
rANUENGAPIDRANUENGAPID1Identity that the AMF receives from the NG-RAN node uniquely identifying the target UE within the NG-RAN Node. See clause 9.3.3.2 of TS 38.413.M
handoverTypeHandoverType1Identifies the type of handover indicated by the AMF to gaining RAN Node as seen in the HANDOVER REQUEST message. See clause 9.3.1.22 of TS 38.413.M
handoverCauseHandoverCause1Indicates the cause of handover as seen in the HANDOVER REQUEST message from AMF to gaining RAN node. See clause 9.3.1.2 of TS 38.413.M
pDUSessionResourceInformationPDUSessionResourceInformation1 Indicates the PDU Session to be transferred and Handover Command Transfer information as seen in the HANDOVER REQUEST and confirmed in the HANDOVER REQUEST ACKNOWLEDGE message. See clauses 9.3.1.50 and 9.3.4.10 of TS 38.413.M
mobilityRestrictionListMobilityRestrictionvList0..1Provides roaming or access restrictions related to mobility from AMF to gaining RAN Node. Include if sent in HANDOVER REQUEST. See clause 9.3.1.85 of TS 38.413.C
locationReportingRequestTypeLocationReportingRequestType0..1Indicates the type of location reporting requested in the HANDOVER REQUEST. Include if in HANDOVER REQUEST message. See clause 9.3.1.65 of TS 38.413.C
targetToSourceContainerRANTargetToSourceContainer1Provides radio related information from gaining to losing NG-RAN node that the AMF receives from the gaining RAN Node in the HANDOVER REQUEST ACKNOWLEDGE message. See clause 9.3.1.21 of TS 38.413.M
nPNAccessInformationNPNAccessInformation0..1Globally identifies the secondary NG-RAN node CAG Cells. Include if sent in the HANDOVER REQUEST ACKNOWLEDGE message from gaining RAN node to AMF. See clause 9.3.3.46 of TS 38.413.C
rANSourceToTargetContainerRANSourceToTargetContainer1Provides radio related information via the AMF in the HANDOVER REQUEST from source to gaining NG-RAN node. See clause 9.3.1.21 of TS 38.413.M
Up
6.2.2.2.10  UE Configuration Update  p. 60
The IRI-POI in the AMF shall generate an xIRI containing a AMFUEConfigurationUpdate record when the IRI-POI present in the AMF detects that a UE matching one of the target identifiers provided via LI_X1 has been commanded to update its configuration. Accordingly, the IRI-POI in the AMF generates the xIRI when the following event is detected:
  • AMF sends a CONFIGURATION UPDATE COMMAND message to the target UE.
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 AMF context. See clause 6.1.6.2.25 of TS 29.518.M
gUTIGUTI1Current 5G-GUTI associated with the UE context. If the AMF includes a new 5G-GUTI as a part of the configuration update, this parameter shall be set to the new GUTI and the oldGUTI parameter shall be populated, see clause 8.2.19.3 of TS 24.501.M
oldGUTIEPS5GGUTI0..1Old 5G-GUTI associated with the UE context. If the AMF includes a new 5G-GUTI as a part of the configuration update, this parameter shall be set to the old GUTI.C
fiveGSTAIListTAIList0..1List of tracking areas associated with the registration area within which the UE is current registered, see clause 9.11.3.9 of TS 24.501. Shall be included each time there is a change to the registration area and omitted if the registration area does not change.C
sliceSlice0..1Provide, if available, one or more of the following:
This is derived from the information sent to the UE in the CONFIGURATION UPDATE COMMAND message.		C
serviceAreaListServiceAreaList0..1Includes a list of allowed service areas or non-allowed service areas, encoded per clause 9.11.3.49 of TS 24.501, omitting the first two octets. Shall be included if present in the CONFIGURATION UPDATE COMMAND message, see clause 8.2.19 of TS 24.501.C
registrationResultAMFRegistrationResult0..1Specifies the result of registration, see clause 9.11.3.6 of TS 24.501. Shall be included if present in the CONFIGURATION UPDATE COMMAND message, see clause 8.2.19 of TS 24.501.C
sMSoverNASIndicatorSMSOverNASIndicator0..1Indicates whether SMS over NAS is supported. Shall be present if the SMS indication is present in the CONFIGURATION UPDATE COMMAND message, see clause 8.2.19 of TS 24.501.C
Up
6.2.2.2.11  Trace  p. 61
6.2.2.2.11.1  General  p. 61
Trace procedures, as defined in TS 32.423, allow for the AMF 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 AMF for a target UE.
The following xIRI records are used to report trace related events between the AMF and RAN nodes for the target UE when the delivery of location information is not restricted by service scoping:
  • AMFRANTraceReport
Up
6.2.2.2.11.2  AMF RAN trace report  p. 61
The IRI-POI in the AMF shall generate an xIRI containing an AMFRANTraceReport record when the IRI-POI present in the AMF has detected any of the following events:
  • AMF sent a TRACE START message to the target RAN node (old RAN node) in response to a Trace Session Activation message for the target.
  • AMF received a CELL TRAFFIC TRACE message from the NG-RAN for the target.
  • AMF sent MDT or trace data to the trace collection entity for the target.
  • AMF sent a deactivate trace message to the NG-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 AMF context. See clause 6.1.6.2.25 of TS 29.518.M
aMFUENGAPIDAMFUENGAPID1Identity that the AMF uses to uniquely identify the target UE over the NG Interface. See clause 9.3.3.1 of TS 38.413. This is correlated to the SUPI known in the UE AMF context.M
rANUENGAPIDRANUENGAPID1Identity that the AMF receives from the NG-RAN node uniquely identifying the target UE with the NG-RAN Node. See clause 9.3.3.2 of TS 38.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
traceDirectionTraceDirection1Identifies which network element is signalling the trace information. This parameter is populated with a choice of either AMF or NG-RAN. See clause 9.2.10.4 of TS 38.413.M
deprecatedTraceActivationInfoTraceActivationInfo0No longer used in present version of this specification. Use traceActivation instead.O
nGRANCGINCGI1Identifies the NR-RAN Cell Global Identifier of the cell performing the UE trace.M
globalRANNodeIDGlobalRANNodeID1Uniquely identifies the NG-RAN node to which the TRACE START message is sent. This is derived from the initial NG Setup exchange between the NG-RAN node and the AMF.M
traceCollectionEntityInfoTraceCollectionEntityInfo0..1 Provides information related to the trace collection entity to which the AMF 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.3.2.4 and 9.3.2.14 of TS 38.413.C
aMFTraceDataXMLType1 Includes the trace data (in raw XML format) sent from the AMF to the trace collection entity when the AMF is the trace collection NE. See clauses 4.18 and 5.2 of TS 32.423.M
locationLocation0..1Shall be provided if the current location is known in the UE context at the AMF or supplemented by the MDF2.C
traceActivationTraceActivation0..1Information related to a trace session activation provided from the AMF to the NG-RAN node. Shall be populated if the traceRecordType is set to Trace Start.
The ExternalASNType.encodedASNValue.alignedPER choice shall be used when populating this type and it shall be populated with the contents of the Trace Activation IE defined in clause 9.3.1.14 of TS 38.413.		C
Field name Type Cardi­nality Description M/C/O
traceCollectionEntityIPBIT STRING (SIZE(1..160, …))1Indicates the transport layer address of the trace collection entity. May include IPv4, IPv6, or IPv4 and IPv6 addresses. Encoded per clause 5.3 of TS 38.414.M
traceCollectionEntityURIUTF8String1Indicates the URI of the trace collection entity. Include if sent in the TRACE START message. If the TRACE START message does not include a traceCollectionEntityURI, this parameter shall be sent as an empty string. See clause 9.3.1.14 of TS 38.413.M
Up
6.2.2.2.12  UE policy transfer  p. 63
The IRI-POI present in the AMF shall generate an xIRI containing an AMFUEPolicyTransfer record when the IRI-POI present in the AMF detects one of the following events:
  • AMF sends a Namf_Communication_N1MessageNotify Request (See clause 5.2.2.3 of TS 29.518) related to the target UE containing the N1 NAS message MANAGE UE POLICY COMPLETE. It confirms that UE policies forwarded by AMF to the target UE in the N1 NAS message MANAGE UE POLICY COMMAND have been accepted by the UE.
Field name Type Cardi­nality Description M/C/O
sUPISUPI1RCS target identities. All identities associated to the target known at the POI shall be included.M
sUCISUCI0..1RCS Registration type, i.e. registration, re-registration and deregistration.C
pEIPEI0..1SIP REGISTER request related to target IMS Registration, Re-registration or Deregistration.C
gPSIGPSI0..1SIP REGISTER response related to target IMS Registration, Re-registration or Deregistration.C
gUTIFiveGGUTI0..1Shall include the target's location when reporting of the target's location information if authorized and available.C
uePolicyUEPolicy1 Content of the N1 NAS message MANAGE UE POLICY COMMAND, as defined in TS 24.501 Table D.5.1.1.1.M
Up
6.2.2.2.13  Service Accept  p. 63
The IRI-POI in the AMF shall generate an xIRI containing an or AMFUEServiceAccept record when the IRI-POI in present in the AMF detects that the AMF has sent a service accept in response to a service request or control plane service request from the target. Accordingly, the IRI-POI in the AMF generates the xIRI when any of the following events are detected:
  • AMF sends a SERVICE ACCEPT message to the target in response to a SERVICE REQUEST message from the target.
  • AMF sends a SERVICE ACCEPT message to the target in response to a CONTROL PLANE SERVICE REQUEST message from 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 AMF context. See clause 6.1.6.2.25 of TS 29.518.M
serviceMessageIdentityServiceMessageIdentity1Indicates the type of message sent within the SERVICE ACCEPT from the AMF to the UE. Encoding per clause 9.7 of TS 24.501.M
serviceTypeOCTET STRING (SIZE (1))0..1Indicates the purpose of the service request procedure. Encoded per clause 9.11.3.50 of TS 24.501.C
fiveGTMSIFiveGTMSI0..1 TMSI value associated with the target within the AMF context. Include if known. Encoded per TS 24.501 Figure 9.11.3.4.5.C
uplinkDataStatusOCTET STRING (SIZE (2..32))0..1Indicates if uplink data is pending for the PDU Session modified in the SERVICE REQUEST. See clause 9.11.3.57 of TS 24.501.C
pDUSessionStatusOCTET STRING (SIZE (2..32))0..1Indicates the current status of the PDU Session (active, inactive) for the PDU Session the target has attempted to activate. This parameter is encoded using the format defined in clause 9.11.3.44 of TS 24.501.C
deprecatedUERequestTypeFiveGSMRequestType0No longer used in present version of this specification. Use uERequestType instead.O
pagingRestrictionPagingRestrictionIndicator0..1 Indicates the current paging restriction status for the target as known at the AMF. Encoded per Figure 9.11.3.77.2 of TS 24.501, omitting the first two octets.C
forbiddenTAIListTAIList0..1 Provides a list of tracking areas that the UE is forbidden to use either during roaming or configured via regional service provisioning. See clauses 8.2.17.7 and 8.2.17.8 of TS 24.501.C
uERequestTypeMUSIMUERequestType0..1Indicates a MUSIM UE has requested release of NAS signalling or has rejected paging. Include if the UE Request Type IE message (see clause 9.11.3.76 of TS 24.501) is sent in the SERVICE REQUEST or CONTROL PLANE SERVICE REQUEST. Encoded per UE Request Type as defined in clause 9.9.3.65 of TS 24.301 omitting the first two octets.C
Up

Up   Top   ToC