Device conversion method and apparatus for wireless communication system

Abstract

The present disclosure relates to a communication technology and a system thereof for integrating IoT technology with a 5G communication system supporting a high data transmission rate exceeding that of a 4G system. The present disclosure can be applied to smart services based on 5G communication technology and IoT-related technologies (such as smart homes, buildings, cities, cars or connected cars, health care, digital education, retail business, safety and security-related services, etc.). The present invention proposes a method and apparatus for realizing inter-device profile movement using only two devices without separately performing identity authentication or ID authentication verification. According to an embodiment of the present invention, a method may be provided, comprising the steps of: receiving an input for moving a first profile installed on a first terminal; deleting a first profile of a first eUI CC; generating digital signature data of a first eUI CC for data including first profile information; and displaying data including the first profile information and the corresponding digital signature data as a QR code on a screen of the first terminal.

Description

Technical Field

[0001] The present disclosure relates to a wireless communication system, and more particularly, to a method and apparatus for reinstalling access information in a device in the wireless system to access the communication system. Background Art

[0002] In order to meet the increased demand for wireless data services since the deployment of 4G communication systems, efforts have been made to develop an improved 5G or quasi-5G communication system. Therefore, 5G or quasi-5G communication systems are also referred to as "super 4G networks" or "post-LTE systems". 5G communication systems are considered to be implemented in higher frequency (millimeter wave) bands (e.g., 60GHz bands) to achieve higher data rates. In order to reduce the propagation loss of radio waves and increase the transmission distance, beamforming, large-scale multiple input multiple output (MIMO), full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and large antenna technology are discussed in 5G communication systems. In addition, in 5G communication systems, development of system network improvements is being carried out based on advanced small cells, cloud radio access networks (RAN), ultra-dense networks, device-to-device (D2D) communications, wireless backhaul, mobile networks, collaborative communications, coordinated multipoint (CoMP), receiving end interference elimination, etc. In 5G systems, hybrid FSK with QAM modulation (FQAM) and sliding window superposition coding (SWSC) have been developed as advanced coded modulation (ACM), and filter bank multi-carrier (FBMC), non-orthogonal multiple access (NOMA) and sparse code multiple access (SCMA) as advanced access technologies.

[0003] The Internet, which is a human-centered connectivity network in which humans generate and consume information, has now evolved into the Internet of Things (IoT), in which distributed entities (such as things) exchange and process information without human intervention. The Internet of Everything (IoE) has emerged, which is a combination of IoT technology and big data processing technology through connection with a cloud server. Since IoT implementation requires technical elements such as "sensing technology", "wired / wireless communication and network infrastructure", "service interface technology" and "security technology", sensor networks, machine-to-machine (M2M) communication, machine type communication (MTC), etc. have recently been studied. Such an IoT environment can provide smart Internet technology services that create new value for human life by collecting and analyzing data generated between connected things. IoT can be applied to a variety of fields, including smart homes, smart buildings, smart cities, smart cars or connected cars, smart grids, health care, smart appliances, and advanced medical services through the integration and combination between existing information technology (IT) and various industrial applications.

[0004] Therefore, various attempts have been made to apply 5G communication systems to IoT networks. For example, technologies such as sensor networks, machine type communications (MTC), and machine-to-machine (M2M) communications can be implemented through beamforming, MIMO, and array antennas. Cloud radio access networks (RANs) as an application of the above-mentioned big data processing technologies can also be considered as an example of the fusion of 5G technology and IoT technology.

[0005] A universal integrated circuit card (UICC) is a smart card that is inserted into and used in a mobile communication terminal, etc., and is also referred to as a UICC card. An access control module for accessing a network of a mobile communication service provider may be included in the UICC. Examples of access control modules include a universal subscriber identity module (USIM), a subscriber identity module (SIM), and an IP multimedia service identity module (ISIM). A UICC including a USIM is generally referred to as a USIM card. Similarly, a UICC including a SIM is generally referred to as a SIM card. In the disclosure described below, a SIM card will be used to include a UICC card, a USIM card, a UICC including an ISIM, etc. in a general sense. That is, although a SIM card is mentioned, its technical application can be equally applied to a USIM card, an ISIM card, or a general UICC card.

[0006] The SIM card may store personal information about a mobile communication subscriber and enable the use of secure mobile communications via subscriber authentication and service security key generation when accessing a mobile communication network.

[0007] At the request of the operator when manufacturing the card, the SIM card is usually manufactured as a dedicated card for a specific mobile communication operator and released, in which the operator's authentication information for network access, such as the global subscriber identity module (USIM) application, the international mobile subscriber identity (IMSI), the K value and the OPc value, are loaded in advance. The mobile communication operator receives the manufactured SIM card and provides the SIM card to the subscriber. If necessary, it is possible to manage (e.g., install, modify or delete) the application in the UICC card using over-the-air (OTA) technology, etc. The subscriber can insert the UICC card into the mobile communication terminal to use the network and application services of the mobile communication operator. When the existing terminal is replaced with a new terminal, the subscriber can insert the UICC card into the new terminal, thereby using the same authentication information, mobile phone number and personal contacts stored in the UICC card in the new terminal.

[0008] However, SIM cards can cause inconvenience to mobile communication terminal users in receiving services from different mobile communication service providers. Mobile communication terminal users inconvenience physically need to obtain SIM cards in order to receive services from mobile communication service providers. For example, when traveling abroad, it is troublesome to obtain a local SIM card in order to receive local mobile communication services. Roaming services may solve this inconvenience to a certain extent, but they incur expensive fees and cannot be received if there is no contract between communication service providers.

[0009] This inconvenience can be largely solved by remotely downloading the SIM and installing it to the UICC card. That is, the user can download the SIM of the mobile communication service to be used to the UICC card at the desired time. The UICC card can download and install multiple SIMs, and only one SIM in the multiple SIMs can be selected and used. The UICC card may or may not be fixed to the terminal.

[0010] The physical shape and logical functions of the UICC card are defined by a standardization organization called the European Telecommunications Standards Institute (ETSI), and thus the UICC card maintains international compatibility. From the perspective of the form factor that defines the physical phenomenon, the size of the SIM is generally reduced from the most widely used mini SIM and small SIM to the recent nano SIM. Although the small SIM contributes to the miniaturization of mobile communication terminals, it is expected that the UICC card smaller in size than the recently established nano SIM is difficult to standardize due to user concerns about loss. In addition, since a space for installing a detachable slot is required in the terminal in view of the characteristics of the detachable UICC card, further miniaturization is expected to be difficult.

[0011] To solve this problem, it is necessary to replace the UICC by embedding a security module that performs functions similar to the UICC in the terminal when manufacturing the mobile communication terminal. In response to this need, an embedded universal integrated circuit card (eUICC) structure is proposed, which is a non-detachable UICC.

[0012] A UICC fixed to a terminal for use is referred to as an embedded UICC (eUICC). Typically, an eUICC refers to a UICC card that is fixed to a terminal for use and from which a SIM can be downloaded and selected remotely from a profile server. In the present disclosure, UICC cards that can remotely download and select a SIM are collectively referred to as eUICCs. That is, among UICC cards that can remotely download and select a SIM, UICC cards that are fixed to a terminal and UICC cards that are not fixed to a terminal are collectively referred to as eUICCs. In addition, the SIM information to be downloaded will be collectively referred to as the term "eUICC profile".

[0013] When changing terminals, subscribers can transfer the SIM card from the old terminal to the new terminal, thereby using the authentication information stored in the UICC card to access the same mobile communication network. However, in a terminal with an eUICC installed, the downloaded SIM card is decrypted and installed only in the eUICC and cannot be extracted from the outside again after installation, causing inconvenience when changing terminals.

[0014] Conventionally, when a SIM card is lost, a mobile operator provides a process for reissuing the SIM card through a subscriber identity or ID authentication process. This process can be applied to the eUICC when the terminal is replaced. However, in order to prevent misuse, such as illegal intrusion / theft of phone numbers, subscribers usually need to go to an offline store to process the identity or ID authentication process, or need to go through a strict online ID authentication process. In addition, there are few official methods for the ID authentication process, making it difficult to handle the process. Summary of the invention

[0015] Technical issues

[0016] A technical aspect of the present disclosure is to provide a method and apparatus for transferring a configuration file installed in a first terminal to a second terminal.

[0017] A technical aspect of the present disclosure is to provide a download method that does not require separate ID authentication when a new terminal that is changed through terminal replacement in a communication system downloads a new eUICC profile corresponding to a profile stored in an eUICC of an existing terminal online and installs the new eUICC to connect to a communication service used by the existing terminal.

[0018] Solution to the problem

[0019] In view of the foregoing, one embodiment of the present disclosure may provide a method performed by a first terminal, the method comprising: receiving input to transfer a configuration file installed in the first terminal; deleting the configuration file from a first universal integrated circuit card (UICC) of the first terminal; generating data including deletion information about the configuration file; and outputting the data as information that can be obtained by a second terminal, wherein the data can be used for the second terminal to obtain the configuration file.

[0020] In view of the foregoing, an embodiment of the present disclosure may provide a method performed by a second terminal, the method comprising: obtaining data including information about a profile deleted from a first universal integrated circuit card (UICC) of a first terminal; transmitting a first message including identification information about the profile and deletion information about the profile to a profile server based on the data; receiving metadata about the profile based on the identification information about the profile and the deletion information about the profile; transmitting a second message including a download request for the profile to the profile server based on the metadata; and downloading the profile from the profile server.

[0021] In view of the foregoing, an embodiment of the present disclosure may provide a method performed by a profile server, the method comprising: receiving a first message from a second terminal, the first message comprising identification information about a profile deleted from the first terminal and deletion information about the profile; generating metadata about the profile based on the identification information about the profile and the deletion information about the profile; transmitting the metadata to the second terminal; receiving a second message from the second terminal, the second message comprising a download request for the profile; and transmitting the profile to the second terminal.

