TTSL Specification for Subscriber Identity Module_v1.3

1

Subscriber Identity Module Specification

Version 1.3

27th Aug, 2009

Tata Teleservices Limited

Document CTT/Specs/GSM/SIM

Revision Version 1.3 Subscriber Identity Module SpecificationsSIM Specs

SIM Specs Author CTT

Corporate Terminal Team Date 27th Aug 2009

TTSL confidential and Proprietary

TABLE OF CONTENT

TABLE OF CONTENT .........................................................................................................2

INTRODUCTION ...................................................................................................................5

1.1 PURPOSE .....................................................................................................................5 1.2 SCOPE .........................................................................................................................5 1.3 NOTICES .....................................................................................................................5 1.4 CONVENTIONS ............................................................................................................5 1.5 REVISION HISTORY.....................................................................................................5 1.6 REFERENCES ...............................................................................................................7 1.7 ACRONYMS.................................................................................................................7

2 REQUIREMENTS...........................................................................................................8

2.1 PHYSICAL CHARACTERISTICS......................................................................................8 2.1.1 Format and layout .............................................................................................8 2.1.2 Temperature range for card operation..............................................................8 2.1.3 Contacts .............................................................................................................8

2.2 ELECTRONIC SIGNALS AND TRANSMISSION PROTOCOLS..............................................8 2.3 LOGICAL MODEL ........................................................................................................8 2.4 SECURITY FEATURES ..................................................................................................8

2.4.1 Authentication and cipher key generation procedure........................................9 2.4.2 Algorithms and processes ..................................................................................9

2.5 FILE ACCESS CONDITIONS ..........................................................................................9 2.6 STANDARDS COMPLIANCY..........................................................................................9 2.7 HARDWARE SPECIFICATIONS ......................................................................................9 2.8 SIM PROFILES ..........................................................................................................10 2.9 ADVANCED FUNCTIONS: ...........................................................................................10

2.9.1 DSTK................................................................................................................10 2.9.2 OTA or Remote file Management ....................................................................10

3 CONTENT OF EF’S .....................................................................................................11

3.1 EF’S AT MF LEVEL ...................................................................................................11 3.1.1 EF 2FE2: ICCID (ICC Identification) ............................................................11 3.1.2 EF 2F05: ELP (Extended language preference) .............................................12

3.2 TATA SPECIFIC EF’S ...............................................................................................12 3.2.1 EF 8F11: EAC (EVD Activation Code)...........................................................12 3.2.2 EF 8F12: ERC (EVD Recharge Code) ............................................................12 3.2.3 EF 8F13: SRAF (Smart Roaming Activation Flag).........................................12 3.2.4 EF 8F14: SRT (Smart Roaming Timer)...........................................................12 3.2.5 EF 8F16 : TISMSC (Triple IMSI SMSC).........................................................13

3.3 GSM DIRECTORY: ....................................................................................................13 3.3.1 EF 6F05: LP (Language preference): .............................................................13 3.3.2 EF 6F07: IMSI: ...............................................................................................13 3.3.3 EF 6F20: Kc: ...................................................................................................14 3.3.4 EF 6F30: PLMN Selector:...............................................................................14 3.3.5 EF 6F31: HPLMN Search Period:..................................................................14






3.3.6 EF 6F37: Advice of Charge Max: ...................................................................14 3.3.7 EF 6F38: SIM Service Table TR: ....................................................................15 3.3.8 EF 6F39: Accumulated Call Meter: ................................................................16 3.3.9 EF 6F41: Price Per Unit & Currency .............................................................17 3.3.10 EF 6F45: Cell Broad. Msg. Identifier .............................................................17 3.3.11 EF 6F46: SPN..................................................................................................17 3.3.12 EF 6F48: CBMID ............................................................................................17 3.3.13 EF 6F50: CBMIR.............................................................................................18 3.3.14 EF 6F52: Kc GPRS: ......................................................................................18 3.3.15 EF 6F53: LOCI GPRS:....................................................................................18 3.3.16 EF 6F54: Setup Menu file: ..............................................................................18 3.3.17 EF 6F74: Broadcast Control Channel: ...........................................................18 3.3.18 EF 6F78: Access Control Class: .....................................................................18 3.3.19 EF 6F7B: Forbidden PLMN: ........................................................................19 3.3.20 EF 6F7E: Location Information:.....................................................................19 3.3.21 EF 6FAD: Administrative Data:......................................................................19 3.3.22 EF 6FAE: Phase Identification: ......................................................................19 3.3.23 EF 6F3E: Group Identifier Level 1 .................................................................19 3.3.24 EF 6F3F: Group Identifier Level 2 .................................................................20 3.3.25 EF 6FB7: Emergency Call Codes ...................................................................20 3.3.26 EF 6FC5: PLMN Network Name.....................................................................20 3.3.27 EF 6FC6: Operator PLMN List.......................................................................20

3.4 TELECOM DIRECTORY: .............................................................................................20 3.4.1 EF 6F3A: Abbreviated dialing numbers (ADN):................................20 3.4.2 EF 6F3B: Fixed Dialing Numbers (FDN):....................................................22 3.4.3 EF 6F40: MSISDN: .........................................................................................22 3.4.4 EF 6F44: Last Number Dialed (LND): ..........................................................23 3.4.5 EF 6F4A: EXT1:..............................................................................................23 3.4.6 EF 6F3C: Short Messages Service:.................................................................23 3.4.7 EF 6F43: Short Message Status: .....................................................................23 3.4.8 EF 6F42: Short Message Parameter:..............................................................23 3.4.9 EF 6F3D: Capability Conf. Parameter:..........................................................24

4 SIM APPLICATION TOOLKIT.................................................................................24

4.1 PROFILE DOWNLOAD ................................................................................................24 4.2 PROACTIVE SIM .......................................................................................................24 4.3 DATA DOWNLOAD TO SIM........................................................................................24 4.4 MENU SELECTION.....................................................................................................24 4.5 CALL CONTROL BY SIM ...........................................................................................25 4.6 SECURITY .................................................................................................................25 4.7 PIN AND PUK RETRIES.............................................................................................25

