Method and apparatus for authenticating user when changing device

By sending device change request message to the configuration file server and verifying the confirmation code hash information, the management and downloading problems of embedded UICC configuration files between different terminals are solved, and efficient mobile communication service switching and cost reduction are achieved.

CN118901251APending Publication Date: 2024-11-05SAMSUNG ELECTRONICS CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380018914.8
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-06-14
Filing Date
2023-01-27
Publication Date
2024-11-05

AI Technical Summary

Technical Problem

The prior art is difficult to efficiently manage and download embedded UICC configuration files in mobile communication systems, resulting in inconvenience when users switch mobile communication services between different terminals, and problems of insufficient services and high fees.

Method used

By sending device change request message to the configuration file server, receiving and verifying confirm code hash information, and generating and sending confirm code hash information, downloading and installing configuration files between different terminals can be realized.

Benefits of technology

It realizes efficient download and installation of configuration files in mobile communication systems, solves the inconvenience of users when switching mobile communication services between different terminals, reduces the problems of insufficient services and high costs, and ensures the security and correctness of configuration files. .

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118901251A_ABST
    Figure CN118901251A_ABST
Patent Text Reader

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. The present disclosure relates to a method and apparatus for reinstalling a configuration file when changing an eUICC terminal. A method performed by a first terminal in a wireless communication system supporting device change comprises the steps of: transmitting a device change request message for device change for a configuration file of the first terminal to a configuration file server; receiving a device change request response message from the profile server, the device change request response message including an acknowledgement code requirement indicator for the device change; acknowledgement of receipt of an acknowledgement code input based on an acknowledgement code requirement indicator for the device change; generating acknowledgement code hash information based on the acknowledgement code; and transmitting a device change acknowledgement message including the acknowledgement code hash information to the profile server.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present disclosure relates to a method and device for installing and managing an eUICC profile. Background Art

[0002] 5G mobile communication technology defines a wide frequency band, making high transmission rates and new services possible, and can be implemented not only in "sub 6GHz" frequency bands such as 3.5GHz, but also in "above 6GHz" frequency bands (including 28GHz and 39GHz) called millimeter waves. In addition, 6G mobile communication technology (called super 5G system) has been considered to be implemented in terahertz frequency bands (such as 95GHz to 3THz bands) in order to achieve a transmission rate fifty times faster than 5G mobile communication technology and an ultra-low latency that is one-tenth of 5G mobile communication technology.

[0003] In the initial stage of 5G mobile communication technology, in order to support services and meet performance requirements related to enhanced mobile broadband (eMBB), ultra-reliable and low-latency communication (URLLC), and massive machine type communication (mMTC), standardization of the following technologies is underway: beamforming and massive MIMO for alleviating radio wave path loss in millimeter waves and increasing radio wave transmission distance, parameter sets for dynamic operation of efficient utilization of millimeter wave resources and time slot formats (e.g., operating multiple subcarrier spacings), initial access technology for supporting multi-beam transmission and broadband, definition and operation of BWP (bandwidth part), new channel coding methods (such as LDPC (low-density parity check) codes for large-capacity data transmission and polarization codes for highly reliable transmission of control information), L2 preprocessing, and network slicing for providing dedicated networks dedicated to specific services.

[0004] Currently, in view of the services supported by 5G mobile communication technology, discussions are underway on improvements and performance enhancements of initial 5G mobile communication technology, and there is physical layer standardization on the following technologies, such as vehicle-to-everything (V2X) for assisting driving decisions by autonomous vehicles based on information about the location and status of the vehicle transmitted by the vehicle and for improving user convenience, new radio unlicensed (NR-U) for system operation designed to comply with various regulatory requirements in unlicensed bands, NR UE power saving, and non-terrestrial network (NTN) as UE-satellite direct communication for ensuring coverage and positioning in areas where terrestrial network communications are not available.

[0005] In addition, the wireless interface architecture / protocol area is being standardized for technologies such as Industrial Internet of Things (IIoT) for supporting new services through interworking and integration with other industries, IAB (Integrated Access and Backhaul) for providing nodes for network service area extension by supporting wireless backhaul links and access links in an integrated manner, mobility enhancement including conditional handover and DAPS (Dual Active Protocol Stack) handover, and two-step random access (2-step RACH for NR) for simplifying the random access process. System architecture / services for technologies such as 5G baseline architecture (e.g., service-based architecture or service-based interface) for combining network function virtualization (NFV) and software defined network (SDN) technologies, and mobile edge computing (MEC) for receiving services based on UE location are also being standardized.

[0006] If such a 5G mobile communication system is commercialized, the already exponentially growing number of connected devices will be connected to the communication network, and it is therefore expected that there will be a need to enhance the functions and performance of the 5G mobile communication system and the integrated operation of the connected devices. To this end, new research is planned related to the following technologies: extended reality (XR) for effectively supporting AR (augmented reality), VR (virtual reality), MR (mixed reality), etc., as well as 5G performance improvement and complexity reduction by utilizing artificial intelligence (AI) and machine learning (ML), AI service support, virtual world service support, and drone communication.

[0007] In addition, such developments in 5G mobile communication systems will serve as a foundation for developing new waveforms for providing coverage in the terahertz band for 6G mobile communication technology, multi-antenna transmission technologies such as full-dimensional MIMO (FD-MIMO), array antennas, and large antennas, metamaterial-based lenses and antennas for improving the coverage of terahertz band signals, high-dimensional spatial multiplexing technology using OAM (orbital angular momentum), RIS (reconfigurable smart surface), full-duplex technology for increasing the frequency efficiency of 6G mobile communication technology and improving system networks, AI-based communication technology for achieving system optimization by utilizing satellites and AI (artificial intelligence) from the design stage and internalizing end-to-end AI support functions, and next-generation distributed computing technology for implementing services at a complexity level that exceeds the limits of UE operating capabilities by utilizing ultra-high-performance communication and computing resources.

[0008] With the development of wireless communication systems as described above, various services can be provided, and thus a way of efficiently providing these services is required.

[0009] "Universal Integrated Circuit Card (UICC)" is a smart card inserted into a mobile communication terminal to be used, and is also called a UICC card. The UICC may include an access control module, through which the terminal accesses the network of a mobile communication service provider. The access control module may 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 module is generally referred to as a SIM card.

[0010] Among UICC cards, a UICC that is fixed to a terminal and used is called an embedded UICC (eUICC). Generally speaking, an eUICC is a UICC that is fixed to a terminal to be used and that can remotely download and select a SIM module. In addition, the downloaded SIM module information is called an eUICC profile or more simply a profile. Summary of the invention

[0011] Technical issues

[0012] Embodiments of the present disclosure provide a method and apparatus for efficiently providing services in a mobile communication system.

[0013] According to an embodiment of the present disclosure, an aspect of the present disclosure is to provide a method and device for a terminal to select a communication service and connect to a network in a communication system.

[0014] According to another embodiment of the present disclosure, another aspect of the present disclosure is to provide a method and device for a terminal to download, install and manage a configuration file in a communication system for online connection to a network.

[0015] According to another embodiment of the present disclosure, another aspect of the present disclosure is to provide a method and apparatus in which a terminal can efficiently download a configuration file installed to connect to a network to another terminal again in a communication system.

[0016] The technical subject matter claimed 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.

[0017] Problem Solution

[0018] According to the present disclosure, in order to solve the problem, a method performed by a first terminal in a wireless communication system supporting device change includes: sending a device change request message for a device change for a profile of the first terminal to a profile server; receiving a device change request response message from the profile server, the device change request response message including a confirmation code required indicator for the device change; identifying reception of a confirmation code input based on the confirmation code required indicator for the device change; generating confirmation code hash information based on the confirmation code; and sending a device change confirmation message including the confirmation code hash information to the profile server.

[0019] According to the present disclosure, in order to solve the problem, a method performed by a profile server in a wireless communication system supporting device change includes: receiving a device change request message for a device change for a profile of the first terminal from a first terminal; receiving a confirmation code from a service provider; sending a device change request response message to the first terminal based on the confirmation code, the device change request response message including a confirmation code required indicator for the device change; receiving a device change confirmation message including confirmation code hash information from the first terminal; and determining a result of the device change request based on the received confirmation code hash information.

[0020] According to the present disclosure, in order to solve the problem, a first terminal in a wireless communication system supporting device change includes a transceiver and a controller, the transceiver is configured to send and receive signals. The controller is connected to the transceiver and is configured to: send a device change request message for device change for a configuration file of the first terminal to a configuration file server; receive a device change request response message from the configuration file server, the device change request response message including a confirmation code requirement indicator for device change; identify the reception of a confirmation code input based on the confirmation code requirement indicator for device change; generate confirmation code hash information based on the confirmation code; and send a device change confirmation message including the confirmation code hash information to the configuration file server.

