WO2014035129A1

WO2014035129A1 - Subscriber authentication module for processing file defined by mobile carrier, and terminal and method using same

Info

Publication number: WO2014035129A1
Application number: PCT/KR2013/007710
Authority: WO
Inventors: 이형진; 김관래; 박철현; 서명희; 이진형
Original assignee: 주식회사 케이티
Priority date: 2012-08-29
Filing date: 2013-08-28
Publication date: 2014-03-06

Abstract

Disclosed are an apparatus and method for processing a file contained in a subscriber authentication module embedded in a terminal. The subscriber authentication module includes: a mobile carrier-defined file storage unit for storing, for each mobile carrier, files defined by mobile carriers; and a standard defined file storage unit for storing, for each mobile carrier, a reference file including information regarding the mobile carrier-defined files and a standard defined file defined by international standards. Thus, a user-defined function can be effectively performed through the interface that performs a standard defined function based on the information regarding the mobile carrier-defined files stored in the reference file. Further, an interface between a terminal and an eUICC can be simplified, and mobile carrier-operated profiles operated by multiple mobile carriers can be effectively used.

Description

Subscriber authentication module for processing a file defined by a mobile operator, a terminal and a method using the same

The present invention relates to a subscriber authentication module for a mobile communication service, and more particularly, to an apparatus and a method for processing a file included in a subscriber authentication module embedded in a terminal.

A UICC (Universal Integrated Circuit Card) is a smart card that can be inserted into a terminal and used as a module for user authentication with a mobile communication network subscribed to by a user. UICC includes your personal information (SMS (Short Message Service), Phonebook, etc.) and network information (IMSI (International Mobile Subscriber Identity), Home Public Land Mobile Network (HPLMN) for your mobile operator. Etc.) can be stored. UICC is also known as a Subscriber Identity Module (SIM) card for Global System for Mobile communications (GSM), Wideband Code Division Multiple Access (WCDMA), and Universal Subscriber Identity Module (USIM) for Long Term Evolution (LTE). do.

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 replaces the terminal, the user can easily replace the terminal by mounting the UICC removed from the existing terminal to a 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 more shock and heat resistance, a built-in UICC structure 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 a 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 released. Therefore, the eUICC should be able to accommodate (change) a plurality of mobile communication providers, and should be able to include a plurality of mobile operator operating profiles (operational profiles) inside the eUICC.

An object of the present invention for solving the above problems is to provide a subscriber authentication module for processing a file defined by a mobile communication provider.

Another object of the present invention for solving the above problems is to provide a terminal having a subscriber authentication module for processing a file defined by a mobile communication provider.

Another object of the present invention for solving the above problems is to provide a service provider definition file processing method using a subscriber authentication module for processing a file defined by a mobile communication provider.

The built-in subscriber authentication module according to an embodiment of the present invention for achieving the above object includes a service provider definition file storage unit for storing the service provider definition file defined by the mobile service provider for each mobile communication provider, and information on the service provider definition file. And a standard definition file storage unit for storing a reference file and a standard definition file defined by an international standard for each mobile carrier.

Here, the reference file may include the structure and characteristic information of the operator definition file.

Here, the reference file may include at least one of information on the address path of the operator definition file, information on the terminal execution command, and information on whether the terminal supports the operator definition file.

Herein, the standard definition file storage unit may access the operator definition file based on the reference file.

A terminal according to an embodiment of the present invention for achieving the above another object is a standard for accessing a standard definition file defined by an international standard stored for each mobile communication provider in a subscriber authentication module and performing an operation corresponding to the standard definition file. Based on the definition function unit and the reference file including information on the operator definition file defined by the mobile operator, the user accesses the operator definition file stored for each mobile operator in the subscriber authentication module and performs an operation corresponding to the operator definition file. Includes operator defined functions to perform.

Service provider definition file processing method according to an embodiment of the present invention for achieving the another object, in the file processing method performed in a terminal with a subscriber authentication module, information on the service provider definition file defined by the mobile operator Receiving a reference file comprising a; and accessing the operator definition file stored in the subscriber authentication module based on the reference file, and performing an operation corresponding to the accessed operator definition file.

The embedded subscriber authentication module, the terminal, and the service provider definition file processing method according to the embodiment of the present invention as described above may perform an operation corresponding to the service provider definition file through a reference file stored in the subscriber authentication module. .