5 CUSTOMIZED APPLICATIONS...............................................................................25

5.1 APPLICATION 1: DSTK PACKAGE.............................................................................25 5.2 APPLICATION 2 – SMART ROAMING APPLICATION....................................................26

5.2.1 Smart roaming application specification.........................................................26 5.3 APPLICATION 3 – MOBILE PAYMENT APPLICATION ..................................................26 5.4 APPLICATION 4 – TRIPLE IMSI .................................................................................26

5.4.1 Triple IMSI Application specification..............................................................27






6 SIM VENDOR ENTRANCE PROCESS.....................................................................28

6.1 PRODUCT DISCUSSION ..............................................................................................28 6.2 PRE REQUISITES FOR TESTING ..................................................................................28

6.2.1 Documentation.................................................................................................28 6.2.2 Compliance Table ............................................................................................29

6.3 PRE-PRODUCTION EVALUATION................................................................................29 6.4 PRODUCTION CARDS TESTING ..................................................................................30

7 OUTPUT FILES ............................................................................................................30

7.1 OUTPUT FILES FORMAT AND NAMING CONVENTION ..................................................30 7.1.1 RSN Format .....................................................................................................30 7.1.2 File Name and format ......................................................................................30






Introduction

1.1 Purpose This document details the generic requirements for SIM cards that will be used in the TTSL GSM network. Use of SIM cards in the network will enable our customers to choose from a wide variety of handsets, provide “plastic roaming” and personal mobility.

1.2 Scope This document is intended for SIM vendors whom TTSL is interested in, for utilizing the SIM Vendors services i.e. SIM Cards and the applications on TTSL’s GSM network.

1.3 Notices The information in this document is provided on an AS IS basis, and without any representations or warranties. Also, no express or implied rights or licenses under any patents or other intellectual property are granted by virtue of the provision of this information. Any use of the information in this document is at the recipient’s own risk.

1.4 Conventions The key words must, must not, required, shall, shall not, should, should not, recommended, may, and optional in this document are to be interpreted as described in [S1].

1.5 Revision History The revision history for this document is shown in Table 1

Version Date Description 1.0 14th November 2008 Initial Spec

1.1 21st November 2008 - Added file type and file size requirements for TATA specific EFs - Added dual records in Dual IMSI EFs for Home and Roam SPN and SMSC. - updated Smart Roaming algorithm

1.2 27th April 2009 -Change in the ICCID format (Sec 3.1.1) -RSN format included (Sec 7.1.1) -Dual IMSI application replaced by Triple IMSI (Sec 5.4) -Output file format and naming convention updated (Sec 7.1.2) -Included CBMID values (Sec 3.3.13) -Changed SPN (Sec 3.3.11) and SUME (Sec 3.3.16) as per branding -Updated SIM profiles (Sec 2.8) -Updated requirements for optimization FDN (Sec 3.4.2), LND (Sec 3.4.4), MSISDN (Sec 3.4.3), removed SDN and EXT2, SMS (Sec 3.4.6 ) -Updated Smart Roaming algorithm (Sec 5.2.1.2) -Updated Triple IMSI (disabling SR while switching on IR) (Sec 5.4.1) -Enabled Smart roaming application (Sec 3.2.3)






1.3 22nd Aug 2009 -Added ECC, GID, OPL/PNN -Update SST as per the added EFs -Preloaded ADNs updated -Number of SMS updated to 25 -EF 8F11 and EF 8F11 removed

Table 1: Revision History






1.6 References Reference documents, which may include 3GPP, standards, and resource documents, are listed in Table 2.

Ref. Document S1 Digital cellular telecommunications system (Phase 2+);Specification of the

Subscriber Identity Module - Mobile Equipment (SIM - ME) interface (GSM 11.11 version 8.3.0 Release 1999)

S2 Digital cellular telecommunications system (Phase 2+);Specification of the SIM Application Toolkit for the Subscriber Identity Module - Mobile Equipment(SIM - ME) interface (GSM 11.14)

Table 2: Reference Standards

1.7 Acronyms The following terms are used throughout this document:

A3 Algorithm 3, authentication algorithm; used for authenticating the subscriber A5 Algorithm 5, cipher algorithm; used for enciphering/deciphering data A8 Algorithm 8, cipher key generator; used to generate Kc A38 A single algorithm performing the functions of A3 and A8 ADN Abbreviated Dialling Number BCD Binary Coded Decimal CB Cell Broadcast

DTMF Dual Tone Multiple Frequency EF Elementary File

ETSI European Telecommunications Standards Institute FDN Fixed Dialling Number GSM Global System for Mobile communications IMSI International Mobile Subscriber Identity Kc Cryptographic key; used by the cipher A5

Ki Subscriber authentication key; the cryptographic key used by the authentication algorithm, A3, and cipher key generator, A8

LND Last Number Dialled ME Mobile Equipment MS Mobile Station

RAND A RANDom challenge issued by the network RFU Reserved for Future Use SIM Subscriber Identity Module SMS Short Message Service

SRES Signed RESponse calculated by a SIM SS Supplementary Service

SSC Supplementary Service Control string USSD Unstructured Supplementary Service Data






2 Requirements Important parameters for type of cards are as mentioned below:

1) Type of Card

•JAVA

2) Size of Card:

3) 64K – For all Domestic and International Roaming

128K – For Channel cards

The other requirements for the SIM cards are listed below:

2.1 Physical characteristics

2.1.1 Format and layout The information on the exterior of either SIM should include at least the individual account identifier and the check digit of the IC Card Identification refer 3.1.1.The card shall have a polarization mark to indicate how the user should insert the card into the ME.

2.1.2 Temperature range for card operation The temperature range for full operational use shall be between -25°C and +70°C

2.1.3 Contacts Refer to Section 4.3 of S1

