hash stringlengths 32 32 | doc_id stringlengths 7 13 | section stringlengths 3 121 | content stringlengths 0 2.2M |
|---|---|---|---|
099e4bd0b61d814e89668f7c98053995 | 101 267 | 15 Security requirements | GSM 03.48 [24] specifies standardised methods of securing the content of application messages to and from the SIM Application Toolkit. If it is necessary to secure application messaging to Toolkit applications, then GSM 03.48 may be used. ETSI TS 101 267 V6.3.0 (1999-05) 57 (GSM 11.14 version 6.3.0 Release 1997) Annex ... |
1c4b4f087015eb6e69461ecdbc9d8f65 | 101 109 | 1 Scope | The present document defines an intermediate universal Geographical Area Description which subscriber applications or GSM services can use and the network can convert into an equivalent radio coverage map. For GSM services which involve the use of an "area", it can be assumed that in the majority of cases the Service R... |
1c4b4f087015eb6e69461ecdbc9d8f65 | 101 109 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document. • References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. • For a specific reference, subsequent revisions do not apply. • Fo... |
1c4b4f087015eb6e69461ecdbc9d8f65 | 101 109 | 3 Definitions and abbreviations | |
1c4b4f087015eb6e69461ecdbc9d8f65 | 101 109 | 3.1 Definitions | For the purposes of the present document, the following definitions apply: Service Requester: Entity, which uses the Geographical Area Description in any protocol to inform the network about a defined area |
1c4b4f087015eb6e69461ecdbc9d8f65 | 101 109 | 3.2 Abbreviations | In addition to those mentioned below, abbreviations used in the present document are listed in GSM 01.04. For the purposes of the present document, the following abbreviations apply: GAD Geographical Area Description GPS Global Positioning System WGS World Geodetic System ETSI TS 101 109 V6.0.0 (1999-04) 6 (GSM 03.32 v... |
1c4b4f087015eb6e69461ecdbc9d8f65 | 101 109 | 4 Reference system | The reference system chosen for the coding of locations is the World Geodetic System 1984, (WGS 84), which is also used by the Global Positioning System, (GPS). The origin of the WGS 84 co-ordinate system is the geometric centre of the WGS 84 ellipsoid. The ellipsoid is constructed by the rotation of an ellipse around ... |
1c4b4f087015eb6e69461ecdbc9d8f65 | 101 109 | 5 Shapes | The intention is to incorporate a number of different shapes, that can be chosen according to need. In this version only a minimum number of shapes are described. - Ellipsoid Point; - Ellipsoid point with uncertainty circle; - Polygon. Each shape is discussed individually. |
1c4b4f087015eb6e69461ecdbc9d8f65 | 101 109 | 5.1 Ellipsoid Point | The description of an ellipsoid point is that of a point on the surface of the ellipsoid, and consists of a latitude and a longitude. In practice, such a description can be used to refer to a point on Earth’s surface, or close to Earth’s surface, with the same longitude and latitude. No provision is made in this versio... |
1c4b4f087015eb6e69461ecdbc9d8f65 | 101 109 | 5.2 Ellipsoid point with uncertainty circle | The "ellipsoid point with uncertainty circle" is characterised by the co-ordinates of an ellipsoid point (the origin) and a distance r. It describes formally the set of points on the ellipsoid which are at a distance from the origin less than or equal to r, the distance being the geodesic distance over the ellipsoid, i... |
1c4b4f087015eb6e69461ecdbc9d8f65 | 101 109 | 5.3 Polygon | A polygon is an arbitrary shape described by an ordered series of points (in the example pictured in the drawing, A to E). The minimum number of points allowed is 3, and the maximum number of points allowed is 15. The points shall be connected in the order that they are given. A connecting line is defined as the line o... |
1c4b4f087015eb6e69461ecdbc9d8f65 | 101 109 | 6 Coding | |
1c4b4f087015eb6e69461ecdbc9d8f65 | 101 109 | 6.1 Point | The co-ordinates of an ellipsoid point are coded with an uncertainty of less than 3 metres The latitude is coded with 24 bits: 1 bit of sign and a number between 0 and 223-1 coded in binary on 23 bits. The relation between the coded number N and the range of (absolute) latitudes X it encodes is the following (X in degr... |
1c4b4f087015eb6e69461ecdbc9d8f65 | 101 109 | 6.2 Uncertainty | A method of describing the uncertainty has been sought which is both flexible (can cover wide differences in range) and efficient. The proposed solution makes use of a variation on the Binomial expansion. The uncertainty r, expressed in metres, is mapped to a number K, with the following formula: ( ) ( ) r C x K = + − ... |
1c4b4f087015eb6e69461ecdbc9d8f65 | 101 109 | 7.1 Overview | A bit string encoding a geographical description shall consist of the following parts: - Type of Shape; - Shape Description. Such a bit string is usually part of an information element. The structure of the information element (e.g., element identifier, length) depends on the protocol in which the message containing th... |
1c4b4f087015eb6e69461ecdbc9d8f65 | 101 109 | 7.2 Type of Shape | The Type of Shape information field identifies the type which is being coded in the Shape Description. The Type of Shape is coded as shown in table 2. Table 2: Coding of Type of Shape Bits 4 3 2 1 0 0 0 0 Ellipsoid Point 0 0 0 1 Ellipsoid point with uncertainty Circle 0 1 0 1 Polygon other values reserved for future us... |
1c4b4f087015eb6e69461ecdbc9d8f65 | 101 109 | 7.3 Shape description | The shape description consist of different elements. ETSI TS 101 109 V6.0.0 (1999-04) 11 (GSM 03.32 version 6.0.0 Release 1997) |
1c4b4f087015eb6e69461ecdbc9d8f65 | 101 109 | 7.3.1 Ellipsoid Point | The coding of a point is described in figure 5. 8 7 6 5 4 3 2 1 spare 0 0 0 0 S Degrees of latitude Degrees of longitude Octet 7 Octet 6 Octet 5 Octet 3 Octet 4 Octet 2 Octet 1 Figure 5: Shape description of a point S: Sign of latitude Bit value 0 North Bit value 1 South Degrees of latitude Bit 1 of octet 4 is the low ... |
1c4b4f087015eb6e69461ecdbc9d8f65 | 101 109 | 7.3.2 Ellipsoid Point with uncertainty Circle | 8 7 6 5 4 3 2 1 spare 0 0 0 1 Uncertainty code S Degrees of latitude Degrees of longitude Octet 8 Octet 7 Octet 6 Octet 5 Octet 3 Octet 4 Octet 2 Octet 1 0 spare Figure 6: Shape description of an ellipsoid point with uncertainty circle ETSI TS 101 109 V6.0.0 (1999-04) 13 (GSM 03.32 version 6.0.0 Release 1997) |
1c4b4f087015eb6e69461ecdbc9d8f65 | 101 109 | 7.3.3 Polygon | 8 7 6 5 4 3 2 1 Number of points 0 1 0 1 S1 Degrees of latitude of point 1 Degrees of longitude of point 1 Octet 7 Octet 6 Octet 5 Octet 3 Octet 4 Octet 2 Octet 1 Sn Degrees of latitude of point n Degrees of longitude of point n Octet 6n+1 Octet 6n Octet 6n-1 Octet 6n-3 Octet 6n-2 Octet 6n-4 Figure 7: Shape description... |
1cd66d8b61f499079a9ac82803e00899 | 101 181 | 1 Scope | The present document specifies the structure of the Secured Packets in a general format and in an implementation using the Short Message Service (SMS). Furthermore, the coding is specified for a set of common application commands within the secured packets. This set is a subset of commands specified in GSM 11.11 [5] an... |
1cd66d8b61f499079a9ac82803e00899 | 101 181 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document. • References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. • For a specific reference, subsequent revisions do not apply. • Fo... |
1cd66d8b61f499079a9ac82803e00899 | 101 181 | 2.1 Normative references | [1] GSM 01.04: "Digital cellular telecommunications system (Phase 2+); Abbreviations and acronyms". [2] GSM 02.48: "Digital cellular telecommunications system (Phase 2+); Security Mechanisms for the SIM Application Toolkit - Stage 1". [3] GSM 03.40: "Digital cellular telecommunications system (Phase 2+); Technical real... |
1cd66d8b61f499079a9ac82803e00899 | 101 181 | 2.2 Informative references | [20] Schneier, Bruce: "Applied Cryptography Second Edition: Protocols, Algorithms and Source code in C", John Wiley & Sons, 1996, ISBN 0-471-12845-7. |
1cd66d8b61f499079a9ac82803e00899 | 101 181 | 3 Definitions and abbreviations | For the purposes of the present document, the following definitions and abbreviations apply. |
1cd66d8b61f499079a9ac82803e00899 | 101 181 | 3.1 Definitions | For the purposes of the present document, the following definitions apply: Application Layer: The layer above the Transport Layer on which the Application Messages are exchanged between the Sending and Receiving Applications. Application Message: The package of commands or data sent from the Sending Application to the ... |
1cd66d8b61f499079a9ac82803e00899 | 101 181 | 3.2 Abbreviations | In addition to those below, abbreviations used in the present document are listed in GSM 01.04. CBC Cipher Block Chaining CC Cryptographic Checksum CNTR Counter CHI Command Header Identifier CHL Command Header Length CPI Command Packet Identifier CPL Command Packet Length DES Data Encryption Standard DS Digital Signatu... |
1cd66d8b61f499079a9ac82803e00899 | 101 181 | 4 Overview of Security System | An overview of the secure communication related to the SIM Application Toolkit together with the required security mechanisms is given in GSM 02.48 [2], (see figure 1). Sending Application Sending Entity Transport Mech. Receiving Entity Receiving Application Security Security Information flow (e.g. a bank) (e.g. SMS -S... |
1cd66d8b61f499079a9ac82803e00899 | 101 181 | 5 Generalised Secured Packet structure | Command and Response Packets have the same overall structure consisting of a variable length security header within a variable length shell. To model this, use is made of a double TLV -tag, length, value- structure. |
1cd66d8b61f499079a9ac82803e00899 | 101 181 | 5.1 Command Packet structure | The Command Header precedes the Secured Data in the Command Packet, and is of variable length. The Command Packet shall be structured according to table 1. Table 1: Structure of the Command Packet Element Length Comment Command Packet Identifier (CPI) 1 octet Identifies that this data block is the secured Command Packe... |
1cd66d8b61f499079a9ac82803e00899 | 101 181 | 5.1.4 Counter Management | The following rules shall apply to counter management: - The SE sets the counter value. It shall only be incremented. - When the counter value reaches its maximum value the counter is blocked . - In order to prevent replay attacks the RE shall increment the counter to its next value upon receipt of a Command Packet irr... |
1cd66d8b61f499079a9ac82803e00899 | 101 181 | 5.2 Response Packet structure | Table 3: Structure of the Response Packet Element Length Comment Response Packet Identifier (RPI) 1 octet Identifies a Response Packet. Response Packet Length (RPL) variable Indicates the number of octets from and including RHI to the end of Additional Response data, including any padding octets. Response Header Identi... |
1cd66d8b61f499079a9ac82803e00899 | 101 181 | 6 Implementation for SMS | 6.1 Structure of the UDH of the Security Header in a Short Message The coding of the SMS-DELIVER, SMS-SUBMIT, SMS-DELIVER-REPORT or SMS-SUBMIT-REPORT header shall indicate that the data is binary (8 bit), and not 7 bit or 16 bit. In order to invoke the UDH functionality of relevant SMS element, the UDHI bit shall be se... |
1cd66d8b61f499079a9ac82803e00899 | 101 181 | 6.2 A Command Packet contained in a Single Short Message | The relationship between the Command Packet and its inclusion in the UDH structure of a single Short Message with no other UDH elements is indicated in table 6. Table 6: Relationship of Command Packet in UDH for single Short Message SMS specific elements Generalised Command Packet Elements (Refer to Table 1) Comments U... |
1cd66d8b61f499079a9ac82803e00899 | 101 181 | 6.4 Structure of the Response Packet | The Response Packet is as follows. This message is generated by the Receiving Entity and possibly includes some data supplied by the Receiving Application, and returned to the Sending Entity/Sending Application. In the case where the Receiving Entity is the SIM, depending on bit 6 of the second octet of the SPI, this R... |
1cd66d8b61f499079a9ac82803e00899 | 101 181 | 7.1 Behaviour of the Remote File Management Application | 1. The parameter(s) in the SIM Data Download Message is either a single command, or a list of commands, which shall be processed sequentially. 2. The application shall take parameters from the SIM Data Download message and shall act upon the GSM files according to these parameters. 3. A Command "session" is defined as ... |
1cd66d8b61f499079a9ac82803e00899 | 101 181 | 7.2 Coding of the commands | A command string may contain a single command or a sequence of commands. Each command is coded according to the generalised structure defined below; each element other than the Data field is a single octet; see GSM 11.11 [5]. Class byte (CLA) Instruction code (INS) P1 P2 P3 Data |
1cd66d8b61f499079a9ac82803e00899 | 101 181 | 7.2.1 Class 1 Commands | The standardised commands are listed in table 9. The commands are as defined in GSM 11.11 [5], except that the SELECT command is extended from the one in GSM 11.11 [5] to include "SELECT by path" as defined in ISO/IEC 7816-4 [7]. The following list of commands require a Class 1 implementation of the SIM Application Too... |
1cd66d8b61f499079a9ac82803e00899 | 101 181 | 7.2.2 Class 2 Commands | The list of commands contained in table 10 require a Class 2 implementation of the SIM Application Toolkit. If SMS is being used, these should result in the generation of a single SM by the SIM application containing the relevant data as a result of executing these commands. Table 10: Class 2 commands Operational comma... |
1cd66d8b61f499079a9ac82803e00899 | 101 181 | 7.3 SIM specific behaviour for Response Packets (Using SMS) | Table 11 summarises the behaviour of the SIM’s RE/RA with regard to PoR if the SMS-DELIVER REPORT is used. ETSI ETSI TS 101 181 V7.0.1 (1999-07) 19 (GSM 03.48 version 7.0.1 Release 1998) Table 11: SIM specific behaviour PoR successful case Unsuccessful cases (see table 5) No '90 00' or '91 XX', null RP-ACK '90 00' or '... |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 1 Scope | The present document defines the interface between the Subscriber Identity Module (SIM) and the Mobile Equipment (ME) for use during the network operation phase of GSM as well as those aspects of the internal organization of the SIM which are related to the network operation phase. This is to ensure interoperability be... |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 2 References | The following documents contain provisions which, through reference in this text, constitute provisions of the present document. • References are either specific (identified by date of publication, edition number, version number, etc.) or non-specific. • For a specific reference, subsequent revisions do not apply. • Fo... |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 3 Definitions, abbreviations and symbols | |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 3.1 Definitions | For the purposes of the present document, the following terms and definitions apply. For further information and definitions refer to GSM 01.02 [1]. access conditions: set of security attributes associated with a file. application: application consists of a set of security mechanisms, files, data and protocols (excludi... |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 3.2 Abbreviations | For the purposes of the present document, the following abbreviations apply, in addition to those listed in GSM 01.04 [2]: A3 Algorithm 3, authentication algorithm; used for authenticating the subscriber A38 A single algorithm performing the functions of A3 and A8 A5 Algorithm 5, cipher algorithm; used for enciphering/... |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 3.3 Symbols | For the purposes of the present document, the following symbols apply: Vcc Supply voltage Vpp Programming voltage '0' to '9' and 'A' to 'F' The sixteen hexadecimal digits ETSI ETSI TS 100 977 V6.3.0 (2000-05) 14 (GSM 11.11 version 6.3.0 Release 1997) |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 4 Physical characteristics | Two physical types of SIM are specified. These are the "ID-1 SIM" and the "Plug-in SIM". The physical characteristics of both types of SIM shall be in accordance with ISO 7816-1,2 [24, 25] unless otherwise specified. The following additional requirements shall be applied to ensure proper operation in the GSM environmen... |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 4.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 (see clause 10, EFICCID). |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 4.1.1 ID-1 SIM | Format and layout of the ID-1 SIM shall be in accordance with ISO 7816-1 [24] and ISO 7816-2 [25]. The card shall have a polarization mark (see GSM 02.07 [3]) which indicates how the user should insert the card into the ME. The ME shall accept embossed ID-1 cards. The embossing shall be in accordance with ISO/IEC 7811 ... |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 4.1.2 Plug-in SIM | The 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 feature for orientation. See figure A.1 in normative annex A for details of the dimensions of the card and the dimensions and location of the contacts. Annexes A.1 and A.2 of ISO 7816-1 [24] do not apply to the Plug-in SI... |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 4.2 Temperature range for card operation | The temperature range for full operational use shall be between -25°C and +70°C with occasional peaks of up to +85°C. "Occasional" means not more than 4 hours each time and not over 100 times during the life time of the card. |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 4.3 Contacts | |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 4.3.1 Provision of contacts | ME: Contacting elements in the ME in positions C4 and C8 are optional, and are not used in the GSM application. They shall present a high impedance to the SIM card in the GSM application. If it is determined that the SIM is a multi-application ICC, then these contacts may be used. Contact C6 need not be provided for Pl... |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 4.3.2 Activation and deactivation | The ME shall connect, activate and deactivate the SIM in accordance with the Operating Procedures specified in ISO/IEC 7816-3 [26]. For any voltage level, monitored during the activation sequence, or during the deactivation sequence following soft power-down, the order of the contact activation/deactivation shall be re... |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 4.3.3 Inactive contacts | The voltages on contacts C1, C2, C3, C6 and C7 of the ME shall be between 0 and ± 0,4 volts referenced to ground (C5) when the ME is switched off with the power source connected to the ME. The measurement equipment shall have a resistance of 50 kohms when measuring the voltage on C2, C3, C6 and C7. The resistance shall... |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 4.3.4 Contact pressure | The contact pressure shall be large enough to ensure reliable and continuous contact (e.g. to overcome oxidisation and to prevent interruption caused by vibration). The radius of any curvature of the contacting elements shall be greater than or equal to 0,8 mm over the contact area. Under no circumstances may a contact... |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 4.4 Precedence | For Mobile Equipment, which accepts both an ID-1 SIM and a Plug-in SIM, the ID-1 SIM shall take precedence over the Plug-in SIM (see GSM 02.17 [6]). |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 4.5 Static Protection | Considering that the SIM is a CMOS device, the ME manufacturer shall take adequate precautions (in addition to the protection diodes inherent in the SIM) to safeguard the ME, SIM and SIM/ME interface from static discharges at all times, and particularly during SIM insertion into the ME. ETSI ETSI TS 100 977 V6.3.0 (200... |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 5 Electronic signals and transmission protocols | Electronic signals and transmission protocols shall be in accordance with ISO/IEC 7816-3 [26] unless specified otherwise. The following additional requirements shall be applied to ensure proper operation in the GSM environment. The choice of the transmission protocol(s), to be used to communicate between the SIM and th... |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 5.1 Supply voltage Vcc (contact C1) | The SIM shall be operated within the following limits: Table 1: Electrical characteristics of Vcc under normal operating conditions Symbol Minimum Maximum Unit Vcc 4,5 5,5 V Icc 10 mA The current consumption of the SIM shall not exceed the value given in table 1 during any state (including activation and deactivation a... |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 5.2 Reset (RST) (contact C2) | The ME shall operate the SIM within the following limits: Table 2: Electrical characteristics of RST under normal operating conditions Symbol Conditions Minimum Maximum VOH IOHmax = +20 µA Vcc-0,7 Vcc (note) VOL IOLmax = -200 µA 0V (note) 0,6 V tR tF Cout = Cin = 30 pF 400 µs NOTE: To allow for overshoot the voltage on... |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 5.3 Programming voltage Vpp (contact C6) | SIMs shall not require any programming voltage on Vpp. The ME need not provide contact C6. If the ME provides contact C6, then, in the case of the ID-1 SIM the same voltage shall be supplied on Vpp as on Vcc, while in the case of Plug-in SIMs the ME need not provide any voltage on C6. Contact C6 may be connected to Vcc... |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 5.4 Clock CLK (contact C3) | The SIM shall support 1 MHz to 5 MHz. The clock shall be supplied by the ME. No "internal clock" SIMs shall be used. If a frequency of 13/4 MHz is needed by the SIM to run the authentication procedure in the allotted time (see GSM 03.20 [11]), or to process an ENVELOPE command used for SIM Data Download, bit 2 of byte ... |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 5.5 I/O (contact C7) | Table 4 defines the electrical characteristics of the I/O (contact C7). The values given in the table have the effect of defining the values of the pull-up resistor in the ME and the impedances of the drivers and receivers in the ME and SIM. Table 4: Electrical characteristics of I/O under normal operating conditions S... |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 5.6 States | There are two states for the SIM while the power supply is on: - the SIM is in operating state when it executes a command. This state also includes transmission from and to the ME; - the SIM is in idle state at any other time. It shall retain all pertinent data during this state. ETSI ETSI TS 100 977 V6.3.0 (2000-05) 1... |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 5.7 Baudrate | The initial baudrate (during ATR) shall be: (clock frequency)/372. Subsequent baudrate shall be: (clock frequency)/372 unless the PTS procedure has been successfully performed. In that case the negotiated baudrate shall be applied according to subclause 5.8.2. |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 5.8 Answer To Reset (ATR) | The ATR is information presented by the SIM to the ME at the beginning of the card session and gives operational requirements. |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 5.8.1 Structure and contents | The following table gives an explanation of the characters specified in ISO/IEC 7816-3 [26] and the requirements for their use in GSM. The answer to reset consists of at most 33 characters. The ME shall be able to receive interface characters for transmission protocols other than T=0, historical characters and a check ... |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 5.8.2 PTS procedure | Specifically related to the present document the PTS procedure according to ISO/IEC 7816-3 [26], clause 7, is applied, only if TA1 is not equal to '11', as follows: a) for MEs only supporting default speed (F=372, D=1) ME ————————————— Reset —————————————> SIM <————————————— ATR —————————————— TA1 not = '11' PTSS = 'FF... |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 5.8.3 Speed enhancement | If speed enhancement is implemented, the ME and the SIM shall at least support F=512 and D=8 in addition to F=372 and D=1. However, other values may also be supported. If the ME requests PTS using values other than those above then the PTS procedure shall be initiated accordingly. The SIM shall support the default valu... |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 5.9 Bit/character duration and sampling time | The bit/character duration and sampling time specified in ISO/IEC 7816-3 [26], subclauses 6.1.1 and 6.1.2, are valid for all communications. |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 5.10 Error handling | Following receipt of an ATR, which is not in accordance with the present document, e.g. because of forbidden ATR characters or too few bytes being transmitted, the ME shall perform a Reset. The ME shall not reject the SIM until at least three consecutive wrong ATRs are received. During the transmission of the ATR and t... |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 6 Logical Model | This clause describes the logical structure for a SIM, the code associated with it, and the structure of files used. |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 6.1 General description | Figure 3 shows the general structural relationships which may exist between files. The files are organized in a hierarchical structure and are of one of three types as defined below. These files may be either administrative or application specific. The operating system handles the access to the data stored in different... |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 6.2 File identifier | A file ID is used to address or identify each specific file. The file ID consists of two bytes and shall be coded in hexadecimal notation. They are specified in clause 10. The first byte identifies the type of file, and for GSM is: - '3F': Master File; - '7F': 1st level Dedicated File; - '5F': 2nd level Dedicated File;... |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 6.3 Dedicated files | A Dedicated File (DF) is a functional grouping of files consisting of itself and all those files which contain this DF in their parental hierarchy (that is to say it consists of the DF and its complete "subtree"). A DF "consists" only of a header part. ETSI ETSI TS 100 977 V6.3.0 (2000-05) 23 (GSM 11.11 version 6.3.0 R... |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 6.4 Elementary files | An Elementary File (EF) is composed of a header and a body part. The following three structures of an EF are used by GSM. |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 6.4.1 Transparent EF | An EF with a transparent structure consists of a sequence of bytes. When reading or updating, the sequence of bytes to be acted upon is referenced by a relative address (offset), which indicates the start position (in bytes), and the number of bytes to be read or updated. The first byte of a transparent EF has the rela... |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 6.4.2 Linear fixed EF | An EF with linear fixed structure consists of a sequence of records all having the same (fixed) length. The first record is record number 1. The length of a record as well as this value multiplied by the number of records are indicated in the header of the EF. Header Body Record 1 Record 2 : : Record n Figure 5: Struct... |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 6.4.3 Cyclic EF | Cyclic files are used for storing records in chronological order. When all records have been used for storage, then the next storage of data shall overwrite the oldest information. An EF with a cyclic structure consists of a fixed number of records with the same (fixed) length. In this file structure there is a link be... |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 6.5 Methods for selecting a file | After the Answer To Reset (ATR), the Master File (MF) is implicitly selected and becomes the Current Directory. Each file may then be selected by using the SELECT function in accordance with the following rules. Selecting a DF or the MF sets the Current Directory. After such a selection there is no current EF. Selectin... |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 6.6 Reservation of file IDs | In addition to the identifiers used for the files specified in the present document, the following file IDs are reserved for use by GSM. Dedicated Files: - administrative use: '7F 4X', '5F1X', '5F2X' - operational use: '7F 10' (DFTELECOM), '7F 20' (DFGSM), '7F 21' (DFDCS1800), '7F 22' (DFIS41), and '7F 2X', where X ran... |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 7 Security features | The security aspects of GSM are described in the normative references GSM 02.09 [4] and GSM 03.20 [11]. This clause gives information related to security features supported by the SIM to enable the following: - authentication of the subscriber identity to the network; - data confidentiality over the radio interface; - ... |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 7.1 Authentication and cipher key generation procedure | This subclause describes the authentication mechanism and cipher key generation which are invoked by the network. For the specification of the corresponding procedures across the SIM/ME interface see clause 11. The network sends a Random Number (RAND) to the MS. The ME passes the RAND to the SIM in the command RUN GSM ... |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 7.2 Algorithms and processes | The names and parameters of the algorithms supported by the SIM are defined in GSM 03.20 [11]. These are: - algorithm A3 to authenticate the MS to the network; ETSI ETSI TS 100 977 V6.3.0 (2000-05) 27 (GSM 11.11 version 6.3.0 Release 1997) - algorithm A8 to generate the encryption key. These algorithms may exist either... |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 7.3 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. For each file: - the access conditions for the commands READ and SEEK are identical; - the access conditions for the commands SELECT a... |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 8 Description of the functions | This clause gives a functional description of the commands and their respective responses. Associated status conditions, error codes and their corresponding coding are specified in clause 9. It shall be mandatory for all cards complying with the present document to support all functions described in the present documen... |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 8.1 SELECT | This function selects a file according to the methods described in clause 6. After a successful selection the record pointer in a linear fixed file is undefined. The record pointer in a cyclic file shall address the last record which has been updated or increased. Input: - file ID. Output: - if the selected file is the... |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 8.2 STATUS | This function returns information concerning the current directory. A current EF is not affected by the STATUS function. It is also used to give an opportunity for a pro-active SIM to indicate that the SIM wants to issue a SIM Application Toolkit command to the ME. Input: - none. Output: - file ID, total memory space a... |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 8.3 READ BINARY | This function reads a string of bytes from the current transparent EF. This function shall only be performed if the READ access condition for this EF is satisfied. Input: - relative address and the length of the string. Output: - string of bytes. |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 8.4 UPDATE BINARY | This function updates the current transparent EF with a string of bytes. This function shall only be performed if the UPDATE access condition for this EF is satisfied. An update can be considered as a replacement of the string already present in the EF by the string given in the update command. Input: - relative addres... |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 8.5 READ RECORD | This function reads one complete record in the current linear fixed or cyclic EF. The record to be read is described by the modes below. This function shall only be performed if the READ access condition for this EF is satisfied. The record pointer shall not be changed by an unsuccessful READ RECORD function. Four mode... |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 8.6 UPDATE RECORD | This function updates one complete record in the current linear fixed or cyclic EF. This function shall only be performed if the UPDATE access condition for this EF is satisfied. The UPDATE can be considered as a replacement of the relevant record data of the EF by the record data given in the command. The record point... |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 8.7 SEEK | This function searches through the current linear fixed EF to find a record starting with the given pattern. This function shall only be performed if the READ access condition for this EF is satisfied. Two types of SEEK are defined: Type 1 The record pointer is set to the record containing the pattern, no output is ava... |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 8.8 INCREASE | This function adds the value given by the ME to the value of the last increased/updated record of the current cyclic EF, and stores the result into the oldest record. The record pointer is set to this record and this record becomes record number 1. This function shall be used only if this EF has an INCREASE access cond... |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 8.9 VERIFY CHV | This function verifies the CHV presented by the ME by comparing it with the relevant one stored in the SIM. The verification process is subject to the following conditions being fulfilled: - CHV is not disabled; - CHV is not blocked. If the access condition for a function to be performed on the last selected file is CH... |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 8.10 CHANGE CHV | This function assigns a new value to the relevant CHV subject to the following conditions being fulfilled: - CHV is not disabled; - CHV is not blocked. The old and new CHV shall be presented. If the old CHV presented is correct, the number of remaining CHV attempts for that CHV shall be reset to its initial value 3 and... |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 8.11 DISABLE CHV | This function may only be applied to CHV1. The successful execution of this function has the effect that files protected by CHV1 are now accessible as if they were marked "ALWAYS". The function DISABLE CHV shall not be executed by the SIM when CHV1 is already disabled or blocked. If the CHV1 presented is correct, the n... |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 8.12 ENABLE CHV | This function may only be applied to CHV1. It is the reverse function of DISABLE CHV. The function ENABLE CHV shall not be executed by the SIM when CHV1 is already enabled or blocked. If the CHV1 presented is correct, the number of remaining CHV1 attempts shall be reset to its initial value 3 and CHV1 shall be enabled.... |
7cb4fd1069780e5630834ee9b5bf2c49 | 100 977 | 8.13 UNBLOCK CHV | This function unblocks a CHV which has been blocked by 3 consecutive wrong CHV presentations. This function may be performed whether or not the relevant CHV is blocked. If the UNBLOCK CHV presented is correct, the value of the CHV, presented together with the UNBLOCK CHV, is assigned to that CHV, the number of remainin... |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.