User equipment to personalize use of service and operating method thereof

An operating method of user equipment configured to personalize use of service is provided. The user equipment includes a storage that stores personalization management information including pieces of personalization information and pieces of service operator information corresponding to each of the pieces of personalization information. The operating method includes accessing the storage to read the personalization management information and, from the personalization management information, detecting personalization information and service operator information matched to reference information registered in the user equipment, and determining whether a user is able to use the service, by using user information that is received from the outside and a result of the detection.

CROSS-REFERENCE TO RELATED APPLICATION

This application claims priority from Korean Patent Application No. 10-2016-0119558, filed on Sep. 19, 2016, in the Korean Intellectual Property Office, the disclosure of which is incorporated by reference herein in its entirety.

BACKGROUND

Methods, apparatuses, and articles of manufacture consistent with the present disclosure relate to user equipment, and more particularly, to user equipment configured to personalize use of service and an operating method thereof.

Personalization of user equipment refers to restricting the use of user equipment by using a code stored in the user equipment, whereby, when a personalization category is activated, the user may normally use the service provided by a service operator only when a code value extracted from a smart card of the user corresponds to a code value stored in the user equipment. Personalization information of the user equipment, which is required by each service operator, may be different, and thus, when the service operator is changed, information associated with the personalization of the user equipment has to be changed.

SUMMARY

It is an aspect to provide user equipment which may efficiently improve use of service by using personalization management information including a plurality of pieces of personalization information and a plurality of pieces of service operator information corresponding to each of the plurality of pieces of personalization information, and an operating method thereof.

According to an aspect of an example embodiment, there is provided an operating method of user equipment configured to personalize use of service, wherein the user equipment includes a storage configured to store personalization management information including a plurality of pieces of personalization information and a plurality of pieces of service operator information corresponding to each of the plurality of pieces of personalization information, the operating method including accessing the storage to read the personalization management information and, from the personalization management information, detecting personalization information and service operator information matched to reference information registered in the user equipment, and determining whether a user is able to use the service, by using user information that is received from the outside and a result of the detection.

According to another aspect of an example embodiment, there is provided user equipment for using a service, the user equipment including a storage configured to store personalization management information including a plurality of pieces of personalization information and a plurality of pieces of service operator information corresponding to each of the plurality of pieces of personalization information, a smart card configured to store user information about a user, and a personalization module configured to detect personalization information and service operator information matched to an activated personalization category from among a plurality of personalization categories and a service operator, respectively, from the personalization management information, and determine whether the user is able to use the service, by using a result of the detection and the user information.

According to another aspect of an example embodiment, there is provided user equipment for using a service User equipment for using a service, the user equipment comprising a storage configured to store personalization management information comprising a plurality of pieces of personalization information stored sequentially in the storage, and a plurality of pieces of service operator information stored sequentially in the storage corresponding to each of the plurality of pieces of personalization information; a smart card configured to store user information about a user; and a personalization module configured to receive an activated personalization category and a pre-set service operator, read the personalization management information from the storage and sequentially search through the personalization management information to detect a match between a piece of personalization information and the activated personalization category, and search through the personalization management information to detect a match between the pre-set service operator and a piece of the service operator information, and determine whether the user is able to use the service, by using a result of the detection and the user information.

DETAILED DESCRIPTION

Hereinafter, example embodiments of the present inventive concept will be described in detail by referring to the accompanying drawings.

FIG. 1is a block diagram of an example of a wireless communication system configured to perform a personalization operation according to an example embodiment.

As illustrated inFIG. 1, a service operator may provide a service, such as communication via a downlink channel and an uplink channel, to user equipment (UE)100, by using a base station200. Here, the UE100for using the service may perform a personalization operation so that only a user configured to use the service may use the service provided by the service operator via the UE100, and a user not configured to use the service may not normally use the service provided by the service operator via the UE100. Whether a user that aims to use the service is able to use the service may be determined via the personalization operation of the UE100. For example, the determination may be performed by comparing information about the user stored in a smart card of the user with information stored in the UE100.

The UE100may be stationary or non-stationary, and may include various devices which may communicate with and exchange data and/or control information with the base station200. For example, the UE100may be referred to as terminal equipment, a mobile station (MS), a mobile terminal (MT), a user terminal (UT), a subscriber station (SS), a wireless device, a handheld device, etc. The base station (BS)200may generally refer to a fixed station configured to communicate with a UE and/or another base station. The BS200may communicate with and exchange data and control information with UEs and/or other base stations. For example, the BS200may also be referred to as Node B, evolved-Node B (eNB), a base transceiver system (BTS), an access point (AP), etc. A wireless communication network may support communication among a plurality of users sharing available network resources. A UMTS terrestrial radio access network (UTRAN), one of such wireless communication networks, is a radio access network (RAN), defined by a universal mobile telecommunications system (UMTS), one of the 3rdgeneration mobile communication technologies that are standardized by the 3rdgeneration partnership project (3GPP). UMTS supports various air interface standards, such as wideband-code division multiple access (W-CDMA), time division-code division multiple access (TD-CDMA), and time division-synchronous code division multiple access (TD_SCDMA).

The UE100may include an antenna AT, a transceiver module110, a processor120, a personalization module130, and a data storage140. Each of the components included in the UE100may be a hardware block including an analog circuit and/or a digital circuit, or a software block including a plurality of instructions executed by a processor, etc.

The transceiver module110may receive radio frequency (RF) signals from the base station200via the antenna AT, and may transmit signals processed in the UE100to the base station200as the RF signals via the antenna AT. The UE100may use the service provided by the service operator via the transceiver module110.