[0021] According to the present disclosure, in order to solve the problem, a profile server in a wireless communication system supporting device change includes a transceiver and a controller. The transceiver is configured to send and receive signals. The controller is connected to the transceiver and is configured to: receive a device change request message for a device change for a profile of the first terminal from a first terminal; receive a confirmation code from a service provider; send a device change request response message to the first terminal based on the confirmation code, the device change request response message including a confirmation code requirement indicator for the device change; receive a device change confirmation message including confirmation code hash information from the first terminal; and determine the result of the device change request based on the received confirmation code hash information. According to the present disclosure, in order to solve the problem, a method for processing a control signal in wireless communication includes: receiving a first control signal sent from a base station; processing the received first control signal; and sending a second control signal generated based on the processing to the base station.

[0022] Advantageous Effects of the Invention

[0023] According to the embodiments of the present disclosure, services can be effectively provided in a mobile communication system.

[0024] According to an embodiment of the present disclosure, when a terminal desires to install a configuration file installed in the terminal in another terminal in a communication system, the terminal may issue an activation code required for reinstalling the configuration file from a configuration file server, or may receive a configuration file move request result from a configuration file server. If necessary, when there is a configuration file move request, a confirmation number of a character string for user authentication may be further sent to the configuration file server; if necessary, the configuration file to be moved may be deleted first; configuration file deletion evidence capable of verifying the deletion of the configuration file may be transmitted to the server; an activation code or a configuration file move result may be transmitted to another terminal; and another terminal may be allowed to effectively download the configuration file from the configuration file server and install the configuration file.

[0025] According to another embodiment of the present disclosure, the profile server may receive a request from a terminal in the communication system to reinstall a profile installed in the terminal in another terminal. If necessary, a request to identify that the profile can be moved may be sent to the operator; if necessary, a request for a confirmation code or character string for user authentication may be issued to the terminal; if necessary, a request to delete the profile may be issued to the terminal; if necessary, a request to send profile deletion evidence may be issued; if necessary, the prepared profile may be configured to a state that cannot be downloaded; if necessary, an activation code for downloading the prepared profile may be generated; when the terminal deletes the profile, the profile may be changed to a state that can be downloaded; and the profile may be downloaded safely by preventing copying of the profile and errors in the terminal.

[0026] Advantageous effects obtainable from the present disclosure may not be limited to the above-mentioned effects, and other effects not mentioned may be clearly understood by those skilled in the art to which the present disclosure relates through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0027] Figure 1 A method for a terminal to access a mobile communication network using a Universal Integrated Circuit Card (UICC) equipped with a fixed profile according to an embodiment of the present disclosure is illustrated.

[0028] Figure 2 A configuration of a system in which a terminal manages a configuration file installed in a first terminal and installs the configuration file in a second terminal according to a user input according to an embodiment of the present disclosure is shown.

[0029] Figure 3 An example of a process between a first terminal, a second terminal, and a server for allowing the second terminal to download a configuration file according to an embodiment of the present disclosure is shown.

[0030] Figure 4 is a block diagram illustrating elements of a terminal according to an embodiment of the present disclosure.

[0031] Figure 5 is a block diagram illustrating elements of a profile server according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0032] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the accompanying drawings.

[0033] In the process of describing the embodiments, descriptions related to technical contents well-known in the relevant field 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.

[0034] 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 corresponding drawings, the same or corresponding elements have the same reference numerals.

[0035] By reference to the embodiments described in detail below in conjunction with the accompanying drawings, the advantages and features of the present disclosure and their implementation will be 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 appended claims. Throughout the present disclosure, the same or similar reference numerals represent the same or similar elements.

[0036] In this article, it should 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 realizing the function specified in one or more flowchart frames. These computer program instructions can also be stored in a computer-available or computer-readable memory, which can instruct the computer or other programmable data processing device to operate in a particular manner, so that the instructions stored in the computer-available or computer-readable memory produce an article including an instruction device, which implements the function specified in the 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 realizing the function specified in one or more flowchart frames.

[0037] In addition, each box in the flowchart diagram may 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 embodiments, the functions mentioned in the box may not occur in order. For example, depending on the functionality involved, two boxes shown in succession may actually be executed roughly at the same time, or these boxes may sometimes be executed in reverse order.

[0038] As used in the embodiments of the present disclosure, "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 limited to software or hardware. "Unit" can be configured to be stored in an addressable storage medium or to execute one or more processors. Therefore, "unit" includes, for example, software elements, object-oriented software elements, class elements or task elements, processes, functions, attributes, procedures, subroutines, program code segments, drivers, firmware, microcodes, circuits, data, databases, data structures, tables, arrays and parameters. The elements and functions 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, elements and "units" can be implemented to reproduce one or more CPUs in a device or a secure multimedia card.

[0039] Specific terminologies used in the following description are provided only to help understanding of the present disclosure, and other types of terminologies may be used without departing from the technical idea of ​​the present disclosure.

[0040] In the present disclosure, a 'Universal Integrated Circuit Card (UICC)' is a smart card inserted into a mobile communication terminal to be used, and is also referred to as a UICC card.

[0041] UICC is a chip that stores personal information such as network access authentication information of mobile communication service providers, phone number lists, and SMS information, and performs subscriber authentication and service security key generation when connecting to mobile communication networks such as GSM, WCDMA, LTE, etc., making it possible to use mobile communications stably.

[0042] The UICC may include a communication application or access control module, through which the terminal accesses the network of a mobile communication service provider. The communication application or access control module may include a Universal Subscriber Identity Module (USIM), a Subscriber Identity Module (SIM), and an IP Multimedia Service Identity Module (ISIM). In addition, the UICC may provide more advanced security functions for installing various applications such as electronic wallets, ticketing, electronic passports, etc.

[0043] A UICC including a USIM is generally referred to as a USIM card. Similarly, a UICC including a SIM module is generally referred to as a SIM card.

[0044] In the present disclosure, "SIM card", "UICC card", "USIM card" and "UICC including ISIM" may have the same meaning. That is, the present disclosure may be equally applied to a SIM card, a USIM card, an ISIM card or a universal UICC card.

[0045] The SIM card stores private information of a mobile communication subscriber, and authenticates the subscriber and generates a service security key during access to a mobile communication network, thereby making it possible to stably use mobile communications.

[0046] In general, a SIM card is manufactured as a card dedicated to a specific mobile communication service provider according to a request of a corresponding service provider, and is issued together with authentication information for network access of the corresponding service provider, for example, a Universal Subscriber Identity Module (USIM) application, an International Mobile Subscriber Identity (IMSI), a K value, and an OPc value installed therein in advance. Therefore, the corresponding mobile communication service provider receives the delivery of the SIM card to provide it to the subscriber, and then performs management, such as installing, modifying, and deleting applications in the UICC using an over-the-air (OTA) technology as needed. The subscriber can use the network and application services of the corresponding mobile communication service provider by inserting the UICC card into the subscriber's mobile communication terminal. In addition, after changing the terminal, the subscriber can still use the authentication information, mobile communication phone number, and personal phone book stored in the UICC card via the new terminal by inserting the UICC card of the conventional terminal into the new terminal.

[0047] However, the SIM card may cause inconvenience to the user of the mobile communication terminal when receiving services from another mobile communication service provider. The user of the mobile communication terminal may feel inconvenienced when physically obtaining the SIM card in order to receive services from the mobile communication service provider. For example, when traveling to another country, the user must obtain a local SIM card in order to receive local mobile communication services, which causes inconvenience to the user. Roaming services can slightly solve this inconvenience, but if there is no contract between mobile operators, there will still be problems of high costs and insufficient services.

[0048] At the same time, when the SIM module is downloaded and installed in the UICC card remotely, this inconvenience can be solved to a large extent. That is, the user can download the SIM module of the mobile communication service that the user expects to use to the UICC card at the time point desired by the user. The UICC card can download and install multiple SIM modules, select only one of the SIM modules and use the selected SIM module. The UICC card may be fixed or not fixed to the terminal. In particular, the UICC fixed to the terminal and used is called an embedded UICC (eUICC). In general, an eUICC is a UICC card that can be fixed to a terminal to be used and remotely download and select a SIM module. In the present disclosure, a UICC card that can remotely download and select a SIM module is referred to as an eUICC. That is, among the UICC cards that can remotely download and select SIM modules, UICC cards are collectively referred to as eUICCs, regardless of whether they are fixed to the terminal. In addition, the downloaded SIM module information is collectively referred to as an eUICC profile or more simply a profile.