[0022] In view of the foregoing, one embodiment of the present disclosure may provide a first terminal, comprising: a transceiver; a first universal integrated circuit card (UICC); and a controller, the controller being configured to perform control to: receive input to transfer a configuration file installed in the first terminal; delete the configuration file from the first UICC; generate data including deletion information about the configuration file; and output the data as information that can be obtained by a second terminal, wherein the data is used for the second terminal to obtain the configuration file.

[0023] In view of the foregoing, one embodiment of the present disclosure may provide a second terminal, the second terminal including: a transceiver; a second universal integrated circuit card (UICC); and a controller, the controller being configured to perform control to: obtain data including information about a profile deleted from a first UICC of a first terminal; transmit a first message including identification information about the profile and deletion information about the profile to a profile server based on the data; receive metadata about the profile based on the identification information about the profile and the deletion information about the profile; transmit a second message including a download request for the profile to the profile server based on the metadata; and download the profile from the profile server.

[0024] In view of the foregoing, an embodiment of the present disclosure may provide a configuration file server, comprising: a transceiver; and a controller, the controller being configured to perform control to: receive a first message from a second terminal, the first message comprising identification information about a configuration file deleted from the first terminal and deletion information about the configuration file; generate metadata about the configuration file based on the identification information about the configuration file and the deletion information about the configuration file; transmit the metadata to the second terminal; receive a second message from the second terminal, the second message comprising a download request for the configuration file; and transmit the configuration file to the second terminal.

[0025] In view of the foregoing, a method for a first terminal according to one embodiment of the present disclosure may include: receiving an input to transfer a first profile installed in the first terminal; deleting the first profile from a first eUICC; generating digital signature data of the first eUICC for data including first profile information; and displaying the data including the first profile information and the digital signature data as a QR code on a screen of the first terminal.

[0026] In view of the foregoing, a method for a second terminal according to one embodiment of the present disclosure may include: scanning a QR code displayed on a screen of a first terminal; transmitting first profile information included in the QR code, digital signature data of a first eUICC, and digital signature data of a second eUICC to a profile server; and receiving and installing the profile from the profile server.

[0027] In view of the foregoing, a method for a profile server according to an embodiment of the present disclosure may include: receiving first profile information, digital signature data of a first eUICC, and digital signature data of a second eUICC from a second terminal; verifying the digital signature data of the second eUICC; verifying the digital signature data of the first eUICC; and transmitting the first profile to the second terminal.

[0028] The technical subject matter pursued in the present disclosure may not be limited to the above-mentioned technical subject matter, and other technical subject matter not mentioned may be clearly understood by those skilled in the art to which the present disclosure relates through the following description.

[0029] Advantageous Effects of the Invention

[0030] According to various embodiments of the present disclosure, it is possible to provide a method and apparatus for transferring a configuration file installed in a first terminal to a second terminal.

[0031] According to various embodiments of the present disclosure, when a terminal in which an eUICC is installed is replaced in a communication system, it is possible to conveniently transfer a SIM between devices by only manipulating an existing terminal and a new terminal without additional identification or ID confirmation. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] Figure 1a An example of a configuration of a communication system to which one embodiment of the present disclosure is applied is shown;

[0033] Figure 1b An additional example of the configuration of a communication system to which one embodiment of the present disclosure is applied is shown;

[0034] Figure 1c An additional example of the configuration of a communication system to which an embodiment of the present disclosure is applied is shown;

[0035] Figure 1d An example of device UI operation in a process of transferring access information from device 1 to device 2 according to an embodiment of the present disclosure is shown;

[0036] Figure 2 shows the internal operation of the device 1 according to one embodiment of the present disclosure;

[0037] Figure 3 2000 and the operation of the configuration file server 6000 according to an embodiment of the present disclosure;

[0038] Figure 4 shows the internal operation of the device 1 according to one embodiment of the present disclosure;

[0039] Figure 6 The process of transferring access information from device 1 to device 2 according to one embodiment of the present disclosure is shown;

[0040] Figure 7 1 shows the operation of the device 1 before transferring the configuration file according to one embodiment of the present disclosure;

[0041] Figure 8 shows the internal operation of the device 1 according to one embodiment of the present disclosure;

[0042] Fig. 9 The process of transferring access information from device 1 to device 2 according to one embodiment of the present disclosure is shown;

[0043] Fig.10 1 shows the operation of the device 1 before transferring the configuration file according to one embodiment of the present disclosure;

[0044] Fig.11The operation of the apparatus 1 according to one embodiment of the present disclosure is shown;

[0045] Fig.12 The operation of a configuration file server according to one embodiment of the present disclosure is shown;

[0046] Fig.13 The process of transferring a configuration file from device 1 to device 2 according to one embodiment of the present disclosure is shown;

[0047] Fig.14 The process of transferring a configuration file according to an embodiment of the present disclosure is shown;

[0048] Fig.15 shows a configuration file transfer according to one embodiment of the present disclosure;

[0049] Fig.16 shows a message displayed to a user when transferring a configuration file according to one embodiment of the present disclosure;

[0050] Fig.17 A configuration file transfer process according to an embodiment of the present disclosure is shown;

[0051] Fig.18 shows the structure of a terminal according to an embodiment of the present disclosure; and

[0052] Fig.19 The structure of a configuration file server according to an embodiment of the present disclosure is shown. DETAILED DESCRIPTION

[0053] Hereinafter, exemplary embodiments of the present disclosure will be described in detail with reference to the accompanying drawings. It should be noted that in the accompanying drawings, identical or similar elements are indicated by identical or similar reference numerals as much as possible. In addition, detailed descriptions of known functions or configurations that may make the subject matter of the present disclosure unclear will be omitted.

[0054] In the process of describing the embodiments of the present disclosure, descriptions related to technical contents well-known in the art and not directly related to the present disclosure will be omitted. Such unnecessary descriptions are omitted to prevent the main idea of ​​the present disclosure from being obscured and to convey the main idea more clearly.

[0055] For the same reason, in the accompanying drawings, some elements may be exaggerated, omitted or schematically shown. In addition, the size of each element does not fully reflect the actual size. In the accompanying drawings, the same or corresponding elements have the same reference numerals.

[0056] By referring to the embodiments described in detail below in conjunction with the accompanying drawings, the advantages and features of the present disclosure and the methods for achieving them will become apparent. However, the present disclosure is not limited to the embodiments set forth below, but can be implemented in various different forms. The following embodiments are provided only to fully disclose the present disclosure and inform those skilled in the art of the scope of the present disclosure, and the present disclosure is limited only by the scope of the attached claims. Throughout the entire specification, the same or similar reference numerals represent the same or similar elements.

[0057] Here, it will be understood that each frame of the flowchart diagram and the frame combination in the flowchart diagram can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device create a device for implementing the functions specified in one or more flowchart frames. These computer program instructions can also be stored in a computer-available or computer-readable memory that can instruct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-available or computer-readable memory produce an article including an instruction component for performing the functions specified in one or more flowchart frames. Computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are performed on a computer or other programmable device, thereby generating a computer-implemented process, so that the instructions executed on a computer or other programmable device provide steps for implementing the functions specified in one or more flowchart frames.

[0058] In addition, each frame of the flowchart diagram can represent a module, a code segment or a code portion, which includes one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions mentioned in the frame may not occur in order. For example, the two frames shown in succession can in fact be performed substantially simultaneously, or each frame can sometimes be performed in reverse order, depending on the functions involved.

[0059] As used herein, "unit" refers to a software element or a hardware element that performs a predetermined function, such as a field programmable gate array (FPGA) or an application specific integrated circuit (ASIC). However, "unit" does not always have a meaning that is limited to software or hardware. "Unit" can be constructed to be stored in an addressable storage medium or to perform one or more processors. Therefore, "unit" includes, for example, software elements, object-oriented software elements, class elements or task elements, processes, functions, attributes, programs, subroutines, program code fragments, drivers, firmware, microcodes, circuits, data, databases, data structures, tables, arrays and parameters. The element and function provided by "unit" can be combined into a smaller number of elements or "units", or divided into a larger number of elements or "units". In addition, element and "unit" can be implemented as one or more CPUs that are reproduced in a device or a secure multimedia card.

[0060] First, the terms used in this article are defined.

[0061] In this specification, UICC is a smart card inserted into a mobile communication terminal for use and refers to a chip that stores personal information about a mobile communication subscriber (such as network access authentication information, phone book, or SMS), and performs subscriber authentication and service security key generation to enable secure use of mobile communication when accessing a mobile communication network (such as GSM, WCDMA, or LTE). Depending on the type of mobile communication network to which the subscriber is connected, communication applications such as a subscriber identity module (SIM), a universal SIM (USIM), or an IP multimedia SIM (ISIM) can be installed in the UICC, and the UICC can provide advanced security functions in order to install various applications such as an electronic wallet, a ticketing application, or an electronic passport.

[0062] In this specification, an embedded UICC (eUICC) is a chip-type security module embedded in a terminal, rather than a detachable type that can be inserted into and removed from a terminal. The eUICC can download and install configuration files using over-the-air (OTA) technology. The eUICC can be referred to as a UICC that is capable of downloading and installing configuration files.

[0063] In this specification, the method of downloading and installing a configuration file in an eUICC using OTA technology can also be applied to a detachable UICC that can be inserted into and removed from a terminal. That is, the embodiments of the present disclosure can be applied to a UICC that can download and install a configuration file using OTA technology.

[0064] In this specification, the term “UICC” may be used interchangeably with the term “SIM”, and the term “eUICC” may be used interchangeably with the term “eSIM”.

[0065] In this specification, a profile may refer to a packaged software form of an application, a file system, and an authentication key value stored in a UICC. The profile may be referred to as access information.

[0066] In this specification, a USIM profile may have the same meaning as a profile, or may refer to a packaged software form included in a USIM application in a profile.

[0067] In this specification, the profile server may include functions of generating a profile, encrypting the generated profile, generating a profile remote management instruction, or encrypting the generated profile remote management instruction, and may be expressed as subscription manager data preparation (SM-DP), subscription manager data preparation plus (SM-DP+), or subscription manager secure routing (SM-SR).

