KR101717530B1 - Apparatus for managing usim data and method thereof - Google Patents

Abstract

(U) A method for efficiently managing data in a SIM is disclosed. (U) A method of managing data in a SIM is a method of managing a reference count indicating the number of times each of records in a second EF (Elementary File) stored in the SIM is referenced by a record of another EF, Storing; Receiving a cascade delete command for a first record in a first Elementary File (EF) stored in the SIM; And if the reference number of the at least one second record in the second EF referenced by the first record indicates that the at least one second record is only referenced by the first record, And deleting one second record.

Description

[0001] APPARATUS FOR MANAGING USIM DATA AND METHOD THEREOF [0002]

The present invention relates to a USIM data management method, and more particularly, to a USIM data management method in a case where there is a connection relationship between elementary files (EFs).

A Subscriber Identity Module (SIM) or a Universal Subscriber Identity Module (Universal SIM) is widely used for subscriber authentication and identification of mobile equipment (ME). (U) SIM includes an integrated circuit for securely storing an IMSI (International Mobile Subscriber Identity) and a key associated with subscriber identification and authentication.

In general, the (U) SIM is inserted into the ME in the form of a plastic card, and includes a storage space for storing data. (U) The discussion of standardization of (U) SIM is actively discussed in order to extend the function of (U) SIM while ensuring the versatility of SIM.

For example, (U) SIM may store information such as a telephone directory. For example, the (U) SIM can store information using a flash memory. However, the flash memory has a relatively slow reading speed and writing speed, has a limitation on the number of times of recording, and has a disadvantage that only block-by-block rewriting is possible. Thus, there is a need for a method that can reduce the process of accessing or updating data in (U) SIM.

SUMMARY OF THE INVENTION The present invention provides a method for extending the lifetime of (U) SIM (U) through efficient management of SIM data.

The technical problem of the present invention is to provide a faster (U) SIM data management method by reducing the number of interfaces to (U) SIM data.

A technical object of the present invention is to provide (U) a SIM data management method for maintaining a link between elementary files (EFs) in a SIM.

SUMMARY OF THE INVENTION It is an object of the present invention to provide a SIM data management method capable of preventing (U) waste of SIM data due to a malfunction of a mobile terminal.

It is to be understood that both the foregoing general description and the following detailed description are exemplary and explanatory and are not intended to limit the invention to the precise forms disclosed. .

According to an aspect of the present invention, there is provided a method of managing data in a subscriber identity module (SIM) of a mobile terminal, the method comprising: receiving a record in a second elementary file (EF) Storing a reference count in the SIM that indicates the number of times each of the plurality of EFs is referenced by a record of another EF; Receiving a cascade delete command for a first record in a first Elementary File (EF) stored in the SIM; And if the reference number of the at least one second record in the second EF referenced by the first record indicates that the at least one second record is only referenced by the first record, And deleting one second record.

According to another aspect of the present invention, there is provided a mobile terminal including a Subscriber Identity Module (SIM) according to an embodiment of the present invention. And a processor, wherein the processor stores in the SIM a reference count in which each of the records in a second Elementary File (EF) stored in the SIM is referenced by a record of another EF, The method comprising: receiving a cascade delete instruction for a first record in a first EF stored in the SIM, the reference number of at least one second record in the second EF referenced by the first record; And delete the first record and the at least one second record if at least one second record indicates that it is only referred to by the first record.

According to embodiments of the present invention, the lifetime of (U) SIM can be extended through efficient management of (U) SIM data.

Further, according to embodiments of the present invention, (U) the link between EFs in the SIM can be securely maintained.

In addition, according to the embodiments of the present invention, (U) SIM data can be prevented from being wasted.

The effects obtained by the present invention are not limited to the above-mentioned effects, and other effects not mentioned can be clearly understood by those skilled in the art from the following description will be.

