KR20130142505A

KR20130142505A - Method and apparatus of managing provisioning embedded uicc devices

Info

Publication number: KR20130142505A
Application number: KR1020120065779A
Authority: KR
Inventors: 이형진; 김관래; 박철현; 이진형
Original assignee: 주식회사 케이티
Priority date: 2012-06-19
Filing date: 2012-06-19
Publication date: 2013-12-30

Abstract

The present invention defines a provisioning profile and the MNO operation profile configuration to be included in the built-in UICC, and defines a procedure in which the terminal accesses the network using the provisioning profile and the MNO operation profile.

Description

Configuration of provisioning and MNO operation profiles stored in the built-in VIC and procedures for the terminal accessing the network using the same {METHOD AND APPARATUS OF MANAGING PROVISIONING EMBEDDED UICC DEVICES}

The present invention relates to a configuration for provisioning and MNO operation profiles stored in the built-in UICC, and a procedure for accessing a network by a terminal using the same.

A UICC (Universal Integrated Circuit Card) is a smart card inserted in a terminal and used as a module for user authentication and a mobile communication network subscribed by a user. UICC includes your personal information (SMS (Short Message Service), Phonebook, etc.) and your carrier information (IMSI (International Mobile Subscriber Identity), HPLMN (Home Public Land Mobile Network) Etc.) can be stored. The UICC is also called a Subscriber Identity Module (SIM) card in the case of the Global System for Mobile communications (GSM) scheme, and a Universal Subscriber Identity Module (USIM) card in the case of the Wideband Code Division Multiple Access (WCDMA) scheme.

When the user mounts the UICC on the user's terminal, user authentication is made with the mobile communication network that is automatically subscribed using the information stored in the UICC, and the user can conveniently use the terminal. In addition, when the user changes the terminal, the user can easily replace the terminal by attaching the UICC removed from the existing terminal to the new terminal. When the user wants to change the mobile communication provider, the user can easily change the mobile communication provider to receive the service by replacing the UICC removed from the existing terminal with the UICC of the corresponding operator.

However, when it is difficult to detach the UICC from the terminal, for example, when the UICC is mounted inside the machine to machine (M2M) terminal and manufactured in a structure that is difficult to replace from the outside, the UICC of the existing removable plastic structure In order to provide durability and resistance to shock and heat, an embedded UICC structure (eUICC) has been proposed to provide the same service as a removable UICC even when a chip-type terminal integrated structure is provided instead of a detachable structure.

Unlike the conventional detachable type UICC, the eUICC cannot change the mobile communication provider through the eUICC detachment due to the physical structure difference that the eUICC is mounted on the terminal in the manufacturing stage of the terminal and is not detached. Therefore, the eUICC needs a function of downloading a mobile operator's network access operation profile (operational profile) to be changed in the eUICC remotely in the eUICC to change the mobile operator.

An object of the present invention is to define a provisioning profile and MNO operation profile configuration to be included in the built-in UICC, and to provide a procedure for the terminal to access the network using the provisioning profile and the MNO operation profile.

According to an embodiment of the present invention, a provisioning profile and an MNO operation profile configuration to be included in a built-in UICC are defined, and a procedure for accessing a network by a terminal using a provisioning profile and an MNO operation profile is provided.

According to the present invention, a procedure of accessing a network to a terminal may be defined using configuration (structure) of provisioning and MNO operation profiles to be included in the embedded UICC and provisioning and MNO operation profile information.

1 through 10 are diagrams illustrating a provisioning and MNO operation profile according to an embodiment of the present invention.
11 is a flowchart illustrating a network access procedure of a terminal using provisioning and MNO operation profile information according to an embodiment of the present invention.

DETAILED DESCRIPTION Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings so that those skilled in the art may easily implement the present invention. The present invention may, however, be embodied in many different forms and should not be construed as limited to the embodiments set forth herein. In order to clearly illustrate the present invention, parts not related to the description are omitted, and similar parts are denoted by like reference characters throughout the specification.

Throughout the specification, when a part is said to "include" a certain component, it means that it can further include other components, except to exclude other components unless otherwise stated.

1 through 10 are diagrams illustrating a provisioning and MNO operation profile according to an embodiment of the present invention.

Referring to FIG. 1, since the initial eUICC has no MNO, files related to the MNO network do not exist. Accordingly, eUICC needs files to support MNO opening and definition of files related to MNO network to be installed in eUICC after MNO opening.

A file that can be stored in the eUICC (Master File), DF (Dedicated File), ADF (Application Dedicated File), EF (Elementary File), and Applet are defined as Profiles. The terminal acquires the network connection information using the profile of the eUICC, and uses the user data information (SMS, MMS, phone book) as a storage space.

The profile may consist of a provisioning profile, an MNO operational profile, a user profile, and the like. When the eUICC is not opened with the MNO, the provisioning profile refers to a file that provides wireless network connection information to access the wireless network and support MNO opening. After the eUICC is opened with the MNO, the MNO operation profile refers to a file that provides MNO wireless network access information for accessing the MNO wireless network and providing a service, and may exist in a plurality of profiles. A user profile refers to a file provided as a storage space for user data information such as SMS, MMS and phone book.

Referring to FIG. 2, the provisioning profile and the MNO operation profile may be composed of a network connection file and an operation configuration file, respectively. The network connection file is a profile for providing wireless network connection information for accessing a wireless network, and the operation setting profile is a profile for providing an eUICC, a terminal, and network operation setting information.

Referring to FIG. 3, network connection files may be classified as follows according to wireless network technology. The network connection profile may consist of a GSM connection file, a WCDMA connection file, an LTE connection file, and other network connection files.

Referring to FIG. 4, the GSM, WCDMA and LTE network connection files may be configured as shown in FIG. 4.

Referring to FIG. 5, the operation setting file may include a GSM operation setting file, a WCDMA operation setting file, an LTE operation setting file, and other files.

Referring to FIG. 6, the GSM connection file may be provided in a SIM file DF_GSM, and the GSM network connection file may be configured as shown in FIG. 6.

Referring to FIG. 7, the WCDMA access file may be provided in a USIM file ADF_USIM, and the WCDMA network access file may be configured as shown in FIG. 7.

Referring to FIG. 8, the LTE access file may be provided in a USIM file (ADF_USIM), and the LTE network access file may be configured as shown in FIG. 8.

Referring to FIG. 9, the GSM, WCDMA, and LTE operation configuration file may be configured as shown in FIG. 9.

