3GPP 24.501 v20.0.0 — the document's own text
4.23.5 Handling multiple tracking area codes from the lower layers
When a UE camps on a satellite NG-RAN cell, the UE may receive multiple TACs from the lower layers. The UE shall construct TAIs from the multiple TACs (i.e. concatenate the identity of the current PLMN and each of the TACs) and select a TAI as follows:
- If at least one TAI belongs to the current registration area of the UE, the UE shall select a TAI which belongs to the current registration area of the UE according to the followings.
If there are multiple TAIs which belong to the current registration area of the UE, the UE shall select a TAI as follows:
- if there is a TAI which belongs to the list of "allowed tracking area" (if any) and does not belong to the list of "non-allowed tracking areas" (if any), the UE shall select a TAI which belongs to the list of "allowed tracking area" (if any) and does not belong to the list of "non-allowed tracking areas" (if any). In this case, if there are multiple TAIs which belong to the list of "allowed tracking area" (if any) and does not belong to the list of "non-allowed tracking areas" (if any), then the UE shall consider each of these TAIs equal and select a TAI in an implementation-specific way (e.g. taking into account LADN service area information). If these multiple TAIs contain the previous current TAI, the current TAI can be left unchanged.
- if there is no TAI which belongs to the list of "allowed tracking area" (if any) and does not belong to the list of "non-allowed tracking areas" (if any) or neither the list of "allowed tracking area" nor the list of "non-allowed tracking areas" is available, then the UE shall consider each of these TAIs equal and select a TAI in an implementation-specific way (e.g. taking into account LADN service area information). If these multiple TAIs contain the previous current TAI, the current TAI can be left unchanged.
- If the current registration area is not available in the UE or no TAI belongs to the current registration area of the UE and:
- there is a TAI which belongs to neither the list of "5GS forbidden tracking areas for roaming" nor the list of "5GS forbidden tracking areas for regional provision of service", the UE shall select a TAI which belongs to neither the list of "5GS forbidden tracking areas for roaming" nor the list of "5GS forbidden tracking areas for regional provision of service". In this case, if there are multiple TAIs which belong to neither the list of "5GS forbidden tracking areas for roaming" nor the list of "5GS forbidden tracking areas for regional provision of service", then the UE shall consider each of these TAIs equal and select a TAI in an implementation-specific way.
- all TAIs belong to the list of "5GS forbidden tracking areas for roaming" or the list of "5GS forbidden tracking areas for regional provision of service", then the UE shall consider each of these TAIs equal and select a TAI in an implementation-specific way.
The UE shall consider the selected TAI as the current TAI. The UE shall select a TAI when:
- the UE receives multiple TACs from the lower layers; or
- the UE has received multiple TACs from the lower layers upon starting to camping on the current cell and the registration area, the list of "allowed tracking areas", the list of "non-allowed tracking areas", the list of "5GS forbidden tracking areas for roaming", or the list of "5GS forbidden tracking areas for regional provision of service" is updated.
Handling of the list of "5GS forbidden tracking areas for roaming" and the list of "5GS forbidden tracking areas for regional provision of service" is specified in clause 5.3.13.