[0049] In the present disclosure, "embedded UICC, ie, eUICC" is a chip-shaped security module embedded in a terminal, rather than a detachable module that can be inserted into and removed from a terminal. The eUICC can download and install a configuration file using an over-the-air (OTA) technology. The eUICC can be referred to as a UICC that is capable of downloading and installing a configuration file.

[0050] In the present disclosure, the method of downloading and installing a configuration file to an eUICC using OTA technology can 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.

[0051] In the present disclosure, “UICC” may be used interchangeably with “SIM”, and “eUICC” may be used interchangeably with “eSIM”.

[0052] In the present disclosure, a “profile” may mean a package of an application, a file system, an authentication key, etc. stored in a UICC in a software format.

[0053] In the present disclosure, a 'USIM profile' may have the same meaning as a 'profile', or may mean an information package in a USIM application incorporated in a profile in a software format.

[0054] In the present disclosure, the operation of enabling a profile by a terminal may be an operation of changing the state of the corresponding profile to an enabled state and allowing the terminal to receive communication services through a communication service provider that provides the corresponding profile. A profile in an enabled state may be expressed as an "enabled profile".

[0055] In the present disclosure, the operation of disabling a configuration file by a terminal may be an operation of changing the state of the corresponding configuration file to a disabled state and preventing the terminal from receiving communication services through a communication service provider that provides the corresponding configuration file. A configuration file in a disabled state may be expressed as a "disabled configuration file".

[0056] In the present disclosure, the operation in which the terminal deletes a configuration file may be an operation of changing the state of the corresponding configuration file to a deleted state and preventing the terminal from enabling or disabling the corresponding configuration file again. The configuration file in the deleted state may be expressed as a "deleted configuration file".

[0057] In the present disclosure, the operation of enabling, disabling or deleting a configuration file by a terminal may be to first make the state of each configuration file a to-be-enabled state, a to-be-disabled state or a to-be-deleted state without immediately changing the state of each configuration file to an enabled state, a disabled state or a deleted state, and then change the state of each configuration file to an enabled state, a disabled state or a deleted state by the terminal or the UICC of the terminal. The operation of marking a specific configuration file as a to-be-changed state (i.e., a to-be-enabled state, a to-be-disabled state or a to-be-deleted state) is not necessarily limited to marking one configuration file as one to-be-changed state, and one or more configuration files may be marked as the same or different to-be-changed states, one configuration file may be marked as one or more to-be-changed states, or one or more configuration files may be marked as the same or one or more different to-be-changed states.

[0058] When the terminal marks one or more states to be changed of a predetermined configuration file, the marks of the two states to be changed can be integrated into one state. For example, when the predetermined configuration file is marked as a state to be disabled and a state to be deleted, the corresponding configuration file can be marked as a state to be disabled and deleted.

[0059] In addition, the operation in which the terminal displays the state to be changed of one or more configuration files can be performed sequentially or simultaneously. In addition, the operation in which the terminal displays the state to be changed of one or more configuration files and then actually changes the state of the configuration files can be performed sequentially or simultaneously.

[0060] In the present disclosure, a "profile provisioning server" may include a function of generating a profile, encrypting a generated profile, generating a profile remote management command, or encrypting a generated profile remote management command. The profile provisioning server may be expressed as a subscription manager data preparation (SM-DP), a subscription manager data preparation plus (SM-DP+), an off-card entity of a profile domain, a profile encryption server, a profile generation server, a profile server, a profile provider (PP), a profile provider, and a profile provisioning credential (PPC) holder.

[0061] In the present disclosure, a "profile management server" may include a function of managing a profile. The profile management server may be expressed as a subscription manager secure routing (SM-SR), a subscription manager secure routing plus (SM-SR+), an off-card entity of an eUICC profile manager, a profile management credential (PMC) holder, an eUICC manager (EM), or a profile manager (PP).

[0062] In the present disclosure, the profile provisioning server may be an entity that also has the functionality of a profile management server. Therefore, in various embodiments of the present disclosure, the operation of the profile provisioning server may be performed by the profile management server. Similarly, the operation of the profile management server or SM-SR may be performed by the profile provisioning server.

[0063] In the present disclosure, a "subscription relay server" may be expressed as a subscription manager discovery service (SM-DS), a discovery service (DS), a root SM-DS, or an alternative SM-DS. A subscription relay server may receive an event registration request (register event request or event registration request) from one or more profile provisioning servers or subscription relay servers. In addition, one or more subscription relay servers may be used together, in which case the first subscription relay server may receive an event registration request not only from the profile provisioning server but also from the second subscription relay server.

[0064] In the present disclosure, the profile provisioning server and the subscription relay server may be collectively referred to as a “Remote SIM Provisioning (RSP) Server.” The RSP server may be expressed as a Subscription Manager (SM)-XX.

[0065] In the present disclosure, "terminal" may be referred to as a mobile station (MS), a user equipment (UE), a user terminal (UT), a wireless terminal, an access terminal (AT), a terminal, a subscriber unit, a subscriber station (SS), a wireless device, a wireless communication device, a wireless transmission / reception unit (WTRU), a mobile node, a mobile device or other terms. In an embodiment, the terminal may include: a cellular phone, a smart phone with a wireless communication function, a personal digital assistant (PDA) with a wireless communication function, a wireless modem, a portable computer with a wireless communication function, a camera device (such as a digital camera) with a wireless communication function, a game device with a wireless communication function, a home appliance with a wireless communication function for storing and reproducing music, an Internet home appliance capable of wireless Internet access and browsing, and a portable unit or terminal with an integrated combination of the aforementioned functions. In addition, the terminal may include, but is not limited to, a machine-to-machine (M2M) terminal and a machine type (MTC) communication terminal / device. In the present disclosure, the terminal may be referred to as an electronic device.

[0066] In the present disclosure, an "electronic device" may have a UICC capable of downloading and installing a configuration file. When the UICC is not embedded in the electronic device, the UICC physically separated from the electronic device may be inserted into the electronic device and connected to the electronic device. For example, the UICC may be inserted into the electronic device in the form of a card. The electronic device may include a terminal, and in this case, the terminal may be a terminal including a UICC capable of downloading and installing a configuration file. The UICC may be embedded in the terminal, and may also be inserted into the terminal when the terminal and the UICC are separated from each other, and the inserted UICC may be connected to the terminal. A UICC capable of downloading and installing a configuration file may be referred to as, for example, an eUICC.

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

[0068] In the present disclosure, a "profile identifier" may be referred to as a factor that matches a profile ID, an integrated circuit card ID (ICCID), a match ID, an event ID, an activation code, an activation code token, a command code, a command code token, a signed command code, an unsigned command code, an ISD-P, or a profile domain (PD). The profile ID may indicate a unique identifier for each profile. The profile identifier may also include an address of a profile provisioning server (SM-DP+) for indexing the profile. The profile identifier may also include a signature of the profile provisioning server (SM-DP+).

[0069] In the present disclosure, "eUICC ID" may be a unique identifier of an eUICC embedded in a terminal and may be referred to as an EID. In addition, when a provisioning profile is pre-installed in an eUICC, the eUICC ID may be an identifier (profile ID) of a corresponding provisioning profile. In addition, in an embodiment of the present disclosure, when the terminal and the eUICC chip are not separated from each other, the eUICC ID may be a terminal ID. In addition, the eUICC ID may refer to a specific security domain of the eUICC chip.

[0070] In the present disclosure, a "profile container" may be named a profile domain. A profile container may be a security domain.

[0071] In the present disclosure, an "application protocol data unit (APDU)" may be a message through which a terminal is linked to an eUICC. In addition, an APDU may be a message through which a profile provider (PP) or a profile manager (PM) is linked to an eUICC.

[0072] In the present disclosure, "Profile Provisioning Credentials (PPC)" may be a means for performing mutual authentication between a profile provisioning server and an eUICC, encrypting and signing a profile. The PPC may include one or more of a symmetric key, a Rivest-Shamir-Adleman (RSA) authentication certificate and a private key, an elliptic curve cryptography (ECC) authentication certificate and a private key, and a root certificate authority (CA) and an authentication certificate chain. In addition, when the number of profile provisioning servers is plural, different PPCs for a plurality of corresponding profile provisioning servers may be stored in the eUICC and used.

[0073] In the present disclosure, "Profile Management Credentials (PMC)" may be a means for performing mutual authentication between a profile management server and an eUICC, encrypting and signing a profile. The PMC may include one or more of a symmetric key, an RSA authentication certificate and a private key, an ECC authentication certificate and a private key, and a root CA and an authentication certificate chain. In addition, when the number of profile management servers is plural, different PMCs for a plurality of corresponding profile management servers may be stored in the eUICC and used.

