EUICC encryption key management method and apparatus for profile provisioning in wireless communication system

Abstract

The present disclosure relates to a 5G or 6G communication system for supporting a higher data transmission rate. The present disclosure discloses a method for provisioning a large number of configuration files for a terminal in a terminal manufacturing plant environment, in which the method acquires key information and index information for configuration file installation, transmits a configuration file request for plant injection including an index ID to a configuration file server, a binding profile package (BPP) and profile installation key information including index information are received from a profile server, the received BPP and profile installation key information are transmitted to a terminal, and an encryption key is selected to decrypt the BPP with reference to an index ID in an eUICC of the terminal.

Description

Technical Field

[0001] The present disclosure relates to a method and apparatus for provisioning a configuration file in a wireless communication system, and more particularly to a method and apparatus for provisioning a plurality of configuration files for a terminal in a wireless communication system. 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 "below 6 GHz" frequency bands such as 3.5 GHz, but also in "above 6 GHz" frequency bands (including 28 GHz and 39 GHz) called millimeter waves. In addition, it has been considered to implement 6G mobile communication technology (called super 5G system) in terahertz frequency bands (e.g., 95 GHz to 3 THz frequency bands) in order to achieve a transmission rate fifty times faster than 5G mobile communication technology and ultra-low latency that is one-tenth of 5G mobile communication technology.

[0003] At the beginning of the development of 5G mobile communication technology, in order to support services and meet the 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 already underway: beamforming and massive MIMO for mitigating radio wave path loss in millimeter waves and increasing radio wave transmission distance; parameter sets supporting dynamic operation for 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 (e.g., LDPC (low-density parity check) codes for large amounts of data transmission and polarization codes for high-reliability 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 on the improvement and performance enhancement of initial 5G mobile communication technology are ongoing, and there is already physical layer standardization on technologies such as: V2X (Vehicle to Everything) for assisting driving decisions of autonomous vehicles based on information about the location and status of the vehicle transmitted by the vehicle and for improving user convenience; NR-U (New Radio Unlicensed) for system operation in compliance with various regulatory requirements in unlicensed bands; NR UE energy saving; Non-Terrestrial Network (NTN), which is UE-satellite direct communication for providing coverage in areas where terrestrial network communications are not available; and positioning.

[0005] In addition, in terms of air interface architecture / protocol, the following technologies are being standardized: Industrial Internet of Things (IIoT), which is used to support new services through interoperability and integration with other industries; IAB (Integrated Access and Backhaul), which is used to provide nodes for network service area expansion by supporting wireless backhaul links and access links in an integrated manner; mobility enhancements including conditional switching and DAPS (Dual Active Protocol Stack) switching; and two-step random access (2-step RACH for NR) to simplify the random access process. In terms of system architecture / services, the following technologies are also being standardized: 5G baseline architecture (e.g., service-based architecture or service-based interface), which is used to combine network function virtualization (NFV) and software-defined network (SDN) technologies; and mobile edge computing (MEC), which is used to receive services based on UE location.

[0006] With the commercialization of 5G mobile communication systems, the number of connected devices, which has been growing exponentially, 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 5G mobile communication systems and the integrated operation of connected devices. To this end, new research related to the following technologies is planned: Extended Reality (XR) for effectively supporting AR (Augmented Reality), VR (Virtual Reality), MR (Mixed Reality), etc.; Improving 5G performance and reducing complexity by utilizing artificial intelligence (AI) and machine learning (ML); AI service support; Metaverse service support and drone communication.

[0007] In addition, such developments in 5G mobile communication systems will serve not only as a basis for developing the following technologies: 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); and RIS (reconfigurable smart surface), but will also serve as a basis for developing the following technologies: 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. Summary of the invention

[0008] Technical issues

[0009] Based on the above discussion, the present disclosure provides a method and apparatus for installing a large number of configuration files in a factory environment of a manufacturer terminal in a wireless communication system.

[0010] Technical Solution

[0011] In the present disclosure, in order to solve the above-mentioned problem, a method performed by a factory in a wireless communication system includes: acquiring encryption key information about a plurality of embedded universal integrated circuit cards (eUICCs) from a first server, wherein the encryption key information includes a one-time public key of the eUICC and an index ID associated with a one-time private key matching the one-time public key of the eUICC; storing the encryption key information about the plurality of eUICCs; transmitting the encryption key information about the plurality of eUICCs to a profile server; receiving a plurality of binding profile packages (BPPs) based on the encryption key information about the plurality of eUICCs from the profile server; and transmitting the eUICC encryption key information and the BPPs matched with the eUICC of a terminal among the plurality of BPPs and the encryption key information about the plurality of eUICCs to a terminal, wherein the eUICC of the terminal is configured to verify a signature of the profile server; and decrypting the BPPs based on the BPPs and the encryption key information about the eUICC to install a profile therein.

[0012] In one embodiment, the method further includes receiving an installation result of the configuration file from the terminal; and transmitting the installation result of the configuration file to a configuration file server.

[0013] In one embodiment, the method further comprises transmitting to a second server a number of profiles associated with an eUICC identifier (EID) and a list of EIDs, wherein the second server is configured to order a plurality of profiles from a profile server based on the number of profiles associated with the eUICC identifier and the list of EIDs.

[0014] In one embodiment, the method further includes loading a configuration file on some or all of the plurality of eUICCs after storing encryption key information related to the plurality of eUICCs, wherein decryption of the BPP is performed by creating a session key based on a one-time private key of the eUICC and an index ID.

[0015] In addition, in another embodiment of the present disclosure, a method performed by a terminal in a wireless communication system includes: receiving from a factory encryption key information about a binding profile package (BPP) and encryption key information about a plurality of embedded universal integrated circuit cards (eUICCs) that matches an eUICC of the terminal among a plurality of binding profile packages (BPPs) and encryption key information about a plurality of eUICCs; verifying a signature of a profile server based on the BPP and the encryption key information about the eUICC; decrypting the BPP when verification of the profile server is completed; and installing a profile by decrypting the BPP, wherein the plurality of BPPs and encryption key information about the plurality of eUICCs are transmitted from a first server to the factory, the encryption key information includes a one-time public key of the eUICC and an index ID associated with a one-time private key that matches the one-time public key of the eUICC; and creating the plurality of BPPs based on the one-time public key of the eUICC.

[0016] In addition, in another embodiment of the present disclosure, a factory in a wireless communication system includes a transceiver capable of transmitting and receiving at least one signal; and a controller coupled to the transceiver, wherein the controller is configured to: acquire encryption key information about a plurality of embedded universal integrated circuit cards (eUICCs) from a first server, wherein the encryption key information includes a one-time public key of the eUICC and an index ID associated with a one-time private key matching the one-time public key of the eUICC; store the encryption key information about the plurality of eUICCs; transmit the encryption key information about the plurality of eUICCs to a profile server; receive a plurality of binding profile packages (BPPs) based on the encryption key information about the plurality of eUICCs from the profile server; and transmit the eUICC encryption key information and the BPP that match the eUICC of a terminal among the plurality of BPPs and the encryption key information about the plurality of eUICCs to a terminal, wherein the eUICC of the terminal is configured to verify a signature of the profile server; and decrypt the BPP based on the BPP and the encryption key information about the eUICC to install the profile therein.

[0017] In addition, in another embodiment of the present disclosure, a terminal in a wireless communication system includes: a transceiver capable of transmitting and receiving at least one signal; and a controller coupled to the transceiver, wherein the controller is configured to: receive from a factory encryption key information about a plurality of binding profile packages (BPPs) and encryption key information about a plurality of embedded universal integrated circuit cards (eUICCs) that matches an eUICC of the terminal and the BPP; verify a signature of a profile server based on the BPP and the encryption key information about the eUICC; decrypt the BPP when the verification of the profile server is completed; and decrypt the BPP to install a profile, wherein the plurality of BPPs and the encryption key information about the plurality of eUICCs are transmitted from a first server to the factory, the encryption key information including a one-time public key of the eUICC and an index ID associated with a one-time private key matching the one-time public key of the eUICC; and create the plurality of BPPs based on the one-time public key of the eUICC.

[0018] Advantageous Effects of the Invention

[0019] The present disclosure may provide a method and apparatus capable of effectively installing a configuration file in a terminal manufacturer's factory environment in a wireless communication system.

[0020] Effects that can be obtained from the present disclosure are not limited to the effects described in the various embodiments, and other effects that are not described will be clearly understood from the following description by those having ordinary skill in the art to which the present disclosure pertains. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] Figure 1 is a block diagram illustrating the relationship between components for provisioning a configuration file according to an embodiment of the present disclosure.

[0022] Figure 2 is a message flow diagram illustrating a method in which an otPK index ID is used and in which factory IT specifies and uses a usage order according to an embodiment of the present disclosure.

[0023] Figure 3 is a message flow diagram illustrating a method in which an otPK index ID is used and in which an eUICC specifies and uses a usage order according to an embodiment of the present disclosure.

[0024] Figure 4 : is a message flow diagram showing another embodiment of a case where an otPK index ID is used and an eUICC specifies and uses a usage order according to an embodiment of the present disclosure.

[0025] Figure 5is a message flow diagram illustrating a method in which an EUM transmits one key material and in which an eUICC specifies the key material to be used at the next reply to Factory IT according to an embodiment of the present disclosure.

[0026] Figure 6 is a message flow diagram illustrating an operation of using an otPK having a usage number or using an otPK indefinitely in an otPK reuse method according to an embodiment of the present disclosure.

[0027] Figure 7 is a block diagram showing the structure of a profile server, factory IT, and a terminal in a wireless communication system according to an embodiment of the present disclosure. DETAILED DESCRIPTION

[0028] Hereinafter, the operating principle of the present disclosure will be described in detail with reference to the accompanying drawings. In the following description, when describing the present disclosure, in the case where it is determined that the detailed description of the relevant well-known functions or structures may unnecessarily obscure the subject matter of the present disclosure, its detailed description will be omitted. The terms described below are defined in consideration of the functions in the present disclosure and may vary according to the intention or customization of the user or operator. Therefore, it should be defined based on the content of the entire specification.

[0029] The advantages and features of the present disclosure and methods for achieving them will become apparent with reference to the embodiments described in detail below in conjunction with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below, but may be implemented in various different forms, and only the embodiments of the present disclosure can make the present disclosure complete and are provided to fully inform the ordinary technicians of the technical field to which the present disclosure belongs of the scope of the present disclosure, and the present disclosure is limited only by the scope of the claims. Throughout the specification, the same reference numerals refer to the same parts.

[0030] In the following, the base station is a subject that performs resource allocation of the terminal, and may be at least one of a gNode B, an eNode B, a node B, a base station (BS), a radio access unit, a base station controller, or a node on a network. The terminal may include a user equipment (UE), a mobile station (MS), a cellular phone, a smart phone, a computer, or a multimedia system capable of performing a communication function. In the present disclosure, a downlink (DL) is a wireless transmission path of a signal transmitted from a base station to a terminal, and an uplink (UL) is a wireless transmission path of a signal transmitted from a terminal to a base station. In the following, although an LTE or LTE-A system may be described as an example, the embodiments of the present disclosure may be applied to other communication systems having similar technical backgrounds or channel forms. For example, a 5G mobile communication technology (5G, new radio (NR)) developed after LTE-A may be included in a system to which an embodiment of the present disclosure may be applied, and the 5G below may be a concept including existing LTE, LTE-A, and other similar services. In addition, the present disclosure may be applied to other communication systems by making some modifications within the scope of not significantly deviating from the present disclosure as determined by a technician with technical knowledge. In this case, it will be understood that each block of the message flow diagram and the combination of message flow diagrams can be executed by computer program instructions.

[0031] Since these computer program instructions can be installed in a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, the instructions executed by the processor of the computer or other programmable data processing device produce a device that performs the functions described in the message flow diagram box. Since these computer program instructions can be stored in a computer-usable or computer-readable memory, the memory can instruct the computer or other programmable data processing device to implement the functions in a specific manner, so the instructions stored in the computer-usable or computer-readable memory can produce a product containing an instruction device for performing the functions described in the message flow diagram box. Since the computer program instructions can be installed on a computer or other programmable data processing device, a series of operating steps are performed on the computer or other programmable data processing device to generate a computer executable process; therefore, the instructions for executing the computer or other programmable data processing device can provide steps for performing the functions described in the message flow diagram box.

[0032] In addition, each box can represent a part of a module, section or code, which includes one or more executable instructions for implementing a specified logical function. In addition, it should also be noted that in some alternative implementations, the functions listed in the box can occur out of order. For example, the two boxes shown one after another can actually be executed substantially at the same time, or the box can sometimes be executed in reverse order according to the corresponding function. In this case, the term "-unit" used in this embodiment indicates a software component or hardware component such as a field programmable gate array (FPGA) or an application-specific integrated circuit (ASIC), and the "-unit" performs a specific role. However, the "-unit" is not limited to software or hardware. The "-unit" can be configured to reside in an addressable storage medium or can be configured to reproduce one or more processors. Therefore, as an example, the "-unit" includes components, such as software components, object-oriented software components, class components and task components, processes, functions, characteristics, procedures, subroutines, program code segments, drivers, firmware, microcodes, circuits, data, databases, data structures, tables, arrays and variables. The functions provided in the components and "-units" can combine fewer components and / or "-units", or can also be divided into additional groups and / or "-units". Furthermore, components and "-units" may be implemented to reproduce one or more CPUs in a device or secure multimedia card. Furthermore, in one embodiment, a "-unit" may include one or more processors.

[0033] In the following, for ease of description, the present disclosure uses terms and names defined in the 5GS and NR specifications, which are standards defined by the Third Generation Partnership Project (3GPP) organization in existing communication standards. However, the present disclosure is not limited to the above terms and names, and can also be applied to wireless communication networks according to other specifications. For example, the present disclosure can be applied to 3GPP 5GS / NR (fifth generation mobile communication standard).

[0034] In the following, for ease of description, the present disclosure uses the terms and names defined in the RSP specifications (SGP.XX series), which are standards defined by the GSM Association (GSMA) in the currently existing eSIM standards. However, the present disclosure is not limited to these terms and names, and can also be applied to eSIMs according to other specifications. A Universal Integrated Circuit Card (UICC) is a smart card inserted and used in a terminal such as a mobile communication terminal, and is also referred to as a UICC card. The UICC may include an access control module for accessing a network of a mobile communication service provider. Examples of such access control modules include a Universal Subscriber Identity Module (USIM), a Subscriber Identity Module (SIM), an Internet Protocol Multimedia Service Identity Module (ISIM), and the like.

[0035] 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. It should be noted that in the following description, the term SIM card may be used in a general sense, including a UICC card, a USIM card, a UICC including an ISIM, and the like. The technology applied to a SIM card may also be applied to a USIM card, an ISIM card, or a general UICC card.

