BEGIN:VCARD

VERSION:2.1

N:;FFA

FN:FFAvvvvvvvvvvvvdddddddddddddddddd

NICKNAME:Test1

ORG:Symbian Foundation

adsdfdfkljdlfijdklfjkldjflkjflkjalkdjalkdjlkajdl[asdjsadjsfgfasddfdsfdfdfdfdfdfdfdfdfdfdfdsfdsfdsfdsfdslfkkdlksfmldksfmlkdsmflkdsmflkdsmflksdmklfsdmffgfasddfdsfdfdfdfdfdfdfdfdfdfdfdsfdsfdsfdsfdslfkkdlksfmldksfmlkdsmflkakljdklasdjklasjdklsajdklasjd;Bluetooth

flkdkfldskjfkldsjflkdsjklfjdsklfjdklfjkldsfjkldsjfkldsjfklsdjflkdsjflkdsjffgfasddfdsfdfdfdfdfdfdfdfdfdfdfdsfdsfdsfdsfdslfkkdlksfmldksfmlkdsmflkdsmflkdsmflksdmklfsdmffgfasddfdsfdfdfdfdfdfdfkjfkljfkdljfksdljfkljfkljlkdsajdklsajdklasjdklasjdksaaflkdkfldskjfkldsjflkdsjklfjdsklfjdklfjkldsfjkldsjfkldsjfklsdjflkdsjflkdsjffgfasddfdsfdfdfdfdfdfdfdfdfdfdfdsfdsfdsfdsfdslfkkdlksfmldksfmlkdsmflkdsmflkdsmflksdmdfdfdfdsfdsfdsfdsfdslfkkdlksfmldksfmlkdsmflkdsmflkdsmflksdmklfsdmffgfasddfdsfdfdfdfdfdfdfdfdfdfdfdsfjdklfjkldsfjkldsjfkldsjfklsdjflkdsjflkdsjffgfasddfdsfdfdfdfdfdfdfdfdfdfdfdsfdsfdsfdsfdslfkkdlksfmldksfmlkdsmflkdsmflkdsmflksdmklfsdmffgfasddfdsfdfdfdfdfdfdfkjfkljfkdljfksdljfkljfkljlkdsajdklsajdklasjdklasjdksaadsdfdfkljdlfijdklfjkldjflkjflkjalkdjalkdjlkajdl[asdjsadjsfgfasddfdsfdfdfdfdfdfdfdfdfdfdfdslkdsmflksdmklfsdmffgfasddfdsfdfdfdfdfdfdfdfdfdfdfdsfdsfdsfdsfdslfkkdlksfmldksfmlkdsmflkakljdklasdjklasjdklsajdklasjd;Bluetooth

Tield: Obsolete term fo=

r Elementary File.=0D=0ADedicated File (DF): A file containing access condit=

ions and optionally Elementary Files (EFs) or other=0D=0ADedicated Files (=

DFs).=0D=0Adirectory: General term for MF and DF.=0D=0AElementary File (EF):=

 A file containing access conditions and data and no other files.=0D=0Afile:=

 A directory or an organised set of bytes or records in the SIM.=0D=0Afile i=

dentifier: The 2 bytes which address a file in the SIM.=0D=0AGSM or DCS 1800=

 application: Set of security mechanisms files data and protocols required=

 by GSM=0D=0Aor DCS 1800.=0D=0AGSM session: That part of the card session de=

dicated to the GSM operation.=0D=0AIC card SIM: Obsolete term for ID-1 SIM.=

=0D=0AID-1 SIM: The SIM having the format of an ID-1 card (see ISO 7816-1 [2=

3]).=0D=0AMaster File (MF): The unique mandatory file containing access cond=

itions and optionally DFs and/or EFs.=0D=0Apadding: One or more bits appende=

d to a message in order to cause the message to contain the required=0D=0Anu=

mber of bits or bytes.=0D=0Aplug-in SIM: A second format of SIM (specified i=

n clause 4).=0D=0Arecord: A string of bytes within an EF handled as a single=

 entity (see clause 6).=0D=0Arecord number: The number which identifies a re=

cord within an EF.=0D=0Arecord pointer: The pointer which addresses one reco=

rd in an EF.=0D=0APage 12=0D=0AGSM 11.11 Version 5.0.0 December 1995=0D=0Aro=

ot directory: Obsolete term for Master File.=0D=0A3.2 Abbreviations=0D=0AFor=

 the purposes of this ETS the following abbreviations apply. In addition to =

the following abbreviations=0D=0Aused in this ETS are listed in GSM 01.04 [2=

].=0D=0AA3 Algorithm 3 authentication algorithm; used for authenticating th=

e subscriber=0D=0AA5 Algorithm 5 cipher algorithm; used for enciphering/dec=

iphering data=0D=0AA8 Algorithm 8 cipher key generator; used to generate Kc=

=0D=0AA38 A single algorithm performing the functions of A3 and A8=0D=0AACM =

Accumulated Call Meter=0D=0AADN Abbreviated Dialling Number=0D=0AADM Access =

condition to an EF which is under the control of the authority which=0D=0Acr=

eates this file=0D=0AALW ALWays=0D=0AAoC Advice of Charge=0D=0AAPDU Applicat=

ion Protocol Data Unit=0D=0AATR Answer To Reset=0D=0ABCCH Broadcast Control =

CHannel=0D=0ABCD Binary Coded Decimal=0D=0ABTS Base Transmitter Station=0D=

=0ACB Cell Broadcast=0D=0ACBMI Cell Broadcast Message Identifier=0D=0ACCITT =

The International Telegraph and Telephone Consultative Committee (now also=

=0D=0Aknown as the ITU Telecommunications Standardization sector)=0D=0ACCP C=

apability/Configuration Parameter=0D=0ACHV Card Holder Verification informat=

ion; access condition used by the SIM for the=0D=0Averification of the ident=

ity of the user=0D=0ACLA CLAss=0D=0ADCS Digital Cellular System=0D=0ADF Dedi=

cated File (abbreviation formerly used for Data Field)=0D=0ADTMF Dual Tone M=

ultiple Frequency=0D=0AEF Elementary File=0D=0AETSI European Telecommunicati=

ons Standards Institute=0D=0Aetu elementary time unit=0D=0AFDN Fixed Diallin=

g Number=0D=0AGSM Global System for Mobile communications=0D=0AHPLMN Home PL=

MN=0D=0AIC Integrated Circuit=0D=0AICC Integrated Circuit(s) Card=0D=0AID ID=

entifier=0D=0AIEC International Electrotechnical Commission=0D=0AIMSI Intern=

ational Mobile Subscriber Identity=0D=0AISO International Organization for S=

tandardization=0D=0AKc Cryptographic key; used by the cipher A5=0D=0AKi Subs=

criber authentication key; the cryptographic key used by the authentication=

=0D=0Aalgorithm A3 and cipher key generator A8=0D=0ALAI Location Area Inf=

ormation; information indicating a cell or a set of cells=0D=0Algth The (spe=

cific) length of a data unit=0D=0ALND Last Number Dialled=0D=0ALSB Least Sig=

nificant Bit=0D=0AMCC Mobile Country Code=0D=0AME Mobile Equipment=0D=0AMF M=

aster File=0D=0AMMI Man Machine Interface=0D=0AMNC Mobile Network Code=0D=

=0AMS Mobile Station=0D=0AMSISDN Mobile Station international ISDN number=

=0D=0AMSB Most Significant Bit=0D=0APage 13=0D=0AGSM 11.11 Version 5.0.0 Dec=

ember 1995=0D=0ANET NETwork=0D=0ANEV NEVer=0D=0ANPI Numbering Plan Identifie=

r=0D=0APIN/PIN2 Personal Identification Number / Personal Identification Num=

ber 2 (obsolete=0D=0Aterms for CHV1 and CHV2 respectively)=0D=0APLMN Public=

 Land Mobile Network=0D=0APTS Protocol Type Select (response to the ATR)=0D=

=0APUK/PUK2 PIN Unblocking Key / PIN2 Unblocking Key (obsolete terms for UNB=

LOCK CHV1=0D=0Aand UNBLOCK CHV2 respectively)=0D=0ARAND A RANDom challenge =

issued by the network=0D=0ARFU Reserved for Future Use=0D=0ASIM Subscriber I=

dentity Module=0D=0ASMS Short Message Service=0D=0ASRES Signed RESponse calc=

ulated by a SIM=0D=0ASSC Supplementary Service Control string=0D=0ASW1/SW2 S=

tatus Word 1 / Status Word 2=0D=0ATMSI Temporary Mobile Subscriber Identity=

=0D=0ATON Type Of Number=0D=0ATP Transfer layer Protocol=0D=0ATS Technical S=

pecification=0D=0AUNBLOCK CHV1/2 value to unblock CHV1/CHV2=0D=0AVPLMN Visit=

ed PLMN=0D=0A3.3 Symbols=0D=0AVcc Supply voltage=0D=0AVpp Programming voltag=

e=0D=0A'0' to '9' and 'A' to 'F' The sixteen hexadecimal digits=0D=0A4 Physi=

cal characteristics=0D=0ATwo physical types of SIM are specified. These are =

the "ID-1 SIM" and the "Plug-in SIM".=0D=0AThe physical characteristics of b=

oth types of SIM shall be in accordance with ISO 7816-12 [23 24] unless=

=0D=0Aotherwise specified. The following additional requirements shall be ap=

plied to ensure proper operation in=0D=0Athe GSM environment.=0D=0A4.1 Forma=

t and layout=0D=0AThe information on the exterior of either SIM should inclu=

de at least the individual account identifier and the=0D=0Acheck digit of th=

e IC Card Identification (see clause 10 EFICCID).=0D=0A4.1.1 ID-1 SIM=0D=

=0AFormat and layout of the ID-1 SIM shall be in accordance with ISO 7816-1=

2 [23 24].=0D=0AThe card shall have a polarisation mark (see TS GSM 02.07 [=

3]) which indicates how the user should=0D=0Ainsert the card into the ME.=

=0D=0AThe ME shall accept embossed ID-1 cards. The embossing shall be in acc=

ordance with ISO 7811=0D=0A[20 21]. The contacts of the ID-1 SIM shall be l=

ocated on the front (embossed face see ISO 7810 [20])=0D=0Aof the card.=0D=

=0A4.1.2 Plug-in SIM=0D=0AThe Plug-in SIM has a width of 25 mm a height of =

15 mm a thickness the same as an ID-1 SIM and a=0D=0Afeature for orientatio=

n. See figure A.1 in normative annex A for details of the dimensions of the =

card and=0D=0Athe dimensions and location of the contacts.=0D=0AAnnexes A.1 =

and A.2 of ISO 7816-1 [23] do not apply to the Plug-in SIM.=0D=0APage 14=0D=

=0AGSM 11.11 Version 5.0.0 December 1995=0D=0AAnnex A of ISO 7816-2 [24] app=

lies with the location of the reference points adapted to the smaller size.=

=0D=0AThe three reference points P1 P2 and P3 measure 75 mm 33 mm and 20=

8 mm respectively from 0.=0D=0AThe values in Table A.1 of ISO 7816-2 [24]=

 are replaced by the corresponding values of figure A.1.=0D=0A4.2 Temperatur=

e range for card operation=0D=0AThe temperature range for full operational u=

se shall be between -25=B0C and +70=B0C with occasional peaks of=0D=0Aup to =

+85=B0C. "Occasional" means not more than 4 hours each time and not over 100=

 times during the life=0D=0Atime of the card.=0D=0A4.3 Contacts=0D=0A4.3.1 P=

rovision of contacts=0D=0AME: There shall not be any contacting elements in =

positions C4 and C8. Contact C6 need not be=0D=0Aprovided for Plug-in SIMs.=

=0D=0ASIM: Contacts C4 and C8 need not be provided by the SIM. Contact C6 sh=

all not be bonded in the SIM=0D=0Afor any function other than supplying Vpp.=

=0D=0A4.3.2 Activation and deactivation=0D=0AThe ME shall connect activate =

and deactivate the SIM in accordance with the Operating Procedures=0D=0Aspec=

ified in ISO/IEC 7816-3 [25].=0D=0AFor any voltage level monitored during t=

he activation sequence or during the deactivation sequence=0D=0Afollowing s=

oft power-down the order of the contact activation/deactivation shall be re=

spected.=0D=0ANOTE 1: Soft Power switching is defined in TS GSM 02.07 [3].=

=0D=0ANOTE 2: It is recommended that whenever possible the deactivation sequ=

ence defined in=0D=0AISO/IEC 7816-3 [25] should be followed by the ME on all=

 occasions when the ME is=0D=0Apowered down.=0D=0AIf the SIM clock is alread=

y stopped and is not restarted the ME is allowed to deactivate all the cont=

acts in=0D=0Aany order provided that all signals reach low level before Vcc=

 leaves high level. If the SIM clock is already=0D=0Astopped and is restarte=

d before the deactivation sequence then the deactivation sequence specified=

 in=0D=0AISO/IEC 7816-3 [25] subclause 5.4 shall be followed.=0D=0AWhen Vpp =

is connected to Vcc as allowed by GSM (see clause 5) then Vpp will be acti=

vated and=0D=0Adeactivated with Vcc at the time of the Vcc activation/deact=

ivation as given in the sequences of ISO/IEC=0D=0A7816-3 [25] subclauses 5.=

1 and 5.4.=0D=0AThe voltage level of Vcc used by GSM differs from that spe=

cified in ISO/IEC 7816-3 [25]. Vcc is powered=0D=0Awhen it has a value betwe=

en 45 V and 55 V.=0D=0A4.3.3 Inactive contacts=0D=0AThe voltages on contac=

ts C1 C2 C3 C6 and C7 of the ME shall be between 0 and =B1 04 volts refe=

renced=0D=0Ato ground (C5) when the ME is switched off with the power source=

 connected to the ME. The=0D=0Ameasurement equipment shall have a resistance=

 of 50 kohms when measuring the voltage on C2 C3 C6=0D=0Aand C7. The resis=

tance shall be 10 kohms when measuring the voltage on C1.=0D=0A4.3.4 Contact=

 pressure=0D=0AThe contact pressure shall be large enough to ensure reliable=

 and continuous contact (e.g. to overcome=0D=0Aoxidisation and to prevent in=

terruption caused by vibration). The radius of any curvature of the contacti=

ng=0D=0Aelements shall be greater than or equal to 08 mm over the contact a=

rea.=0D=0APage 15=0D=0AGSM 11.11 Version 5.0.0 December 1995=0D=0AUnder no c=

ircumstances may a contact force be greater than 05 N per contact.=0D=0A4.4=

 Precedence=0D=0AFor Mobile Equipment which accepts both an ID-1 SIM and a =

Plug-in SIM the ID-1 SIM shall take=0D=0Aprecedence over the Plug-in SIM (s=

ee TS GSM 02.17 [6]).=0D=0A4.5 Static Protection=0D=0AConsidering that the S=

IM is a CMOS device the ME manufacturer shall take adequate precautions (in=

=0D=0Aaddition to the protection diodes inherent in the SIM) to safeguard th=

e ME SIM and SIM/ME interface=0D=0Afrom static discharges at all times and=

 particularly during SIM insertion into the ME.=0D=0A5 Electronic signals an=

d transmission protocols=0D=0AElectronic signals and transmission protocols =

shall be in accordance with ISO/IEC 7816-3 [25] unless=0D=0Aspecified otherw=

ise. The following additional requirements shall be applied to ensure proper=

 operation in=0D=0Athe GSM environment.=0D=0AThe choice of the transmission =

protocol(s) to be used to communicate between the SIM and the ME shall=0D=

=0Aat least include that specified and denoted by T=3D0 in ISO/IEC 7816-3 [2=

5].=0D=0AThe values given in the tables hereafter are derived from ISO/IEC 7=

816-3 [25] subclause 4.2 with the=0D=0Afollowing considerations:=0D=0A- VOH=

 and VOL always refer to the device (ME or SIM) which is driving the interfa=

ce. VIH and VIL=0D=0Aalways refer to the device (ME or SIM) which is operati=

ng as a receiver on the interface.=0D=0A- This convention is different to th=

e one used in ISO/IEC 7816-3 [25] which specifically defines an=0D=0AICC fo=

r which its current conventions apply. The following clauses define the spec=

ific core=0D=0Arequirements for the SIM which provide also the basis for Ty=

pe Approval. For each state (VOH VIH=0D=0AVIL and VOL) a positive current =

is defined as flowing out of the entity (ME or SIM) in that state.=0D=0A- Th=

e high current options of ISO/IEC 7816-3 [25] for VIH and VOH are not specif=

ied for the SIM as=0D=0Athey apply to NMOS technology requirements. No reali=

sation of the SIM using NMOS is foreseen.=0D=0A5.1 Supply voltage Vcc (conta=

ct C1)=0D=0AThe SIM shall be operated within the following limits:=0D=0ATabl=

e 1: Electrical characteristics of Vcc under normal operating conditions=0D=

=0ASymbol Minimum Maximum Unit=0D=0AVcc 45 55 V=0D=0AIcc 10 mA=0D=0AThe cu=

rrent consumption of the SIM shall not exceed the value given in table 1 at =

any frequency accepted=0D=0Aby the SIM.=0D=0AWhen the SIM is in idle state (=

see below) the current consumption of the card shall not exceed 200 =B5A at =

1=0D=0AMHz and 25=B0C.=0D=0AThe ME shall source the maximum current requirem=

ents defined above. It shall also be able to counteract=0D=0Aspikes in the c=

urrent consumption of the card up to a maximum charge of 40 nAs with no more=

 than 400 ns=0D=0Aduration and an amplitude of at most 200 mA ensuring that=

 the supply voltage stays in the specified range.=0D=0ANOTE: A possible solu=

tion would be to place a capacitor (e.g. 100 nF ceramic) as close as=0D=0Ap=

ossible to the contacting elements.=0D=0APage 16=0D=0AGSM 11.11 Version 5.0.=

0 December 1995=0D=0A5.2 Reset (RST) (contact C2)=0D=0AThe ME shall operate =

the SIM within the following limits:=0D=0ATable 2: Electrical characteristic=

s of RST under normal operating conditions=0D=0ASymbol Conditions Minimum Ma=

ximum=0D=0AVOH IOHmax =3D +20=B5A Vcc-07 Vcc (note)=0D=0AVOL IOLmax =3D -20=

0 =B5A 0V (note) 06V=0D=0AtR tF Cout =3D Cin =3D 30pF 400=B5s=0D=0ANOTE: To=

 allow for overshoot the voltage on RST shall remain=0D=0Abetween -03V and =

Vcc+03V during dynamic operation.=0D=0A5.3 Programming voltage Vpp (contact=

 C6)=0D=0ASIMs shall not require any programming voltage on Vpp. The ME need=

 not provide contact C6. If the ME=0D=0Aprovides contact C6 then in the ca=

se of the ID-1 SIM the same voltage shall be supplied on Vpp as on=0D=0AVcc=

 while in the case of Plug-in SIMs the ME need not provide any voltage on C6=

. Contact C6 may be=0D=0Aconnected to Vcc in any ME but shall not be connect=

ed to ground.=0D=0A5.4 Clock CLK (contact C3)=0D=0AThe SIM shall support 1 t=

o 5 MHz. The clock shall be supplied by the ME. No "internal clock" SIMs sha=

ll be=0D=0Aused.=0D=0AIf a frequency of 13/4 MHz is needed by the SIM to run=

 the authentication procedure in the allotted time=0D=0A(see TS GSM 03.20 [1=

0]) bit 2 of byte 1 in the directory characteristics shall be set to 1. Oth=

erwise a=0D=0Aminimum frequency of 13/8 MHz may be used.=0D=0AThe duty cycle=

 shall be between 40% and 60% of the period during stable operation.=0D=0ATh=

e ME shall operate the SIM within the following limits:=0D=0ATable 3: Electr=

ical characteristics of CLK under normal operating conditions=0D=0ASymbol Co=

nditions Minimum Maximum=0D=0AVOH IOHmax =3D +20=B5A 07xVcc Vcc (note)=0D=

=0AVOL IOLmax =3D -200 =B5A 0V (note) 05V=0D=0AtR tF Cout =3D Cin =3D 30pF =

9 % of period with a maximum=0D=0Aof 05=B5s=0D=0ANOTE: To allow for oversho=

ot the voltage on CLK shall remain between -03V=0D=0Aand Vcc+03V during dy=

namic operation.=0D=0A5.5 I/O (contact C7)=0D=0ATable 4 defines the electric=

al characteristics of the I/O (contact C7). The values given in the table ha=

ve the=0D=0Aeffect of defining the values of the pull-up resistor in the ME =

and the impedances of the drivers and=0D=0Areceivers in the ME and SIM.=0D=

=0APage 17=0D=0AGSM 11.11 Version 5.0.0 December 1995=0D=0ATable 4: Electric=

al characteristics of I/O under normal operating conditions=0D=0ASymbol Cond=

itions Minimum Maximum=0D=0AVIH IIHmax =3D =B120=B5A (note 2) 07xVcc Vcc+0=

3V=0D=0AVIL IILmax =3D +1mA -03V 08V=0D=0AVOH (note 1) IOHmax =3D +20=B5A =

38V Vcc (note 3)=0D=0AVOL IOLmax =3D -1mA 0V (note 3) 04V=0D=0AtR tF Cout =

=3D Cin =3D 30pF 1=B5s=0D=0ANOTE 1: It is assumed that a pull-up resistor is=

 used in the interface device=0D=0A(recommended value: 20kohms).=0D=0ANOTE 2=

: During static conditions (idle state) only the positive value can apply.=

=0D=0AUnder dynamic operating conditions (transmission) short term voltage=

=0D=0Aspikes on the I/O line may cause a current reversal.=0D=0ANOTE 3: To a=

llow for overshoot the voltage on I/O shall remain between -03V and=0D=0AVc=

c+03V during dynamic operation.=0D=0A5.6 States=0D=0AThere are two states f=

or the SIM while the power supply is on:=0D=0A- The SIM is in operating stat=

e when it executes a command. This state also includes transmission=0D=0Afro=

m and to the ME.=0D=0A- The SIM is in idle state at any other time. It shall=

 retain all pertinent data during this state.=0D=0AThe SIM may support a clo=

ck stop mode. The clock shall only be switched off subject to the conditions=

=0D=0Aspecified in the directory characteristics (see clause 9).=0D=0AClock =

stop mode. An ME of Phase 2 or later shall wait at least five (5) elementary=

 time units after having=0D=0Areceived the last bit of the response before i=

t switches off the clock (if it is allowed to do so). It shall wait=0D=0Aat =

least two (2) elementary time units before it sends the first command after =

having started the clock.=0D=0ATo achieve phase compatibility the following=

 procedure shall be adhered to:=0D=0AA SIM of Phase 2 or later shall always =

send the status information "normal ending of the command" after=0D=0Athe su=

ccessful interpretation of the command SLEEP received from a Phase 1 ME. An =

ME of Phase 2 or=0D=0Alater shall not send a SLEEP command.=0D=0AA Phase 1 M=

E shall wait at least two (2) elementary time units after having received th=

e compulsory=0D=0Aacknowledgement SW1 SW2 of the SLEEP command before it swi=

tches off the clock (if it is allowed to do=0D=0Aso). It shall wait at least=

 two (2) elementary time units before it sends the first command after havin=

g=0D=0Astarted the clock.=0D=0A5.7 Baudrate=0D=0AThe baudrate for all commun=

ications shall be: (clock frequency)/372.=0D=0A5.8 Answer To Reset (ATR)=0D=

=0AThe ATR is information presented by the SIM to the ME at the beginning of=

 the card session and gives=0D=0Aoperational requirements.=0D=0A5.8.1 Struct=

ure and contents=0D=0AThe following table gives an explanation of the charac=

ters specified in ISO/IEC 7816-3 [25] and the=0D=0Arequirements for their us=

e in GSM. The answer to reset consists of at most 33 characters. The ME shal=

l=0D=0APage 18=0D=0AGSM 11.11 Version 5.0.0 December 1995=0D=0Abe able to re=

ceive interface characters for transmission protocols other than T=3D0 hist=

orical characters and=0D=0Aa check byte even if only T=3D0 is used by the M=

E.=0D=0ATable 5: ATR=0D=0ACharacter Contents sent by=0D=0Athe card=0D=0Aa) e=

valuation by the ME=0D=0Ab) reaction by the ME=0D=0A1. Initial=0D=0Acharacte=