[0074] In the present disclosure, "AID" may be an application identifier. This value may be an identifier used to identify different applications within the eUICC.

[0075] In the present disclosure, "event" may be a term that collectively indicates profile download, remote profile management, or other profile or eUICC management / processing instructions. An event may be named a remote SIM provisioning operation (remote SIM provisioning operation or RSP operation) or an event record, and each event may be referred to as data including one or more of the following: an event identifier (event ID or EventID) corresponding thereto, a matching identifier (matching ID or MatchingID), and an address (FQDN, IP address or URL) of a profile provisioning server (SM-DP+) or a subscription relay server (SM-DS) storing the corresponding event, a signature of the profile provisioning server (SM-DP+) or the subscription relay server (SM-DS), or a digital certificate of the profile provisioning server (SM-DP+) or the subscription relay server (SM-DS).

[0076] The data corresponding to the event may be referred to as a "command code". Some or all of the processes using command codes may be referred to as a "command code processing process", a "command code process", or a "local profile assistant application programming interface (LPAAPI)". Profile download may be used interchangeably with "profile installation".

[0077] "Event type" may be used as a term to indicate whether a specific event is a profile download, remote profile management (e.g., deletion, activation, deactivation, change, update, etc.), or may indicate a management / processing command of another profile or eUICC, and may be named as an operation type (OperationType), an operation class (OperationClass), an event request type, an event class, or an event request class. With respect to a predetermined event identifier (EventID or MatchingID), a path through which the terminal obtains the corresponding event identifier (EventID or MatchingID) or a use of the path (EventID source or MatchingID source) may be specified.

[0078] In the present disclosure, "profile package" may be used interchangeably with "profile" or may be used as a term for a data object indicating a specific profile, and may be named as a Profile TLV or a Profile Package TLV. When the Profile Package is encrypted using encryption parameters, the Profile Package may be a Protected Profile Package (PPP) or a Protected Profile Package TLV (PPP TLV). When the Profile Package is encrypted using encryption parameters that can only be decrypted by a specific eUICC, the Profile Package may be a Binding Profile Package (BPP) or a Binding Profile Package (BPP) TLV. The Profile Package TLV may be a data set indicating information for configuring a profile in a tag, length, and value (TLV) format.