2.2 Electronic signals and transmission protocols The SIM shall be operated within the accepted limits and shall not exceed the values mentioned below: Electrical characteristics of Vcc under normal operating conditions: Vcc 4.5 – 5.5 V Refer to Section 5 of S1.

2.3 Logical Model This clause describes the logical structure for a SIM, the code associated with it, and the structure of files used. Refer to Section 6 of S1.

2.4 Security Features The security aspects of GSM are described in the normative references GSM 02.09 and GSM 03.20. This section gives information related to security features supported by the SIM to enable the following:






2.4.1 Authentication and cipher key generation procedure The authentication procedure for subscribers shall be as specified in section 4 of the S1 The network sends a Random Number (RAND) to the MS. The ME passes the RAND to the SIM in the command RUN GSM ALGORITHM. The SIM returns the values SRES and Kc to the ME which are derived using the algorithms and processes. The ME sends the SRES to the network. The network compares this value with the SRES which it has calculated by itself. The comparison of these values provides the authentication. The value Kc is used by the ME in future enciphered communications with the network

2.4.2 Algorithms and processes Following algorithms shall be used: Algorithm A3 to authenticate the MS to the network; Algorithm A8 to generate the encryption key. COMP128Version3 to be used for Ki authentication The output of these algorithms on the SIM/ME interface is 12 bytes. The inputs to both A3 and A8, or A38, are Ki (128 bits) internally derived in the SIM, and RAND (128 bits) across the SIM/ME interface. The output is SRES (32 bits)/Kc (64 bits).

2.5 File Access Conditions Every file has its own specific access condition for each command. The relevant access condition of the last selected file shall be fulfilled before the requested action can take place.

2.6 Standards Compliancy The SIM Card shall comply with Release 99 of the following standards:

TS 101 476 / 3GPP TS 03.19 v7.5.0 Java Card 2.1.1 (all specifications). 3GPP TS 11.11 v8.3.0 3GPP TS 03.48 v8.7.0. 3GPP TS 11.14 v8.6.0 3GPP TS 03.19 v7.5.0. 101 220 v1.4.0 (1999-09) (tag value definitions). GSM 03.40

2.7 Hardware Specifications Clock frequency: 1 MHz - 10 MHz Single power supply: 1.8V - 5V ± 10% Temperature range: -25 - 75°C EEPROM size: 64 Kbytes






2.8 SIM Profiles SIM’s shall be broadly categorized into three profiles depending upon the features supported. Details as in Table 3:

Feature \ Profiles Domestic Cards

International Roaming Cards

Channel Cards

DSTK Menu Y Y N Smart Roaming Y Y Y mChek Y Y N Triple IMSI Application N Y N EVD Menu N N Y

Table 3 : SIM Profile Table

Supports voice & data roaming to GSM air interfaces to all domestic and international roaming subscribers. SIM shall support above feature’s profile wise.

2.9 Advanced functions: Advanced function provides new capabilities to SIM cards like changing the STK Menu remotely or changing the elementary files remotely. New applications can be pushed by the operator or pulled by the user, Over the Air.

2.9.1 DSTK

A DSTK client will be installed on SIM cards, which will execute the operator commands sent to the SIM over-the-air. This advanced function will allow the operators to build and remotely maintain a portfolio of SIM-resident services built around SIM Toolkit (STK). The SIM card should have sufficient buffer or the limitation should be clearly stated beforehand during the product discussion phase so that informed decision can be made about the applications. The SIM should be capable of accepting the changes related to STK Menu, be it pull based or push based. The SIM should accept add/remove any level of STK Menu Over-the-Air using DSTK. DSTK Engine along with the DSTK Menu will be provided by the DSTK Vendor. More details are provided in Section 5.1

2.9.2 OTA or Remote file Management

Using SMSPP, SIM card shall be able to update EF’s based on file access conditions set for them.






3 Content of EF’s The files have been classified in three categories namely, GSM Directory, Telecom Directory and TATA specific EF’s. Default Access condition to be set as per S1 standard, unless explicitly mentioned.

3.1 EF’s at MF level

3.1.1 EF 2FE2: ICCID (ICC Identification) This EF provides a unique identification number for the SIM Format of SIM or ICCID: A typical SIM (19 digit) example 89 91 100 1200 01234560 + C provides details as below

ICCID format (19+1 digits)

Description Appl. Code

Country code

N/W code Pre/Post

Vendor code

Card size Sr. No

Check digit

No of Digits (20 incl. check digit) 2 2 3 1 1 1 9 1

Ex. 89 91 045 1 1 1 XXXXXXXXX 1 Where:

Card Type Code Prepaid 1 Postpaid 2 Card Size Code 64K 1 128k 2 Vendor Code Gemalto Digital 1 Oberthur Card 2 Eastcompeace 3 Syscom 4 G&D 5 Watchdata 6 Sharon Solutions 7

Table 4: Vendor Code

For MNC: Please refer to the MNC column of Table 5

Value: TATA Specific Access Condition: Default






3.1.2 EF 2F05: ELP (Extended language preference) This EF contains the codes for up to n languages. This information, determined by the user/operator, defines the preferred languages of the user in order of priority. This information may be used for the screening of Cell Broadcast messages in a preferred language. Value: FF…FF Access Condition: Default + OTA capable

3.2 TATA Specific EF’s

The following EF’s shall be present under MF 3F00 and shall be OTA updatable

3.2.1 EF 8F11: EAC (EVD Activation Code)

This EF is no longer required

3.2.2 EF 8F12: ERC (EVD Recharge Code) This EF is no longer required

3.2.3 EF 8F13: SRAF (Smart Roaming Activation Flag) This EF contains Flag to activate and deactivate the Smart Roaming Application.

Identifier: 8F13 Structure: linear fixed Mandatory

Record length: 1 Bytes Update activity: low Access Conditions: READ CHV1 UPDATE ADM INVALIDATE ADM REHABILITATE ADM

Bytes Description M/O Length

1 Smart Roaming Activation Flag M 1

