Transcript USIM requirements and structure NOKIA Mobile Phones TSGT3#3(99)082 © NOKIA

USIM requirements and structure
NOKIA Mobile Phones
TSGT3#3(99)082
© NOKIA
DEFAULT.PPT / 22.08.1997 / AO page: 1
Outline of the presentation
•
The USIM related requirements as (currently) listed by TSG-SA
•
•
•
Browsing through the relevant service requirement documents.
Summary of the identified requirements.
NOKIA's proposal for the USIM application content
•
© NOKIA
A comparison of the GSM and the USIM file structures as agreed at the last
TSG-T3 meeting.
DEFAULT.PPT / 22.08.1997 / AO page: 2
3GPP specifications analysed
•
The following UMTS documents are analysed for USIM requirements:
•
•
•
•
UMTS 22.00 v2.0.0, "UMTS phase 1".
UMTS 22.01 v3.5.0, " Service aspects; Service principles".
UMTS 22.05 v3.1.0, "UMTS services and capabilities".
draft UMTS 22.29 v1.0.0, "Handover between UMTS and GSM or other Radio
systems".
NOTE: All these documents have been presented for TSG-SA and will be used as base
line for the UMTS standard.
© NOKIA
DEFAULT.PPT / 22.08.1997 / AO page: 3
22.00 v2.0.0
9
USIM
In the first phase of UMTS, the USIM shall be developed on the basis of the phase 2+ release 99 GSM
SIM. The additional requirements for the phase 1 UMTS USIM are as follows :
1) USIM shall provide new and enhanced security features (e.g. mutual authentication...) as defined by
SMG10.
2) The UMTS mobile terminal shall support phase 2 and phase 2+ GSM SIMs as access modules to
UMTS networks. The services that can be provided in this case may be limited to GSM like services
provided by that UMTS network. UMTS mobile terminals shall not support 5V SIMs. It shall be up
to the UMTS network operator to accept or reject the use of GSM SIM as access modules in its
network.
3) It shall be possible to have multiple applications on the UMTS IC Card (UICC). There shall be a
secured and easy mechanism for application selection. An authorised access for each application is
mandatory, however it shall be possible to have shared directories between applications where
appropriate. The UICC shall be capable of supporting SIM and USIM applications.
4) Simultaneous activation of several USIMs on one mobile terminal need not be supported in UMTS
phase 1.
5) A standardised mechanism allowing highly secure transfer of applications and/or associated data
to/from the UICC shall be supported in UMTS phase 1.
NOTE: There are NO requirements here indicating that a GSM terminal shall
be able to support a UICC+SIM, or UICC+USIM or UICC+SIM+USIM!
© NOKIA
DEFAULT.PPT / 22.08.1997 / AO page: 4
22.01 v3.5.0
•
Ch. 9.2: "(For UMTS Phase 1) It is required that is shall be possible to identify UMTS
users using GSM identities, namely IMSI, MSISDN and possibly TMSI and IMEI."
•
•
Ch. 9.5:"It shall be possible for several numbers to be associated with a single
subscription on a single UICC."
•
•
Conclusion: the GSM identities may be reused!
Comment: One IMSI many MSISDN's.
Ch. is devoted to USIM issues.
© NOKIA
DEFAULT.PPT / 22.08.1997 / AO page: 5
22.01 v3.5.0
•
Ch. 11.1.1:
•
Every USIM shall have a unique identity and shall be associated with one and
only one home environment.
•
It shall be possible for a home environment to uniquely identify a user by the
USIM.
•
The USIM shall be used to provide security features.
•
For access to UMTS services, provided via a UMTS home environment, a valid
USIM shall be required.
•
The USIM shall reside on a UICC, UMTS shall adopt both of the GSM SIM card
physical formats. New UMTS terminals may require other formats also. USIM
specific information shall be protected against unauthorised access or alteration.
•
It shall be possible to update USIM specific information via the air interface, in a
secure manner.
© NOKIA
DEFAULT.PPT / 22.08.1997 / AO page: 6
22.01 v3.5.0
•
•
11.1.2:
•
it shall be possible to have one or more user profiles associated with a number
(should this be per subscription?)
•
•
the profiles should be controlled by e.g. a PIN mechanism.
11.1.3:
•
•
•
Each profile shall have it's own address (e.g. IMUN).
In Phase 1 it is only required to support one USIM application on the UICC.
The standard shall not prevent that two USIM applications from different home
environments reside on the same UICC.
11.2:
•
The physical aspects of the UICC will be handled outside the UMTS
specification.
•
The UICC shall support access to services via GSM and UMTS.
© NOKIA
DEFAULT.PPT / 22.08.1997 / AO page: 7
22.01 v3.5.0
•
•
11.2.1 The UMTS UICC and Applications other than the USIM:
•
•
•
•
Other applications than the USIM shall be able to reside on the UICC
•
•
Applications may share information such as a common address book.
each application. may require it's own security mechanisms.
Applications shall reside in their own logical/physical domain.
Applications shall be separate, I.e. some kind of firewall mechanism shall exist
between applications.
Address applications over the air.
11.2 Terminals and Multiple UICCs
•
© NOKIA
The standard shall support multiple UICCs (in phase 2).
DEFAULT.PPT / 22.08.1997 / AO page: 8
22.01 v3.5.0
•
•
14 Evolution.
•
"UMTS shall provide some mechanisms which permit pre UMTS users to roam
easily onto UMTS and access the services. See Figure 5 for clarification.
•
UMTS shall provide some mechanisms which permit UMTS users to roam easily
onto pre-UMTS systems and access the services."
17 Handover:
•
"It shall be possible for users to be handed over between UMTS networks
operated by different operators subject to appropriate roaming/commercial
agreements. Handover between networks operated by different network
operators is not required for UMTS phase 1."
•
"Handover between UMTS and GSM systems (in both directions) is required,
even if this requires changes to GSM specifications. In addition, a generic
solution may be implemented in UMTS which allows calls to be handed over
between UMTS and other pre-UMTS systems in both directions. For UMTS
phase 1, handover between UMTS and GSM networks operated by different
network operators is not required."
© NOKIA
DEFAULT.PPT / 22.08.1997 / AO page: 9
22.05 v3.1.0
•
9.2 Execution environment:
•
© NOKIA
The execution environment requires SAT.
DEFAULT.PPT / 22.08.1997 / AO page: 10
22.29 v1.0.0,
Handover Matrix
The handover matrix
handover
possible?
to UMTS
to GSM-cs
to GSM-GPRS
to IMT2000 
UMTS
from UMTS
1
1
1
x
from GSM-cs
1
oos
oos
oos
from GSM-GPRS
1
oos
oos
oos
from IMT2000 
UMTS
x
oos
oos
oos
oos = out of scope of UMTS specifications
1= supporting standards required for UMTS phase 1
x= supporting standards required, not necessarily for phase 1
© NOKIA
DEFAULT.PPT / 22.08.1997 / AO page: 11
22.29 v1.0.0,
Security Matrix
The security matrix indicates the security level after handing over
which security
level?
To UMTS
to GSM-cs
to GSM-GPRS
to IMT2000 
UMTS
from UMTS
U
G
G
*)
from GSM-cs
U or G1
oos
oos
oos
from GSM-GPRS
U or G1
oos
oos
oos
from IMT2000 
UMTS
U
oos
oos
oos
U: UMTS Security Level.
G: GSM security Level
oos: out of scope of this document
1) U is not envisaged for phase 1 or intra-operator handover
*) security level of specific IMT2000 family member
© NOKIA
DEFAULT.PPT / 22.08.1997 / AO page: 12
22.29 v1.0.0,
Roaming Matrix
The roaming matrix
roaming possible?
to UMTS
to GSM-cs
to GSM-GPRS
to IMT2000 
UMTS
from UMTS
1
1
1
1
from GSM-cs
1
oos
oos
oos
from GSM-GPRS
1
Oos
oos
oos
from IMT2000 
UMTS
x
Oos
oos
oos
oos = out of scope this specification
1 = standardisation of this capability is required for UMTS phase 1
x = standardisation of this capability if required, but not necessarily for UMTS phase 1
© NOKIA
DEFAULT.PPT / 22.08.1997 / AO page: 13
Summary
key UMTS phase 1 USIM-UICC features
•
USIM
•
•
•
•
•
•
•
GSM SIM ph2+ can be used to get UMTS service.
The GSM identities IMSI, MSISDN and possibly TMSI and IMEI.
The USIM shall support multiple user profiles.
Pre-UMTS users shall be able to roam in UMTS networks.
UMTS users shall be able to roam into GSM networks.
Handover between GSM and UMTS shall be supported (for ph1 only intra PLMN
handover is required).
UICC
•
•
© NOKIA
The UICC shall be able to host GSM SIM applications
The UICC shall support multiple applications (telecom and other e.g. banking).
DEFAULT.PPT / 22.08.1997 / AO page: 14
NOKIA’s proposal for the USIM application
NOKIA proposes that a separate application under control of 3GPP is created. For phase 1 it
will be assigned a special file id e.g. ‘7FXX’ and will reside directly under the MF but for later
phases the multi-USIM issue must be handled
MF
Master File
'7F20'
EF-DIR
'2F00'
DF-TELECOM
Type title here
'7F10'
© NOKIA
DEFAULT.PPT / 22.08.1997 / AO page: 15
DF-USIM
USIM APPL.
'7FXX'
DF-BANK
BANK-APPL.
'QXYZ'
BASIC USIM/UICC FUNCTIONALLITY
•
This USIM application will have the following main features:
 Provide access to UMTS systems including security and confidentiality.
 Provide access to GSM systems – by providing Ki, A8/3, A5 and other mandatory