The processor120may control general operations of the UE100so that the user may use the service provided by the service operator. The processor120may be a microprocessor or a central processing unit (CPU). When the UE100is booted, for example, when the UE100is put in a state of “on” from a state of “off,” the processor120may control a start of the personalization operation. In detail, when the UE100is booted, the processor120may control an operation of the personalization module130by applying a control signal CS_P to the personalization module130. Further, the processor120may set information indicating a personalization category which is currently activated from among a plurality of personalization categories and a service operator providing a service via the UE100. The data storage140may store personalization management information. The personalization management information may include a plurality of pieces of personalization information and a plurality of pieces of service operator information corresponding to each of the plurality of pieces of personalization information. Also, the personalization management information may have various data formats. Detailed descriptions regarding this aspect will be given later.

The personalization module130according to an example embodiment may receive the information about the currently activated personalization category and the service operator providing the service from the processor120. The personalization module130may detect the personalization information matched to the activated personalization category from among the plurality of personalization categories and the service operator information matched to the service operator providing the service, from the personalization management information (PMI) stored in the data storage140. The personalization module130may extract a first data set Data Set_1(DS_1) including at least one reference source code from the personalization management information, as a result of the detection. Also, the personalization module130may receive a second data set DS_2including at least one user source code corresponding to the activated personalization category from the outside, and the second data set DS_2may correspond to information about the current user. The personalization module130may generate at least one reference code by using the first data set DS_1and generate at least one user code by using the second data set DS_2. The personalization module130may compare the reference code with the user code and determine whether the current user may use the service based on a result of the comparison.

The processor120may receive a result signal RS from the personalization module130and when it is determined that the current user may use the service with reference to the result signal RS, may control the UE100so that the current user may normally use the service. Also, when it is determined that the current user may not use the service with reference to the result signal RS, the processor120may control the UE100so that the current user may not use the service. However, regardless of whether the current user may or may not use the service, the processor120may control the UE100such that the current user may use an emergency call service. As described above, the UE100may perform the personalization operation so that only the user configured to use the service may use the service, by using the personalization management information.

FIG. 2is a block diagram of an example of a wireless communication system configured to perform a personalization operation according to another example embodiment.

Referring toFIG. 2, compared toFIG. 1, UE100′ may further include a smart card150′. Other components of the UE100′ may be the same as those of the UE100illustrated inFIG. 1. The smart card150′ may be at least one of a subscriber identity module (SIM), a universal SIM (USIM), and a user identity module (UIM). However, it is only an example embodiment, and the smart card150′ may include various other modules. The smart card150′ may be inserted into or removed from the UE100′, and when the smart card150′ is inserted into the UE100′, a processor120′ may control an operation of a personalization module130′. The personalization module130′ may receive data from the smart card150′, and extract a second data set DS_2from the data corresponding to user information of a current user from the smart card150′. According to an example embodiment, a user code necessary to perform the personalization operation may vary according to a currently activated personalization category, and thus, a user source code necessary to generate the user code may vary according to the activated personalization category. The personalization module130′ may extract the second data set DS_2including at least one user source code necessary to generate the user code, based on the currently activated personalization category. The personalization module130′ may determine whether the current user may use the service by using a first data set DS_1extracted from personalization management information of a data storage140′ and the second data set DS_2extracted from the smart card150′.

FIG. 3is a detailed block diagram of a personalization module330of a UE according to an example embodiment.

Referring toFIG. 3, the personalization module330may include a first code generator331, a second code generator332, a comparator333, and a decision circuit334. The first code generator331may receive first information Act_PT indicating an activated personalization category and second information Preset_OT indicating a pre-set service operator from the processor120ofFIG. 1. The first information Act_PT and the second information Preset_OT may be reference information RI pre-registered in the UE. According to an example embodiment, the processor of the UE may store the reference information RI, and the reference information RI may be changed later. The first code generator331may extract a first data set DS_1including at least one reference source code from personalization management information of a data storage340, by using the first information Act_PT and the second information Preset_OT. The first code generator331may generate at least one reference code RC by using the first data set DS_1and transmit the at least one generated reference code RC to the comparator333. The second code generator332may receive the first information Act_PT from the processor120ofFIG. 1. The second code generator332may extract a second data set DS_2including at least one user source code necessary to generate a user code UC, from information stored in the smart card350, by using the first information Act_PT. The second code generator332may generate at least one user code UC by using the second data set DS_2and transmit the at least one generated user code UC to the comparator333.

The comparator333may determine whether the received reference code RC and the user code UC correspond to each other by comparing the received reference code RC and the user code UC. The comparator333may compare the reference code RC with the user code UC and transmit a comparison result signal CRS to the decision circuit334. The decision circuit334may determine whether a user may use a service, based on the comparison result signal CRS. According to an example embodiment, when the reference code RC and the user code UC correspond to each other, the decision circuit334may determine that the user may use the service, and when the reference code RC and the user code UC do not correspond to each other, the decision circuit334may determine that the user may not use the service. The decision circuit334may generate a determination result signal RS and transmit the generated determination result signal RS to the processor120ofFIG. 1. The processor120ofFIG. 1may control an operation of the UE100based on whether the user may use the service or not.

FIGS. 4A through 4Care diagrams of a data format for describing personalization management information PMI including personalization information and service operator information corresponding thereto according to an example embodiment.