[0068] The term "terminal" or "device" used herein may be referred to as a mobile station (MS), user equipment (UE), user terminal (UT), wireless terminal, access terminal (AT), terminal, subscriber unit, subscriber station (SS), wireless device, wireless communication device, wireless transmit / receive unit (WTRU), mobile node, mobile device or other terms. Various examples of terminals may include cellular phones, smart phones with wireless communication functions, personal digital assistants (PDAs) with wireless communication functions, wireless modems, portable computers with wireless communication functions, photographic devices (such as digital cameras) with wireless communication functions, gaming devices with wireless communication functions, music storage and playback devices with wireless communication functions, Internet appliances capable of wireless Internet access and browsing, and portable units or terminals that combine these functions. In addition, terminals may include machine-to-machine (M2M) terminals and machine type (MTC) communication terminals / devices, but are not limited thereto. In this specification, a terminal may be referred to as an electronic device or simply a device.

[0069] In this specification, a terminal or a device may include software or an application installed in the terminal or the device for controlling a UICC or an eUICC. The software or the application may be referred to as, for example, a Local Profile Assistant (LPA).

[0070] In the present specification, an eUICC identifier (eUICC ID) may be a unique identifier of an eUICC embedded in a terminal and may be referred to as an EID.

[0071] In this specification, an application protocol data unit (APDU) may be a message for a controller in a terminal or a device to interwork with an eUICC.

[0072] In this specification, a profile package may be used interchangeably with a profile, or may be used as a term for a data object indicating a specific profile, and may be referred to as a profile TLV or a profile package TLV. A profile package encrypted using encryption parameters may be referred to as a protected profile package (PPP) or a protected profile package TLV (PPPTLV). A profile package encrypted using encryption parameters that can only be decrypted by a specific eUICC may be referred to as a bound profile package (BPP) or a bound profile package TLV (BPPTLV). A profile package TLV may be a data set representing information forming a profile in a tag-length-value (TLV) format.

[0073] In this specification, AKA may mean Authentication and Key Agreement, and may refer to an authentication algorithm for accessing 3GPP and 3GPP2 networks.

[0074] In this specification, K is an encryption key value for the AKA authentication algorithm stored in the eUICC.

[0075] In this specification, OPc is a parameter value for the AKA authentication algorithm that can be stored in the eUICC.

[0076] In this specification, NAA is a network access application and may be an application program for accessing a network stored in a UICC, such as a USIM or an ISIM. NAA may be a network access module.

[0077] When, in the process of describing the present disclosure, a detailed description about a related known function or configuration is determined to make the gist of the present disclosure unclear, the detailed description will be omitted herein.

[0078] Hereinafter, the proposed embodiments will be described with reference to the accompanying drawings.

[0079] In various embodiments of the present disclosure, the first device may be used interchangeably with the first terminal or device 1 , and the second device may be used interchangeably with the second terminal or device 2 .

[0080] Figure 1a An example of a configuration of a communication system to which one embodiment of the present disclosure is applied is shown.

[0081] refer to Figure 1a , a communication system to which an embodiment of the present disclosure is applied includes a first device 1a-10, a configuration file providing server 1a-30, and a second device 1a-20. The first device 1a-10 may be defined as a first terminal, and the second device 1a-20 may be defined as a second terminal.

[0082] The first device 1a-10 may download and install a configuration file from the configuration file server 1a-30, may delete the installed configuration file to transfer the configuration file, and may provide information about the deleted configuration file and verification information to verify the deletion of the configuration file to the second device 1a-20.

[0083] The second device 1a-20 can receive information about the configuration file and verification information about deletion of the configuration file from the first device 1a-10, can transmit a request message including the information and the signature of the second device to the configuration file server, and can receive and install the configuration file from the configuration file server 1a-30.

[0084] The profile providing server 1a-30 verifies the deletion of the profile that has been installed in the first device 1a-10 by a request from the second device 1a-20, and transmits the profile to the second device so that the profile can be installed. In addition, when a profile deletion request event requesting the deletion of a profile is received through an input unit (user interface unit) of software or an application (e.g., a local profile assistant (LPA)) installed in a terminal or device for controlling a UICC or eUICC, according to an embodiment of the present disclosure, each of the first terminal and the second terminal deletes the profile and transmits a message indicating that the profile has been deleted to the profile providing server 1a-30. Therefore, the profile providing server can manage the profile for providing a communication service previously generated in the first terminal so as to be reused in the second terminal.

[0085] Figure 1b An additional example of the configuration of a communication system to which one embodiment of the present disclosure is applied is shown.

[0086] refer to Figure 1b The communication system using the embodiment of the present disclosure includes: Figure 1a The first device 1b-10, the configuration file providing server 1b-30 and the second device 1b-20 in the embodiment further include a communication service provider server 1b-40 interworking with the configuration file server.

[0087] Figure 1b The operation of the first device 1b-10 and the second device 1b-20 is Figure 1a The configuration file providing server 1b-30 is also the same as that of Figure 1a The same operation is performed so that the deletion of the configuration file already installed in the first device 1b-10 is verified by a request from the second device 1b-20, and the configuration file is transmitted to the second device 1b-20 so that the configuration file can be installed. Figure 1bIn the configuration, the profile server 1b-30 may additionally inquire of the communication service provider server 1b-40 whether to reinstall the deleted profile by requesting, may receive a response from the communication service provider server 1b-40, and may then transmit the profile to the second device 1b-20 to enable installation of the profile.

[0088] In the following embodiments, reference will be made to Figure 1a Configuration or Figure 1b However, it should be noted that although reference Figure 1a , but the description can also be applied to Figure 1b The configuration operation.

[0089] Figure 1c An additional example of the configuration of a communication system to which one embodiment of the present disclosure is applied is shown.

[0090] refer to Figure 1c The communication system using the embodiment of the present disclosure includes: Figure 1a The first device 1c-10, the configuration file providing server 1c-30 and the second device 1c-20, and further includes a checking server 1c-40 that interacts with the first device 1c-10.

[0091] Figure 1c The configuration file server 1c-30 and the second device 1c-20 operate with Figure 1a The operation of the first device 1c-10 is also the same as that of Figure 1a The first device 1c-10 may download and install a configuration file from the configuration file server 1c-30, may delete the installed configuration file to transfer the configuration file, and may provide information about the deleted configuration file and verification information to verify the deletion of the configuration file to the second device 1c-20.

[0092] Here, in Figure 1c In the configuration, the device 1 1c-10 performs a process of asking a separate check server 1c-40 whether the configuration file can be transferred before deleting the installed configuration file to transfer the configuration file, and can delete the configuration file according to the query result. The check server 1c-40 may be the configuration file server 1c-30.

[0093] In the following embodiments, reference will be made to Figure 1a Configuration, Figure 1b Configuration or Figure 1c However, it should be noted that although reference Figure 1a , but the description can also be applied to Figure 1b Configuration or Figure 1c The configuration operation.

[0094] Figure 1d An example of device UI operation in a process of transferring access information from device 1 to device 2 according to an embodiment of the present disclosure is shown.

[0095] refer to Figure 1d , device 1 1000 may display a menu showing configuration files to the user (1002). When the user selects menu 1002a, device 1 1000 may display a list of configuration files (1004). When the user selects a configuration file 1004a on the list of configuration files, device 1 1000 may display information about configuration file 1 and local management functions for the configuration file (1006). The functions may include configuration file activation, configuration file deactivation, configuration file deletion, and configuration file transfer to a different device 1006. When the user selects transfer to a different device 1006a (input is received to transfer the configuration file), device 1 1000 may ask the user whether the user really wants to transfer and may provide a confirmation menu 1008a (1008). When the user selects the confirmation menu 1008a, the device 1 1000 may delete the profile, and then may display data including at least one of the following in the format of a QR code: a profile server address, processing sequence information, ICCID information about the deleted profile, an indicator indicating that the profile has been deleted, or signature value information about the eUICC including such information, and may also display a cancel / restore menu 1010b and a later confirmation menu 1010c. The information included in the QR code may be an activation code, which may be similarly applied to the QR code mentioned in the following embodiments of the present disclosure. The method for displaying data is not limited to the format of the QR code, and the data may be displayed as barcode information, other encrypted information, etc. In the following, although the description is made with reference to an example using a QR code, the embodiments of the present disclosure are not limited thereto.

[0096] When the user selects the cancel / restore menu 1010b, the device 1 1000 may download and install the configuration file from the configuration file server again using the information 1010a displayed on the QR code or the internal storage information corresponding thereto. When the user selects the confirm later menu 1010c, the device 1 1000 may internally store the information 1010a displayed on the QR code or the internal storage information corresponding thereto, instead of deleting the information, and may then provide information to determine whether to restart the transfer of the configuration file or restore the configuration file back to the device 1 1000 using the information.

[0097] Subsequently, the configuration file installation process of device 2 2000 is as follows. First, device 2 2000 provides a SIM configuration file download menu 2002a in a QR code (2002). The QR code can be replaced with barcode information, other encrypted information, etc. When the user selects menu 2002a and device 2 2000 starts scanning the QR code, device 2 2000 can be used to scan the QR code 1010a of device 1 1000. Subsequently, device 2 2000 can access the configuration file server address included in the QR code, can transmit a request message including the configuration file server address, processing sequence information, ICCID information about the deleted configuration file, an indicator indicating that the configuration file has been deleted, and signature value information about the eUICC including these data, can receive the configuration file, and can install the configuration file (2006). After the configuration file is installed, device 2 2000 can display the installed configuration file (2008).

[0098] Before or after the device 1 1000 displays the profile transfer menu 1006a, the device 1 1000 may identify whether the profile transfer of the profile is possible and may display appropriate guidance information. For example, the device 1 1000 may identify whether the profile transfer is possible before displaying the menu, and then may display the transfer menu 1006a only when the profile transfer is possible. Alternatively, even if the profile transfer is impossible or limited, the device 1 1000 may display the transfer menu, and then may display a guidance message indicating that the profile transfer is impossible or limited when the user selects the transfer menu. In addition, in operation 1010, the device 1 1000 may obtain information about the device 2 2000 before deleting the profile, may inquire the profile server whether the profile transfer is possible to the device 2 2000, and then may delete the profile and display the QR code 1010a when the transfer is possible according to the query result. Although the foregoing embodiments are not limited to the scope of the description, some embodiments thereof will be described with reference to the attached drawings and embodiments.