- Smart Roaming Flag Content: Byte 1, b0=0 means Smart Roaming disabled. Byte 1, b0=1 means Smart Roaming enabled. Rest of the bits shall be set to 0. Default Value: b0=1, Smart Roaming shall be enabled. Access Condition: Default + OTA capable

3.2.4 EF 8F14: SRT (Smart Roaming Timer) This EF contains timer information for the Smart Roaming Application.






Identifier: 8F14 Structure: linear fixed Mandatory

Record length: 2 Bytes Update activity: low Access Conditions: READ CHV1 UPDATE ADM INVALIDATE ADM REHABILITATE ADM

Bytes Description M/O Length 1 Smart Roaming Timer M 2

- Smart Roaming Timer Content: two bytes contains value of Smart Roaming Timer in minutes. Default Value: 300 Access Condition: Default + OTA capable

3.2.5 EF 8F16 : TISMSC (Triple IMSI SMSC) This EF contains SMSC parameters values for Home and Roaming Sponsored Carrier for Dual IMSI Application. Encoding and structure of the file shall be same as EF 6F42 Refer Section 3.4.8. This EF shall have two records/copies of EF 6F42 where first record contains SMSC parameters for Home network and second on contains SMSC parameters for Roaming network. Default Value for first record: Same as that of EF 6F42 Default Value for second record: +919821900300 Access Condition: Default + OTA capable

3.3 GSM Directory:

3.3.1 EF 6F05: LP (Language preference): This EF contains the codes for one or more languages. This information, determined by the user/operator, defines the preferred languages of the user in order of priority. Value: FFFFFFFF Access Condition: Default + OTA capable

3.3.2 EF 6F07: IMSI: This EF contains the International Mobile Subscriber Identity (IMSI) Value: TATA Specific Access Condition: Default






3.3.3 EF 6F20: Kc: This EF contains the ciphering key Kc and the ciphering key sequence number n. Value: FFFFFFFFFFFFFFFF07 Access Condition: Default

3.3.4 EF 6F30: PLMN Selector: This EF contains information for the preferred TATA PLMNs of the user in priority order. SIM vendor should support at least 83 PLMNs to accommodate home and other TATA PLMNs. Each card will be circle specific.

Sr No Circle MCC-MNC

1 Delhi 405-029 2 HP 405-032 3 Punjab 405-042 4 Haryana 405-031 5 UP-E 405-045 6 UP-W 405-046 7 Rajasthan 405-043 8 Gujarat 405-030 9 MP 405-038

10 Kolkata 405-036 11 RoWB 405-047 12 Bihar 405-027 13 Orissa 405-041 14 AP 405-025 15 Karnataka 405-034 16 Tamilnadu 405-044 17 Kerala 405-035 18 Maharastra 405-037 19 Mumbai 405-039

Table 5 : TATA PLMN Table Value: To be derived from the above table Access Condition: Default + OTA capable

3.3.5 EF 6F31: HPLMN Search Period: This EF contains the interval of time between searches for the HPLMN Time interval. The time interval between two searches to be set as 30 Minutes Value: To be derived from above detail Access Condition: Default + OTA capable

3.3.6 EF 6F37: Advice of Charge Max: This EF contains the maximum value of the accumulated call meter.






Value: 000000 Access Condition: Default + OTA capable

3.3.7 EF 6F38: SIM Service Table This EF indicates which services are allocated, and whether, if allocated, the service is activated. If a service is not allocated or not activated in the SIM, the ME shall not select this service.

Service table Service Service Allocated

Service Activated

Service n°1 CHV1 disable function Y Y

Service n°2 Abbreviated Dialling Numbers (ADN) Y Y

Service n°3 Fixed Dialling Numbers (FDN) Y Y

Service n°4 Short Message Storage (SMS) Y Y

Service n°5 Advice of Charge (AoC) Y Y

Service n°6 Capability Configuration Parameters (CCP) Y Y

Service n°7 PLMN selector Y Y

Service n°8 RFU N N

Service n°9 MSISDN Y Y

Service n°10 Extension1 Y Y

Service n°11 Extension2 N N

Service n°12 SMS Parameters Y Y

Service n°13 Last Number Dialled (LND) Y Y

Service n°14 Cell Broadcast Message Identifier Y Y

Service n°15 Group Identifier Level 1 N N

Service n°16 Group Identifier Level 2 N N

Service n°17 Service Provider Name Y Y

Service n°18 Service Dialling Numbers (SDN) N N


Service n°20 RFU N N

Service n°21 VGCS Group Identifier List (EFVGCS and EFVGCSS) N N

Service n°22 VBS Group Identifier List (EFVBS and EFVBSS) N N

Service n°23 Enhanced Multi-Level Precedence and Pre-emption Service N N

Service n°24 Automatic Answer for eMLPP N N

Service n°25 Data download via SMS-CB Y Y

Service n°26 Data download via SMS-PP Y Y

Service n°27 Menu selection Y Y






Service n°28 Call control N N

Service n°29 Proactive SIM Y Y

Service n°30 Cell Broadcast Message Identifier Ranges Y Y

Service n°31 Barred Dialling Numbers (BDN) N N


Service n°33 De-personalization Control Keys N N

Service n°34 Co-operative Network List N N

Service n°35 Short Message Status Reports Y Y

Service n°36 Network's indication of alerting in the MS N N

Service n°37 Mobile Originated Short Message control by SIM N N

Service n°38 GPRS Y Y

Service n°39 Image (IMG) N N

Service n°40 SoLSA (Support of Local Service Area) N N

Service n°41 USSD string data object supported in Call Control N N

Service n°42 RUN AT COMMAND command N N

Service n 43 PLMN Selector List with Access Technology N N

Service n 44 OPLMN Selector List with Access Technology N N

Service n 45 HPLMN Access Technology N N

Service n 46 CPBCCH Information N N

Service n 47 Investigation Scan N N

Service n°48 Extended Capability Configuration Parameters N N

Service n°49 MExE N N

Service n°50

Service n°51 PLMN Network Name Y Y