r=0D=0ATS=0D=0Acoding convention for all=0D=0Asubsequent characters=0D=0A(di=

rect or inverse=0D=0Aconvention)=0D=0Aalways a) always=0D=0Ab) using appropr=

iate convention=0D=0A2. Format=0D=0Acharacter=0D=0AT0=0D=0Asubsequent interf=

ace=0D=0Acharacters number of=0D=0Ahistorical characters=0D=0Aalways a) alw=

ays=0D=0Ab) identifying the subsequent=0D=0Acharacters accordingly=0D=0A3. I=

nterface=0D=0Acharacter=0D=0A(global)=0D=0ATA1=0D=0Aparameters to calculate=

=0D=0Athe work etu=0D=0Aoptional a) always if present=0D=0Ab) if TA1 is not =

'11' PTS procedure=0D=0Ashall be used (see subclause 5.8.2)=0D=0A4. Interfa=

ce=0D=0Acharacter=0D=0A(global)=0D=0ATB1=0D=0Aparameters to calculate=0D=0At=

he programming voltage=0D=0Aand current=0D=0Aoptional a) always if present=

=0D=0Ab) if PI1 is not 0 then reject the SIM=0D=0A(in accordance with subcl=

ause 5.10)=0D=0A5. Interface=0D=0Acharacter=0D=0A(global)=0D=0ATC1=0D=0Apara=