[0036] The SIM card stores personal information of mobile communication subscribers and performs subscriber authentication and traffic security key creation when accessing a mobile communication network to enable secure mobile communication usage.

[0037] SIM cards are usually produced as dedicated cards for specific mobile communication service providers according to the requirements of specific mobile communication service providers when producing SIM cards, and authentication information for network access of the corresponding service provider, such as Universal Subscriber Identity Module (USIM) application and International Mobile Subscriber Identity (IMSI), K value, OPc value, etc., are preloaded on the card before release. Therefore, the produced SIM card is sent to the corresponding mobile communication service provider and provided to the subscriber, and if necessary, the management of installation, modification and deletion of applications in the UICC can also be performed using technologies such as Over the Air (OTA).

[0038] A subscriber can use the network and application services of a corresponding mobile communication service provider by inserting the UICC card into his mobile communication terminal. When changing a mobile communication terminal, a subscriber can use the authentication information, mobile communication phone number, personal phone book, etc. stored in the UICC card intactly in the new mobile communication terminal by moving the UICC card from the existing mobile communication terminal and inserting it into the new mobile communication terminal.

[0039] However, SIM cards are not convenient for mobile terminal users to receive services from other mobile communication companies. Mobile communication terminal users have the inconvenience of having to physically obtain a SIM card in order to receive services from a mobile communication provider. For example, when traveling to another country, in order to receive local mobile communication services, it is inconvenient to obtain a local SIM card. Roaming services solve some of the inconveniences, but there are also problems such as high fees and the inability to receive services without a contract between mobile communication companies.

[0040] In the case where the SIM module is downloaded remotely and installed on the UICC card, this inconvenience can be significantly solved. For example, the SIM module of the mobile communication service that the user wants to use can be downloaded to the UICC card at the desired time point. The UICC card can also download and install multiple SIM modules, and select and use only at least one SIM module therefrom. The UICC card may be fixed or not fixed to the terminal. The UICC fixed and used on the terminal is generally referred to as eUICC, but in the present disclosure, the UICC card that can remotely download and select the SIM module is collectively referred to as eUICC. That is, in the UICC card that can remotely download and select the SIM module, the UICC card fixed to the terminal and the UICC card not fixed to the terminal are collectively referred to as eUICC. In addition, the downloaded SIM module information is collectively referred to as a profile. Examples of profiles can be further classified according to use, such as a provisioning profile (a profile with usage restrictions only for connectivity of the initial configuration), an operation profile (without such usage restrictions), and a test profile (with usage restrictions for testing).

[0041] In order to install the profile in the eUICC, it is generally assumed that the terminal user downloads the profile through a real-time network connection with the profile download server after the terminal is released. At present, according to the remote profile provisioning specification, that is, the eSIM standardization standard defined in the GSMA, such as the remote SIM provisioning standard SGP.21 / 22 for consumer terminals, the remote SIM provisioning standard SGP.31 / 32 for IoT terminals, and the remote SIM provisioning standard SGP.01 / 02 for M2M terminals, the terminal performs a process of connecting to the profile download server in real time through the network, exchanging messages between the terminal and the profile server multiple times, and performing common mutual authentication in this process to download the profile. However, at the time point when the terminal downloads the profile with the profile download server, it may not be possible to assume that the network is always connected. Therefore, in order to solve this problem, a provisioning profile is introduced in SGP.21 / 22, which is a restricted use profile that only provides the terminal with a connection for initial configuration. Therefore, the terminal manufacturer can release an eUICC equipped with a provisioning profile. In addition, the manufacturer can preload the operation profile of the communication service provider without the above-mentioned usage restrictions into the eUICC before releasing the eUICC based on the contract signed with the service provider.

[0042] In addition, after the service profile is first installed in the eSIM terminal in the factory, there may be a situation where the installed profile needs to be changed and re-injected to support release due to reasons such as service order changes or refurbished terminals. The current SGP.XX only creates and uses a one-time encryption key (otPK.EUICC.KA) for the eUICC installed with the profile, and since the eUICC is discarded after the profile is installed, it is impossible to support the release after the profile is re-injected or additionally injected into the eUICC of the terminal in the factory, so the present disclosure aims to solve this problem.

[0043] The GSM Association (GSMA, Telecommunications Operators Association) recently approved a new work item for provisioning profiles in terminals in the factory, and will discuss the standardization of devices and methods for provisioning profiles in terminals in the factory in the form of SGP.41 (Technical Requirements Specification) and SGP.42 (Technical Specification (Planned)).

[0044] In the present disclosure, the function for provisioning a profile in the factory is referred to as a factory profile provisioning (IFPP) function, and in the case of entering a state that supports the corresponding function, it can be expressed as entering an IFPP mode or an IFPP state. Alternatively, an "f" may be additionally added to the end of the name of each entity to indicate that it is operating in the corresponding mode. For example, a specific entity such as a terminal, LPA, eUICC, a profile server, a factory IT, a service provider (SP) server, an eUICC manufacturer (EUM) server, etc. may be an entity that further supports the IFPP mode, or may be an entity that only supports the corresponding function. For example, the SM-DP+ as one of the profile servers may be a server that supports the remote SIM provisioning function for consumers defined in SGP.21 / 22 but also supports some IFPP functions defined in SGP.41 / 42. Alternatively, the SM-DP+ as a profile server may be a profile server that only supports the IFPP function. In the present disclosure, a profile server operating in an IFPP state may be interchangeably expressed as, for example, a profile server f.

[0045] In the present disclosure, a universal integrated circuit card (UICC) is a smart card inserted into a mobile communication terminal and used, and may refer to a chip that stores personal information such as network access authentication information, phonebook, and SMS of a mobile communication subscriber and performs subscriber authentication and traffic security key creation when accessing mobile communication systems such as GSM, WCDMA, LTE, and 5G, thereby achieving secure use of mobile communications. Depending on the type of mobile communication network accessed by the subscriber, the UICC may be loaded with communication applications such as a subscriber identity module (SIM), a universal SIM (USIM), and an IP multimedia SIM (ISIM), and also provides a higher level of security functions for loading various applications such as an electronic wallet, ticketing, and an electronic passport.

[0046] In the present disclosure, the embedded UICC (eUICC) is not limited to a security module built into a terminal, and includes a detachable security module that can be inserted into and removed from a terminal. The eUICC can be downloaded and installed from a server storing a configuration file using an over-the-air (OTA) technology. The eUICC can be referred to as a UICC that can download and install a configuration file.

[0047] The method for downloading and installing a configuration file in an eUICC using OTA technology in the present disclosure can be applied to a detachable UICC that can be inserted into and removed from a terminal as described above. For example, an embodiment of the present disclosure can be applied to a detachable UICC that can download and install a configuration file using OTA technology. In the present disclosure, the eUICC unique identification number (eUICCID) can be referred to as an EID. The UICC mentioned in the present disclosure can be used interchangeably with a SIM, and the term eUICC can be used interchangeably with an eSIM.

[0048] In the present disclosure, a profile may refer to an application, a profile system, an authentication key value, etc. stored in a UICC encapsulated in software form. In addition, a profile may be referred to as access information. In addition, a USIM profile in the present disclosure may refer to information having the same meaning as a profile or information contained in a USIM application in a profile encapsulated in software form. In the present disclosure, a profile package or an encrypted binding profile package (BPP) may be used interchangeably with a profile or as a term for a data object indicating a specific profile, and may be referred to as a profile TLV or a profile package TLV. A profile identifier may be referred to as an integrated circuit card identifier (ICCID), thereby indicating a unique identification number of a profile. In the case of encrypting a profile package using encryption parameters, it may be referred to as a protected profile package (PPP) or a protected profile package TLV (PPP TLV). In the case of encrypting a profile package using encryption parameters that can only be decrypted by a specific eUICC, it may be referred to as a binding profile package (BPP) or a binding profile package TLV (BPP TLV). A profile package TLV may be a data set representing information constituting a profile in a tag, length, and value (TLV) format.

[0049] In the present disclosure, a profile server is a server that can provide the following functions: creating a profile, encrypting the created profile, creating a profile remote management instruction, or encrypting the created profile remote management instruction, or can be a server including the following functions: providing an IFPP mode, or supporting multiple profile activation of a terminal, and can be expressed as subscription manager data preparation (SM-DP), subscription manager data preparation plus (SM-DP+), or subscription manager secure routing (SM-SR).

[0050] The term "terminal" or "device" used in the present disclosure may be referred to as a mobile station (MS), a user equipment (UE), a mobile equipment (ME), 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. Various embodiments of 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, an image capture device with a wireless communication function (such as a digital camera), a game device with a wireless communication function, a music storage and playback device with a wireless communication function, an Internet home appliance capable of wireless Internet access and browsing, and a portable unit or terminal incorporating a combination of such functions. In addition, depending on the performance features supported, the terminal may include a machine-to-machine (M2M) terminal and a machine type communication (MTC) terminal / device and an IoT terminal / device. In the present disclosure, a terminal may be referred to as an electronic device or simply a device. The terminal 120 that provides the function of installing a profile to an eUICC may be referred to as an eSIM terminal.

[0051] In the present disclosure, EUM is an eUICC manufacturer and refers to a manufacturer that produces eUICC and provides personalized eUICC, and the information transmitted by EUM can be transmitted online or offline through a channel between an EUM server or individual components. According to an embodiment of the present disclosure, EUM may refer to an EUM server or a role performed by EUM.

[0052] In the present disclosure, the UE or device may include software or applications installed in the UE or device to control the UICC or eUICC. The software or application may be an application such as a local profile assistant (LPA), a SIM manager, or an IoT profile assistant (IPA). The software or function may be provided in an integrated manner. For example, the LPA and the IPA may be provided as a single integrated application. In the present disclosure, the software or application installed in the UE or device to control the UICC or eUICC may be collectively referred to as LPA.

[0053] In the present disclosure, an application protocol data unit (APDU) may be a message format or message exchanged between a controller in a UE or device and an eUICC. APDU is a pair of commands and responses, and APDU commands and APDU responses are defined in ETSI 102.221 with reference to ISO 7816. As defined in ETSI 102.221, an APDU command has a structure of a command category (CLA), a command (INS), a command parameter 1 (P1), and a command parameter 2 (P2) as a header of the APDU, and Lc (the number of bytes in the command data field), data, and Le (the number of bytes expected in the response to the command) as a body, and an APDU response has a structure of an optional data field, a status byte 1 (SW1), and a status byte 2 (SW2), and a detailed description thereof refers to the ETSI 102.221 specification. An application message transmitted from an LPA or a UE may be transmitted to an eUICC in the form of an APDU, and in this case, the information transmitted may be included in the data of the APDU and transmitted.

[0054] In the present disclosure, AKA may represent Authentication and Key Agreement and may represent an authentication algorithm for accessing 3GPP and 3GPP2 networks. K is an encryption key value for the AKA authentication algorithm stored in the eUICC, and OPc in the present disclosure is a parameter value that may be stored in the eUICC for the AKA authentication algorithm.

[0055] In the present disclosure, NAA is a program applied by a network access application, which may be a program applied by a USIM or ISIM stored in a UICC and used to access a network. NAA may be a network access module.

[0056] In the present disclosure, end-user, user, subscriber and service subscriber may be used interchangeably as a user of a corresponding UE.

[0057] In the present disclosure, factory IT is a device that is responsible for the role of supplying specific data or configuration to the UE during the manufacturing process, and may refer to a module that includes the function of downloading a configuration file to the UE, and also includes the function of obtaining and storing the configuration file from the configuration file server. Factory IT may be used interchangeably with factory IT equipment, factory IT server, factory supply equipment, and factory server, and even if it is expressed as a server below, the factory IT in the present disclosure may also be composed of one or more modules, such as a server that stores data and a UE that plays the role of injecting configuration or data into the eSIM UE.

[0058] In this disclosure, OEM may be used interchangeably with UE manufacturer and manufacturer.

[0059] In the present disclosure, a service provider (SP) may be used interchangeably as a communication service provider, MNO, mobile network provider, service operator, communication company, and SP server, and depending on the embodiment, the service provider may represent a server of the service provider or a role played by the service provider.

[0060] In this disclosure, a server vendor refers to a vendor that operates a profile server, and may refer to a role played by a profile server vendor.

[0061] In the present disclosure, an encryption key is used to cover all encryption and decryption keys. For example, an encryption key may include a private key for encrypting data or a public key for decrypting data, and the public key may be shared in the form of a certificate. The present disclosure provides a method and apparatus for inserting and publishing a configuration file into a UE including an eUICC.

[0062] Specifically, the present disclosure provides a method and apparatus for supporting modification, re-injection, and then release of an installed profile due to a service order change or the like after the service profile is first installed in an eSIM UE in a factory. The meaning of "one-time" in a one-time encryption key is generally used in the industry to indicate that it is only used when one profile is successfully installed. Currently, referring to the SGP.XX series, since only one one-time encryption key (otPK / otSK.EUICC.KA) of the eUICC for profile installation is created and used, and should be discarded when the installation is successful, it is not possible to support modification, re-injection, and release of an installed profile.

[0063] In addition, the present disclosure provides a method and apparatus capable of quickly downloading and installing configuration files in a large number of UEs, which overcomes the difficulty of the process of performing message exchange multiple times in order to quickly inject configuration files into a large number of UEs due to the characteristics of the factory environment, including the process of real-time network connection and mutual authentication between the configuration file server and each UE. In addition, a method for factory IT equipment to provision configuration files in UEs without considering the real-time connection between the configuration file server and the UE may be required, and in particular, a method for transmitting, verifying and installing configuration file encryption keys taking into account the "non-real time" between the configuration file server (e.g., SM-DP+) and the eUICC may be required. In addition, a method is required that takes into account the environment of large-scale provisioning of configuration files in a factory, and in particular, a method and apparatus capable of transmitting information of a large number of configuration files between entities in the process of ordering and preparing configuration files for this purpose may be required.

[0064] According to various embodiments of the present disclosure, UE manufacturers can pre-install and release a large number of profiles in eSIM UEs without real-time connection to a profile server. In addition, UE manufacturers can support changes, re-injections, and releases of installed profiles due to returns, business order changes, etc., thereby effectively managing inventory.

[0065] In addition, according to various embodiments of the present disclosure, since the user can directly access the network by purchasing a UE with a configuration file already installed, the user can solve the inconvenience of having to go to a Wi-Fi or mobile communication network to download the configuration file, thereby increasing user convenience.

[0066] In addition, according to various embodiments of the present disclosure, a communication operator may provide a user with a UE installed with a provisioning profile for downloading an operator's profile or an operation profile for immediately using an operator's network service, thereby improving the convenience of the user in using an eSIM.