BRIEF DESCRIPTION OF THE DRAWINGS The accompanying drawings, which are included to provide a further understanding of the invention and are incorporated in and constitute a part of the specification, illustrate embodiments of the invention and, together with the description, serve to explain the principles of the invention.
1 is a block diagram showing the configuration of a base station and a terminal in a wireless communication system.
FIG. 2 shows the structure of an Elementary File_Abbreviated Dialing Number (EF_ADN) record according to an example.
FIG. 3 shows a structure of EF_EXT1 (Extension 1) according to an example.
FIG. 4 shows a chain of extension records of EF_EXT1 according to an example.
5 shows a record of EF_ADN according to an example.
6 shows a record of EF_EXT1 according to an example.
FIG. 7 shows a process of deleting a conventional telephone directory entry.
FIG. 8 illustrates a process of deleting a phonebook entry according to an example.

The following embodiments are a combination of elements and features of the present invention in a predetermined form. Each component or characteristic may be considered optional unless otherwise expressly stated. Each component or feature may be implemented in a form that is not combined with other components or features. In addition, some of the elements and / or features may be combined to form an embodiment of the present invention. The order of the operations described in the embodiments of the present invention may be changed. Some configurations or features of certain embodiments may be included in other embodiments, or may be replaced with corresponding configurations or features of other embodiments.

In this specification, a base station has a meaning as a network terminal node that directly communicates with a terminal. The specific operation described herein as being performed by the base station may be performed by an upper node of the base station, as the case may be. That is, it is apparent that various operations performed for communication with a terminal in a network composed of a plurality of network nodes including a base station can be performed by a network node other than the base station or the base station.

In this specification, a 'base station (BS)' may be replaced by a term such as a fixed station, a Node B, an eNode B (eNB), an access point (AP) Repeaters can be replaced by terms such as Relay Node (RN), Relay Station (RS), and so on. The term 'terminal' may be replaced with terms such as User Equipment (UE), Mobile Station (MS), Mobile Subscriber Station (MSS), and Subscriber Station (SS).

The specific terminology used in the following description is provided to aid understanding of the present invention, and the use of such specific terminology may be changed into other forms without departing from the technical idea of the present invention.

In some instances, well-known structures and devices may be omitted or may be shown in block diagram form, centering on the core functionality of each structure and device, to avoid obscuring the concepts of the present invention.

Embodiments of the present invention may be supported by standard documents disclosed in at least one of the IEEE 802 systems, 3GPP systems, 3GPP LTE and LTE-Advanced (LTE-Advanced) systems, and 3GPP2 systems, which are wireless access systems. That is, the steps or portions of the embodiments of the present invention that are not described in order to clearly illustrate the technical idea of the present invention can be supported by the documents. In addition, all terms disclosed in this document may be described by the standard document. For example, embodiments of the present document may be described by standard documents such as 3GPP TS 24. 008, 3GPP TS 31.101, 3GPP TS 51.101 and / or ETSI TS 102 221.

Embodiments of the present invention may also be implemented in a wireless communication system, such as a Code Division Multiple Access (CDMA), a Frequency Division Multiple Access (FDMA), a Time Division Multiple Access (TDMA), an Orthogonal Frequency Division Multiple Access (OFDMA), a Single Carrier Frequency Division Multiple Access) and the like. CDMA may be implemented in radio technology such as Universal Terrestrial Radio Access (UTRA) or CDMA2000. The TDMA may be implemented in a wireless technology such as Global System for Mobile communications (GSM) / General Packet Radio Service (GPRS) / Enhanced Data Rates for GSM Evolution (EDGE). OFDMA may be implemented in wireless technologies such as IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, and E-Utra (Evolved UTRA). UTRA is part of the Universal Mobile Telecommunications System (UMTS). 3GPP (3rd Generation Partnership Project) LTE (Long Term Evolution) is a part of E-UMTS (Evolved UMTS) using E-UTRA, adopting OFDMA in downlink and SC-FDMA in uplink. LTE-A (Advanced) is the evolution of 3GPP LTE. WiMAX can be described by the IEEE 802.16e standard (WirelessMAN-OFDMA Reference System) and the advanced IEEE 802.16m standard (WirelessMAN-OFDMA Advanced system). For the sake of clarity, the 3GPP LTE and 3GPP LTE-A systems will be described below, but the technical idea of the present invention is not limited thereto.