Referring toFIG. 4A, the personalization management information PMI may include a plurality of pieces of personalization information PI and a plurality of pieces of service operator information SOI corresponding to each of the plurality of pieces of personalization information. Each personalization information PI may include a personalization tag TAG_PERSO_x indicating a personalization category, value data VALUE_PERSO_x including service operator information SOI corresponding to the personalization category, and length data LENGTH_PERSO_x about the personalization information PI. The length data LENGTH_PERSO_x may indicate a data length of the value data VALUE_PERSO_x, and the data length of the value data VALUE_PERSO_x may correspond to a data length of the service operator information SOI. Also, a value of the length data LENGTH_PERSO_x may vary based on the data length of the value data VALUE_PERSO_x. As such, the personalization information PI may have a data format having a form of a tag, a length, and a value (TLV).

The service operator information SOI may include an operator tag TAG_OP_y indicating a type of a service operator, operator value data VALUE_OP_y including at least one reference source code corresponding to the type of the service operator, and length data LENGTH_OP_y about the service operator information SOI. The length data LENGTH_OP_y may include information indicating a data length of the operator value data VALUE_OP_y. Also, a value of the length data LENGTH_OP_y may vary based on the data length of the operator value data VALUE_OP_y. As such, the service operator information SOI may have a data format having a form of a tag, a length, and a value (TLV). However, the data format of the personalization management information PMI illustrated inFIG. 4Ais not limited thereto, and may include various data formats in which the plurality of pieces of service operator information SOI may correspond to each personalization information PI.

Referring toFIG. 4B, according to an example embodiment, the operator tag TAG_OP_1of the service operator information SOI may have a value “K1,” the operator value data VALUE_OP_1may include a reference source code RS_code, “123 456,” and the length data LENGTH_OP_1may have a value “L1” corresponding to a length of the reference source code RS_code.

Referring toFIG. 4C, the operator value data VALUE_OP_1of the service operator information SOI may include a greater number of reference source codes RS_code_1and RS_code_2, compared toFIG. 4B. That is, the operator value data VALUE_OP_1may include the first reference source code RS_code_1, “123 456,” and a second reference source code RS_code_2, “123 457.” Also, the operator value data VALUE_OP_1may further include an identifier for distinguishing the first reference source code RS_code_1and the second reference source code RS_code_2. Accordingly, the length data LENGTH_OP_1may have a value “L1”, which is greater than the value “L1” inFIG. 4B.

FIG. 5is a table Table_1showing a relationship between a personalization tag and a personalization category of personalization information, according to an example embodiment.

A plurality of personalization categories may be set in UE, and the UE may perform a personalization operation based on activated personalization categories from among the plurality of personalization categories. Also, one or more personalization categories may be activated, and one or more activated personalization categories may be deactivated later, and other personalization categories may be activated. The plurality of personalization categories may include network personalization (NP), network subset personalization (NSP), service operator personalization (SOP), corporate personalization (CP), and SIM/USIM personalization (S/UP). The 3GPP recommends the personalization operation in accordance with the NP, the NSP, the SP, the CP, and the S/UP, in “3GPP technical specification 22.022,” which defines personalization of UE.

Referring toFIG. 5, as illustrated in the table Table_1, the personalization management information stored in the data storage140ofFIG. 1may include first through fifth pieces of personalization information PI_1through PI_5. According to an example embodiment, a first personalization tag TAG_PERSO_1included in the first personalization information PI_1may indicate the NP. A second personalization tag TAG_PERSO_2included in the second personalization information PI_2may indicate the NSP. A third personalization tag TAG_PERSO_3included in the third personalization information PI_3may indicate the SOP. A fourth personalization tag TAG_PERSO_4included in the fourth personalization information PI_4may indicate the CP. A fifth personalization tag TAG_PERSO_5included in the fifth personalization information PI_5may indicate the S/UP. Further, the personalization management information may further include Nthpersonalization information PI_N, and an Nthpersonalization tag TAG_PERSO_N of the Nthpersonalization information PI_N may indicate an optional personalization (OP) category, based on which other personalization operations may be performed.

FIG. 6is a table Table_2showing a relationship between an operator tag of service operator information and a service operator, according to an example embodiment.

The service operator providing a service that a user aims to use may be pre-set in the UE, and the UE may perform a personalization operation based on the pre-set service operator. Also, a plurality of service operators may be pre-set, and later, the pre-set service operators may be changed to other service operators.

Referring toFIG. 6, as illustrated the table Table_2, the personalization management information stored in the data storage140ofFIG. 1may include the plurality of pieces of personalization information and the plurality of pieces of service operator information corresponding to each of the plurality of pieces of personalization information. For example, the personalization management information may include first through Mthpieces of service operator information SOP_1through SOP_M corresponding to the first personalization information PI_1ofFIG. 5. A first operator tag TAG_OP_1of the first service operator information SOP_1may indicate a first service operator Operator #1, a second operator tag TAG_OP_2may indicate a second service operator Operator #2, and an Mthoperator tag TAG_OP_M may indicate an Mthservice operator Operator #M.

FIGS. 7A through 7Care diagrams for describing a personalization operation of UE according to an example embodiment.

Referring toFIG. 7A, the personalization management information PMI may include first through Nthpieces of personalization information PI_1through PI_N, and first through Mthpieces of service operator information SOI_1_1through SOI_1_M, SOI_2_1through SOI_2_M, SOI_3_1through SOI_3_M, . . . , SOI_N_1through SOI_N_M corresponding to each of the plurality of pieces of personalization information PI_1through PI_N. That is, first personalization information PL_1may include first through Mthpieces of service operator information SOI_1_1through SOI_1_M, and the second personalization information PL_2may include first through Mthpieces of service operator information SOI_2_1through SOI_2_M, etc. An Nthpersonalization tag TAG_PERSO_N of the Nthpersonalization information PI_N may indicate an Nthpersonalization category. Nthvalue data VALUE_PERSO_N of the Nthpersonalization information PI_N may include the first through Mthpieces of service operator information SOI_N_1through SOI_N_M. Also, Nthlength data LENGTH_PERSO_N of the Nthpersonalization information PI_N may indicate a length of the Nthvalue data VALUE_PERSO_N.