Referring to FIG. 10, in case of an eUICC supporting both GSM, WCDMA, and LTE, a provisioning profile or an MNO operation profile may be configured as shown in FIG. 10.

EF _Kc and EF _KcGPRS files were added in DF _GSM _{_} _ACCESS and DF _GSM _{_} _ACCESS to provide GSM network access function using files existing in ADF _USIM even through USIM file (ADF _USIM ) selection. .

11 is a flowchart illustrating a network access procedure of a terminal using provisioning and MNO operation profile information according to an embodiment of the present invention.

(1) PLMN selection

1) Registered PLMN

The RPLMN is the most recently registered PLMN successfully selected as the PLMN in the PLMN selection process. RPLMN exists in EF_LOCI or EF_LOCIGPRS in DF_GSM in GSM network, EF_LOCI or EF_PSLOCI in ADF_USIM in WCDMA network, and EF_EPSLOCI in ADF_USIM in LTE network.

2) Home PLMN

The HPLMN is selected as the PLMN of the home network. If the PLMN selection process fails with the RPLMN, the HPLMN is selected as the PLMN during the PLMN selection process with the HPLMN. HPLMN is in EF_HPLMNwAcT in DF_GSM in GSM network, EF_HPLMNwAcT in ADF_USIM in WCDMA and LTE network.

3) User PLMN

The UPLMN is a PLMN set by the user. When the PLMN selection process fails with the HPLMN, the UPLMN is selected as the PLMN during the PLMN selection process with the UPLMN. UPLMN is in EF_PLMNwAcT in DF_GSM in GSM network, and EF_PLMNwAcT in ADF_USIM in WCDMA and LTE network.

4) Operator PLMN

The OPLMN is a PLMN set by the subscribed mobile communication network operator. If the PLMN selection process fails with the UPLMN, the OPLMN is selected as the PLMN during the PLMN selection process with the OPLMN. OPLMN is in EF_OPLMNwAcT in DF_GSM in GSM network, and EF_OLMNwAcT in ADF_USIM in WCDMA and LTE network.

5) Forbidden PLMN

The FPLMN includes PLMN information that should not be selected during the PLMN selection process. The FPLMN is in EF_FPLMN in DF_GSM in GSM network, in EF_FPLMN in ADF_USIM in WCDMA and LTE network.

6) High Priority PLMN search period

The HPPLMN includes PLMN selection cycle information. The terminal determines the PLMN selection period with reference to the corresponding information. HPPLMN is in EF_HPPLMN in DF_GSM in GSM network, EF_HPPLMN in ADF_USIM in WCDMA and LTE network.

For reference, PLMN (Public Land Mobile Network) is a unique code for identifying a mobile carrier. The PLMN consists of a Mobile Contry Code (MCC) and a Mobile Network Code (MNC).

(2) Location registration request

With the function of notifying the current location of the terminal to the network, the network transmits data to the terminal with reference to the identified mobility information of the terminal. In this case, IMSI is used as a terminal identifier. IMSI exists in EF_IMSI in DF_GSM in GSM network, EF_IMSI in ADF_USIM in WCDMA and LTE network.

(3) certification

The terminal requests authentication from the network, and the network sends an authentication response to the terminal.

(4) encryption key storage

Authentication is performed between the terminal and the network, and an encryption key is generated during the authentication process. In a GSM network, encryption keys for ciphering of data are stored in EF_Kc (Circuit Switch domain) or EF_KcGPRS (Packet Switch domain) in DF_GSM. In a WCDMA network, encryption keys for confidentiality of data and encryption keys for integrity are stored in EF_Key (Circuit Switch domain) or EF_KeyPS (Packet Switch domain) in ADF_USIM. In the LTE network, an encryption key for confidentiality of data and an encryption key for integrity are stored in an EF_EPSNSC (Packet Switch Domain) in ADF_USIM.

(5) Location registration response

The location of the terminal is registered in the network, and the location information of the terminal is received from the network. The location information is stored in EF_LOCI (Circuit Switch domain) or EF_LOCIGPRS (Packet Switch domain) in DF_GSM in GSM network. In a WCDMA network, it is stored in EF_LOCI (Circuit Switch Domain) or EF_LOCIPS (Packet Switch Domain) in ADF_USIM. In the LTE network, it is stored in the EF_EPSLOCI (Packet Switch Domain) in the ADF_USIM.

(6) Emergency call function

Emergency call numbers are stored in EF_ECC in DF_GSM in GSM networks. In WCDMA and LTE networks, they are stored in EF_ECC in ADF_USIM. The terminal provides an emergency call function using the emergency call number.

The detailed information of the operator operation profile is as follows.

1.Contents of the Files

1.1.Contents of EFs at the MF Level

1.1.1.EF _DIR

This EF contains information that should be referenced to execute a specific application included in the eUICC in the terminal. This EF can configure a field to allow up to three Application ID settings.

Identifier: '2F00' Structure: Linear fixed Mandatory SFI: '1E' 3 Records Record size: 50 bytes Update activity: low Access Conditions:
READ ALW
UPDATE ADM1
DEACTIVATE ADM1
ACTIVATE ADM1
Bytes Description M / O Length 1 to 50 Application template TLV object M Y bytes

Each record of this EF composes information for related application and each information is composed of Application Template Data Object (DO).

Length (hex) Description Status One Application template tag = '61' M One Length of the application template = '03'-'7F' M One Application Identifier tag = '4F' M One AID length = '01'-'10' M '01' '10' AID value. For 3G applications,
See ETSI TS 101.220 M One Application label tag = '50' O One Application label length O NOTE 1 Application label value O NOTE 1: The application label is a DO that contains a string of bytes provided by the application provider to be shown to the user for information, e.g. operator name. The value part of the application label shall be coded according to ETSI 102.221 annex A. It is recommended that the number of bytes in the application label does not exceed 32.

KT eUICC defines the following USIM Application Template Data Object to enable a terminal to select a USIM Application with reference to this EF.

Length (hex) Description Status One Application template tag = '61' M One Length of the application template = '1F' M One Application Identifier tag = '4F' M One AID length = '10' M 10 AID value = 'A0 00 00 00 87 10 02 FF 82 FF 30 89 01 00 00 FF' M One Application label tag = '50' M One Application label length = '0B' M NOTE 1 Application label value = "KT LTE USIM" M NOTE 1: Label indicating KT LTE USIM
Value = "4B 54 20 4C 54 45 20 55 53 49 4D"