In addition, a user-defined function can be effectively performed through an interface that performs a standard definition function based on the information on the operator definition file stored in the reference file.

In addition, not only the interface between the terminal and the eUICC can be simplified, but also the operator operation profile managed by a plurality of mobile communication operators can be effectively used.

1 is a conceptual diagram illustrating an interface between a terminal and a subscriber authentication module.

2 is another conceptual diagram illustrating an interface between a terminal and a subscriber authentication module.

3 is a conceptual diagram illustrating an interface between a terminal using a reference file and a subscriber authentication module according to an embodiment of the present invention.

4 is a conceptual diagram illustrating the structure of a reference file according to an embodiment of the present invention.

5 is a flowchart illustrating a method of processing a service provider definition file using a reference file according to an embodiment of the present invention.

As the invention allows for various changes and numerous embodiments, particular embodiments will be illustrated in the drawings and described in detail in the written description. However, this is not intended to limit the present invention to specific embodiments, it should be understood to include all modifications, equivalents, and substitutes included in the spirit and scope of the present invention. In describing the drawings, similar reference numerals are used for similar elements.

Terms such as first, second, A, and B may be used to describe various components, but the components should not be limited by the terms. The terms are used only for the purpose of distinguishing one component from another. For example, without departing from the scope of the present invention, the first component may be referred to as the second component, and similarly, the second component may also be referred to as the first component. The term and / or includes a combination of a plurality of related items or any item of a plurality of related items.

When a component is referred to as being "connected" or "connected" to another component, it may be directly connected to or connected to that other component, but it may be understood that other components may be present in between. Should be. On the other hand, when a component is said to be "directly connected" or "directly connected" to another component, it should be understood that there is no other component in between.

The terminology used herein is for the purpose of describing particular example embodiments only and is not intended to be limiting of the present invention. Singular expressions include plural expressions unless the context clearly indicates otherwise. In this application, the terms "comprise" or "have" are intended to indicate that there is a feature, number, step, operation, component, part, or combination thereof described in the specification, and one or more other features. It is to be understood that the present invention does not exclude the possibility of the presence or the addition of numbers, steps, operations, components, components, or a combination thereof.

Unless defined otherwise, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art. Terms such as those defined in the commonly used dictionaries should be construed as having meanings consistent with the meanings in the context of the related art and shall not be construed in ideal or excessively formal meanings unless expressly defined in this application. Do not.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings.

First, a mobile operator operating profile means a file including mobile carrier wireless network access information in order to access a corresponding mobile carrier wireless network and receive a service.

The subscriber authentication module 200 is developed (issued) at the request of a mobile communication provider (hereinafter referred to as a "operator"), and the file recorded in the subscriber authentication module 200 is a file other than the standard according to the request of the service provider. It can be configured in addition.

Here, the subscriber authentication module 200 may refer to a universal integrated circuit card (UICC).

Referring to FIG. 1, the UICC file may include a 'standard definition file' defined by an international standard (ETSI, 3GPP) and a 'business definition file' defined by a specific operator.

Although the terminal 100 and the UICC are shown as separate components for the convenience of the interface description between the subjects, since the UICC is a built-in component included in the terminal 100, the UICC is interpreted as being located inside the terminal 100. Can be.

Meanwhile, the terminal 100 may include a standard definition function unit 110 and a service provider definition function unit 120. Here, the standard definition function unit 110 may perform a 'standard definition function', and the operator definition function unit 120 may perform a 'business operator definition function'.

In addition, the subscriber authentication module 200 may be configured to include a standard definition file storage 210 and a service provider definition file storage 220. Here, the standard definition file storage unit 210 stores the standard definition file, and the operator definition file storage unit 220 may store the operator definition file.

Here, the 'standard definition function' may mean a function that recognizes a 'standard definition file' defined in an international standard, accesses a 'standard definition file', or performs an operation related to the 'standard definition file'.

In addition, the "business-defined function" may mean a function that recognizes a "business-defined file" defined by a specific business operator, accesses a "business-defined file", or performs an operation related to the "business-defined file."

Specifically, the terminal-UICC standard definition for command request / response between the 'standard definition function' of the terminal 100 and the 'standard definition file' of the UICC as shown in FIG. 1 for the interface between the terminal 100 and the UICC. External interface (1-①) ',' Terminal-defined function 'of terminal 100 and' Terminal-defined external interface (1-②) 'between terminal and UICC for command request / response May be included.