Service n°52 Operator PLMN List Y Y

Table 6: GSM Service Table Value: To be derived from Table 6 Access Condition: Default + OTA capable

3.3.8 EF 6F39: Accumulated Call Meter: This EF contains the total number of units for both the current call and the preceding calls. Value: FFFFF Access Condition: Default + OTA capable






3.3.9 EF 6F41: Price Per Unit & Currency This EF contains the Price per Unit and Currency Table (PUCT). The PUCT is Advice of Charge related information which may be used by the ME in conjunction with EFACM to compute the cost of calls in the currency chosen by the subscriber Value: FFFFFF0000 Access Condition: Default + OTA capable

3.3.10 EF 6F45: Cell Broad. Msg. Identifier This EF contains the Message Identifier Parameters which specify the type of content of the cell broadcast messages that the subscriber wishes the MS to accept. Value: FFFF Access Condition: Default + OTA capable

3.3.11 EF 6F46: SPN This EF contains the service provider name and appropriate requirements for the display by the ME. The encoding used shall be 7 bit packed. SPN to be displayed as: TATA DOCOMO Value: To be derived from above; Display Condition: 00 Access Condition: Default + OTA capable

3.3.12 EF 6F48: CBMID This EF contains the message identifier parameters which specify the type of content of the cell broadcast messages which are to be passed to the SIM. Any number of CB message identifier parameters may be stored in the SIM.

Channel Number(Dec) Channel No(Hex)

2000 7D0 3000 BB8 4000 FA0 5000 1388 6000 1770 7000 1B58 8000 1F40 9000 2328 10000 2710 11000 2AF8

Value: Vendor shall derive from the above table Access Condition: Default + OTA capable






3.3.13 EF 6F50: CBMIR This EF contains ranges of cell broadcast message identifiers that the subscriber wishes the MS to accept. Any number of CB Message Identifier Parameter ranges may be stored in the SIM. No order of priority is applicable. Value: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF Access Condition: Default + OTA capable

3.3.14 EF 6F52: Kc GPRS: This EF contains the ciphering key KcGPRS and the ciphering key sequence number n for GPRS Value: FFFFFFFFFFFFFFFF07 Access Condition: Default

3.3.15 EF 6F53: LOCI GPRS: This EF contains Location Information: Packet Temporary Mobile Subscriber Identity (P-TMSI); Packet Temporary Mobile Subscriber Identity signature value (P-TMSI signature value); Routing Area Information (RAI); Routing Area update status. Value: FFFFFFFFFFFFFFFFFFFF0000FF01 Access Condition: Default

3.3.16 EF 6F54: Setup Menu file: This EF contains Simple TLVs related to the menu title to be used by a SIM card supporting the SIM API when issuing a SET UP MENU proactive command. Menu name to be displayed as Dive-in Now Value: To be derived from above Access Condition: Default + OTA capable

3.3.17 EF 6F74: Broadcast Control Channel: BCCH storage may reduce the extent of a Mobile Station's search of BCCH carriers when selecting a cell. The BCCH carrier lists in an MS. The information is coded as octets 2-17 of the "neighbor cells description information element" Value: FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF Access Condition: Default

3.3.18 EF 6F78: Access Control Class: The access control class is a parameter to control the RACH utilization. 15 classes are split into 10 classes randomly allocated to normal subscribers and 5 classes allocated to specific high priority users.






Value: Last digit of IMSI. Example: 0003 Access Condition: Default + OTA capable

3.3.19 EF 6F7B: Forbidden PLMN: This EF contains the coding for four Forbidden PLMNs (FPLMN). It is read by the ME as part of the SIM initialization procedure and indicates PLMNs which the MS shall not automatically attempt to access. A PLMN is written to the EF if a network rejects a Location Update with the cause "PLMN not allowed". The ME shall manage the list as follows. When four FPLMNs are held in the EF, and rejection of a further PLMN is received by the ME from the network, the ME shall modify the EF using the UPDATE command. This new PLMN shall be stored in the fourth position, and the existing list "shifted" causing the previous contents of the first position to be lost. When less than four FPLMNs exist in the EF, storage of an additional FPLMN shall not cause any existing FPLMN to be lost.

Value: FF...FF Access Condition: Default

3.3.20 EF 6F7E: Location Information: This EF contains the following Location Information: Temporary Mobile Subscriber Identity (TMSI); Location Area Information (LAI); TMSITIME; Location update status. Value: FFFFFFFFFFFFFF0000FF01 Access Condition: Default

3.3.21 EF 6FAD: Administrative Data: This EF contains information concerning the mode of operation according to the type of SIM, such as normal to be used by PLMN subscribers for GSM operations. Value: 00FFFF Access Condition: Default

3.3.22 EF 6FAE: Phase Identification: This EF contains information concerning the phase of the SIM. EFPhase is coded '03' an ME supporting SIM Application Toolkit shall perform the PROFILE DOWNLOAD procedure, as defined in GSM 11.14 Value: 03 Access Condition: Default

3.3.23 EF 6F3E: Group Identifier Level 1 This EF contains the value of Group Identifier 1. Value: 54 Access Condition: Default + OTA capable






3.3.24 EF 6F3F: Group Identifier Level 2 This EF contains the value of Group Identifier 2. Value: 55 Access Condition: Default + OTA capable

3.3.25 EF 6FB7: Emergency Call Codes This EF shall hold the following Emergency codes: Value: 100, 101, 102 Access Condition: Default + OTA capable

3.3.26 EF 6FC5: PLMN Network Name This EF contains the full and short form versions of the network name for the registered PLMN. Value: First and second Record content: Full name for network contents: TATA DOCOMO Short name for network contents: TATA DOCOMO CI: The MS should not add the letters for the Country's Initials to the text string. Coding: GSM default alphabet Access Condition: Default + OTA capable