In addition, specific terms used in the following description are provided to facilitate understanding of the present invention, and the use of such specific term can be changed into other forms without departing from the technical idea of the present invention.

1 is a block diagram showing the configuration of a base station 105 and a terminal 110 in a wireless communication system 100. As shown in FIG.

Although one base station 105 and one terminal 110 (including a D2D terminal) are shown for the sake of simplicity of the wireless communication system 100, the wireless communication system 100 may include one or more base stations and / And may include a terminal.

1, a base station 105 includes a transmit (Tx) data processor 115, a symbol modulator 120, a transmitter 125, a transmit and receive antenna 130, a processor 180, a memory 185, a receiver 190, a symbol demodulator 195, and a receive data processor 197. The terminal 110 includes a transmission (Tx) data processor 165, a symbol modulator 170, a transmitter 175, a transmission / reception antenna 135, a processor 155, a memory 160, a receiver 140, A demodulator 155, and a receive data processor 150. Although the transmission / reception antennas 130 and 135 are shown as one in the base station 105 and the terminal 110, respectively, the base station 105 and the terminal 110 have a plurality of transmission / reception antennas. Therefore, the base station 105 and the terminal 110 according to the present invention support a Multiple Input Multiple Output (MIMO) system. Also, the base station 105 according to the present invention can support both a Single User-MIMO (MIMO) MU-MIMO (Multi User-MIMO) scheme.

On the downlink, the transmit data processor 115 receives traffic data, formats, codes, and interleaves and modulates (or symbol maps) the coded traffic data to generate modulation symbols Symbols "). A symbol modulator 120 receives and processes the data symbols and pilot symbols to provide a stream of symbols.

The symbol modulator 120 multiplexes the data and pilot symbols and transmits it to the transmitter 125. At this time, each transmission symbol may be a data symbol, a pilot symbol, or a signal value of zero. In each symbol period, the pilot symbols may be transmitted continuously. The pilot symbols may be frequency division multiplexed (FDM), orthogonal frequency division multiplexed (OFDM), time division multiplexed (TDM), or code division multiplexed (CDM) symbols.

Transmitter 125 receives the stream of symbols and converts it to one or more analog signals and further modulates (e.g., amplifies, filters, and frequency upconverts) The transmission antenna 130 transmits the generated downlink signal to the mobile station.

In the configuration of the terminal 110, the reception antenna 135 receives the downlink signal from the base station and provides the received signal to the receiver 140. The receiver 140 adjusts (e.g., filters, amplifies, and downconverts) the received signal and digitizes the conditioned signal to obtain samples. The symbol demodulator 145 demodulates the received pilot symbols and provides it to the processor 155 for channel estimation.