The first through Mthpieces of service operator information SOI_1_1through SOI_1_M, SOI_2_1through SOI_2_M, SOI_3_1through SOI_3_M, . . . , SOI_N_1through SOI_N_M corresponding to each of the plurality of pieces of personalization information PI_1through PI_N are described with reference toFIGS. 4B through 4C, and thus, detailed descriptions thereof will be omitted. As described above, the personalization management information PMI may be sequentially stored in an area of the data storage340ofFIG. 3. For example, the N−1thpersonalization information PI_N−1 may be stored in an area of the data storage340, and the Nthpersonalization information PI_N may be stored in a data area adjacent to the data area in which the N−1thpersonalization information PI_N−1 is stored. As a result, a distance between areas in which the N−1thpersonalization information PL_N−1 and the Nthpersonalization information PL_N are stored may correspond to a value of length data LENGTH_PERSO_N−1 of the N−1thpersonalization information PL_N−1.

Also, the plurality of pieces of service operator information corresponding to each of the plurality of pieces of personalization information PI_1through PI_N may be sequentially stored in the data storage340. For example, the M−1thservice operator information SOI_1_M−1 corresponding to the N−1thpersonalization information PI_N−1 may be stored in an area of the data storage340, and the Mthservice operator information SOI_1_M may be stored in a data area adjacent to the data area in which the M−1thservice operator information SOI M−1 is stored. As a result, a distance between areas in which the M−1thservice operator information SOI_1_M−1 and the Mthservice operator information SOI_1_M are stored may correspond to a value of length data LENGTH_OP_M−1 of the M−1thservice operator information SOI_1_M−1. InFIG. 7A, it is illustrated that the number of pieces of service operator information corresponding to each of the plurality of pieces of personalization information PI_1through PI_N is M. However, it is only an example embodiment, and the number of pieces of service operator information corresponding to each of the plurality of pieces of personalization information PI_1through PI_N may vary. For example, the number of pieces of service operator information corresponding to the personalization information PL_1may be 6 (i.e., M=6 for PL_1), while the number of pieces of service operator information corresponding to the personalization information PL_2may be 7 (i.e., M=7 for PL_2), etc.

Hereinafter, the operation of the personalization module330ofFIG. 3will be described in detail with reference to the illustration ofFIG. 7A.

Referring toFIG. 3, the first code generator331according to an example embodiment may access the data storage340, and detect personalization information including a personalization tag matched to an activated personalization category from the personalization management information PMI, based on the first information Act_PT. Here, the first code generator331may detect the personalization information based on length data of each of the pieces of personalization information. However, this is only an example and other methods may be used to perform the detection. The first code generator331may detect service operator information including an operator tag matched to a pre-set service operator from among a plurality of pieces of service operator information corresponding to the detected personalization information, based on the second information Preset_OT. Here, the first code generator331may detect the service operator information based on length data of each of the pieces of service operator information. However, this is only an example and other methods may be used to perform the detection. The first code generator331may extract operator value data of the detected service operator information as the first data set DS_1.

Referring toFIGS. 3 and 7B, the first code generator331may receive the first information Act_PT indicating that a third personalization category PERSO_3is activated and the second information Preset_OT indicating that a second service operator OP_2is pre-set. Also, the first code generator331may receive a start address corresponding to an address of the data storage340in which a first personalization tag TAG_PERSO_1of the first personalization information PI_1is stored. That is, the start address may be an address of a point of an area of the data storage340, in which the plurality of pieces of personalization information PI_1through PI_N are started to be stored.

With reference to the start address, first, the first code generator331may read the first personalization information PI_1and match the first personalization tag TAG_PERSO_1of the first personalization information PI_1with the third personalization category PERSO_3. Since the first personalization tag TAG_PERSO_1and the third personalization category PERSO_3are mismatched, the first code generator331may find a location of a second personalization tag TAG_PERSO_2of the second personalization information PI_2based on the length data LENGTH_PERSO_1of the first personalization information PI_1, read the second personalization tag TAG_PERSO_2, and match the second personalization tag TAG_PERSO_2with the third personalization category PERSO_3. Since the second personalization tag TAG_PERSO_2and the third personalization category PERSO_3are mismatched, the first code generator331may find a location of a third personalization tag TAG_PERSO_3of the third personalization information PI_3based on the length data LENGTH_PERSO_2of the second personalization information PI_2, read the third personalization tag TAG_PERSO_3, and match the third personalization tag TAG_PERSO_3with the third personalization category PERSO_3. Since the third personalization tag TAG_PERSO_3is matched to the third personalization category PERSO_3, the first code generator331may detect the third personalization information PI_3.

The first code generator331may detect the service operator information matched to the second service operator OP_2from among the plurality of pieces of service operator information SOI_3_1through SOI_3_M included in the value data VALUE_PERSO_3of the detected third personalization information PI_3. First, the first code generator331may read and match a first operator tag TAG_OP_1of the first service operator information SOI_3_1with the second service operator OP_2. Since, the first operator tag TAG_OP_1and the second service operator OP_2are mismatched, the first code generator331may find a location of a second operator tag TAG_OP_2of the second service operator information SOI_3_2based on length data LENGTH_OP_1of the first service operator information SOI_3_1and read and match the second operator tag TAG_OP_2with the second service operator OP_2. Since the second operator tag TAG_OP_2and the second service operator OP_2are matched, the first code generator331may detect the second service operator information SOI_3_2and extract a reference source code RS_code from second operator value data VALUE_OP_2of the second service operator information SOI_3_2.