3.3.27 EF 6FC6: Operator PLMN List This EF contains a prioritised list of Location Area Information (LAI) identities that are used to associate a specific operator name contained in EFPNN with the LAI. Value: MCC, MNC- as per PLMN list specified in latest spec of SIM. LAC- wild value PLMN Network Name Record Identifier-2nd record of 6FC5 for all LAIs above. Access Condition: Default + OTA capable

3.4 Telecom Directory:

3.4.1 EF 6F3A: Abbreviated dialing numbers (ADN): This EF contains Abbreviated Dialing Numbers (ADN) and/or Supplementary Service Control strings (SSC). In addition it contains identifiers of associated network/bearer capabilities and identifiers of extension records. It may also contain an associated alpha-tagging.

Prepaid:






Customer Care 121

Account Info 12525

Recharge 12526

24-hrs Music 543213

Astrology 54321217

Call me tunes 543211

Cricket Scores 54321210

Devotional 54321219

Dive In Voice 54321

Jokes 54321214

Learn English 54321213

News 54321211

Star Services *123#

Voice Chat 543216

Balance Info *111#

Postpaid:

Customer Care 121

24-hrs Music 543213

Astrology 54321217



Devotional 54321219

Dive In Voice 54321

Jokes 54321214


News 54321211

Star Services *123#

Voice Chat 543216

EVD:






e charge 52200

Activation 52201

Helpdesk 52202

Customer Care 121

Account Info 12525

Recharge 12526

24-hrs Music 543213

Astrology 54321217



Devotional 54321219

Dive In Voice 54321

Jokes 54321214


News 54321211

Star Services *123#

Voice Chat 543216 Value: To be derived from the above table Access Condition: Default + OTA capable

3.4.2 EF 6F3B: Fixed Dialing Numbers (FDN): This EF contains Fixed Dialing Numbers (FDN) and/or Supplementary Service Control strings (SSC). In addition it contains identifiers of associated network/bearer capabilities and identifiers of extension records. It shall contain an associated alpha-tagging. Capacity to store 5 entries with alpha tag. Value: FF…FF Access Condition: Default + OTA capable

3.4.3 EF 6F40: MSISDN: This EF contains MSISDN(s) related to the subscriber. In addition it contains identifiers of associated network/bearer capabilities and identifiers of extension records. It may also contain an associated alpha-tagging.

Value: FFFFFFFFFFFFFFFFFFFFFFFFFFFF (14 Byte) Access Condition: Default






3.4.4 EF 6F44: Last Number Dialed (LND): This EF contains the last numbers dialed (LND) and/or the respective supplementary service control strings (SSC). In addition it contains identifiers of associated network/bearer capabilities and identifiers of extension records. It may also contain associated alpha-tagging. Capacity to store 1 entry. Value: Default Access Condition: Default + OTA capable

3.4.5 EF 6F4A: EXT1: This EF contains extension data of an ADN/SSC, an MSISDN, or an LND. Extension data is caused by: - an ADN/SSC (MSISDN, LND) which is greater than the 20 digit capacity of the ADN/SSC (MSISDN, LND) Elementary File or where common digits are required to follow an ADN/SSC string of less than 20 digits. The remainder is stored in this EF as a record, which is identified by a specified identification byte inside the ADN/SSC (MSISDN, LND) Elementary File. The EXT1 record in this case is specified as additional data. Value: 00FFFFFFFFFFFFFFFFFFFFFFFF Access Condition: Default + OTA capable

3.4.6 EF 6F3C: Short Messages Service: This EF contains information in accordance with GSM 03.40 comprising short messages (and associated parameters) which have either been received by the MS from the network, or are to be used as an MS originated message. Number of SMS’s should be 25. Value: To be derived from the above Access Condition: Default

3.4.7 EF 6F43: Short Message Status: This EF contains status information relating to the short message service. The provision of this EF is associated with EFSMS. Both files shall be present together, or both absent from the SIM. Value: Value: FFFF Access Condition: Default + OTA capable

3.4.8 EF 6F42: Short Message Parameter: This EF contains values for Short Message Service header Parameters (SMSP), which can be used by the ME for user assistance in preparation of mobile originated short messages. For example, a service centre address will often be common to many short messages sent by the subscriber. SMSC for PAN India MO : +919032055002 Value: To be derived from above Access Condition: Default + OTA capable






3.4.9 EF 6F3D: Capability Conf. Parameter: This EF contains parameters of required network and bearer capabilities and ME configurations associated with a call established using an abbreviated dialing number, a fixed dialing number, an MSISDN, a last number dialed, a service dialing number or a barred dialing number. For compatibility reasons, this file may be present for release 98 or earlier MEs in order to support Capability Configuration Parameters service. Value: Value: FFFFFFFFFFFFFFFFFFFFFFFFFFFF Access Condition: Default + OTA capable

4 SIM Application Toolkit

The SIM Application Toolkit provides mechanisms that allow applications, existing in the SIM, to interact and operate with any ME which supports the specific mechanism(s) required by the application.

4.1 Profile Download Profile downloading provides a mechanism for the ME to tell the SIM what it is capable of. The ME knows what the SIM is capable of through the SIM Service Table and EFPHASE. A SIM card shall identify an ME that supports proactive SIMs based on TERMINAL PROFILE command exchanged during SIM initialization.

4.2 Proactive SIM Proactive SIM gives a mechanism whereby the SIM can initiate actions to be taken by the ME. SIM to support all proactive commands as per Release 99

4.3 Data download to SIM Data downloading to the SIM uses the transport mechanisms of SMS point-to-point and Cell Broadcast. Transfer of information over the SIM-ME interface uses the ENVELOPE command.

4.4 Menu Selection A set of possible menu entries is supplied by the SIM in a proactive SIM command. The menu selection mechanism is used to transfer the SIM application menu item which has been selected by the user to the SIM. A set of possible menu options can be supplied by the SIM using the proactive command SET UP MENU. If the SIM has sent this command, and the user subsequently chooses an option, the ME shall use this procedure to inform the SIM.






4.5 Call Control by SIM When this service is activated by the SIM, all dialed digit strings and supplementary service control strings are first passed to the SIM before the ME sets up the call or the supplementary service operation. The SIM has the ability to allow, bar or modify the call or the supplementary service operation.