The default EF for KT eUICC is Record # 1: 0x61 1F 4F 10 A0 00 00 00 87 10 02 FF 82 FF 30 89 01 00 00 FF 50 0B 4B 54 20 4C 54 45 20 55 53 49 4D FF ... FF Remaining Records: All Set to 'OxFF'.

1.2. Contents of EFs at the ADF USIM Level under the MF

1.2.1.EF International Mobile Subscriber Identity ( _IMSI )

This EF includes IMSI, which stands for Subscriber Identification Number. This EF can be configured to be reflected when changing the default value by linking with EF _IMSI defined in Section 1.4.1.

Identifier: '6F07' Structure: transparent Mandatory SFI: '07' File size: 9 bytes Update activity: low Access Conditions:
READ PIN1
UPDATE ADM1
DEACTIVATE ADM1
ACTIVATE ADM1
Bytes Description M / O Length One Length of IMSI M 1 byte 2 to 9 IMSI M 8 bytes

Length of IMSI: indicates the length of IMSI. (see 3GPP TS 24.008)

IMSI

Byte 2:

Byte 3:

etc

If the number of digits in IMSI is even, the upper four bits of the last byte are set to "1111 ₂ ".

Coding example 1: If IMSI is odd

Logical Value (IMSI) 450080000000002 (15 digit) Physical Value 08 4 9 05 80 00 00 00 00 20

Coding example 2: IMSI is even

Logical Value (IMSI) 45008000000002 (14 digit) Physical Value 08 4 1 05 80 00 00 00 00 F 2

Default value of EF of KT eUICC is set by referring to KT Input file.

1.2.2. EF _HPLMNwAcT (HPLMN selector with Access Technology)