Symbol demodulator 145 also receives a frequency response estimate for the downlink from processor 155 and performs data demodulation on the received data symbols to obtain a data symbol estimate (which is estimates of the transmitted data symbols) And provides data symbol estimates to a receive (Rx) data processor 150. [ The receive data processor 150 demodulates (i.e., symbol demaps), deinterleaves, and decodes the data symbol estimates to recover the transmitted traffic data.

The processing by symbol demodulator 145 and received data processor 150 is complementary to processing by symbol modulator 120 and transmit data processor 115 at base station 105, respectively.

On the uplink, the terminal 110 processes the traffic data and provides data symbols. The symbol modulator 170 may receive and multiplex data symbols, perform modulation, and provide a stream of symbols to the transmitter 175. A transmitter 175 receives and processes the stream of symbols to generate an uplink signal. The transmission antenna 135 transmits the generated uplink signal to the base station 105.

In the base station 105, an uplink signal is received from a terminal 110 via a receive antenna 130, and a receiver 190 processes the received uplink signal to obtain samples. The symbol demodulator 195 then processes these samples to provide received pilot symbols and data symbol estimates for the uplink. The receive data processor 197 processes the data symbol estimates to recover the traffic data transmitted from the terminal 110.

The processors 155 and 180 of the terminal 110 and the base station 105 respectively instruct (for example, control, adjust, manage, etc.) the operation in the terminal 110 and the base station 105. Each of the processors 155 and 180 may be coupled with memory units 160 and 185 that store program codes and data. The memories 160 and 185 are connected to the processor 180 to store operating systems, applications, and general files.

The processors 155 and 180 may also be referred to as a controller, a microcontroller, a microprocessor, a microcomputer, or the like. Meanwhile, the processors 155 and 180 may be implemented by hardware or firmware, software, or a combination thereof. (DSP), digital signal processing devices (DSPDs), programmable logic devices (PLDs), and the like may be used to implement embodiments of the present invention using hardware, , FPGAs (field programmable gate arrays), and the like may be provided in the processors 155 and 180.

Meanwhile, when implementing embodiments of the present invention using firmware or software, firmware or software may be configured to include modules, procedures, or functions that perform the functions or operations of the present invention. Firmware or software configured to be stored in the memory 155 may be contained within the processor 155 or 180 or may be stored in the memory 160 or 185 and be driven by the processor 155 or 180. [

Layers of a wireless interface protocol between a terminal and a base station and a wireless communication system (network) are divided into a first layer (L1), a second layer (L2) based on the lower three layers of an open system interconnection ), And a third layer (L3). The physical layer belongs to the first layer and provides an information transmission service through a physical channel. An RRC (Radio Resource Control) layer belongs to the third layer and provides control radio resources between the UE and the network. The UE and the base station can exchange RRC messages through the RRC layer with the wireless communication network.

The processor 155 of the terminal and the processor 180 of the base station perform operations of processing signals and data except for the functions of the terminal 110 and the base station 105 to receive or transmit signals and the storage function, respectively But for the sake of convenience, the processors 155 and 180 are not specifically referred to hereafter. It may be said that the processor 155 or 180 performs a series of operations such as receiving and transmitting a signal and processing data instead of a storage function.

Hereinafter, the terminal 110 may be referred to as a mobile equipment (ME) or a user equipment (UE).

The identification module is a chip for storing various information for authenticating the use right of the mobile terminal and includes a user identification module (UIM), a subscriber identity module (SIM), a universal subscriber identity module module (USIM), and the like. The device equipped with the identification module can be manufactured in a smart card format. Hereinafter, the data in (U) SIM will be described with reference to (U) SIM. Also, in the following, the Subscriber Identity Module (SIM) may be referred to as a Universal Subscriber Identity Module (USIM).

(U) SIM may store various data such as a telephone directory in addition to the information for authentication and / or identification of the subscriber. For example, (U) SIM may store various element files (EF), and each EF may contain one or more records.

FIG. 2 shows the structure of an Elementary File_Abbreviated Dialing Number (EF_ADN) record according to an example.

EF_ADN may include Abbreviated Dialing Numbers (ADN) and / or Supplementary Service Control Strings (SSC). The EF_ADN may also include an identifier of the associated network / bearer capability and an identifier of the extended records. The EF_ADN may also include associated alpha-tagging.

With reference to FIG. 2, an Alpha Identifier that includes alpha-tagging of the associated dialing number may be stored in bytes 1 through X of EF_ADN, where X may be any natural number.

In the X + 1 byte, BCD number (Binary Code Decimal Number) / length of SSC contents (Length of BCD number / SSC contents) can be recorded. The length of the BCD number / SSC content includes the number of bytes following two data items including the actual BCD number / SSC information. The maximum value of the length of the BCD number / SSC contents is 11 even if the actual ADN / SSC information length is longer. By making the value of the extension 1 identifier not equal to 'FF', it can indicate that the ADN / SSC has an extension. The rest of the ADN / SSC information may be stored in EF_EXT1 (Elementary File_Extension 1) described later.

A Type of Number (TON) and a Numbering Plan Identification (NPI) may be stored in the X + 2 byte.

Also, a telephone number / SSC string (Dialing Number / SSC String) may be stored in the X + 3 to X + 12 bytes. Thus, the telephone number / SSC string may include a number of up to 20 digits (digits) and / or SSC information.

A Capability / Configuration 1 Record Identifier may be recorded in the X + 13 byte. The availability / configuration record identifier may identify the number of the record in EF_CCP1 (EF_Capability Configuration Parameters1) that contains the relevant availability / configuration parameters required for the call.

Extension 1 Record Identifier may be recorded in X + 14 bytes. The extended 1 record identifier identifies the number of the record containing the called party subaddress or additional data within EF_EXT1. If the ADN / SSC requires both the additional data and the destination secondary address, the extended 1 record identifier can identify the associated additional record.

Also, (U) SIM may include EF_ANR (EF_Additional Number). Some telephone numbers and / or auxiliary service control strings (SSCs) may be attached to one EF_ADN record using one or more EF_ANRs. The amount of additional number entries may be less than the amount of records in EF_ADN. Each record may include an additional telephone number or an auxiliary service control string. The additional number can not be shared among several phonebook entries. The first byte indicates whether the record is free or whether it is a type of additional number indicating the record number in the EF_AAS (AIS) containing the text to be displayed. The portion following the first byte represents the reference associated with the record in the additional number and EF_ADN. In addition, the ANR may include identifiers of extension records (e.g., Extension 1 Record Identifier) and identifiers of associated network / bearer availability.

FIG. 3 shows a structure of EF_EXT1 (Extension 1) according to an example.

EF_EXT1 may contain extension data of ADN / SSC. Extension data may occur when ADN / SSC or common digits greater than the 20 digit capacity of the ADN / SSC EF are required to follow an ADNS / SSC of less than 20 digits. The remainder is stored in EF_EXT1 as a record identified by a specific identification byte in the ADN / SSC EF. In this case, the EXT1 record is specified as additional data. In addition, the extension data may be generated by an associated called party subaddress. In this case, the EXT1 record can be specified as sub address data.

FIG. 3 (a) shows the structure of the EF_EXT1 record according to an example. The record type (record type) is recorded in the first byte of the EF_EXT1 record. 3 (b) shows one byte in which a record type composed of 8 bits of b1, b2, b3, b4, b5, b6, b7 and B8 is recorded. Here, one block means one bit, b1 can be LSB (Least Significant Bit) and B8 can be MSB (Most Significant Bit). The bits b3 to b8 of the EF_EXT1 record are reserved for future use (RFU) and are set to zero. The type of the EF_EXT1 record is set by setting the corresponding bit to 1, and only one type can be set for that record. Therefore, by setting b1 to 1, the type of the corresponding EF_EXT1 record can be set to the called party subaddress. Further, by setting b2 to 1, the type of the corresponding EF_EXT1 can be set as additional data. On the other hand, when b1 and b2 are set to " 00 ", the type of the EF_EXT1 record may be set to " unknown " FIG. 3C shows an example of the EF_EXT1 record set as additional data. In (c) of FIG. 3, when b2 is set to 1, the type of the corresponding EF_EXT1 record is set as additional data.

3 (a), extended data is recorded in the 2nd to 12th bytes. Extension data may include additional data or destination secondary addresses depending on the record type.

First, if the EF_EXT1 record is additional data, the number of remaining bytes of the ADN / SSC is recorded in the first byte of the extended data. The remaining bytes are coded in BCD according to the coding of the ADN / SSC. The unused nibble at the end is set to the "F" value. If the number of additional digits exceeds the capacity of the additional record, an identifier of the thirteenth byte may be used to form a chain for other records in EF_EXT1. In this case, the second byte (i.e., the first byte of the extension data) of all records for additional data within the same linkage is the number of bytes for the ADN / SSC in the same record whose value is not the same as "FF" '0A').