meters to calculate=0D=0Athe extra guardtime=0D=0Arequested by the card; no=

=0D=0Aextra guardtime is used to=0D=0Asend characters from the=0D=0Acard to =

the ME=0D=0Aoptional a) always if present=0D=0Ab) if TC1 is neither 0 nor 25=

5 then=0D=0Areject the SIM (in accordance with=0D=0Asubclause 5.10); see th=

e note after=0D=0Athe table=0D=0A6. Interface=0D=0Acharacter=0D=0ATD1=0D=0Ap=

rotocol type; indicator=0D=0Afor the presence of interface=0D=0Acharacters=

=0D=0Aspecifying rules to be=0D=0Aused for transmissions=0D=0Awith the given=

 protocol=0D=0Atype=0D=0Aoptional a) always if present=0D=0Ab) identifying t=

he subsequent=0D=0Acharacters accordingly=0D=0A7. Interface=0D=0Acharacter=

=0D=0A(specific)=0D=0ATA2=0D=0Anot used for protocol T=3D0 optional a) optio=

nal=0D=0Ab) --------=0D=0A8. Interface=0D=0Acharacter=0D=0A(global)=0D=0ATB2=

=0D=0Aparameter to calculate=0D=0Athe programming voltage=0D=0Anever the all=

owed value of TB1 above=0D=0Adefines that an external=0D=0Aprogramming volta=