The first code generator331may generate the reference code RC by using the reference source code RS_code. According to an example embodiment, when the reference code RC is encoded by using a certain encoding method and stored in the data storage340as the reference source code RS_code, the first code generator331may generate the reference code RC by decoding the reference source code RS_code. However, it is only an example embodiment, and when the reference code RC is not encoded, the first code generator331may transmit the reference source code RS_code extracted from the data storage340to the comparator333as the reference code RC. The second code generator332may need a different user source code to generate the user code UC, according to an activated personalization category. Thus, the second code generator332may extract at least one user source code necessary to generate the user code UC from information stored in the smart card350, based on the first information Act_PT indicating that the received third personalization category PERSO_3is activated.

InFIG. 7B, at least one of the activated personalization category and the pre-set service operator that the first code generator331uses to extract the reference source code RS_code may be changed later.FIG. 7Cillustrates an operation of the personalization module330when the activated personalization category is changed from the third personalization category PERSO_3to the second personalization category PERSO_2and the pre-set second service operator OP_2is changed to the first service operator OP_1.

Referring toFIGS. 3 and 7C, when the pre-set service operator is changed from the second service operator OP_2to the first service operator OP_1, an additional update operation may not be performed on the personalization management information stored in the data storage340, and the personalization module330may newly detect the personalization information and the service operator information. The first code generator331of the personalization module330may detect the second personalization information PI_2including the second personalization tag TAG_PERSO_2matched to the second personalization category PERSO_2by using the same method as described with reference toFIG. 7B. Then, the first code generator331may detect the first service operator information SOI_2_1matched to the first service operator OP_1from among the plurality of pieces of service operator information SOI_2_1through SOI_2_M included in the value data VALUE_PERSO_2of the detected second personalization information PI_2. The first code generator331may extract a reference source code RS_code′ from the operator value data VALUE_OP_1of the first service operator information SOI_2_1.

As described above, the UE according to the example embodiments may perform a rapid personalization operation since there is no need for an additional operation of updating the personalization management information stored in the data storage, even if the activated personalization category and the pre-set service operator are changed later.

FIGS. 8A through 8Bare diagrams for describing a personalization operation of UE according to another example embodiment.

Referring toFIG. 8A, the personalization management information PMI may include first through Nthpieces of personalization information PI_1through PI_N, and first through Mthpieces of service operator information SOI_1_1through SOI_1_M, SOI_2_1through SOI_2_M, SOI_3_1through SOI_3_M, . . . , SOI_N_1through SOI_N_M corresponding to each of the pieces of personalization information PI_1through PI_N. The personalization management information PMI may be stored in the data storage340ofFIG. 3. According to an example embodiment, the first through Nthpieces of personalization information PI_1through PI_N may be stored in a first data area Data_area_1of the data storage340, and the first through Mthpieces of service operator information SOI_1_1through SOI_1_M, SOI_2_1through SOI_2_M, SOI_3_1through SOI_3_M, . . . , SOI_N_1through SOI_N_M corresponding to each of the pieces of personalization information PI_1through PI_N may be stored in a second data area Data_area_2of the data storage340. According to an example embodiment, the first through Nthpieces of personalization information PI_1through PI_N may be sequentially stored in the first data area Data_area_1. For example, the N−1thpersonalization information PI_N−1 may be stored in an area of the first data area Data_area_1of the data storage340ofFIG. 3, and the Nthpersonalization information PI_N may be stored in an area adjacent to the area of the first data area Data_area_1, in which the N−1thpersonalization information PI_N−1 is stored. As a result, a distance between areas in which the N−1thpersonalization information PL_N−1 and the Nthpersonalization information PL_N are stored may correspond to a value of the length data LENGTH_PERSO_N−1 of the N−1thpersonalization information PL_N−1.

Also, the plurality of pieces of service operator information SOI_1_1through SOI_1_M, SOI_2_1through SOI_2_M, SOI_3_1through SOI_3_M, . . . , SOI_N_1through SOI_N_M corresponding to each of the pieces of personalization information PI_1through PI_N may be sequentially stored in a second data area Data_area_2of the data storage340. For example, the M−1thservice operator information SOI_N_M−1 corresponding to the Nthpersonalization information PI_N may be stored in an area of the second data area Data_area_2, and the Mthservice operator information SOI_N_M may be stored in an area adjacent to the area of the second data area Data_area_2, in which the M−1thservice operator information SOI_N_M−1 is stored. As a result, a distance between areas in which the M−1thservice operator information SOI_1_M−1 and the Mthservice operator information SOI_1_M are stored may correspond to a value of the length data LENGTH_OP_M−1 of the M−1thservice operator information SOI_N_M−1.

Hereinafter, to describe the personalization information again, Nthvalue data VALUE_PERSO_N of the Nthpersonalization information PI_N may include a start address AddrN indicating a location of a point of the second data area Data_area_2, in which the first through Mthpieces of service operator information SOI_N_1through SOI_N_M are started to be stored. For example, the start address AddrN may be an address of a data area in which the first operator tag TAG_OP_1of the first service operator information SOI_N_1corresponding to the Nthpersonalization information PI_N is stored. Also, the Nthlength data LENGTH_PERSO_N of the Nthpersonalization information PI_N may indicate a data length of the Nthvalue data VALUE_PERSO_N. That is, the Nthlength data LENGTH_PERSO_N of the Nthpersonalization information PI_N may correspond to a data length of the start address AddrN.

Hereinafter, an operation of the personalization module330ofFIG. 3will be described in detail with reference to the illustration ofFIG. 8B.

