Tech-invite3GPPspaceIETF RFCsSIP
Quick21222324252627282931323334353637384‑5x

Content for  TS 24.501  Word version:  17.5.0

Top   Top   Up   Prev   Next
1…   3…   4…   4.4…   4.4.3…   4.5…   4.5.3…   4.6…   4.7…   4.9…   4.15…   5…   5.2…   5.3…   5.3.2…   5.3.7…   5.3.19…   5.4…   5.4.1.3…   5.4.2…   5.4.4…   5.4.5…   5.4.6…   5.5…   5.5.1.2.4   5.5.1.2.5…   5.5.1.3…   5.5.1.3.4   5.5.1.3.5…   5.5.2…   5.6…   5.6.2…   6…   6.1.4…   6.2…   6.3…   6.3.2…   6.3.3…   6.4…   6.4.1.4…   6.4.2…   6.5…   7…   8…   8.2.9…   8.3…   9…   9.11.2…   9.11.2.10…   9.11.3…   9.11.3.4…   9.11.3.8…   9.11.3.14…   9.11.3.18C…   9.11.3.29…   9.11.3.33…   9.11.3.39…   9.11.3.45…   9.11.3.50…   9.11.3.53A…   9.11.3.68…   9.11.3.75…   9.11.4…   9.11.4.10…   9.11.4.13…   9.11.4.16…   9.11.4.30…   9.12   10…   A…   B…   C…   D…   D.6…   D.6.3…

 

C (Normative)  Storage of 5GMM informationWord‑p. 841

C.1  Storage of 5GMM information for UEs not operating in SNPN access operation mode |R16|Word‑p. 841

The following 5GMM parameters shall be stored on the USIM if the corresponding file is present:
  1. 5G-GUTI;
  2. last visited registered TAI;
  3. 5GS update status;
  4. 5G NAS security context parameters from a full native 5G NAS security context (see TS 33.501);
  5. KAUSF and KSEAF (see TS 33.501);
  6. SOR counter (see subclause 9.11.3.51);
  7. SOR-CMCI; and
  8. UE parameter update counter (see subclause 9.11.3.53A);
The UE may support multiple records of NAS security context storage for multiple registration (see TS 31.102). If the UE supports multiple records of NAS security context storage for multiple registration, the first 5G security context of one access shall be stored in record 1 of the 5G NAS Security Context USIM file for that access and the second 5G security context of that access shall be stored in record 2 of the same file. The presence and format of corresponding files on the USIM is specified in TS 31.102.
If the corresponding file is not present on the USIM, these 5GMM parameters are stored in a non-volatile memory in the ME together with the SUPI from the USIM. These 5GMM parameters can only be used if the SUPI from the USIM matches the SUPI stored in the non-volatile memory; else the UE shall delete the 5GMM parameters.
The following 5GMM parameters shall be stored in a non-volatile memory in the ME together with the SUPI from the USIM:
  • configured NSSAI(s);
  • NSSAI inclusion mode(s);
  • MPS indicator;
  • MCS indicator;
  • operator-defined access category definitions;
  • network-assigned UE radio capability IDs;
  • "CAG information list", if the UE supports CAG;
  • signalled URSP (see TS 24.526); and
  • SOR-CMCI.
Each configured NSSAI consists of S-NSSAI(s) stored together with a PLMN identity, if it is associated with a PLMN. The UE shall store the S-NSSAI(s) of the HPLMN. If the UE is in the VPLMN, the UE shall also store the configured NSSAI for the current PLMN and any necessary mapped S-NSSAI(s). The configured NSSAI(s) can only be used if the SUPI from the USIM matches the SUPI stored in the non-volatile memory of the ME; else the UE shall delete the configured NSSAI(s).
Each NSSAI inclusion mode is associated with a PLMN identity and access type. The NSSAI inclusion mode(s) can only be used if the SUPI from the USIM matches the SUPI stored in the non-volatile memory of the ME; else the UE shall delete the NSSAI inclusion mode(s).
The MPS indicator is stored together with a PLMN identity of the PLMN that provided it, and is valid in that RPLMN or equivalent PLMN. The MPS indicator can only be used if the SUPI from the USIM matches the SUPI stored in the non-volatile memory of the ME, else the UE shall delete the MPS indicator.
The MCS indicator is stored together with a PLMN identity of the PLMN that provided it, and is valid in that RPLMN or equivalent PLMN. The MCS indicator can only be used if the SUPI from the USIM matches the SUPI stored in the non-volatile memory of the ME, else the UE shall delete the MCS indicator.
Operator-defined access category definitions are stored together with a PLMN identity of the PLMN that provided them, and is valid in that PLMN or equivalent PLMN. The operator-defined access category definitions can only be used if the SUPI from the USIM matches the SUPI stored in the non-volatile memory of the ME, else the UE shall delete the operator-defined access category definitions. The maximum number of stored operator-defined access category definitions is UE implementation dependent.
Each network-assigned UE radio capability ID is stored together with a PLMN identity of the PLMN that provided it as well as a mapping to the corresponding UE radio configuration, and is valid in that PLMN. A network-assigned UE radio capability ID can only be used if the SUPI from the USIM matches the SUPI stored in the non-volatile memory of the ME, else the UE shall delete the network-assigned UE radio capability ID. The UE shall be able to store at least the last 16 received network-assigned UE radio capability IDs. There shall be only one network-assigned UE radio capability ID stored for a given combination of PLMN identity and UE radio configuration and any existing UE radio capability ID shall be deleted when a new UE radio capability ID is added for the same combination of PLMN identity and UE radio configuration. If the UE receives a network-assigned UE radio capability ID with a Version ID value different from the value included in the network-assigned UE radio capability ID(s) stored at the UE for the serving PLMN, the UE may delete these stored network-assigned UE radio capability ID(s).
The allowed NSSAI(s) can be stored in a non-volatile memory in the ME together with the SUPI from the USIM. Allowed NSSAI consists of S-NSSAI(s) stored together with a PLMN identity, if it is associated with a PLMN. If the allowed NSSAI is stored, then the UE shall store the S-NSSAI(s) of the HPLMN. If the UE is in the VPLMN, the UE shall also store the allowed NSSAI for the serving PLMN and any necessary mapping of the allowed NSSAI for the serving PLMN to the S-NSSAI(s) of the HPLMN. The allowed NSSAI(s) can only be used if the SUPI from the USIM matches the SUPI stored in the non-volatile memory of the ME; else the UE shall delete the allowed NSSAI(s).
If the UE is registered for emergency services, the UE shall not store the 5GMM parameters described in this Annex on the USIM or in non-volatile memory. Instead the UE shall temporarily store these parameters locally in the ME and the UE shall delete these parameters when the UE is deregistered.
If the UE is configured for eCall only mode as specified in TS 31.102, the UE shall not store the 5GMM parameters described in this Annex on the USIM or in non-volatile memory. Instead the UE shall temporarily store these parameters locally in the ME and the UE shall delete these parameters when the UE enters 5GMM-DEREGISTERED.eCALL-INACTIVE state, the UE is switched-off or the USIM is removed.
The "CAG information list" can only be used if the SUPI from the USIM matches the SUPI stored in the non-volatile memory of the ME; else the UE shall delete the "CAG information list".
If the UE receives the steering of roaming information over N1 NAS signalling containing the SOR-CMCI, and the Store the SOR-CMCI in the ME indicator is set to "Store SOR-CMCI in ME", then:
  • if the length of the SOR-CMCI contents field is not equal to zero, the UE shall store the received SOR-CMCI in the ME's non-volatile memory; or
  • if the length of the received SOR-CMCI contents field is equal to zero, the UE shall delete the stored SOR-CMCI in the ME's non- volatile memory, if any.