[0079] In the present disclosure, "local profile management (LBM)" may be named as profile local management, local management, local management command, local command, local profile management (LPM) package, profile local management package, local management package, local management command package, or local command package. LPM may be used to change the state (enable, disable, or delete) of a specific profile or update the content of a specific profile (e.g., a profile nickname or profile summary information (profile metadata, etc.) through software installed in a terminal. LPM may include one or more local management commands, in which case, depending on the local management command, the profiles subject to the local management command may be the same or different.

[0080] In the present disclosure, "remote profile management (RPM)" may be named profile remote management, remote management, remote management command, remote command, RPM package, profile remote management package, remote management package, remote management command package, or remote command package. RPM may be used to change the state of a specific profile (enable, disable, or delete) or change (update) the content of a specific profile (e.g., a profile nickname or profile summary information (profile metadata). RPM may include one or more remote management commands, in which case, depending on the remote management command, the profiles involved in each remote management command may be the same or different from each other.

[0081] In the present disclosure, a "certificate" or "digital certificate" may be a digital certificate for mutual authentication based on an asymmetric key consisting of a pair of public keys (PK) and secret keys (SK). Each certificate may include one or more public keys (PK), a public key identifier (PKID) corresponding to the corresponding PK, an ID of a certificate issuer (CI) that issued the corresponding certificate, and a digital signature.

[0082] In addition, the "certificate issuer" may be named a certificate issuer, a certificate authority (CA), or a certification authority.

[0083] In the present disclosure, "public key (PK)" and "public key identifier (PKID)" may be used interchangeably to indicate a specific public key, a certificate including a corresponding public key, a portion of a specific public key, a portion of a certificate including a corresponding public key, a value (e.g., hash) of a calculation result of a specific public key, a value (e.g., hash) of a calculation result of a certificate including a corresponding public key, a value (e.g., hash) of a calculation result of a portion of a specific public key, a value (e.g., hash) of a calculation result of a portion of a certificate including a corresponding public key, or a storage space for storing data.

[0084] In the present disclosure, when a certificate (primary certificate) issued by one certificate issuer is used to issue other certificates (secondary certificates) or when a second certificate is used to successively issue a third or higher certificate, the relationship between the corresponding certificates may be named as a certificate chain or a certificate hierarchy. At this time, the CI certificate used to issue the first certificate may be referred to as a root certificate, a top certificate, a root CI, a root CI certificate, a root CA, or a root CA certificate.

[0085] In the present disclosure, "communication service provider (mobile operator)" may indicate a company that provides communication services to a terminal, and may include all business support systems (BSS), operation support systems (OSS), point of sale (POS) terminals, and other IT systems of mobile operators. In the present disclosure, mobile operator is not limited to expressing only one specific company that provides communication services, and may be used to refer to a group or association (or consortium) of one or more companies or a representative representing a corresponding group or association. In addition, in the present disclosure, a mobile operator (OP or Op) may be named as an operator (OP or Op), a mobile network operator (MNO), a mobile virtual network operator (MVNO), a service provider (or SP), or a profile owner (PO), and each mobile operator may configure or receive at least one of the names and / or unique identifiers (object identifiers (OIDs)) of the mobile operator. When a mobile operator refers to a group or association or representative of one or more companies, the name or unique identifier of the predetermined group, association, representative may be a name or unique identifier shared by all companies belonging to the corresponding group or association or all companies cooperating with the corresponding representative.

[0086] In the present disclosure, 'AKA' may indicate Authentication and Key Agreement, and correspond to an authentication algorithm for accessing 3GPP and 3GPP2 networks.

[0087] In the present disclosure, "K" is an encryption key value for the AKA authentication algorithm stored in the eUICC.

[0088] In the present disclosure, “OPc” is a parameter value for the AKA authentication algorithm that may be stored in the eUICC.

[0089] In the present disclosure, "NAA" is a network access application, and may be an application for accessing a network stored in a UICC, such as a USIM or an ISIM. The NAA may be a network access module.

[0090] In the present disclosure, "indicator" may be used to express that a predetermined function, configuration, or operation is not required, or to express the corresponding function, configuration, or operation itself. In addition, in the present disclosure, an indicator may be expressed in various forms, such as a string, an alphanumeric string, an operator indicating true / false (Boolean value - true or false), a bitmap, an array, a flag, etc., and other expressions with the same meaning may be used interchangeably.

[0091] According to an embodiment of the present disclosure, a terminal configured to use an embedded universal integrated circuit card (eUICC) to manage a profile for connecting to a network in a wireless communication system may include a transceiver and at least one processor, wherein the at least one processor is configured to control the terminal to: receive an input of a profile from a user; identify profile moving information; send a message requesting to move the profile to a profile server; if necessary, further send a confirmation number or character string for user authentication to the profile server; receive an activation code or whether an event is registered or whether the profile needs to be deleted from the profile server; delete the profile; send a profile deletion result to the profile server; transmit an activation code or a profile moving request result to another terminal; receive an activation code or a profile moving request result from another terminal; send a message requesting to the profile server by using the activation code; receive a profile package from the profile server; and install the profile package.

[0092] According to an embodiment, a profile server in a wireless communication system configured to provide a terminal with a profile for connecting to a network may include a transceiver and at least one processor, the at least one processor being configured to control the profile server to: receive a profile move request message from a terminal; if necessary, further receive a confirmation number or string for user authentication from the terminal; determine whether the profile can be moved; generate an activation code for downloading the profile or a new profile; configure the prepared profile to be in a state that cannot be downloaded after deleting the profile from the terminal; send the activation code and whether the profile needs to be deleted to the terminal; receive a profile deletion result from the terminal; change the profile to a state that can be downloaded; receive a profile download request message from the terminal; determine whether the profile is in a state that can be downloaded; send an error code when the profile cannot be downloaded; verify the profile deletion result included in the profile download request; and send an error code when the profile deletion result does not exist or the verification fails.

[0093] In the following, reference Figures 1 to 5 The method and device for installing and managing configuration files according to the present disclosure are described.

[0094] Figure 1A mobile communication network connection method of a terminal using a UICC having a profile fixed to the terminal according to an embodiment of the present disclosure is illustrated.

[0095] like Figure 1 As shown, the UICC 120 may be inserted into the terminal 110. For example, the UICC 120 may be removable, or may be embedded in the terminal in advance.

[0096] The fixed profile of the UICC 120 with a fixed profile means that the "access information" for accessing a specific mobile operator is fixed. For example, the access information may be an IMSI as a subscriber identifier, or K or Ki required for authenticating the network together with the subscriber identifier.

[0097] The terminal 110 according to various embodiments may perform authentication with an authentication processing system (e.g., a home location register (HLR)) of a mobile communication service provider through the UICC 120. For example, the authentication process may be an authentication and key agreement (AKA) process. When the authentication is successful, the terminal 110 may use mobile communication services such as phone calls or mobile data through the mobile operator network 130 of the mobile communication system.

[0098] Figure 2 A configuration of a system in which a terminal manages a configuration file installed in a first terminal and installs the configuration file in a second terminal according to a user input according to an embodiment of the present disclosure is shown.

[0099] like Figure 2 As shown, eSIMs 211 and 221 may be installed in terminals 210 and 220, and profiles (not shown) may be installed in the eSIMs 211 and 221. In addition, LPAs 212 and 222 may be installed in the terminals 210 and 220. The eSIMs 211 and 221 may be controlled by the LPAs 212 and 222. The user 200 may control the profiles installed in the eSIMs 211 and 221 of the corresponding terminals through the LPAs 212 and 222.

[0100] The user 200 may receive communication services from a service provider 250 (hereinafter referred to as a "mobile operator" or "operator"). To this end, a configuration file (not shown) of the operator 250 may be installed in the first terminal 210. For example, when the user 200 newly purchases the second terminal 220, the user 200 may try to install the configuration file installed in the first terminal 210 in the second terminal 220.

[0101] The operator 250 may be connected to the first profile server 230 and the second profile server 240, the LPA 212 of the first terminal 210 may be connected to the first profile server 230, and the LPA 222 of the second terminal 220 may be connected to the second profile server 240. At this time, the first profile server 230 and the second profile server 240 may be the same as or different from each other. In addition, when one or more operator servers are included in the configuration, each operator server may be connected to each of the separate profile servers or may be connected to the same profile server. In addition, although Figure 2 A case is shown in which each of the profile servers 230 and 240 is configured as a single server, but according to implementations and embodiments, one or more profile servers (SM-DP+) may be included in the server configuration. As described above, it should be noted that various server configurations may be simply expressed as a single profile server.

[0102] Detailed operations and message exchange processes of the user 200 , the operator 250 , the terminals 210 and 220 , the eSIMs 211 and 221 , the LPAs 212 and 222 , and the profile servers 230 and 240 are described in detail with reference to the following drawings.

[0103] Figure 3 An example of a process between a first terminal, a second terminal, and a server for allowing the second terminal to download a configuration file according to an embodiment of the present disclosure is shown.

[0104] That is to say, Figure 3 The present invention shows a process in which a first terminal issues a request for changing an installed configuration file, that is, in order to change a device to a second terminal through a configuration file server, the configuration file server issues a request for a confirmation code (i.e., a configuration file move confirmation code for configuration file move (confirmation code or confirmation code for device change)) to the first terminal, verifies the configuration file move confirmation code sent by the first terminal, and then prepares a configuration file prepared for the second terminal, and the second terminal downloads the configuration file prepared for configuration file move from the configuration file server.

[0105] exist Figure 3 In, reference Figure 2 The user 200, the first terminal 210, the second terminal 220, the configuration file server 230 and the operator 250 are configured and described. For example, the user 200, the first terminal 210, the second terminal 220, the configuration file server 230 and the operator 250 may correspond to Figure 2 A user 200, a first terminal 210, a second terminal 220, a configuration file server 230 and an operator 250 are shown in FIG.

[0106] refer to Figure 3 In operation 3001, the operator 250 may issue a request to prepare a configuration file for the first terminal 210 to the configuration file server 230. For example, for the request to prepare the configuration file, the operator 250 may sign a contract with the user 200 for the service to be provided to the corresponding configuration file. The user 200 may select a service provided by the operator 250 through the first terminal 210, subscribe to the service from the operator 250, and purchase a configuration file corresponding to the service. According to an embodiment, the operator 250 may issue a request to prepare a configuration file to the configuration file server 230 by using the function of ES2+.DownloadOrder and the function of ES2+.ConfirmOrder. According to an embodiment, the operator 250 may selectively include a confirmation code for downloading the configuration file in the configuration file preparation request. In addition, according to an embodiment, the operator 250 may also selectively include a confirmation code for moving the configuration file (i.e., a configuration file move confirmation code (confirmation code or a confirmation code for device change)) that can be used when the configuration file is moved in the future in the configuration file preparation request. The confirmation code for downloading the configuration file and the configuration file move confirmation code may be a string or an alphanumeric string including one or more numbers or characters. According to an embodiment, the confirmation code for downloading the configuration file and the configuration file moving confirmation code may be the same or different from each other, and the operator 250 may reuse the confirmation code for downloading the configuration file without the configuration file moving confirmation code in order to issue a request to configure the configuration file moving confirmation code to have the same value as the confirmation code for downloading the configuration file. According to an embodiment of the present disclosure, the configuration file moving confirmation code and the confirmation code for downloading the configuration file may be used interchangeably. According to an embodiment, when only the confirmation code is used, the confirmation code may refer to the configuration file moving confirmation code or the confirmation code for downloading the configuration file. In this case, it may be determined whether the confirmation code indicates the configuration file moving confirmation code or the confirmation code for downloading the configuration file based on the overall process of the relevant operation.

[0107] In operation 3001, the profile server 230 may prepare a profile to be transmitted to the first terminal 210. The profile server 230 or the operator 250 may allocate and manage a matching ID corresponding to the prepared profile. When the operator 250 includes a confirmation code for downloading a profile or a profile moving confirmation code in a profile preparation request, the profile server 230 may store the corresponding confirmation code to correspond to the prepared profile. When storing the corresponding confirmation code, the profile server 230 may store the corresponding confirmation code without making any changes or selectively generate and store a hash value of the confirmation code. The hash may use algorithms such as secure hash algorithm (SHA)-0, SHA-1, and SHA-256.

[0108] In operation 3001, the profile server 230 or the operator 250 may generate an activation code for downloading a profile and transmit the activation code to the user 200. The activation code may include at least one of the following: an FQDN of an address of the profile server 230 that prepares the profile, a matching ID corresponding to the prepared profile, a profile download confirmation code requirement indicator (confirmation code requirement flag), and a profile move confirmation code requirement indicator (confirmation code requirement flag for device change). According to an embodiment, the profile download confirmation code requirement indicator and the profile move confirmation code requirement indicator may be used interchangeably. In addition, according to an embodiment, the profile download confirmation code requirement indicator may be used as the profile move confirmation code requirement indicator. According to an embodiment, the profile download confirmation code requirement indicator and the profile move confirmation code requirement indicator may be indicated using the same flag (e.g., the profile download confirmation code requirement indicator (confirmation code requirement flag) of the confirmation code indicator). When the profile download confirmation code is included in the profile preparation request of the operator 250, the profile download confirmation code requirement indicator may be configured as "1" or "true". Furthermore, when the profile move confirmation code is included in the profile preparation request of the operator 250 , the profile move confirmation code required indicator may be configured as “1” or “true”.

[0109] In operation 3001, according to an embodiment, the profile server 230 may selectively register an event corresponding to the prepared profile in a subscription relay server (not shown) that can be accessed by the first terminal 210. The event registered in the subscription relay server (not shown) may include at least one of the FQDN of the address of the profile server 230 that prepares the profile and the matching ID (or event ID) of the prepared profile.

[0110] In operation 3003, the first terminal 210 may download the configuration file prepared by the configuration file server 230 by using an activation code provided by the configuration file server 230 or the operator 250 or an event obtained from a subscription relay server (not shown), and install the configuration file to the eSIM (not shown) of the first terminal 210 (corresponding to Figure 2 211).

[0111] In operation 3005, the user 200 may issue a request for transmitting the first profile to the first terminal 210. To this end, the user 200 may identify information about the first profile (profile metadata) and information that the user of the first profile should know through the first terminal 210. The information about the first profile and the information that the user of the first profile should know may be stored in the first terminal 210 or the first profile.

[0112] The information about the first profile may include, for example, the name or identification of the operator 250 and the profile policy. The information that the user who moves the first profile should know may include, for example, the remaining number of times that the user 250 is allowed to move the profile or the fee paid by the user for moving the profile. According to an embodiment, the first profile information may include content that requires obtaining information about the second terminal 220 to move the profile. The information about the second terminal 220 may selectively include at least one of the following: the ID of the eUICC installed in the second terminal 220, the type allocation code (TAC) of the second terminal 220, and information about a subscription relay server (not shown) supported by the second terminal 220, and the information about the subscription relay server supported by the second terminal 220 may include the FQDN of the address of one or more subscription relay servers and an indicator indicating whether the corresponding subscription relay server supports push notification. In addition, the first profile may store at least one of the addresses of the profile server that the terminal should access for profile movement. The profile server that the terminal should access for profile movement may be, for example, the profile server 230. In addition, the first profile may include a profile move confirmation code required indicator (confirmation code required flag for device change) indicating whether a profile move confirmation code needs to be supplied to the profile server 230 during the profile move request process, and when the profile move confirmation code needs to be supplied to the profile server 230, the corresponding indicator may be configured as "true" or a null value.

[0113] In operation 3007, the first terminal 210 may issue a request for moving the first profile to the profile server 230. Operation 3007 may be performed by using, for example, at least one of an initiation authentication message, an authentication client message, and a transfer request message and / or by further sending an operation type configured as a device change or transfer profile. In operation 3007, the process of issuing the request for moving the first profile may include an operation of transmitting at least a profile ID (ICCID) of the first profile. In addition, the process of issuing the request for moving the first profile may selectively include at least one of the following: an ID of an eUICC installed in the second terminal 220, a type allocation code (TAC) of the second terminal 220, and information about a subscription relay server (not shown) supported by the second terminal 220.

[0114] In operation 3009, the profile server 230 and the operator 250 may identify the possibility of movement of the first profile. For example, operation 3009 may be performed using a profile move confirmation request message (Confirm Device Change Request), through which the profile server 230 issues a request to the operator 250 to confirm whether the profile requested by the first terminal 210 is movable. The profile move confirmation request message may selectively include at least one of the following: a profile ID of the requested first profile, an ID of the eUICC installed in the second terminal 220, and a type allocation code (TAC) of the second terminal 220.

[0115] In operation 3009, the operator 250 that receives the profile move confirmation request message from the profile server 230 may identify the requested profile by using the profile ID and determine whether the corresponding profile can be moved. In addition, when the profile is moved to the second terminal 220, it may be determined whether the profile server 230 can reuse the same profile as the first profile or should prepare a new profile, and the result may be returned to the profile server 230.

[0116] When the corresponding profile is moved, it may be determined whether a profile move confirmation code (or confirmation code) needs to be received from the first terminal 210, and when the corresponding code needs to be received, a profile move code requirement indicator may be returned to the profile server 230. In addition, a new profile move confirmation code may be generated in response to the current profile move request, and the corresponding generated profile move confirmation code may be returned to the profile server 230.

[0117] When the corresponding profile is moved, it may be determined whether it is necessary to receive a profile move confirmation code (or confirmation code) from the first terminal 210, and when it is necessary to receive the corresponding code, a new profile move confirmation code may be generated in response to the current profile move request, and the corresponding generated profile move confirmation code may be returned to the profile server 230. At this time, the profile move confirmation code requirement indicator may not be sent.

[0118] The profile server 230 may store the corresponding confirmation code sent from the operator 250. When storing the corresponding confirmation code, the profile server 230 may store the corresponding confirmation code without any change or selectively generate and store a hash value of the confirmation code. The hash may use algorithms such as secure hash algorithm (SHA)-0, SHA-1, and SHA-256. In addition, the profile server 230 may store the corresponding confirmation code to correspond to at least one of a session identifier (TransactionID) or a first profile ID. The operator 250 may transmit the generated profile move confirmation code to the user 200 via email, text message, or call. When the first profile needs to be deleted from the profile server 230 before the second profile for the second terminal 220 prepared for the move of the first profile is transmitted to the second terminal 220, the operator 250 may return the first profile deletion indicator (delete the old profile) to the profile server 230. In addition, the operator 250 may transmit information that the user who moves the first profile should know to the profile server 250.

[0119] In operation 3009, the possibility of moving the first profile can be determined by the profile server 230 itself without interacting with the operator 250. In this case, the operator 250 can provide the profile server 230 with a configuration for moving the first profile before operation 3001 or 3007, and the profile server 230 can store the configuration. The profile server 230 can identify the requested profile by using the profile ID and determine whether the corresponding profile can be moved. In addition, when the profile is moved to the second terminal 220, it can be determined whether the profile server 230 can reuse the same profile as the first profile or should prepare a new profile. When the corresponding profile is moved, it can be determined whether it is necessary to receive a profile moving confirmation code from the first terminal 210. In addition, a new profile moving confirmation code can be generated in response to the current profile moving request, and a value prepared by the operator 250 or a value identical to the profile download confirmation code for downloading an existing profile can be used. The profile server 230 can transmit the profile moving confirmation code to the user 200 by email, text message or call as needed. Furthermore, it may be determined whether the first profile needs to be deleted from the profile server 230 before transmitting the second profile for the second terminal 220 prepared for the movement of the first profile to the second terminal 220 .

[0120] In operation 3011, the profile server 230 may return the result of the profile move request to the first terminal 210 according to the result of operation 3009. For example, at least one of an authentication client message or a transmission response message may be used. The profile move request result may include a message containing the following items: a profile move confirmation code requirement indicator (a confirmation code requirement flag for device change) configured as a "true" or null value indicating that a profile move confirmation code needs to be sent to the profile server 230 when the current profile is moved, and information that the user who moves the first profile should pay attention to.

[0121] In operation 3013, the first terminal 210 may receive confirmation of the move of the first profile or input of a profile move confirmation code from the user 200. When the information about the first profile stored in the first terminal 210 or the first profile includes a profile move confirmation code requirement indicator (confirmation code requirement flag for device change) configured as "true" or a null value, the first terminal 210 may receive input of the profile move confirmation code. In addition, in operation 3011, when the profile move confirmation code requirement indicator (confirmation code requirement flag for device change) configured as "true" or a null value is included in the profile move request result returned from the profile server 230, input of the profile move confirmation code may be received.

[0122] In operation 3013, the first terminal 210 may selectively generate a hash value of the input profile move confirmation code. The hash may use algorithms such as secure hash algorithm (SHA)-0, SHA-1, and SHA-256. In addition, when generating the hash value of the profile move confirmation code, the first terminal 210 may selectively include and generate at least one of the following values ​​together with the profile move confirmation code or the hash value of the profile move confirmation code.

[0123] -First profile move confirmation result (eg, approval or rejection by user 200)

[0124] -Session Identifier (TransactionID)

[0125] The first profile move confirmation result may be expressed by an integer, for example, 1=granted, 2-rejected and 3=timeout.

[0126] In operation 3013, the first terminal 210 can use the SIM card (not shown) of the terminal (corresponding to Figure 2 212 ) generates a digital signature of the eSIM (not shown) in the hash value of the event registration notification ID.

[0127] In operation 3015, the first terminal 210 may return the first profile move confirmation result to the profile server 230. The first profile move confirmation result may include the generated digital signature of the eSIM and at least one of the generated session identifier, the generated session identifier including at least one of the first profile move confirmation result, the profile move confirmation code, the hash value of the profile move confirmation code, and the profile move confirmation code hash value.

[0128] In operation 3015, the profile server 230 may verify the first profile move confirmation result received from the first terminal 210. When a profile move confirmation code required indicator (confirmation code required flag for device change) configured as "true" or a null value is included in the information about the profile, or during a previous operation, the profile server 230 returns a profile move confirmation code required indicator (confirmation code required flag for device change) configured as "true" or a null value as a profile move request result, the profile server 230 may compare and verify the profile move confirmation code returned by the first terminal or the hash value of the profile move confirmation code with the profile move confirmation code corresponding to the current profile move request stored in the profile server 230. When the hash value of the profile move confirmation code is verified, the profile server 230 may generate a hash value of the profile move confirmation code corresponding to the current profile move request. The hash may use an algorithm such as Secure Hash Algorithm (SHA)-0, SHA-1, and SHA-256. Furthermore, when the stored hash value of the profile move confirmation code is generated, at least one of the following values ​​may be selectively included and generated along with the stored profile move confirmation code or the stored hash value of the profile move confirmation code.

[0129] - A first profile move confirmation result transmitted by the first terminal 210 (eg, approval or rejection by the user 200)

[0130] -Session Identifier (TransactionID)

[0131] The profile server 230 may compare the hash value of the profile move confirmation code received from the first terminal 210 with the hash value of the profile move confirmation code generated by the profile server 230, and prepare a second profile for the second terminal 220 when the hash values ​​are the same.

[0132] In operation 3015, the profile server 230 may prepare a second profile to be transmitted to the second terminal 220. Operation 3015 may be performed using, for example, at least one of a download instruction message, a confirmation instruction message, an rpm instruction message, a release instruction message, and a disposal notification. In addition, the profile server 230 may register an event corresponding to the prepared profile in a subscription relay server (not shown) that the second terminal 220 may access. The profile server 230 may store a second profile and a profile download confirmation code corresponding to the second profile and a hash value of the profile download confirmation code. When the operator 250 indicates the use of the confirmation code in operation 3001 or 3009, the confirmation code may be stored. The confirmation code may be the same as the confirmation code provided by the operator 250 in operation 3001 or 3009.

[0133] In operation 3017, the profile server 230 may return the first profile move request result to the first terminal 210. The first profile move request result may include information for downloading the second profile. The information for downloading the second profile may selectively include at least one of the following: an activation code (AC) corresponding to the second profile, a profile deletion indicator (delete profile flag), an indicator indicating whether to register an event (event registration flag), and a confirmation code requirement indicator (confirmation code requirement flag).

[0134] In operation 3017, the activation code may include the FQDN of the address of the profile server 230 storing the second profile and the event ID (MatchingID) connected to the second profile. In addition, the profile server 230 may include the FQDN of the address of the subscription relay server 270 in which the event has been fully registered in the activation code. In operation 3017, when the event is registered in one or more subscription relay servers (not shown), the profile server 230 may include the FQDN of the address of one or more subscription relay servers or select the FQDN of the address of one subscription relay server and include it in the activation code.

[0135] In operation 3019, the first terminal 210 may notify the user 200 or the second terminal 220 that the second configuration file can be downloaded. For example, the first terminal 210 may transmit the activation code sent in operation 3017 to the second terminal 220. In the example where the first terminal 210 transmits the activation code to the second terminal 220, the first terminal 210 may convert the activation code into a format of an image such as a QR code or a format of a character string, output the converted activation code to the screen, and notify the user 200 that the activation code has been prepared. The user 200 may input the activation code output to the screen of the first terminal 210 into the second terminal 220.

[0136] For example, in operation 3019, the first terminal 210 may output information indicating that the second configuration file has been prepared to the screen or transmit the result directly to the second terminal 220 through a wired connection, Wi-Fi, Bluetooth, or NFC.

[0137] In operation 3021, the second terminal 220 may send a message requesting download of a configuration file to the profile server 230. For example, the configuration file download request in operation 3021 may use a terminal authentication request message (authentication client request), which includes an identifier (eUICC ID or EID) of an eUICC in the second terminal 220 and a matching identifier corresponding to the prepared configuration file. In operation 3021, the profile server 230 may provide the second terminal 220 with a second configuration file corresponding to the matching identifier or the identifier of the eUICC. For example, operation 3021 may also include one or more message exchanges between the second terminal 220 and the profile server 230, and the first message sent by the profile server 230 in reply to the second terminal 220 may be a terminal authentication response message (authentication client response).

[0138] Figure 4 is a block diagram illustrating elements of a terminal according to an embodiment of the present disclosure.

[0139] Each of the terminals described in the present disclosure (the first terminal 210, the second terminal 220, and the terminals mentioned without reference numerals) may correspond to Figure 2 The first terminal 210 and the second terminal 220 may be Figure 2 , and the expressions “first” and “second” are only used to indicate that the corresponding terminals are physically different terminals.

[0140] like Figure 4 As shown, the terminal may include a transceiver 410 and a processor 420. In addition, the terminal may include a UICC 430. For example, the UICC 430 may be inserted into the terminal, or may be an eUICC embedded in the terminal.

[0141] The transceiver 410 may send and receive signals, information, and data to and from a profile server.

[0142] The transceiver 410 according to an embodiment of the present disclosure may send a message requesting to move a profile to a profile server, receive a profile move confirmation code requirement indicator from the profile server, send a profile move confirmation code to the profile server, receive an activation code from the profile server, whether to register an event in a subscription relay server, and whether the profile needs to be deleted, and send a profile deletion result to the profile server.

[0143] The transceiver 410 according to an embodiment of the present disclosure may send a message requesting a configuration file to the configuration file server by using an activation code and receive a configuration file package.

[0144] Meanwhile, the processor 420 is an element for controlling the terminal as a whole. According to various embodiments of the present disclosure, the processor 520 may control the overall operation of the terminal. The processor 420 may be named as a controller. According to an embodiment of the present disclosure, the processor 420 may include at least one processor.

[0145] The processor 420 according to an embodiment of the present disclosure may control the terminal to: receive an input of a profile move request from a user, identify profile move information, send a message of a request to move the profile to a profile server, receive a profile move confirmation code required indicator from the profile server, send a profile move confirmation code to the profile server, receive an activation code from the profile server or whether an event is registered in a subscription relay server and whether the profile needs to be deleted, delete the profile, send a profile deletion result to the profile server, and send an activation code or profile move preparation completion to another terminal.

[0146] The processor 420 according to an embodiment of the present disclosure may control the terminal to: receive an activation code from another terminal, send a message requesting a configuration file to a configuration file server by using the activation code, receive a configuration file package from the configuration file server, and install the configuration file package.

[0147] The UICC 430 according to an embodiment of the present disclosure may download and install a configuration file. In addition, the UICC 430 may manage the configuration file.

[0148] The UICC 430 may operate according to the control of the processor 420 . Alternatively, the UICC 430 may include a processor or a controller for installing a profile, or may have an application installed therein. A part of the application may be installed in the processor 420 .

[0149] At the same time, the terminal may also include a storage unit (not shown), and may store data, such as basic programs, applications, and configuration information for the operation of the terminal. In addition, the storage unit may include a flash memory type, a hard disk type, a multimedia card micro type, a card type memory (e.g., SD memory, XD memory, etc.), a magnetic memory, a disk, an optical disk, a random access memory (RAM), a static RAM (SRAM), a read-only memory (ROM), a programmable read-only memory (PROM), and at least one type of storage medium in an electrically erasable programmable ROM (EEPROM). The processor 520 may perform various operations by using various programs, contents, and data stored in the storage unit.

[0150] Figure 5 is a block diagram illustrating elements of a profile server according to an embodiment of the present disclosure.

[0151] Each of the profile servers described in the present disclosure (the first profile server 230, the second profile server 240, and the servers mentioned without reference numerals) may correspond to Figure 2 The first profile server 230 and the second profile server 240 may be Figure 2 The examples of servers in the embodiment and the expressions “first” and “second” are merely used to indicate that the corresponding profile servers are physically different profile servers.

[0152] refer to Figure 5 , the profile server may include a transceiver 510 and a processor 520 .

[0153] The transceiver 510 may transmit and receive signals, information, and data to and from a terminal, a subscription relay server, or an operator.

[0154] The transceiver 510 according to an embodiment of the present disclosure may receive a configuration file move request message from a terminal, send a configuration file move confirmation code requirement indicator to the terminal, receive a configuration file move confirmation code from the terminal, send a message including an activation code and whether the configuration file needs to be deleted to the terminal, receive a configuration file deletion message from the terminal, receive a configuration file download request message from the terminal, send a configuration file package to the terminal when the configuration file can be downloaded, and send an error code to the terminal when the configuration file cannot be downloaded.

[0155] Meanwhile, the processor 520 is an element for overall control of the profile server. According to various embodiments of the present disclosure, the processor 520 may control the overall operation of the profile server. The processor 520 may be named as a controller. According to an embodiment of the present disclosure, the processor 520 may include at least one processor.

[0156] The processor 520 according to an embodiment of the present disclosure may control the profile server to: receive a profile move request from a terminal, determine whether the profile can be moved, send a profile move confirmation code requirement indicator to the terminal, receive a profile move confirmation code from the terminal, prepare a profile for moving an existing profile, generate an activation code for downloading the profile, configure the status of the prepared profile to a state that cannot be downloaded when the existing profile needs to be deleted, send a message including the activation code and whether the profile needs to be deleted to the terminal, receive a profile deletion result from the terminal, change the profile to a state that can be downloaded, receive a profile download request message from the terminal, determine whether the profile can be downloaded, send a profile package to the terminal when the profile can be downloaded, and send an error code to the terminal when the profile cannot be downloaded.

[0157] Meanwhile, the profile server may further include a storage unit (not shown), and may store data, such as basic programs, applications, and configuration information for the operation of the profile server. In addition, the storage unit may include at least one type of storage medium in a flash memory type, a hard disk type, a multimedia card micro type, a card type memory (e.g., an SD memory, an XD memory, etc.), a magnetic memory, a disk, an optical disk, a random access memory (RAM), a static RAM (SRAM), a read-only memory (ROM), a programmable read-only memory (PROM), and an electrically erasable programmable ROM (EEPROM). The processor 520 may perform various operations by using various programs, contents, and data stored in the storage unit.

[0158] 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.

[0159] 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 being limited to the embodiments set forth herein, but should be defined by the appended claims and their equivalents.

[0160] It should be understood that the embodiments and the terms used therein are not intended to limit the technical features stated herein to specific embodiments, and the present disclosure includes various changes, equivalents and / or alternatives of corresponding embodiments. Regarding the description of the figure, similar reference numerals can be used to specify similar or related elements. Unless absolutely different in context, singular expressions can include plural expressions. As used herein, for example, each of the phrases such as "A or B", "at least one of A and B", "at least one of A or B", "A, B or C", "at least one of A, B and C" and "at least one of A, B or C" can be included in all possible combinations of items enumerated together with the corresponding one in the phrase. As used herein, expressions such as "first", "second", "the first" and "the second" can modify corresponding elements regardless of their order or importance, and can be used to simply distinguish corresponding elements from other elements and do not limit corresponding elements. When an element (e.g., a first element) is referred to as being “coupled with / to another element (e.g., a second element)” or “connected with / to another element” with or without the term “operably” or “communicatively,” the element may be coupled / connected / coupled to / to the other element directly or via another element (e.g., a third element).

[0161] As used in various embodiments of the present disclosure, the term "module" may include a unit implemented in hardware, software, or firmware, and may be used interchangeably with other terms such as "logic," "logic block," "component," or "circuit." A "module" may be a single integrated component adapted to perform one or more functions, or its smallest unit or portion. For example, according to an embodiment, a module may be implemented in the form of an application specific integrated circuit (ASIC).

[0162] Various embodiments of the present disclosure may be implemented as software (e.g., a program), including instructions stored in a storage medium (e.g., an internal memory or an external memory) readable by a machine (e.g., a computer). The machine is a device that can call the stored instructions from the storage medium and operate according to the called instructions, and may include terminals (e.g., a first terminal 210 and a second terminal 220) according to various embodiments of the present disclosure. When the instruction is executed by a processor (e.g., the processor 520 in FIG. 9 or the processor 620 in FIG. 10), the processor may use or not use other components under the control of the processor to perform the function corresponding to the instruction. The instruction may include a code generated or executed by a compiler or a code executable by an interpreter.

[0163] The machine-readable storage medium may be provided in the form of a non-transitory storage medium, wherein the term "non-transitory" simply means that the storage medium is a tangible device and does not include signals (e.g., electromagnetic waves), but this term does not distinguish between data semi-permanently stored in the storage medium and data temporarily stored in the storage medium.

[0164] According to an embodiment, the method according to various embodiments of the present disclosure may be included and provided in a computer program product. The computer program product may be traded between a seller and a buyer as a product. The computer program product may be released in the form of a machine-readable storage medium (e.g., a compact disc read-only memory (CD-ROM)), or may be downloaded via an application store (e.g., PlayStore). TM ) online (e.g., downloading or uploading), or distributed (e.g., downloading or uploading) directly between two user devices (e.g., smart phones). If published online, at least a portion of the computer program product may be temporarily generated or at least temporarily stored in a machine-readable storage medium (such as a memory of a manufacturer's server, an application store's server, or a relay server).

[0165] Each element (for example, module or program) according to various embodiments may include a single entity or multiple entities, some sub-elements in the above-mentioned sub-elements may be omitted, or other sub-elements may be included in various embodiments in addition. Alternatively or additionally, some elements (for example, module or program) may be integrated into a single entity. In this case, the integrated entity may still perform the function performed by each of the corresponding elements before integration in the same or similar manner. According to various embodiments, the operation performed by a module, program or another element may be performed sequentially, in parallel, repeatedly or in a heuristic manner, or one or more of the operations may be performed in different orders or omitted, or one or more other operations may be added.

Claims

1. A method performed by a first terminal in a wireless communication system supporting device change, the method include: Sending a device change request message for device change for a configuration file of the first terminal to a configuration file server; receiving a device change request response message from the profile server, the device change request response message including a confirmation code required indicator for the device change; identifying receipt of a confirmation code input based on the confirmation code required indicator for the device change; Based on the confirmation code, generate confirmation code hash information; as well as A device change confirmation message including the confirmation code hash information is sent to the configuration file server.

2. The method according to claim 1, further comprising: include: receiving a device change confirmation response message from the profile server, the device change confirmation response message including one or more of an activation code or profile deletion information; as well as The activation code for the device change is provided to a second terminal.

3. The method according to claim 1, wherein the device change request message includes at least one of a profile identifier (integrated circuit card identifier ICCID) for the device change, an identifier (embedded universal integrated circuit card identifier EID) of an eUICC installed in the second terminal, or a type allocation code TAC of the second terminal, and The confirmation code hash information is generated to include a session identifier.

4. A method performed by a configuration file server in a wireless communication system supporting device change, the method include: receiving, from a first terminal, a device change request message for a device change for a configuration file of the first terminal; receiving a confirmation code from the service provider; Based on the confirmation code, sending a device change request response message to the first terminal, the device change request response message including a confirmation code required indicator for the device change; receiving a device change confirmation message including confirmation code hash information from the first terminal; as well as Based on the received confirmation code hash information, a result of the device change request is determined. 5 . The method of claim 4 , wherein the result of the device change request is determined based on a comparison between confirmation code-hash information received from the first terminal and stored confirmation code-hash information.

6. The method of claim 5, further comprising, upon determining that the confirmation code-hash information received from the first terminal corresponds to the stored confirmation code-hash information: sending a device change confirmation response message to the first terminal, the device change confirmation response message including at least one of an activation code or configuration file deletion information; and Based on the activation code for the device change, a configuration file download request message sent from a second terminal is received. 7 . The method of claim 4 , further comprising receiving a service provisioning message from the service provider, the service provisioning message including information on whether a new configuration file for the device change is required.

8. The method of claim 4, further comprising sending a second device change confirmation message to the service provider, wherein the device change request message includes at least one of a profile identifier (integrated circuit card identifier ICCID), an identifier of an eUICC installed in the second terminal (embedded universal integrated circuit card identifier EID), or a type allocation code TAC of the second terminal, and Wherein the second device change confirmation message includes at least one of the profile identifier, an identifier of the eUICC installed in the second terminal, or the TAC of the second terminal.

9. A first terminal in a wireless communication system supporting device change, the first terminal include: a transceiver configured to transmit and receive signals; as well as A controller, connected to the transceiver, wherein the controller is configured to: send a device change request message for a device change for a configuration file of the first terminal to a configuration file server; receive a device change request response message from the configuration file server, the device change request response message including a confirmation code required indicator for the device change; Based on the confirmation code required indicator for the device change, identifying receipt of a confirmation code input; based on the confirmation code, generating confirmation code hash information; and sending a device change confirmation message including the confirmation code hash information to the profile server.

10. The first terminal according to claim 9, wherein the controller is further configured to: receive a device change confirmation response message from the profile server, the device change confirmation response message including one or more of an activation code or profile deletion information; and provide the activation code for the device change to the second terminal.

11. The first terminal according to claim 9, wherein the device change request message includes at least one of a profile identifier (integrated circuit card identifier ICCID) for the device change, an identifier (embedded universal integrated circuit card identifier EID) of an eUICC installed in the second terminal, or a type allocation code TAC of the second terminal, and The confirmation code hash information is generated to include a session identifier.

12. A configuration file server in a wireless communication system supporting device change, the configuration file server include: a transceiver configured to transmit and receive signals; as well as A controller, connected to the transceiver, wherein the controller is configured to: receive a device change request message for a device change for a configuration file of the first terminal from a first terminal; receive a confirmation code from a service provider; based on the confirmation code, send a device change request response message to the first terminal, the device change request response message including a confirmation code required indicator for the device change; receiving a device change confirmation message including confirmation code hash information from the first terminal; and determining a result of the device change request based on the received confirmation code hash information.

13. The configuration file server according to claim 12, wherein the controller is configured to: send a device change confirmation response message to the first terminal in a case where it is determined that the confirmation code hash information received from the first terminal corresponds to the stored confirmation code hash information, the device change confirmation response message including at least one of an activation code or configuration file deletion information; and receive a configuration file download request message sent from a second terminal based on the activation code for the device change, and Wherein a result of the device change request is determined based on a comparison between confirmation code-hash information received from the first terminal and stored confirmation code-hash information.

14. The profile server of claim 12, wherein the controller is configured to receive a service provisioning message from the service provider, the service provisioning message including information on whether a new profile for the device change is required.

15. The profile server of claim 12, wherein the controller is configured to send a second device change confirmation message to the service provider, wherein the device change request message includes at least one of a profile identifier (integrated circuit card identifier ICCID), an identifier of an eUICC installed in the second terminal (embedded universal integrated circuit card identifier EID), or a type allocation code TAC of the second terminal, and Wherein the second device change confirmation message includes at least one of the profile identifier, an identifier of the eUICC installed in the second terminal, or the TAC of the second terminal.