The case where the EF_EXT1 record is the destination side address will be described. The subaddress data may include information defined in 3GPP TS 24.008. Except for the information element identifier, all information defined in TS 24.008 shall be stored in the USIM. The length of the subaddress data is 22 bytes at most. If two extension records are required, these records are linked by an identifier field. An extended record containing the first part of the called party's secondary address can point to the record containing the second part.

An identifier is recorded in the thirteenth byte of the EF_EXT1 record. The identifier makes it possible to store more than 11 bytes of information by indicating a subsequent extension record. The extension record at the end of the association has an identifier of "FF" value. For example, if there is no further association for the extension record, the identifier is recorded with the value " FF ". However, if there is a succeeding link to the record, the number of the succeeding record is recorded in the identifier.

In the example of FIG. 4, the association of extension records associated with the ADN / SSC is shown. The EF_EXT1 record identifier of EF_ADN is set to 3. Thus, in this connection, the first EF_EXT1 record of the corresponding EF_ADN is Record 3. In addition, the identifier of record 3 points to the fourth EF_EXT1 record. In the same manner, record 4 specifies record 6, record 6 records 1, and so on. The identifier of record 1 has the value "FF", indicating the end of this association. Therefore, the EF_ADN record in this embodiment has an extended data association having the order of Record 3, Record 4, Record 6, and Record 1 of EF_EXT1. Here, the record type of record 3 and record 4 is set as additional data, and the record type of record 6 and record 1 is set as the destination side address. Therefore, the ADN / SSC has the last 27 digits or 28 digits of the entire ADN / SSC represented by records 3 and 4 (since the first 20 digits are stored in EF_ADN) 1 having a length of 11 bytes or more.