Referring toFIGS. 3 and 8B, the first code generator331may receive the first information Act_PT indicating that the third personalization category PERSO_3is activated and the second information Preset_OT indicating that the second service operator OP_2is pre-set. Also, the first code generator331may receive a start address corresponding to an address of the data storage340in which the first personalization tag TAG_PERSO_1of the first personalization information PI_1is stored. That is, the start address may indicate a point of the first data area Data_area_1of the data storage340, in which the plurality of pieces of personalization information PI_1through PI_N are started to be stored.

With reference to the start address, first, the first code generator331may read and match the first personalization tag TAG_PERSO_1of the first personalization information PI_1with the third personalization category PERSO_3. Since the first personalization tag TAG_PERSO_1and the third personalization category PERSO_3are mismatched, the first code generator331may find a location of the second personalization tag TAG_PERSO_2of the second personalization information PI_2based on the length data LENGTH_PERSO_1of the first personalization information PI_1and read and match the second personalization tag TAG_PERSO_2with the third personalization category PERSO_3. Since the second personalization tag TAG_PERSO_2and the third personalization category PERSO_3are mismatched, the first code generator331may find a location of the third personalization tag TAG_PERSO_3of the third personalization information PI_3based on the length data LENGTH_PERSO_2of the second personalization information PI_2and read and match the third personalization tag TAG_PERSO_3with the third personalization category PERSO_3. Since the third personalization tag TAG_PERSO_3and the third personalization category PERSO_3are matched, the first code generator331may detect the third personalization information PI_3.

The first code generator331may access the first service operator information SOI_3_1corresponding to the third personalization information PI_3stored in the second data area Data_area_2of the data storage340, with reference to a third address Addr3 included in the value data VALUE_PERSO_3of the detected third personalization information PI_3. The first code generator331may read and match the first operator tag TAG_OP_1of the first service operator information SOI_3_1with the second service operator OP_2. Since the first operator tag TAG_OP_1and the second service operator OP_2are mismatched, the first code generator331may find a location of the second operator tag TAG_OP_2of the second service operator information SOI_3_2based on the length data LENGTH_OP_1of the first service operator information SOI_3_1, and read and match the second operator tag TAG_OP_2with the second service operator OP_2. Since the second operator tag TAG_OP_2and the second service operator OP_2are matched, the first code generator331may detect the second service operator information SOI_3_2and extract a reference source code RS_code from the second operator value data VALUE_OP_2of the second service operator information SOI_3_2. Sequential operations of the personalization module330are described in detail with reference toFIG. 7B, and thus, will not be repeatedly described.

FIG. 9is a block diagram for describing an operation of a personalization module430of UE according to another example embodiment.

Referring toFIG. 9, the personalization module430may include a first code generator431, a second code generator432, a comparator433, and a decision circuit434. According to an example embodiment, the first code generator431may generate a plurality of user codes in response to received second information Preset_OT indicating a plurality of pre-set service operators. In detail, the first code generator431may use first information Act_PT indicating a second personalization category PERSO_2activated by the first processor120and the second information Preset_OT indicating a first pre-set service operator OP_1and a second pre-set service operator OP_2to extract a first data set DS_1afrom personalization management information of a data storage440. For example, referring toFIG. 7A, the first data set DS_1amay include the first operator value data VALUE_OP_1of the first service operator information SOI_2_1corresponding to the second personalization information PI_2and the second operator value data VALUE_OP_2of the second service operator information SOI_2_2.

The first code generator431may generate a first reference code RC1by using the first operator value data VALUE_OP_1of the first service operator information SOI_2_1and a second reference code RC2by using the second operator value data VALUE_OP_2of the second service operator information SOI_2_2. The first code generator431may provide the first reference code RC1and the second reference code RC2to the comparator433. The second code generator432may use the first information Act_PT to extract a second data set DS_2afrom information stored in the smart card450and generate the user code UC. The second code generator432may provide the user code UC to the comparator433.

The comparator433may compare the first reference code RC1with the user code UC to determine whether the first reference code RC1corresponds to the user code UC, and compare the second reference code RC2with the user code UC to determine whether the second reference code RC2corresponds to the user code UC. The comparator433may transmit a comparison result signal CRS_a to the decision unit434. According to an example embodiment, when the plurality of reference codes RC1and RC2are generated by the second information Preset_OT indicating the plurality of pre-set service operators, the decision circuit434may determine that a user may use a service, when at least one of the plurality of reference codes RC1and RC2corresponds to the user code UC. In detail, the decision circuit434may determine whether the user who aims to use the service may use the service, based on the comparison result signal CRS. According to an example embodiment, when either one or both of the first reference code RC1and the second reference code RC2corresponds to the user code UC, the decision circuit434may determine that the user may use the service, and when neither the first reference code RC1nor the second reference code RC2corresponds to the user code UC, the decision circuit434may determine that the user may not use the service. The decision circuit434may generate a determination result signal RS_a and transmit the determination result signal RS to the processor120ofFIG. 1.

FIG. 10is a block diagram for describing an operation of a personalization module530of UE according to another example embodiment.

Referring toFIG. 10, the personalization module530may include a first code generator531, a second code generator532, a comparator533, and a decision circuit534. According to an example embodiment, the first code generator531may generate a plurality of reference codes in response to received first information Act_PT indicating a plurality of activated personalization categories. In detail, the first code generator531may extract a first data set DS_1bfrom personalization management information of a data storage540, by using the first information Act_PT indicating a first personalization category PERSO_1and a second personalization category PERSO_2activated by the processor120, and second information Preset_OT indicating a pre-set first service operator OP_1. For example, referring toFIG. 7A, the first data set DS_1bmay include the first operator value data VALUE_OP_1of the first service operator information SOI_1_1corresponding to the first personalization information PI_1and the second operator value data VALUE_OP_2of the second service operator information SOI_2_1corresponding to the second personalization information PI_2.

