Editing My 33.128 Notes (section)

====== 6.2.2A.2.2	Association Events ======
For each association event, the IEF shall create an IEFAssociationRecord, as defined below.
{| class="wikitable sortable"
|+ Payload for IEFAssociationRecord
|-
! Field name !! Description !! M/C/O
|-
| sUPI || SUPI associated with detected association event. || M
|-
| fiveGGUTI || 5G-GUTI shall be provided. Encoded as per TS 24.501 figure 9.11.3.4.1, omitting the first four octets. || M
|-
| timeStamp || Time at which the identifier association event occurred. Shall be given qualified with time zone information (i.e. as UTC or offset from UTC, not as local time). || M
|-
| tAI || Last known TAI associated with the SUPI. Encoded as per TS 24.501 clause 9.11.3.8, omitting the first octet. || M
|-
| nCGI || Last known nCGI(s) available when identifier association event detected. Given as a sequence of PLMNID (encoded as per TS 38.413 clause 9.3.3.5) and NCI (encoded as per TS 38.413 clause 9.3.1.7). || M
|-
| nCGITime || ueLocationTimestamp(s) of nCGIs if available in AMF as per TS 29 .571 clause 5.4.4.9. If ueLocationTimestamp(s) is not available, shall be populated with timeStamp(s) of when last known nCGI(s), were obtained and stored by the AMF. || M
|-
| sUCI || SUCI shall be provided when event is triggered by association of a SUCI to a SUPI. Encoded as per TS 24.501 clause 9.11.3.4, omitting the first 3 octets. || C
|-
| pEI || PEI, (see NOTE 1). || C
|-
| fiveGSTAIList || List of tracking areas associated with the registration area within which the UE is current registered, see TS 24.501, clause 9.11.3.9. (see NOTE 2) || C
|-
| gPSI || GPSI, (see NOTE 1). || C
|-
|colspan="3"|
:NOTE 1: Shall be provided in first association record to ICF after PEI or GPSI is available and following any change of PEI or GPSI.
:NOTE 2: As a minimum, list of tracking areas shall be included in the first association event for each SUPI registered (per UE session) with the AMF and additionally whenever the TAI list changes due to a change in registration area.
|}

For each de-association event, the IEF shall create an IEFDeassociationRecord, as defined below.

{| class="wikitable sortable"
|+ Payload for IEFDeassociationRecord
|-
! Field name !! Description !! M/C/O
|-
| sUPI || SUPI associated with detected de-association event. || M
|-
| fiveGGUTI || 5G-GUTI shall be provided. Encoded as per TS 24.501 [13] figure 9.11.3.4.1, omitting the first four octets. || M
|-
| timeStamp
| Time at which the identifier de-association event occurred.
Shall be given qualified with time zone information (i.e. as UTC or offset from UTC, not as local time).
| M
|-
| nCGI
| Last known nCGI(s) available when identifier de-association event detected. Given as a sequence of PLMNID (encoded as per TS 38.413 clause 9.3.3.5) and NCI (encoded as per TS 38.413 clause 9.3.1.7).
| M
|-
| nCGITime
| ueLocationTimestamp(s) of nCGIs if available in AMF as per TS 29 .571 clause 5.4.4.9.
If ueLocationTimestamp(s) is not available, shall be populated with timeStamp(s) of when last known nCGI(s), were obtained and stored by the AMF.	
| M
|}