Also, an internal interface (1-③) between the terminal standard and the operator-defined function for command request / response between the 'standard definition function' and the 'operator definition function' of the terminal 100 may be included.

Subscriber authentication module 200 may mean an embedded Universal Integrated Circuit Card (eUICC). Therefore, an embodiment of the present invention will be described based on the case where the subscriber authentication module 200 is an eUICC.

Although the terminal 100 and the eUICC are shown as separate components for the convenience of the interface description between the subjects, the eUICC is a built-in component included in the terminal 100, and thus, the eUICC is located inside the terminal 100. Can be.

The terminal 100 may include a standard definition function unit 110 and a plurality of service provider definition functions 121, 122, and 123.

For example, each of the first operator defined function unit 121, the second operator defined function unit 122, and the third operator defined function unit 123 may be defined by each of the first operator, the second operator, and the third operator. The defined operator definition file.

As shown in FIG. 2, the eUICC may have an 'operator definition file' defined for each operator in each mobile operator's operation profile.

For example, the eUICC may include a first operator operation profile, a second operator operation profile, and a third operator operation file, each operator operation profile storing a standard definition file storage 210 and a plurality of operator definition files. It may include a portion (221, 222, 223).

That is, the eUICC includes a first standard definition file storage unit 211, a second standard definition file storage unit 212, and a third standard definition file storage unit 213, which are classified for each operator, and define a first operator. The file storage unit 221 may include a second operator definition file storage unit 222 and a third operator definition file storage unit 223.

An interface between the terminal 100 and the eUICC will be described with reference to FIG. 2.

In order to recognize and support the 'company definition file', the terminal 100 may need a 'company-defined external interface (2-②, ③, ④) between each terminal-eUICC' as shown in FIG. 2. That is, as the number of operators that can be accommodated in the eUICC increases, the 'interface between the terminal-eUICC operator-defined external interfaces (2-②, ③, ④)' and the 'standard-definition function-operator-defined functions' of the terminal 100 (2 Since the number of ⑤, ⑥, ⑦) 'is increased, the complexity of implementation of the terminal 100 may be increased.

Therefore, the present invention is added to the 'terminal-eUICC operator-defined external interface (2-②, ③, ④)' according to the requirements defined by each operator 'terminal-eUICC standard definition external interface (2-①)' It can be configured to process in the implementation complexity of the terminal 100 can be reduced.

However, an eUICC (embedded UICC) should be able to accommodate (change) a plurality of operators (unlike conventional UICC), and for this purpose, it should be able to include a plurality of mobile operator operating profiles (Operational Profile) inside the eUICC.

Accordingly, an object of the present invention is to propose a configuration of a reference file including information on a service provider definition file stored in an eUICC, and to propose an interface between an eUICC and a terminal including a reference file.

In FIG. 3, the terminal 100 and the eUICC are illustrated as separate components for the convenience of the interface description between the subjects. However, since the eUICC is a built-in component included in the terminal, the eUICC is interpreted as being located inside the terminal 100. Can be.

Referring to FIG. 3, an eUICC according to an embodiment of the present invention may additionally include a file named 'reference file' in a 'standard definition file'. That is, each standard definition file storage unit 210 may store a reference file.

For example, the first standard definition file storage 211 of the first operator management profile stores the first reference file, and the second standard definition file storage 212 of the second operator management profile is the second reference file. The third standard definition file storage unit 213 of the third operator operating profile may store the third reference file.

'Reference file' may be referred to by various names without departing from the gist of the present invention. For example, "meta file", "meta information file", "meta data file", "base file", "address file" May be called. Hereinafter, it will be referred to as a 'reference file'.

In detail, in order for the terminal 100 to recognize and access the 'operator definition file' defined by each operator and to perform related operations (commands), the 'reference file' is the structure and characteristics of the 'operator definition file'. May contain information.

That is, the eUICC may provide file structure information of operator definition files including file address (File ID, FID) of operator definition files. (There shall be a mechanism for the eUICC to provide information about proprietary files (e.g. File ID, Path) to the terminal)

The terminal 100 understands the structure and characteristics of the 'operator definition file' corresponding to the reference file through the reference file included in the standard definition file of the specific operator operation file, and the 'terminal-eUICC standard definition external interface (3- ①) 'can access and operate the corresponding' business definition file '.

Through this, even if the number of operators that can be accommodated in the eUICC increases, there is no need to additionally configure a 'terminal-eUICC operator-defined external interface' can be designed for a simple interface.