The first code generator531may generate a third reference code RC3by using the first operator value data VALUE_OP_1of the first service operator information SOI_1_1and a fourth reference code RC4by using the second operator value data VALUE_OP_2of the second service operator information SOI_2_1. The first code generator531may provide the third reference code RC3and the fourth reference code RC4to the comparator533.

According to an example embodiment, the second code generator532may generate a plurality of user codes in response to the received first information Act_PT indicating the plurality of activated personalization categories. In detail, the second code generator532may generate a first user code UC1corresponding to the first personalization category PERSO_1and a second user code UC2corresponding to the second personalization category PERSO_2by extracting a second data set DS_2bfrom information stored in the smart card450by using the first information Act_PT. The second code generator432may provide the first user code UC1and the second user code UC2to the comparator533.

The comparator533may compare the third reference code RC3with the first user code UC1and the fourth reference code RC4with the second user code UC2to determine whether the third reference code RC corresponds to the first user code UC1and the fourth reference code RC4corresponds to the second user code UC2, respectively. The comparator533may transmit a comparison result signal CRS_b to the decision unit534. The decision unit534may determine whether a user who aims to use a service may use the service, based on the comparison result signal CRS. According to an example embodiment, when the plurality of reference codes RC3and RC4are generated by using the first information Act_PT indicating the plurality of activated personalization categories, and the plurality of user codes, for example, the first and second user codes UC1and UC2, are generated, the decision circuit534may determine that the user may use the service when the reference codes RC3and RC4correspond to the first and second user codes UC1and UC2, respectively. In detail, when the third reference code RC3corresponds to the first user code UC1and the fourth reference code RC4corresponds to the second user code UC2, the decision circuit534may determine that the current user may use the service. When the third reference code RC3does not correspond to the first user code UC1or the fourth reference code RC4does not correspond to the second user code UC2, the decision circuit534may determine that the user may not use the service. The decision unit534may generate a determination result signal RS_b and transmit the determination result signal RS to the processor120ofFIG. 1.

FIG. 11is a flowchart of an operating method of UE for personalization, according to an example embodiment.

Referring toFIG. 11, the personalization information and the service operator information matched to the activated first personalization category and the first service operator providing the service, respectively, are detected from the personalization management information including the plurality of pieces of personalization information and the plurality of pieces of service operator information corresponding to each of the plurality of pieces of personalization information (S10). Thereafter, whether a user may use a service is determined by using a result of the detection and user information of the user who aims to use the service (S11).

FIG. 12is a flowchart of a method of detecting personalization information and service operator information of UE, according to an example embodiment.

Referring toFIG. 12, the personalization information including the personalization tag matched to the activated first personalization category is detected from the plurality of pieces of personalization information (S20). The service operator information including the operator tag matched to the first service operator is detected from the plurality of pieces of service operator information corresponding to the detected personalization information (S21).

FIG. 13is a flowchart of a method of determining whether a current user may use a service, via UE, according to an example embodiment.

Referring toFIG. 13, the reference code is generated by using the operator value data included in the detected service operator information (S30). The user code corresponding to the first personalization category is generated by using the user information of the user who aims to use the service (S31). The reference code and the user code are compared and whether the user may use the service may be determined based on a result of the comparison (S32).

FIG. 14is a flowchart of a method of detecting personalization information and service operator information via a personalization module, according to an example embodiment.

Referring toFIG. 14, the personalization operation is performed when the UE is booted (S40). According to an example embodiment, when the UE is turned on, or the smart card is inserted into the UE, the UE is booted or re-booted and may perform the personalization operation. In order for the UE to detect the personalization information and the service operator information corresponding to an activated personalization category Get_PERSO and a pre-set service operator Get_OP, respectively, from the personalization management information, first, the UE sets x and y as 1 (S41). To detect the personalization information matched to the activated personalization category Get_PERSO from among a plurality of pieces of personalization information, the UE determines whether a value of x is N+1 (S42_1). N may indicate the number of pieces of personalization information. When the value of x is not N+1 (S42_1, N), the activated personalization category Get_PERSO and an xthpersonalization tag TAG_PERSO_x included in the xthpersonalization information are compared (S42_2). When the activated personalization category Get_PERSO and the xthpersonalization tag TAG_PERSO_x are not matched (S42_3, NO), the next personalization information of the xthpersonalization information is searched for (S42_5) by referring to xthlength data LENGTH_PERSO_x included in the xthpersonalization information (S42_4.) Thereafter, 1 is added to the value of x (S42_6). Then, the operation of detecting the xthpersonalization information including the xthpersonalization tag TAG_PERSO_x matched to the activated personalization category Get_PERSO is repeated (S42_1through S42_6) until the value of x becomes N+1.

When the xthpersonalization information including the xthpersonalization tag TAG_PERSO_x matched to the activated personalization category Get_PERSO is detected (S42_3, YES), the UE may determine whether a value of y is M+1 (S43_1) in order to detect the service operator information matched to the pre-set service operator Get_OP from among a plurality of pieces of service operator information corresponding to the xthpersonalization information. M may indicate the number of pieces of service operator information corresponding to the xthpersonalization information. When the value of y is not M+1 (S43_1, N), the pre-set service operator Get_OP and a ythoperator tag TAG_OP_y included in the ythservice operator information are compared (S43_2). When the pre-set service operator Get_OP and the ythoperator tag TAG_OP_y included in the ythservice operator information are not matched (S43_3, NO), the next personalization information of the ythservice operator information is searched for (S43_5) by referring to ythlength data LENGTH_OP_y included in the ythservice operator information (S43_4). Thereafter, 1 is added to the value of y (S43_6). Then, the operation of detecting the ythservice operator information including the ythoperator tag TAG_OP_y matched to the pre-set service operator Get_OP is repeated (S43_1through S43_6) until the value of y becomes M+1.

