USIM requirements and structure

1
USIM requirements and structure

• NOKIA Mobile Phones
• TSGT33(99)082

2
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
• A comparison of the GSM and the USIM file
  structures as agreed at the last TSG-T3 meeting.

3
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.

4
22.00 v2.0.0
5
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."
• Conclusion the GSM identities may be reused!
• Ch. 9.5"It shall be possible for several numbers
  to be associated with a single subscription on a
  single UICC."
• Comment One IMSI many MSISDN's.
• Ch. is devoted to USIM issues.

6
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.

7
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.
• Each profile shall have it's own address (e.g.
  IMUN).
• 11.1.3
• 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.

8
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
• 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.
• Applications may share information such as a
  common address book.
• Address applications over the air.
• 11.2 Terminals and Multiple UICCs
• The standard shall support multiple UICCs (in
  phase 2).

9
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."

10
22.05 v3.1.0

• 9.2 Execution environment
• The execution environment requires SAT.

11
22.29 v1.0.0, Handover Matrix
12
22.29 v1.0.0, Security Matrix
13
22.29 v1.0.0, Roaming Matrix
14
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
• The UICC shall be able to host GSM SIM
  applications
• The UICC shall support multiple applications
  (telecom and other e.g. banking).

15
NOKIAs 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

16
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.

17
USIM questions

• Why create a USIM application with the listed
  functionality?
• 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.
• What happens when cards containing multiple
  USIMs 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.

18
GSM SIM application
19
UICC and USIM layout