4.6 Security Applications designed using the features in this specification may require methods to ensure data confidentiality, data integrity, and data sender validation, or any subset of these.

4.7 PIN and PUK retries

Card Type Test Commercial Re-try

PIN1 1234 1234 3

PIN2 1234 R 3

PUK1 12345678 R 10

PUK2 12345678 R 10

Table 7 : PIN- PUK details

5 Customized Applications The below listed applications are mandatory. The names of the applications are indicative and the contents are not finalized yet; hence this should be treated as the draft. The complete details entailing the content, procedure, requirements will be given separately.

5.1 Application 1: DSTK Package Tata will be implementing a DSTK platform for VAS administration and VAS management. It provides effective delivery, personalization and management of any VAS services ranging from IOD, entertainment (voting, gaming, and others), to m-commerce. The DSTK implementation consists of a client (Service Engine) and Menu (bytecode) to be loaded onto the SIM card which communicates with the DSTK server components on the network side. The following components of DSTK package will be provided by the DSTK solution provider:

• DSTK Engine • Cell Broadcast • IMEI Tracking • DSTK Menu Bytecode

Domestic consumer menu






International consumer menu Channel cards menu

5.2 Application 2 – Smart Roaming Application The objective of Smart Roaming application is to ensure that a subscriber in national roaming is always connected to preferred network if the preferred network exists.

5.2.1 Smart roaming application specification

5.2.1.1 Configuration parameters

The following parameters are required for smart roaming application: • Application (enable/disable) flag (App flag) • Smart roaming timer (Ref as Timer) The range and default values of the parameter shall be as Table 8

Parameter Range Default Value

App Flag (EF 8F13) Enable, Disable Disabled Timer (EF 8F14) 0-10Hours 5 Hours

Table 8 : Smart Roaming settings

5.2.1.2 Algorithm

i. Wait for Smart roaming timer to expire. ii. If the acquired PLMN if a non preferred PLMN (any PLMN outside PLMN list, Force MS to scan and look for preferred PLMN (this can be done by flushing EFLOCI and issuing REFRESH command) iii.Smart roaming shall not REFRESH in Home NW

5.3 Application 3 – Mobile Payment Application This will be a banking application that will enable the user to do transactions like pay mobile bills, insurance premiums, buy air tickets and movie tickets from the convenience of phone thereby causing convergence of mobile operator network with bank networks using mobile phone. The application and integration details will be shared by mChek.

5.4 Application 4 – Triple IMSI This application will be ported only on International Roaming cards. Triple IMSI application allows to stores three IMSIs against the same subscription. Application would enable subscriber to select Roaming Sponsored Carrier IMSI while roaming and experience seamless voice & data services.






5.4.1 Triple IMSI Application specification The SIM shall support storage of three IMSI values. After IMSI change EF_LOCI shall be cleared and the following DISPLAY TEXT shall be display, user response to DISPLAY TEXT shall be ignored. Roam-1: "Dear customer, To activate international roaming, Please Restart your Phone." Roam-2: "Dear customer, To activate international roaming, Please Restart your Phone." Off: "Dear customer, To De activate international roaming, Please Restart your Phone." The following menu shall be appended to DSTK main menu

International Roaming

Roam- 1 Roam- 2 Off

Upon selection of ‘Roam-1’ application shall set parameters as per the following Table 9

Parameter Value for ‘Roam- 1’ IMSI Roam-1 IMSI (Tata

Gateway circle IMSI) SMSC number First record of EF 8F16 EF 8F13: SRAF (Smart Roaming Activation Flag)

b0=0 (Smart Roaming disabled)

Table 9: Parameter value for international Roaming ‘Roam-1’

Upon selection of ‘Roam- 2’ application shall set parameters as per the following Table 10

Parameter Value for ‘Roam- 2’ IMSI Roam- 2 IMSI (BPL

Gateway IMSI SMSC number Second record of EF

8F16 EF 8F13: SRAF (Smart Roaming Activation Flag)

b0=0 (Smart Roaming disabled)

Table 10: Parameter value for international Roaming ‘on’

Upon selection of ‘off’ application shall change IMSI to Home IMSI ( Tata Home circle IMSI) and following the parameters listed in Table 11






Parameter Value for ‘off’ IMSI TATA home circle

IMSI SMSC number First record of EF 8F16 EF 8F13: SRAF (Smart Roaming Activation Flag)

b0=1 (Smart Roaming enabled)

Table 11: Parameter value for international Roaming ‘off

6 SIM Vendor Entrance Process

6.1 Product Discussion a) A new vendor expressing interest in being a SIM supplier to the operator shall be routed through SCM. b) The latest specification will be shared by SCM and discussions will take place between SCM, Vendor and Technology Testing Team to freeze on the requirements. c) Following requirements shall be closed upon

size of the card 64 or 128K card Profile of the card STK Menu on the card

d) The SIM vendors will integrate the requirements and prepare the sample test cards.

6.2 Pre Requisites for Testing

6.2.1 Documentation This describes the general requirements to be met by SIM Card Vendor. Hard and soft copy of all documents shall be provided in English.

The documents shall comprise of:

•Electrical Profile •Graphical Profile •Memory Map •Output files (Inventory/Network/CRM) •User manual describing the usage of the SIM card, intended for the end subscriber. •Tools to read Elementary file (Standard based & TATA specific) •Decoders to read the content from the tools above. •Certification (Self) for SIM to support GSM 11.17 V8.1.0






6.2.2 Compliance Table

TTSL REQUIREMENTS COMPLIANCE

SIM Cards Total 30

Electrical Profile

Memory Map

Sync Tool Phone Book

SMS

6.3 Pre-Production evaluation The location for testing would be communicated to the vendors beforehand. The testing would be carried out on some reference handsets and the new handsets. The testing process shall include the following:

a) Basic Parameters expected to be programmed in the SIM Card will be tested as