For example, the reference file may include one or more of the following information.

1) Total number of operator definition files

2) Path of File Provider's Address (File ID, FID)

3) Operator defined file characteristics

-Attributes of information (user data information or network connection information);

-Terminal execution command (command information to be executed by the terminal to recognize the file data)

-Terminal performance function (function information to be performed in the terminal by using the file data after recognizing the file data through the terminal execution command)

4) Whether the terminal supports the operator definition file

In addition, the terminal 100 may know the above information through the information included in the reference file. For example, the terminal 100 may infer the total number of operator definition files as the valid number of operator definition file addresses.

Referring to FIG. 4, the reference file may include information about an address path of a service provider definition file, a terminal execution command, and whether the terminal supports the service provider definition file.

The information 310 on the address path of the operator definition file may include information on a file ID (FID) path of the operator definition file.

In addition, the information 310 on the address path of the service provider definition file 310 may include information about the length of the service provider definition file address path information and the actual service provider definition file address path.

On the other hand, the 'information 320 for the terminal execution command' may be composed of the command information to be performed after the terminal 100 accesses the file through the address path of the operator definition file. For example, the 'terminal execution command' may include a 'Read' command for instructing to read the operator definition file, and a 'Search & Read' command for instructing to read after searching the operator definition file. It may be.

The information 330 on whether the terminal supports the operator definition file 330 may include information for registering whether the terminal 100 can support the function of the operator definition file.

For example, the default value of 'the information on whether the terminal supports the operator definition file (330)' is set to 'unsupported', the terminal 100 for the file pointed to in the operator definition file address path in the terminal 100 ), You can update to 'support' if you can, or 'unsupported' if you can not.

The reference file may be configured as shown in Table 1 below in the form of an Elementary File (EF) of the eUICC.

Table 1

Referring to Table 1 in more detail as follows.

-Length of Operational EF path : It is the length of Operational EF path indicated in 2nd ~ 13th byte of EF and can have the value of '0x04' / '0x06' / '0x08' / '0x10' / 0x12.

-Operational EF Path : It can contain the actual path of the operator-defined profile EF. Paths can be started from MF (Master File) 3F00, and each path can be designated as FID. However, in the case of ADF, the Recode number of EF _DIR including 7FFF and AID (Application ID) of the corresponding Application Dedicated File (ADF) may be included.

7FFF is an implicit FID (File ID) value that can be selected for the ADF after the application ID of the ADF is selected, and EF _DIR is a file containing an AID value for selecting the ADF. At this time, if the length of Operational EF Path is not filled up to 12, the relevant part can be set as '0x00'.

Command Information : This may indicate 'information 330 for the terminal execution command'.

Byte 14: For example, the value of 'terminal execution command' may be determined as follows, but the value may be selectively changed.

● 0 0 0 0 0 0 0 0 1: Read

-You can read all the values of each EF (for each record).

● 0 0 0 0 0 0 1 1: Search & Read

-After searching the value of each EF (for each record), related value can be read according to the result.

● others: reserved

Support Information : Indicates whether the terminal supports the operator definition file. The default value of this field is '0x00' (not supported), and the terminal can update the value by checking whether the file is supported.

Byte 15: For example, the value of 'supporting terminal definition file of the terminal' can be determined as follows, but the value can be selectively changed.

● 0 0 0 0 0 0 0 0: 'Initial value (NULL)'

● 0 0 0 0 0 0 0 1: 'Not supported'

● 0 0 0 0 0 0 1 0: 'Support'

The default value for this EF in eUICC is

Record # 1: 0x04 3F 00 2F 33 00 00 00 00 00 00 00 00 01 00

Record # 2: 0x04 3F 00 2F 35 00 00 00 00 00 00 00 00 01 00

Record # 3: 0x04 3F 00 2F 36 00 00 00 00 00 00 00 00 01 00

Record # 4: 0x04 3F 00 2F 38 00 00 00 00 00 00 00 00 01 00

Record # 5: 0x04 3F 00 2F 39 00 00 00 00 00 00 00 00 01 00

Record # 6: 0x06 3F 00 7F FF 00 01 2F 27 00 00 00 00 03 00

Remaining Records: All '0x00'

It can be set to.

In the present specification, the 'function' may be referred to as 'functional part', 'module', and 'operating part', etc., and one 'function' may be referred to as a separate 'function' independent of the other 'function'. Each may be implemented, but may also be implemented in a single 'function' (for example, the control unit provided by the terminal 100).

