© NOKIADEFAULT.PPT / 22.08.1997 / AO page: 1 USIM requirements and structure NOKIA Mobile Phones TSGT3#3(99)082.

Slides:



Advertisements
Similar presentations
Doc.: IEEE /087 Submission May, 2000 Steven Gray, NOKIA Jyri Rinnemaa, Jouni Mikkonen Nokia Slide 1.
Advertisements

XXX IEEE MEDIA INDEPENDENT HANDOVER DCN: XXX Title: MRPM – an augmenting feature for MIH Date Submitted: July 15,
GSM Security and Encryption
GSM Network. GSM-Introduction Architecture Technical Specifications Frame Structure Channels Security Characteristics and features Applications Contents.
Company Confidential 1 © 2005 Nokia V1-Filename.ppt / yyyy-mm-dd / Initials Pre-Shared Key TLS with GBA support Thesis presentation ESPOO, Finland.
Access Control Intro, DAC and MAC System Security.
6 The IP Multimedia Subsystem Selected Topics in Information Security – Bazara Barry.
Federated Authentication mechanism for mobile services Dasun Weerasinghe, Saritha Arunkumar, M Rajarajan, Veselin Rakocevic Mobile Networks Research Group.
Doc.: IEEE /0408r0 Submission March 2004 Colin Blanchard, BTSlide 1 3GPP WLAN Interworking Security Colin Blanchard British Telecommunications.
SMUCSE 5349/7349 GSM Security. SMUCSE 5349/7349 GSM Security Provisions Anonymity Authentication Signaling protection User data protection.
UPnP AV Architectural Multimedia System with a Home Gateway Powered by the OSGi Platform Manuscript received January 15, 2005 Reporter: Sy-Han Wang.
MOBILE PHONE ARCHITECTURE & TECHNOLOGY. HISTORY  The idea of the first cellular network was brainstormed in 1947  Disadvantages  All the analogue system.
Summary of 3GPP TR GPP2 TSG-S WG4 S Source: Qualcomm Incorporated Contact(s): Anand Palanigounder,
Effectively Integrating Information Technology (IT) Security into the Acquisition Process Section 5: Security Controls.
© 2011 Open Mobile Alliance Ltd. All Rights Reserved. Used with the permission of the Open Mobile Alliance Ltd. under the terms as stated in this document.
Cdma2000 Card Environments and Provisioning Doug Dunn TSG-C WG 1 Chair
GSM: The European Standard for Mobile Telephony Presented by Rattan Muradia Requirement for course CSI 5171 Presented by Rattan Muradia Requirement for.
22-23 June 2004TISPAN-3GPP Workshop - Sophia-Antipolis 1 Joint 3GPP & TISPAN Workshop on NGN-IMS - NGN-IMS issues handling - Alain Le Roux (France Telecom),
5.1 © 2004 Pearson Education, Inc. Lesson 5: Administering User Accounts Exam Microsoft® Windows® 2000 Directory Services Infrastructure Goals 
Mechanism to support establishment of charging policies Group Name: WG2-ARC Source: InterDigital Meeting Date: TP8 Agenda Item:
© Alcatel-Lucent | M2M Numbering | April 12, GPP2 M2M TITLE Numbering in 3GPP2 for M2MSOURCE Mike Dolan, Alcatel-Lucent, Mike.
EU Regulation for Intercommunication And Roaming Lasse Rautopuro Helsinki University of Technology
An Operators Input for oneM2M Baseline  Group name: TP#2/WG1  Source: DTAG, Vodafone Group  Meeting Date:  Agenda Item: WG1 agenda item.
4G-MOBILE COMMUNICATION D.MANOJ KUMAR III. B.Tech, E.C.E N.B.K.R.Institue of Science and technology P.PALLAVI II. B.Tech, E.C.E Kakatiya Institue of Technology.
Identities and Network Access Identifier in M2M Page 1 © GPP2 3GPP2 and its Organizational Partners claim copyright in this document and individual.
2003/12/291 Security Aspects of 3G-WLAN Interworking 組別: 2 組員: 陳俊文 , 李奇勇 , 黃弘光 , 林柏均
Chapter 4 Application Level Security in Cellular Networks.
Third TETRA World Congress A Report on ‘TETRA Release 2’ Brian Oliver Chairman, ETSI Project TETRA.
1 Issues Degree to which standardisation is needed for IMS services, like for example video conferencing? Same service across different terminals Terminal.
CP-a Emergency call stage 2 requirements - A presentation of the requirements from 3GPP TS Keith Drage.
Ericsson, ALLIP Features control at Home or at the Visited Systems.
Heidelberg, 25 February 1999 MTM’99 Workshop Terminal and Application Aspects of the Evolution of Broadband Mobile Services EURESCOM P809 Mobility in.
21-05-xxxx IEEE MEDIA INDEPENDENT HANDOVER DCN: xxxx Title: LB #1b Comment Summary Date Submitted: March, 2007 Presented at.
Doc.: IEEE /209r0 Submission 1 March GPP SA2Slide 1 3GPP System – WLAN Interworking Principles and Status From 3GPP SA2 Presented.
SIM application
Report to S1 on: ad-hoc on Handover and Cell Selection (Sophia Antipolis, 9/10 June 99) David Cooper, GPP TSG-S1XXX (99)492 Quebec 6-9 July 1999Agenda:
September 28, 2006 Page 1 3GPP2 MMD Status for IMS Workshop Jack Nasielski
Update on ETSI Security work Charles Brookson OCG Security Chairman DOCUMENT #:GSC13-PLEN-57 FOR:Information SOURCE:Charles Brookson AGENDA ITEM:6.3
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: IEEE d base ideas and prototype implementation Date Submitted: Presented at.
November 2001 Lars Falk, TeliaSlide 1 doc.: IEEE /617r1 Submission Status of 3G Interworking Lars Falk, Telia.
NETLMM Applicability Draft (Summary) 28 Sep
MIKEY-IBAKE and LI Requirements. All Rights Reserved © 2010 Alcatel-Lucent Page 2 | Introduction 3GPP TSG-SA WG3-LI adopted requirements for LI relating.
IEEE MEDIA INDEPENDENT HANDOVER DCN: Title: Proposed Presentation for 3GPP Date Submitted: September,
Mobile Phone Forensics Michael Jones. Overview Mobile phones in crime The mobile phone system Components of a mobile phone The challenge of forensics.
多媒體網路安全實驗室 A Secure Privacy-Preserving Roaming Protocol Based on Hierarchical Identity-Based Encryption for mobile Networks 作者 :Zhiguo Wan,Kui Ren,Bart.
GPRS General Packet Radio Service Shay Toder – Ori Matalon The Department of Communication System Engineering Ben-Gurion University June 19, 2002.
Doc.: IEEE /0085r1 Submission June 2010 Tuncer Baykas, NICTSlide TG1 and System Design Document Notice: This document has been prepared.
3GPP TSG RAN WG2 meeting #92 Nanjing, China 23-27, May 2016 R
1 Wireless Networks Lecture 17 GPRS: General Packet Radio Service (Part I) Dr. Ghalib A. Shah.
Overview of the GSM for Cellular System
Wireless Network PMIT- By-
TSG-RAN Workshop on Radio mobility MOB
NETLMM Applicability Draft (Summary)
5G Architecture Standardization Landscape in 3GPP
Proposal for IEEE solution
IEEE MEDIA INDEPENDENT HANDOVER
WIEN Study Group Proposed Roadmap
IEEE MEDIA INDEPENDENT HANDOVER
IEEE MEDIA INDEPENDENT HANDOVER DCN: xxx
IEEE MEDIA INDEPENDENT HANDOVER DCN:
AAA: A Survey and a Policy- Based Architecture and Framework
FPLMN: A detailed Explanation | UPLMN, OPLMN, HPLMN, VPLMN, EPLMN, IPLMN FPLMN: What is FPLMN? | A detailed Explanation | Forensic SIM Analysis Author.
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER DCN:
TG1 and System Design Document
Requirements Date: Authors: March 2010 Month Year
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER DCN:
IEEE MEDIA INDEPENDENT HANDOVER DCN:
LM 7. Cellular Network Security
Presentation transcript:

© NOKIADEFAULT.PPT / / AO page: 1 USIM requirements and structure NOKIA Mobile Phones TSGT3#3(99)082

© NOKIADEFAULT.PPT / / AO page: 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.

© NOKIADEFAULT.PPT / / AO page: 3 3GPP specifications analysed The following UMTS documents are analysed for USIM requirements: UMTS v2.0.0, "UMTS phase 1". UMTS v3.5.0, " Service aspects; Service principles". UMTS v3.1.0, "UMTS services and capabilities". draft UMTS 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.

© NOKIADEFAULT.PPT / / AO page: v2.0.0

© NOKIADEFAULT.PPT / / AO page: 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.

© NOKIADEFAULT.PPT / / AO page: v3.5.0 Ch : 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.

© NOKIADEFAULT.PPT / / AO page: v : 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) : 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.

© NOKIADEFAULT.PPT / / AO page: v 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 Terminals and Multiple UICCs The standard shall support multiple UICCs (in phase 2).

© NOKIADEFAULT.PPT / / AO page: v 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."

© NOKIADEFAULT.PPT / / AO page: v Execution environment: The execution environment requires SAT.

© NOKIADEFAULT.PPT / / AO page: v1.0.0, Handover Matrix

© NOKIADEFAULT.PPT / / AO page: v1.0.0, Security Matrix

© NOKIADEFAULT.PPT / / AO page: v1.0.0, Roaming Matrix

© NOKIADEFAULT.PPT / / AO page: 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).

© NOKIADEFAULT.PPT / / AO page: 15 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

© NOKIADEFAULT.PPT / / AO page: 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.

© NOKIADEFAULT.PPT / / AO page: 17 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.

© NOKIADEFAULT.PPT / / AO page: 18 GSM SIM application

© NOKIADEFAULT.PPT / / AO page: 19 UICC and USIM layout