[0067] The following embodiments describe the process of injecting and publishing a configuration file in the factory, and it should be noted that at a specific point in time after the configuration file is injected and published in the factory, the UE user can also provision and install the configuration file in a general user environment outside the factory according to the process defined in SGP.21 / 22. That is, the following embodiments describe the provisioning in the factory installation environment, and it should be clear that this does not mean that the configuration file cannot be installed in the general environment after the factory release.

[0068] Figure 1 is a block diagram illustrating the relationship between components for provisioning a configuration file according to an embodiment of the present disclosure.

[0069] refer to Figure 1, the profile server / server provider (hereinafter, may be referred to as a profile server or server provider) 100 may represent at least one of a server including the following functions: creating a profile, storing a created profile, encrypting a created profile, creating a remote profile management (RPM) instruction, and encrypting a created profile remote management instruction, supporting a function of transmitting a created profile to an eSIM UE or other profile storage server, or supporting a function of creating a profile for an IFPP, storing a profile created for an IFPP, or encrypting a profile created for an IFPP. RPM may be collectively referred to as a series of processes in which profile installation, activation, deactivation, deletion, and other functions are performed by instructions transmitted from the profile server 100 to the UE 120. RPM may be requested by a communication provider, a service provider, or an owner of a UE, and the instructions may be created by the profile server 100. The profile server / server vendor 100 may receive a profile ordering request from a service provider (SP) / SP server (hereinafter may be referred to as SP or SP server) 150 and determine whether the request is a request for profile creation for an IFPP, or may combine profile ordering information received from a factory IT server / OEM (hereinafter may be referred to as factory IT, factory server or OEM) 110 or SP / SP server 150 with ordered EID information to map profiles and EIDs, thereby preparing them in the profile server 100. The SP / SP server 150 receives a profile ordering request from the factory IT / server / OEM 110, determines whether the request is a request for an order for provisioning a profile for an IFPP, and inputs the order to the profile server / server vendor 100, thereby enabling the profile server 100 to provide one or more binding profile packages (BPPs) to the factory IT / OEM 110.

[0070] The UE 120 may include an eUICC 140 and a communication modem (not shown). The communication modem may be equipped with one or more baseband processors (hereinafter referred to as baseband) for wireless communication. The UE 120 may provide a function of receiving a BPP created for an IFPP from the factory IT / OEM 110 and installing the BPP into the eUICC 140. The UE 120 may transmit the BPP to the eUICC 140, and may transmit the BPP to the eUICC 140 through the LPA 130 operating with the LPAf, or may not transmit the BPP to the eUICC 140 through the LPA 130. The transmitted corresponding message may be transmitted together with the BPP, or may be transmitted with additional parameters added to the BPP, which will be referred to below. Figures 2 to 6Described in detail in (step 275), (step 375), (step 475), (step 575) or (step 675).

[0071] An example of a method of transmitting a message about the installation of the encryption key information and the BPP to the eUICC 140 using the LPA 130 operating as LPAf may be a method of including the BPP in one or more messages starting with ES10x and transmitting. Alternatively, without transmitting the message through the LPA, the message may be transmitted as data of the APDU (e.g., STORE DATA).

[0072] Although one profile server 100 is shown, there may be a plurality of profile servers 100 , and thus, the factory IT 110 may receive and store BPPs from the plurality of profile servers 100 .

[0073] As described above, the LPA 130 may support the IFPP function using the eUICC control software or application. The LPA 130 may be implemented as a logical function of the UE 120 or the eUICC 140. The LPA 130 operating as the LPAf may receive a profile and additional authentication information for authenticating the profile server 100 from the factory IT 110 and provide them to the eUICC 140, and perform the role of obtaining the profile installation result from the eUICC 140 and transmitting it to the factory IT 110.

[0074] The eUICC 140 may determine whether the request is a request for profile installation in the factory through one or more messages of the ES10x received from the LPA 130 operating in the LPAf or a profile installation message received through an application or software for factory configuration of the factory IT 110 or the UE, and determine to enter the IFPP mode. In the case that the eUICC 140 does not support the IFPP function, the eUICC 140 may return an error and terminate the IFPP process.

[0075] The eUICC 140 may obtain the profile and information for authentication of the profile server 100 from the UE 120, decrypt the profile using the corresponding information, process the installation, and reply the installation result to the component that transmits the corresponding request, that is, the specific application of the UE, or to the LPA 130 operating in the UE as LPAf. In addition, the eUICC 140 may verify the profile server 100 that encrypts the profile, or authenticate the profile server 100 that transmits the message by performing signature verification on the signature component in the received message. The eUICC 140 may include an embedded UICC control authority security domain (ECASD), which is a space for storing credentials required in its security domain, such as a root public key for verifying the certificate issuer of the SM-DP+ certificate of the profile server 100, and a key set of the eUICC manufacturer and the eSIM operating platform. In addition, some functions of the LPA may be implemented.

[0076] The factory IT / OEM 110 is a device that is responsible for the role of provisioning a profile to a UE in a factory, and may be composed of one or more servers or UEs (e.g., PCs). The factory IT / OEM 110 may be a server that acquires predetermined information (including a one-time encryption key) about the corresponding eUICC 140 from an EUM / EUM server (hereinafter may be referred to as EUM or EUM server) 160, or transmits all or part of the acquired information to a profile server / server provider 100, or transmits an EID to be ordered and information for mapping a profile to an SP / SP server 150, or stores received encryption key information and BPP. The factory IT server / OEM 110 may perform at least the following operations: requesting a BPP for injection in the factory from the profile server / server vendor 100, or as a result of the request, obtaining a BPP for installation in the eUICC 140 and data signed by the profile server 100 from the profile server / server vendor 100, storing the received BPP and signed data in the factory IT server 110, selecting a BPP mapped to the EID of the target UE from the received or stored BPPs to install the profile, or transmitting the BPP to the mapped UE during the factory configuration process. Some of the information exchanged between the factory IT server 110 and the profile server 100, the SP server 150, and the EUM 160 may be shared between entities performing corresponding roles (i.e., UE manufacturers, profile server operation vendors, service providers, and eUICC manufacturers) in another online or offline channel form (e.g., email transmission, etc.), rather than transmitting and receiving messages through an interface between servers.

[0077] Since the factory IT / OEM 110 can perform operations performed by the UE manufacturer or the factory IT of the UE manufacturer, as described above, the factory IT / OEM 110 is represented as a single entity in the following figures, but it should be noted that the factory IT / OEM 110 can be composed of multiple devices (e.g., a server or a UE such as a PC). Therefore, for example, it should be noted that the device in the factory IT / OEM 110 that requests the BPP from the profile server / server vendor 100 or provides an interface for obtaining the BPP and the device in the factory IT / OEM 110 at the contact point for injecting the profile from the factory IT / OEM 110 into the UE 120 or obtaining the injected installation result can be the same device or different devices.

[0078] The eUICC manufacturer (EUM) 160 is an eUICC manufacturer and may inject key information of a credential for eUICC authentication into the eUICC 140 to provide a personalized eUICC 140 to a UE manufacturer, or the EUM / EUM server 160 may provide predetermined information including a one-time encryption key on the corresponding eUICC 140 to the OEM / factory IT server 110. In addition, although not shown in the present disclosure, the predetermined information including a one-time encryption key on the corresponding eUICC 140 may be transmitted from the EUM / EUM server 160 to the profile server / server vendor 100 according to a request of the OEM 110.

[0079] The service provider (SP) 150 is a business operator that provides network services using profiles as described above, and the SP / SP server 150 can order profiles for IFPP functions from the profile server / server provider 100 and enable the profile server 100 to create and prepare the ordered profiles.

[0080] Hereinafter, the description of the above-mentioned constituent modules may be applied to the roles and relationships of the modules shown in the figures described later. In addition, in the above-mentioned constituent modules, the order information as the information exchanged between the profile server / server provider 100, the factory IT server / OEM 110, the EUM / EUM server 160, and the SP / SP server 150 may be transmitted in other forms, such as an interface link or email between the servers of each entity.

[0081] Figure 2 is a message flow diagram illustrating a method in which an otPK index ID is used and in which factory IT specifies and uses a usage order according to an embodiment of the present disclosure.

[0082] refer to Figure 2Before releasing the UE, the UE manufacturer may preload the profile into the eUICC in the factory and release the UE, and in this case, the UE manufacturer may provision the profile in one or more UEs, especially for a large number of UEs. This step may be divided into a step (227) of preparing the profile and transmitting the profile to the factory IT / OEM 215, and a step (270) of the factory IT installing the profile in N different eUICCs 225.

[0083] At step 227, a configuration file of the IFPP may be prepared and transmitted to the factory IT / OEM. A UE manufacturer wishing to produce a UE equipped with an eUICC may order M eUICCs through the EUM / EUM server 200, and the EUM 200 may provide (step 230) predetermined information (key material) to the factory IT / OEM 215, the information including encryption key information about the ordered M eUICCs. As key material information provided by the EUM 200, the EUM 200 may include otPK.EUICC.KA for each eUICC, and otPK.EUICC.KA may be transmitted as an eUICC signature value. In addition, as key material information provided by the EUM 200, the EUM 200 may also include an index ID as identification information for identifying otPK.EUICC.KA. The index ID may be transmitted as an eUICC signed or unsigned value. In the case where otPK.EUICC.KA or index ID is transmitted as an eUICC signature value, the EUM may also include the public key of the eUICC and transmit it to the factory IT / OEM 215. The public key may be included in the eUICC certificate and transmitted. In the case where the EUM 200 supports installation of N profiles in the eUICC, N otPK.EUICC.KA and index IDs used to distinguish them may be transmitted to the factory IT / OEM 215.

[0084] The index ID is information mapped to otPK.EUICC.KA, and the eUICC 225 that has received the index ID may transmit the corresponding index ID as information for determining otSK.EUICC.KA for creating a session key. The index ID may be constructed as a value that can distinguish otPK.EUICC.KA, and this may be composed of, for example, a partial value or the entire value of otPK.EUICC.KA, a value created by including part or all of otPK.EUICC.KA, a hash value of a value created by including part or all of otPK.EUICC.KA, a part of the hash value, or a value created by deriving from otPK.EUICC.KA. Alternatively, the index ID may be a number that can specify otPK.EUICC.KA or a value created by including a number that can specify otPK.EUICC.KA. The index ID may be defined in data formats such as integers, strings, and binary. Even if not described in other figures in the present disclosure, the description of the index ID may also be applied in the same manner.

[0085] In the case where the EUM / EUM server 200 receives an order for a configuration file of the IFPP, the EUM / EUM server 200 may provide the eUICC encryption key information required for BPP decryption of each eUICC to the factory IT / OEM 215. Upon receiving the information, the factory IT / OEM 215 may store (step 235) the encryption key information about the ordered M eUICCs in the factory IT server 215.

[0086] Thereafter, at a particular point in time, the factory IT / OEM 215 may determine to load the profile onto some N eUICCs or all M eUICCs ordered from the EUM 200. This may be based on a profile preload release request from a service provider (SP) / SP server 205.

[0087] The factory IT / OEM 215 may transmit (step 240) at least one information of the number of configuration files or the list of EIDs to the SP / SP server 205 so that the SP / SP server 205 can prepare configuration files linked to the EIDs in advance as an additional optional procedure. The SP / SP server 205 may order (step 245) configuration files from the configuration file server / server provider 210. In the case where step 240 has been performed in advance and the EID list exists or the EID list is acquired at a specific time point before, the SP / SP server 205 may include the EID information when ordering the configuration files and request the information from the configuration file server / server provider 210. The SP / SP server 205, the configuration file server / server provider 210, and the factory IT / OEM 215 may share (step 250) information that may specify the corresponding order with each other. The information that may specify the corresponding order may be shared as identification information provided by the SP / SP server 205 or the configuration file server / server provider 210 to the factory IT / OEM 215. For example, the identification information may be at least one of a batch ID and an order ID, an ordered profile list or EID list, information about the start and end numbers of the profile list or EID list, a factory serial number, or information about a manufacturer identification number.

[0088] The factory IT / OEM 215 may request a BPP from the profile server / server vendor 210. When requesting a BPP, the factory IT / OEM 215 may transmit (step 255) to the profile server / server vendor 210 the key information of the eUICC obtained at step 230 corresponding to the eUICC of the corresponding target UE (up to N), where N is the number of UEs to which the SP / SP server 205 is to load the profile. This may be part or all of the key information previously received (at step 230). In the event that the factory IT / OEM 215 receives multiple otPK.EUICC.KA for each eUICC from the EUM / EUM server 200, the factory IT / OEM 215 may select and transmit one of the unused otPK.EUICCs. Depending on whether the index ID was included and received previously (step 230), the transmission (step 255) may be as follows.

[0089] In the case where the index ID is received as signature data, transmit data containing the index ID

[0090] When data containing an index ID is received but received as unsigned data, transmit the data with or without the index ID

[0091] In case the index ID is not received, the factory IT / OEM 215 does not contain the index ID

[0092] The profile server / server provider 210 may combine the collected information in at least one of the following steps: collecting the received profile order information (step 245),

[0093] The profile server 210 receives the link information of the profile EID (step 240), the mutually shared order information (step 250), and the encryption key information of the target eUICC to install the received profile (step 255) to create (step 260) an encrypted profile package, and then provides (step 265) the created profile package and the information about eUICC binding to the factory IT / OEM 215. When the profile server 210 receives the message (step 255) and composes (step 260) a verification and reply message for BPP creation, if the index ID exists, the profile server 210 may further perform the following operations.

[0094] In case the Index ID is received as eUICC signature data, the eUICC signature is verified by including the Index ID.

[0095] • When the Index ID is received as eUICC signed or unsigned data, the Profile Server’s signature is created by including the Index ID.

[0096] Create a signature for the configuration file server by including the index ID as a value or new parameter for the transaction ID.

[0097] The created encrypted configuration file package and each BPP encryption key information may be transmitted (step 265) to the factory IT / OEM 215 in one or more messages, and part or all of the data transmitted in the corresponding message may be provided as signature data.

[0098] In case the index ID is included and transmitted (step 255), the index ID may be included in the signature data and transmitted (step 265). In case the index ID is included or not included and transmitted, otPK.EUICC.KA may be included in the signature data and transmitted (step 265).

[0099] At step 270, the operation of the factory IT 215 to install the profile of the IFPP in the eUICC may be described. This step may be performed for N eUICCs.

[0100] The factory IT / OEM 215 may inject the configuration file into the UE before the UE is released from the factory. To this end, the factory IT / OEM 215 may obtain and store a series of encryption key information required for decrypting the configuration file from the BPP and the eUICC. The series of encryption key information may include a one-time public key of the EUICC (hereinafter referred to as otPK.EUICC.KA). The series of encryption key information may also include an index ID mapped to otPK.EUICC.KA.