Referring to FIG. 5, in the method of processing a service provider definition file according to an exemplary embodiment of the present disclosure, the method may further include receiving a reference file including information about the service provider definition file (S510), based on the reference file, to the subscriber authentication module. Accessing the stored operator definition file (S520) and performing an operation corresponding to the accessed operator definition file (S530).

In operation S510, a reference file including information on an operator definition file defined by the mobile communication operator may be received. That is, the terminal 100 may read the reference file stored in the eUICC, and may know information about the operator definition file from the reference file.

The reference file may include the structure and characteristic information of the operator definition file. For example, the reference file includes at least one of information 310 about the address path of the operator definition file, information 320 about the terminal execution command, and information 330 about whether the terminal supports the operator definition file. can do.

In particular, the reference file may be stored in addition to a standard definition file defined in an international standard stored for each mobile carrier in the eUICC.

The terminal 100 may access the operator definition file stored in the subscriber authentication module 200 based on the reference file (S520). For example, the terminal 100 may access the operator definition file stored in the eUICC based on the reference file.

The terminal 100 may perform an operation corresponding to the accessed operator definition file (S530). That is, the terminal 100 may perform an operation corresponding to the operator definition file using the reference file stored in the eUICC.

Therefore, the operator definition file processing method according to an embodiment of the present invention may perform an operation corresponding to the operator definition file through the reference file stored in the subscriber authentication module 200. That is, the user-defined function can be effectively performed through an interface that performs the standard definition function based on the information on the operator definition file stored in the reference file.

Through this, not only the interface between the terminal 100 and the eUICC can be simplified, but also the operator operation profile managed by a plurality of mobile communication operators can be effectively used.

Although described above with reference to a preferred embodiment of the present invention, those skilled in the art will be variously modified and changed within the scope of the invention without departing from the spirit and scope of the invention described in the claims below I can understand that you can.

Claims

In the subscriber authentication module embedded in the terminal,

An operator definition file storage unit which stores an operator definition file defined by a mobile communication provider for each mobile communication provider;

And a standard definition file storage unit which stores a reference file including information on the service provider definition file and a standard definition file defined by an international standard for each mobile communication provider.
The method according to claim 1,

The reference file above

Embedded subscriber authentication module comprising the structure and characteristic information of the operator definition file.
The method according to claim 1,

The reference file above

And at least one of information on an address path of the operator definition file, information on a terminal execution command, and information on whether the terminal supports the operator definition file.
The method according to claim 1,

The standard definition file storage unit

And the terminal accesses the service provider definition file based on the reference file.
In the terminal embedded subscriber authentication module,

A standard definition function unit configured to access a standard definition file defined by an international standard stored for each mobile communication operator in the subscriber authentication module and perform an operation corresponding to the standard definition file; And

Accessing the service provider definition file stored for each mobile communication operator in the subscriber authentication module based on a reference file including information on the service provider definition file defined by the mobile communication operator, and performing an operation corresponding to the service provider definition file. A terminal comprising an operator-defined function to perform.
The method according to claim 6,

The reference file above

And a structure and characteristic information of the operator definition file.
The method according to claim 6,

The reference file above

And at least one of information on an address path of the operator definition file, information on a terminal execution command, and information on whether the terminal supports the operator definition file.
The method according to claim 6,

The reference file above

And the terminal is added to the standard definition file and stored in the subscriber authentication module.
The method according to claim 6,

The standard definition function unit and the operator definition function unit

Terminal for the exchange of information through the internal interface.
The method according to claim 6,

The operator defined function unit

And accessing the service provider definition file through an interface established between the standard definition function unit and the subscriber authentication module.
In the file processing method performed in a terminal having a subscriber authentication module,

Receiving a reference file including information on an operator definition file defined by the mobile communication provider;

Accessing the operator definition file stored in the subscriber authentication module based on the reference file; And

And performing an operation corresponding to the accessed operator definition file.
The method according to claim 11,

The reference file above

And a service provider definition file structure and characteristic information of the service provider definition file.
The method according to claim 11,

The reference file above

And at least one of information on an address path of the operator definition file, information on a terminal execution command, and information on whether the terminal supports the operator definition file.
The method according to claim 11,

The reference file above

And the subscriber definition module is added to a standard definition file defined by an international standard stored for each mobile communication provider and stored in the subscriber authentication module.