[0099] Figure 2 The internal operation of the device 1 according to one embodiment of the present disclosure is shown.

[0100] refer to Figure 2, the device 1 1000 is a device in which the eUICC 4000 is installed, and includes a controller 3000 capable of exchanging eUICC control messages with the eUICC 4000. The controller 3000 is collectively referred to as hardware (HW) and software (SW), which controls the eUICC 4000 in conjunction with the eUICC 4000 (except the eUI CC 4000 in the device 1 1000), and may be hardware such as an application processor (AP), a central processing unit (CP), or a baseband, or may be software such as an LPA. The controller 3000 may include at least one processor, and may control the overall operation of the device 1 1000. In an embodiment of the present disclosure, the device 1 1000 may further include a transceiver to communicate with a server, a base station, or other terminals. The configuration of the device 1 1000 may be applied to other embodiments of the present disclosure.

[0101] In addition to the device 1, the configuration of the device 1 1000 can also be applied to the configuration of the device 2. That is, the device 2 can also include an eUICC and a controller, and can further include a transceiver to communicate with a server, a base station, and other terminals. The configuration of the device 2 can be applied to other embodiments of the present disclosure.

[0102] because Figure 2 The process of operation 3001, operation 3001a and operation 3002 is the same as Figure 1d The processes of operation 1002, operation 1004, operation 1006 and operation 1008 are equivalent or similar, so the detailed description thereof is omitted and Figure 1d The description mentioned there.

[0103] Subsequently, the device 1 1000 may transmit a first control message (eg, ES10c.DeleteProfile message) including the ID (ICCID) of the selected profile to the eUICC 4000 (3004). The eUICC 4000 may delete the profile and may generate a deletion notification message (3006). The deletion notification message may include Figure 1d The eUICC 4000 may transmit a result message to the controller 3000 (3008).

[0104] Operations 3010 to 3018 correspond to an example of a process in which the controller 3000 obtains data for verifying that a profile specified by a value of the ICCID has been deleted from the eUICC 4000 .

[0105] The process of obtaining this data does not need to be performed in exactly the same order as operations 3010 to 3018 in the figure, and may be performed by obtaining a large number of data fragments from the eUICC 4000 and extracting the deletion notification for the ICCID therefrom. Operations 3010 to 3018 are described as follows.

[0106] The controller 3000 sets the DeleteProfile bit in the event information (NotificationEvent) data to be received in the second control message (e.g., ES10c.ListNotificationRequest message), and transmits the second control message to the eUICC 4000 (3010). After receiving the second message, the eUCICC 4000 transmits all notification information corresponding to DeleteProfile to the controller 3000. The corresponding notification includes at least one of the processing sequence information (indicated by sequence, Seq, or seqNumber) and the profile ID (or iccid or ICCID) (3012).

[0107] The controller 3000 may select a notification or Seq value corresponding to the profile deleted in operation 3006 (3014), and may transmit a third control message (e.g., ES10c.RetrieveNotification message) including the Seq value to the eUICC 4000 (3016). The eUICC 4000 may transmit notification information corresponding to the Seq value in the stored notification information fragment to the controller 3000 (3018). The information included in the communication information may include at least one of the following information fragments:

[0108] -seqNumber: Process sequence number information (3018a)

[0109] -profileManagementOperation: An identifier used to identify whether the profile has been deleted (3018b)

[0110] -notificationAddress: configuration file server address (3018c)

[0111] -iccid: ID of the deleted configuration file (3018d)

[0112] -euiccNotificationSignature: Digital signature of the eUICC 4000 used to verify that the profile is an ICCID, that the proposed operation is an indicator indicating deletion, and that the processing sequence information is a SEQ value (3018e)

[0113] -eUICCCertificate: eUICC certificate used to verify the validity of the eUICC signature (3018f)

[0114] -EUMCertificate: Additional certificate used to verify the validity of the eUICC certificate (3018g)

[0115] Subsequently, the device 1 1000 may configure information including at least one of the above information in the form of an activation code, may encode the activation code into a QR code 1010a, and may display the QR code through a display of the device 1 (3020).

[0116] The information included in the QR code is information to be transmitted to the device 2. According to one embodiment of the present disclosure, the device 22000 eventually transmits part or all of the information obtained through the QR code to the profile server.

[0117] In the above data, the eUICC certificate is data used to verify that the eUICC signature is valid and does not necessarily need to be transmitted through the device 2 , and the EUM certificate is a certificate used to verify that the eUICC certificate is a valid certificate and does not necessarily need to be transmitted through the device 2 .

[0118] In this case, all or part of the eUICC certificate or additional certificates may be transmitted to the profile server using a different method rather than being included in the QR code.

[0119] For example, the device 1 may transmit the eUICC certificate or the additional certificate to the profile server through the profile download process, or may transmit the eUICC certificate or the additional certificate to the profile server separately through a profile activation / deactivation notification message or a different message. In another example, the device 1 1000 may store the eUICC certificate and the EUM certificate of the device 1 1000 in the process of issuing a subscription transfer request to the profile server before transmitting the activation code information to the device 2, and then may transmit the activation code to the device 2, but excluding the eUICC certificate and the EUM certificate in the aforementioned notification information fragment. The profile server may store the eUICC certificate and the EUM certificate received in advance, and may use them for signature verification of the activation code information transmitted by the device 2 to the profile server. The operation of the device 1 1000 regarding whether to include the eUICC certificate and the EUM certificate in the information transmitted from the device 1 1000 to the device 2 may be a fixed operation or may be changed according to the situation. For example, there may be a variety of methods, as follows.

[0120] 1) An operation of including or excluding certificates by the LPA or eUICC according to information provided by the profile server (e.g., version information about the server or indicator information included in a response to a subscription transfer request).

[0121] 2) An operation including or not including a certificate according to a setting value of a device (eg, version information about an eUICC).

[0122] 3) An operation in which the eUICC or LPA includes or does not include a certificate according to information of a setting value of a profile (eg, profile metadata) of the device 1 .

[0123] When the LPA performs an operation of excluding certificates in the above methods 1) to 3), the LPA may exclude the eUICC certificate and the EUM certificate from the notification data transmitted by the eUICC, may modify the data length value, and then may encode the data in the form of an activation code.

[0124] Furthermore, in operation 3020 , instead of displaying the information as a QR code, it is possible to transmit the information to the device 2 via short-range communication (such as NFC, Bluetooth, and UWB, Wi-Fi communication) or a server.

[0125] However, when device 1 displays the information as a QR code ( 1010 a ), device 2 can install the profile of device 1 through a general eSIM profile download process of scanning the QR code, thus enabling a device transfer operation without modifying the existing profile download process.

[0126] An example of the configuration of data to be displayed as the QR code (1010a) is shown below.

[0127] LPA: x$SMDP.TEST.COM$XXXXX

[0128] In this example, SMDP.TEST.COM represents the address of the configuration file server shown, $ represents an identifier for identifying each information fragment, LPA represents that this data is an activation code format for configuration file download, x represents the type of activation code and can have a value of, for example, 1, 2, 3, or 4, and XXXXX represents data in the ACToken area and can be information obtained by encoding information including part or all of the ASN.1 data shown below, which is indicated by XXXXX for simplicity.

[0129] ASN.1 Data

[0130] OtherSignedNotification::=SEQUENCE{

[0131] tbsOtherNotificationNotificationMetadata,

[0132] euiccNotificationSignature[APPLICATION 55]OCTET STRING,--eUICCsignature of tbsOtherNotification,Tag'5F37'

[0133] euiccCertificate Certificate,--eUICC Certificate(CERT.EUICC.ECDSA)signed by the EUM

[0134] eumCertificate Certificate--EUM Certificate(CERT.EUM.ECDSA)signed by the requested CI

[0135] }

[0136] NotificationMetadata::=

[47] SEQUENCE{--Tag'BF2F'

[0137] seqNumber[0]INTEGER,

[0138] profileManagementOperation[1]NotificationEvent, / *Only one bit SHALLbe set to 1* /

[0139] notificationAddress UTF8String,--FQDN to forward the notification

[0140] iccidIccid OPTIONAL

[0141] }

[0142] Here, the encoding may be 1) a method for expressing data in the ASN.1 format as characters by performing DER encoding and then performing hexadecimal encoding, or 2) a method for expressing data in the ASN.1 format as characters by performing DER encoding and then performing BASE64 encoding.

[0143] In addition, the process of generating an activation code by device 1 1000 may include some or all of the following operations.

[0144] 1. An operation of the LPA of the device 1 1000 to delete a profile by transmitting a message to the eUICC, for example, an operation of the LPA of the device 1 to delete a profile by transmitting an ES10c.DeleteProfile message to the eUICC using the profile ID or ICCID of the profile to be deleted

[0145] 2. The LPA of the device 1 1000 obtains at least one of the PendingNotification TLV or the OtherSignedNotification TLV by transmitting the Es10b.RetrieveNotificationList message to Euicc

[0146] 3. Use notificationMetadata information to obtain the DeleteNotification operation of the ICCID in one or more of PendingNotification TLV or OtherSignedNotification TLV separately. For example, notificationMetadata information may include at least one of ICCID or NotificationEvent

[0147] 4. When transmitted from the eUICC to the LPA, the PendingNotification TLV or OtherSignedNotification TLV may be ASN.1DER encoded byte stream data. An operation of expressing each 1-byte data as a 2-digit string by treating this hexadecimal byte stream data as characters from 0 to 9 and A to F (e.g., an operation of expressing 9-byte byte stream data (such as "0x01 0x23 0x45 0x67 0x89 0xAB 0xCD 0xEF 0x00" expressed in hexadecimal numbers) as an 18-digit string (such as "0123456789ABCDEF"))

[0148] 5. Operation of including a string in AC_Token as an activation code