[0101] The factory IT 215 may transmit the BPP and a series of encryption key information required for decrypting the profile in the eUICC from the factory to each UE 220 through a wired / wireless network within the factory. The BPP and a series of encryption key information may be included in one or more messages and transmitted to the UE 220. In the case where the otPK.eUICC.KA is included and transmitted, the otPK.eUICC.KA may be included in the signature data from the profile server and received by the UE 220. For example, the otPK.eUICC.KA may be included in the signature data and received as one of the following. This is not limited to the following examples.

[0102] -SK.DPauth.SIG: The profile server's private key for authentication with the profile server

[0103] -SK.DPpb.SIG: Private key used in the profile server for profile binding of the profile server

[0104] -SK.DPxx.SIG: The private key of the configuration file server, where xx is defined to indicate the use of IFFP

[0105] As described above, SK.DPpb.SIG may be a private key of a profile server used for profile binding in the profile server, or may be a private key of a profile server used by the profile server for IFPP. In DPxx.SIG, xx indicating use may be indicated as specific information indicating xx indicating IFPPP use.

[0106] The UE 220 may provide a function of receiving a BPP from the factory IT 215 and injecting the BPP into the eUICC 225 in the IFPP mode. For example, the corresponding UE 220 may operate in the factory supply mode at the time point of receiving the BPP, or the UE 220 may recognize that it should enter the IFPP and initiate the operation at the time point of receiving the BPP. Alternatively, the UE 220 may enter the corresponding mode by an event input into the UE by a factory employee, a configuration value, or recognition of a specific virtual private network (VPN). Entering the IFPP mode by the UI or the configuration value may be provided by limiting the UI not to be displayed to the user in a general environment. The UE 220 may transmit the BPP to the eUICC 225 by the LPAf (not shown) as described above or without the LPAf (not shown) (step 275). As an example of a message transmitted to the eUICC using the LPAf (not shown), the BPP may be included in one or more messages of the ES10x and transmitted. That is, LPAf may include and transmit BPP in a function, for example, ES10f.LoadBPP function for transmitting BPP to eUICC 225, or may include BPP in a separate function, that is, a separate function for transmitting eUICC key information and transmitting otPK.EUICC.KA or / and index ID before calling LoadBPP. This may be, for example, ES10f.prepareLoading function. This may also apply to references later. Figures 2 to 6 In the following, reference will be made to Figures 2 to 6 An embodiment thereof is described.

[0107] The eUICC 225 may receive information that allows identification that the message received by the eUICC 225 from the UE 220 is an operation for IFPP. The eUICC 225 may determine that the profile installation operation is performed for IFPP through the message received from the UE 220 and enter.

[0108] This can be a new function defined for IFPP, an IFPP identifier parameter added to the ES10x message defined in the existing SGP.21 / 22 or SGP.31 / 32, or identification information for factory release that is not included in the (consumer-oriented, M2M-oriented, or IoT-oriented) profile provisioning in a general environment after the release of the UE. For example, it can be one of the values ​​such as factory serial number, batch ID, manufacturer identification information. It is not limited to this.

[0109] As described above, the UE 220 may receive data including otPK.EUICC.KA or index ID from the profile server, and the data including the corresponding otPK.EUICC.KA or index ID may be included and received in data signed by one of the following. This is not limited to the following examples.

[0110] -SK.DPauth.SIG: The profile server's private key used for authenticating the profile server to the profile server

[0111] -SK.DPpb.SIG: The private key of the profile server used for profile binding by the profile server

[0112] -SP.DPifpp.SIG: The profile server's private key used exclusively by the profile server for IFPP

[0113] The UE 220 may transmit the signed data back to the eUICC 225 with or without LPAf. The eUICC 225 verifies the signature of the data received by the profile server 210, and as described below, the eUICC 225 may use a pre-stored one-time private key (otSK.EUICC.KA) corresponding to otPK.EUICC.KA or / and the index ID of the eUICC to create a session key to decrypt the BPP and process the installation (step 280). As described above, (step 275) to (step 280) may be performed as a sequential operation of receiving one or more messages and replying to the corresponding processing results thereof. For example, at step 275, LPAf (not shown) may transmit some data required for profile installation as one or more ES10x messages to the eUICC 225 using ES10f.prepareLoading, and LPAf (not shown) receives the installation result thereof from the eUICC 225, and then transmits BPP to the eUICC 225 through functions such as ES10f.LoadBPP, and the eUICC 225 having received the BPP processes the received message by combining the previously received information, and then creates a response message and replies to LPAf (not shown). In this case, the eUICC may first receive otPK.EUICC.KA or / and the index ID for creating a session key independently of otPK.DP.KA (ES10f.prepareLoading in the above example), and the eUICC 225 may identify and store whether there is otPK.EUICC.KA or / and otSK.EUICC.KA mapped to the index ID, and then process the session key creation by combining the identified and stored otSK.EUICC.KA and otPK.DP.KA at the time point of creating a session key including the received PK.DP.KA. In this way, in the case of transmitting information for profile installation with one or more messages, an identifier for identifying whether the information is information for the same profile installation may be included in the transmitted message. For example, this may be a transaction ID. This may also apply to the later-described Figures 2 to 6.

[0114] In the process of verifying the signature of the profile server 210 (step 280), in the case where the index ID is received as signature data, the eUICC 225 verifies the signature by including the index ID. In the case where the index ID is received as unsigned data, the eUICC 225 should verify the signature without including the index ID when verifying the signature of the profile server.

[0115] In the process of creating the session key (step 280), the eUICC 225 may perform the following process according to whether the index ID or otPK.EUICC.KA is received.

[0116] • Upon receiving the Index ID: create a session key where otSK.EUCC.KA is mapped to the Index ID.

[0117] When no index ID is received but otPK.EUCC.KA is received: create session key where otSK.EUCC.KA is mapped to otPK.EUCC.KA

[0118] When the Index ID is not received and the otPK.EUCC.KA is not received: the eUICC sequentially selects one of the unused otSK.EUICC.KA and uses the otSK.EUICC.KA or returns an error.

[0119] If the profile is successfully installed by decrypting the BPP (step 280), the eUICC 225 discards the corresponding otPK / SK.EUICC.KA used for BPP installation. If the profile installation fails, the eUICC 225 may maintain and store the otPK / SK.EUICC.KA for future use.

[0120] The eUICC 225 may transmit the profile installation result to the UE with or without LPAf, and the UE may reply to the Factory IT Server 215 (step 285). The eUICC 225 may transmit an installation result message reply to the Factory IT 215, including the installation result data signed by the eUICC and to be recognized by the Profile Server / Server Vendor 210, in addition to the installation result data to be recognized by the Factory IT 215.

[0121] When the factory IT 215 receives a response indicating that the configuration file installation result is successful, the factory IT 215 may delete the used key material or change the status of the corresponding key material to use completed. When the factory IT 215 receives a response indicating that the configuration file installation result is an error, the factory IT 215 may maintain and store the used key material and change the status of the corresponding key material (e.g., error, installation error, etc.).

[0122] The factory IT 215 may reply the profile installation result to the profile server / server vendor 210. The factory IT / OEM 215 may reply the installation results to the profile server / server vendor 210 individually, or collect the results and provide them to the profile server / server vendor 210 in batches at a specific time point. In the case where the processing result is received as the installation result data signed by the eUICC, the profile server / server vendor 210 may verify the signature of the eUICC to identify the processing result. After receiving the success result as the processing result, the profile server / server vendor 210 may manage the use of the otPK.EUICC.KA (+index ID) corresponding to the BPP installation by discarding the otPK.EUICC.KA (+index ID) received in (step 255) and changing the status of the otPK.EUICC.KA to use complete. The profile server / server vendor 210 or the factory IT / OEM 215 may optionally provide the corresponding installation result to the SP / SP server 205.

[0123] Figure 3 is a message flow diagram illustrating a method in which an otPK index ID is used and in which an eUICC specifies and uses a usage order according to an embodiment of the present disclosure.

[0124] Figure 3 Shown with Figure 2 The same approach is used in the case of otPK index ID, and in Figure 2 In the factory IT specifies the order in which the index IDs are used, but Figure 3 to Figure 4 and Figure 2 The difference is the way the eUICC specifies the order of use using the otPK index ID.

[0125] Figure 3 The operation of the eUICC having no profile and first installing the profile in the factory is shown, and Figure 4 An operation of processing installation in a case where the eUICC has transmitted an index ID at a point in time before the profile is installed in the eUICC is shown. Figure 3 and Figure 4The process can be handled as a separate process or in Figure 3 Processing in the connection operation at a specific point in time after the process occurs Figure 4 process.

[0126] exist Figure 3 In , the above process is used, but because some operations are different, the corresponding operations are mainly described. Figure 3 In the case of explicit description, it should be noted that reference can be made to Figure 2 process is explained.

[0127] exist Figure 3 At step 327 of , a configuration file of IFPP may be prepared and transmitted to the factory IT / OEM. A UE manufacturer wishing to produce a UE equipped with an eUICC may order M eUICCs through the EUM / EUM server 300, and the EUM 300 may provide (step 330) predetermined information (key material) to the factory IT / OEM 315, the information including encryption key information about the ordered M eUICCs. As key material information provided by the EUM 300, the EUM 300 may include otPK.EUICC.KA for each eUICC, and otPK.EUICC.KA may be transmitted as a signature value of the eUICC. In addition, as key material information provided by the EUM 300, the EUM 300 may also include an index ID as identification information for identifying otPK.EUICC.KA. The index ID may be transmitted as a value signed or unsigned by the eUICC. In the case where otPK.EUICC.KA or Index ID is transmitted as an eUICC signed value, the EUM may also include and transmit the public key of the eUICC to the factory IT / OEM 315, which may be included in the eUICC certificate and transmitted. In addition, the EUM may also explicitly include and transmit the first used Index ID indicator. The first used Index ID indicator is information that can be identified by the factory IT and can be transmitted with an eUICC unsigned value.

[0128] In the case where the EUM 300 supports installation of N profiles in the eUICC, N otPK.EUICC.KA of each eUICC and an index ID for distinguishing them may be transmitted to the factory IT / OEM 315. The index ID for first installing the profile in the corresponding eUICC may be transmitted together.

[0129] The index ID is information mapped to otPK.EUICC.KA, and the eUICC 325 that has received the index ID may transmit the corresponding index ID as information for determining otPK.EUICC.KA for creating a session key. The index ID may be constructed as a value that can distinguish otPK.EUICC.KA, and this may be composed of, for example, a partial value or the entire value of otPK.EUICC.KA, a value created by including part or all of otPK.EUICC.KA, a hash value of a value created by including part or all of otPK.EUICC.KA, a part of the hash value, or a value created by deriving from otPK.EUICC.KA. Alternatively, the index ID may be a number that can specify otPK.EUICC.KA or a value created by including a number that can specify otPK.EUICC.KA. The index ID may be defined in data formats such as integers, strings, and binary. The description of the index ID may also be applied even if it is not described in other figures in the present disclosure.

[0130] The Factory IT / OEM 315 may store by additionally indicating in the case of the EID of the Index ID of eUICC-otPK.EUICC.KA-Index ID-to be used first.

[0131] Thereafter, at a particular point in time, the factory IT / OEM 315 may determine to load the profile onto N eUICCs that are part of the M eUICCs ordered from the EUM 300, or onto all M eUICCs ordered from the EUM 300. This may be based on a profile preload release request from the service provider (SP) / SP server 305.

[0132] The factory IT / OEM 315 may transmit (step 340) at least one information of the number of configuration files or the list of EIDs to the SP / SP server 305 so that the SP / SP server 305 can prepare configuration files linked to the EIDs in advance as an additional optional procedure. The SP / SP server 305 may order (step 345) configuration files from the configuration file server / server provider 310. In the case where step 340 has been performed in advance and the EID list exists or the EID list is acquired at a specific time point before, the SP / SP server 305 may include the EID information when ordering the configuration file and request the information from the configuration file server / server provider 310. The SP / SP server 305, the configuration file server / server provider 310, and the factory IT / OEM 315 may share (step 350) information that may specify the corresponding order with each other. The information that may specify the corresponding order may be shared as identification information provided by the SP / SP server 305 or the configuration file server / server provider 310 to the factory IT / OEM 315. For example, the identification information may be at least one of information such as a batch ID and an order ID, an ordered profile list or EID list, information about the start and end numbers of the profile list or EID list, a factory serial number, or information about a manufacturer identification number.

[0133] The factory IT / OEM 315 may request a BPP from the profile server / server vendor 310. When requesting a BPP, the factory IT / OEM 315 may transmit (step 355) to the profile server / server vendor 310 the key information corresponding to the eUICC of the corresponding target UE (up to N) among the key information of the eUICC obtained at step 330, where N is the number of UEs to which the SP / SP server 305 is to load the profile. This may be part or all of the key information received previously (at step 330). In the event that the factory IT / OEM 315 receives multiple otPK.EUICC.KA for each eUICC from the EUM / EUM server 300, the factory IT / OEM 315 may identify the index ID to be used first and receive it from the EUM / EUM server 300, and select and transmit the otPK.EUICC.KA corresponding to the index ID. Depending on whether the index ID is included previously (at step 350), transmission (step 355) may be as follows.

[0134] In the case where the index ID is received as signature data, transmit data containing the index ID

[0135] When data containing an index ID is received but received as unsigned data, transmit the data with or without the index ID

[0136] In case no index ID is received, the factory IT / OEM 315 does not contain the index ID

[0137] The profile server / server vendor 310 may combine the collected information in at least one step of collecting the received profile order information (step 345), the link information of the profile EID (step 340), the mutually shared order information (step 350), and the encryption key information of the target eUICC (step 355) to install the received profile to create (step 360) an encrypted profile package, and then provide (step 365) the created profile package and the information about the eUICC binding to the factory IT / OEM 315. When the profile server 310 receives the message (step 355), and composes (step 360) the verification and reply message for BPP creation, if the index ID exists, the profile server 310 may further perform the following operations.

[0138] In case the Index ID is received as eUICC signature data, verify the eUICC signature by including the Index ID, and if the signature verification fails, return an error, and if the signature verification succeeds,

[0139] Create a signature for the profile server by including the index ID.

[0140] When the Index ID is received as unsigned data, the Index ID is not included in the eUICC signature verification. The Profile Server's signature is created by including the Index ID.

[0141] An index ID can be defined and used as the value of the transaction ID or as a new parameter.

[0142] The created encrypted profile package and mapped BPP encryption key information may be transmitted (step 365) to the factory IT / OEM 315 in one or more messages, and some or all of the data transmitted in the corresponding messages may be provided as signature data for the profile server.

[0143] If the index ID is included and transmitted in the previous step (step 355), the corresponding message being transmitted may be replied to by including the index ID in the signature data (step 365).

[0144] At step 370, the operation of the factory IT 315 to install the profile of the IFPP in the eUICC may be described. This step may be performed for N eUICCs.