per the Electrical profile provided by the SIM vendor b) The SIM vendor will provide a memory map. Memory capacities will be tested

for Phone book feature Call registers SMS registers User’s personal settings if any.

c) For the above the following shall be tested: Length of the records supported for respective fields. Total number of records that can be stored. Creation of records Deletion of records Modification of records Transfer of records between memory locations. Call features SMS features Network feature i.e. call forwarding & call waiting.

d) Depending on the applications supported by the card, the following shall also be tested.

Browser test - These tests include connecting to the WAP Browser, Browsing sites, and Downloading content and related functions.

DSTK – Capability & Functionality of Dynamically changing the STK Menu

Various preloaded application as mentioned in Section of this document will be tested for their functionality.

IMEI Tracking Implementation.

e) Authentication functionality shall be tested. f) All the specifications mentioned in this document will be tested for compliance. g) Necessary hardware / software tools shall be provided by SIM vendor to read,

write and edit parameters in the card to perform the necessary tests.






A detailed test report will be provided to the SIM vendor. This will include the complete environment under which the tests were performed including the terminals used for testing. The cards will be produced in bulk only when the samples pass the above test criteria.

6.4 Production Cards Testing After the ordered cards are shipped to TTSL, a sample of mutually agreed cards will be pulled out of the shipment randomly and tested for any anomalies from agreed specifications. The test cases will be the same as above. TTSL has the right to reject lots based on this test criterion.

7 Output files The SIM Vendor shall provide 3 output files in the format mentioned below

7.1 Output files format and naming convention

7.1.1 RSN Format RSN format (15 digits)

Description Prefix N/W code Pre/Post

Vendor code Card size Sr. No

No of Digits (15) 1 2 1 1 1 9

Ex. 5 45 1 1 1 XXXXXXXXX

Table 12: RSN Format

7.1.2 File Name and format The files given shall follow the file name conventions as given below:

Single IMSI Vendor upload file Type of File Type File Naming Convention Fields Sequence Remarks

Postpaid GSM_Post_<VendorName>_Date<DDMMYYYY>_<FileNo>.txt

ICCID,KI(Encrypted), IMSI NA Network

File Prepaid

GSM_Pre_<VendorName>_Date<DDMMYYYY>_<FileNo>.txt

ICCID,KI(Encrypted), IMSI NA

Postpaid

GSM_CRM_Date<DDMMYYYY>_<circleid>_<VendorName>_<FileNo>.txt

CIRCLE_ID, ICCID, PUK1, PIN1, PIN2, PUK2. NA

CC File Prepaid


CIRCLE_ID, ICCID, PUK1, PIN1, PIN2, PUK2. NA






Postpaid

GSM_INV_POST_<circle_id>_Date<DDMMYYYY>_RID<Reservation_id>_<VendorName >_<FileNo>.txt

ICCID, IMSI, RSN, MAKE-N-MODEL NA

Inventory File Prepaid

GSM_INV_PRE_<circle_id>_Date<DDMMYYYY>_RID<Reservation_id>_<VendorName >_<FileNo>.txt

ICCID, IMSI, RSN, MAKE-N-MODEL NA

Triple IMSI Vendor Upload File Type of File Pre/Post Field Sequence Remarks

Postpaid GSM_Post_<VendorName>_Date<DDMMYYYY>_<FileNo>.txt

ICCID,KI(Encrypted), IMSI(Primary Only)

Gateway IMSI & Triple IMSI need not to be mentioned as IMSI does not hold any values for network file.

Network File Prepaid

GSM_Pre_<VendorName>_Date<DDMMYYYY>_<FileNo>.txt

ICCID,KI(Encrypted), IMSI(Primary Only)

Gateway IMSI & Triple IMSI need not to be mentioned as IMSI does not hold any values for network file.

Postpaid


CIRCLE_ID, ICCID, PUK1, PIN1, PIN2, PUK2.

IMSI's not required to be mentioned

CC File Prepaid


CIRCLE_ID, ICCID, PUK1, PIN1, PIN2, PUK2.

IMSI's not required to be mentioned

Inventory File Postpaid

GSM_INV_POST_TRIPLEIMSI_<circle_id>_Date<DDMMYYYY>_RID<Reservation_id>_<VendorName >_<FileNo>.txt

ICCID, IMSI(Primary), RSN, MAKE-N-MODEL, IMSI2(Gateway IMSI),IMSI2(BPL IMSI)

Gateway IMSI & Triple IMSI need not to be mentioned as last two fields in the file






Prepaid

GSM_INV_PRE_TRIPLEIMSI_<circle_id>_Date<DDMMYYYY>_RID<Reservation_id>_<VendorName >_<FileNo>.txt

ICCID, IMSI(Primary), RSN, MAKE-N-MODEL, IMSI2(Gateway IMSI),IMSI2(BPL IMSI)

Gateway IMSI & Triple IMSI need not to be mentioned as last two fields in the fil

Vendor Code Gemalto Digital Gemalto Oberthur Card Oberthur Eastcompeace Eastcompeace Syscom Syscom G&D G&D Watchdata Watchdata Sharon Solutions SharonSolutions

Table 13: Vendor Name

For Circle ID refer Table 14:

Circle ID Circle AP ANDHRA PRADESH BH BIHAR MH MAHARASHTRA GJ GUJARAT HR HARYANA HP HIMACHAL PRADESH KA KARNATAKA KL KERALA MP MADHYA PRADESH DL NEW DELHI OR ORISSA PB PUNJAB RJ RAJASTHAN RW REST OF WEST BENGAL TN TAMILNADU UPE UTTAR PRADESH EAST UPW UTTAR PRADESH WEST WB WEST BENGAL

ROM REST OF MAHARASHTRA

Table 14: Circle ID

RID (Reservation ID) will be shared through Input file






Separator to be used for content: For Network and CC files, use comma For Inventory file use tab

TTSL Specification for Subscriber Identity Module_v1.3

Documents

Transcript of TTSL Specification for Subscriber Identity Module_v1.3