Also, (U) SIM may include Capability Configuration Parameters 1 (CCP1). EF_CCP1 may include the parameters of the required network and bearer availability and the parameters of the Mobile Terminal (ME) configuration associated with the call established using the phonebook entry.

For the sake of explanation, it is assumed that the record configuration of the EF in the (U) SIM is as follows. The (U) SIM telephone book entry to be deleted corresponds to the third record of EF_ADN, and the telephone directory entry of the record is the dialing number " 00112233445566778899012345678901234567899988776655443322110011p12345 ". Therefore, the numbers exceeding the 20-digit storage capacity of EF_ADN are stored in the records 1, 2 and 3 of EF_EXT in order. Record 3 of EF_ADN according to the above assumption is shown in FIG. Further, records 1, 2 and 3 of EF_EXT according to the above assumptions are shown in FIG.

A record deletion method in the conventional EF_ADN will be described with reference to FIGS. 5 and 6. FIG. In the case of deleting EF_ADN record 3 in FIG. 5, the mobile terminal must delete the related EF_EXT1 record (records 1, 2 and 3) before deleting EF_ADN record 3. To do this, it must check whether the corresponding EF_EXT1 records are referenced by other records in EF_ADN. Furthermore, as described above, since EF_EXT1 can be referred to by EF_ANR, it is necessary to check whether the EF_EXT1 record (records 1, 2, 3) is referenced by the record of EF_ANR by the record of EF_ANR. Accordingly, the mobile station must confirm the Extension 1 record identifier field value of the EF_ADN and EF_ANR records. In this case, when the records (records 1, 2 and 3) of EF_EXT1 are not referred to by the records of other EF_ADN and EF_ANR, the records (records 1, 2 and 3) of the corresponding EF_EXT1 are deleted using the "UPDATE RECORD" do. Also, the mobile terminal deletes the EF_ADN record 3 using the "UPDATE RECORD" command.

7 is a flowchart of a conventional telephone directory entry deletion.

In FIG. 7, EF_EXT1 records 1, 2, 3 and EF_ADN record 3 which are not referred to by other records by the above procedure are sequentially deleted by the "UPDATE RECORD" command. Thus, if the EF_ADN record to be deleted has three association records (e.g., EF_EXT1 record and / or EF_CCP1 record), at least four "UPDATE RECORD" commands are performed. Thus, if the mobile terminal wishes to remove one phonebook entry present in the (U) SIM, the number of interfaces may be increased by the number of records associated with that entry (e.g., EF_EXT1 and / or EF_CCP1 records) .

In addition, when the mobile terminal deletes the data of EF_EXT1 or EF_CCP1 which is still referred to by another record of EF_ADN or EF_ANR due to, for example, erroneous calculation of the reference number for EF_EXT1 or EF_CCP1 record, An EF_ADN or EF_ANR record referencing a record of an EF refers to an EF_EXT1 or EF_CCP1 record having invalid (i.e., already deleted) data, thereby losing information on the later part of the dialing number.