[0145] The factory IT / OEM 315 may inject the configuration file into the UE before the UE is released from the factory. To this end, the factory IT / OEM 315 may obtain and store a series of encryption key information required for decrypting the configuration file from the BPP and the eUICC. The series of encryption key information may include a one-time public key of the EUICC (hereinafter referred to as otPK.EUICC.KA). The series of encryption key information may also include an index ID mapped to otPK.EUICC.KA.

[0146] The factory IT 315 may transmit the BPP and a series of encryption key information required for decrypting the profile in the eUICC from the factory to each UE 320 through a wired / wireless network within the factory. The BPP and a series of encryption key information may be included in one or more messages and transmitted to the UE 320. In the case where the otPK.eUICC.KA is included and transmitted, the otPK.eUICC.KA may be included in the signature data from the profile server and received by the UE 320. In the case where the index ID is included and transmitted, the index ID may be included in the signature data from the profile server and received by the UE 320. In the case where the otPK.EUICC.KA or the index ID is received as the signature data of the profile server, for example, the otPK.EUICC.KA or the index ID may be included in the signature data and received as one of the following. This is not limited to the following examples.

[0147] -SK.DPauth.SIG: The profile server's private key for authentication with the profile server

[0148] -SK.DPpb.SIG: Private key used in the profile server for profile binding of the profile server

[0149] -SK.DPxx.SIG: The private key of the configuration file server, where xx is defined to indicate the use of IFFP

[0150] As described above, SK.DPpb.SIG may be a private key of a profile server used for profile binding in the profile server, or may be a private key of a profile server used by the profile server for IFPP. In DPxx.SIG, xx indicating use may be indicated as specific information indicating xx indicating IFPPP use.

[0151] The UE 320 may provide a function of receiving a BPP from the factory IT 315 and injecting the BPP into the eUICC 325 in the IFPP mode. For example, the corresponding UE 320 may operate in the factory provision mode at the time of receiving the BPP, or the UE 320 may recognize that it should enter the IFPP and initiate the operation at the time of receiving the BPP. Alternatively, the UE 320 may enter the corresponding mode by an event input into the UE by a factory employee, a configuration value, or recognition of a specific virtual private network (VPN). Entering the IFPP mode by a UI or a configuration value may be provided by limiting a UI that is not displayed to the user in a general environment. The UE 320 may transmit the BPP to the eUICC 325 (step 375).

[0152] In this case, in the case where the factory IT does not transmit the index ID to the profile server (step 355), the factory IT may also include the index ID mapped to the BPP so as to be installed in the corresponding UE and transmit it to the UE 320. This may be transmitted to the eUICC 325 through the LPAf (not shown) as described above, or may be transmitted to the eUICC 325 without the LPAf (not shown) (step 375). As an example of a message transmitted to the eUICC using the LPAf (not shown), the BPP may be included in one or more messages of the ES10x and transmitted.

[0153] The eUICC 325 may receive information that allows identification that the message received by the eUICC 325 from the UE 320 is an operation for IFPP. The eUICC 325 may determine that the profile installation operation is performed for IFPP through the message received from the UE 320 and enter.

[0154] This can be a new function defined for IFPP, an IFPP identifier parameter added to an existing SGP.31 / 33 or an ES10x message defined in SGP.31 / 33, or identification information for factory release that is not included in the (consumer-oriented, M3M-oriented, or IoT-oriented) profile provisioning in a general environment after the release of the UE. For example, it can be one of the values ​​such as factory serial number, batch ID, manufacturer identification information. It is not limited to this.

[0155] As described above, the UE 320 may receive data including otPK.EUICC.KA or index ID from the profile server, and the data including the corresponding otPK.EUICC.KA or index ID may be included and received in data signed by one of the following. This is not limited to the following examples.

[0156] -SK.DPauth.SIG: The profile server's private key used for authenticating the profile server to the profile server

[0157] -SK.DPpb.SIG: The private key of the profile server used for profile binding by the profile server

[0158] -SP.DPifpp.SIG: The profile server's private key used exclusively by the profile server for IFPP

[0159] UE 320 may transmit the signed data to eUICC 325 again with or without LPAf. eUICC 325 may verify the signature of the data received by profile server 310, create a session key using the pre-stored one-time private key of eUICC (otSK.EUICC.KA) to decrypt the BPP and process the installation (step 380).

[0160] In the process of verifying the signature of the profile server 310 (step 380), in the case where the index ID is received as signature data, the eUICC 325 verifies the signature by including the index ID. In the case where the index ID is received as unsigned data, the eUICC 325 should verify the signature without including the index ID when verifying the signature of the profile server.

[0161] In the process of creating the session key (step 380), the eUICC 325 may perform the following process depending on whether the index ID or otPK.EUICC.KA is received.

[0162] If an Index ID is received, the eUICC may also identify whether there is a usage order configured first in the eUICC before selecting the otSK.EUICC.KA mapped to the Index ID.

[0163] In case the usage order is the same, a session key is created using the otSK.EUCC.KA mapped to the index ID, and if the usage order is different or there is no index ID matching the received index ID, an error may be returned.

[0164] If no Index ID is received and otPK.EUCC.KA is received: create session key where otSK.EUCC.KA is mapped to otPK.EUCC.KA

[0165] If no Index ID is received and no otPK.EUCC.KA is received: the eUICC selects one of the unused otSK.EUICC.KA in turn and uses the otSK.EUICC.KA or returns an error.

[0166] If the profile is successfully installed by decrypting the BPP (step 380), the eUICC 325 discards the corresponding otPK / SK.EUICC.KA used for BPP installation. If the profile installation fails, the eUICC 325 may maintain and store the otPK / SK.EUICC.KA for future use.

[0167] The eUICC 325 may transmit the profile installation result to the UE with or without LPAf, and the UE may reply to the factory IT server 315 (step 375).

[0168] The eUICC 325 may transmit an Installation Result message reply to the Factory IT 315 that includes, in addition to the Installation Result data to be recognized by the Factory IT 315 , the Installation Result data signed by the eUICC to be recognized by the Profile Server / Server Vendor 310 .

[0169] If the configuration file is installed successfully, then the reply message (at step 385) may provide the following usage order by including an index ID.

[0170] When the factory IT 315 receives a response that the profile installation result is successful, the factory IT 315 can delete the used key material or change the status of the corresponding key material to use completed. When the factory IT 315 receives a response that the profile installation result is an error, the factory IT 315 can maintain and store the used key material and change the status of the corresponding key material (e.g., error, installation error, etc.). In addition, when the index ID is included and received, the factory IT / OEM 315 can indicate and store the BPP mapped to the corresponding index ID in the following order.

[0171] The factory IT 315 may again reply the profile installation result to the profile server / server vendor 310. The factory IT / OEM 315 may reply the installation results to the profile server / server vendor 310 individually, or collect the results and provide them to the profile server / server vendor 310 in batches at a specific time point. In the case where the processing result is received as the installation result data signed by the eUICC, the profile server / server vendor 310 may verify the signature of the eUICC to identify the processing result. After receiving the success result as the processing result, the profile server / server vendor 310 may manage the use of the otPK.EUICC.KA (+index ID) corresponding to the BPP installation by discarding the otPK.EUICC.KA (+index ID) received in (step 355) and changing the status of the otPK.EUICC.KA to use complete. The profile server / server vendor 310 or the factory IT / OEM 315 may optionally provide the corresponding installation result to the SP / SP server 305.

[0172] Figure 4 : is a message flow diagram showing another embodiment of a case where an otPK index ID is used and an eUICC specifies and uses a usage order according to an embodiment of the present disclosure.

[0173] Figure 3 and Figure 4 The process can be handled as a separate process or in Figure 3 The connection operation is processed at a specific point in time after the process occurs. Figure 4 process.

[0174] The factory IT / OEM 415 may store the key material - [index ID] - usage order, including the EID of the eUICC - otPK.EUICC.KA. The usage order may be as specified by the factory IT / OEM 415 in executing Figure 4 The result of performing BPP installation at a specific point in time before the process of receiving the information from the eUICC 425, such as the index ID used in the following order.

[0175] Thereafter, at a specific point in time, the factory IT / OEM 415 may request a BPP from the profile server / server vendor 410 (step 455). The factory IT / OEM 415 may transmit (step 455) the key information (up to N) of the eUICCs corresponding to the target UEs to the profile server / server vendor 410, where N is the number of UEs to which the SP / SP server 405 will load the profile in the eUICC key information obtained at the previous specific point in time (step 435). This may be part or all of the key information received previously (step 430). In the event that the factory IT / OEM 415 receives multiple otPK.EUICC.KA for each eUICC from the EUM / EUM server 400, the factory IT / OEM 415 may identify the index ID received from the eUICC during the previous BPPP installation, select the otPK.EUICC.KA mapped to the index ID, and transmit it to the profile server / server vendor 410. The factory IT may determine whether the index ID is included and transmit it (step 455). This may be handled in one of the following ways depending on whether the Index ID is received as signed data of the eUICC, as described above: Figure 3 As described in (step 330).

[0176] In case the Index ID is received as eUICC Signature Data, data including the Index ID is transmitted.

[0177] When data containing an Index ID is received but the data is received as eUICC unsigned data, transmit the data with or without the Index ID

[0178] • In the event that no Index ID is received, the Factory IT / OEM 415 does not include the Index ID.

[0179] like Figure 3 As shown, the profile server / server vendor 410 may combine the collected information in at least one of the steps of collecting the received profile order information (step 345), the link information of the profile EID (step 340), the mutually shared order information (step 350), and the encryption key information of the target eUICC to install the received profile (step 355), creating (step 460) an encrypted profile package, and then providing (step 465) the created profile package and the information about the eUICC binding to the factory IT / OEM 415. When the profile server 410 receives the message (step 455) and composes (step 460) the verification and reply message for BPP creation, if the index ID exists, the profile server 410 may further perform the following operations.

[0180] In case the Index ID is received as eUICC signature data, verify the eUICC signature by including the Index ID, and if the signature verification fails, return an error, and if the signature verification succeeds,

[0181] Create a profile server signature by including the index ID.

[0182] When the Index ID is received as unsigned data, the Index ID is not included in the eUICC signature verification. The Profile Server's signature is created by including the Index ID.

[0183] An index ID can be defined and used as the value of the transaction ID or as a new parameter.

[0184] The created encrypted profile package and mapped BPP encryption key information may be transmitted (step 465) to the factory IT / OEM 415 in one or more messages, and some or all of the data transmitted in the corresponding messages may be provided as signature data for the profile server.

[0185] If the index ID is included and transmitted in the previous step (step 455), the corresponding message being transmitted may be replied to by including the index ID in the signature data (step 465).

[0186] Can refer to and reference Figure 3 The corresponding description of (step 375) to (step 390) can be used to understand (step 475) to (step 490) after step 470.

[0187] In the case where the profile installation is successful and the index ID used for the profile installation is the last index ID, the eUICC may transmit a message without including the index ID in (step 385). In the case where the reply message received by the factory IT / OEM 415 is transmitted without the index ID, the factory IT / OEM 415 may additionally identify whether all index IDs mapped to the corresponding eUICC have been exhausted and complete the process.

[0188] Figure 5 is a message flow diagram illustrating a method in which an EUM transmits one key material and in which an eUICC specifies the key material to be used next time and replies to the factory IT according to an embodiment of the present disclosure.

[0189] In the above description, Figure 5The process and operation in which the EUM creates otPK.EUICC.KA (i.e., a list of multiple eUICC encryption keys and / or corresponding index IDs) for each eUICC, stores the corresponding multiple key information of each eUICC, and also transmits (step 550) and uses the corresponding list to the factory IT / OEM 515 is mainly shown. Figure 2 compared to, Figure 5 The process and operation of the EUM being initially transmitted (step 550) to the factory IT / OEM 515 for each eUICC and using only one key material is shown.

[0190] The key material may include at least otPK.EUICC.KA (ie, eUICC encryption key) and a corresponding index ID.

[0191] Before releasing the UE, the UE manufacturer may preload the profile onto the eUICC in the factory and release the UE, and in this case, the UE manufacturer may provision the profile in one or more UEs, especially for a large number of UEs. This step may be divided into a step (527) of preparing the profile and transmitting the profile to the factory IT / OEM 515, and a step (570) of the factory IT installing the profile in N different eUICCs 525.

[0192] At step 527, a configuration file of the IFPP may be prepared and transmitted to the factory IT / OEM. A UE manufacturer wishing to produce a UE equipped with an eUICC may order M eUICCs through the EUM / EUM server 500, and the EUM 500 may provide (step 550) predetermined information (key material) to the factory IT / OEM 515, the information including encryption key information about the ordered M eUICCs. As key material information provided by the EUM 500, the EUM 500 may include otPK.EUICC.KA for each eUICC, and otPK.EUICC.KA may be transmitted as an eUICC signature value. In addition, as key material information provided by the EUM 500, the EUM 500 may also include an index ID as identification information for identifying otPK.EUICC.KA. The index ID may be transmitted as an eUICC signed or unsigned value. In the case where otPK.EUICC.KA or index ID is transmitted as an EUM signature value, EUM may also include the public key of the eUICC and transmit it to the factory IT / OEM 515, and the public key may be included in the eUICC certificate and transmitted. In the case where EUM 500 supports installation of N profiles in the eUICC, N otPK.EUICC.KA and index IDs for distinguishing them may be transmitted to the factory IT / OEM 515. Index ID is information mapped to otPK.EUICC.KA, and the eUICC 525 having received the index ID may transmit the corresponding index ID as information for determining otSK.EUICC.KA for creating a session key.

[0193] The index ID is information mapped to otPK.EUICC.KA, and the eUICC 525 having received the index ID may transmit the corresponding index ID as information for determining otPK.EUICC.KA for creating a session key. The index ID may be configured as a value that can distinguish otPK.EUICC.KA, and this may be composed of, for example, a partial value or the entire value of otPK.EUICC.KA, a value created by including part or all of otPK.EUICC.KA, a hash value of a created value including part or all of otPK.EUICC.KA, a part of the hash value, or a value created by deriving from otPK.EUICC.KA. Alternatively, the index ID may be a number that can specify otPK.EUICC.KA or a value created by including a number that can specify otPK.EUICC.KA. The index ID may be defined in data formats such as integers, strings, and binary.

[0194] In the event that the EUM / EUM server 500 receives an order for a configuration file of the IFPP, the EUM / EUM server 500 may provide the eUICC encryption key information required for BPP decryption of each eUICC to the factory IT / OEM 515. Upon receiving the information, the factory IT / OEM 515 may store (step 555) the encryption key information about the ordered M eUICCs in the factory IT server 515. Figure 2 In contrast, the factory IT / OEM 515 may also receive and manage one otPK.EUICC.KA for each eUICC and optionally mapped index ID. The EUM / EUM server 500 may provide only one otPK.EUICC.KA-[index ID] for each eUICC (step 550). This may correspond to the case where the EUM / EUM server 500 creates multiple otPK.EUICC.KA-[index ID] and injects multiple key information into the eUICC or the case where the EUM / EUM server 500 creates one otPK.EUICC.KA-[index ID] and injects one key information into the eUICC.

