Method and apparatus for processing upon delay in provisioning large number of profiles in wireless communication system
The method addresses the inefficiency in provisioning profiles by determining and managing delayed processing in the profile server, enabling efficient profile installation and immediate network access without real-time connections, enhancing the profile server's processing efficiency and user convenience.
Patent Information
- Application Number
- PCT/KR2024/006647
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-16
- Filing Date
- 2024-05-16
- Publication Date
- 2024-11-21
AI Technical Summary
Current methods for provisioning profiles in wireless communication systems, such as those using eUICCs, face challenges in efficiently handling large numbers of profile requests, leading to potential delays and inefficiencies, especially in factory environments where real-time connections may not be guaranteed.
A method and apparatus that allow a profile server to determine if delayed processing will occur when generating bound profile packages (BPPs) and provide comeback time information to the terminal manufacturer server, enabling the server to manage and transmit BPPs accordingly, ensuring efficient processing and installation of profiles without real-time connections.
This approach enhances the efficiency of profile server processing for a large number of profiles, allowing for pre-installation on eSIM terminals and reducing user inconvenience by enabling immediate network access without the need for real-time connections, thus improving convenience and service provisioning.
Smart Images

Figure KR2024006647_21112024_PF_FP_ABST
Abstract
Description
Method and device for handling delay in mass profile preparation in wireless communication system
[0001] The present disclosure relates to a method and device for provisioning profiles in a wireless communication system. Specifically, the present disclosure relates to a method and device for requesting a large number of profiles from a terminal manufacturer server to a profile server for provisioning to eUICCs (embedded universal integrated circuit cards) of terminals, and providing processing results thereof.
[0002] 5G mobile communication technology defines a wide frequency band to enable fast transmission speeds and new services, and can be implemented not only in the sub-6GHz frequency band, such as 3.5 gigahertz (3.5GHz), but also in the ultra-high frequency band called millimeter wave (mmWave), such as 28GHz and 39GHz ('above 6GHz'). In addition, for 6G mobile communication technology, which is called the system after 5G communication (beyond 5G), implementation in the terahertz band (for example, the 3 terahertz (3THz) band at 95GHz) is being considered to achieve a transmission speed that is 50 times faster than 5G mobile communication technology and an ultra-low latency time that is reduced to one-tenth.
[0003] In the early stages of 5G mobile communication technology, the goal is to support services and meet performance requirements for enhanced mobile broadband (eMBB), ultra-reliable low-latency communications (URLLC), and massive machine-type communications (mMTC). These include beamforming and massive MIMO to mitigate path loss of radio waves in ultra-high frequency bands and increase the transmission distance of radio waves, support for various numerologies (such as operation of multiple subcarrier intervals) and dynamic operation of slot formats for efficient use of ultra-high frequency resources, initial access technology to support multi-beam transmission and wideband, definition and operation of BWP (band-width part), new channel coding methods such as LDPC (low density parity check) codes for large-capacity data transmission and polar codes for reliable transmission of control information, L2 pre-processing, and dedicated networks specialized for specific services. Standardization has been made for network slicing, etc.
[0004] Currently, discussions are underway to improve and enhance the initial 5G mobile communication technology in consideration of the services that 5G mobile communication technology was intended to support, and physical layer standardization is in progress for technologies such as V2X (vehicle-to-everything) to help autonomous vehicles make driving decisions and increase user convenience based on their own location and status information transmitted by vehicles, NR-U (new radio unlicensed) for the purpose of system operation that complies with various regulatory requirements in unlicensed bands, NR terminal low power consumption technology (UE power saving), non-terrestrial network (NTN), which is direct terminal-satellite communication to secure coverage in areas where communication with terrestrial networks is impossible, and positioning.
[0005] In addition, standardization of radio interface architecture / protocols for technologies such as intelligent factories (industrial internet of things, IIoT) to support new services through linkage and convergence with other industries, integrated access and backhaul (IAB) that provides nodes for expanding network service areas by integrating wireless backhaul links and access links, mobility enhancement technologies including conditional handover and dual active protocol stack (DAPS) handover, and 2-step random access (2-step RACH for NR) that simplifies random access procedures is also in progress, and standardization of system architecture / services for 5G baseline architecture (e.g., service-based architecture, service-based interface) for grafting network functions virtualization (NFV) and software-defined networking (SDN) technologies, and mobile edge computing (MEC) that provides services based on the location of the terminal is also in progress.
[0006] Once these 5G mobile communication systems are commercialized, an explosive increase in connected devices will be connected to the communication network, necessitating enhanced functionality and performance of 5G mobile communication systems and integrated operation of these connected devices. To this end, new research will be conducted on improving 5G performance and reducing complexity, supporting AI services, metaverse services, and drone communications by leveraging extended reality (XR), artificial intelligence (AI), and machine learning (ML) to efficiently support augmented reality (AR), virtual reality (VR), and mixed reality (MR).
[0007] In addition, the development of these 5G mobile communication systems will serve as the basis for the development of new waveforms to ensure coverage in the terahertz band of 6G mobile communication technology, multi-antenna transmission technologies such as full-dimensional MIMO (FD-MIMO), array antennas, and large-scale antennas, metamaterial-based lenses and antennas to improve the coverage of terahertz band signals, high-dimensional spatial multiplexing technology using orbital angular momentum (OAM), reconfigurable intelligent surface (RIS) technology, as well as full duplex technology to improve the frequency efficiency and system network of 6G mobile communication technology, satellite, AI-based communication technology that utilizes artificial intelligence (AI) from the design stage and internalizes end-to-end AI support functions to realize system optimization, and next-generation distributed computing technology that realizes services with complexity that exceeds the limits of terminal computing capabilities by utilizing ultra-high-performance communication and computing resources. It will be possible.
[0008] The technical problem to be achieved in the present disclosure is to provide a device and method capable of effectively providing a service in a wireless communication system.
[0009] The purpose of this disclosure is to support the operation of injecting and installing a profile into a terminal at a factory.
[0010] According to one of the various embodiments of the disclosure, a method performed by a profile server providing a profile to be provisioned to an eUICC (embedded universal integrated circuit card) may include the steps of: receiving a provision request for a plurality of bound profile packages (BPPs) from a terminal manufacturer server; determining whether a delay processing occurs when generating a BPP according to the plurality of BPP provision requests; if a delay processing does not occur when generating a BPP according to the plurality of BPP provision requests, generating the requested BPPs and transmitting them to the terminal manufacturer server; and if it is determined that a delay processing will occur when generating a BPP according to the plurality of BPP provision requests, transmitting a processing time limit (comeback time) information for processing the plurality of BPP provision requests to the terminal manufacturer server.
[0011] The method of the above profile server may further include a step of generating only BPPs corresponding to some of the plurality of BPP provision requests and transmitting them to the terminal manufacturer server, if it is determined that a delay in processing will occur when generating BPPs according to the plurality of BPP provision requests.
[0012] The above multiple BPP provision requests may include information indicating that some of the requested BPPs are allowed to be transmitted.
[0013] The method of the above profile server may further include a step of transmitting to the terminal manufacturer at least one of an error message, some of the BPPs requested for creation that have been completed, or the remaining time until the creation of all of the BPPs requested for creation is completed, if a connection request from the terminal manufacturer is received before the processing time limit has elapsed.
[0014] The method of the above profile server may further include a step of transmitting, to the terminal manufacturer, BPPs among the BPPs for which creation has been completed but which have not been previously transmitted to the terminal manufacturer, when a connection request is received from the terminal manufacturer after the processing time limit has elapsed.
[0015] The BPP provision request received from the terminal manufacturer server may include information indicating that it is a BPP request for IFPP (in factory profile provisioning).
[0016] The method of the above profile server may further include the step of receiving a request for information on BPP generation capability from the terminal manufacturer server; and the step of transmitting information on the BPP generation capability of the profile server to the terminal manufacturer server.
[0017] According to another of the various embodiments of the present disclosure, a method performed by a terminal manufacturer server performing profile provisioning on an eUICC (embedded universal integrated circuit card) may include the steps of: transmitting a provision request for a plurality of bound profile packages (BPPs) to a profile server; receiving, from the profile server, information on a processing time (comeback time) for the plurality of BPP provision requests; and, after the processing time has elapsed, accessing the profile server to receive the requested BPPs.
[0018] According to another of the various embodiments of the present disclosure, a profile server for providing a profile to be provisioned to an eUICC (embedded universal integrated circuit card) includes a communication unit; and a control unit, wherein the control unit is configured to receive a request for provision of a plurality of BPPs (bound profile packages) from a terminal manufacturer server, determine whether a delay occurs when generating a BPP according to the plurality of BPP provision requests, and if a delay does not occur when generating a BPP according to the plurality of BPP provision requests, generate the requested BPPs and transmit them to the terminal manufacturer server, and if it is determined that a delay will occur when generating a BPP according to the plurality of BPP provision requests, transmit information on a processing time limit (comeback time) for processing the plurality of BPP provision requests to the terminal manufacturer server.
[0019] According to various embodiments of the present disclosure, a device and method for effectively providing a service in a mobile communication system can be provided.
[0020] According to various embodiments of the present invention, efficiency can be increased in the process of a profile server performing processing on a large number of profiles.
[0021] The effects that can be obtained from the present disclosure are not limited to the effects mentioned in the various embodiments, and other effects that are not mentioned can be clearly understood by a person having ordinary skill in the art to which the present disclosure belongs from the description below.
[0022] FIG. 1 is a diagram illustrating the relationship between components for provisioning a profile according to one embodiment of the present disclosure.
[0023] FIG. 2A and FIG. 2B are exemplary diagrams of a process for requesting and receiving a profile from a profile server / server vendor in a factory IT server / OEM according to one embodiment of the present disclosure.
[0024] FIG. 3 is an exemplary diagram illustrating a procedure for requesting a large number of profiles from a Factory IT / OEM to a profile server / server vendor according to one embodiment of the present disclosure.
[0025] Figure 4 is an exemplary diagram illustrating the judgment of a profile server according to one embodiment of the present disclosure (when a BPPs request including otPK.EUCC.KA is received).
[0026] FIG. 5 is an exemplary diagram showing the judgment of a profile server according to one embodiment of the present disclosure.
[0027] Figure 6 is an exemplary diagram illustrating the judgment of a profile server according to one embodiment of the present disclosure (when a BPPs request is received that does not include otPK.EUCC.KA).
[0028] FIG. 7 is an exemplary diagram illustrating a factory IT / OEM judgment according to one embodiment of the present disclosure.
[0029] FIG. 8 is an exemplary diagram illustrating a factory IT / OEM judgment according to one embodiment of the present disclosure.
[0030] FIG. 9 is a block diagram showing the structure of a profile server, factory IT, and terminal in a wireless communication system according to one embodiment of the present disclosure.
[0031] Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the attached drawings. It should be noted that, where possible, identical components are represented by identical reference numerals throughout the attached drawings. Furthermore, detailed descriptions of well-known functions and configurations that may obscure the gist of the present invention will be omitted.
[0032] In describing the embodiments of this disclosure, descriptions of technical details that are well known in the technical field to which the present invention pertains and are not directly related to the present disclosure will be omitted. This is to convey the gist of the present disclosure more clearly without obscuring it by omitting unnecessary explanations.
[0033] For the same reason, some components in the attached drawings are exaggerated, omitted, or schematically depicted. Furthermore, the dimensions of each component do not entirely reflect its actual size. Identical or corresponding components in each drawing are assigned the same reference numbers.
[0034] The advantages and features of the present disclosure, and methods for achieving them, will become clearer with reference to the embodiments described below in detail with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below and may be implemented in various different forms. These embodiments are provided solely to ensure that the present disclosure is complete and to fully inform those skilled in the art of the scope of the invention, and the present disclosure is defined solely by the scope of the claims. Like reference numerals designate like elements throughout the specification.
[0035] At this time, it will be understood that each block of the processing flowchart drawings and combinations of the flowchart drawings can be performed by computer program instructions. These computer program instructions can be installed in a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing equipment, so that the instructions executed by the processor of the computer or other programmable data processing equipment create a means for performing the functions described in the flowchart block(s). These computer program instructions can also be stored in a computer-available or computer-readable memory that can direct a computer or other programmable data processing equipment to implement the functions in a specific manner, so that the instructions stored in the computer-available or computer-readable memory can also produce a manufactured item that includes an instruction means for performing the functions described in the flowchart block(s). Since the computer program instructions may be installed on a computer or other programmable data processing device, a series of operational steps may be performed on the computer or other programmable data processing device to create a computer-executable process, and the instructions that cause the computer or other programmable data processing device to perform the steps for performing the functions described in the flowchart block(s) may also provide steps for performing the functions described in the flowchart block(s).
[0036] Additionally, each block may represent a module, segment, or portion of code that contains one or more executable instructions for performing a specific logical function(s). It should also be noted that in some alternative implementation examples, the functions described in the blocks may occur out of order. For example, two blocks depicted in succession may actually be executed substantially concurrently, or the blocks may sometimes be executed in reverse order, depending on their corresponding functions.
[0037] Here, the term '~ unit' used in the present embodiment means software or hardware components such as FPGA (field programmable gate array) or ASIC (application specific integrated circuit), and the '~ unit' performs certain roles. However, the '~ unit' is not limited to software or hardware. The '~ unit' may be configured to be on an addressable storage medium and may be configured to play one or more processors. Accordingly, as an example, the '~ unit' includes components such as software components, object-oriented software components, class components, and task components, processes, functions, properties, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and '~ units' may be combined into a smaller number of components and '~ units' or further separated into additional components and '~ units'. Additionally, components and '~parts' may be implemented to regenerate one or more CPUs within a device or secure multimedia card.
[0038] Hereinafter, the base station is an entity that performs resource allocation of a terminal, and may be at least one of a Node B, a BS (base station), an eNB (eNode B), a gNB (gNode B), a wireless access unit, a base station controller, or a node on a network. The terminal may include a UE (user equipment), an MS (mobile station), a cellular phone, a smartphone, a computer, or a multimedia system capable of performing a communication function. In addition, the embodiments of the present disclosure may be applied to other communication systems having a similar technical background or channel type to the embodiments of the present disclosure described below. In addition, the embodiments of the present disclosure may be applied to other communication systems with some modifications without significantly departing from the scope of the present disclosure at the discretion of a person having skilled technical knowledge. For example, the 5th generation mobile communication technology (5G, new radio, NR) developed after LTE-A (long term evolution-advanced) may be included here, and the 5G below may also be a concept that includes the existing LTE (long term evolution), LTE-A, and other similar services. In addition, the present disclosure may be applied to other communication systems with some modifications within a scope that does not significantly deviate from the scope of the present disclosure, as judged by a person having skilled technical knowledge.
[0039] In the following description, terms used to identify connection nodes, terms referring to network entities or network functions (NFs), terms referring to messages, terms referring to interfaces between network objects, terms referring to various identification information, etc. are examples provided for convenience of explanation. Therefore, the present invention is not limited to the terms described below, and other terms referring to objects having equivalent technical meanings may be used.
[0040] For convenience of explanation below, some terms and names defined in the 3rd generation partnership project (3GPP) LTE (long term evolution) standard and / or 3GPP NR (new radio) standard may be used. However, the present invention is not limited to the above terms and names, and can be equally applied to systems conforming to other standards.
[0041] For the convenience of explanation below, the present disclosure uses terms and names defined in the remote SIM provisioning (RSP) specifications (SGP.XX series), which are standards defined by the GSMA (global system for mobile communications association, GSM association) among the existing eSIM standards. However, the present disclosure is not limited by the above terms and names, and can be equally applied to eSIMs that comply with other standards. A universal integrated circuit card (UICC) is a smart card that is 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 connecting to the network of a mobile communication operator. Examples of such an access control module include a universal subscriber identity module (USIM), a subscriber identity module (SIM), an Internet protocol multimedia service identity module (ISIM), etc.
[0042] Based on the discussion described above, the present disclosure provides a method and device for installing profiles in an eUICC of a terminal in a factory environment of a manufacturer terminal in a wireless communication system.
[0043] The present disclosure can provide a method and device for effectively providing a result of processing profiles one or more times in a terminal manufacturer factory environment to one eUICC in a wireless communication system.
[0044] A UICC containing a USIM is commonly referred to as a USIM card. Similarly, a UICC containing a SIM module is commonly referred to as a SIM card. It should be noted that the term "SIM card" in the following description may be used in its general sense to include UICC cards, USIM cards, and UICCs containing ISIM. Even though it is referred to as a SIM card, the technical application thereof can be equally applied to USIM cards, ISIM cards, or general UICC cards.
[0045] SIM cards store the personal information of mobile subscribers and can enable secure mobile communication by performing subscriber authentication and generating traffic security keys when connecting to a mobile communication network.
[0046] SIM cards are generally manufactured as dedicated cards for mobile carriers upon request from specific mobile carriers when manufacturing SIM cards, and authentication information for network access of the carrier, such as the USIM (universal subscriber identity module) application and IMSI (international mobile subscriber identity), K value, OPc (operator constant) value, etc. are pre-loaded on the card before shipment. Therefore, the manufactured SIM card is delivered to the mobile carrier and provided to the subscriber, and if necessary, management such as installation, modification, and deletion of applications in the UICC can be performed using technologies such as OTA (over the air).
[0047] Subscribers can access their mobile carrier's network and application services by inserting a UICC card into their mobile terminal. Furthermore, when replacing their mobile terminal, subscribers can transfer the UICC card from their existing device to the new one, allowing them to use the authentication information, mobile phone number, and personal phonebook stored on the UICC card on their new device.
[0048] However, SIM cards can present inconveniences for mobile device users when accessing services from other carriers. Users may experience the inconvenience of having to physically obtain a SIM card to access services from their mobile carrier. For example, when traveling to another country, obtaining a local SIM card can be inconvenient. While roaming services can alleviate some of this inconvenience, they can also face the problem of high fees and service inaccessibility if a contract with another carrier is not in place.
[0049] Meanwhile, if a SIM module is downloaded and installed remotely on a UICC card, this inconvenience can be significantly resolved. For example, a user can download a SIM module of a mobile communication service they wish to use onto a UICC card at a desired time. Such a UICC card can also download and install multiple SIM modules, and select and use only at least one SIM module among them. Such a UICC card can be fixed or not fixed to a terminal. A UICC fixed to a terminal is typically referred to as an eUICC, but in the present disclosure, a UICC card that can remotely download and select a SIM module can be collectively referred to as an eUICC. In other words, among UICC cards that can remotely download and select a SIM module, a UICC card that is fixed to a terminal and a UICC card that is not fixed can be collectively referred to as an eUICC. In addition, the downloaded SIM module information can be collectively referred to as a profile. Examples of profiles can be further categorized by their intended use, such as provisioning profiles, which are restricted to initial setup (e.g., only allowing profile server access), operational profiles, which do not have such restrictions, and test profiles, which are restricted to testing purposes. Provisioning profiles may also be referred to as bootstrap profiles.
[0050] To install a profile in an eUICC, it is typically assumed that the terminal user downloads the profile through a real-time network connection to a profile download server after the terminal is shipped. Currently, according to the remote profile provisioning standards, which are eSIM standardization standards defined by the GSMA, such as SGP.21 / 22, a remote SIM provisioning standard for consumer terminals, SGP.31 / 32, a remote SIM provisioning standard for IoT terminals, and SGP.01 / 02, a remote SIM provisioning standard for M2M terminals, the terminal can be defined as a process in which a terminal is connected to a profile download server in real-time over a network, multiple messages are exchanged between the terminal and the profile server, and common mutual authentication is performed during this process before the profile is downloaded. However, the terminal cannot always assume a network connection to the profile download server when downloading the profile. Therefore, to resolve this issue, the provisioning profile, a limited-purpose profile that only provides connectivity for initial setup of the terminal, was introduced in SGP.21 / 22. Accordingly, terminal manufacturers may ship eUICCs equipped with provisioning profiles. Furthermore, manufacturers may pre-install the telecommunications carrier's operational profile, which does not have the above-mentioned usage restrictions, on eUICCs based on contracts with service providers.
[0051] Meanwhile, a new work item for provisioning profiles to terminals at the factory has recently been approved by the GSMA (GSM Association, a telecommunications operator association), and discussions on standardization of devices and methods for provisioning profiles to terminals at the factory will be held as SGP.41 (technical requirements specification) and SGP.42 (technical specification (planned)).
[0052] In the present disclosure, the function for provisioning a profile at the factory is referred to as the IFPP (in factory Profile provisioning) function, and when entering a state supporting the IFPP function, it can be indicated as entering the IFPP mode or the 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 IFPP mode. For example, a specific entity such as a terminal, a local profile assistant (LPA), an eUICC, a profile server, a factory IT, a service provider (SP) server, or an eUICC manufacturer (EUM) server may be an entity that further supports the IFPP mode, or may be an entity that only supports the IFPP function. For example, SM-DP+, which is one of the profile servers, may be a server that supports the consumer-oriented remote SIM provisioning function defined in SGP.21 / 22, but additionally supports some of the IFPP functions defined in SGP.41 / 42. Alternatively, SM-DP+, which is a profile server, may be a profile server that only supports the IFPP function. A profile server operating in IFPP state may be referred to in this disclosure as, for example, profile server f, SM-DPf.
[0053] In the present disclosure, a UICC (universal integrated circuit card) is a smart card inserted into a mobile communication terminal, and stores personal information such as network access authentication information, a phone book, and SMS (short message service) of a mobile communication subscriber, and performs subscriber authentication and traffic security key generation when connecting to a mobile communication system such as GSM, WCDMA (wideband code division multiple access), LTE, 5G, etc., thereby enabling safe use of mobile communication. The UICC may be loaded with communication applications such as a SIM (subscriber identification module), USIM (universal SIM), and ISIM (IP multimedia SIM) depending on the type of mobile communication network to which the subscriber is connected, and may also provide a high-level security function for loading various application applications such as an electronic wallet, ticketing, and electronic passport.
[0054] In the present disclosure, the eUICC (embedded UICC) is not limited to a security module built into a terminal, and may include a removable security module that can be inserted and removed from the terminal. The eUICC can download and install profiles in real time or non-real time via a wired or wireless network. The eUICC can be referred to as a UICC that can download and install profiles. In the case where the eUICC installs a profile in a factory environment where real-time communication with the outside is difficult, the SM-DPf server that created the profile can install the profile on the terminal through a device that injects the profile into the eUICC via wired or wireless from the factory IT / OEM (original equipment manufacturer).
[0055] The method of downloading and installing a profile on an eUICC in the present disclosure can also be applied to a removable UICC that can be inserted and removed from a terminal, as described above. For example, the embodiments of the present disclosure can be applied to a removable UICC that can download and install a profile. In the present disclosure, the eUICC unique identification number (eUICC ID) may be referred to as an EID. The UICC referred to in the present disclosure may be used interchangeably with a SIM, and the term eUICC may be used interchangeably with an eSIM.
[0056] In the present disclosure, a profile may mean an application, file system, authentication key value, etc. stored in a UICC packaged in software form. In addition, a profile may be named as connection information. In addition, a USIM profile in the present disclosure may mean the same meaning as a profile or information included in a USIM application in a profile packaged in software form. In the present disclosure, a profile package or an encrypted profile package (bound profile package, BPP) may be used interchangeably with a profile or as a term indicating a data object of a specific profile, and may be named a profile TLV (tag, length, value) or a profile package TLV. A profile identifier may be referred to as an integrated circuit card identifier (ICCID) indicating a unique identification number of the profile. If a profile package is encrypted using an encryption parameter, the encrypted profile package may be named a protected profile package (PPP) or a protected profile package TLV (PPP TLV). When a profile package is encrypted using encryption parameters that can only be decrypted by a specific eUICC, the profile package may be referred to as a bound profile package (BPP) or a bound profile package TLV (BPP TLV). A profile package TLV may be a data set representing information that constitutes a profile in the TLV (tag, length, value) format.
[0057] In the present disclosure, a profile server is a server that provides a function to create a profile, encrypt a created profile, store a created profile, create a profile remote management command, encrypt a created profile remote management command, or provide an IFPP mode, and may be expressed as SM-DP (subscription manager data preparation), SM-DP+ (subscription manager data preparation plus), or SM-SR (subscription manager secure routing). As mentioned above, a profile server that operates by providing an IFPP function in the present invention may be expressed as SM-DPf.
[0058] The term 'terminal' or 'device' used in the present disclosure may be referred to as a mobile station (MS), user equipment (UE), mobile equipment (ME), user terminal (UT), wireless terminal, access terminal (AT), terminal, subscriber unit (SS), subscriber station (SS), wireless device, wireless communication device, wireless transmit / receive unit (WTRU), mobile node, mobile, or other terms. Various embodiments of the terminal may include a cellular telephone, a smart phone having a wireless communication function, a personal digital assistant (PDA) having a wireless communication function, a wireless modem, a portable computer having a wireless communication function, a photographing device such as a digital camera having a wireless communication function, a gaming device having a wireless communication function, a music storage and playback home appliance having a wireless communication function, an Internet home appliance capable of wireless Internet access and browsing, as well as portable units or terminals incorporating combinations of such functions. Additionally, depending on the performance characteristics supported, the terminal may include an M2M (machine-to-machine) terminal, an MTC (machine type communication) terminal / device, or an IoT terminal / device. In the present disclosure, the terminal may also be referred to as an electronic device or simply a device. A terminal (120) that provides the function of installing a profile using an eUICC may also be referred to as an eSIM terminal.
[0059] In this disclosure, EUM refers to an eUICC manufacturer, a manufacturer that produces and provides personalized eUICCs. Information transmitted by the EUM can be transmitted online or offline through channels between the EUM server or separate components. According to an embodiment of the present disclosure, the EUM may refer to an EUM server or a role performed by the EUM.
[0060] In the present disclosure, a terminal or device may include software or an application installed in the terminal or device to control the UICC or eUICC. The software or application may be, for example, an application such as a local profile assistant (LPA), a SIM manager, or an IoT profile assistant (IPA). The software or functions may be provided in an integrated manner. For example, the LPA and IPA may be provided as a single integrated app. In the present disclosure, when the software or application installed in the terminal or device to control the UICC or eUICC operates as an IFPP function, it may be collectively referred to as FPA or LPAf.
[0061] In the present disclosure, an APDU (application protocol data unit) may be a message format or message that a controller in a terminal or device exchanges with an eUICC. An APDU is a pair of a command and a response, and an APDU command and an APDU response may be defined in ETSI 102.221 with reference to ISO 7816. As defined in ETSI 102.221, an APDU command has a structure of a CLA (class of instruction), INS (Instruction), P1 (instruction parameter 1), P2 (instruction parameter 2) as a header of the APDU, and Lc (number of bytes in the command data field), data, and Le (number of bytes expected in response of the command) as a body, and an APDU response has a structure of an optional data field, SW1 (status byte 1), and SW2 (status byte 2), and a detailed description thereof may refer to the ETSI 102.221 standard. Application messages transmitted from LPA or terminals can be transmitted to eUICC in the form of APDU, and the information transmitted at this time can be included in the data of the APDU and transmitted.
[0062] 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 stored in an eUICC used in the AKA authentication algorithm, and OPc in the present disclosure may be a parameter value that may be stored in an eUICC used in the AKA authentication algorithm.
[0063] In the present disclosure, NAA is a network access application, which may be an application such as a USIM or ISIM stored in a UICC for accessing a network. NAA may be a network access module.
[0064] In this disclosure, end user, user, subscriber, service subscriber, and user may be used interchangeably as a user of a terminal.
[0065] In the present disclosure, factory IT refers to a device that handles provisioning of specific data or settings to a terminal during the manufacturing process, and may refer to a module that includes a function for downloading a profile to the terminal, and may further include a function for acquiring and storing profiles from a profile server, or may be a device that can perform a function for collecting profile processing results and transmitting them. Factory IT may be used interchangeably with factory IT equipment, factory IT server, factory provisioning equipment, factory server, OEM, and terminal manufacturer server, and even if expressed as a server hereinafter, factory IT in the present invention may also be composed of one or more modules, for example, a server that acquires, collects, stores, or processes data and transmits it, an eSIM terminal, and a terminal that acquires settings or data or a processing result from a contact point.
[0066] In this disclosure, the term "OEM" may be used interchangeably with "terminal manufacturer" and "manufacturer." Some of the OEM's devices in this disclosure may be connected wirelessly or wired only within the manufacturer's internal network, not allowing access to external networks. For example, data storage servers used for the manufacturing process or communication devices that inject profiles into terminals may not provide network connectivity outside the manufacturer and may only be connected to the company's internal network. The profile storage server within the manufacturer may be the same device as the server that responds to the profile BPP Loading Report externally, or a different device. In this disclosure, "factory IT / OEM" may be described as one or more devices that install profiles on terminals and respond with BPP Loading Reports at the manufacturer's factory.
[0067] In this disclosure, the BPP Loading Report, Profile Loading Report, and Profile Loading Report can be described as reports generated by a terminal manufacturer by collecting processing results generated and returned by an eUICC after the terminal manufacturer installs, deletes, etc. profiles acquired from SM-DPf on the terminal.
[0068] In the present disclosure, the Profile Order ID is an identification ID for specific profile orders, which can be generated by a communication service provider or a profile server vendor upon a profile order request from a communication service provider and shared with a terminal manufacturer. The Profile Order ID is defined as a unique value between MSP-SM-DPf, and can be utilized as information that enables the SM-DPf to determine which order a profile mapped to is requested by a terminal manufacturer by presenting the Profile Order ID. An example of the notation of the Profile Order ID may be expressed as a combination of 0-9, AZ, and "-" in hexadecimal. In the present disclosure, the service provider (SP) may be used interchangeably with a communication service provider (MSP, mobile service operator), MNO (mobile network operator), mobile network operator, operator, telecommunications company, and (M)SP server, and depending on the embodiment, the service provider may mean a server of the service provider or a role performed by the service provider. In this disclosure, the Profile Order ID may be defined in a later standard as other terms such as Bundle ID, order identification information, etc., but in the present invention, it is used unified as Profile Order ID.
[0069] In this disclosure, the processing deadline, processing deadline, comebackTime, and comeback time refer to the time it takes for the profile server to process all of the bulk of profiles requested, and the time limit within which the factory IT / OEM can reconnect and obtain all of the requested profiles. In cases where it is difficult to process all of the bulk of profiles, the profile server can provide the factory IT / OEM with information about when it will be possible to generate and respond to the requested profiles.
[0070] The processing deadline, processing deadline, comebackTime, and comeback time can be expressed in the format defined in ISO 8601, for example, YYYY-MM-DDThh:mm:ssTZD (TZD represents the time zone, Z or +hh:mm or -hh:mm), and can be included in the message returned from the profile server and returned. This can be included in the following , for example.
[0071] In this disclosure, the remaining time, remaining deadline, and remaining time refer to the remaining time required for the profile server to process a large number of profiles requested for ordering. This time may be included as additional information and transmitted by the profile server if a profile request is received before the comeback time.
[0072] The remaining time, remaining deadline, and remaining Time can be expressed in the format defined in ISO 8601, for example, YYYY-MM-DDThh:mm:ssTZD (TZD represents the time zone, Z or +hh:mm or -hh:mm), and can be included in the message returned from the profile server. This can be included in the following , for example.
[0073] Table 1
[0074]
[0075] In this disclosure, a server vendor refers to a vendor that operates a profile server, and may refer to a role performed by a profile server vendor.
[0076] In this disclosure, the term "encryption key" is used to encompass both encryption and decryption keys. For example, it may include a private key used to encrypt data or a public key used to decrypt it. The public key may also be shared in the form of a certificate.
[0077] In the present disclosure, otSK.EUICC.KA to otPK.EUICC.KA represent one-time secret key (otSK) of eUICC and one-time public key (otPK) of eUICC defined in SGP.22, and KA may mean key agreement. In the present disclosure, one-time encryption key pair or one-time eUICC encryption key pair may mean otSK.EUICC.KA and otPK.EUICC.KA. The secret key is used interchangeably as a secret key or private key, and the public key is used interchangeably as a public key.
[0078] In the present disclosure, the key material must include otPK.EUICC.KA and may represent encryption key data information for one-time profile installation on a specific eUICC as eUICC information that further includes an eUICC certificate chain or capability information such as eUICC info. In the key material, otPK.EUICC.KA may be transmitted as signed data of the eUICC. When transmitted as signed data of the eUICC, the profile server that creates a profile using it may need to verify the signed data by checking whether it has the same root of trust certificate. In the description of the drawing below, the key material may be used interchangeably with key information and encryption key information.
[0079] The present disclosure provides a method and device for enabling delivery by inserting a profile into a terminal including an eUICC.
[0080] In particular, the present disclosure provides a method and device for requesting a large number of profiles from a factory and supporting the provision of the requested large number of profiles from a profile server. The current method of transmitting profile requests by SGP.22 to SGP.32 operates under the assumption that the profile requests are processed and responded to on a 1:1 basis based on a real-time connection between the profile server (SM-DP+) and the terminal, and operates without considering delay situations. According to such a method of transmitting profile requests, it is impossible to efficiently obtain and transmit the results of processing a large number of profiles.
[0081] According to various embodiments of the present disclosure, a terminal manufacturer can receive a large number of profiles through a connection to a profile server and then pre-install and ship the profiles on an eSIM terminal without a real-time connection between the profile server and the terminal.
[0082] In addition, according to various embodiments of the present disclosure, a user can directly connect to a network by purchasing a terminal on which a profile is already installed, thereby eliminating the inconvenience of having to go to a Wi-Fi or mobile network to download a profile, thereby increasing user convenience.
[0083] In addition, according to various embodiments of the present disclosure, a telecommunications operator can provide a terminal to a user with a provisioning Profile for downloading the operator's profile or an operational Profile installed for immediate use of the operator's network service, thereby improving the user's convenience in using eSIM.
[0084] The examples below describe the procedures for injecting profiles at the factory and shipping them. It should be noted that, at some point after the profiles are injected at the factory and shipped, a terminal user may provision and install the profiles in a general user environment outside the factory according to the procedures defined in SGP.21 / 22. That is, the examples below describe provisioning in a factory-installed environment, and it should be made clear that this does not mean that profile installation in a general environment after factory shipment is impossible.
[0085] FIG. 1 is a diagram showing the relationship between components for supporting In-Factory Profile Provisioning according to one embodiment of the present disclosure.
[0086] Referring to FIG. 1, a profile server / server vendor (hereinafter, referred to as a profile server or server vendor) (100) may support functions for generating a profile for IFPP, storing a profile generated for IFPP, or encrypting a profile generated for IFPP. Additionally, it may support functions for generating profiles to be used in the field in general as defined in SGP.22. The profile server / server vendor (100) may support functions for storing generated profiles. The profile server / server vendor (100) may provide functions for encrypting generated profiles. The profile server / server vendor (100) may include functions for generating remote profile management commands (RPMs) or encrypting generated profile remote management commands. The profile server / server vendor (100) may also support functions for transmitting generated profiles to eSIM terminals or other profile storage servers. RPM can be a general term for a series of procedures in which profile installation, activation, deactivation, deletion, and other functions are performed by commands transmitted from a profile server / server vendor (100) to a terminal (120). RPM commands can be requested by a telecommunications carrier, service provider, or terminal owner and generated by the profile server / server vendor (100).
[0087] The profile server / server vendor (100) can receive a profile order request from a SP (service provider) / SP server (hereinafter, may be referred to as SP or SP server) (150) and determine whether the request is for creating a profile for IFPP. The profile server / server vendor (100) can also prepare the profile order information received from the factory IT server / OEM (hereinafter, may be referred to as factory IT, factory server, or OEM) (110) or SP / SP server (150) by combining it with the ordered EID information (by mapping the profile and EID) in the profile server / server vendor (100). The SP / SP server (150) can receive the profile order request received from the factory IT server / OEM (110) and determine whether the request is for providing an order for profiles for IFPP. After determination, the SP / SP server (150) can place an order for provision of profiles to the profile server / server vendor (100), thereby allowing the profile server / server vendor (100) to provide one or more BPPs (bound Profile packages) to the factory IT / OEM (110).
[0088] The terminal (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 basebands) for wireless communication. The communication modem may be referred to as a communication unit or a transceiver unit. The terminal (120) may provide a function of receiving BPP(s) generated for IFPP from a factory IT / OEM (110) and installing the BPP(s) into the eUICC (140). The terminal (120) may transmit the BPP to the eUICC (140), and may transmit it to the eUICC (140) via the FPA (130), or may transmit it to the eUICC (140) without going through the FPA (130). The transmitted messages may include, together with the BPP, parameters included in or added to the BPP, specifically. This is described in detail in step 675 in FIG. 6.
[0089] An example of a method for transmitting a message regarding BPP installation and encryption key information transmitted to an eUICC (140) using FPA (130) may include, but is not limited to, a method of transmitting the message by being included in one or more messages starting with ES10x. In the case of transmitting without going through FPA, the message may be transmitted as the body of the data as data of an APDU such as STORE DATA.
[0090] Meanwhile, in FIG. 1, a single profile server / server vendor (100) is represented, but there may be multiple profile servers / server vendors (100). A factory IT / OEM (110) can receive and store BPPs from multiple profile servers / server vendors (100).
[0091] As described above, the FPA (130) may be eUICC control software or an application that supports the IFPP function. The FPA (130) may also be implemented as a logical function of the terminal (120) or the eUICC (140). The FPA (130) may receive additional authentication information for authenticating a profile and a profile server / server vendor (100) from the factory IT / OEM (110) and provide the same to the eUICC (140). The FPA (130) may perform a role of acquiring a profile installation result from the eUICC (140) and transmitting it to the factory IT / OEM (110).
[0092] The eUICC (140) can determine whether a request for profile installation at the factory is made through one or more messages of ES10x received from the FPA (130) or a profile installation message received through an application or software for the factory settings of the factory IT (110) or the terminal, and decide to enter the IFPP mode. If the eUICC (140) does not support the IFPP function (e.g., if it does not understand the received function), the eUICC (140) can return an error and terminate the IFPP processing.
[0093] The eUICC (140) can process and respond to a request received through the FPA (130). The eUICC (140) can obtain information for authentication of a profile and a profile server / server vendor (100) from the terminal (130), decrypt the profile using the information for pre-stored authentication, and process the installation of the profile. The eUICC (140) can also respond with the result of the profile installation to the component that transmitted the request, i.e., a specific application of the terminal or the FPA (130) of the terminal. In addition, the eUICC (140) can verify the profile server / server vendor (100) that encrypted the profile through signature verification of the component that signed the received message, or authenticate the profile server / server vendor (100) that transmitted the message. The eUICC (140) may include an embedded UICC controlling Authority security domain (ECASD), which is a space for storing credentials required by security domains of the eUICC (140), for example, a certificate issuer's root public key for verifying an SM-DPf certificate, which is a profile server / server vendor (100), a keyset of an eUICC manufacturer, etc., and an eSIM operating platform. In addition, some of the functions of the FPA may be implemented in the eUICC (140).
[0094] The factory IT / OEM (110) is a device that is responsible for provisioning profiles to terminals in the factory, and may be configured to include one or more servers or terminals such as PCs. The factory IT / OEM (110) may obtain certain information about eUICCs (140) including one-time encryption keys from an EUM / EUM server (hereinafter, referred to as EUM or EUM server) (160), transmit all or part of the obtained information to a profile server / server vendor (100), or transmit information for mapping between an EID to be ordered and a profile to an SP / SP server (150). The factory IT / OEM (110) may be a server that stores or manages received encryption key information and BPP. The factory IT / OEM (110) may request a BPP (S) for injection at the factory from the profile server / server vendor (100), or as a result of the BPP (S) request, obtain a BPP for installation in the eUICC (140) and data signed by the profile server / server vendor (100) from the profile server / server vendor (100). The factory IT / OEM (110) may store the received BPPs and the signed data in the factory IT / OEM (110). The factory IT / OEM (110) may select a BPP mapped to the EID of the target terminal on which the profile is to be installed from among the received or stored BPPs and transmit the BPP to the terminal mapped during the factory setup process. The factory IT / OEM (110) may obtain the BPP processing result from the terminal (120) via the FPA (130).
[0095] The factory IT / OEM (110) may be a server that acquires the received BPP processing results from the terminal (120), stores the acquired results, processes the results to generate a BPP Loading Report, or transmits the generated Report to the profile server / server vendor (100).
[0096] As described above, factory IT / OEM (110) refers to operations performed by a terminal manufacturer or a factory IT of a terminal manufacturer, and therefore, although it is expressed as a single entity in the drawings below, it may be composed of multiple devices (e.g., terminals such as servers or PCs). Accordingly, for example, the device in the factory IT / OEM (110) that is at the point of contact with the profile server / server vendor (100) and the device of the factory IT / OEM (110) that is at the point of contact with the eSIM terminal (120) may be the same or different devices. Some of the information exchanged between the profile server / server vendor (100), SP server (150), and EUM (160) in the factory IT / OEM (110) may be shared between entities that perform roles in other forms (i.e., terminal manufacturers, profile server operating vendors, service providers, eUICC manufacturers) through other online and offline channels (e.g., email transmission) rather than message transmission and reception through the server-to-server interface.
[0097] The EUM (eUICC manufacturer) (160) can provide personalized eUICCs (140) to terminal manufacturers by injecting key information for eUICC authentication credentials into the eUICC (140). The EUM (eUICC manufacturer) (160) can provide certain information about the eUICCs (140), including a one-time encryption key, to the OEM / factory IT / OEM (110) from the EUM (eUICC manufacturer) / EUM server (160). In addition, although not shown in the drawing, certain information about the eUICCs (140), including a one-time encryption key, can also be transmitted from the EUM (eUICC manufacturer) / EUM server (160) to the profile server / server vendor (100) at the request of the OEM (110).
[0098] As described above, the SP (service provider) (150) is a business operator that provides network services using profiles, and can order profile(s) for IFPP functions from the SP / SP server (150) to the profile server / server vendor (100) so that the profile server / server vendor (100) can create and prepare the ordered profiles. In addition, a profile order ID can be created and provided to the profile server / server vendor (100) and the OEM (110). In addition, the profile processing result can be received from the profile server / server vendor (100) so that additional management can be processed for the corresponding profiles thereafter.
[0099] Hereinafter, the description of the aforementioned configuration modules can also be applied to the roles and relationships of the modules indicated in the drawings described later. In addition, among the aforementioned configuration modules, order information as information exchanged between the profile server / server vendor (100), factory IT server / OEM (110), EUM / EUM server (160), and SP / SP server (150) may be transmitted in other forms such as interface linkage between the servers of each entity or email.
[0100] FIG. 2 is an exemplary diagram of a process in which a factory IT server / OEM (210) requests and receives a profile from a profile server / server vendor (210) according to one embodiment of the present disclosure.
[0101] Referring to FIGS. 2A and 2B, a factory IT / OEM (215) that wishes to install an eUICC can order eUICCs from an EUM / EUM server (200). The EUM (200) can create a pair of otSK.eUICC.KA and PK.eUICC.KA used in the eUICC in advance and transmit them to the factory IT / OEM (215) (step 230). When delivering an eUICC with otSK.EUICC.KA installed, the EUM (200) can transmit to the factory IT / OEM (215) at least one of otPK.EUICC.KA, [Euicc info], [EID], data including otPK.EUICC.KA signed with the private key of the EUM, a certificate (CERT.EUICC.SIG) and certificate chain of the EUICC, EID, or PK.EUICC.KA for each eUICC (step 230). The transmitted information can be transmitted through an interface linked to the factory IT (215) from the profile server. The transmitted information can be transmitted online or offline. Each transmitted information can indicate the following. Of course, the information is not limited to the examples below and other information can also be indicated.
[0102] - otPK.EUICC.KA: eUICC's one-time public key
[0103] - Public key used to generate session keys between the profile server and eUICC
[0104] - SK (data including otPK.EUICC.KA): Data including otPK.EUICC.KA signed with the secret key of eUICC
[0105] - CERT.EUICC.SIG and certificate chain: eUICC certificate and chain of certificates for eUICC certificate verification.
[0106] - CERT.EUICC.SIG may contain the EID, the unique identification number of the eUICC, and the public key (PK.EUICC.KA) for decrypting the eUICC signature. It can also be used to prove that the eUICC is authenticated by the EUM.
[0107] - The parent certificate chain of CERT.EUICC.SIG may include CERT.EUM.SIG, a certificate containing an EUM public key.
[0108] - eUICC info: Information about eUICC capabilities. This may or may not include an indication of capabilities indicating whether the eUICC supports IFPP. If multiple orders have the same eUICC capabilities, eUICC info may be transmitted for each order rather than per eUICC. As previously described, information regarding the support for installing multiple profiles and the method of supporting the installation of multiple profiles may also be included.
[0109] - EID: Unique identification number assigned to each eUICC
[0110] - PK.EUICC.KA: When the public EID of eUICC for decrypting the eUICC signature or PK.EUICC.KA is transmitted, it can be transmitted as a value included in CERT.EUICC.SIG, or when transmitted without being included in CERT.EUICC.SIG, it can be transmitted as a separate parameter.
[0111] The factory IT / OEM (215) that receives the transmitted information stores and retains the information, and at a specific point in time, the factory IT / OEM (215) can decide to load the profile on N or all eUICCs that are part of the M eUICCs ordered from the EUM (200). Alternatively, the SP / SP server (205) can request the factory IT / OEM (215) to pre-load the profiles on terminals (220) to which the profiles will be shipped.
[0112] Factory IT / OEM (215) may optionally transmit to SP / SP server (205) at least one of the profile number and EID(s) information so that SP / SP server (205) can prepare profiles linked to EIDs in advance. (Step 233)
[0113] The SP / SP server (205) can order a profile to a profile server / server vendor (210) (step 235).
[0114] If the SP / SP server (205) has acquired and has the EID lists at step 333 or a previous point in time, the SP / SP server (205) may transmit the order to the profile server / server vendor (210) including the EID information while ordering the profile. The profile order message may be defined in a form that further includes IFPP order identification information in the ES2+ order interface between the service provider and the profile server defined in the new function or the existing GSMA RSP. The information included in the order message may include at least one of the following. Of course, the information is not limited to the information below, and inclusion of other information is not excluded.
[0115] - Profile order ID that represents a group of order profiles
[0116] - Number of profiles assigned by profile order ID or ICCID lists
[0117] - Number of order profile(s)
[0118] - ICCID(s)
[0119] - EID(s) that require linked profiles
[0120] - SP (service provider) ID
[0121] - Profile server address where order profiles will be prepared (e.g., FQDN type address)
[0122] - IFPP order identifier (IFPP indication)
[0123] - Factory IT serial number to which the generated BPP will be transferred
[0124] - OEM identification number (manufacturer number) to which the generated BPP will be transmitted
[0125] The IFPP order identifier can be transmitted as part of the value of the IFPP indication data. Alternatively, the Profile order ID can be transmitted as part of one of the values of the Profile type data of the ES2+ order interface.
[0126] The profile server / server vendor (210) may be a profile server that supports only IFPP, but may also be a profile server that supports IFPP as one of its functions. For example, the profile server / server vendor (210) may be a server that supports SGP.21 / 22 (a standard for profile provisioning to consumer terminals such as smartphones) defined by GSMA. Alternatively, the profile server / server vendor (210) may be a profile server that supports SGP.31 / 32 (a standard for profile provisioning to IoT-specific terminals). The profile server / server vendor (210) may be a server that additionally supports a function for profile provisioning in the factory. The profile server / server vendor (210) that receives a profile download order can identify and manage whether the profile download order is for IFPP by determining whether there is IFPP determination information as a new function defined as IFPPorder or a new parameter of the existing ES2+.Downloadorder. Identification of whether it is for IFPP can be based on the IFPP order identifier or Profile order ID mentioned above. Meanwhile, if the EID is not received together in the previous step (235), the profile server / server vendor (210) can change the status of the Profile to the allocated stage and process it. If the EID is received together in step 235, the EID can be linked to the ICCID and the status of the Profile can be changed to the linked stage and prepared.
[0127] Later, the profile server / server vendor (210) may receive a profile provision request (step 245). According to one embodiment of the present disclosure, the SP / SP server (205) or the profile server / server vendor (210) may share information that can specify a profile download order with the factory IT / OEM (215) (step 240).
[0128] When the profile server / server vendor (210) receives a request for providing a profile for IFPP from the factory IT / OEM (215), the profile server / server vendor (210) can check which order it corresponds to among the profile creation orders previously requested from the SP. Information that can check which order it corresponds to may include information such as a profile order ID, the address of the server storing the profile, identification information of the service provider that requested the profile creation, the start and end numbers of the ordered profile list or EID list, or at least one of the ordered profile list, EID list, and factory IT identification number.
[0129] Thereafter, when the profile server / server vendor (210) receives the profile request information, it can optionally check the included order identification information, and if there are pre-prepared profiles for the optionally included orders, it can prepare BPPs by encrypting the pre-prepared profiles with otPK.EUICC.KA corresponding to the eUICC as described below.
[0130] At step 245, the factory IT / OEM (215) may wish to inject a profile into the terminal before shipping it from the factory. To this end, the factory IT / OEM (215) may request a BPP prepared for IFPP from the profile server / server vendor (210).
[0131] The method of indicating that the request is an IFPP request from the factory IT (215) to the profile server / server vendor (210) may include at least one of a method in which a message is transmitted with a new function indicating that the request is a BPP request for IFPP, a method in which an IFPP identification indication is transmitted by utilizing an existing ES9+ function, or a method in which parameters required only for IFPP (for example, at least one of otPK.eUICC.KA, Profile order ID, or SP ID) are included and transmitted. The method of indicating that the request is an IFPP request to the profile server / server vendor (210) may be determined by the profile server / server vendor (210). As an example of utilizing the ES9+ function defined in the aforementioned existing SGP.22, a message such as ES9+. GetBoundProfilePackage may be transmitted, and an IFPP identification indication may be included therein. Meanwhile, in one of the data of a series of follow-up messages accompanying a BPP request for IFPP or a BPP generation request, the factory IT / OEM (215) may transmit to the profile server / server vendor (210) key information including otPK.EUICC.KA corresponding to the eUICCs of the target terminals as many as the number of terminals on which the SP (service provider) (205) will load the profile among the key information of the eUICCs acquired in step 630. In addition, in one of the data of a series of follow-up messages accompanying the BPP generation request transmitted from the factory IT / OEM (215) to the profile server / server vendor (210), eUICC info may be selectively included as device info or eUICC capability information as additional information provided for BPP generation, as the capability of the terminal.
[0132] If the profile server / server vendor (210) receives a message from the factory IT (215) that can determine that it is a BPP request for IFPP and receives key information for otPK.eUICC.KA, the profile server / server vendor (210) can determine that BPP for IFPP is ready. In this case, the profile server / server vendor (210) can then determine the number of profiles that can be prepared at present and, if it is difficult to process the requested number in real time, transmit a comeback time. (Step 250) In this step, the profile server / server vendor (210) can also reply including the number of profiles that were processed immediately upon the request. (Step 250)
[0133] Meanwhile, although not shown in this drawing, it may be possible for the profile server to reply with information that is in addition to or in place of the comeback time, such as the interval time and / or the number of profiles that can be provided per interval time. If the interval time and the number of profiles that can be provided per interval time are replied, the factory IT / OEM may have that information and send a profile request message once per interval time to acquire profiles until the comeback time is reached or the desired number of profiles is reached.
[0134] Upon receiving this, Factory IT / OEM (215) can recognize that not all orders corresponding to the corresponding Profile order ID have been processed, and after the comeback time, can access the ID for the corresponding order (step 275) and obtain all remaining BPPs generated (step 270) for the previous order from the profile server / server vendor (210) (step 280).
[0135] Factory IT / OEM (215) may connect (step 260) with the ID for the order before the received comeback time. In this case, the profile server / server vendor (210) checks the Profile Order ID, checks whether the profile request deadline for the Profile Order ID has been provided previously, and if it is determined that the connection has occurred before the request deadline for the profiles, it may reply with an error message regarding the profile creation. This may be a message such as stillInProgress (121) indicated in above. At this time, depending on the settings of the profile server / server vendor (210), it may optionally add additional profiles created up to that point along with the error message regarding the profile creation, and / or optionally add the time required to create the profiles and reply (step 245).
[0136] If the profile server / server vendor (210) requests BPPs including a Profile order ID without otPK.EUICC.KA, the profile server may return an error (step 285). This may be because either all otPK.EUICC.KA key materials required for profile creation for the order have been exhausted, or otPK.EUCC.KA for the order has not been previously received.
[0137] The operation of the profile server / server vendor (210) and Factory IT / OEM (215) for processing a large number of profile transmission requests through ESbpp in FIG. 2 will be described in detail later in FIGS. 4 to 6 and FIGS. 7.
[0138] The profile server / server vendor (210) may perform a step of generating a BPP for IFPP (step 250 or step 270). The profile server / server vendor (210) may enter a procedure of generating a BPP, which is an encrypted profile package, in IFPP mode. When the profile server / server vendor (210) determines to generate a BPP for IFPP, the step may include receiving information that can recognize the message received from the factory IT (215) (for example, information including at least one of a new function defined for IFPP, a new IFPP indication that can recognize that an existing ES9+ message is a profile download request from the factory, or new parameters (such as encryption key information)). When the profile server / server vendor (210) determines that a BPP for IFPP should be generated, the profile server / server vendor (210) may generate the BPP for IFPP by including one or more of the following procedures. Of course, the present invention is not limited to the following examples.
[0139] - Profile Eligibility Check
[0140] This can be optionally performed as a procedure for the profile server / server vendor (210) to check whether the profile type received from the SP through the ES2+ order interface is suitable for installation on the target terminal / EID before performing a profile download. If at least one of EID, eUICC info, and device info is received through steps 235 to 245, a procedure for checking whether the profile order received in step 250, particularly the profile type specified in the order, can be installed can be optionally performed. Accordingly, the profile server / server vendor (210) can or can not perform qualification verification, including whether the EID / terminal is suitable for installing the profile for IFPP.
[0141] - Verification of CERT.EUICC.SIG, the eUICC certificate
[0142] The profile server / server vendor (210) can perform verification when receiving CERT.EUICC.SIG in step 245. The profile server / server vendor (210) can verify the CERT.EUICC.SIG received in step 245 with the EUM certificate. The CERT.EUICC.SIG can include an EID, which can be composed of a series of numbers including one of the EINs in the EUM certificate. The profile server can authenticate whether the CERT.EUICC.SIG is a legitimate eUICC by checking whether the EID included in the CERT.EUICC.SIG matches one of the values of the allowed EINs (EUM identification IDs) included in the EUM certificate CERT.EUM.SIG.
[0143] - Verify the signature of eUICC
[0144] The profile server / server vendor (210) can verify the signature by decrypting the secret key of the eUICC used to sign the data containing otPK.EUICC.KA with the public key of the eUICC contained in CERT.EUICC.SIG.
[0145] - otSK / PK.DP.KA: Generate a one-time private key and public key pair for the profile server.
[0146] - Generate a session key using otSK.DP.KA and otPK.EUICC.KA received in (step 245)
[0147] The profile server / server vendor (210) can use otSK.DP.KA and otPK.EUICC.KA to generate a shared secret value to be used for a specific profile transfer session.
[0148] - ServerChallenge
[0149] In step 245 or a step before step 245, if the factory IT / OEM (215) requests transmission including ServerChallenge information to the profile server / server vendor (210), the profile server / server vendor (210) can generate ServerChallenge information. This can be provided if the eUICC (225) is designed to be able to send the ServerChallenge value that the profile server / server vendor (210) sends to the eUICC (225) as is during the mutual authentication procedure between the profile server / server vendor (210) and the eUICC (225).
[0150] - Create BPP (bound Profile package)
[0151] A profile server / server vendor (210) can generate a profile package bound to an EID that includes a session key, a key replacement package, ISD-P generation, and configuration information.
[0152] If the profile server / server vendor (210) successfully creates a BPP for the IFPP in step 250 or step 270, the profile server / server vendor (210) may transmit the BPP and a series of information required for BPP installation to the factory IT / OEM (215) via one or more messages (step 265 or step 280).
[0153] The profile server / server vendor (210) may transmit a list of a series of encryption key information required for BPP verification in the BPP generated by the factory IT / OEM (215) and the mapped eUICC via one or more messages. The encryption key information, for example, public keys, may be transmitted together with the certificate or may not be transmitted together with the certificate. In addition, the information transmitted by the profile server / server vendor (210) may include order identification information, for example, a service provider ID or a Profile order ID or an order ID. According to one embodiment of the present disclosure, the information transmitted from the profile server / server vendor (210) may include a message such as ESbpp.getBoundProfilePackage Response([SP ID], ([Profile order ID], (BPP including otPK.DP.KA, CERT.EUICC.SIG, [CERT.DPauth.SIG], CERT.DPpb.SIG, [ServerChallenge]) XN). The information transmitted in step 355 may be composed of one message or one or more messages and transmitted to the factory IT / OEM (215) and stored in the factory IT (215).
[0154] The factory IT (215) stores the received BPP, the EID mapped to each BPP, and the encryption key information for downloading and installing the BPP to the EID, and can then perform provisioning of the profile (step 290). The provisioning procedure can be performed by the factory IT (215) transmitting the encryption key information for downloading and installing the BPP to the BPP and the EID to the terminal (220), and the terminal (220) transmitting the BPP and the encryption key information for downloading and installing the BPP to the eUICC (225), and the eUICC (225) verifying the transmitted BPP and the encryption key for installing the BPP and installing the profile.
[0155] The procedure for installing BPP from a terminal (220) to an eUICC (225) may involve transmitting a message to the eUICC (225) via an LPAf (not shown) or transmitting the message to the eUICC (225) without passing through the LPAf. As an example of a message transmitted to the eUICC using the LPAf, the message may be transmitted by being included in one or more messages included in ES10x. In addition, the method of transmitting from the terminal may be one of the following methods. Of course, the present invention is not limited to the following methods.
[0156] - A method of processing by reusing the three steps of the existing SGP.22 server and eUICC authentication procedure, the pre-information sharing procedure for profile installation, and the BPP installation procedure.
[0157] - A method of processing in two steps, reusing the authentication procedure between the server and eUICC and the BPP installation procedure in the three-step procedure of the aforementioned SGP.22.
[0158] - A method for transmitting key information related to BPP and BBP in batches from a terminal (220) to an eUICC (225) by defining a new function consisting of 1 step.
[0159] When a profile is installed in eUICC (225), the profile installation result is returned to the terminal (220) as an eUICC-signed value and transmitted to Factory IT / OEM (215) through the terminal (220). Afterwards, at a specific point in time, Factory IT / OEM (215) collects the installation results and transmits them all at once to the profile server / server vendor (210). Alternatively, the eUICC-signed installation result may be transmitted to the profile server / server vendor through the ES9+ interface as a notification defined in SGP.22 after shipment from the factory.
[0160] FIG. 3 is an exemplary diagram illustrating a procedure for requesting a large number of profiles from a Factory IT / OEM (315) to a profile server / server vendor (310) according to one embodiment of the present disclosure. Steps 330 to 340 in FIG. 3 are identical to steps 230 to 240 in FIG. 2 and are therefore referred to herein.
[0161] In Fig. 3, Factory IT / OEM (315) may first check the capabilities of real-time profile creation of the profile server / server vendor (310) before transmitting key materials including otPK.EUICC.KA when requesting a profile, and then transmit the required quantity accordingly. For example, Factory IT / OEM (315) may first transmit the Profile order ID and additionally the corresponding BPP counts while transmitting a message such as ESbpp.GetCapability. (Step 345) The profile server / server vendor (310) that receives this may transmit at least one of the (real-time) processable count, the corresponding processing time, and whether real-time processing is possible at a time. (Step 350)
[0162] Factory IT / OEM (315) that receives this can transmit key materials including otPK.EUICC.KA based on the information replied in (step 350) when requesting a large number of profiles in (step 355). For example, if Factory IT / OEM (315) wants to request 1 million profiles, if the value replied in step 350 is 500,000, it can transmit only information corresponding to 500,000 without transmitting key materials including otPK.EUICC.KA corresponding to 1 million.
[0163] In step 355, Factory IT / OEM (315) may transmit key materials including otPK.EUICC.KA in a larger number than the number of processable numbers received in step 350. At this time, the profile server / server vendor (310) may generate and reply to BPPs in the number of real-time processable numbers, or may generate and reply to them while additionally including the Comeback time, so that the factory IT / OEM (315) may request BPPs with the Profile order ID from the profile server / server vendor (310) at a specific time, as in steps 255-290 of FIG. 2, so that the profiles generated in the meantime can be obtained.
[0164] The operation of the profile server / server vendor (310) and Factory IT / OEM (315) for processing a large number of profile transmission requests through ESbpp in FIG. 3 will be described in detail later in FIGS. 5 to 8.
[0165] FIG. 4 is an exemplary diagram showing the judgment of a profile server according to one embodiment of the present disclosure.
[0166] FIG. 4 illustrates the operation of a profile server when a BPPs request including otPK.EUCC.KA is received in FIGS. 2 and 3. The profile server is a server that supports IFPP and has been requested to order profiles for IFPP, and may have information about the profile order, for example, a Profile order ID (step 400). Thereafter, the profile server / server vendor may receive a message about a BPPs request from the factory IT / OEM at a specific time (step 405). The profile server / server vendor that receives this may determine whether a delay occurs when generating the requested BPPs (step 410), and if no delay occurs, may process it in real time and transmit the requested BPPs as the processing result (step 435).
[0167] If it is determined that not all of the requested BPPs can be generated in step 410, the profile server can additionally determine whether to allow transmission of some of the BPPs in the request (step 415). If the profile server / server vendor allows transmission of some of the generated BPPs, it can transmit some of the generated BPPs and can also transmit a processing deadline as additional information as a comeback time. If the profile server / server vendor allows transmission of BPPs in batches only after all of the requested BPPs have been generated, the profile server / server vendor can transmit a processing deadline for the case (step 440) and complete the procedure (step 430).
[0168] FIG. 5 is an exemplary diagram illustrating the judgment of a profile server according to an embodiment of the present disclosure. FIG. 5 is a diagram for detailing the operation of the profile server of FIG. 3, which differs from the operation of the profile server mentioned in FIG. 4 in that steps 500 to 505 to 510 are added before step 410, and subsequent operations can be processed in the same manner. Accordingly, steps 515 to 550 in this diagram can be interpreted with reference to steps 405 to 440 of FIG. 4.
[0169] Figure 5 illustrates the operation of a profile server when receiving a BPPs request containing otPK.EUCC.KA from Figures 2 and 3. The profile server is a server that supports IFPP and has received a request for an order for profiles for IFPP, and may have information about the profile order, for example, a Profile order ID (Step 500).
[0170] The profile server may receive a request message from the factory IT / OEM to confirm the profile server's capability for processing real-time BPPs. The message may include at least one of the following information: whether real-time processing is possible, the number of BPPs to be processed, and a Profile order ID. If the ESbpp. function explicitly indicates real-time processing capability, the message may also be received without parameters. (Step 505) The profile server that receives the message determines the number of real-time generation capabilities and may reply with the number of BPPs that can be generated, and if more BPP requests are received than the number of generation capabilities, it may also reply with a processing deadline for the remaining BPPs. (Step 510)
[0171] Afterwards, at a certain point in time, a message for a BPPs request can be received from the factory IT / OEM. (Step 515) The profile server / server vendor that receives this determines whether there is a delay in the generation of the requested BPPs (Step 520), and if there is no delay, it can process in real time and transmit the requested BPPs as a result of the processing (Step 550).
[0172] If no delay processing occurs, the profile server can determine that a number of otPK.EUICC.KAs equal to or less than the number of real-time generable profiles previously transmitted is received, or a number of profile requests equal to or less than the number of real-time generable profiles is received.
[0173] If it is determined in step 520 that not all of the requested BPPs can be generated, the profile server can make an additional determination (step 525) as to whether transmission of some of the BPPs in the request is permitted. If the profile server / server vendor permits transmission of some of the generated BPPs, it can transmit some of the generated BPPs and can also transmit a processing deadline as additional information as a comeback time. If transmission of BPPs in batches is permitted only after all of the requested BPPs have been generated, the processing deadline for the case is transmitted (step 545) and the profile server / server vendor can complete the procedure (step 535).
[0174] FIG. 6 is an exemplary diagram illustrating the judgment of a profile server according to an embodiment of the present disclosure. FIG. 6 illustrates the operation of the profile server when receiving a BPPs request that does not include otPK.EUCC.KA as in FIGS. 2 and 3.
[0175] The profile server can receive a BPP request without otPK.EUICC.KAs (step 605) and decide whether to return an error or transmit BPPs. The profile server can check the corresponding Profile order ID and determine whether there are any unused otPK.EUICC.KAs received for the order (step 610). If there are no unused otPK.EUICC.KAs, it can determine whether the profile server / server vendor has generated all BPPs corresponding to the order with otPK.EUICC.KAs and transmitted them to the factory IT / OEM (step 655). For example, the profile server can distinguish whether the profile reception request is for a case where all BPPs were generated for a previously received otPK.EUICC.KAs, or whether the profile creation request was sent without including otPK.EUICC.KAs.
[0176] The profile server can generate BPPs using all otPK.EUICC.KAs and return a response indicating that all orders have been processed, and can return an error indicating that the processing has been completed (step 640). If there are no unused otPK.EICC.KAs and not all BPPs corresponding to the order have been transmitted, it can be determined that the otPK.EUCC.KA is missing and an error indicating missing data can be returned (step 645).
[0177] Meanwhile, if there is an unused otPK.EUICC.KA received for the order previously (step 610), the profile server can determine whether a processing deadline (comeback time) has been given previously (step 615) and perform one of the following actions, construct a reply message, and send it to complete the action (step 630).
[0178] ● If no processing deadline is given, BPPs may be generated and responded to up to the number of unused BPPs. (Step 655)
[0179] ● If a processing deadline is given and the request is made after the deadline, all remaining BPPs can be transmitted (step 625). If the request is made after the deadline and requires additional processing time, the profile server can regenerate the comeback time and respond (step 625).
[0180] ● If a processing deadline is given and the request is within the processing deadline, an error can be returned during processing, and the response can include or exclude the profiles created up to that point, or the response can include the remaining time.
[0181] FIG. 7 is an exemplary diagram illustrating a factory IT / OEM judgment according to one embodiment of the present disclosure.
[0182] FIG. 7 illustrates the operation and judgment of a terminal manufacturer server that transmits a large number of BPPs requests for IFPP in FIG. 2. Prior to performing this procedure, the factory IT / OEM may receive and store key materials including otPK.EUICC.KA, and may request profiles from the SP / SP server so that the SP / SP server prepares to request an order for profiles from the profile server. In addition, the factory IT / OEM may obtain and have a Profile order ID as information about the order from the SP / SP server or the profile server. (Step 400) Afterwards, at a certain point in time, the factory IT / OEM may request profiles from the profile server / server vendor. In the process of generating a message for an order, the factory IT / OEM may determine whether the otPK.EUICC.KAs for the corresponding BPP order have already been transmitted to the profile server / server vendor (Step 705). If so, the factory IT / OEM may transmit the BPP transmission request including the Profile order ID without including the transmitted otPK.EUICC.KAs. (Step 730) Meanwhile, if the factory IT / OEM has not already transmitted the otPK.EUICC.KAs, it can transmit the otPK.EUICC.KAs together with the Profile order ID when transmitting the BPP request message. (Step 710)
[0183] The factory IT / OEM can determine whether the message returned as a result of the transmission contains all previously requested BPPs (step 715). This can be determined by one of the following values: the number of otPK.EUICC.KAs or the number of explicitly requested BPPs.
[0184] If all requested BPPs have been received, the factory IT / OEM can store the received BPPs and complete the process (step 735).
[0185] If not all the requested number of BPPs are received in the reply message, the factory IT / OEM can additionally determine whether a parameter for a transmission deadline has been received (step 735). If a transmission deadline has been received, the factory IT / OEM can store the transmission deadline and request transmission of BPPs after the transmission deadline. (step 740) When requesting transmission of BPPs after the transmission deadline, the factory IT / OEM can create a message including the Profile order ID and excluding otPK.EUCC.KAs and make the request. (step 740) The factory IT / OEM can receive the remaining BPPs as a result of the request and store the received BPPs to complete the process. (step 725) If the transmission deadline has not been received (step 735), the factory IT / OEM can repeatedly re-request BPPs from the profile server / server vendor to obtain the remaining BPPs. In this case, since otPK.EUICC.KAs have already been transmitted, factory IT / OEM can proceed to step 730 and perform subsequent procedures to complete (step 725).
[0186] FIG. 8 is an exemplary diagram illustrating a factory IT / OEM judgment according to one embodiment of the present disclosure.
[0187] Figure 8 illustrates the operation and judgment of a terminal manufacturer server transmitting a large number of BPP requests for IFPP in Figure 3. Parts not described in the drawing can be understood by referring to Figures 3 to 5.
[0188] The factory IT / OEM may be configured to send a message to the profile server to verify real-time processing capability before sending key information including otPK.EUICC.KAs when requesting the creation of BPPs (step 800). Real-time processing may mean processing while the terminal manufacturer server maintains a session between the terminal manufacturer server and the factory IT / OEM.
[0189] In this case, the factory IT / OEM can construct and transmit a message requesting real-time processing capability including certain information (step 805). The specified information may include the number of profiles to be requested and be transmitted, or may include a Profile order ID as profile order information. Alternatively, the message may be constructed and transmitted so that the ESbpp. function determines whether it is a request for real-time processing capability without the specified information. After transmitting the message, the factory IT / OEM can receive a message regarding real-time processing capability from the profile server (step 810). The message may be returned including at least one of information regarding whether real-time processing is possible, BPPs processed in real-time, comeback time for processing (remaining) BPPs, number of BPPs that can be processed per request, and processing time per request. The factory IT / OEM that receives the message can determine the number of profiles that can be processed in real time, and determines whether to send a message including the number of otPK.EUICC.KA within the number according to the factory IT / OEM settings. (Step 815) If the factory IT / OEM sends only the number of otPK.EUICC.KA within the number, BPPs corresponding to the number may be received as a message received from the profile server (Step 820). If the processing time and the number that can be processed are received in one request in Step 810, the terminal manufacturer server may periodically request BPPs and receive them from the profile server with reference to this. For example, the profile server may send a BPPs request message for the number that can be processed in one request repeatedly in the processing time cycle.At this time, the profile BPPs request message transmitted by the terminal manufacturer may further include certain information indicating which message it is among the multiple BPPs request messages transmitted to receive a total of BPPs. If the profile server receives a message including certain information indicating which message it is among the total of BPPs request messages, it can predict how many more identical BPPs request messages will be received in the previously replied processing time cycle and, accordingly, determine how many profiles it should prepare in total.
[0190] If the number of otPK.EUICC.KAs is greater than the corresponding number, the factory IT / OEM may receive a transmission deadline in the received message for this (step 830). If the transmission deadline is received, the factory IT / OEM may retransmit the BPPs request after the transmission deadline, and since more otPK.EUICC.KAs were transmitted previously, the factory IT / OEM may transmit the BPPs request without additionally transmitting otPK.EUICC.KAs by including the Profile order ID (step 835). In this case, the factory IT / OEM may receive a message from the profile server including profiles corresponding to the number of remaining otPK.EUICC.KAs transmitted previously. If the factory IT / OEM has not received all the profiles corresponding to the remaining otPK.EUICC.KA and a processing deadline has been reached, the factory IT / OEM may determine that the profile server has not generated all BPPs. In this case, the factory IT / OEM may additionally reconnect after the processing deadline as shown in FIG. 7 to receive the remaining BPPs.
[0191] FIG. 9 is a block diagram showing the structure of a profile server (900), a factory IT (920), and a terminal (940) in a wireless communication system according to one embodiment of the present disclosure.
[0192] Referring to FIG. 9, a profile server (900) according to one embodiment of the present disclosure may include a communication unit (905), a control unit (910), and an encryption unit (915). The control unit (910) may be composed of at least one processor.
[0193] The communication unit (905) can transmit data to or receive data from other devices. The communication unit (905) can transmit or receive encrypted keys, encrypted profiles, etc. To this end, the communication unit (905) can be equipped with at least one communication module and an antenna.
[0194] The control unit (910) can control each component of the profile server (900) to install a profile according to the present invention. The specific operation of the control unit (910) is as described above or below. According to one embodiment, the profile server (900) can refer to the information received from the service provider server or the manufacturer's server or from the service provider and the manufacturer to determine whether the order is the same, and can process the mapping of the profile and the eUICC provided information for the same order and store them in the storage unit (917). In addition, the control unit (910) can control the operation to prepare in advance by referencing the EID information received from the service provider by mapping the profile to a specific EID. According to another embodiment, the control unit (910) can perform the operation by entering the operation of preparing the profile by determining whether a profile should be prepared for IFPP based on the information received from the message received through the communication unit (905).
[0195] According to another embodiment, the control unit (910) may determine whether there is eUICC provision information, for example, otPK, EUICC, KA, stored in the storage unit (917), using information received from a message received through the communication unit (905), and may configure a reply message based on whether the information is included and reply through the communication unit (905). In addition, the control unit (910) may determine whether profiles can be processed in real time to reply, and if processing is not possible, a processing deadline or / and a remaining deadline may be generated and processed so that a reply can be sent through the communication unit (905). In addition, when generating a processing deadline or a remaining deadline, the control unit (910) may manage the deadline through a clock.
[0196] According to another embodiment, the control unit (910) may determine that a message received through the communication unit (905) is a message received within or after the processing time limit, and may process the message to be replied to by composing a reply message accordingly and replying to the message through the communication unit (905).
[0197] According to another embodiment, the control unit (910) can control the operation of the profile server (900) described in various embodiments of the present disclosure.
[0198] According to another embodiment, the profile server (900) may receive a message received from factory IT through the communication unit (905) in a preliminary process of preparing and providing BPP, determine that the received message is a request to download a profile for IFPP, process an operation to prepare profiles for the factory, and transmit the processing result to the factory IT through the communication unit (905). The encryption unit (915) may perform encryption on the profile under the control of the control unit (910) to generate a Bound Profile Package and provide the Bound Profile Package to the control unit (910). Part or all of the information received through the communication unit (905), for example, the Profile Order ID received from the SP / SP server (not shown), the eUICC certificate chain information or otPK.EUICC.KAs received from the factory IT (920), may be stored in the storage unit (917).
[0199] The encryption unit (915) may include a hardware security module (HSM) or be named as such, and may perform encryption and decryption of profiles without exposing encryption keys. Depending on the implementation, the encryption unit (915) may be embedded in the control unit (910) or implemented in the form of software code driven by the control unit (910).
[0200] Referring to FIG. 9, a factory IT (920) according to an embodiment of the present disclosure may include a communication unit (925), a control unit (930), and a storage unit (935). The factory IT (920) may be configured as a combination of multiple devices including one or more of the communication unit, the control unit, and the storage unit. When multiple devices are connected to each other, each device for connection may be implemented to include a communication unit, and a device for centrally controlling each device may be included. The factory IT (920) may also be configured as one or more devices as described above. For this, additional reference is made to the description of FIG. 1.
[0201] In addition, according to one embodiment of the present disclosure, the communication unit (925) can transmit or receive an encrypted key, an encrypted profile, etc. For this purpose, the communication device (925) can be equipped with at least one communication module and an antenna, etc. In accordance with one embodiment of the present disclosure, the storage unit (935) and the communication unit (925) can be equipped as a single device for the factory IT (920) itself. The factory IT (920) can transmit profile order information and / or encrypted key information to the profile server (900) through the communication unit (925) that provides a wireless communication connection, or receive at least one of encrypted profiles and / or a processing time limit from the profile server (900). In addition, according to one embodiment of the present disclosure, the factory IT (920) can transmit a stored encrypted profile to the terminal (920) through the communication unit (925), or receive a response message regarding the processing result from the terminal.
[0202] In addition, according to one embodiment of the present disclosure, the factory IT (920) may store a profile received from the profile server (900) through the communication unit (925) or an encrypted key previously obtained from the EUM (not shown) in the storage unit (935) by the control unit (930), or may transmit the profile to a device within the factory IT (920) responsible for profile injection through the communication unit (925), and may transmit the profile to the terminal (940) by wire or wirelessly from the communication unit (925) of the device within the factory IT (920) responsible for profile injection.
[0203] Additionally, according to one embodiment of the present disclosure, the storage unit (935) of the factory IT (920) may store at least one encrypted profile, or store encrypted key information for one encrypted profile, or receive a loading result received from the terminal (940).
[0204] According to one embodiment of the present disclosure, the control unit (930) may obtain at least one of a processing time limit, a remaining time limit, encrypted key information, and profile order information through the storage unit (935) to construct a BPPs request message to be transmitted to the profile server (900), and may construct a message by making a judgment based on the information and transmit the message to the communication unit (905) of the profile server through the communication unit (925).
[0205] In addition, according to one embodiment of the present disclosure, the factory IT (920) can process the processing deadline or remaining deadline received from the profile server (900) through the communication unit (925) to be stored in the storage unit (935) through the control unit (930). In addition, the control unit can process the BPPs generation request message to be generated at a specific point in time after the processing deadline or remaining deadline based on the processing deadline or remaining deadline, and transmit the message through the communication unit (925) for processing.
[0206] The storage unit (935) may include at least one type of storage medium among 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. In addition, according to one embodiment of the present disclosure, the factory IT (910) may be composed of multiple devices as described above, and when composed of multiple devices, the communication unit may provide a communication service limited to only a terminal manufacturer's external network connection or a terminal manufacturer's internal network connection.
[0207] Additionally, according to one embodiment of the present disclosure, the control unit (930) may include at least one processor. The control unit (930) may control the operation of the Factory IT (920) according to various embodiments of the present disclosure.
[0208] Referring to FIG. 9, the terminal (940) may include a communication unit (945), a control unit (950), a storage unit (955), and an eUICC (960). The eUICC (960) may be detachable as described above, but is usually shipped non-removably fixed to the terminal, and is therefore indicated as a part of the terminal (940). The communication unit (945) may receive or transmit data to other devices. For example, the received data may be one of an encryption key, an encrypted profile, and certificate information. The transmitted data may be a response message according to the profile loading result. For this purpose, the communication unit (945) may be equipped with at least one communication module and an antenna, etc.
[0209] In addition, according to one embodiment of the present disclosure, the control unit (950) can control each component of the terminal (940) for installing a profile according to the present invention. The control unit (950) can control the overall operations of the terminal (940). For example, the control unit (950) can transmit and receive signals through the communication unit (945). In addition, the control unit (950) can record and read data in the storage unit (955). The control unit (950) can include at least one processor. For example, the control unit (950) can include a communication processor (CP) that performs control for communication and an application processor (AP) that controls upper layers such as application programs. According to one embodiment, when there is configuration information stored in the storage unit (955), the control unit (950) can request the configuration information from the storage unit (955) so that the screen display unit (not shown) can display it or receive the configuration information and process additional operations.
[0210] According to another embodiment, the control unit (950) may perform a processing process in which the terminal infers information that can be referenced for selecting a profile installation at the factory by matching the data recorded through the storage unit (955) or the information collected through the control unit (950) and the communication unit (945). The control unit (950) may control the terminal (940) to perform a corresponding operation. According to one embodiment, the control unit (950) may include an FPA responsible for driving and controlling the eUICC (960), an application in which the FPA is integrated and implemented, and an application managing the factory installation. In addition, the control unit (950) may include a terminal framework that interprets information received by the FPA or the application and processes a specific command APDU request to the CP (communication processor) or collects some or all of the requested information from the storage unit (955) and returns it to the FPA or the application.
[0211] In addition, according to one embodiment of the present disclosure, the control unit (955) may determine an operation to enter the IFPP mode by synthesizing predetermined information obtained from the eUICC (960) through the terminal (940) and the communication unit (945), and control the eUICC (960) to enter the IFPP mode. The eUICC (960) may operate under the control of the control unit (950). According to one embodiment of the present disclosure, the eUICC (960) may process a request for profile installation received from the control unit (950) and return the processing result to the control unit (950).
[0212] In addition, the control unit (950) according to one embodiment of the present disclosure may receive profile information or a response message of a profile package received from the factory IT (920), and, by referring to terminal settings or user input information at the time of reception, determine whether to perform profile installation in the factory mode, decide to enter the IFPP mode, or configure a message to be transmitted to the eUICC (960) to install the profile with IFPP. In addition, the control unit (950) may configure profile information of the profile package into one or more messages, and control to transmit a message including the profile information to the eUICC (960), or detect that an error occurs during the profile installation process and transmit a request for a cancel session to the eUICC (960). In addition, the control unit (950) can control the terminal (940) to receive the processing result received from the eUICC (960) at the terminal (940) or to determine whether to terminate the procedure and store the processing result in the storage unit (955), transmit the processing result to the communication unit (945), or control the terminal (940) to transmit the processing result to the factory IT (920) by the communication unit (945).
[0213] The storage unit (955) can store data such as basic programs, application programs, and setting information for the operation of the terminal (940). In one embodiment according to the present disclosure, the storage unit (955) may include at least one storage medium among a flash memory type, a hard disk type, a multimedia card micro type, a card type memory (e.g., SD or XD memory, etc.), a magnetic memory, a magnetic 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), and an electrically erasable programmable read-only memory (EEPROM). The storage unit (955) may be implemented as an integrated system on a chip (SoC) with the control unit (950). The control unit (950) can perform various operations using various programs, contents, data, etc. stored in the storage unit.
[0214] In Fig. 9, the eUICC (960) is a UICC chip embedded in the terminal (940) and can perform functions of storing, managing, and deleting at least one profile. A profile can be a general term for one or more applications, subscriber authentication information, phone book, and other data information stored in an existing UICC card. The eUICC (960) can be included as a part of the terminal (940) as illustrated in Fig. 1, and in the preceding drawings, the terminal (940) and the eUICC (960) are each expressed as separate modules to explain the operation between them. The eUICC (960) may include a control unit, a storage unit, and a communication unit for installing a profile. Some of the applications within the eUICC (960) may be installed in the control unit (950), and the installed applications may include some of the functions of the FPA.
[0215] According to one embodiment of the present disclosure, the control unit of the eUICC (960) may obtain profile installation request or deletion request information through a message of the terminal (920) received through the communication unit, and then process the profile installation or deletion, reply with a different loading result for the installation or deletion, process to create a pending notification and store it in the storage unit after the installation or deletion, determine whether to additionally delete the created pending notification, or delete the pending notification accordingly and reply with a response message. In addition, the control unit of the eUICC (960) may determine an action by determining whether to enter the IFPP through the information in the received message or a new function defined for the IFPP, and may process the profile installation or deletion procedure for the IFPP accordingly, and compare and verify the received information with the information in the storage unit of the eUICC (960). For example, when a command for a profile installation request is received, the control unit may verify the received profile package, perform an operation for installation, and sign and reply with the processing result to the terminal (940) through the communication unit. As mentioned in the embodiments of the present invention, an example of information that is processed through the control unit (950) by comparing and verifying with information in the storage unit of the eUICC (960) may be information such as the presence or absence of otPK.EUICC.KA used when installing or deleting a profile, a transaction ID mapped to a session, and certificate information of SM-DPf.
[0216] However, the components mentioned in FIG. 9 are not limited to the examples described above. For example, the factory IT (920) may include more or fewer components than the components described above. For example, the profile server (900) may include more or fewer components than the components described above. For example, the terminal (940) may include more or fewer components than the components described above. The terminal (940) according to various embodiments disclosed in this document may be an electronic device, and the electronic device may be a variety of devices. The electronic device may include, for example, a portable communication device (e.g., a smartphone), a computer device, a portable multimedia device, a portable medical device, a camera, a wearable device, or a home appliance device. The electronic device according to an embodiment of this document is not limited to the devices described above.
[0217] In various embodiments of the present disclosure, the operations of FPA, LPA, and eUICC are described separately. However, this is for convenience of explanation, and it should be noted that the operations of FPA, LPA, and eUICC can be described as operations of the terminal. For example, the transmission / reception operations of FPA can be described as transmission / reception operations of the terminal.
[0218] The methods according to the embodiments described in the claims or specification of the present disclosure may be implemented in the form of hardware, software, or a combination of hardware and software.
[0219] When implemented in software, a computer-readable storage medium storing one or more programs (software modules) may be provided. The one or more programs stored in the computer-readable storage medium are configured for execution by one or more processors within an electronic device. The one or more programs include instructions that cause the electronic device to execute methods according to the embodiments described in the claims or specification of the present disclosure.
[0220] These programs (software modules, software) may be stored in a random access memory, a non-volatile memory including a flash memory, a read only memory (ROM), an electrically erasable programmable read only memory (EEPROM), a magnetic disc storage device, a compact disc ROM (CD-ROM), a digital versatile disc (DVD) or other forms of optical storage, a magnetic cassette, or a memory formed by a combination of some or all of these. In addition, each configuration memory may include multiple copies.
[0221] Additionally, the program may be stored on an attachable storage device that is accessible via a communication network, such as the Internet, an intranet, a local area network (LAN), a wide LAN (WLAN), a storage area network (SAN), or a combination thereof. Such a storage device may be connected to a device performing an embodiment of the present disclosure via an external port. Additionally, a separate storage device on the communication network may be connected to a device performing an embodiment of the present disclosure.
[0222] In the specific embodiments of the present disclosure described above, components included in the disclosure are expressed in the singular or plural form, depending on the specific embodiment presented. However, the singular or plural expressions are selected to suit the presented situation for convenience of explanation, and the present disclosure is not limited to singular or plural components. Components expressed in the plural form may be composed of singular elements, or components expressed in the singular form may be composed of plural elements.
[0223] While the detailed description of this disclosure has described specific embodiments, it should be understood that various modifications are possible without departing from the scope of this disclosure. Therefore, the scope of this disclosure should not be limited to the described embodiments, but should be defined not only by the scope of the claims described below, but also by equivalents thereof.
Claims
1. A method performed by a profile server that provides a profile to be provisioned to an eUICC (embedded universal integrated circuit card), A step of receiving a request for provision of multiple BPPs (bound profile packages) from a terminal manufacturer server; A step for determining whether a delay in processing occurs when generating a BPP according to the above multiple BPP provision requests; When no delay processing occurs in generating BPPs according to the above multiple BPP provision requests, a step of generating the requested BPPs and transmitting them to the terminal manufacturer server; and A method comprising the step of transmitting, to the terminal manufacturer server, information on a processing time limit (comeback time) for processing the plurality of BPP provision requests, when it is determined that a delay in BPP generation according to the plurality of BPP provision requests will occur.
2. In paragraph 1, A method further comprising the step of generating BPPs corresponding to only some of the plurality of BPP provision requests and transmitting them to the terminal manufacturer server, if it is determined that a delay in processing will occur when generating BPPs according to the plurality of BPP provision requests.
3. In paragraph 2, A method wherein the above multiple BPP provision requests include information indicating that transmission of some of the requested BPPs is permitted.
4. In paragraph 1, A method further comprising the step of transmitting to the terminal manufacturer at least one of an error message, some of the BPPs requested for creation being completed, or the time remaining until the creation of all of the BPPs requested for creation is completed, if a connection request from the terminal manufacturer is received before the processing time limit expires.
5. In paragraph 1, A method further comprising the step of transmitting, to the terminal manufacturer, BPPs among the BPPs whose creation has been completed but which have not been previously transmitted to the terminal manufacturer, when a connection request from the terminal manufacturer is received after the processing time limit has elapsed.
6. In paragraph 1, A method wherein a BPP provision request received from the terminal manufacturer server includes information indicating that the BPP request is for IFPP (in factory profile provisioning).
7. In paragraph 1, A step of receiving a request for information on BPP generation capability from the terminal manufacturer server; and A method further comprising the step of transmitting information about the BPP generation capability of the profile server to the terminal manufacturer server.
8. A method performed by a terminal manufacturer server that performs profile provisioning on an eUICC (embedded universal integrated circuit card), A step of transmitting a provision request for multiple BPPs (bound profile packages) to a profile server; A step of receiving, from the profile server, information on a processing deadline (comeback time) for the plurality of BPP provision requests; and A method comprising the step of connecting to the profile server and receiving requested BPPs after the above processing time limit has elapsed.
9. In paragraph 8, A step of transmitting a request for information on BPP generation capability to the above profile server; and Further comprising a step of receiving information about the BPP generation capability of the profile server from the profile server, A method wherein the request for provision of the above plurality of BPPs is determined based on the BPP generation capability of the profile server.
10. In a profile server that provides a profile to be provisioned to an eUICC (embedded universal integrated circuit card), Department of Communications; and Includes a control unit, The above control unit, Receives a request for provision of multiple BPP (bound profile packages) from the terminal manufacturer server, Determine whether there is a delay in BPP generation according to the above multiple BPP provision requests. If there is no delay in BPP generation in response to the above multiple BPP provision requests, the requested BPPs are generated and transmitted to the terminal manufacturer server. A profile server configured to transmit, to the terminal manufacturer server, information on a processing time limit (comeback time) for processing the plurality of BPP provision requests, when it is determined that a delay in BPP generation will occur in response to the plurality of BPP provision requests.
11. In paragraph 10, The above control unit, A profile server further configured to generate BPPs corresponding to only some of the above multiple BPP provision requests and transmit them to the terminal manufacturer server when it is determined that a delay in processing will occur when generating BPPs according to the above multiple BPP provision requests.
12. In paragraph 10, The above control unit, A profile server further configured to transmit to the terminal manufacturer at least one of an error message, some of the BPPs requested for creation completed, or the time remaining until the creation of all BPPs requested for creation is completed, if a connection request from the terminal manufacturer is received before the processing time limit expires.
13. In paragraph 10, The above control unit, A profile server further configured to transmit to the terminal manufacturer, among the BPPs whose creation has been completed, BPPs that have not been previously transmitted to the terminal manufacturer, when receiving a connection request from the terminal manufacturer after the above processing time limit has elapsed.
14. In paragraph 10, The above control unit, Receive a request for information on BPP generation capability from the terminal manufacturer server, A profile server further configured to transmit information about the BPP generation capability of the profile server to the terminal manufacturer server.
15. In a terminal manufacturer server that performs profile provisioning on an eUICC (embedded universal integrated circuit card), Department of Communications; and Includes a control unit, The above control unit, Sends a request to the profile server to provide multiple BPPs (bound profile packages), Receives, from the above profile server, information on the processing time (comeback time) for the multiple BPP provision requests, A terminal manufacturer server set to receive requested BPPs by connecting to the profile server after the above processing time limit has elapsed.
Citation Information
Patent Citations
Matching network for antenna element of antenna array and electornic device including the same
KR1020230163252A
Apparatus for pet toilet training
KR102473718B1
ELECTRONIC SUBSCRIBER IDENTITY MODULE (eSIM) PROVISIONING ERROR RECOVERY
US20170338954A1
Technique for managing profile in communication system
US20180123803A1
MANAGING EMBEDDED UNIVERSAL INTEGRATED CIRCUIT CARD (eUICC) PROVISIONING WITH MULTIPLE CERTIFICATE ISSUERS (CIs)
US20190074983A1