The service provided by this EF may be set to enable or disable in EF _UST (service n'43). This EF includes HPLMN code and access technology information according to priority. (See 3GPP TS 23.122) This EF can be configured to link with the EF _HPLMNwAcT defined in Section 1.4.2 so that it is reflected when changing the default value. This EF can configure fields to allow up to 10 HPLMN settings.

Identifier: '6F62' Structure: transparent Mandatory SFI: '13' File size: 50 bytes Update activity: low Access Conditions:
READ PIN1
UPDATE ADM1
DEACTIVATE ADM1
ACTIVATE ADM1

Bytes Description M / O Length 1 to 3 1 ^st PLMN (highest priority) M 3 bytes 4 to 5 1 ^st PLMN Access Technology Identifier M 2 bytes 6 to 8 2 ^nd PLMN M 3 bytes 9 to 10 2 ^nd PLMN Access Technology Identifier M 2 bytes : : 46 to 48 10 ^th PLMN (lowest priority) M 3 bytes 49 to 50 10 ^th PLMN (lowest priotity) M 2 bytes

-PLMN: Contains information of MCC + MNC according to coding method of 3GPP TS 24.008

_-Access Technology: It is same as EF _PLMNwAcT coding method defined in 1.2.2.

Coding example

Logical value PLMN = 45008, PLMN Access Technology Identifier = UMTS Physical Value 54 F0 80 C0 00 FF FF FF 00 00 FF FF FF 00 00 FF FF FF 00 00 FF FF FF 00 00 FF FF FF 00 00 FF FF FF 00 00 FF FF FF 00 00 FF FF FF 00 00 FF FF FF 00 00

The default value for this EF in KT eUICC is

'54 F0 80 C0 00 FF FF FF 00 00 FF FF FF 00 00 FF FF FF 00 00 FF FF FF 00 00 FF FF FF 00 00 FF FF FF 00 00 FF FF FF 00 00 FF FF FF 00 00 FF FF FF 00 00

.

1.2.3.EF _PLMNwAcT (User controlled PLMN selector with Access Technology)

This EF is used to store PLMN and Access Technology information according to the user's intention. After acquiring the PLMN information, the terminal may provide a function of including the PLMN and Access Technology information acquired by the user's selection in the EF. This EF can be configured to be reflected when changing the default value by linking with EF _PLMNwAcT defined in Section 1.4.3. This EF can configure fields to allow up to 20 PLMN settings.

Identifier: '6F60' Structure: transparent Mandatory SFI: '0A' File size: 100 bytes Update activity: low Access Conditions:
READ PIN1
UPDATE PIN1
DEACTIVATE ADM1
ACTIVATE ADM1
Bytes Description M / O Length 1 to 3 1st PLMN (highest priority) M 3 bytes 4 to 5 1st PLMN Access Technology Identifier M 2 bytes 6 to 8 2nd PLMN M 3 bytes 9 to 10 2nd PLMN Access Technology Identifier M 2 bytes : : 96 to 98 20th PLMN (lowest priority) M 3 bytes 99 to 100 20th PLMN Access Technology Identifier M 2 bytes

- PLMN: The MCC and MNC is included according to the format defined in the 3GPP TS 23.008

8 7 6 5 4 3 2 One MCC digit 2, PLMN MCC digit 1, PLMN octet 1 MNC digit 3, PLMN MCC digit 3, PLMN octet 2 MNC digit 2, PLMN MNC digit 1, PLMN octet 3

At this time, if the MNC has two digits, the MNC digit 3 is set to 1111.

Coding example: MCC + MNC = 45008

8 7 6 5 4 3 2 One 0101 (5) 0100 (4) octet 1 1111 (F) 0000 (0) octet 2 1000 (8) 0000 (0) octet 3

-Access Technology Identifier: It indicates whether Access Technology (GSM / WCDMA / LTE, etc.) is enabled / disabled, and can be selected as '1' is recorded in the corresponding Access Technology field.

bit = 1: access technology selected.

bit = 0: access technology not selected.

Byte5n-1:

Byte 5n:

KT eUICC defaults to '0xFF FF FF 00 00 ... FF FF FF 00 00'.

1.2.4.EF _OPLMNwAcT (Operator controlled PLMN selector with Access Technology)

The service provided by this EF may be set to enable or disable in EF _UST (service n'42). This EF includes preferred PLMN information determined by KT and Access Technology information for each PLMN. Preferred PLMN information should be stored according to priority. The first record represents the highest priority PLMN and the nth record represents the lowest PLMN. (see 3GPP TS 23.122) This EF can be configured to be reflected when changing the default value by linking with EF _OPLMNwAcT defined in Section 1.4.4. This EF can configure fields to allow up to 20 OPLMN settings.

Identifier: '6F61' Structure: transparent Mandatory SFI: '11' File size: 100 bytes Update activity: low Access Conditions:
READ PIN1
UPDATE ADM1
DEACTIVATE ADM1
ACTIVATE ADM1
Bytes Description M / O Length 1 to 3 1st PLMN (highest priority) M 3 bytes 4 to 5 1st PLMN Access Technology Identifier M 2 bytes 6 to 8 2nd PLMN M 3 bytes 9 to 10 2nd PLMN Access Technology Identifier M 2 bytes : : 96 to 98 20th PLMN (lowest priority) M 3 bytes 99 to 100 20th PLMN Access Technology Identifier M 2 bytes

When data is stored in this EF, it is coded as follows according to the coding method of 3GPP TS 24.008.

At this time, if the MNC has two digits, the MNC digit 3 is set to 1111.

Coding example: MCC + MNC = 45008

-Access Technology Identifier : Contains Access Technology (GSM / WCDMA / LTE, etc.) and whether it is enabled / disabled. It can be selected as '1' is recorded in the corresponding Access Technology field.

bit = 1: access technology selected;

bit = 0: access technology not selected.

Byte5n-1:

Byte 5n:

Currently, OPLMN List of countries and operators contracted with KT is as follows.

country Business name MCC MNC Hong Kong Hutch 454 03 454 04 Singapore StarHub 525 05 Taiwan FET 466 01 KGT 466 88 Japan NTT DoCoMo 440 10 Indonesia Indosat 510 01 Macau Hutch 455 03 Philippines SMART 515 03 Thailand AIS 520 01 China China mobile 460 00 USA AT & T (formerly Cingular) 310 410 Germany T-Mobile Deutschland GmbH 262 01 France SFR France 208 10 Italy Vodafone Omnitel N.V. 222 10 United kingdom O2 (Uk) Ltd. 234 10 Australia Hutchison 3G Australia PTY Ltd. 505 06 Malaysia Maxis Mobile Sdn Bhd 502 12 Spain Telefonica Moviles Espana S.A. 214 07 Vietnam Vietnam Telecom Services (Vinaphone) 452 02

The Access Technology information corresponding to OPLMN is set to provide both WCDMA and GSM for all operators of OPLMN to enable communication with the new network even if the carrier included in OPLMN provides a new network (WCDMA / LTE or GSM). do.

That is, the default value of the corresponding EF in KT eUICC is

'0x54 F4 30 80 80 54 F4 40 80 80 25 F5 50 80 80 64 F6 10 80 80 64 F6 88 80 80 44 F0 01 80 80 15 F0 10 80 80 54 F5 30 80 80 15 F5 30 80 80 25 F0 10 80 80 64 F0 00 80 80 13 00 14 80 80 62 F2 10 80 80 02 F8 01 80 80 22 F2 01 80 80 32 F4 01 80 80 05 F5 60 80 80 05 F2 21 80 80 12 F4 70 80 80 54 F2 20 80 Set to 80 '.

1.2.5. EF _FPLMN (Forbidden PLMNs)

This EF contains PLMN information that should not be obtained upon system acquisition. This EF can be configured to be reflected when changing the default value by linking with EF _FPLMN defined in Section 1.4.5. This EF can configure fields to allow up to 20 FPLMN settings.

Identifier: '6F7B' Structure: transparent Mandatory SFI: '0D' File size: 60 bytes Update activity: low Access Conditions:
READ PIN1
UPDATE PIN1
DEACTIVATE ADM1
ACTIVATE ADM1
Bytes Description M / O Length 1 to 3 PLMN 1 M 3 bytes 4 to 6 PLMN 2 M 3 bytes 7 to 9 PLMN 3 M 3 bytes 10 to 12 PLMN 4 M 3 bytes : : 58 to 60 PLMN 20 M 3 bytes

- PLMN: it allows the MCC and MNC recorded in accordance with the 3GPP TS 24.008 and the specification section 1.2.2.

The default value of EF of KT eUICC is set as '0x54 F0 50 FF ... FF'.

1.2.6. EF _HPPLMN (High Priority PLMN search period)

This EF includes PLMN Searching period information. The terminal determines the PLMN Searching period with reference to this EF. (see 3GPP TS 22.011) This EF can be configured to be reflected when changing the default value by linking with EF _HPPLMN defined in Section 1.4.6.

Identifier: '6F31' Structure: transparent Mandatory SFI: '12' File size: 1 byte Update activity: low Access Conditions:
READ PIN1
UPDATE ADM1
DEACTIVATE ADM1
ACTIVATE ADM1
Bytes Description M / O Length One Time interval M 1 byte

The time interval is stored in minutes, and the meaning according to the time interval is as follows.

-Time interval :

'00': No HPLMN search attempts

'01': n minutes

'02': 2n minutes

-::

-'YZ': (16Y + Z) n minutes (maximum value)

-All other values shall be interpreted by the ME as a default period.

According to 3GPP TS 23.122 4.4.3.3, n corresponds to a value of 6 and YZ corresponds to a value of 0x50 (80), so a time interval can be set in a range of 6 minutes to 8 hours. If YZ is set above 0x50, the terminal operates according to the defined default value. (The terminal using Qualcomm source sets the time interval to 60 minutes when the value exceeds 0x50.) The default value of the EF of KT eUICC is set to '0x0A'.

1.2.7. EF _Keys (Ciphering and Integrity Keys)

This EF includes Key Set Indentifier (KSI), Ciphering Key (CK) and Integrity Key (IK) generated during authentication in CS domain.

Identifier: '6F08' Structure: transparent Mandatory SFI: '08' File size: 33 bytes Update activity: high Access Conditions:
READ PIN1
UPDATE PIN1
DEACTIVATE ADM1
ACTIVATE ADM1
Bytes Description M / O Length One Key set identifier KSI M 1 byte 2 to 17 Ciphering key CK M 16 bytes 18 to 33 Integrity key IK M 16 bytes

-Key Set Identifier KSI : Set the default value to '0x07'.

Coding:

Ciphering key CK

Coding:

# Byte ordering 2 MSB byte .
.
. .
.
. 17 LSB byte

-Integrity key IK

Coding:

# Byte ordering 18 MSB byte .
.
. .
.
. 33 LSB byte

The default value of EF of KT eUICC is set as '0x07 FF ... FF'.

1.2.8. Ciphering and Integrity Keys for Packet Switched domain (EF _KeysPS )

This EF includes key set identifier KSI and Ciphering key CK and Integrity key IK generated during authentication in PS domain.

Identifier: '6F09' Structure: transparent Mandatory SFI: '09' File size: 33 bytes Update activity: high Access Conditions:
READ PIN1
UPDATE PIN1
DEACTIVATE ADM1
ACTIVATE ADM1
Bytes Description M / O Length One Key set identifier KSIPS M 1 byte 2 to 17 Ciphering key CKPS M 16 bytes 18 to 33 Integrity key IKPS M 16 bytes

See EF _Keys in Section 1.2.2 for details. The default value of EF of KT eUICC is set as '0x07 FF ... FF'.

1.2.9. EF _START _- Initialization values for Hyperframe number ( _HFN )

This EF contains the values of the bearer's START _CS and START _{PS that} were protected by the key values stored in the EF _KEYS or EF _KEYSPS at the time of the last release of the CS or PS RRC Connection. This value is used to control the lifetime of key values stored in EF _KEYS or EF _KEYSPS . (see 3GPP TS 33.102)

Identifier: '6F5B' Structure: transparent Mandatory SFI: '0F' File size: 6 bytes Update activity: high Access Conditions:
READ PIN1
UPDATE PIN1
DEACTIVATE ADM1
ACTIVATE ADM1
Bytes Description M / O Length 1 to 3 STARTCS M 3 bytes 4 to 6 STARTPS M 3 bytes

-START _CS

Contents: Initialization value for Hyperframe number -CS domain.

Coding: The LSB of STARTCS is stored in bit 1 of byte 3. Unused nibbles are set to 'F'.

-START _PS

Contents: Initialization value for Hyperframe number -PS domain.

Coding: As for STARTCS.

The default value of EF of KT eUICC is set as '0xF0 00 00 F0 00 00'.

1.2.10. EF _THRESHOLD (Maximum value of START)

This EF includes the maximum value of START _CS or START _PS . It is used to control the lifetime of key values in EF _KEYS or EF _KEYSPS . (see 3GPP TS 33.102)

Identifier: '6F5C' Structure: transparent Mandatory SFI: '10' File size: 3 bytes Update activity: low Access Conditions:
READ PIN1
UPDATE ADM1
DEACTIVATE ADM1
ACTIVATE ADM1
Bytes Description M / O Length 1 to 3 Maximum value of START _CS or START _PS . M 3 bytes

The default value of EF of KT eUICC is set to '0xFF'.

1.2.11. EF _LOCI (Location Information)

This EF includes the following location-related information.

Temporary Mobile Subscriber Identity (TMSI)

Location Area Information (LAI)

Location update status

This EF can be configured to be reflected when changing the default value by linking with EF _LOCI defined in Section 1.4.9.

Identifier: '6F7E' Structure: transparent Mandatory SFI: '0B' File size: 11 bytes Update activity: high Access Conditions:
READ PIN1
UPDATE PIN1
DEACTIVATE ADM1
ACTIVATE ADM1
Bytes Description M / O Length 1 to 4 TMSI M 4 bytes 5 to 9 LAI M 5 bytes 10 RFU M 1 byte 11 Location update status M 1 byte

TMSI : See 3GPP TS 24.008 for detailed coding and control methods.

Byte 1:

Byte 2 to 4:

LAI : See 3GPP TS 24.008 for detailed coding and control methods.

8 7 6 5 4 3 2 One MCC digit 2 MCC digit 1, octet 1 MNC digit 3 MCC digit 3, octet 2 MNC digit 2 MNC digit 1 octet 3 LAC octet 4 LAC (continued) octet 5

At this time, if the MNC has two digits, the MNC digit 3 should be stored as '1111 ₂ '.

Coding example: MCC + MNC = 45008

8 7 6 5 4 3 2 One 0101 (5) 0100 (4) octet 1 1111 (F) 0000 (0) octet 2 1000 (8) 0000 (0) octet 3 LAC octet 4 LAC (continued) octet 5

-Location update status : See 3GPP TS 24.008 for detailed coding and control methods.

Byte 11:

Bits: b3 b2 b1

0 0 0: updated.

0 0 1: not updated.

0 1 0: PLMN not allowed.

0 1 1: Location Area not allowed.

1 1 1: reserved.

Bits b4 to b8 are RFU (see 3GPP TS 31.101)

The default value of EF of KT eUICC is set as '0xFF FF FF FF FF FF FF 00 00 FF 01'.

1.2.12. EF _PSLOCI (Packet Switched location information)

This EF contains information related to the position in the PS network as follows.

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

This EF can be configured to be reflected when changing the default value by linking with EF _LOCIGPRS defined in Section 1.4.10.

Identifier: '6F73' Structure: transparent Mandatory SFI: '0C' File size: 14 bytes Update activity: high Access Conditions:
READ PIN1
UPDATE PIN1
DEACTIVATE ADM1
ACTIVATE ADM1
Bytes Description M / O Length 1 to 4 P-TMSI M 4 bytes 5 to 7 P-TMSI signature value M 3 bytes 8 to13 RAI M 6 bytes 14 Routing Area update status M 1 byte

P- TMSI : Contains Packet Temporary Mobile Subscriber Identity information and is coded according to 3GPP TS 24.008.

Byte 1:

Byte 2 to 4:

* n = 2

P- TMSI signature value : Contains Packet Temporary Mobile Subscriber Identity signature value information and is coded according to 3GPP TS 24.008.

Byte 5: first byte of P-TMSI signature value.

-RAI : Contains Routing Area Information information. Refer to 3GPP TS 24.008 for detailed coding and control method.

8 7 6 5 4 3 2 One MCC digit 2 MCC digit 1, octet 1 MNC digit 3 MCC digit 3, octet 2 MNC digit 2 MNC digit 1 octet 3 LAC octet 4 LAC (continued) octet 5 RAC octet 6

At this time, if the MNC has two digits, the MNC digit 3 should be stored as '1111'.

Coding example: MCC + MNC = 45008

8 7 6 5 4 3 2 One 0101 (5) 0100 (4) octet 1 1111 (F) 0000 (0) octet 2 1000 (8) 0000 (0) octet 3 LAC octet 4 LAC (continued) octet 5 RAC octet 6

-Routing Area update status : contains status of routing area update information and is coded according to 3GPP TS 24.008

The information according to the value is as follows.

Byte 14:

Bits: b3 b2 b1.

0 0 0: updated.

0 0 1: not updated.

0 1 0: PLMN not allowed.

0 1 1: Routing Area not allowed.

1 1 1: reserved.

Bits b4 to b8 are RFU (see 3GPP TS 31.101).

The default value of EF of KT eUICC is set as '0xFF FF FF FF FF FF FF FF FF FF 00 00 FF 01'.

1.2.13. EF _EPSLOCI (EPS location information)

The service provided by this EF may be set to enable or disable in EF _UST (service n'85). This EF includes the following EPS location information.

Globally Unique Temporary Identifier (GUTI)

Last visited registered Tracking Area Identity (TAI)

-EPS update status

Identifier: '6FE3' Structure: transparent Mandatory SFI: E File size: 18 bytes Update activity: high Access Conditions:
READ PIN1
UPDATE PIN1
DEACTIVATE ADM1
ACTIVATE ADM1
Bytes Description M / O Length 1 to 12 GUTI M 12 bytes 13 to 17 Last visited registered TAI M 5 bytes 18 EPS update status M 1 byte

-GUTI ( Globally Unique Temporary Identifier ) : For detailed coding and control method, refer to GUTI type among EPS mobile identity information elements defined in 3GPP TS 24.301. The first byte corresponds to "octec2" of the EPS mobile identity information item including the GUTI, and the 12th byte corresponds to "octet3".

Byte 1: First byte of GUTI

-Last visited registerd TAI : For detailed coding and control methods, refer to the content of the tracking area identity information element defined in 3GPP TS 24.301. The 13th byte corresponds to "octet2" of the tracking area identity information item, and the 17th byte corresponds to "octet6".

8 7 6 5 4 3 2 One MCC digit 2 MCC digit 1, octet 1 MNC digit 3 MCC digit 3, octet 2 MNC digit 2 MNC digit 1 octet 3 TAC octet 4 TAC (continued) octet 5

Coding example: MCC + MNC = 45008

8 7 6 5 4 3 2 One 0101 (5) 0100 (4) octet 1 1111 (F) 0000 (0) octet 2 1000 (8) 0000 (0) octet 3 TAC octet 4 TAC (continued) octet 5

-EPS update status : See 3GPP TS 24.301 for detailed coding and control methods.

Byte 18:

Bits: b3 b2 b1

0 0 0: UPDATED.

0 0 1: NOT UPDATED.

0 1 0: ROAMING NOT ALLOWED.

Other values: reserved.

Bits b4 to b8 are RFU. (See 3GPP TS 31.101)

The default EF value of KT eUICC is set to '0xFF FF FF FF FF FF FF FF FF FF FF FF FF FF 00 00 01'.

1.2.14. EF _EPSNSC (EPS NAS Security Context)

The service provided by this EF may be set to enable or disable in EF _UST (service n'85). This EF includes EPS NAS Security context as defined in 3GPP TS 33.401.

Identifier: '6FE4' Structure: linear fixed Mandatory SFI: 8 File size: 54 bytes Update activity: high Access Conditions:
READ PIN1
UPDATE PIN1
DEACTIVATE ADM1
ACTIVATE ADM1
Bytes Description M / O Length 1 to 54 EPS NAS Security Context TLV Object M 54 bytes

EPS NAS Security Context tags

Description Tag Value EPS NAS Seuciryt Context Tag 'A0'

EPS NAS Security Context information

Description Value M / O Length ( bytes ) EPS NAS Seucrity Context Tag 'A0' M One Length (length of all subsequent data) '34' M One Key set identifier KSI _ASME Tag '80' M One Length '01' M One Key set identifier KSI _ASME - M One ASME key (K _ASME ) Tag '81' M One Length '20' M One ASME key (K _ASME ) - M 32 Uplink NAS count Tag '82' M One Length '04' M One Uplink NAS count - M 4 Downlink NAS count Tag '83' M One Length '04 M One Downlink NAS count - M 4 Identifiers of selected NAS integrity and encryption algorithms Tag '84 M One Length '01' M One Identifiers of selected NAS integrity and encryption algorithms - M One

-Key set identifier KSI _ASME Tag '80': ASME key set identifier. See 3GPP TS 33.401 for detailed coding and control methods.

Coding:

ASME key ( K _ASME ) Tag '81': See 3GPP TS 33.401 for detailed coding and control methods.

-Uplink NAS count Tag '82': For detailed coding and control method, refer to 3GPP TS 33.401.

Downlink NAS count Tag '83': For detailed coding and control method, refer to 3GPP TS 33.401.

Identifiers of selected NAS integrity and encryption algorithms Tag '84': For detailed coding and control methods, refer to 3GPP TS 33.401 and 3GPP TS 24.301.

Coding:

First byte of value field of this TLV: First byte of NAS security algorithms information element

All unused bytes are set to '0xFF'.

If the saved EPS NAS security context value is invalid, all record bytes must be set to 'FF'.

The corresponding EF default value of KT eUICC is set as '0xFF FF FF ... FF'.

1.2.15. Emergency Call Codes (EF _ECC )

This EF contains a Call Code for emergency calls. The terminal should be able to make emergency calls with reference to this EF for emergency calls. This EF can configure a field to allow up to eight emergency call setups.

Identifier: '6FB7' Structure: Linear fixed Mandatory SFI: '01' 8 Records Record size: 20 bytes Update activity: low Access Conditions:
READ ALW
UPDATE ADM1
DEACTIVATE ADM1
ACTIVATE ADM1
Bytes Description M / O Length 1 to 3 Emergency Call Code M 3 bytes 4 to 19 Emergency Call Code Alpha Identifier M 16 bytes 20 Emergency Service Category M 1 byte

-Emergency Call Code : Includes maximum 6 digit Call Code. If the designated number is less than 6 digits, set the rest to '0xF'.

Byte 1:

Byte 2:

Byte 3:

-Emergency Call Code Alpha Identifier : A field that is referred to when displaying information on the emergency call code on the terminal when a call is established according to the emergency call code. It is defined in SMS default 7-bit coded alphabet defined in 3GPP TS 23.038 or 3GPP TS 31.101. Can be encoded into UCS2.

-Emergency Service Category : Contains the category of emergency call to be sent to the network and is coded according to 3GPP TS 24.008.

The ECCs basically accepted by KT eUICC are 112, 113, 119, 125, 127, 911, 111 and 122.

The default value of each record of the relevant EF of KT eUICC is set as follows.

Logical value

Physical value

Record No. Default Record 1 0x11 F2 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 01 Record 2 0x11 F3 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 03 Record 3 0x11 F9 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 04 Record 4 0x21 F5 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 09 Record 5 0x21 F7 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 11 Record 6 0x19 F1 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 04 Record 7 0x11 F1 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 07 Record 8 0x21 F2 FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF 08

* When the terminal processes the Emergency Call Code Alpha Identifier as a NULL value (0xFF ... FF), the terminal may display its own emergency call phrase mapped to the terminal.

1.3. Contents of EFs at the DF GSM - ACCESS Level

This section defines file information of EFs that must exist under DF _GSM _- _ACCESS .

The USIM application can access the GSM Netwrok using these files.

1.3.1. EFKc (GSM Ciphering key Kc)

The service provided by this EF may be set to enable or disable in EF _UST (service n'27). This EF includes a ciphering key (Kc) and a sequence number (n) generated during authentication for the GSM network. This EF can be configured to be reflected when changing the default value by linking with EFKc defined in Section 1.4.7.

Identifier: '4F20' Structure: transparent Mandatory SFI: '01' File size: 9 bytes Update activity: high Access Conditions:
READ PIN1
UPDATE PIN1
DEACTIVATE ADM1
ACTIVATE ADM1
Bytes Description M / O Length 1 to 8 Ciphering key Kc M 8 bytes 9 Ciphering key sequence number n M 1 byte

Ciphering key Kc

Coding:

the least significant bit of Kc is the least significant bit of the eighth byte. The most significant bit of Kc is the most significant bit of the first byte.

Ciphering key sequence number n

Coding:

NOTE: 3GPP TS 24.008 defines the value of n = 111 as "key not available". Therefore the value '07' and not 'FF' should be present following the administrative phase.

The default value of EF of KT eUICC is set as '0xFF ... FF 07'.

1.3.2. EFKcGPRS (GPRS Ciphering key KcGPRS)

The service provided by this EF may be set to enable or disable in EF _UST (service n'27). This EF includes a ciphering key (KcGPRS) and sequence number (n) generated during authentication for GPRS (see 3GPP TS 23.060). This EF can be configured to be reflected when changing the default value by linking with EF _KcGPRS defined in Section 1.4.8.

Identifier: '4F52' Structure: transparent Mandatory SFI: '02 File size: 9 bytes Update activity: high Access Conditions:
READ PIN1
UPDATE PIN1
DEACTIVATE ADM1
ACTIVATE ADM1
Bytes Description M / O Length 1 to 8 Ciphering key KcGPRS M 8 bytes 9 Ciphering key sequence number n for GPRS M 1 byte

Ciphering key KcGPRS

Coding:

the least significant bit of KcGPRS is the least significant bit of the eighth byte. The most significant bit of KcGPRS is the most significant bit of the first byte.

Ciphering key sequence number n for GPRS

Coding:

The default value of EF of KT eUICC is set as '0xFF ... FF 07'.

1.4. Contents of EFs at the DF GSM Level under the MF

1.4.1. International Mobile Subscriber Identity (EF _IMSI )

This EF includes IMSI, which stands for Subscriber Identification Number. This EF can be configured to be reflected when changing the default value by linking with EF _IMSI defined in Section 1.2.1.

Identifier: '6F07' Structure: transparent Mandatory File size: 9 bytes Update activity: low Access Conditions:
READ PIN1
UPDATE ADM1
DEACTIVATE ADM1
ACTIVATE PIN1
Bytes Description M / O Length One length of IMSI M 1 byte 2 to 9 IMSI M 8 bytes

Default value of EF of KT eUICC is set by referring to KT Input file.

1.4.2. EF _HPLMNwAcT (HPLMN Selector with Access Technology)

This EF includes HPLMN code and access technology information according to priority. (See 3GPP TS 23.122) This EF can be configured to link with the EF _HPLMNwAcT defined in Section 1.2.6 to reflect the default changes.

Identifier: '6F62' Structure: transparent Mandatory File size: 50 bytes Update activity: low Access Conditions:
READ PIN1
UPDATE ADM1
DEACTIVATE ADM1
ACTIVATE ADM1
Bytes Description M / O Length 1 to 3 1st PLMN (highest priority) M 3 bytes 4 to 5 1st PLMN Access Technology Identifier M 2 bytes 6 to 8 2nd PLMN M 3 bytes 9 to 10 2nd PLMN Access Technology Identifier M 2 bytes : : 46 to 48 n ^th PLMN (lowest priority) M 3 bytes 49 to 50 n ^th PLMN Access Technology Identifier M 2 bytes

The default value for this EF in KT eUICC is

'54 F0 80 80 00 FF FF FF 00 00 FF FF FF 00 00 FF FF FF 00 00 FF FF FF 00 00 FF FF FF 00 00 FF FF FF 00 00 FF FF FF 00 00 FF FF FF 00 00 FF FF FF 00 00

.

1.4.3. EF _PLMNwAcT (User controlled PLMN Selector with Access Technology)

This EF is used to store PLMN and Access Technology information according to the user's intention. After acquiring the PLMN information, the terminal may provide a function of including the PLMN and Access Technology information acquired by the user's selection in the EF. This EF can be configured to be reflected when changing the default value by linking with EF _PLMNwAcT defined in Section 1.2.3.

Identifier: '6F60' Structure: transparent Mandatory File size: 100 bytes Update activity: low Access Conditions:
READ PIN1
UPDATE PIN1
DEACTIVATE ADM1
ACTIVATE ADM1
Bytes Description M / O Length 1 to 3 1st PLMN (highest priority) M 3 bytes 4 to 5 1st PLMN Access Technology Identifier M 2 bytes 6 to 8 2nd PLMN M 3 bytes 9 to 10 2nd PLMN Access Technology Identifier M 2 bytes : : 96 to 98 20th PLMN (lowest priority) M 3 bytes 99 to 100 20th PLMN Access Technology Identifier M 2 bytes

The default value of EF of KT eUICC is set as xFF FF FF 00 00 ... FF FF FF 00 00 '.

1.4.4. EF _OPLMNwAcT (Operator controlled PLMN Selector with Access Technology)

This EF includes preferred PLMN information determined by KT and Access Technology information for each PLMN. Preferred PLMN information should be stored according to priority. The first record represents the highest priority PLMN and the nth record represents the lowest PLMN. (see 3GPP TS 23.122) This EF can be configured to be reflected when changing the default value by linking with EF _OPLMNwAcT defined in section _1.2.21.2.4 .

Identifier: '6F61' Structure: transparent Mandatory File size: 100 bytes Update activity: low Access Conditions:
READ PIN1
UPDATE ADM1
DEACTIVATE ADM1
ACTIVATE ADM1
Bytes Description M / O Length 1 to 3 1st PLMN (highest priority) M 3 bytes 4 to 5 1st PLMN Access Technology Identifier M 2 bytes 6 to 8 2nd PLMN M 3 bytes 9 to 10 2nd PLMN Access Technology Identifier M 2 bytes : : 96 to 98 20th PLMN (lowest priority) M 3 bytes 99 to 100 20th PLMN Access Technology Identifier M 2 bytes

The default value of the corresponding EF in KT eUICC is

'0x54 F4 30 80 80 54 F4 40 80 80 25 F5 50 80 80 64 F6 10 80 80 64 F6 88 80 80 44 F0 01 80 80 15 F0 10 80 80 54 F5 30 80 80 15 F5 30 80 80 25 F0 10 80 80 64 F0 00 80 80 13 00 14 80 80 62 F2 10 80 80 02 F8 01 80 80 22 F2 01 80 80 32 F4 01 80 80 05 F5 60 80 80 05 F2 21 80 80 12 F4 70 80 80 54 F2 20 80 80 '

.

1.4.5. EF _FPLMN (Forbidden PLMNs)

This EF contains PLMN information that should not be obtained upon system acquisition. This EF can be configured to be reflected when changing the default value by linking with EF _FPLMN defined in Section 1.2.5.

Identifier: '6F7B' Structure: transparent Mandatory File size: 60 bytes Update activity: low Access Conditions:
READ PIN1
UPDATE PIN1
DEACTIVATE ADM1
ACTIVATE ADM1
Bytes Description M / O Length 1 to 3 PLMN 1 M 3 bytes 4 to 6 PLMN 2 M 3 bytes 7 to 9 PLMN 3 M 3 bytes 10 to 12 PLMN 4 M 3 bytes : : 58 to 60 PLMN 20 M 3 bytes

The default value of EF of KT eUICC is set as '0x54 F0 50 FF ... FF'.

1.4.6. EF _HPPLMN (Higher Priority PLMN search period)

This EF includes PLMN Searching period information. The terminal determines the PLMN Searching period with reference to this EF. (see 3GPP TS 22.011) This EF can be configured to be reflected when changing the default value by linking with EF _HPPLMN defined in Section 1.2.6.

Identifier: '6F31' Structure: transparent Mandatory File size: 1 byte Update activity: low Access Conditions:
READ PIN1
UPDATE ADM1
DEACTIVATE ADM1
ACTIVATE ADM1
Bytes Description M / O Length One Time interval M 1 byte

The default value of EF of KT eUICC is set as '0x0A'.

1.4.7. EF _Kc (Ciphering key Kc)

This EF includes a ciphering key (Kc) and a sequence number (n) generated during authentication for the GSM network. This EF can be configured to be reflected when changing the default value by linking with EF _Kc defined in Section 1.3.11.3.1.

Identifier: '6F20' Structure: transparent Mandatory File size: 9 bytes Update activity: high Access Conditions:
READ PIN1
UPDATE PIN1
DEACTIVATE ADM1
ACTIVATE ADM1
Bytes Description M / O Length 1 to 8 Ciphering key Kc M 8 bytes 9 Ciphering key sequence number n M 1 byte

The default value of EF of KT eUICC is set as '0xFF ... FF 07'.

1.4.8. EF _KcGPRS (GPRS Ciphering key KcGPRS)

This EF includes a ciphering key (KcGPRS) and sequence number (n) generated during authentication for GPRS (see 3GPP TS 23.060). This EF can be configured to be reflected when changing the default value by linking with EF _KcGPRS defined in Section 1.3.2.

Identifier: '6F52' Structure: transparent Mandatory File size: 9 bytes Update activity: high Access Conditions:
READ PIN1
UPDATE PIN1
DEACTIVATE ADM1
ACTIVATE ADM1
Bytes Description M / O Length 1 to 8 Ciphering key KcGPRS M 8 bytes 9 Ciphering key sequence number n for GPRS M 1 byte

The default value of EF of KT eUICC is set as '0xFF ... FF 07'.

1.4.9. EF _LOCI (Location information)

This EF includes the following location-related information.

Temporary Mobile Subscriber Identity (TMSI)

Location Area Information (LAI)

Location update status

This EF can be configured to be reflected when changing the default value by linking with EF _LOCI defined in Section 1.2.11.

Identifier: '6F7E' Structure: transparent Mandatory File size: 11 bytes Update activity: high Access Conditions:
READ PIN1
UPDATE PIN1
DEACTIVATE ADM1
ACTIVATE PIN1
Bytes Description M / O Length 1 to 4 TMSI M 4 bytes 5 to 9 LAI M 5 bytes 10 RFU M 1 byte 11 Location update status M 1 byte

1.4.10. EF _LOCIGPRS (GPRS location information)

Packet Temporary Mobile Subscriber Identity (P-TMSI)

Routing Area Information (RAI)

-Routing Area update status

This EF can be configured to link with the EF _PSLOCI defined in Section 1.2.12 to reflect the changes in the default value.

Identifier: '6F53' Structure: transparent Mandatory File size: 14 bytes Update activity: high Access Conditions:
READ PIN1
UPDATE PIN1
DEACTIVATE ADM1
ACTIVATE ADM1
Bytes Description M / O Length 1 to 4 P-TMSI M 4 bytes 5 to 7 P-TMSI signature value M 3 bytes 8 to 13 RAI M 6 bytes 14 Routing Area update status M 1 byte

1.4.11. Emergency Call Codes (EF _ECC )

This EF includes call codes for emergency calls. This EF can configure fields to allow up to five emergency calls.

Identifier: '6FB7' Structure: transparent Mandatory File size: 15 bytes Update activity: low Access Conditions:
READ ALW
UPDATE ADM1
DEACTIVATE ADM1
ACTIVATE ADM1
Bytes Description M / O Length 1 to 3 Emergency Call Code 1 M 3 bytes 4 to 6 Emergency Call Code 2 M 3 bytes : : 13 to 15 Emergency Call Code 5 M 3 bytes

-Emergency Call Code : The maximum 6 digit Call Code is included. If the designated number is less than 6 digits, the rest will be filled with 'F'. If a valid call code is not stored in this field, the terminal uses the terminal default value for use without a USIM card.

Byte 1:

Byte 2:

Byte 3:

- Emergency Call Code Alpha Identifier : Use SMS default 7-bit coded alphabet (3GPP TS 23.038) or UCS2 (3GPP TS 31.101) as the information displayed on the terminal when using emergency call dialling.

- Emergency Service Category : Category of emergency call to be sent to the network (3GPP TS 24.008)

The default value of EF of KT eUICC is set as '0x11 F2 FF 11 F9 FF 19 F1 FF 21 F2 FF FF FF FF'.

Claims

Configuration of provisioning and MNO operation profiles stored in the built-in UICC, and the procedure of connecting the terminal to the network using the same.