[0149] 6. Operation of encoding the activation code into a QR code image

[0150] Although not shown in the figure, before deleting the profile to transfer the profile from device 1 1000, device 1 1000 can obtain device information (e.g., eUICCInfo or DeviceInfo) about device 2, the device information can be transmitted to the profile server to check whether it is possible to reinstall the profile in device 2, and then subsequent processes can be performed.

[0151] Figure 3 The operation of the device 2 2000 and the configuration file server 6000 according to one embodiment of the present disclosure is shown.

[0152] refer to Figure 3 , device 2 2000 can be Figure 2 The QR code displayed on the device 1 1000 in the operation 3020 shown in the figure starts the profile download process (5002). The device 2 2000 may transmit an InitiateAuthenticate message 5006 to the profile server 6000 corresponding to the profile server address included in the QR code 1010a (5004). Here, the InitiateAuthenticate message may include an eUICCChallenge. When receiving the InitiateAuthenticate message 5006, the profile server 6000 may generate a transaction ID, may generate a signature of the profile server for the data including the eUICCChallenge and the transaction ID (5008), and may transmit a response to the device 2 2000 (5010). Here, the transmitted InitiateAuthenticate response message may include a profile signature value and a transaction ID (5010). After receiving the InitiateAuthenticate response message, device 2 2000 may generate data including the ICCID and eUICC signature data of device 1 included in the QR code and device 2 eUICC signature data obtained by signing the data by the eUICC of device 2 2000 (5012), and may transmit an AuthenticateClientRequest message including the data fragment to the profile server 6000 (5014).

[0153] When receiving the AuthenticateClientRequest message, the profile server 6000 performs a validity verification process (which includes verification of the ICCID included in the AuthenticateClientRequest message, the signature data of the eUICC of the device 1, and the signature data of the eUICC of the device 2), may determine whether to download the profile, and may transmit an AuthenticateClientResponse message including data having ProfileMetadata corresponding to the profile (5018). The verification of the signature data of the eUICC of the device 1 may be a signature verification using the certificate 3018f of the eUICC 4000 of the device 1 2000 for data including the ICCID and data including the additional data (that is, data including 3018a, 3018b, 3018c, and 3018d).

[0154] The signature verification may be an elliptic curve digital signature authentication (ECDSA). The eUICC certificate 3018f may be authenticated as the EUM certificate 3018g as described above. The EUM certificate 3018g may be verified as a certificate authority (CA) certificate included in the profile server. The CA certificate may also be referred to as a certificate issuer (CI) certificate. The validity verification process 5016 may include a process of identifying the eUICC that is ultimately installed relative to the ICCID as the eUICC of device 1 and a process of using the seq number 3018a to identify the validity of the message. In addition, although not shown in the figure, the validity verification process of the profile server 6000 may also include a process in which the profile server 6000 inquires the operator server whether to allow the reinstallation of the profile of the ICCID and receives the query result, such as in Figure 1b As described in.

[0155] Specifically, the process of the configuration file server verifying the signature data of the device 1 may include some or all of the following operations.

[0156] 1. An operation of configuring the configuration server to obtain information (e.g., CtxParamsForCommonAuthentication TLV) included in the AuthenticateClient Request message received from the device 2 (here, the operation of obtaining the CtxParamsForCommonAuthentication TLV may include an operation of obtaining ASN.1DER-encoded byte stream data by performing Base64 decoding on the AuthenticateClient Request message)

[0157] 2. Extract matchingId TLV from CtxParamsForCommonAuthentication TLV

[0158] 3. The operation of obtaining the string corresponding to AC_Token by performing UTF8 decoding in matchingID TLV

[0159] 4. An operation of converting the AC_Token string into byte stream data of the ASN.1DER-encoded PendingNotification TLV or OtherSignedNotification TLV by matching each 2-digit string with each 1-byte data (e.g., an operation of converting an 18-digit string (such as "0123456789ABCEDF00") into 9-byte byte stream data expressed in hexadecimal numbers (such as "0x01 0x23 0x45 0x67 0x89 0xAB 0xCD 0xEF 0x00")

[0160] 5. Operations to extract signature information from the ASN.1DER encoded byte stream data of the PendingNotification TLV or OtherSignedNotification TLV (e.g., the ASN.1DER encoded byte stream data of the euiccNotificationSignature TLV)

[0161] 6. Operation of verifying the signature of device 1 using euiccNotificationSignature byte stream data and other data

[0162] Subsequently, device 2 2000 may receive an AuthenticateClientResponse message (5018), and when the AuthenticateClienteResponse message includes ProfileMetadata, device 2 2000 may perform some or all of the following processes: a process of consenting to receive a profile through a UI displayed to a user, a process of requesting input of a confirmation code and receiving the confirmation code, and a process of generating a one-time public key (otpk.eUICC) of an eUICC (5020).

[0163] When the device 2 2000 transmits a GetBoundProfilePackage request including otpk.eUICC to the profile server 6000 (5022), the profile server 6000 may generate a BoundProfilePackage including information encrypted by the encryption key generated using otpk.eUICC (5024), and may transmit the BoundProfilePackage to the device 2 2000 (5026). Upon receiving the BoundProfilePackage (5026), the device 2 2000 may install the profile in the eUICC of the device 2 2000 (5028).

[0164] Figure 4 The internal operation of the device 1 according to one embodiment of the present disclosure is shown.

[0165] refer to Figure 4 , the device 1 1000 is a device in which the eUICC 4000 is installed, and includes a controller 3000 capable of exchanging eUICC control messages with the eUICC 4000. The controller 3000 is collectively referred to as HW and SW, which control the eUICC 4000 in conjunction with the eUICC 4000 (except the eUICC 4000 in the device 1 1000), and the controller 3000 may be HW such as AP, CP or baseband, or may be SW such as LPA.

[0166] because Figure 4 The process of operation 6002 and operation 6002a is the same as Figure 1d The process from operation 1002 to operation 1004 is equivalent or similar, so Figure 1d The description mentioned there.

[0167] Referring to operation 6004, when a user selects a specific profile on the screen of device 1 1000, device 1 1000 may determine whether the profile 6004a supports a profile transfer function (6004).

[0168] The determination can be performed by the following method.

[0169] 1) Determine by querying the configuration file server

[0170] 2) Determined by querying a different server other than the configuration file server (e.g., a check server)

[0171] 3) Use information stored in the device to determine

[0172] These methods are further described below.

[0173] 1) The process in which the device determines whether a specific profile supports profile transfer by querying the profile server may include the following process: the device transmits a query request message when querying the server, the query request message including at least one data fragment among ICCID, SEQ, ProfileManagementOperation type identifier, eUICC signature, eUICC certificate, eUICC EUM certificate, or secondary CA certificate. The ProfileManagementOperation type identifier may include information indicating enabling, disabling, or deleting a profile.

[0174] In the process of determining whether a specific profile supports profile transfer by querying a profile server, after the device queries the profile server, the profile server may transmit a response message including whether the server supports the profile transfer function of the specific profile and additional information to the device in response. The additional information may include at least one data segment of additional information about the following items: a payment requirement related to profile transfer of the specific profile, a remaining possible number of transfers related to profile transfer of the specific profile, or constraint information indicating a restriction on allowing the profile to be installed only on a specific device.

[0175] 2) The process in which the device determines whether a specific profile supports profile transfer by querying a checking server may include the following process: the device transmits a query request message to the server when querying the server, and the query request message includes at least one data segment of ICCID, operator information, profile server address or profile server ID.

[0176] The process of a device determining whether a specific profile supports profile transfer by querying different servers may include the following process: after the device queries the server, in response, the server may transmit a response message to the device, wherein the response message includes at least one data segment including transfer information about whether profile transfer by ICCID is supported and profile server information.

[0177] 3) A process in which a device determines whether a specific profile supports profile transfer using information stored in the device may be a method in which the device transfers a profile using profile transfer support information stored when the profile is installed.

[0178] In an embodiment of the present disclosure, it is possible to select the profile transfer menu (6006 / 6008) after operation 6004. However, in another embodiment, after the profile transfer menu is first displayed and the user selects or confirms the profile transfer, it may be determined whether the profile transfer is possible (6004), and when the transfer is possible, operation 6010 to be described below may be performed, and when the profile transfer is not possible in operation 6004, it may be indicated to the user through the UI of the device 11000 that the profile transfer is not supported. Here, in the aforementioned various processes of determining whether the profile transfer function is supported, a guidance message for using the information obtained by the device 11000 from the profile server or the check server or the information stored in the device 11000 may also be displayed through the UI of the device 11000.

[0179] In yet another embodiment, when the user has not entered the profile management menu but the device has previously confirmed for each profile whether profile transfer is supported, the profile transfer may be displayed in 6006 using the corresponding information only if profile transfer is supported.

[0180] Subsequently, the device 1 1000 may transmit an ES10c.DeleteProfile message including the ID (ICCID) of the selected profile to the eUICC (6010). The eUICC 4000 may delete the profile and may generate information of a deletion notification (6012). The information of the deletion notification may include Figure 1d The eUICC 4000 may transmit a result message to the controller 3000 after deleting the configuration file.

[0181] Operation 6016 is a process in which the controller 3000 obtains data for verifying that the profile specified by the ICCID value has been deleted from the eUICC 4000, and the data may be notification data generated by the eUICC 4000 in operation 6012. In one example of operation 6016, the controller 3000 may fully or partially apply Figure 2 Operation 3010 to operation 3018.

[0182] In operation 6018, device 1 1000 may additionally transmit a notification to the profile server. Using operation 6018, all or part of the certificate of the eUICC of device 1 1000 or the advanced certificate of the certificate of the eUICC may be directly transmitted to the server through device 1 1000 instead of device 2.

[0183] The device 1 1000 may encode the information including the information into a QR code and may display the QR code (6020).

[0184] The encoding method and data included in the QR code can be Figure 1d and Figure 2 are the same as or similar to those described in , and therefore their description will be omitted.