[0195] Thereafter, at a particular point in time, the factory IT / OEM 515 may determine to load the profile onto all of the N or M eUICCs ordered from the EUM 500. This may be based on a profile preload release request from the service provider (SP) / SP server 505.

[0196] The factory IT / OEM 515 may transmit (step 540) at least one information of the number of configuration files or the list of EIDs to the SP / SP server 505 so that the SP / SP server 505 can prepare configuration files linked to the EIDs in advance as an additional optional procedure. The SP / SP server 505 may order (step 545) configuration files from the configuration file server / server provider 510. In the case where step 540 has been performed in advance and the EID list exists or the EID list is acquired at a specific time point before, the SP / SP server 505 may include the EID information when ordering the configuration file and request the information from the configuration file server / server provider 510. The SP / SP server 505, the configuration file server / server provider 510, and the factory IT / OEM 515 may share (step 550) information that can specify the corresponding order with each other. The information that can specify the corresponding order may be shared as identification information provided by the SP / SP server 505 or the configuration file server / server provider 510 to the factory IT / OEM 515. For example, the identification information may be at least one of information such as a batch ID and an order ID, an ordered profile list or EID list, information about the start and end numbers of the profile list or EID list, a factory serial number, or information about a manufacturer identification number.

[0197] The factory IT / OEM 515 may request a BPP from the profile server / server vendor 510. When requesting a BPP, the factory IT / OEM 515 may transmit (step 555) to the profile server / server vendor 510 the key information of the eUICC obtained at step 550 corresponding to the eUICC of the corresponding target UE (up to N), where N is the number of UEs to which the SP / SP server 505 is to load the profile. This may be part or all of the key information received previously (at step 550). The factory IT / OEM 515 may transmit the otPK.EUICC.KA for each eUICC received from the EUM / EUM server 500 to the factory IT / OEM 515. Depending on whether the index ID was included and received previously (step 550), the transmission (step 555) may be as follows.

[0198] In the case where the index ID is received as signature data, transmit data containing the index ID

[0199] When data containing an index ID is received but received as unsigned data, transmit the data with or without the index ID

[0200] In case the index ID is not received, the factory IT / OEM 515 does not contain the index ID

[0201] The profile server / server vendor 510 may combine the collected information in at least one step of collecting the received profile order information (step 545), the link information of the profile EID (step 540), the mutually shared order information (step 550), and the encryption key information of the target eUICC to install the received profile (step 555), creating (step 560) an encrypted profile package, and then providing (step 565) the created profile package and the information about the eUICC binding to the factory IT / OEM 515. When the profile server 510 receives the message (step 555) and composes (step 560) the verification and reply message for BPP creation, if the index ID exists, the profile server 510 may further perform the following operations.

[0202] In case the Index ID is received as eUICC signature data, the eUICC signature is verified by including the Index ID.

[0203] • When the Index ID is received as eUICC signed or unsigned data, the Profile Server’s signature is created by including the Index ID.

[0204] Create a signature for the configuration file server by including the index ID as a value or new parameter for the transaction ID.

[0205] The created encrypted configuration file package and each BPP encryption key information may be transmitted (step 565) to the factory IT / OEM 515 in one or more messages, and part or all of the data transmitted in the corresponding message may be provided as signature data.

[0206] The BPP may be received (step 565), and in case the Index ID has been previously received, the corresponding message being transmitted may be transmitted including the Index ID in the Signature Data (step 565). In case the message is transmitted with or without the Index ID, the otPK.EUICC.KA may be included in the Signature Data and transmitted (step 565).

[0207] At step 570, the operation of the factory IT 515 to install the profile of the IFPP in the eUICC may be described. This step may be performed for N eUICCs.

[0208] The factory IT / OEM 515 may inject the configuration file into the UE before the UE is released from the factory. To this end, the factory IT / OEM 515 may obtain and store a series of encryption key information required for decrypting the configuration file from the BPP and the eUICC. The series of encryption key information may include a one-time public key of the EUICC (hereinafter referred to as otPK.EUICC.KA). The series of encryption key information may also include an index ID mapped to otPK.EUICC.KA.

[0209] The factory IT 515 may transmit the BPP and a series of encryption key information required for decrypting the profile in the eUICC from the factory to each UE 520 through a wired / wireless network within the factory. The BPP and a series of encryption key information may be included in one or more messages and transmitted to the UE 520. In the case where the otPK.eUICC.KA or index ID is included and transmitted, the otPK.eUICC.KA or index ID may be included in the signature data from the profile server and received by the UE 520. For example, the otPK.eUICC.KA or index ID may be included in the signature data and received as one of the following. This is not limited to the following examples.

[0210] -SK.DPauth.SIG: The profile server's private key for authentication with the profile server

[0211] -SK.DPpb.SIG: Private key used in the profile server for profile binding of the profile server

[0212] -SK.DPxx.SIG: The private key of the configuration file server, where xx is defined to indicate the use of IFFP

[0213] As described above, SK.DPpb.SIG may be a private key of a profile server used for profile binding in the profile server, or may be a private key of a profile server used by the profile server for IFPP. In DPxx.SIG, xx indicating use may be indicated as specific information indicating xx indicating IFPPP use.

[0214] The UE 520 may provide a function of receiving a BPP from the factory IT 515 and injecting the BPP into the eUICC 525 in the IFPP mode. For example, the corresponding UE 520 may operate in the factory provision mode at the time of receiving the BPP, or the UE 520 may recognize that it should enter the IFPP and initiate the operation at the time of receiving the BPP. Alternatively, the UE 520 may enter the corresponding mode by an event input into the UE by a factory employee, a configuration value, or recognition of a specific virtual private network (VPN). Entering the IFPP mode by a UI or a configuration value may be provided by limiting a UI that is not displayed to the user in a general environment. The UE 520 may transmit the BPP to the eUICC 525 by LPAf (not shown) as described above or without LPAf (not shown) (step 575).

[0215] As an example of a message transmitted to the eUICC using LPAf (not shown), it may be included in one or more messages of ES10x and transmitted. Figures 4 to 6 An embodiment thereof is described.

[0216] Information that allows identification that a message received by the eUICC 525 from the UE 520 is an operation for IFPP may be received. The eUICC 525 may determine that a profile installation operation is performed for IFPP through the message received from the UE 520 and enter.

[0217] This can be a new function defined for IFPP, an IFPP identifier parameter added to an existing SGP.51 / 52 or an ES10x message defined in SGP.51 / 52, or identification information for factory release that is not included in the (consumer-oriented, M2M-oriented, or IoT-oriented) profile provisioning in a general environment after the release of the UE. For example, it can be one of the values ​​such as factory serial number, batch ID, manufacturer identification information. It is not limited to this.

[0218] As described above, the UE 520 may receive data including otPK.EUICC.KA or index ID from the profile server, and the data including the corresponding otPK.EUICC.KA or index ID may be included and received in data signed by one of the following. This is not limited to the following examples.

[0219] -SK.DPauth.SIG: The profile server's private key used for authenticating the profile server to the profile server

[0220] -SK.DPpb.SIG: The private key of the profile server used for profile binding by the profile server

[0221] -SP.DPifpp.SIG: The profile server's private key used exclusively by the profile server for IFPP

[0222] UE 520 may transmit the signed data to eUICC 525 again with or without LPAf. eUICC 525 may verify the signature of the data received by profile server 510, create a session key using the pre-stored one-time private key of eUICC (otSK.EUICC.KA) to decrypt the BPP and process the installation (step 580).

[0223] In the process of verifying the signature of the profile server 510 (step 580), in the case where the index ID is received as signature data, the eUICC 525 verifies the signature by including the index ID. In the case where the index ID is received as unsigned data, the eUICC 525 should verify the signature without including the index ID when verifying the signature of the profile server.

[0224] In the process of creating the session key (step 580), the eUICC 525 may perform the following process according to whether the index ID or otPK.EUICC.KA is received.

[0225] • Upon receiving the Index ID: create a session key where otSK.EUCC.KA is mapped to the Index ID.

[0226] When no index ID is received and otPK.EUCC.KA is received: create session key where otSK.EUCC.KA is mapped to otPK.EUCC.KA

[0227] When no Index ID is received and no otPK.EUCC.KA is received: the eUICC selects one of the unused otSK.EUICC.KA (eg, according to the order) and uses the otSK.EUICC.KA or returns an error.

[0228] If the BPP (step 580) is decrypted and the profile installation is successful, the eUICC 525 discards the corresponding otPK / SK.EUCC.KA for BPP installation. In addition, when the profile installation is successful, the eUICC 525 may additionally perform one of the following operations 1 and 2.

[0229] 1. Create otPK / otSK.EUICC.KA and optionally corresponding Index ID, and store otPK.EUICC.KA or Index ID mapped to otSK.EUICC.KA. Sign the data including otPK.EUICC.KA using the eUICC's private key and transmit the key material. The Index ID (when created) may or may not be included in the signed data.

[0230] 2. Select an unused otSK.EUICC.KA and transmit the data including the corresponding otPK.EUICC.KA using key material signed with the eUICC's private key. The Index ID (when stored) is transmitted with or without inclusion in the signature data.

[0231] If the profile installation fails, the eUICC 525 may maintain and store the otPK / SK.EUICC.KA for future use.

[0232] The eUICC 525 may transmit the installation result of the profile to the UE with or without LPAf, and the UE may reply to the Factory IT Server 515 (step 585). The eUICC 525 may transmit an installation result message reply to the Factory IT 515, including the installation result data signed by the eUICC and to be recognized by the Profile Server / Server Vendor 510, in addition to the installation result data to be recognized by the Factory IT 515.

[0233] An example of data being transmitted may have a structure in the following format.

[0234] Profile Installation Result ([signed (key material), key material], result 1, [index ID], [signed (result 2), result 2])

[0235] Signed (Key Material) is the key material data signed by the eUICC. This data may be included and transmitted when the profile is successfully installed. otPK.EUICC.KA shall be included as the key material that may be used to create a BPP in the corresponding eUICC and optionally includes an index ID.

[0236] Key Material: This may be emitted as a hash value, as compared by the Profile Server for signature verification.

[0237] Result 1: Installation result information to be recognized by factory IT, which can be encrypted and transmitted using an encryption key that factory IT can interpret.

[0238] Index ID: In the event that an Index ID exists but Signature Data 1 is not created including the Index ID, it may optionally be included for identification by the Factory IT. It may be encrypted and transmitted using an encryption key that the Factory IT can interpret.

[0239] Signed (Result 2): Installation result to be transmitted to the Profile Server and signed by the eUICC.

[0240] Result 2: This may be transmitted together with the hash value as a value used by the profile server for signature verification by comparing the signature result 2.

[0241] If the factory IT 515 receives a response that the profile installation result is successful, the factory IT 515 can delete the used key material or change the status of the corresponding key material to use completed. The factory IT 515 can store the signed (key material) and key material as information to be used for the next BPP installation request to the profile server. If the factory IT 515 receives a response that the profile installation result is an error, the factory IT 515 can maintain and store the used key material and change the status of the corresponding key material (e.g., error, installation error, etc.).

[0242] The factory IT 515 may reply the profile installation result to the profile server / server vendor 510 again. In this case, referring to the above example, the factory IT 515 may transmit the profile installation result excluding the signature (key material), the key material and the index ID. The factory IT / OEM 515 may reply the installation result to the profile server / server vendor 510 individually, or may collect the results and provide them to the profile server / server vendor 510 in batches at a specific time point. In the case where the processing result is received as the installation result data signed by the eUICC, that is, if it is received with the signature (result 2) referring to the above example, the profile server / server vendor 510 may verify the signature of the eUICC to identify the processing result. After receiving the success result as the processing result, the profile server / server vendor 510 may manage the otPK.EUICC.KA by discarding the otPK.EUICC.KA (+index ID) received in (step 555) and changing the status of the otPK.EUICC.KA to use completed to complete the use of the otPK.EUICC.KA (+index ID) installed by the corresponding BPP. The profile server / server vendor 510 or factory IT / OEM 515 may optionally provide corresponding installation results to the SP / SP server 505 .

[0243] Figure 6is a message flow diagram illustrating an operation of using an otPK having a usage number or using an otPK indefinitely in an otPK reuse method according to an embodiment of the present disclosure.

[0244] Figure 2 and Figure 3 A method that does not reuse the eUICC encryption key, such as a method using an index ID, is shown. Figure 6 A method for handling profile provisioning by reusing eUICC encryption keys is shown. Figure 6 Before releasing the UE, the UE manufacturer may preload the profile into the eUICC in the factory and release the UE, and in this case, the UE manufacturer may provision the profile in one or more UEs, especially for a large number of UEs. This step may be divided into a step (627) of preparing the profile and transmitting the profile to the factory IT / OEM 615, and a step (670) of the factory IT installing the profile in N different eUICCs 625.

[0245] At step 627, a configuration file of the IFPP may be prepared and transmitted to the factory IT / OEM. A UE manufacturer wishing to produce a UE equipped with an eUICC may order M eUICCs through the EUM / EUM server 600, and the EUM 600 may provide (step 630) predetermined information (key material) to the factory IT / OEM 615, which includes encryption key information about the ordered M eUICCs. As key material information provided by the EUM 600, the EUM 600 may include otPK.EUICC.KA for each eUICC, and otPK.EUICC.KA may be transmitted as an EUM signed value. In addition, as key material information provided by the EUM 600, the EUM 600 may also include a usage policy (policy rule) for otPK.EUICC.KA. The policy rule may be transmitted as an EUM unsigned value. In the case where otPK.EUICC.KA is transmitted with an EUM signature value, EUM may also include the public key of the eUICC and transmit it to the factory IT / OEM 615, and the public key may be included in the eUICC certificate and transmitted. In the case where EUM600 supports the installation of N number of profiles in the eUICC, N number of otPK.EUICC.KA may be transmitted to the factory IT / OEM 615, and policy rules (otPK usage policy) for otPK.EUICC.KA may be included and transmitted. The otPK usage policy may include at least one of information such as whether it can be reused, reuse method = number of times, unlimited, number of times used = allowed number of times, etc. In the case of applying the otPK usage policy, the EUM / EUM server 600 may configure the otPK usage policy to the eUICC and provide the corresponding otPK usage policy to the factory IT.

[0246] The Factory IT / OEM 615, which has received (step 616) the eUICC encryption key information required for BPP decryption of each eUICC from the EUM / EUM server 600, can map the encryption key information to the M number of subscribed eUICCs and otPK usage policies and store them (step 635) in the Factory IT server 615.

