Tech-invite3GPPspecsSIPRFCs
Overview21222324252627282931323334353637384‑5x

Content for  TS 31.102  Word version:  17.1.0

Top   Top   Up   Prev   None
0…   3…   4…   4.2.9…   4.2.17…   4.2.26…   4.2.34…   4.2.44…   4.2.52…   4.2.60…   4.2.68…   4.2.76…   4.2.85…   4.2.93…   4.2.101…   4.2.107…   4.3…   4.4.2…   4.4.2.4…   4.4.3…   4.4.4…   4.4.5…   4.4.6…   4.4.8…   4.4.8.7…   4.4.9…   4.4.11…   4.4.11.7…   4.5…   4.6…   4.7   5…   5.2   5.3   5.4…   5.9…   6…   7…   7.1.2…   7.3…   A   B…   D   E…   G   H…   I…   L…   M…

 

M (Normative)  USIM application dedicated for IOPS |R13|Word‑p. 320

M.1  Introduction

IOPS allows to provide network service to Public Safety users even in the case the network has no or only limited backhaul connectivity. One of the main issues in such cases is the missing backhaul to perform authentication. A solution has been defined by using local HSSs which take over the responsibility for authentication in IOPS mode.
A problem identified for IOPS security when making use of local HSS is the higher probability of a compromise of a local HSS. Therefore the security solution described in TS 33.401 uses a local HSS with different authentication credentials than the standard HSS in normal operation. Additionally there might be several local HSSs and to further reduce the impact of possible compromised local HSSs, each local HSS should use different authentication credentials.
The security solution described in TS 33.401 is based on a USIM application dedicated for IOPS and using derived individual keys per local HSS.
3GPP TS 23.401 Annex K specifies a PLMN identity dedicated for IOPS mode of operation. Additionally a USIM dedicated for IOPS uses an Access Control Class of '11' or '15'.
Up

M.2  Features of the USIM dedicated for IOPS

The USIM dedicated for IOPS may be implemented as a single USIM on a UICC or as a secondary USIM application together with a normal USIM on one UICC. The USIM for IOPS is a regular USIM application and contains all mandatory EFs for a USIM and may also include any of the optional EFs defined for a USIM.
The USIM dedicated for IOPS nevertheless has some specifics:
  • As specified in TS 23.401 Annex K, the Access Control Class in EF ACC is set to either '11' or '15'. The specific values for the Access Control Class prevent UEs with different Access Control Classes from trying to attach to the IOPS network.
  • The entry for the USIM dedicated for IOPS in EFDIR has a label starting with 'USIM-IOPS'.
In case multiple local HSSs are to be supported, The USIM should also support:
  • The AMF (Authentication Management Field) mechanism as described in TS 33.401 Annex F.4.1 is supported.
  • An Operator specific mechanism to derive local HSS individual keys is supported (see TS 33.401 Annex F.4).
Up

M.3  Selection mechanisms

The method for selecting a USIM dedicated for IOPS is left to ME implementation.

N (Normative)  USIM supporting non-IMSI SUPI Type |R16|Word‑p. 321

N.1  Introduction

IMSI based USIM is a USIM Application which is configured with a SUPI of type IMSI (i.e Service No. 130 in the USIM Service Table shall not be "available").
Non-IMSI based USIM is a USIM Application which is configured with a SUPI of type non-IMSI (i.e Service No. 130 in the USIM Service Table shall be "available"). Examples of non-IMSI type are: NSI, GLC and GLI.
Both USIM application types shall use different AID ranges as defined in Annex O of TS 31.101.
Up

N.2  Features of USIM supporting non-IMSI SUPI type

The non-IMSI based USIM may be implemented as a single USIM application on a UICC or as a secondary USIM application together with an IMSI based USIM on one UICC.
The non-IMSI based USIM is a regular USIM application and shall contain all mandatory EFs defined for a USIM application in the present document and may also include any of the optional EFs defined for a USIM application except EF IMSI.
No additional features are supported by Non-IMSI based USIM.
Up

N.3  Application selection procedure

Application selection is performed according to the procedures defined in clause 5.1.1.1. The following provisions apply:
The method for selecting a non-IMSI based USIM is based on the presence of the corresponding application with the associated AID in EFDIR, as defined in the Annex O of TS 31.101.
Up

$  Change historyWord‑p. 322

Up   Top