Tech-invite  3GPPspace  IETFspace
21  22  23  24  25  26  27  28  29  31  32  33  34  35  36  37  38  4‑5x
Top   in Index   Prev   Next

TR 31.822
Study on GBA_U Based APIs

3GPP‑Page  
V18.1.0 (Wzip)  2023/09  15 p.
Rapporteur:
Miss Huo, Weijing
CMDI

full Table of Contents for  TR 31.822  Word version:  18.0.0

Here   Top
1 Scope  2 References  3 Definitions of terms, symbols and abbreviations  4 Key Issues  4.1 Key Issues1: Support for GBA_U_APIs  4.2 Key Issues2: Support for Access Control to GBA_U_APIs  5 Solutions  5.1 Solution1: Classes and Interfaces of GBA_U_APIs  5.2 Solution2: Access Control to GBA_U_APIs  5.3 Solution 3: Access Control to GBA_U_APIs through install parameters  6 Overall Evaluation  6.1 Evaluation criteria  6.2 Solutions evaluations  7 Conclusion  $ Change history 

 

1  Scope  p. 7

The present document studies the GBA_U based APIs.

2  References  p. 7

The following documents contain provisions which, through reference in this text, constitute provisions of the present document.
  • References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific.
  • For a specific reference, subsequent revisions do not apply.
  • For a non-specific reference, the latest version applies. In the case of a reference to a 3GPP document (including a GSM document), a non-specific reference implicitly refers to the latest version of that document in the same Release as the present document.
[1]
TR 21.905: "Vocabulary for 3GPP Specifications".
[2]
TS 33.220: "Generic Authentication Architecture (GAA); Generic bootstrapping architecture".
[3]
TS 31.102: "Characteristics of the Universal Subscriber Identity Module (USIM) application".
[4]
TS 31.130: "(U)SIM Application Programming Interface (API); (U)SIM API for Java™ Card".
[5]
ISO/IEC 18033-3: "2010/AMD1:2021 Information technology - Security techniques - Encryption algorithms - Part 3: Block ciphers - Amendment 1: SM4".
[6]
ISO/IEC 10118-3: "2018 IT Security techniques - Hash-functions - Part 3: Dedicated hash-functions".
[7]
TS 31.116: "Remote APDU Structure for (U)SIM Toolkit applications".
Up

3  Definitions of terms, symbols and abbreviations  p. 7

3.1  Abbreviations  p. 7

For the purposes of the present document, the abbreviations given in TR 21.905 and the following apply. An abbreviation defined in the present document takes precedence over the definition of the same abbreviation, if any, in TR 21.905.
3GPP
3rd Generation Partnership Project
AES
Advanced Encryption Standard
AID
Application Identifier
API
Application Programming Interface
GBA
Generic Bootstrapping Architecture
GBA_U
GBA with UICC-based enhancements
NAF
Network Application Function
SM
ShangMi
Up

4  Key Issues  p. 8

4.1  Key Issues1: Support for GBA_U_APIs  p. 8

Since the Ks_int_NAF is derived from the Long Term Key of the UICC, and the GBA mechanism is highly recognized, the APIs for Ks_int_NAF should be defined, so other applications could use the Ks_int_NAF for security purpose.

4.2  Key Issues2: Support for Access Control to GBA_U_APIs  p. 8

When an application calls GBA_U_APIs, the Ks_int_NAF is required. Since Ks_int_NAF is associated with B-TID and NAF_ID, it is not allowed to use by all of applications. Therefore, access control should be supported to specify the AID that could call GBA_U_APIs with NAF_ID.

5  Solutions  p. 8

5.1  Solution1: Classes and Interfaces of GBA_U_APIs  p. 8

5.1.1  Description  p. 8

5.1.1.1  General  p. 8

5.1.1.2  Class cipher  p. 8

5.1.1.2.1  Algorithm identifier  p. 8
5.1.1.2.2  init  p. 8
5.1.1.2.3  update  p. 9
5.1.1.2.4  doFinal  p. 9

5.1.1.3  Class signature  p. 10

5.1.1.3.1  Algorithm identifier  p. 10
5.1.1.3.2  init  p. 10
5.1.1.3.3  update  p. 10
5.1.1.3.4  sign  p. 10
5.1.1.3.5  verify  p. 11

5.1.2  Solution Evaluation  p. 11

5.2  Solution2: Access Control to GBA_U_APIs  p. 11

5.2.1  Description  p. 11

5.2.2  Solution Evaluation  p. 12

5.3  Solution 3: Access Control to GBA_U_APIs through install parameters  p. 12

5.3.1  Description  p. 12

5.3.2  Solution Evaluation  p. 12

6  Overall Evaluation  p. 12

6.1  Evaluation criteria  p. 12

6.1.1  Overview  p. 12

6.1.2  Key issues addressed  p. 12

6.1.3  Impact on USIM and ISIM  p. 12

6.1.4  Impact on UICC  p. 12

6.1.5  Backward compatibility  p. 13

6.1.6  Impact on core and RAN networks  p. 13

6.2  Solutions evaluations  p. 13

6.2.1  Overview  p. 13

6.2.2  Solution 1  p. 13

6.2.2.1  Key issues addressed  p. 13

6.2.2.2  Impact on USIM and ISIM  p. 13

6.2.2.3  Impact on UICC  p. 13

6.2.2.4  Backward compatibility  p. 13

6.2.2.5  Impact on core and RAN networks  p. 13

6.2.3  Solution 2  p. 13

6.2.3.1  Key issues addressed  p. 13

6.2.3.2  Impact on USIM and ISIM  p. 13

6.2.3.3  Impact on UICC  p. 14

6.2.3.4  Backward compatibility  p. 14

6.2.3.5  Impact on core and RAN networks  p. 14

6.2.4  Solution 3  p. 14

6.2.4.1  Key issues addressed  p. 14

6.2.4.2  Impact on USIM and ISIM  p. 14

6.2.4.3  Impact on UICC  p. 14

6.2.4.4  Backward compatibility  p. 14

6.2.4.5  Impact on core and RAN networks  p. 14

7  Conclusion  p. 14

$  Change history  p. 15

Up   Top