[0247] Thereafter, at a particular point in time, the factory IT / OEM 615 may determine to load the profile onto some N eUICCs or all M eUICCs ordered from the EUM 600. This may be based on a profile preload release request from the service provider (SP) / SP server 605.

[0248] The factory IT / OEM 615 may transmit (step 660) at least one information of the number of configuration files or the list of EIDs to the SP / SP server 605 so that the SP / SP server 605 can prepare configuration files linked to the EIDs in advance as an additional optional procedure. The SP / SP server 605 may order (step 665) configuration files from the configuration file server / server provider 610. In the case where step 660 has been performed in advance and the EID list exists or the EID list is obtained at a specific time point before, the SP / SP server 605 may include the EID information when ordering the configuration file and request the information from the configuration file server / server provider 610. The SP / SP server 605, the configuration file server / server provider 610, and the factory IT / OEM 615 may share (step 650) information that can specify the corresponding order with each other. The information that can specify the corresponding order may be shared as identification information provided by the SP / SP server 605 or the configuration file server / server provider 610 to the factory IT / OEM 615. For example, the identification information may be at least one of information such as a batch ID and an order ID, an ordered profile list or EID list, information about the start and end numbers of the profile list or EID list, a factory serial number, or information about a manufacturer identification number.

[0249] The factory IT / OEM 615 may request a BPP from the profile server / server vendor 610. When requesting a BPP, the factory IT / OEM 615 may transmit (step 655) to the profile server / server vendor 610 the key information corresponding to the eUICC of the corresponding target UE (up to N) among the key information of the eUICC obtained at step 630, where N is the number of UEs to which the SP / SP server 605 is to load the profile. This may be part or all of the key information received previously (at step 630). In the event that the factory IT / OEM 615 receives information about the otPK usage policy from the EUM / EUM server 630, the factory IT / OEM 615 may indicate and transmit the information if otPK reuse is configured as possible. This may be, for example, the value of a reuse flag (resuseFlag).

[0250] In the case where the profile server 610 implements a policy that does not support otPK reuse, the profile server may identify whether the otPK has been received and used before, and return an error and terminate the process when the same otPK is received. Alternatively, the profile server may not identify whether the otPK has been received and used before, but return an error when the reuse flag is set and received and terminate the process by not supporting it regardless of this situation.

[0251] In at least one of the steps of collecting the link information of the profile EID (step 660), the mutually shared order information (step 650), and the encryption key information of the target eUICC (step 655) to install the received profile, the profile server 610 may combine the collected information, create (step 660) an encrypted profile package, and then provide (step 665) the created profile package and the information about eUICC binding to the factory IT / OEM 615.

[0252] The created encrypted configuration file package and each BPP encryption key information may be transmitted (step 665) to the factory IT / OEM 615 in one or more messages, and part or all of the data transmitted in the corresponding message may be provided as signature data.

[0253] The corresponding message transmitted (step 665) may be transmitted including otPK.EUICC.KA in the signature data.

[0254] At step 670, the operation of the factory IT 615 to install the profile of the IFPP in the eUICC may be described. This step may be performed for N eUICCs.

[0255] The factory IT / OEM 615 may inject the configuration file into the UE before the UE is released from the factory. To this end, the factory IT / OEM 615 may obtain and store a series of encryption key information required for decrypting the configuration file from the BPP and the eUICC. The series of encryption key information may include a one-time public key of the EUICC (hereinafter referred to as otPK.EUICC.KA). The series of encryption key information may also include an index ID mapped to otPK.EUICC.KA.

[0256] The factory IT 615 may transmit the BPP and a series of encryption key information required for decrypting the profile in the eUICC from the factory to each UE 620 through a wired / wireless network within the factory. The BPP and a series of encryption key information may be included in one or more messages and transmitted to the UE 620. In the case where the otPK.eUICC.KA is included and transmitted, the otPK.eUICC.KA may be included in the signature data from the profile server and received by the UE 620. For example, the otPK.eUICC.KA may be included in the signature data and received through one of the following. This is not limited to the following examples.

[0257] -SK.DPauth.SIG: The profile server's private key for authentication with the profile server

[0258] -SK.DPpb.SIG: Private key used in the profile server for profile binding of the profile server

[0259] -SK.DPxx.SIG: The private key of the configuration file server, where xx is defined to indicate the use of IFFP

[0260] As described above, SK.DPpb.SIG may be a private key of a profile server used for profile binding in the profile server, or may be a private key of a profile server used by the profile server for IFPP. In DPxx.SIG, xx indicating use may be indicated as specific information indicating xx indicating IFPPP use.

[0261] The UE 620 may provide a function of receiving a BPP from the factory IT 615 and injecting the BPP into the eUICC 625 in the IFPP mode. For example, the corresponding UE 620 may operate in the factory provision mode at the time of receiving the BPP, or the UE 620 may recognize that it should enter the IFPP and initiate the operation at the time of receiving the BPP. Alternatively, the UE 620 may enter the corresponding mode by an event input into the UE by a factory employee, a configuration value, or recognition of a specific virtual private network (VPN). Entering the IFPP mode by a UI or a configuration value may be provided by limiting a UI that is not displayed to the user in a general environment. The UE 620 may transmit the BPP to the eUICC 625 by the LPAf (not shown) as described above or without the LPAf (not shown) (step 675).

[0262] As an example of a message transmitted to the eUICC using LPAf (not shown), it may be included in one or more messages of ES10x and transmitted. Figure 6 An embodiment thereof is described.

[0263] Information that allows identification that a message received by the eUICC 625 from the UE 620 is an operation for IFPP may be received. The eUICC 625 may determine that a profile installation operation is performed for IFPP through the message received from the UE 620 and enter.

[0264] This can be a new function defined for IFPP, an IFPP identifier parameter added to the ES10x message defined in the existing SGP.61 / 62 or SGP.31 / 32, or identification information for factory release that is not included in the (consumer-oriented, M2M-oriented, or IoT-oriented) profile provisioning in a general environment after the release of the UE. For example, the information can be one of the values ​​such as factory serial number, batch ID, manufacturer identification information. It is not limited to this.

[0265] As described above, the UE 620 may receive data including otPK.EUICC.KA or index ID from the profile server, and the data including the corresponding otPK.EUICC.KA or index ID may be included and received in data signed by one of the following. This is not limited to the following examples.

[0266] -SK.DPauth.SIG: The profile server's private key used for authenticating the profile server to the profile server

[0267] -SK.DPpb.SIG: The private key of the profile server used for profile binding by the profile server

[0268] -SP.DPifpp.SIG: The profile server's private key used exclusively by the profile server for IFPP

[0269] UE 620 may transmit the signed data to eUICC 625 again with or without LPAf. eUICC 625 may verify the signature of the profile server 610 on the data received thereby, thereby creating a session key using the pre-stored one-time private key of the eUICC (otSK.EUICC.KA) to decrypt the BPP and process the installation (step 680).

[0270] At (step 680), the eUICC 625 may identify the stored otPK reuse policy or number of uses. If the reuse policy / number of uses is used, the eUICC 625 may terminate the process by returning an error when the number of uses is exceeded. In the case where the otPK reuse policy is allowed or / and the number of reuses is within the predetermined number of reuses, the eUICC 625 may create a session key using the otSK.EUICC.KA mapped to the otPK.EUICC.KA. When the otPK.EUICC.KA is received, the eUICC 625 may use the mapped otSK.EUICC.KA (step 675). Since reuse is allowed, there may be only one otSK.EUICC.KA in the eUICC. In this case, since there is only one otSK.EUICC.KA when the otPK.EUICC.KA is not received (step 675), the eUICC 625 may use the corresponding otSK.EUICC.KA to create a session key. In the event that two or more otSK.EUICC.KA exist and otPK.EUICC.KA is not received, the eUICC 625 may return an error.

[0271] After successfully installing the profile, the eUICC 625 may do one of the following.

[0272] -otPK / SK non-reusable policy: discard the used otSK.EUICC.KA

[0273] -otPK / SK reuse policy: store used otSK.EUICC.KA

[0274] In otSK.EUICC.KA, it can be reused and the strategy of using the number of otPK / SK is used.

[0275] -Deduct and store the used amount. When the used amount is reached, discard the used otSK.EUICC.KA.

[0276] If the profile installation fails, the eUICC 625 may handle it using one of the following methods.

[0277] -otPK / SK cannot be reused: Maintain the existing otSK.EUICC.KA

[0278] -otPK / SK reuse policy: store otSK.EUICC.KA (regardless of success / failure)

[0279] In otSK.EUICC.KA, it can be reused and the strategy of using the number of otPK / SK is used.

[0280] - If it fails, the previous amount used is retained

[0281] At (step 680), in the case that the eUICC 625 stores the otSK.EUICC.KA and the mapped otPK.EUICC.KA together, if the eUICC 625 discards / stores / maintains the otSK.EUICC.KA, the eUICC 625 may also discard / store / maintain the mapped otPK.EUICC.KA.

[0282] The eUICC 625 may transmit the installation result of the profile to the UE with or without LPAf, and the UE may reply to the Factory IT Server 615 (step 685). The eUICC 625 may transmit an installation result message reply to the Factory IT 615, including the installation result data signed by the eUICC and to be recognized by the Profile Server / Server Vendor 610, in addition to the installation result data to be recognized by the Factory IT 615.

[0283] When the factory IT 615 receives a response that the profile installation result is successful, the factory IT 615 can use the reuse policy, and in the case of a reuse quantity, the factory IT 615 can store the number of otPKs used + 1, and if the used quantity has been reached, the factory IT 615 can delete the used key material or change the status of the corresponding key material to use completed. In the case where the reuse policy is used and configured for unlimited use, the factory IT 615 can process without additional operations. When the factory IT 615 receives a profile installation result that is an error, the factory IT 615 can maintain and store the key material used and change the status of the key material (e.g., error, installation error, etc.). In addition, the factory IT 615 can store the used quantity without deduction.

[0284] The factory IT 615 may again reply the profile installation result to the profile server / server vendor 610. The factory IT / OEM 615 may reply the installation results to the profile server / server vendor 610 individually, or collect the results and provide them to the profile server / server vendor 610 in batches at a specific time point. In the case where the processing result is received as the installation result data signed by the eUICC, the profile server / server vendor 610 may verify the signature of the eUICC to identify the processing result. When a successful result is received as the processing result, the profile server / server vendor 610 may complete the use of the otPK.EUICC.KA for the corresponding BPP installation, and manage the otPK.EUICC.KA by discarding (at step 655) the received otPK.EUICC.KA or changing the status of the otPK.EUICC.KA to use completed.

[0285] The profile server / server vendor 610 or factory IT / OEM 615 may optionally provide the corresponding installation results to the SP / SP server 605 .

[0286] Figure 7 7 is a block diagram showing the structures of a profile server 700, a factory IT 720, and a UE 740 in a wireless communication system according to an embodiment of the present disclosure.

[0287] refer to Figure 7 , the profile server 700 according to an embodiment of the present disclosure may include a communication unit 705 , a controller 710 , and an encryption unit 715 .

[0288] The communication unit 705 may transmit data to other devices or receive data from other devices. The communication unit 705 may transmit or receive encryption keys, encryption configuration files, etc. To this end, the communication unit 705 may be equipped with at least one communication module and an antenna.

[0289] The controller 710 may control each component of the profile server 700 to install a profile according to the present disclosure. The specific operation of the controller 710 is as described above. According to one embodiment, the profile server 700 may refer to the information received from the service provider server, the manufacturer's server, or the service provider and the manufacturer to determine whether the order is the same order, and map the profile and eUICC provisioning information of the same order and store them in a storage device (not shown). In addition, the controller 710 may control the operation of preparing in advance by mapping the profile to a specific EID with reference to the EID information received from the service provider. According to another embodiment, the controller 710 may use the information received from the message received through the communication unit 705 to determine whether a profile should be prepared for IFPP to perform an operation by entering an operation of preparing a profile.

[0290] According to another embodiment, the controller 710 may determine whether there is an index ID in the information received from the message received through the communication unit 705, and if there is an index ID, determine whether to verify the signature of the eUICC by including the index ID, and control the creation of the signature value of the profile server by including the index ID.

[0291] According to another embodiment, the controller 710 may determine whether there is a reuse indicator, such as a reuse flag, for otPK.EUICC.KA in the information received from the message received through the communication unit 705 to determine whether the profile server does not support otPK reuse, and process it through the communication unit 705.

[0292] The profile server 700 may receive a message received from the factory IT through the communication unit 705, determine that a request from the corresponding received message is a request for downloading a profile of the IFPP, process an operation to prepare a profile for the factory, and transmit a corresponding processing result to the factory IT through the communication unit 705. The encryption unit 715 may encrypt or decrypt a key or a profile according to the control of the controller 710.

[0293] The encryption unit 715 may include an HSM or be called an HSM itself, and encrypt and decrypt the configuration file without exposing the encryption key. According to the implementation, the encryption unit 715 may be built into the controller 710, or implemented in the form of software code driven by the controller 710.

[0294] refer to Figure 7 , the factory IT 720 according to an embodiment of the present disclosure may include a communication device 725, a control device 730, and a storage device 735. The communication device 725 may transmit data to other devices or receive data from other devices. In the case where the factory IT 720 operates as a single device including the storage device 735, the factory IT 720 may have a separate control device 730 and a storage device 735, which centrally control the communication device 725 and the storage device 735. As described above, the factory IT 720 may be composed of one or more devices.

[0295] The communication device 725 can transmit or receive encryption keys, encryption configuration files, etc. To this end, the communication device 725 can be equipped with at least one communication module and an antenna, etc. According to an embodiment of the present disclosure, in the case where the factory IT 720 operates as a single device including a storage device 735, the communication device 725 may be equipped for the factory IT 720 itself. The factory IT 720 can transmit or receive encryption key information, encryption configuration files, etc. through the communication device 725. In addition, the factory IT 720 can transmit or receive (including encryption index ID). The received configuration file or encryption key, etc. can be transmitted to the UE 740 through the communication device 725, which is determined by the control device 730 of the factory IT 720 and the UE mapped to the corresponding information.

[0296] The storage device 735 of the factory IT 720 may store at least one encrypted configuration file. In addition, the storage device 735 may store encryption key information about at least one encrypted configuration file. In addition, the storage device 735 may also store an index ID mapped to the encryption key information about at least one encrypted configuration file. The storage device 735 may also store an otPK reuse policy mapped to the encryption key information about one encrypted configuration file. When the communication device 725 of the factory IT 720 receives the configuration file installation result, the control device 730 may determine this and update the installation result information of the mapped configuration file, update the result information in the storage device 735, and then provide the result information in batches to the configuration file server 700 at a specific time point. The storage device 735 may include at least one type of storage medium of a hard disk type, a random access memory (RAM), a static random access memory (SRAM), a read-only memory (ROM), an electrically erasable programmable read-only memory (EEPROM), a programmable read-only memory (PROM), a magnetic memory, a magnetic disk, and an optical disk. The factory IT 720 may be implemented in the form of a server, etc.