[0185] In operation 6020, instead of displaying the information as a QR code, it is possible to transmit the information to the device 2 through short-range communication such as NFC, Bluetooth, and UWB or Wi-Fi communication or via a check server, which can be applied to all embodiments of the present disclosure.

[0186] Figure 5 The internal operation of the device 1 according to one embodiment of the present disclosure is shown.

[0187] Figure 5 The process of operation 7000 to operation 7014 is Figure 4 The processes of operation 6002a to operation 6020 are the same or similar, and thus the description thereof will be omitted. Figure 5 The process of operation 7016, operation 7018 and operation 7020 may correspond to the user selecting Figure 1d The operations in the case of the cancel / restore menu in the example and the operations in the case where the user selects the later confirmation menu. The detailed description of these operations corresponds to the Figure 1d Description of embodiments of the present invention.

[0188] Figure 6 The process of transferring access information from device 1 to device 2 according to one embodiment of the present disclosure is shown.

[0189] refer to Figure 6 , operations 8002 to 8008 and Figure 1d Operations 1002 to 1008 are the same or similar, and therefore their related descriptions correspond to Figure 1d Description of the . Figure 6 In operation 8010 of , when displaying the QR code 8010a, the device 1 1000 may display information of a confirmation code (CC) 8010e. The confirmation code 8010e may be information that the device 1 1000 stores internally and then displays when the confirmation code is required when installing the profile 8004a that is the profile transfer target. The method of storing the confirmation code internally may be a method of storing the confirmation code in the controller or eUICC of the device 1 1000 when installing the profile. The subsequent process is the same as Figure 1dThe operation of the device 2 2000 is similar to that of the device 1 1000, but an operation (8016) of requesting the user to input a confirmation code is added after the device 2 2000 scans the QR code (8014) of the device 1 1000. Here, the user can input the displayed confirmation code 8010e to the device 1 1000. Therefore, it is possible to easily provide a profile transfer without recognizing a separately stored confirmation code.

[0190] In another embodiment, the device 1 1000 may display a guide message indicating that a confirmation code is required, instead of displaying the confirmation code in operation 8010. In addition, the device 1 1000 may display a guide message indicating that a confirmation code is required to the user at a time before the device 1 1000 deletes the profile. Therefore, the guide message may be provided so that the user who has not stored the confirmation code does not perform the profile move. Since operations 8018 and 8020 correspond to Figure 1d Operation 2006 and operation 2008 are described, and thus their description is omitted.

[0191] Figure 7 The operation of the apparatus 1 before transferring the configuration file according to one embodiment of the present disclosure is shown. Figure 7 The process may need to be executed in advance to execute Figure 6 process of process of process.

[0192] refer to Figure 7 , when receiving AuthenticationClientResponse or scanning the activation code, device 1 may determine whether a confirmation code is required for profile download (9002). When a confirmation code is required (9004), device 1 may display a UI for inputting a confirmation code (9006). When the user inputs the confirmation code, device 1 may temporarily store the confirmation code (9010). Device 1 may transmit GetBoundProfilePackage to the profile server, and when BoundProfilePackage is received normally (9014), device 1 may install BoundProfilePackage (9016). When it is determined in operation 9014 or 9016 whether to maintain or delete the temporarily stored value after determining to maintain the temporarily stored confirmation code, the temporarily stored confirmation code may be mapped to the profile and may be stored in the memory of device 1. In the process of storing the confirmation code in the memory in or after operation 9010, the confirmation code may be stored in a controller, an eUICC, a secure element, or a HW equivalent thereto. In addition, the confirmation code may be stored in association with the profile. That is, when the ICCID or profile is subsequently specified, the corresponding confirmation code may be stored in association with the ICCID or profile.When the confirmation code is not required and the profile is installed based on user consent, operation 9012 and subsequent operations may be performed.

[0193] Figure 8 The internal operation of the device 1 according to one embodiment of the present disclosure is shown.

[0194] Figure 8 Similar to Figure 5 The process is similar to that of , but the difference is that the confirmation code can be additionally displayed in operation 7014a. Other operations are similar to Figure 5 Those operations, Figure 5 The description mentioned there.

[0195] Fig. 9 The process of transferring access information from device 1 to device 2 according to one embodiment of the present disclosure is shown.

[0196] because Fig. 9 The process and Figure 6 The process is the same or similar, so the overall description is omitted and Figure 6 The description mentioned there. Fig. 9 The process and Figure 6 The process has the following additional differences. Fig. 9 When the user selects a configuration file transfer of a specific configuration file on the device 1 1000, the device 1 1000 may request the user to enter a confirmation code (9008). The user may enter the confirmation code used when installing the configuration file. The device 1 1000 may identify whether the confirmation code entered by the user matches the one entered in the Figure 7 Alternatively, it is possible to identify whether the value of the operation (e.g., hash operation) of the confirmation code input by the user in operations 9006 to 9010 is the same as the internally stored confirmation code. When the device 1 1000 determines that the confirmation code input by the user is valid through the aforementioned various processes of identifying whether the confirmation codes are the same, operation 9010 may be performed. The description of operation 9010 is the same as that of operation 9011. Figure 6 or Figure 1d , and thus further description is omitted.

[0197] Fig.10 The operation of the apparatus 1 before transferring the configuration file according to one embodiment of the present disclosure is shown.

[0198] Fig.10 Operation and Figure 7 The operation is similar to that of Fig.10 The specific operation corresponds to Figure 7 However, in Fig.10 When the confirmation code is stored in the device 1, the confirmation code may be stored or a hash of the confirmation code may be stored (operation 10010). The hash value may be a SHA256 hash function.

[0199] Fig.11 The operation of the apparatus 1 according to one embodiment of the present disclosure is shown.

[0200] Fig.11 Shows Fig. 9 The operation of the device 1 is reconfigured, and its detailed description is similar to Fig. 9 Description and Figure 8 , and specific operations correspond to Figure 8 , Fig. 9 and Fig.10 Description.

[0201] Fig.12 The operation of a profile server according to one embodiment of the present disclosure is shown. Fig.12 Can correspond to Figure 3 The operations of the configuration file server 6000 in operations 5014, 5016 and 5018.

[0202] refer to Fig.12 When the profile server receives the AuthenticateClientRequest (1210), the profile server may use the matchingID information or the EID information of the AuthenticateClientRequest to check whether there is a pending command for internally downloading the profile (1220). When there is no pending command, operation 1230 may be performed, and the profile server may additionally identify whether there is a valid profile deletion verification message in the AuthenticationClientRequest (1230). The validity verification process may be as follows.

[0203] The information / record stored in the profile server needs to include the ID of the eUICC (or EID or EID of the device 1) on which the profile is installed, data including the ICCID and Seq number information of the profile, and signature information about the eUICC of the device 1 for the data. In addition, the process includes determining whether the signature value of the eUICC is valid and whether a condition that there is a value equal to or greater than the Seq number included in the AuthenticationClientRequest in the Seq number included in the notification data about the previously received eUICC and ICCID is satisfied. When the determination process is successful, a request to download the profile may be added to the pending command (1240).

[0204] When there are pending commands, the profile server may generate an AuthenticateClientResponse message including the profile metadata ( 1250 ). The profile server may transmit the AuthenticateClientResponse message including the profile metadata to device 2 .

[0205] Fig.13 The process of transferring a configuration file from device 1 to device 2 according to one embodiment of the present disclosure is shown.

[0206] refer to Fig.13 ,

[0207] 1), 2) Device 1 and Device 2 can respectively execute the integrated terminal transfer application.

[0208] 3) Device 1 and device 2 can be connected through an integrated terminal delivery application. Here, short-range communication (such as NFC, Wi-Fi, Bluetooth, and UWB) can be used for connection, or the connection can be established through a server.

[0209] 4) Device 1 can transmit the terminal usage environment (such as contact information on the terminal, installed application list information and data in the application) to device 2.

[0210] 5) Device 1 may perform a profile transfer process for each profile installed in the eUICC of device 1 according to all or part of the profile transfer operations described in the above embodiments. For effective transfer, multiple deletion notification information fragments may be transmitted through the connection between applications established in operation 3), instead of displaying the corresponding information as a QR code mentioned in the above embodiments. Instead of displaying the information as a QR code, the information may be transmitted to device 2 via short-range communication (such as NFC, Bluetooth and UWB, or Wi-Fi communication) or via a server.

[0211] 6) Device 2 may use the information (such as contact information) received from device 1 in 4) to set the environment to be the same as or similar to that of device 1.

[0212] 7) Device 2 can be based on Figure 3 The corresponding configuration file is installed for each of the one or more deletion notification fragments received in 5) according to the process described in . Here, the deletion notification information can be converted into ACToken format for use.

[0213] Fig.14 The figure shows a process of transferring a configuration file according to an embodiment of the present disclosure.

[0214] Fig.14 Can be used with Figure 4 The contents are similar to the other embodiments above, but the operation process of the improved details and the newly added operations are specifically explained in a supplementary manner.

[0215] refer to Fig.14 , the SM-DP+ (or profile server) may execute a mechanism for determining whether profile transfer of a specific profile is allowed. The mechanism may be one of the following methods (operation 20000).

[0216] 1) Method to configure SM-DP+ to allow profile transfer for all or some profiles

[0217] 2) A method for configuring whether to allow profile transfer of a profile when the operator server requests the SM-DP+ server to prepare to download a profile (for example, including information for configuring whether profile transfer is allowed in a profile download preparation request). The profile download preparation request may be an ES2+.DownloadOrder, ES2+.ConfirmOrder, or ES2+.ReleaseProfile command message. The information for configuring whether profile transfer is allowed may be included in a message defined separately from the command message.

[0218] 3) A method in which the device inquires the operator server through SM-DP+ to determine whether to allow the profile transfer whenever the device inquires the SM-DP+ about the profile transfer request

[0219] 4) A method for SM-DP+ to determine that configuration file transfer of all installed configuration files is allowed when the terminal identifies version information (e.g., SVN value) through information exchange with SM-DP+ and the version information satisfies a specific condition