GSM features.
 Provide means to enable handover between GSM and UMTS systems (in phase
1 only intra-PLMN handover will be supported).
•
For the card (UICC) the following is proposed:
 It will have a DIR file that is a collection of application templates containing an
AID, an application name and a path to the application.
 A GSM application (under 7F20) can coexist with a USIM application on the
same card – it is proposed that the two applications can not belong to the same
operator, i.e. they are independent.
© NOKIA
DEFAULT.PPT / 22.08.1997 / AO page: 16
USIM questions
Q Why create a USIM application with the listed functionality?
A
The main reason for creating a USIM application is to create a 3GPP context and to
prepare for later phases were multiple USIM applications may reside on the same
card which will incur the need to separate all functionality belonging to a specific
subscription (operator) in a separate application.
Consider the alternative scenario:
•
For every system an operator has a license to there will be an application!
•
This would imply that an operator with GSM and UMTS licenses has two
applications.
Q What happens when cards containing multiple USIM’s emerges – should only the
first operator with licenses to both systems get a GSM application, i.e. who owns
‘7F20’?
Conclusion: Therefore the complete functionality should be
located in a separate application.
© NOKIA
DEFAULT.PPT / 22.08.1997 / AO page: 17
GSM SIM application
MF
'3F00'
DF-GSM
'7F20'
DF-TELECOM
'7F10'
EF-ICCID
'2FE2'
DF-IS41
'7F22'
EF-ELP
'2F05'
DF-GRAPHICS
'5F50'
EF-ADN
'6F3A'
DF-IMG
'4F20'
EF-SMSR
'6F47'
EF-LP
'6F05'
EF-PUCT
'6F41'
EF-VGCS
'6FB1'
DF-Iridium
'5F30'
© NOKIA
EF-IMSI
'6F07'
EF-CBMII
'6F45'
EF-VGBSS
'6FB2'
EF-Kc
'6F20'
EF-SPN
'6F46'
EF-VBS
'6FB3'
DF-Globst
'5F31'
EF-PLMNsel
'6F30'
EF-CBMID
'6F48'
EF-VBSS
'6FB4'
DF-ICO
'5F32'
DEFAULT.PPT / 22.08.1997 / AO page: 18
EF-HPLMN
'6F31'
EF-BCCH
'6F74'
EF-eMLPP
'6FB5'
EF-FDN
'6F3B'
EF-SDN
'6F49'
EF-ACMmax
'6F37'
EF-ACC
'6F78'
EF-AAeM
'6FB6'
DF-ACeS
'5F33'
EF-SMS
'6F3C'
EF-EXT1
'6F4A'
EF-SST
'6F38'
EF-FPLMN
'6F7B'
EF-ECC
'6FB7'
DF-PCS1900
'5F40'
EF-CCP
'6F3D'
EF-EXT2
'6F4B'
EF-MSISDN
'6F40'
EF-EXT3
'6F4C'
EF-ACM
'6F39'
EF-GID1
'6F3E'
EF-LOCI
'6F7E'
EF-AD
'6FAD'
EF-CBMIR
'6F50'
EF-NIA
'6F51'
EF-SMSP
'6F42'
EF-BDN
'6F4D'
EF-SMSS
'6F43'
EF-LND
'6F44'
EF-EXT4
'6F4E'
EF-GID
'6F3F'
EF-PHASE
'6FAE'
EF-KcGPRS
'6F52'
EF-CNI
'6F32'
EF-LOCIGPRS
'6F53'
EF-DCK
'6F2C'
UICC and USIM layout
MF
'3F00'
DF-USIM
'XXXX'
DF-TELECOM
'7F10'
EF-DIR
'2F00'
EF-ICCID
'2FE2'
EF-ELP
'2F05'
DF-IS41
'7F22'
DF-GRAPHICS
'5F50'
EF-ADN
'6F3A' GU
DF-IMG
'4F20'
EF-IMSI
'6F07' GU
EF-PUCT
'6F41' GU?
EF-ECC
'6FB7' GU
EF-SDN
'6F49' GU
EF-Kc
'6F20' GU
EF-CBMII
'6F45' GU?
EF-CBMIR
'6F50' GU
EF-EXT3
'6F4C' GU
EF-PLMNsel
'6F30' GU
EF-SPN
'6F46' ?
EF-KcGPRS
'6F52' GU
EF-HPLMN
'6F31' GU
EF-ACMmax
'6F37' GU?
EF-CBMID
'6F48' GU?
EFLOCIGPRS
'6F53' GU
EF-ACC
'6F78' GU
EF-FDN
'6F3B' GU
EF-EXT1
'6F4A' GU
EF-SST
'6F38' GU
EF-FPLMN
'6F7B' GU
EF-EXT2
'6F4B' GU
EF-CCP
'6F3D' GU
EF-ACM
'6F39' GU?
EF-LOCI
'6F7E' GU
EF-SMS
'6F3C' GU
EF-GID1
'6F3E' GU
EF-GID
'6F3F' GU
EF-AD
'6FAD' GU
EF-PHASE
'6FAE' GU
EF-SMSR
'6F47' GU
EF-SMSP
'6F42' GU
EF-LND
'6F44' GU
EF-DCK
'6F2C' GU
EF-SMSS
'6F43' GU
EF-CNI
'6F32' GU
EF-MSISDN
'6F40' GU
EF-CCP
'6F3D' GU
DF-GRAPHICS
'5F50'
DF-Iridium
'5F30'
© NOKIA
DF-Globst
'5F31'
DF-ICO
'5F32'
DEFAULT.PPT / 22.08.1997 / AO page: 19
DF-ACeS
'5F33'
DF-PCS1900
'5F40'
DF-IMG
'4F20'
Abbreviations:
GU:
The file exists in GSM and w ill be used in UMTS but may be modified.
GU?:
Is used in GSM (optional) but w hether ot w ill be used in UMTS is FFS.
?:
Undecided