For example, assume that the telephone number of entry 1 of the telephone book is "111111111122222222223333333333" and the telephone number of entry 2 is "777777777788888888883333333333". The first 20 digits of the telephone number of entry 1 are stored in record 1 of EF_ADN. In addition, the first 20 digits of the telephone number of entry 2 are stored in record 2 of EF_ADN. In addition, the last 10 digits (3333333333) of the telephone number of EF_ADN records 1 and 2 can be stored in EF_EXT1 record 10. Thus, EF_ADN records 1 and 2 share EF_EXT1 record 10 and have the same extended 1 data identifier. In this case, when the mobile terminal deletes the EF_ADN record 1 and deletes the EF_EXT1 record 10 for reasons such as an error, the last ten digits of the telephone number of the telephone directory entry 2 are deleted.

Conversely, it is actually not referenced by EF_ADN or EF_ANR but should be deleted, but EF_EXT1 or EF_CCP1 records may not be deleted because of, for example, calculation errors on the number of references to EF_EXT1 or EF_CCP1 records. In this case, since the EF_EXT1 or EF_CCP1 record is actually stored without being used, there may be insufficient space for adding data when adding new data later.

To solve the above problems, it is desired to add a "CASCADE DELETE" command to the (U) SIM command. (U) The SIM can internally manage the reference count for each record of the referenced EF (for example, EF_EXT1, EF_CCP1) when it has a reference to another EF such as EF_ADN and EF_ANR. For example, the mobile terminal may store the number of references for each referenced record in the data storage space of the (U) SIM and update it whenever there is a change or periodically. In this case, when (U) SIM accesses the main EF (for example, EF_ADN or EF_ANR) through the "batch delete" command, not only the main record (EF_ADN or EF_ANR record) (For example, EF_EXT1 and / or EF_CCP1) is " 0 ", the records of the related EFs EF_EXT1 and EF_CCP1 are collectively deleted.

As described above with respect to FIG. 7, in order to delete an EF_ADN record having three association records in a conventional manner, at least four " UPDATE RECORD " must be performed. However, the method presented here can delete EF_ADN or EF_ANR records by performing a single " CASCADE DELETE " command. &Quot; Batch deletion " can be applied to EFs having links to other EFs (e.g., EF_EXT1, EF_CCP1) such as EF_ADN and EF_ANR. &Quot; Bulk delete " can delete some records of related EF as well as records in the current linear fixed EF. In addition, " batch deletion " can be performed only when the UPDATE access condition for the EF and the related EFs subjected to the " batch deletion "

When the " batch deletion " is received, the mobile terminal confirms that the main record (for example, EF_ADN or EF_ANR record) to be deleted has a reference to another record. If the main record has a reference to another record, the mobile terminal confirms the related record (e.g., EF_EXT1 or EF_CCP1 record) referenced by the main record, and if the value of the reference number of each related record is " 0 " In this case, the related records are deleted at once. On the other hand, the reference number of the related record referenced only by one main record may be set to "0" or "1", and when it is set to "1", if the reference number value of each related record is "1" And deletes the related records in a batch.

That is, when the mobile terminal indicates that the reference number among the related records of the main record to be deleted is referred to only by the main record to be deleted, the mobile terminal can delete the main record and related records at once. Also, the mobile terminal may delete some related records, which are referred to only by the main record among the related records, along with the corresponding main record based on the reference number. In addition, if the reference number of the related record related to the main record to be deleted indicates that the record is referenced by a record other than the main record, the mobile terminal may delete the main record and update the reference number of the related record. On the other hand, if the main record to be deleted does not have another record associated therewith, the mobile terminal may delete the main record based on the "batch delete" command.

Referring again to FIG. 5 and FIG. 6, the mobile terminal may receive a " delete batch " command for EF_ADN record 3. The " delete batch " command may include an ID (e.g., EF_ADN or EF_ANR) of the file to be deleted and a record number (e.g., record 3 of FIG. 5). In this case, the mobile terminal checks whether a record related to the record to be deleted (for example, EF_EXT1 or EF_CCP1 record) is referred to by another record. 5 and 6, if the EF_EXT1 records 1, 2 and 3 are not referred to by other records, the mobile terminal may store the EF_ADN record 3 and the EF_EXT1 records 1, 2 and 3 in a lump Can be deleted.

