School of Specs 24.501v20.0.0

3GPP 24.501 v20.0.0 — the document's own text

C.2 Storage of 5GMM information for UEs operating in SNPN access operation mode

Taught in 5. Finding your way around TS 24.501 (CT1 — the group that writes what your phone says, in depth), 4. Inside TS 24.501, the document at the centre (CT1 — the group that writes what your phone says, overview).

The 5GMM information for UEs operating in SNPN access operation mode and not registering or registered for the onboarding service in SNPN are stored according to the following conditions:

  • if the UE does not support access to an SNPN using credentials from a credentials holder and equivalent SNPNs, 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 3GPP TS 23.122 [5]) or with the SUPI from the USIM if no subscriber identifier is configured in the entry of the "list of subscriber data" associated with the SNPN identity and the UE has a valid USIM;and
  • if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, the following 5GMM parameters shall be stored in a non-volatile memory in the ME per:
    • the subscribed SNPN together with the subscriber identifier associated with the selected entry in the "list of subscriber data" configured in the ME (see 3GPP TS 23.122 [5]) or with the SUPI from the USIM if no subscriber identifier is configured in the selected entry of the "list of subscriber data" configured in the ME and the UE has a valid USIM; or
    • if the UE supports access to an SNPN using credentials from a credentials holder, the PLMN subscription together with the SUPI from the USIM which is associated with the PLMN subscription:
  • 5G-GUTI;

a1) NID of the registered SNPN;

  • last visited registered TAI;
  • 5GS update status;
  • 5G NAS security context parameters from a full native 5G NAS security context (see 3GPP TS 33.501 [24]);
  • KAUSF and KSEAF (see 3GPP TS 33.501 [24]);
  • UE parameter update counter (see clause 9.11.3.53A);
  • configured NSSAI(s);

g1) NSSRG information;

g2) S-NSSAI time validity information;

g3) S-NSSAI location validity information;

g4) on-demand NSSAI;

  • NSSAI inclusion mode(s);
  • MPS indicator;
  • MCS indicator;
  • operator-defined access category definitions;
  • network-assigned UE radio capability IDs;
  • zero or more instances of signalled URSP (see 3GPP TS 24.526 [19]), each associated with a non-subscribed SNPN or, the subscribed SNPN, which provided the URSP and, for each URSP rule of the signalled URSP, a UPSI of a UE policy section in which the URSP rule was received;

m1) zero or more instances of pre-configured URSP rules (see 3GPP TS 24.526 [19]), each associated with the subscribed SNPN or the HPLMN, which provided the URSP;

  • optionally a non-subscribed SNPN signalled URSP handling indication indicating whether the UE is allowed to accept URSP signalled by non-subscribed SNPNs;
  • "permanently forbidden SNPNs" list;

o1) "permanently forbidden SNPNs for access for localized services in SNPN" list;

  • "temporarily forbidden SNPNs" list;

p1) "temporarily forbidden SNPNs for access for localized services in SNPN" list;

  • SOR counter (see clause 9.11.3.51);
  • SOR-CMCI;
  • optionally, the SNPN selection parameters associated with the PLMN subscription (see 3GPP TS 23.122 [5] clause 4.9.3.0); and
  • signalled ProSeP (see 3GPP TS 24.555 [19F]) and, for each ProSeP info (see clause 5.2 of 3GPP TS 24.554 [19F]) of the signalled ProSeP, a UPSI of a UE policy section in which the ProSeP info of the signalled ProSeP was received.

The 5GMM information for UEs operating in SNPN access operation mode and registering or registered for the onboarding service in SNPN are stored as follows:

  • 5G-GUTI;
  • last visited registered TAI;
  • 5GS update status;
  • 5G NAS security context parameters from a full native 5G NAS security context (see 3GPP TS 33.501 [24]);
  • KAUSF and KSEAF (see 3GPP TS 33.501 [24]);
  • UE parameter update counter (see clause 9.11.3.53A);
  • network-assigned UE radio capability IDs;
  • "permanently forbidden SNPNs for onboarding services in SNPN" list; and
  • "temporarily forbidden SNPNs for onboarding services in SNPN" list.

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, equivalent SNPNs or both, the following 5GMM parameters should 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 3GPP TS 23.122 [5]) or with the SUPI from the USIM if no subscriber identifier is configured in the entry of the "list of subscriber data" associated with the SNPN identity and the UE has a valid USIM; and
  • if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, the following 5GMM parameters should be stored in a non-volatile memory in the ME per:
    • the subscribed SNPN together with the subscriber identifier associated with the selected entry in the "list of subscriber data" configured in the ME (see 3GPP TS 23.122 [5]) or with the SUPI from the USIM if no subscriber identifier is configured in the selected entry of the "list of subscriber data" configured in the ME and the UE has a valid USIM; or
    • if the UE supports access to an SNPN using credentials from a credentials holder, the PLMN subscription together with the SUPI from the USIM which is associated with the PLMN subscription:
      • allowed NSSAI(s).

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, equivalent SNPNs or both, the following 5GMM parameters may 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 3GPP TS 23.122 [5]) or with the SUPI from the USIM if no subscriber identifier is configured in the entry of the "list of subscriber data" associated with the SNPN identity and the UE has a valid USIM; and
  • if the UE supports access to an SNPN using credentials from a credentials holder, equivalent SNPNs or both, the following 5GMM parameters may be stored in a non-volatile memory in the ME per:
    • the subscribed SNPN together with the subscriber identifier associated with the selected entry in the "list of subscriber data" configured in the ME (see 3GPP TS 23.122 [5]) or with the SUPI from the USIM if no subscriber identifier is configured in the selected entry of the "list of subscriber data" configured in the ME and the UE has a valid USIM; or
    • if the UE supports access to an SNPN using credentials from a credentials holder, the PLMN subscription together with the SUPI from the USIM which is associated with the PLMN subscription:
      • the N3AN node configuration information of subscribed SNPN signalled ANDSP (see 3GPP TS 24.526 [19]) and a UPSI of a UE policy section in which the N3AN node configuration information of subscribed SNPN signalled ANDSP was received.

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 or if the subscriber identifier from the USIM matches the subscriber identifier stored in the non volatile memory, no subscriber identifier is configured in the selected entry of the "list of subscriber data" configured in the ME and the UE has a valid USIM.

Each configured NSSAI consists of S-NSSAI(s) stored together with an SNPN identity, if it is associated with an SNPN. A configured NSSAI may be associated with NSSRG information, S-NSSAI time validity information, S-NSSAI location validity information, NSAG information and on-demand NSSAI.

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 or equivalent SNPN.

The MCS indicator is stored together with an SNPN identity of the SNPN that provided it, and is valid in that registered SNPN or equivalent 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 or equivalent 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 handling of the SOR-CMCI stored in the non-volatile memory in the ME is specified in 3GPP TS 23.122 [5].

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.

The partially allowed NSSAI(s) can be stored as allowed NSSAI(s) in a non-volatile memory in the ME. Partially allowed NSSAI consists of S-NSSAI(s) and a list of TAs for which the S-NSSAI is allowed, stored together with an SNPN identity, if it is associated with an SNPN.