ge is not=0D=0Aapplicable=0D=0A9. Ine given protocol=0D=

=0Atype=0D=0Aoptional a) always if present=0D=0Ab) identifying the subsequen=

t=0D=0Acharacters accordingly=0D=0APage 19=0D=0AGSM 11.11 Version 5.0.0 Dece=

mber 1995=0D=0ATable 5: ATR (concluded)=0D=0ACharacter Contents sent by=0D=

=0Athe card=0D=0Aa) evaluation by the ME=0D=0Ab) reaction by the ME=0D=0A11.=

 Interface=0D=0Acharacter=0D=0ATAi TBi TCi=0D=0A(i>2)=0D=0Acharacters whic=

h contain=0D=0Ainterface characters for=0D=0Aother transmission=0D=0Aprotoco=

ls=0D=0Aoptional a) optional=0D=0Ab) --------=0D=0A12. Historical=0D=0Achara=

cters=0D=0AT1

.TK=0D=0Acontents not specified in=0D=0AISO/IEC=0D=0Aoption=

al a) optional=0D=0Ab) --------=0D=0A13. Check=0D=0Acharacter=0D=0ATCK=0D=

=0Acheck byte (exclusive -=0D=0AORing)=0D=0Anot sent if=0D=0Aonly T=3D0 is=