On the other hand, when the main record to be deleted does not have a reference to another record, the mobile terminal can delete the main record through a "batch delete" command.

In addition, when the related record (for example, EF_EXT1 or EF_CCP1 record) referenced by the main record to be deleted is referred to by another record (for example, EF_ADN or EF_ANR record not to be deleted) You can also delete only the main record and update the reference count of the related record.

The mobile terminal can reduce the number of interfaces between the mobile terminal and the (U) SIM by using the " delete batch " command proposed by the present disclosure. Table 1 below shows an example of the effect of reducing the interface according to the number of deletes and the number of records of the main EF and the related EF to be deleted.

Therefore, it is possible to reduce the number of interfaces through the " delete batch " command presented by the present disclosure, and it is possible to reduce the number of EFs (for example, EF_ADN or EF_ANR) EF_EXT1 and / or EF_CCP1) can be prevented. In addition, it is possible to prevent the (U) SIM data from being wasted due to the malfunction of the mobile terminal.

Table 2 shows an instruction table according to one example. Table 2 is a simplified table of Table 10.5 of Section 10.2.1 of ETSI TS 102 221 that adds the "CASCADE DELETE" proposed in this disclosure to the command table, Can be improved. In addition, for example, the parameters and data of " batch deletion " may be set as shown in Table 3 below.

The embodiments described above are those in which the elements and features of the present invention are combined in a predetermined form. Each component or feature shall be considered optional unless otherwise expressly stated. Each component or feature may be implemented in a form that is not combined with other components or features. It is also possible to construct embodiments of the present invention by combining some of the elements and / or features. The order of the operations described in the embodiments of the present invention may be changed. Some configurations or features of certain embodiments may be included in other embodiments, or may be replaced with corresponding configurations or features of other embodiments. It is clear that the claims that are not expressly cited in the claims may be combined to form an embodiment or be included in a new claim by an amendment after the application.

It will be apparent to those skilled in the art that the present invention may be embodied in other specific forms without departing from the spirit or essential characteristics thereof. Accordingly, the above description should not be construed in a limiting sense in all respects and should be considered illustrative. The scope of the present invention should be determined by rational interpretation of the appended claims, and all changes within the scope of equivalents of the present invention are included in the scope of the present invention.

Claims (8)

A method of managing data in a subscriber identity module (SIM) of a mobile terminal,
A reference count indicating the number of times each of the records in the second EF stored in the SIM is referenced by records of other EFs in the SIM excluding the second EF, Storing;
Receiving a cascade delete command for a first record in a first Elementary File (EF) stored in the SIM; And
Wherein the reference number of the at least one second record in the second EF referenced by the first record indicates that the at least one second record is only referenced by the first record, ≪ / RTI > wherein the second record of the data is deleted. The method according to claim 1,
If the reference number of the at least one second record indicates that the at least one second record is referenced by a record other than the first record then the first record is deleted and the reference of the at least one second record And updating the number. The method according to claim 1,
Wherein the first EF is an Abbreviated Dialing Number (EF_ADN) or an EF_ANR (Additional Number). The method according to claim 1,
Wherein the second EF is at least one of EF_EXT1 (Extension 1) and EF_CCP1 (Capability Configuration Parameters 1, CCP1). The method according to claim 1,
Wherein the SIM is a universal subscriber identity module (Universal SIM, USIM). A mobile terminal comprising a subscriber identity module (SIM)
A radio frequency unit; And
A processor,
The processor comprising:
Storing, in the SIM, a reference count in which each record in a second elementary file stored in the SIM is referenced by records of other EFs in the SIM except for the second EF,
Receiving a cascade delete command for a first record in a first elementary file (EF) stored in the SIM,
Wherein the reference number of the at least one second record in the second EF referenced by the first record indicates that the at least one second record is only referenced by the first record, And deletes the second record of the mobile terminal. The method according to claim 6,
The processor comprising:
If the reference number of the at least one second record indicates that the at least one second record is referenced by a record other than the first record then the first record is deleted and the reference of the at least one second record The mobile terminal updates the number. 8. The method of claim 7,
Wherein the SIM is a universal subscriber identity module (Universal SIM, USIM).

Images