[0220] 5) A method for identifying a profile transfer permission condition (e.g., a specific communication operator code in a profile (e.g., a profile downloaded from SM-DP+) that is allowed to be installed after a specific date) recognized by a terminal that is connected to SM-DP+ through a message, and allowing profile transfer of all profiles that meet the condition

[0221] The user may enter a configuration file transfer menu in the device from which the configuration file is to be transferred (referred to as device 1 (old device) for convenience) (operation 20010).

[0222] The device 1 may transmit a message for inquiring whether to allow the profile transfer to the SM-DP+ in order to perform the profile transfer (operation 20020). The message may include the ICCID. The message may be a message for mutual authentication in the mutual authentication process between the device 1 and the SM-DP+. For example, the message may be at least one of ES9.InitiateAuthenticateRequest or ES9.AuthenticateClientRequest. Depending on the method for allowing the profile transfer, operation 20020 may be omitted. The message for inquiring whether to allow the profile transfer may include or omit the ID (e.g., ICCID) of a specific profile ID.

[0223] When the message is received in operation 20020, the SM-DP+ may determine whether the profile transfer of the profile is allowed and may transmit the determination result and the message to be displayed to the user to the device 1 (operation 20030). Here, the SM-DP+ may use the three methods described in operation 20000 to determine whether the transfer of the profile is allowed. For example, in operation 20040, the SM-DP+ may inquire the operator server whether the profile transfer is allowed, and in operation 20050, the result and the message to be displayed to the user may be received, in which case the message in operation 20030 may include all or part of the information included in the message in operation 20050.

[0224] When SM-DP+ basically supports profile transfer, operations 20020 and 20030 may be omitted. Alternatively, operation 20020 or operation 20030 may be replaced by identifying version information on a specific SM-DP+ to identify whether SM-DP+ supports profile transfer. For example, device 1 may transmit an ES9.InitiateAuthenticateRequest message to SM-DP+, and may use version information on SM-DP+ or other indicator information transmitted in response to determine that SM-DP+ provides profile transfer for all profiles.

[0225] When it is determined that the profile transfer is possible through the above-mentioned various methods, the device 1 may display a UI using the information in operation 20030 or the information internally set in operation 20060 to obtain the user's consent to the profile transfer.

[0226] When the user agrees to the configuration file transfer, the device 1 may delete the configuration file and may generate an activation code using the DeleteNotification information (operation 20070 to operation 20100). Figure 4Some or all of operations 6010 to 6020 overlap, so their detailed descriptions are omitted in this figure and their related descriptions correspond to Figure 4 Description.

[0227] The activation code information generated from device 1 in operation 20100 may be transmitted to device 2 (new device) 1) by displaying it as a QR code on the screen of device 1, or 2) by Wi-Fi connection, Bluetooth connection, or cable connection between device 1 and device 2 (operation 20110). In operation 20110, a profile nickname of the profile may be additionally transmitted when the activation code information is transmitted. The profile nickname may be information stored in the eUICC or information stored in the LPA, and the user may set the profile nickname through the LPA before the profile transfer operation in this figure, or the LPA may read the profile nickname from the eUICC in advance and may store the profile name.

[0228] Device 2 may download a configuration file from SM-DP+ using the activation code information transmitted in operation 20110 (operation 20120). Operation 20120 is described in detail in operations 20130 to 20160 as follows.

[0229] Device 2 may start a mutual authentication process between device 2 and SM-DP+ by transmitting an ES9.InitiateAuthenticate request to SM-DP+. In this process, in order for device 2 to authenticate SM-DP+ before transmitting the information received in operation 20110, device 2 generates a random value, includes the random value in the information and transmits the information to SM-DP+, and SM-DP+ generates a server signature value for the information including the random value and transmits the server signature value and the server certificate to device 2 together (operation 20130). Device 2 may transmit an ES9.AuthenticateClientRequest message including the activation code information received in operation 20110 to SM-DP+. Here, the activation code information may be information including some or all of the DeleteNotification information, as described above. When receiving the information, SM-DP+ may perform at least one of an operation of verifying that the profile corresponding to the DeleteNotification information has been deleted from the eUICC of device 1 and an operation of determining whether profile transfer is possible, thereby determining whether to download the profile corresponding to the deleted profile to device 2, and may transmit the determination result to device 2 through an AuthenticateClient Response message (operations 20140 and 20150). For example, SM-DP+ may transmit profile metadata for profile download to device 1.

[0230] When a response accepting the profile download is received in operation 20140, device 1 may use ES9.GetBoundProfilePackage to request profile download from SM-DP+ in operation 20160, and SM-DP+ may transmit the corresponding encrypted profile package upon receiving the message. Subsequently, device 2 may install the profile in the eUICC of device 2 (operation 20120).

[0231] When the profile nickname information is also transmitted to the device 2 in operation 20110, the device 2 may download and install the profile in operation 20120, and then the profile nickname of the profile may be updated to the profile nickname transmitted in operation 20110 (operation 20170). When this function is used, when all profiles of the device 1 are transferred to the device 2 (such as Fig.13 As shown), device 2 does not need to re-execute the user setting each information for each configuration file in device 1.

[0232] Fig.15 A configuration file transfer according to one embodiment of the present disclosure is shown.

[0233] refer to Fig.15 , reference may be made to an embodiment of the UX of device 1 21000 and device 2 2000 when transferring a configuration file. Fig.15 The operations and screens indicated by 21002 to 22008 in the embodiment are similar to Figure 1d The operations and screens indicated by 1002 to 2008 in FIG. 1 are substantially similar, but are shown in separate figures to indicate the following differences.

[0234] refer to Fig.15 In the operation of obtaining the user's consent to transfer the configuration file of device 1, device 1 21000 may display information necessary for the user to consent. The information displayed to the user may be information preset in the device, or may include at least one information included in the information obtained by asking the configuration file server whether to allow the transfer of the configuration file. For example, device 1 21000 may display a user message 21008b1 obtained from SM-DP+ and description information 21008b2 preset in device 1 21000 together. The user message obtained from SM-DP+ may be Fig.14 The user message transmitted in operation 20030. Various messages related to the configuration file transfer may be transmitted to the user via the user message. Fig.16 A related embodiment is shown in FIG.

[0235] Fig.16 An example of a message that may be displayed to a user when transferring a configuration file is shown.

[0236] Fig.16 A message displayed to a user when transferring a configuration file according to one embodiment of the present disclosure is shown.

[0237] Fig.16 Various embodiments show Figure 1d The screen of operation 1008 or Fig.15 Configuration example of the screen of operation 21008 in FIG.

[0238] 23002 shows whether the result of allowing the configuration file transfer is successful, and Fig.14 The user message is transmitted in operation 20030 as follows:

[0239] "You can transfer this profile to another device.

[0240] Once this profile is transferred to another device, profile transfer will be prohibited for 2 weeks.

[0241] Please take note when your decision is confirmed.”

[0242] Since the result was success,

[0243] As set in device 1,

[0244] Therefore, a message "Are you sure you want to confirm the transfer of this configuration file?" can also be displayed. When the result is successful, a menu can be provided to the user for confirming or still canceling the configuration file transfer.

[0245] 23004 shows whether the result of allowing the configuration file transfer is successful, and Fig.14 The user message is transmitted in operation 20030 as follows:

[0246] "You have consumed all the free quota for profile transfers available on your plan.

[0247] Further transfers will be charged $1 per transfer on your next monthly bill. "Similarly, since the result is successful, as set in Device 1,

[0248] Therefore, a message "Are you sure you want to confirm the transfer of this configuration file?" can also be displayed. When the result is successful, a menu can be provided to the user for confirming or still canceling the configuration file transfer.

[0249] 23006 shows the Fig.14 The result of whether to allow the configuration file transfer in operation 20030 is a rejection, and a user message such as

[0250] "Sorry, you need to visit your service provider to transfer this profile."

[0251] When the result is a rejection, a menu for canceling (or returning) the profile transfer may be displayed to the user instead of a menu for confirming the profile transfer.

[0252] As described above, in the present disclosure, since the configuration file of the device 1 needs to be deleted in order to transfer the configuration file, various related user guide messages may be configured.

[0253] Although not shown in the drawings, instead of agreeing to the user message and immediately deleting the profile, when the user agrees to the user message, device 1 may transmit consent to the profile transfer back to SM-DP+, SM-DP+ may provide information on whether the profile transfer is additionally allowed or code information additionally required for the profile transfer to device 1, device 1 may transmit this information to device 2, and device 2 may transmit the information to SM-DP+ and download the profile.

[0254] Fig.17 The following is a diagram showing a configuration file transfer process according to an embodiment of the present disclosure.

[0255] refer to Fig.17 Describes an operation of allowing a profile transfer based on a public key or information corresponding to a public key pre-registered in a profile server when transferring a profile. For example, when a public key signed by a terminal manufacturer or an ID of a public key is stored in a profile server (SM-DP+) with the agreement between the terminal manufacturer and the communication service provider, the SM-DP+ may allow a profile transfer of a subsequent profile transfer request including a digital signature corresponding to the public key. Fig.17 A specific example is shown in .

[0256] The device 1 may be installed with an eUICC and an LPA. However, the LPA may be outside the device 1. For example, when repairing the terminal, the terminal manufacturer may connect the AS device and the device 1, and may perform device transfer by controlling the eUICC using the LPA of the AS device. For convenience, it is assumed that the LPA exists in the device 1 for description, including the case where the device 1 is connected to the AS device.

[0257] First, a public key, a certificate corresponding to the public key, a public key identifier (PKID) value, or an identifier that can be included in the signature value later may be stored in the SM-DP + in advance (24002). Alternatively, even if it is not stored in operation 24002, the necessary information may be obtained in the following operation 24018.

[0258] The user may input a profile transfer (24004) through the LPA of the device 1. The profile transfer may be input through the screen of the device 1, or may be input by the LPA of a different device (e.g., an AS device) connected to the device 1. Here, a specific profile or profile ID may be specified through the LPA. The operation of inputting a profile transfer is not limited to the above example.