=0D=0Aindicated in=0D=0Athe ATR; in=0D=0Aall other=0D=0Acases TCK=0D=0Ashall=

 be=0D=0Asent=0D=0Aa) optional=0D=0Ab as follows:=0D=

=0Aa) for MEs only supporting default speed (F=3D372 D=3D1)=0D=0A=C9=CD=CD=

=BB Reset =C9=CD=CD=CD=BB=0D=0A=BAME=BA =C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=

=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=

=C4=C4=C4=C4=C4> =BASIM=BA=0D=0A=C8=CD=CD=BC =C8=CD=CD=CD=BC=0D=0AATR=0D=0A<=

=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=

=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4 TA1 not '11'=0D=0A=DA=C4=C4=C4=

=C4=C4=C2=C4=C4=C4=C4=BF=0D=0A=B3PTSS=3D=B3'FF'=B3 PTS Request=0D=0A=B3PTS0=

=3D=B3'00'=C3=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=

=C4=C4=C4=C4=C4=C4=C4=C4=C4>=0D=0A=B3PCK =3D=B3'FF'=B3=0D=0A=C0=C4=C4=C4=C4=

=C4=C1=C4=C4=C4=C4=D9=0D=0A=DA=C4=C4=C4=C4=C4=C2=C4=C4=C4=C4=BF=0D=0APTS Res=

ponse =B3PTSS=3D=B3'FF'=B3=0D=0A<=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=

=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=B4PTS0=3D=B3'00'=B3=0D=0A=B3PC=

K =3D=B3'FF'=B3=0D=0A=C0=C4=C4=C4=C4=C4=C1=C4=C4=C4=C4=D9=0D=0AFigure 1: PTS=

 procedure=0D=0APTS Request and PTS Response consist of the three (3) charac=

ters PTSS PTSO and PCK of which=0D=0APTSS is sent first.=0D=0AAfter this pr=

ocedure the protocol T=3D0 and the parameters F=3D372 D=3D1 and N=3D0 will =

be used.=0D=0Ab) for MEs only supporting enhanced speed (F=3D512 D=3D8)=0D=

=0APage 20=0D=0AGSM 11.11 Version 5.0.0 December 1995=0D=0A=C9=CD=CD=BB Rese=

t =C9=CD=CD=CD=BB=0D=0A=BAME=BA =C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=

=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=

=C4=C4> =BASIM=BA=0D=0A=C8=CD=CD=BC =C8=CD=CD=CD=BC=0D=0AATR=0D=0A<=C4=C4=

=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=

=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4 TA1 =3D '94'=0D=0A=DA=C4=C4=C4=C4=C4=

=C2=C4=C4=C4=C4=BF=0D=0A=B3PTSS=3D=B3'FF'=B3 PTS Request=0D=0A=B3PTS0=3D=B3'=

10'=C3=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=

=C4=C4=C4=C4=C4=C4>=0D=0A=B3PTS1=3D=B3'94'=B3=0D=0A=B3PCK =3D=B3'7B'=B3=0D=

=0A=C0=C4=C4=C4=C4=C4=C1=C4=C4=C4=C4=D9=0D=0A=DA=C4=C4=C4=C4=C4=C2=C4=C4=C4=

=C4=BF=0D=0APTS Response =B3PTSS=3D=B3'FF'=B3=0D=0A<=C4=C4=C4=C4=C4=C4=C4=