[0297] refer to Figure 7, UE 740 may include a communication unit 745, a controller 750, a storage device 755, and an eUICC 760. The communication unit 745 may transmit data to or receive data from other devices. The communication unit 745 may receive encryption keys, encryption configuration files, etc. To this end, the communication unit 745 may be equipped with at least one communication module and an antenna, etc. The controller 750 may control each component of the UE 740 to install a configuration file according to the present disclosure. The controller 750 may control the overall operation of the UE 740. For example, the controller 750 may transmit and receive signals through the communication unit 745. In addition, the controller 750 may record and read data in the storage device 755. There may be at least one controller 750. For example, the controller 750 may include a communication processor (CP) that performs communication control and an application processor (AP) that controls an upper layer (such as an application). According to one embodiment, in the case where configuration information is stored in the storage device 755 of the UE, the controller 750 may request the corresponding information from the storage device 755; thereby, the screen display unit (not shown) may display or receive the corresponding information and process additional operations. According to another embodiment, the controller 750 may perform a process in which the UE infers that the information referenced by the profile installation selection may be performed in the factory by matching the data record read through the storage device 755 or the information collected through the controller 750 and the communication unit 745. In addition, the controller 750 may determine whether specific information stored in the UE 740 requires user consent and display it on a screen display unit (not shown).

[0298] The controller 750 may control the UE 740 to perform corresponding operations. According to one embodiment, the controller 750 may include an LPA responsible for driving and controlling the eUICC 760, applications integrated and implemented by the LPA, and applications for managing factory installations. In addition, the controller 750 may include a UE framework that interprets information received by the LPA or application and processes a specific command APDU request to a communication processor (CP), or collects part or all of the requested information from the storage device 755 and replies to the LPA or application.

[0299] The controller 750 may determine an operation of entering the IFPP mode by synthesizing predetermined information acquired from the eUICC 760 through the UE 740 and the communication unit 745, and control the eUICC 760 to enter the IFPP mode. The eUICC 760 may operate according to the control of the controller 750. According to an embodiment of the present disclosure, the eUICC 760 may enter the IFPP mode, process a process of profile installation, and reply a corresponding processing result to the UE 740. The controller 750 according to an embodiment of the present disclosure may receive a response message of the profile information or the profile package received from the factory IT 720, determine whether there is profile installation request information for IFPP from the received profile information or the response message, determine whether to perform profile installation in the factory mode with reference to UE configuration or user input information upon reception, determine whether to enter the general mode or the IFPP mode, determine to enter the IFPP mode, compose a message to be transmitted to the eUICC 760 in order to install the profile using the IFPP, compose the profile information of the profile package into one or more messages, and control the transmission of the corresponding message to the eUICC 760, determine whether to terminate the profile installation process by receiving a processing result received by the UE 740 from the eUICC 760, transmit the processing result to the communication unit 745, and control the UE 740 to enable the communication unit 745 to transmit the processing result to the factory IT 720.

[0300] The storage device 755 may store data, such as basic programs, applications, and configuration information for the operation of the UE 740. In an embodiment of the present disclosure, the storage device 755 may include at least one storage medium of a flash memory type, a hard disk type, a multimedia card micro type, a card type memory (e.g., an SD or XD memory), a magnetic memory, a disk, an optical disk, a random access memory (RAM), a static random access memory (SRAM), a read-only memory (ROM), a programmable read-only memory (PROM), or an electrically erasable programmable read-only memory (EEPROM). The storage device 755 may be implemented as an integrated system on a chip (SoC) together with the controller 750. The controller 750 may perform various operations using various programs, contents, and data stored in the storage device.

[0301] exist Figure 7 In the embodiment, the eUICC 760 is a UICC chip embedded in the UE 740 and can perform functions of storing, managing, and deleting at least one profile. The profile can collectively refer to one or more applications and subscriber authentication information and data information (such as a phone book) stored in an existing UICC card. The eUICC 760 can be included as part of the UE 740, such as Figure 1 shown, and in Figures 2 to 6In the figure, each is represented as a separate module to describe the operation between UE 740 and eUICC 760. eUICC 760 may include a controller, a storage device, and a communication unit for installing a configuration file. Some applications in eUICC 760 may be installed in controller 750, and some functions of LPA may be included in the installed applications.

[0302] According to an embodiment of the present disclosure, the controller of the eUICC 760 may acquire the received profile installation request information of the UE 740 through the communication unit, then acquire the predetermined information and encryption key information about the profile package through the corresponding message information, determine whether the eUICC 760 will enter the IFPP and determine the operation, and thus process the profile installation process of the IFPP and the received information by comparing and verifying it with the information in the storage device of the eUICC 760, perform the installation operation by verifying the received profile package, compose a message, and reply the processing result to the UE 740 through the communication unit. As described in the above-mentioned embodiment of the present disclosure, an example of the information to be processed by comparing and verifying it with the information in the storage device of the eUICC 760 may be information such as an index ID, a reuse policy, or otPK.EUICC.KA.

[0303] However, Figure 7 The components described in are not limited to the above examples. For example, the factory IT 720 may include more or fewer components than the above components. The UE 740 according to various embodiments disclosed in this document may be an electronic device, and the electronic device may be a device in various forms. The electronic device may include, for example, a portable communication device (e.g., a smart phone), a computer device, a portable multimedia device, a portable medical device, a camera, a wearable device, or a household appliance device. The electronic device according to the embodiments of this document is not limited to the above devices.

[0304] It should be understood that the various embodiments of this document and the terms used therein are not intended to limit the technical features described in this document to specific embodiments, but include various modifications, equivalents and / or substitutions of the corresponding embodiments. In conjunction with the description of the accompanying drawings, similar reference numerals may be used for similar or related parts. The nouns in the singular form corresponding to the term may include one or more things unless the relevant context clearly indicates otherwise. In this document, 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" may include any one or all possible combinations of the terms listed together in the corresponding one of the phrases. Terms such as "first" or "second" may be used only to distinguish the corresponding component from other corresponding components, and do not limit the corresponding component in other aspects (such as importance or order). When one (e.g., a first) component is referred to as being "coupled" or "connected" to another (e.g., a second) component, with or without the term "functionally" or "communicatively," it means that one component can be connected to the other component directly (e.g., by wire), wirelessly, or through a third component.

[0305] The term "module" used in this document includes a unit implemented in hardware, software, or firmware, and can be used interchangeably with terms such as logic, logic block, component, or circuit. A module can be an integral forming part or a minimum unit or part of the part that performs one or more functions. For example, according to one embodiment, a module can be implemented in the form of an application specific integrated circuit (ASIC).

[0306] Various embodiments of this document may be implemented as software (e.g., a program) including one or more instructions stored in a storage medium (e.g., an internal memory or an external memory) readable by a machine (e.g., an electronic device). For example, a processor of a machine (e.g., an electronic device) may call and execute at least one command from one or more stored instructions of a storage medium. This enables the device to operate according to at least one of the called instructions to perform at least one function. One or more instructions may include code generated by a compiler or code executable by an interpreter. The device-readable storage medium may be provided in the form of a non-transitory storage medium. Here, "non-transitory" only 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 a case where data is semi-permanently stored in a storage medium and a case where data is temporarily stored in a storage medium.

[0307] According to an embodiment, the methods according to various embodiments disclosed in this document may be included and provided in a computer program product. The computer program product may be traded between a buyer and a seller as a commodity. The computer program product may be distributed in the form of a device-readable storage medium (e.g., a compact disc read-only memory (CD-ROM)), or may be distributed via an application store (e.g., PlayStore). TM ) distribution (e.g., downloading or uploading), or online distribution, or direct distribution between two user devices (e.g., smart phones). In the case of online distribution, at least a portion of the computer program product may be at least temporarily stored or temporarily generated in a device-readable storage medium (such as a memory of a manufacturer's server, an application store's server, or a relay server).

[0308] According to various embodiments, each component (e.g., module or program) in the above-mentioned components may include a single entity or multiple entities. According to various embodiments, one or more components or operations in the above-mentioned corresponding components may be omitted, or one or more other components or operations may be added. Alternatively or additionally, multiple components (e.g., module or program) may be integrated into one component. In this case, the integrated component may perform one or more functions of each component in the multiple components in the same or similar manner as performed by the corresponding components in the multiple components before integration. According to various embodiments, the operations performed by modules, programs or other components may be performed sequentially, in parallel, repeatedly or in a heuristic manner, or one or more operations in these operations may be performed or omitted in different orders, or one or more other operations may be added.

[0309] In the specific embodiments of the present disclosure described above, the components included in the present disclosure are expressed as singular or plural, depending on the specific embodiments presented. However, for the convenience of description, singular or plural expressions are appropriately selected for the presented situations, and the present disclosure is not limited to singular or plural components, and even if a component is expressed in the plural, the component may also be composed of the singular, or even if a component is expressed in the singular, the component may also be composed of the plural.

[0310] In the detailed description of the present disclosure, although specific embodiments have been described, various modifications can be made without departing from the scope of the present invention. Therefore, the scope of the present disclosure should not be limited to the described embodiments, but should be defined by the claims described below and the equivalents of the claims.

Claims

1. A method performed by a factory in a wireless communication system, the method comprising: Acquire, from the first server, encryption key information related to a plurality of embedded universal integrated circuit cards eUICCs, wherein the encryption key information includes a one-time public key of the eUICC and an index ID associated with a one-time private key matching the one-time public key of the eUICC; storing encryption key information related to the plurality of eUICCs; transmitting encryption key information related to the plurality of eUICCs to a profile server; receiving, from the profile server, a plurality of binding profile packages (BPPs) based on encryption key information related to the plurality of eUICCs; and transmitting, to the terminal, eUICC encryption key information and BPP that match the eUICC of the terminal among the plurality of BPPs and encryption key information related to the plurality of eUICCs, The eUICC of the terminal is configured to: verify the signature of the profile server based on the BPP and encryption key information related to the eUICC, and decrypt the BPP to install the profile in the eUICC of the terminal.

2. The method according to claim 1, further comprising: receiving a configuration file installation result from the terminal; as well as The configuration file installation result is transmitted to the configuration file server.

3. The method according to claim 1, further comprising: transmitting to a second server a list of the number of profiles associated with the eUICC identifiers EID and said eUICC identifiers, The second server is configured to order a plurality of configuration files from the configuration file server based on the number of configuration files associated with the EID and the list of the EID.

4. The method according to claim 1, further comprising: determining to load a configuration file on some or all of the plurality of eUICCs after storing encryption key information related to the plurality of eUICCs, The decryption of the BPP is performed by creating a session key based on the one-time private key of the eUICC and the index ID.

5. A method performed by a terminal in a wireless communication system, the method comprising: receiving from a factory the encryption key information related to the eUICC and the BPP that match the eUICC of the terminal among the plurality of binding profile packages BPP and the encryption key information related to the plurality of embedded universal integrated circuit cards eUICC; verifying a signature of a profile server based on the BPP and encryption key information related to the eUICC; decrypting the BPP if authentication of the profile server is complete; as well as Install the profile by decrypting the BPP, wherein the plurality of BPPs and encryption key information related to the plurality of eUICCs are transmitted from a first server to the factory, The encryption key information includes a one-time public key of the eUICC and an index ID associated with a one-time private key matching the one-time public key of the eUICC, and The multiple BPPs are created based on a one-time public key of the eUICC.

6. The method according to claim 5, further comprising: The results of the profile installation are emitted to the factory.

7. The method according to claim 5, further comprising: A plurality of profile orders are transmitted from the second server to the profile server based on the number of profiles associated with the eUICC identifiers EID transmitted from the factory and the list of EIDs.

8. The method according to claim 5, wherein: Decryption of the BPP is performed by creating a session key based on the one-time private key of the eUICC and the index ID.

9. A factory in a wireless communication system, the factory comprising: a transceiver capable of transmitting and receiving at least one signal; as well as a controller, coupled to the transceiver, Wherein, the controller is configured as: Acquire, from the first server, encryption key information related to a plurality of embedded universal integrated circuit cards eUICCs, wherein the encryption key information includes a one-time public key of the eUICC and an index ID associated with a one-time private key matching the one-time public key of the eUICC; storing encryption key information related to the plurality of eUICCs, transmitting encryption key information related to the plurality of eUICCs to a profile server; receiving from the profile server a plurality of binding profile packages (BPPs) based on encryption key information related to the plurality of eUICCs, and transmitting, to the terminal, eUICC encryption key information and BPP that match the eUICC of the terminal among the plurality of BPPs and encryption key information related to the plurality of eUICCs, The eUICC of the terminal is configured to: verify the signature of the profile server based on the BPP and encryption key information related to the eUICC, and decrypt the BPP to install the profile in the eUICC of the terminal.

10. The plant according to claim 9, wherein: The controller is also configured to: receiving a configuration file installation result from the terminal, and The configuration file installation result is transmitted to the configuration file server.

11. The plant according to claim 9, wherein: The controller is also configured to: transmitting to a second server a list of the number of profiles associated with the eUICC identifiers EID and said EIDs, The second server is configured to order a plurality of configuration files from the configuration file server based on the number of configuration files associated with the EID and the list of the EID.

12. The plant according to claim 9, wherein: The controller is also configured to: determining to load a configuration file on some or all of the plurality of eUICCs after storing encryption key information related to the plurality of eUICCs, The decryption of the BPP is performed by creating a session key based on the one-time private key of the eUICC and the index ID.

13. A terminal in a wireless communication system, the terminal comprising: a transceiver capable of transmitting and receiving at least one signal; as well as a controller, coupled to the transceiver, Wherein, the controller is configured as: receiving from a factory the encryption key information related to the eUICC and the BPP that match the eUICC of the terminal among the plurality of binding profile packages BPP and the encryption key information related to the plurality of embedded universal integrated circuit cards eUICC; verifying a signature of a profile server based on the BPP and encryption key information related to the eUICC; decrypting the BPP if authentication of the profile server is complete; and decrypt the BPP to install the configuration file, wherein the plurality of BPPs and encryption key information related to the plurality of eUICCs are transmitted from a first server to the factory, The encryption key information includes a one-time public key of the eUICC and an index ID associated with a one-time private key matching the one-time public key of the eUICC, and The multiple BPPs are created based on the one-time public key of the eUICC. The terminal according to claim 13 , wherein the controller is further configured to transmit a configuration file installation result to the factory.

15. The terminal according to claim 13, wherein: Decryption of the BPP is performed by creating a session key based on the one-time private key of the eUICC and the index ID.

Images