[0259] The LPA of device 1 may transmit an Initiate Authentication Request to SM-DP+ (24006). The Initiate Authentication Request message may include eUICC challenge information, etc. SM-DP+ may transmit an Initiate Authentication Response to device 1 (24008). The Initiate Authentication Response may include a signature of SM-DP+, a server challenge, a TransactionId, etc.

[0260] The LPA of device 1 may generate digital signature data (24010). The LPA of device 1 may generate a digital signature value for data including at least one value of a profile transfer indicator, an ICCID, a ServerChallenge, or a TransactionID using a private key of the OEM. When generating signature data, the signature may be generated by the LPA of device 1, but may be generated by a device of a terminal manufacturer or a separate server and may be transmitted to the LPA of device 1 (24012).

[0261] The LPA of device 1 may transmit an AuthClientRequest to the SM-DP+ (24014). The AuthClientRequest may include at least one of an OEMSignature, an ICCID, a profile transfer indicator, a public key, a public key ID, or a certificate chain. When the OEM signature is included, the SM-DP+ may verify the OEM signature and may also verify whether the OEM signature corresponds to the information registered in operation 24002, such as a public key. The verification may be performed by an operator server (24018).

[0262] When the OEM signature is verified, the SM-DP+ may transmit an AuthClientResponse to the LPA of the device 1 (24020). The AuthClientResponse may include an indicator indicating whether an AC is generated based on the ActivationCode or the DeleteNotifciation.

[0263] Device 1 can determine whether the indicator indicates the use of AC through DeleteNotification. When the indicator indicates the use of AC through DeleteNotification, the LPA of device 1 can delete the configuration file and can generate an activation code using the DeleteNotification (24022). The process of deleting the configuration file, obtaining the DeleteNotification, and generating the activation code using the DeleteNotification has been described in detail in other embodiments of the present disclosure, and its detailed description is therefore omitted. The LPA of device 1 can display the activation code or the activation code received in operation 24020 as a QR code on the screen of the terminal, or can transmit it to device 2 (24024). Device 2 can scan the displayed QR code, or can download the configuration file from SM-DP+ using the received activation code (24026). When an AC based on DeleteNotification is transmitted when downloading a configuration file, SM-DP+ can verify the DeleteNotification and can then download the configuration file.

[0264] In this profile transfer involving OEMSignature, whenever the profile transfer is performed, the SM-DP+ or operator may record the OEMSignature and the attached data together. In operation 24028, the terminal manufacturer and the communication service provider or SM-DP+ provider may use the data to mutually verify the amount of the profile transfer, and the cost may be calculated based on the amount.

[0265] Fig.18 The structure of a terminal according to an embodiment of the present disclosure is shown.

[0266] refer to Fig.18 , the terminal may include a transceiver 1810, a controller 1820, and a storage unit 1830. In an embodiment of the present disclosure, the controller 1820 may include a circuit, an application specific integrated circuit, or at least one processor. In an embodiment of the present disclosure, the terminal may further include at least one UICC 1840. The UICC 1840 may be embedded in the terminal, or may be detachably coupled to the terminal. According to various embodiments of the present disclosure, the terminal may correspond to a device for transferring a configuration file, a device for downloading a configuration file, etc.

[0267] The transceiver 1810 may transmit signals to different network entities or receive signals from different network entities.

[0268] According to the embodiments proposed herein, the controller 1820 may control the overall operation of the terminal. For example, the controller 1820 may control the signal flow between blocks to perform the operation of the terminal according to the above flowchart.

[0269] The storage unit 1830 may store at least one of information transmitted or received by the transceiver or information generated by the controller.

[0270] According to various embodiments of the present disclosure, the operation of the LPA may be interpreted as the operation of the controller 1820. In addition, the operation of the LPA may be interpreted as the operation according to the control of the controller 1820.

[0271] Fig.19 The structure of a configuration file server according to an embodiment of the present disclosure is shown.

[0272] refer to Fig.19 , the profile server may include a transceiver 1910, a controller 1920, and a storage unit 1930. For example, the profile server may include at least one of an SM-DP, an SM-DP+, or an SM-DS.

[0273] The transceiver 1910 may transmit signals to different network entities or receive signals from different network entities.

[0274] According to the embodiments proposed herein, the controller 1920 may control the overall operation of the profile server. For example, the controller may control the signal flow between blocks to perform the operation of the profile server according to the above flowchart.

[0275] The storage unit 1930 may store at least one of information transmitted or received by the transceiver or information generated by the controller.

[0276] In the above detailed embodiments of the present disclosure, the elements included in the present disclosure are expressed in the singular or plural, depending on the detailed embodiments presented. However, for ease of description, the singular form or plural form is appropriately selected for the presented situation, and the present disclosure is not limited to elements expressed in the singular or plural. Therefore, an element expressed in the plural may also include a single element, or an element expressed in the singular may also include multiple elements.

[0277] Although specific embodiments have been described in the detailed description of the present disclosure, various modifications and changes may be made thereto without departing from the scope of the present disclosure. Therefore, the scope of the present disclosure should not be defined as limited to the embodiments, but should be defined by the appended claims and their equivalents.

Claims

1. A method performed by a first terminal, the method comprising: receiving input to transfer a configuration file installed in the first terminal; deleting the configuration file from a first universal integrated circuit card (UI CC) of the first terminal; generating data including information indicating deletion of the configuration file and an address of a configuration file server for the second terminal to download the configuration file; as well as outputting the data as information obtainable by a second terminal, The data is used for the second terminal to obtain the configuration file.

2. The method of claim 1, wherein the data corresponds to an access token of an activation code, and Among the available information is a Quick Response (QR) code in a format corresponding to the activation code. 3 . The method of claim 1 , wherein the data comprises at least one of: identification information about the profile and a certificate of the first UI CC.

4. A method performed by a second terminal, the method comprising: obtaining data including information about a profile deleted from a first universal integrated circuit card (UI CC) of a first terminal; transmitting, based on the data, a first message including identification information about the profile and deletion information about the profile to a profile server; receiving metadata about the profile based on identification information about the profile and deletion information about the profile; transmitting, based on the metadata, a second message including a download request for the configuration file to the configuration file server; as well as The configuration file is downloaded from the configuration file server.

5. The method of claim 4, wherein the first message further includes signature information about the first UI CC and signature information about the second UI CC of the second terminal, wherein said data corresponds to an access token of an activation code, wherein the data is obtained from a Quick Response (QR) code of a format corresponding to the activation code, and The data includes at least one of the following: identification information about the configuration file, an address of a configuration file server for the second terminal to download the configuration file, indication information indicating deletion of the configuration file, and a certificate of the first UI CC.

6. A method performed by a configuration file server, the method comprising: receiving a first message from a second terminal, the first message including identification information about a configuration file deleted from the first terminal and deletion information about the configuration file; generating metadata about the profile based on the identification information about the profile and the deletion information about the profile; transmitting the metadata to the second terminal; receiving a second message from the second terminal, wherein the second message includes a download request for the configuration file; as well as The configuration file is transmitted to the second terminal.

7. The method according to claim 6, wherein the second terminal obtains identification information about the deleted configuration file and deletion information about the configuration file from the first terminal, and The first message further includes signature information about a first UI CC of the first terminal and signature information about a second UI CC of the second terminal.

8. The method of claim 7, wherein the data corresponds to an access token of an activation code, wherein the data is obtained from a Quick Response (QR) code of a format corresponding to the activation code, and The data includes at least one of the following: identification information about the configuration file, an address of a configuration file server for the second terminal to download the configuration file, indication information indicating deletion of the configuration file, and a certificate of the first UI CC.

9. A first terminal, comprising: Transceiver; The first Universal Integrated Circuit Card (UI CC); as well as a controller configured to: receive an input to transfer a configuration file installed in the first terminal; Deleting the configuration file from the first UI CC; generating data including information indicating deletion of the configuration file and an address of a configuration file server for the second terminal to download the configuration file; and outputting the data as information obtainable by a second terminal, The data is used for the second terminal to obtain the configuration file.

10. The first terminal of claim 9, wherein the data corresponds to an access token of an activation code, and Among the available information is a Quick Response (QR) code in a format corresponding to the activation code. 11 . The first terminal according to claim 9 , wherein the data comprises at least one of: identification information about the profile and a certificate of the first UI CC.

12. A second terminal, comprising: Transceiver; Second Universal Integrated Circuit Card (UI CC); as well as A controller, the controller being configured to: obtain data including information about a profile deleted from a first UI CC of a first terminal; transmit a first message including identification information about the profile and deletion information about the profile to a profile server based on the data; receive metadata about the profile based on the identification information about the profile and the deletion information about the profile; transmit a second message including a download request for the profile to the profile server based on the metadata; and download the profile from the profile server.

13. The second terminal according to claim 12, wherein the first message further includes signature information about the first UI CC and signature information about the second UI CC of the second terminal, wherein said data corresponds to an access token of an activation code, wherein the data is obtained from a Quick Response (QR) code of a format corresponding to the activation code, and The data includes at least one of the following: identification information about the configuration file, an address of a configuration file server for the second terminal to download the configuration file, indication information indicating deletion of the configuration file, and a certificate of the first UI CC.

14. A configuration file server, comprising: Transceiver; and A controller configured to: receive a first message from a second terminal, the first message including identification information about a configuration file deleted from the first terminal and deletion information about the configuration file; generate metadata about the configuration file based on the identification information about the configuration file and the deletion information about the configuration file; transmitting the metadata to the second terminal; receiving a second message from the second terminal, the second message including a download request for the configuration file; and transmitting the configuration file to the second terminal.

15. The configuration file server according to claim 14, wherein the second terminal obtains identification information about the deleted configuration file and deletion information about the configuration file from the first terminal, The first message further includes signature information about a first UI CC of the first terminal and signature information about a second UI CC of the second terminal, where data corresponds to the access token of the activation code, wherein the data is obtained from a Quick Response (QR) code of a format corresponding to the activation code, and The data includes at least one of the following: identification information about the configuration file, an address of a configuration file server for the second terminal to download the configuration file, indication information indicating deletion of the configuration file, and a certificate of the first UI CC.

Images