=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C

and the parameters F=3D512 D=3D8 and N=3D0 will be used.=0D=0A5.8.3 Speed e=

nhancement=0D=0AIf speed enhancement is implemented the ME and the SIM shall=

 at least support F=3D512 and D=3D8 in=0D=0Aaddition to F=3D372 and D=3D1. H=

owever other values may also be supported. If the ME requests PTS using=0D=

=0Avalues other than those above then the PTS procedure shall be initiated a=

ccordingly.=0D=0AThe SIM shall support the default value (F=3D372 and D=3D1)=

. If the speed enhancement is supported by the=0D=0ASIM it is mandatory that=

 F=3D512 and D=3D8 is supported. However the value in TA1 may even indicate=

 a=0D=0Afaster speed (F=3D512 and D=3D16). The SIM may also support other va=

lues between the default value=0D=0A(F=3D372 and D=3D1) and the values indic=

ated in TA1. The SIM shall offer the negotiable mode to ensure=0D=0Abackwar=

ds compatibility with exing MEs. In the negotiable mode the SIM will use def=

ault values even if=0D=0Aother parameters are offered in the ATR if the PTS =

procedure is not initiated.=0D=0AThe ME shall support the default value (F=

=3D372 and D=3D1). If the speed enhancement is supported in the ME=0D=0Ait i=

s mandatory to support F=3D512 and D=3D8. The ME may additionally support ot=

her values.=0D=0AIf the SIM does not answer the PTS request within the initi=

al waiting time the ME shall reset the SIM. After=0D=0Atwo failed PTS attemp=

ts using F=3D512 and D=3D8 or values indicated in TA1 (no PTS response from=

 the=0D=0ASIM) the ME shall initiate PTS procedure using default values. If =

this also fails (no PTS response from the=0D=0ASIM) the ME may proceed using=

 default values without requesting PTS=0D=0AIf the SIM does not support the =

values requested by the ME the SIM shall respond to the PTS request=0D=0Ain=

dicating the use of default values.=0D=0A5.9 Bit/character duration and samp=

ling time=0D=0AThe bit/character duration and sampling time specified in ISO=

/IEC 7816-3 [25] subclauses 6.1.1 and=0D=0A6.1.2 are valid for all communi=

cations.=0D=0A5.10 Error handling=0D=0AFollowing receipt of an ATR which is=

 not in accordance with this specification e.g. because of forbidden=0D=0AA=

TR characters or too few bytes being transmitted the ME shall perform a Res=

et. The ME shall not reject=0D=0Athe SIM until at least three consecutive wr=

ong ATRs are received.=0D=0ADuring the transmission of the ATR and the proto=

col type selection the error detection and character=0D=0Arepetition proced=

ure specified in ISO/IEC 7816-3 [25] subclause 6.1.3 is optional for the M=

E. For the=0D=0Asubsequent transmission on the basis of T=3D0 this procedure=

 is mandatory for the ME.=0D=0APage 21=0D=0AGSM 11.11 Version 5.0.0 December=

 1995=0D=0AFor the SIM the error detection and character repetition procedur=

e is mandatory for all communications.=0D=0A6 Logical Model=0D=0AThis clause=

 describes the logical structure for a SIM the code associated with it and=

 the structure of files=0D=0Aused.=0D=0A6.1 General description=0D=0AFigure =

3 shows the general structural relationships which may exist between files. =

The files are organised=0D=0Ain a hierarchical structure and are of one of t=

hree types as defined below. These=0D=0Afiles may be either administrative o=

r application specific. The operating system=0D=0Ahandles the access to the =

data stored in different files.=0D=0A=C9=CD=CD=CD=CD=CD=CD=CD=CD=CD=CB=CD=

=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=

=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=BB=0D=0A=BA =

MF =BA =BA=0D=0A=BA =BA =C9=CD=CD=CD=CD=CD=CB=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=

=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=BB =BA=0D=0A=CC=CD=CD=

=CD=CD=CD=CD=CD=CD=CD=BC =BA DF2 =BA =DA=C4=C4=C4=C4=BF =BA =BA=0D=0A=BA =

=CC=CD=CD=CD=CD=CD=BC =B3 EF =B3 =BA =BA=0D=0A=BA =C9=CD=CD=CD=CD=CD=CB=CD=

=CD=CD=CD=CD=CA=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=

=CD=CD=BB =C0=C4=C4=C4=C4=D9 =BA =BA=0D=0A=BA =BA DF1 =BA =BA =BA =BA=0D=0A=

=BA =CC=CD=CD=CD=CD=CD=BC =C9=CD=CD=CD=CD=CD=CD=CB=CD=CD=CD=CD=CD=CD=CD=CD=

=CD=CD=CD=CD=BB =BA =DA=C4=C4=C4=C4=BF =BA =BA=0D=0A=BA =BA =BA DF11 =BA =

=C9=CD=CD=CD=CD=CD=CD=CD=BB =BA =BA =B3 EF =B3 =BA =BA=0D=0A=BA =BA =CC=CD=

=CD=CD=CD=CD=CD=BC =BA DF111 =BA =BA =BA =C0=C4=C4=C4=C4=D9 =BA =BA=0D=0A=

=BA =BA =C9=CD=CD=CD=CD=CD=CD=CB=CD=CA=CD=CD=CD=CD=CD=CD=CD=CD=BB=C8=CD=CD=

=CD=CD=CD=CD=CD=BC =BA =BA 

 =BA =BA=0D=0A=BA =BA =BA DF12 =BA =DA=C4=C4=

=C4=C4=BF =CC=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=BC =CC=CD=CD=CD=CD=CD=CD=CD=CD=

=CD=CD=BC =BA=0D=0A=BA =BA =CC=CD=CD=CD=CD=CD=CD=BC =B3 EF =B3 =BA =DA=C4=

=C4=C4=C4=BF =BA =BA=0D=0A=BA =BA =BA =C0=C4=C4=C4=C4=D9 =BA =B3 EF =B3 =BA =

=DA=C4=C4=C4=C4=BF =BA=0D=0A=BA =BA =C8=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=

=CD=CD=CD=CD=CD=BC =C0=C4=C4=C4=C4=D9 =BA =B3 EF =B3 =BA=0D=0A=BA =BA =BA =

=C0=C4=C4=C4=C4=D9 =BA=0D=0A=BA =C8=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=

=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=BC =BA=0D=

=0A=BA =DA=C4=C4=C4=C4=BF =DA=C4=C4=C4=C4=BF =BA=0D=0A=BA =B3 EF =B3 =B3 EF =