The ME shall not delete the SOR-CMCI when the UE is switched off. The ME shall delete the SOR-CMCI when a new USIM is inserted.
Up

C.2  Storage of 5GMM information for UEs operating in SNPN access operation mode |R16|Word‑p. 843

The 5GMM information for UEs operating in SNPN access operation mode are stored according to the following conditions:
  • if the UE does not support access to an SNPN using credentials from a credentials holder, the following 5GMM parameters shall be stored per subscribed SNPN in a non-volatile memory in the ME together with the subscriber identifier associated with the SNPN identity of the SNPN in the "list of subscriber data" configured in the ME (see TS 23.122);and
  • if the UE supports access to an SNPN using credentials from a credentials holder, the following 5GMM parameters shall be stored in a non-volatile memory in the ME per:
    1. the subscribed SNPN together with the subscriber identifier associated with the selected entry in the "list of subscriber data" configured in the ME (see TS 23.122); or
    2. the PLMN subscription together with the SUPI from the USIM which is associated with the PLMN subscription:
      1. 5G-GUTI;
      2. last visited registered TAI;
      3. 5GS update status;
      4. 5G NAS security context parameters from a full native 5G NAS security context (see TS 33.501);
      5. KAUSF and KSEAF (see TS 33.501);
      6. UE parameter update counter (see subclause 9.11.3.53A);
      7. configured NSSAI(s);
      8. NSSAI inclusion mode(s);
      9. MPS indicator;
      10. MCS indicator;
      11. operator-defined access category definitions;
      12. network-assigned UE radio capability IDs; and
      13. signalled URSP (see TS 24.526).
If the 5GMM parameters are associated with the PLMN subscription, then the 5GMM parameters can only be used if the SUPI from the USIM which is associated with the selected PLMN subscription matches the SUPI stored in the non-volatile memory; else the UE shall delete the 5GMM parameters.
If the 5GMM parameters are associated with the subscribed SNPN of the entry in the "list of subscriber data", then the 5GMM parameters can only be used if the subscriber identifier of the selected entry of the "list of subscriber data" matches the subscriber identifier stored in the non-volatile memory.
Each configured NSSAI consists of S-NSSAI(s) stored together with an SNPN identity, if it is associated with an SNPN.
Each NSSAI inclusion mode is associated with an SNPN identity and access type.
The MPS indicator is stored together with an SNPN identity of the SNPN that provided it, and is valid in that registered SNPN.
The MCS indicator is stored together with an SNPN identity of the SNPN that provided it, and is valid in that registered SNPN.
Operator-defined access category definitions are stored together with an SNPN identity of the SNPN that provided them, and are valid in that SNPN. The maximum number of stored operator-defined access category definitions is UE implementation dependent.
Each network-assigned UE radio capability ID is stored together with an SNPN identity of the SNPN that provided it as well as a mapping to the corresponding UE radio configuration, and is valid in that SNPN. The UE shall be able to store at least the last 16 received network-assigned UE radio capability IDs. There shall be only one network-assigned UE radio capability ID stored for a given combination of SNPN identity and UE radio configuration and any existing UE radio capability ID shall be deleted when a new UE radio capability ID is added for the same combination of SNPN identity and UE radio configuration. If the UE receives a network-assigned UE radio capability ID with a Version ID value different from the value included in the network-assigned UE radio capability ID(s) stored at the UE for the serving SNPN, the UE may delete these stored network-assigned UE radio capability ID(s).
The allowed NSSAI(s) can be stored in a non-volatile memory in the ME. Allowed NSSAI consists of S-NSSAI(s) stored together with an SNPN identity, if it is associated with an SNPN.
Up

Up   Top   ToC