When the ythservice operator information including the ythoperator tag TAG_OP_y matched to the pre-set service operator Get_OP is detected (S43_3, YES), ythoperator value data VALUE_OP_y included in the ythservice operator information is extracted (S43_7). Also, according to an example embodiment, when the xthpersonalization information including the xthpersonalization tag TAG_PERSO_x matched to the activated personalization category Get_PERSO is not detected until the value of x becomes N+1 (S42_1, Y), or the ythservice operator information including the ythoperator tag TAG_OP_y matched to the pre-set service operator Get_OP is not detected until the value of y becomes M+1 (S43_1, Y), the user may determine to use the service by using the UE. According to another example embodiment, the UE may update the personalization management information by receiving new personalization management information from the outside and storing the new personalization management information.

FIG. 15is a block diagram of UE1000according to an example embodiment.

As illustrated inFIG. 15, the UE1000may include an application specific integrated circuit (ASIC)1100, an application specific instruction set processor (ASIP)1300, a memory1500, a main processor1700, and a main memory1900. At least two of the ASIC1100, the ASIP1300, and the main processor1700may communicate with each other. Also, at least two of the ASIC1100, the ASIP1300, the memory1500, the main processor1700, and the main memory1900may be installed in one chip.

The ASIC1100is an integrated circuit customized for particular purposes. For example, the ASIC1100may include a radio frequency integrated circuit (RFIC), a modulator, a demodulator, etc. The ASIP1300may support an exclusive instruction set for particular applications, and execute instructions included in the instruction set. The memory1500may communicate with the ASIP1300and may be a non-transitory storage medium configured to store a plurality of instructions executed by the ASIP1300. For example, the memory1500may include random types of memory which may be accessed by the ASIP1300, such as random access memory (RAM), read only memory (ROM), a tape, a magnetic disk, an optical disk, a volatile memory, a non-volatile memory, and a combination thereof.

The main processor1700may control the UE1000by executing the plurality of instructions. For example, the main processor1700may control the ASIC1100and the ASIP1300, and may process data received via a wireless communication network or a user input received by the UE1000. The main memory1900may communicate with the main processor1700, and may be a non-transitory storage medium configured to store a plurality of instructions executed by the main processor1900. For example, the main memory1900may include random types of memory which may be accessed by the main processor1700, such as RAM, ROM, a tape, a magnetic disk, an optical disk, a volatile memory, a non-volatile memory, and a combination thereof.

The components of the UE according to the example embodiments or the operations included in the operation of personalization via the UE may be included in at least one of the components included in the UE1000ofFIG. 15. For example, the personalization module130ofFIG. 1may be realized as the plurality of instructions stored in the memory1500, and the operation of the personalization module130may be performed as the ASIP1300executes the plurality of instructions stored in the memory1500. As another example, the personalization module130ofFIG. 1may be realized as a hardware block and included in the ASIC1100. As another example, the personalization module130ofFIG. 1may be realized as the plurality of instructions stored in the main memory1900, and the operation of the personalization module130may be performed as the main processor1700executes the plurality of instructions stored in the main memory1900.

FIG. 16is a block diagram of an example in which a communication method according to example embodiments is applied to internet of things (IoT).

The IoT may refer to a network between things using wired/wireless communication. Also, an IoT device2000may include devices having an accessible wired or wireless interface, and transmitting or receiving data to and from at least another device by communicating with the other device via the wired/wireless interface. For example, the IoT device2000may correspond to various types of devices which may perform communication, such as a refrigerator, an air-conditioner, a telephone, an automobile, etc.

The example embodiments of the present inventive concept described above may be applied to the IoT. For example, the base station described above may be applied to an access point (AP), a gateway, a server, etc. in the IoT. Also, the terminals described above may correspond to the IoT device2000. Any one IoT device may communicate with another IoT device via the access point, the gateway, etc., or the IoT devices may perform device-to-device (D2D) communication according to the embodiments described above.

Referring toFIG. 16, the IoT device2000may include an IoT device application2100and a communication module2200. The communication module2200may include firmware2210, a radio baseband chip set2220, a security module2230, etc.

The IoT device application2100may control the communication module2200as a software component, and may be executed by a central processing unit (CPU) (not shown) in the IoT device2000. The communication module2200may refer to a wireless communication component which may be connected to or exchange data with LAN, WLAN such as Wi-fi, wireless universal serial bus (USB), ZigBee, or a mobile communication network.

The firmware2210may provide the IoT device application2100and an application programming interface (API), and may control the radio baseband chipset2220according to control of the IoT device application2100. The radio baseband chipset2220may provide connectivity to the wireless communication network. The security module2230may include a processor2231and a security element2232. The security module2232may authenticate the IoT device2000to be connected to the wireless communication network, and authenticate the IoT device2000for an access to services of the wireless network.

The IoT device2000may perform the personalization operation according to the above-described example embodiments according to the present inventive concept. Via the personalization operation, the IoT device2000may determine whether a current user may use a communication service with another IoT device. The security element2232may include the personalization module130and/or the data storage140configured to store the personalization management information, described with reference toFIG. 1. The IoT device2000may extract the activated personalization category and the information matched to the service operator from the personalization management information and perform the personalization operation based on the extracted activated personalization category and information matched to the service operator.