=B3 =BA=0D=0A=BA =C0=C4=C4=C4=C4=D9 =C0=C4=C4=C4=C4=D9 =BA=0D=0A=BA 

 =

=BA=0D=0A=C8=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=

=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=

=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=BC=0D=0AFigure 3: Organisation of memory=

=0D=0AFiles are composed of a header which is internally managed by the SIM=

 and optionally a body part. The=0D=0Ainformation of the header is related =

to the structure and attributes of the file and may be obtained by using=0D=

=0Athe commands GET RESPONSE or STATUS. This information is fixed during the=

 administrative phase. The=0D=0Abody part contains the data of the file.=0D=

=0A6.2 File identifier=0D=0AA file ID is used to address or identify each sp=

ecific file. The file ID consists of two bytes and shall be=0D=0Acoded in he=

xadecimal notation. They are specified in clause 10.=0D=0AThe first byte ide=

ntifies the type of file and for GSM is:=0D=0A- '3F': Master File;=0D=0A- '=

7F': Dedicated File;=0D=0A- '2F': Elementary File under the Master File;=0D=

=0A- '6F': Elementary File under a Dedicated File.=0D=0APage 22=0D=0AGSM 11.=

11 Version 5.0.0 December 1995=0D=0AFile IDs shall be subject to the followi=

ng conditions:=0D=0A- the file ID shall be assigned at the time of creation =

of the file concerned;=0D=0A- no two files under the same parent shall have =

the same ID;=0D=0A- a child and any parent either immediate or remote in th=

e hierarchy e.g. grandparent shall=0D=0Anever have the same file ID.=0D=

=0AIn this way each file is uniquely identified.=0D=0A6.3 Dedicated files=

=0D=0AA Dedicated File (DF) is a functional grouping of files consisting of =

itself and all those fi Master File (MF) and may coexist on a =

multi-application card.=0D=0A6.4 Elementary files=0D=0AAn Elementary File (E=

F) is composed of a header and a body part. The following three structures o=

f an EF=0D=0Aare used by GSM.=0D=0A6.4.1 Transparent EF=0D=0AAn EF with a tr=

ansparent structure consists of a sequence of bytes. When reading or updatin=

g the=0D=0Asequence of bytes to be acted upon is referenced by a relative a=

ddress (offset) which indicates the start=0D=0Aposition (in bytes) and the=

 number of bytes to be read or updated. The first byte of a transparent EF h=

as=0D=0Athe relative address '00 00'. The total data length of the body of t=

he EF is indicated in the header of the=0D=0AEF.=0D=0A=DA=C4=C4=C4=C4=C4=C4=

=C4=C4=C4=C4=C4=C4=C4=BF=0D=0AHeader =B3 =B3=0D=0A=C6=CD=CD=CD=CD=CD=CD=CD=

=CD=CD=CD=CD=CD=CD=B5=0D=0A=B3 =B3=0D=0ABody =B3 Sequence =B3=0D=0A=B3 of =

=B3=0D=0A=B3 bytes =B3=0D=0A=B3 =B3=0D=0A=B3 =B3=0D=0A=C0=C4=C4=C4=C4=C4=C4=

=C4=C4=C4=C4=C4=C4=C4=D9=0D=0AFigure 4: Structure of a transparent EF=0D=0AN=

OTE: This structure was previously referred to as "binary" in GSM.=0D=0A6.4.=

2 Linear fixed EF=0D=0AAn EF with linear fixed structure consists of a seque=

nce of records all having the same (fixed) length. The=0D=0Afirst record is =

record number 1. The length of a record as well as this value multiplied by =

the number of=0D=0Arecords are indicated in the header of the EF.=0D=0APage =

23=0D=0AGSM 11.11 Version 5.0.0 December 1995=0D=0A=DA=C4=C4=C4=C4=C4=C4=C4=

=C4=C4=C4=C4=C4=C4=BF=0D=0AHeader =B3 =B3=0D=0A=C6=CD=CD=CD=CD=CD=CD=CD=CD=

=CD=CD=CD=CD=CD=B5=0D=0ABody =B3 Record 1 =B3=0D=0A=C3=C4=C4=C4=C4=C4=C4=C4=

=C4=C4=C4=C4=C4=C4=B4=0D=0A=B3 Record 2 =B3=0D=0A=C3=C4=C4=C4=C4=C4=C4=C4=

=C4=C4=C4=C4=C4=C4=B4=0D=0A=B3 : =B3=0D=0A=B3 : =B3=0D=0A=C3=C4=C4=C4=C4=C4=

=C4=C4=C4=C4=C4=C4=C4=C4=B4=0D=0A=B3 Record n =B3=0D=0A=C0=C4=C4=C4=C4=C4=

=C4=C4=C4=C4=C4=C4=C4=C4=D9=0D=0AFigure 5: Structure of a linear fixed file=..=0D=0AThere are several methods to access records within an EF of this type:=

=0D=0A- absolutely using the record number;=0D=0A- when the record pointer i=

s not set it shall be possible to perform an action on the first or the=0D=

=0Alast record;=0D=0A- when the record pointer is set it shall be possible t=

o perform an action on this record the next=0D=0Arecord (unless the record =

pointer is set to the last record) or the previous record (unless the=0D=0Ar=

ecord pointer is set to the first record);=0D=0A- by identifying a record us=

ing pattern seek starting=0D=0A- forwards from the beginning of the file;=

=0D=0A- forwards from the record following the one at which the record point=

er is set (unless=0D=0Athe record pointer is set to the last record);=0D=0A-=

 backwards from the end of the file;=0D=0A- backwards from the record preced=

ing the one at which the record pointer is set (unless=0D=0Athe record point=

er is set to the first record).=0D=0AIf an action following selection of a r=

ecord is aborted then the record pointer shall remain set at the record=0D=

=0Aat which it was set prior to the action.=0D=0ANOTE 1: It is not possible=

 at present to have more than 255 records in a file of this type and=0D=

=0Aeach record cannot be greater than 255 bytes.=0D=0ANOTE 2: This structure=

 was previously referred to as "formatted" in GSM.=0D=0A6.4.3 Cyclic EF=0D=

=0ACyclic files are used for storing records in chronological order. When al=

l records have been used for=0D=0Astorage then the next storage of data sha=

ll overwrite the o record n. The last updated record containi=

ng the newest data is record number=0D=0A1 and the oldest data is held in r=

