5 Specification of the MS-Subscriber Identity Module:

11.193GPPCTS SIM Fixed PartTS

GSM 11.11[11] applies for all GSM aspects that are not dedicated to CTS

5.1 Contents of the EFs at the DF CTS level

The EFs in the Dedicated File DFCTS contain CTS service related information.

5.1.1 EFCTS-FPRIP (CTS Fixed Part Radio and Identity Parameters)

This EF contains miscellaneous information which identify each CTS-MS/CTS-FP pair within a record. Two types of information are stored in the file:

Identity parameters:

– FPBI and IFPEI are used to identify a CTS-FP. IFPEI is transmitted by the CTS-FP to the CTS-MS during the enrolment for verification. FPBI is always transmitted by the beacon channel;

– CTS-MSI is a local number to identify a CTS-MS enrolled on a CTS-FP. The CTS-MSI is used when a identity request is sent by the CTS-FP;

– Ka is the CTS authentication key (refer to GSM 03.20, Annex E [5]).

Radio parameters:

– CTSBCH is used by the CTS-FP to allow synchronisation of CTS-MSs. The CTSBCH carrier frequency is issued from the CTS Generic Frequency List (see GSM 05.56, [11]);

– CTS_RXLEV_ACCESS_MIN is the minimum received signal level to access to a CTS-FP;

– CTS_MS_Max_TXPWR is the maximum authorized output power control level that the CTS-MS shall use with a CTS-FP.

Identifier: ‘4F01’

Structure: linear fixed

Mandatory

Record length: X +46 bytes

Update activity: low

Access Conditions:

READ CHV1

UPDATE CHV1

INVALIDATE ADM

REHABILITATE ADM

Bytes

Description

M/O

Length

1 to X

Alpha Identifier

O

X bytes

X+3

FPBI

M

3 bytes

X+19

IFPEI

M

16 bytes

X+22

CTS-MSI

M

3 bytes

X+38

Ka

M

16 bytes

X+40

CTSBCH ARFCN

M

2 bytes

X+41

CTS_RXLEV_ACCESS_MIN

M

1 byte

X+42

CTS_MS_Max_TXPWR

M

1 byte

X+46

Bytes reserved – see below

M

4 bytes

– Alpha Identifier

Contents: Alpha-tagging of the associated fixed part

Coding: see GSM 11.11 [10] (e.g., EF ADN).

– FPBI

Coding: As defined in GSM 03.03 [4]

– IFPEI

Coding: As defined in GSM 03.03 [4]

– CTS-MSI

Coding: As defined in GSM 03.03 [4]

– Ka

Coding: The least significant bit of Ka is the least significant bit of the sixteenth byte of the corresponding key. The most significant bit of Ka is the most significant bit of the first byte of the key.

– CTSBCH

Contents: CTS Beacon channel

Coding: Absolute Radio Frequency Channel Number as defined in GSM 05.05 [36].

– CTS_RXLEV_ACCESS_MIN

Coding: As defined in GSM 05.08 [10].

– CTS_MS_Max_TXPWR

Coding: As defined in GSM 05.05 [9].

– Bytes reserved shall be set to ‘FF’ and shall not be interpreted by the ME.

Annex A (informative):
Support of SIM Application Toolkit by CTS-FPE

For further study.

Annex B (informative):
Suggested contents of the CTS MS-SIM EF(s) at pre‑personalization

If EFs have an unassigned value, it may not be clear from the main text what this value should be. This annex suggests values in these cases.

File Identification

Description

Value

‘4F 01’

CTS FP RIP

‘FF…FF’

Annex C (informative):
Suggested contents of the CTS FP-SIM EF(s) at pre‑personalization

If EFs have an unassigned value, it may not be clear from the main text what this value should be. This annex suggests values in these cases.

File Identification

Description

Value

‘2F E2’

ICC identification

operator dependant (see GSM 11.11 [12])

‘6F 07’

IFPSI

operator dependant (see GSM 03.03 [4])

‘6F 38’

CTS Info

Phase: (see 6.7.2.2)

Services: operator dependant (see 6.7.2.2))

‘6F 41’

CTS Service Node Dialling Number

‘FF…FF’

‘6F 3D’

CTS Capability configuration parameters

‘FF…FF’

‘6F 4A’

CTS Extension

‘FF…FF’

‘6F 7B’

Permitted PLMNs

Status: operator dependant (see 6.7.2.6)

Permitted PLMNs: ‘FF…FF’

‘6F AD’

Administrative Data

Operator dependant (see6.7.2.7)