ecord number n.=0D=0A=DA=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=BF=0D=0AHead=

er =B3 =B3=0D=0A=C6=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=CD=B5=0D=0ABody =B3 =

Record 1 =B3=C4=C4=BF=0D=0A=C3=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=B4 =

=B3=0D=0A=B3 Record 2 =B3 =B3=0D=0A=C3=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=

=C4=B4 =B3=0D=0A=B3 : =B3 =B3=0D=0A=B3 : =B3 =B3=0D=0A=C3=C4=C4=C4=C4=C4=C4=

=C4=C4=C4=C4=C4=C4=C4=B4 =B3=0D=0A=B3 Record n =B3=C4=C4=D9=0D=0A=C0=C4=C4=

=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=C4=D9=0D=0AFigure 6: Structure of a cyclic fi=

le=0D=0APage 24=0D=0AGSM 11.11 Version 5.0.0 December 1995=0D=0AFor update o=

perations only PREVIOUS record shall be used. For reading operations the me=

thods of=0D=0Aaddressing are Next Previous Current and Record Number.=0D=

=0AAfter selection of a cyclic file (for either operation) the record point=

er shall address the record updated or=0D=0Aincreased last. If an action fol=

lowing selection of a record is aborted then the record pointer shall remai=

n=0D=0Aset at the record at which it was set prior to the action.=0D=0ANOTE:=

 It is not possible at present to have more than 255 records in a file of =

this type and=0D=0Aeach record cannot be greater than 255 bytes.=0D=0A6.5 M=

ethods for selecting a file=0D=0AAfter the Answer To Reset (ATR) the Master=

 File (MF) is implicitly selected and becomes the Current=0D=0ADirectory. Ea=

ch file may then be selected by using the SELECT function in accordance with=

 the following=0D=0Arules.=0D=0ASelecting a DF or the MF sets the Current Di=

rectory. After such a selection there is no current EF.=0D=0ASelecting an EF=

 sets the current EF and the Current Directory remains the DF or MF which is=

 the parent of=0D=0Athis EF. The current EF is always a child of the Current=

 Directory.=0D=0AAny application specific command shall only be operable if =

it is specific to the Current Directory.=0D=0AThe following files may be sel=

ected from the last selected file:=0D=0A- any file which is an immediate chi=

ld of the Current Directory;=0D=0A- any DF which is an immediate child of th=

e parent of the current DF;=0D=0A- the parent of the Current Directory;=0D=

=0A- the current DF;=0D=0A- the MF.=0D=0AThis means in particular that a DF =

shall be selected prior to the selection of any of its EFs. All selections=

=0D=0Aare made using the file ID.=0D=0AThe following figure gives the logica=

l structure for the GSM application. GSM defines only one level of DFs=0D=

=0Aunder the MF.=0D=0AFigure 7: Logical structure=0D=0AThe following table g=

ives the valid selections for GSM for the logical structure in figure 7. Res=

election of=0D=0Athe last selected file is also allowed but not shown.=0D=

=0APage 25=0D=0AGSM 11.11 Version 5.0.0 December 1995=0D=0ATable 6: File sel=

ection=0D=0ALast selected file Valid Selections=0D=0AMF=0D=0ADF1=0D=0ADF2=

=0D=0AEF1=0D=0AEF2=0D=0AEF3=0D=0AEF4=0D=0ADF1 DF2 EF1=0D=0AMF DF2 EF2=

=0D=0AMF DF1 EF3 EF4=0D=0AMF DF1 DF2=0D=0AMF DF1 DF2=0D=0AMF DF1 DF=

2 EF4=0D=0AMF DF1 DF2 EF3=0D=0A6.6 Reservation of file IDs=0D=0AIn addit=

ion to the identifiers used for the files specified in this TS the followin=

g file IDs are reserved for use=0D=0Aby GSM.=0D=0ADedicated Files:=0D=0A- ad=

ministrative use:=0D=0A'7F 4X';=0D=0A- operational use:=0D=0A'7F 10' (DFTELE=

COM) '7F 20' (DFGSM) '7F 21' (DFDCS1800) and '7F 2X' where X=0D=0Aranges=

 from '2' to 'F'.=0D=0AElementary files:=0D=0A- administrative use:=0D=0A'6F=

 XX' in the DFs '7F 4X';=0D=0A'6F 1X' in the DFs '7F 10' '7F 20' '7F 21';=

=0D=0A'2F 01' '2F EX' in the MF '3F 00';=0D=0A- operational use:=0D=0A'6F 2=

X' '6F 3X' '6F 4X' in '7F 10' and '7F 2X';=0D=0A'2F 1X' in the MF '3F 00'.=

=0D=0AIn all the above X ranges unless otherwise stated from '0' to 'F'.=

=0D=0A7 Security features=0D=0AThe security aspects of GSM are described in =

the normative references TS GSM 02.09 [4] and=0D=0ATS GSM 03.20 [10]. This c=

lause gives information related to security features supported by the SIM to=

=0D=0Aenable the following:=0D=0A- authentication of the subscriber identity=

 to the network;=0D=0A- data confidentiality over the air interface;=0D=0A- =

file access conditions.=0D=0A7.1 Authentication and cipher key generation pr=

ocedure=0D=0AThis subclause describes the authentication mechanism and ciphe=

r key generation which are invoked by=0D=0Athe network. For the specificatio=

n of the corresponding procedures across the SIM/ME interface see=0D=0Aclaus=

e 11.=0D=0AThe network sends a Random Number (RAND) to the MS. The ME passes=

 the RAND to the SIM in the=0D=0Acommand RUN GSM ALGORITHM. The SIM returns =

the values SRES and Kc to the ME which are derived=0D=0Ausing the algorithms=

 and processes given below. The ME sends SRES to the network. The network=

=0D=0Acompares this value with the value of SRES which it calculates for its=

elf. The comparison of these SRES=0D=0Avalues provides the authentication. T=

he value Kc is used by the ME in any future enciphered=0D=0Acommunications w=

ith the network until the next invocation of this mechanism.=0D=0APage 26=

=0D=0AGSM 11.11 Version 5.0.0 December 1995=0D=0AA subscriber authentication=

 key Ki is used in this procedure. This key Ki has a length of 128 bits and =

is=0D=0Astored within the SIM for use in the algorithms described below.=0D=

=0A7.2 Algorithms and processes=0D=0AThe names and parameters of the algorit=

hms supported by the SIM are defined in TS GSM 03.20 [10].=0D=0AThese are:=