Method for SSP terminal to interoperate between bundle download process and ESIM configuration file download process

Abstract

Provided is a communication method and system for integrating a fifth generation (5G) communication system and Internet of Things (IoT) technology for supporting higher data rates beyond the fourth generation (4G) system. The communication method and system include smart services based on 5G communication technology and IoT-related technologies, such as smart homes, smart buildings, smart cities, smart cars, connected cars, healthcare, digital education, smart retail, safety and security services.

Description

Technical Field

[0001] The present disclosure relates to a method and apparatus for installing an embedded subscriber identity module (eSIM) profile when a bundle download process of a smart secure platform (SSP) terminal fails. Background Art

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

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

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

[0005] The above information is provided as background information only to assist with an understanding of the present disclosure. No determination has been made, and no assertion is made, as to whether any of the above might be applicable as prior art with respect to the present disclosure. Summary of the invention

[0006] Technical issues

[0007] Aspects of the present disclosure are intended to solve at least the above-mentioned problems and / or disadvantages and to provide at least the advantages described below. Therefore, one aspect of the present disclosure is to provide a method, wherein when in an SSP terminal, a server may not be able to process an SSP bundle download process or when the SSP terminal fails to install a bundle, the SSP terminal may perform a switch to an eSIM profile download process through the disclosed embodiments.

[0008] Another aspect of the present disclosure is to provide a method, which can be applied as a method in which, according to the present disclosure, when an SSP terminal attempts to download a bundle or fails to install a bundle, the SSP terminal selectively performs another operation defined in a corresponding family industry according to a family of the requested bundle.

[0009] Additional aspects will be set forth in part in the description which follows and, in part, will be obvious from the description, or may be learned by practice of the presented embodiments.

[0010] Solution to the problem

[0011] According to one aspect of the present disclosure, a method performed by a server in a wireless communication system is provided. The method includes: receiving a first message from a terminal requesting to download a bundle package; determining whether the bundle package can be installed based on the first message; and sending a second message including a family identifier-specific error code to the terminal if the bundle package cannot be installed.

[0012] In an embodiment, the family identifier specific error code includes information about the configuration file download.

[0013] In an embodiment, wherein the terminal selects a bundle previously installed in the terminal based on an error code specific to the family identifier included in the second message.

[0014] In an embodiment, based on the selected bundle, a configuration file regarding the bundle previously installed in the terminal is downloaded by the terminal.

[0015] In an embodiment, the first message includes at least one of smart security platform (SSP) information or terminal information.

[0016] According to another aspect of the present disclosure, a method performed by a terminal in a wireless communication system is provided. The method includes: sending a first message to a server requesting a bundle package download; and receiving a second message from the server including an error code specific to a family identifier if the bundle package cannot be installed, wherein whether the bundle package can be installed is determined by the server based on the first message.

[0017] According to another aspect of the present disclosure, a server is provided. The server includes a transceiver configured to send or receive at least one signal, and a controller / processor coupled to the transceiver, wherein the controller / processor is configured to: receive a first message requesting download of a bundle from a terminal; determine whether the bundle can be installed based on the first message; and send a second message including a family identifier-specific error code to the terminal if the bundle cannot be installed.

[0018] According to another aspect of the present disclosure, a terminal is provided. The terminal includes a transceiver configured to send or receive at least one signal, and a controller / processor coupled to the transceiver, wherein the controller / processor is configured to: send a first message requesting a bundle package download to a server; and receive a second message including a family identifier specific error code from the server if the bundle package cannot be installed, wherein whether the bundle package can be installed is determined by the server based on the first message.

[0019] In addition, an embodiment may provide a method, the method comprising: transmitting SSP information and terminal information to a server of a secondary platform bundle (SPB) manager when an SSP terminal requests a bundle download; determining, by the SPB manager, the compatibility of the bundle based on the terminal information and SSP information provided by the SSP terminal that has requested the bundle download; determining, by the SPB manager, whether switching to eSIM profile download is possible when the SSP terminal fails to download the bundle due to the absence of a bundle compatible with the SSP terminal that has requested the bundle; determining, by the SPB manager, whether the SSP terminal is capable of performing switching to eSIM profile download; generating, by the SPB manager, a family identifier-specific error code; sending the generated family identifier-specific error code and an error message to the SSP terminal; and performing, by the SSP terminal, an eSIM profile download process by applying the eSIM bundle, a local profile assistant (LPA), and information included in the family identifier-specific error code.

[0020] According to another aspect of the present disclosure, a method is provided. The method includes: when a bundle installation fails, generating a notification message by an SSP terminal and transmitting it to an SPB manager; determining by the SPB manager whether switching to eSIM profile download is possible; determining by the SPB manager whether the SSP terminal is capable of performing switching to eSIM profile download; generating a family identifier-specific error code by the SPB manager; sending the generated family identifier-specific error code to the SSP terminal as a response to the notification message; and performing an eSIM profile download process by the SSP terminal by applying information included in the eSIM bundle, LPA, and the family identifier-specific error code.

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

[0022] Advantageous Effects of the Invention

[0023] According to various embodiments, even when installation is not possible, the SSP terminal may provide services by downloading a telecommunication bundle from the SPB manager server or downloading a configuration file to an eSIM bundle of the SSP terminal.

[0024] Furthermore, according to various embodiments, user convenience may be increased by minimizing user intervention through linking on a protocol between the processes of SSP bundle download and configuration file download.

[0025] Other aspects, advantages, and salient features of the disclosure will become apparent to those skilled in the art from the following detailed description, which, taken in conjunction with the annexed drawings, discloses various embodiments of the disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] The above and other aspects, features and advantages of certain embodiments of the present disclosure will become more apparent from the following description in conjunction with the accompanying drawings, in which:

[0027] Figure 1 is a diagram showing internal elements of an SSP terminal and interfaces between the elements according to an embodiment of the present disclosure;

[0028] Figure 2 is a diagram showing an example of internal and external elements of a terminal for downloading a bundle package by an SSP terminal according to an embodiment of the present disclosure;

[0029] Figure 3 is a diagram showing a process in which an SSP terminal switches to an eSIM profile download process during a bundle download process according to an embodiment of the present disclosure;

[0030] Figure 4A is a diagram showing a flowchart of a process in which an SSP terminal receives a family identifier-specific error code from an SPB manager according to an embodiment of the present disclosure;

[0031] Figure 4B is a diagram illustrating a flow chart of a process according to an embodiment of the present disclosure, in which the LBA transmits a notification message to the SPB manager, and in response thereto, when the SSP terminal fails to install an encryption bundle received from the SPB manager, the SSP terminal receives a family identifier specific error code;

[0032] Figure 5A is a diagram illustrating a next operation when an LBA of an SSP terminal receives a family identifier specific error code transmitted from an SPB manager during a bundle download process according to an embodiment of the present disclosure;

[0033] Figure 5Bis a diagram illustrating a next operation when an LBA of an SSP terminal receives a family identifier specific error code transmitted from an SPB manager during a bundle download process according to an embodiment of the present disclosure;

[0034] Fig. 6A is a diagram showing a flowchart of the operation of the SPB manager when the SPB manager receives a bundle download request from an SSP terminal according to an embodiment of the present disclosure;

[0035] Figure 6B is a diagram showing a flowchart of the operation of the SPB manager when the SPB manager receives a bundle download request from an SSP terminal according to an embodiment of the present disclosure;

[0036] Figure 6C is a diagram showing a flowchart of the operation of the SPB manager when a bundle installation failure notification message is received from an SSP terminal according to an embodiment of the present disclosure;

[0037] Fig.6D is a diagram showing a flowchart of the operation of the SPB manager when a bundle installation failure notification message is received from an SSP terminal according to an embodiment of the present disclosure;

[0038] Fig. 7A is a diagram showing a flowchart of the operation when an LBA of an SSP terminal receives a response to a request that the LBA has sent to an SPB manager during a bundle download process according to an embodiment of the present disclosure;

[0039] Figure 7BA and Figure 7BB is a diagram illustrating a flowchart of operations when an LBA of an SSP terminal receives a response to a request that the LBA has sent to an SPB manager during a bundle download process according to various embodiments of the present disclosure;

[0040] Figure 7CA and Figure 7CB is a diagram illustrating a flowchart of operations when an LBA of an SSP terminal receives a response to a request that the LBA has sent to an SPB manager during a bundle download process according to various embodiments of the present disclosure;

[0041] Fig. 8A is a diagram showing a flowchart of an operation when an LBA of an SSP terminal receives a response to a notification message that the LBA has sent to an SPB manager during a bundle download process according to an embodiment of the present disclosure;

[0042] Figure 8B is a diagram showing a flowchart of an operation when an LBA of an SSP terminal receives a response to a notification message that the LBA has sent to an SPB manager during a bundle download process according to an embodiment of the present disclosure;

[0043] Figure 8CA and Figure 8CB is a diagram illustrating a flowchart of operations when an LBA of an SSP terminal receives a response to a notification message that the LBA has sent to an SPB manager during a bundle download process according to various embodiments of the present disclosure;

[0044] Fig. 9 is a diagram showing a structure of a terminal according to an embodiment of the present disclosure; and

[0045] Fig.10 is a diagram showing a structure of a server according to an embodiment of the present disclosure.

[0046] Throughout the drawings, like reference numerals will be understood to refer to like parts, components and structures. DETAILED DESCRIPTION

[0047] The following description with reference to the accompanying drawings is provided to assist in a comprehensive understanding of the various embodiments of the present disclosure as defined by the claims and their equivalents. It includes various specific details that aid in understanding, but these are considered to be exemplary only. Therefore, it will be appreciated by those of ordinary skill in the art that various changes and modifications may be made to the various embodiments described herein without departing from the scope and spirit of the present disclosure. In addition, for the sake of clarity and conciseness, descriptions of well-known functions and structures may be omitted.

[0048] The terms and words used in the following description and claims are not limited to the bibliographical meanings, but are merely used by the inventor to enable a clear and consistent understanding of the present disclosure. Therefore, it will be apparent to those skilled in the art that the following description of various embodiments of the present disclosure is provided for illustrative purposes only and not for the purpose of limiting the present disclosure as defined by the appended claims and their equivalents.

[0049] It will be understood that the singular forms "a," "an," and "the" include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to "a component surface" includes reference to one or more of such surfaces.

[0050] Here, it will be understood that each block of the flowchart illustration and the combination of blocks in the flowchart illustration can be implemented by computer program instructions. These computer program instructions can be loaded into a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, so that the instructions executed by the processor of the computer or another programmable data processing device create a device for implementing the functions specified in the (multiple) flowchart blocks. These computer program instructions can also be stored in a computer-usable or computer-readable memory, which can instruct the computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-usable or computer-readable memory produce an article of manufacture including an instruction device for implementing the functions specified in the flowchart block. The computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operations are performed on the computer or other programmable data processing device, thereby generating a computer-implemented process, so that the instructions executed on the computer or other programmable data processing device provide operations for implementing the functions specified in the (multiple) flowchart blocks.

[0051] In addition, each block of the flowchart diagram may represent a module, a code segment or a code portion, which includes one or more executable instructions for implementing (multiple) specified logical functions. It should also be noted that in some alternative embodiments, the functions mentioned in the blocks may not occur in order. For example, depending on the functions involved, two blocks shown in succession may actually be executed substantially simultaneously, or these blocks may sometimes be executed in reverse order.

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

[0053] Specific terms used in the following description are provided to help understanding of the present disclosure, and the use of these specific terms may be modified in other forms without departing from the technical idea of ​​the present disclosure.

[0054] A secure element (SE) indicates a security module configured as a single chip, which can store security information (e.g., mobile communication network access keys, user identification information such as ID cards and passports, credit card information, encryption keys, etc.), and can include and operate a control module loaded thereon and using the stored security information (e.g., a network access control module such as a USIM, an encryption module, a key generation module, etc.). SE can be applied to various electronic devices (e.g., smartphones, tablet PCs, wearable devices, vehicles, IoT devices, etc.), and can provide security services (e.g., mobile communication network access, payment, user authentication, etc.) through security information and control modules.

[0055] SE can be divided into universal integrated circuit card (UICC), embedded secure element (eSE) and smart security platform (SSP) which is an integrated form of UICC and eSE, and can be subdivided into removable type, embedded type and integrated type in which SE is integrated into specific components or system on chip (SoC) depending on the form of connection or installation to electronic equipment.

[0056] UICC is a smart card inserted into a mobile communication terminal for use, and is referred to as a UICC card. UICC may include an access control module for accessing the network of a mobile network operator. Examples of access control modules include a universal subscriber identity module (USIM), a subscriber identity module (SIM), an IP multimedia service identity module (ISIM), and the like. A UICC including a USIM may generally be referred to as a USIM card. Similarly, a UICC including a SIM module may generally be referred to as a SIM card. At the same time, a SIM module may be installed when the UICC is manufactured, or a user may download the SIM module of the service to be used by the user to the UICC card when the user wants to use a mobile communication service. In addition, a UICC card may download and install multiple SIM modules, and select and use at least one SIM module therein. The UICC card may be fixed to or fixed to a terminal. A UICC fixed to a terminal for use is referred to as an embedded UICC (eUICC), and specifically, a UICC embedded in a communication processor of a terminal, an application processor of a terminal, or a system on a chip (SoC) having a single processor structure in which two processors are integrated may be referred to as an integrated UICC (iUICC). Generally, eUICC and iUICC are fixed to the terminal for use, and can indicate a UICC card that can remotely download and select a SIM module. In the present disclosure, a UICC card that can remotely download and select a SIM module is collectively referred to as eUICC or iUICC. That is, among UICC cards that can remotely download and select a SIM module, UICC cards that are fixed to or not fixed to a terminal are collectively referred to as eUICC or iUICC. In addition, eUICC profile, iUICC profile, or more simply, profile is used as a general term to indicate downloaded SIM module information.

[0057] Embedded security element (eSE) indicates an embedded type SE fixed to an electronic device to be used. eSE is usually manufactured for manufacturers only by request of terminal manufacturers, and can be manufactured by including an operating system and architecture. eSE remotely downloads and installs a service control module of applet type, and can be used for various security services such as electronic wallets, ticketing, electronic passports, and digital keys. In the present disclosure, single-chip type SEs that are attached to electronic devices and can remotely download and install service control modules are collectively referred to as eSEs.

[0058] A smart security platform (SSP) can integrate the functions of a UICC and an eSE on a single chip, and can be referred to as an SSP for short. An SSP can be divided into a removable SSP (rSSP), an embedded SSP (eSSP), and an integrated SSP (iSSP) embedded in a SoC. An SSP can be composed of a primary platform (PP) and at least one auxiliary platform bundle (SPB) running on the PP, the primary platform can include at least one of a hardware platform and a low level operating system (LLOS), and the auxiliary platform bundle can include at least one of a high-level operating system (HLOS) and an application operating on the HLOS. An auxiliary platform bundle is also referred to as an SPB or a bundle. The bundle can access resources such as a central processing unit and a memory of the PP through a primary platform interface (PPI) provided by the PP, and operate on the PP through the interface. The bundle can allow communication applications such as a subscriber identity module (SIM), a universal SIM (USIM), and an IP multimedia SIM (ISIM) to be installed therein, and can also allow various applications such as an electronic wallet, ticketing, an electronic passport, and a digital key to be installed therein.

[0059] According to the bundle package that is downloaded and installed remotely, the SSP can be used for the above-mentioned UICC or eSE, and by installing multiple bundle packages on a single SSP and operating all the bundle packages, the SSP can be used for both UICC and eSE. That is, when a bundle package including a configuration file is operated, the SSP can be used for the UICC to access the network of the mobile network operator. Similar to the eUICC or iUICC, the corresponding UICC bundle package can be operated by remotely downloading at least one configuration file therein and selecting the configuration file. In addition, when a bundle package including a service control module is operated, the SSP can be used for the eSE, and the service control module includes an application installed therein, and can provide services such as an electronic wallet, ticketing, an electronic passport, and a digital key. Multiple service control modules can be operated by being integrated with a single bundle package for installation, or each service control module can be operated by being installed in a separate bundle package.

[0060] Hereinafter, the terms used in the present disclosure will be described in more detail.

[0061] In the present disclosure, SSP indicates a chip-type security module that can integrate the functions of UICC and eSE on a single chip, and is divided into a removable SSP (rSSP), an embedded SSP (eSSP), and an integrated SSP (iSSP) embedded on a SoC. The SSP can download bundles from an external bundle management server (Secondary Platform Bundle Manager, SPB Manager) and install bundles by using over the air (OTA) technology.

[0062] In the present disclosure, a method in which an SSP downloads and installs a bundle package by using OTA technology can be equally applied to a removable SSP (rSSP) that can be inserted into or removed from a terminal, an embedded SSP (eSSP) installed in a terminal, and an integrated SSP (iSSp) embedded in a SoC installed in a terminal.

[0063] In the present disclosure, the term for UICC may be used interchangeably with the term for SIM, and the term for eUICC may be used interchangeably with the term for eSIM.

[0064] In the present disclosure, SPB operates on PP by using the resources of PP of SSP, for example, UICC bundle may indicate the software package of applications stored in existing UICC, file system, value of authentication key and operating system (HLOS) in which they operate. SPB may be referred to as bundle.

[0065] A USIM profile may have the same meaning as a profile, or may indicate a package of information included in a USIM application of a profile.

[0066] The operation of enabling a bundle by a terminal or an external server may indicate an operation of changing the state of a corresponding configuration file to an enabled state to configure the terminal to receive services provided by the corresponding bundle (e.g., communication services via a mobile operator, credit card payment services, user authentication services, etc.). A bundle in an enabled state may be represented as an "enabled bundle". A bundle in an enabled state may be stored in a storage space inside or outside the SSP while being in an encrypted state.

[0067] Depending on the bundle external input (e.g., user input, push, request from application in terminal, authentication request from mobile operator, PP management message, etc.) or bundle internal operation (e.g., timer and polling), the enabled bundle can be changed to be in active state. The active bundle can be loaded from the storage space inside or outside the SSP to the active memory inside the SSP, can process security information by using the security control device (security CPU) inside the SSP, and can provide security services to the terminal.

[0068] The operation of disabling a bundle by a terminal or an external server may indicate an operation of changing the state of the corresponding bundle to a disabled state so as to configure the terminal not to receive the service provided by the corresponding bundle. The configuration file in the disabled state may be represented as a "disabled bundle". The bundle in the enabled state may be stored in a storage space inside or outside the SSP while being in an encrypted state.

[0069] In the present disclosure, the bundle management server may include the following functions: generating a bundle through a request from a service provider or other bundle management server; encrypting the generated bundle; generating a bundle remote management instruction; or encrypting the generated bundle remote management instruction. The bundle management server providing the above functions may be represented as at least one of an auxiliary platform bundle manager (SPB manager), a remote bundle manager (RBM), an image delivery server (IDS), subscription manager data preparation (SM-DP), subscription manager data preparation + (SM-DP +), a manager bundle server, a management subscription manager data preparation + (management SM-DP +), a bundle encryption server, a bundle generation server, a bundle provisioner (BP), a bundle provider, and a bundle provisioning credential holder (BPC holder).

[0070] The bundle management server can download, install or update the bundle in the SSP, and manage the settings of keys and certificates for remote management of the bundle status. The bundle management server providing the above functions can be represented as at least one of an SPB manager, an RBM, an IDS, a subscription manager secure routing (SM-SR), a subscription manager secure routing + (SM-SR+), an off-card entity of an eUICC profile manager, a profile management credential holder (PMC holder), or an eUICC manager (EM).

[0071] The open relay server may be represented as at least one of an SPB manager, an RBM, a secondary platform bundle discovery server (SPBDS), a bundle discovery server (BDS), a subscription manager discovery service (SM-DS), a discovery service (DS), a root inauguration relay server (root SM-DS), and an alternative inauguration relay server (alternative SM-DS). The inauguration relay server may receive an event registration request (register event request) from one or more bundle management servers and inauguration relay servers. In addition, one or more inauguration relay servers may be used in a composite manner, and in this case, the first inauguration relay server may receive an event registration request not only from the bundle management server, but also from the second inauguration relay server. In the present disclosure, the function of the inauguration relay server may be integrated with the bundle management server.

[0072] The term "terminal" used in the present disclosure may be referred to as a mobile station (MS), a user equipment (UE), a user terminal (UT), a wireless terminal, an access terminal (AT), a terminal, a subscriber unit, a subscriber station (SS), a wireless device, a wireless communication device, a wireless transmission / reception unit (WTRU), a mobile node, a mobile phone or other terms. Various embodiments of the terminal may include a cellular phone, a smart phone with a wireless communication function, a personal digital assistant (PDA) with a wireless communication function, a wireless modem, a portable computer with a wireless communication function, a photographing device such as a digital camera with a wireless communication function, a gaming device with a wireless communication function, a home appliance with a wireless communication function for storing and reproducing music, an Internet home appliance capable of performing wireless Internet access and browsing, and a portable unit or terminal with an integrated combination of its functions. In addition, the terminal may include a machine-to-machine (M2M) terminal and a machine type communication (MTC) terminal / device, but is not limited thereto. In the present disclosure, a terminal may be referred to as an electronic device. The electronic device may include an SSP embedded therein, and a bundle may be downloaded and installed. When the SSP is not embedded in the electronic device, the SSP physically separated from the electronic device may be inserted into the electronic device to be connected to the electronic device. For example, the SSP may be inserted into the electronic device in the form of a card. The electronic device may include a terminal, and the terminal may be a terminal including an SSP capable of downloading and installing the bundle. The SSP may be embedded in the terminal, and when the SSP is separated from the terminal, the SSP may also be inserted into the terminal to be connected to the terminal.

[0073] The terminal or electronic device may include a local bundle assistant (LBA) or a local bundle manager (LBM), which is software or an application installed in the terminal or electronic device to control the SSP. The LBA application may download bundles to the SSP, or transmit commands to the SSP to activate, deactivate, and delete installed bundles.

[0074] The terminal or electronic device may include a Local Profile Assistant (LPA), which is software or an application installed in the terminal or electronic device to control the eUICC. The LPA may be implemented by being included in the LBA, or may exist as an application separate from the LBA in the terminal. The LPA may be software or an application capable of controlling the eSIM bundle of the terminal including the SSP embedded therein.

[0075] In the present disclosure, a bundle identifier may be referred to as a factor that matches a bundle family identifier (SPB family identifier), a bundle match ID, and an event identifier (event ID). A bundle identifier (SPB ID) may represent a unique identifier for each bundle. A bundle family identifier (SPB family identifier) ​​may represent an identifier that identifies the type of a bundle (e.g., a telecommunications bundle for accessing a mobile network operator's network). A bundle delimiter may be used as a value that can index a bundle in a bundle management server. In the present disclosure, an SSP identifier (SSP ID) may be a unique identifier of an SSP embedded in a terminal, and may be referred to as an sspID. In addition, as shown in an embodiment, when the terminal and the SSP chip are not separated from each other, the SSP identifier may be a terminal ID. In addition, the SSP identifier may be referred to as a specific bundle identifier (SPB ID) in an SSP. More specifically, an SSP identifier may be referred to as a loader (auxiliary platform bundle loader, SPBL) that installs other bundles in an SSP and manages their activation, deactivation, and deletion, or a bundle identifier that manages a bundle. An SSP may have multiple SSP identifiers, and the multiple SSP identifiers may be values ​​derived from a unique single SSP identifier.

[0076] The loader (SPBL) may be referred to as a management bundle that installs other bundles in the SSP and manages their activation, deactivation, and deletion. The LBA of the terminal or a remote server may install, activate, deactivate, or delete a specific bundle through the loader. In the present disclosure, the loader may also be referred to as an SSP.

[0077] In the present disclosure, an event may be a term generally referred to as an instruction for bundle download, remote bundle management, or management / processing of another bundle or SSP. An event may be referred to as a remote bundle provisioning operation, an RBP operation, or an event record, and each event may be referred to as data including at least one of an event identifier (event ID, eventID) or a matching identifier (matching ID, matchingID) corresponding thereto and each server identifier or address (FQDN, IP address, or URL) of a startup relay server or bundle management server storing the corresponding event. The terms used for bundle download may be used interchangeably with the terms used for bundle installation. In addition, an event type may be used as a term indicating whether a particular event indicates a bundle download, remote bundle management (e.g., deletion, activation, deactivation, replacement, update, etc.), or management / processing command of an SSP or other bundle, and may be referred to as an operation type (operationtype), an operation class (operationclass), an event request type, an event class, an event request class, and the like.

[0078] Local bundle management (LBM) may be referred to as bundle local management, local management, local management command, local command, local bundle management package (LBM package), bundle local management package, local management package, local management command package, and local command package. LBM may change the state (enable, disable, delete) of a specific bundle through software installed in a terminal, etc., or may be used to change (update) the content of a specific bundle (e.g., bundle nickname, bundle summary information (bundle metadata), etc.). LBM may include one or more local management commands, and in this case, for each local management command, the target bundle of each local management command may be the same or different.

[0079] In the present disclosure, a target bundle may be used as a term indicating a bundle that is a target of a local management command and a remote management command.

[0080] In addition, the service provider can request to generate a bundle by issuing a demand to the bundle management server, and can indicate the enterprise that provides services to the terminal through the corresponding bundle. For example, the service provider can indicate a mobile operator that provides communication network access services by including a bundle of communication applications loaded therein, and can be collectively referred to as all business support systems (business supporting system, BSS), operation support systems (operational supporting system, OSS), point of sale (point of sale, POS) terminals and other IT systems of the mobile operator. In the present disclosure, the service provider is not limited to representing only one specific enterprise, and can be used as a term indicating a group or association (or consortium) of one or more enterprises and a representative representing a corresponding group or association. In addition, the service provider can be referred to as an operator (OP or Op), a bundle owner (bundle owner, BO), an image owner (imageowner, IO), etc., and each service provider can configure at least one name and / or unique identifier (object identifier, OID), or can receive at least one name and / or unique identifier assigned. If the service provider indicates a group, association or representative of one or more enterprises, the name or unique identifier of any group, association or representative can be a name or unique identifier shared by all enterprises belonging to the corresponding group or association and all partners of the corresponding representative.

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

[0082] In the present disclosure, the telecom bundle may include at least one NAA loaded therein, or may be a bundle having a function of remotely downloading and installing at least one NAA. The telecom bundle may include a telecom bundle identifier indicating the telecom bundle.

[0083] In the present disclosure, an eSIM bundle may be a bundle in which an eUICC OS operates and runs like an eUICC to enable a terminal to receive a configuration file. The eSIM bundle may include a telecommunication bundle identifier indicating the eSIM bundle.

[0084] In the present disclosure, the eSIM activation code is predetermined information for downloading a configuration file to an eSIM terminal or an SSP terminal, and may be referred to as an eSIM activation code. The eSIM activation code may include an address of an SM-DS server or an SM-DP+ address that can notify the SM-DP+ address (which should be accessed in order to download the configuration file), and may include an activation code token value, which may be used as a matching identifier for a specific configuration file for SM-DP+. When the eSIM activation code is input in the form of a QR code, "LPA:" may be added as a prefix to the data included in the QR code.

[0085] In the present disclosure, the SSP activation code is predetermined information for downloading the bundle to the SSP terminal and may be referred to as the SSP activation code. The terminal user may start the bundle download process by inputting the SSP activation code into the LBA application of the SSP terminal. The SSP activation code may include an eSIM activation code.

[0086] The activation code may be collectively referred to as an SSP activation code and an eSIM activation code. Generally, in the present disclosure, before determining whether the activation code is an SSP activation code or an eSIM activation code, the activation code may be any activation code, and when input into the terminal, may be interpreted by the terminal as one of an SSP activation code or an eSIM activation code. When the SSP activation code includes an eSIM activation code, the terminal may selectively perform bundle download and configuration file download.

[0087] In the present disclosure, the function called by LBA may include a function executed in a Si2 interface, which is an interface between LBA and SPB manager, and a function executed in a Si3 interface, which is an interface between LBA and auxiliary platform bundle loader. LBA may transmit parameters to SPB manager or auxiliary platform bundle loader through a specific function. The parameters transmitted from LBA through a specific function call may indicate a command, a function command or a function instruction of a corresponding function. When receiving a function command, SPB manager or auxiliary platform bundle loader may perform a specific operation according to the function command and then respond to the function command. The response may include parameters. The function command and the operation corresponding thereto transmitted through the Si3 interface, as well as the response to the function command may be composed of a plurality of function commands, the operation corresponding thereto and the response to the sub-function command.

[0088] Function command transmission through Si2 interface can use Hypertext Transfer Protocol (HTTP). Specifically, function command transmission through Si2 interface can be performed through HTTP POST request message of HTTP, and command can be included in the body part of HTTP POST request message to be transmitted.

[0089] In the present disclosure, the object identifier of a management agent may represent the object identifier of an agent that manages a specific family identifier. For a specific family identifier, there may be multiple management agents, and each agent may have an object identifier. The SSP terminal, the service provider, and the bundle management server may know which agent is the main management agent of the bundle and who performs bundle management including downloading through the object identifier of the management agent. In addition, which main management agent manages the service to be provided by the corresponding bundle may be identified through the object identifier of the management agent.

[0090] In the present disclosure, the SSP information may include first SSP information and second SSP information. The first SSP information is SSP related information and may include unencrypted data. The first SSP information may be interpreted by the LBA and SPB managers without any special decryption process. The second SSP information may include data obtained by encrypting the SSP related information.

[0091] In the present disclosure, the first bundle information may include metadata, bundle metadata, and metadata of the auxiliary platform bundle. The first bundle information may include unencrypted data about the bundle that the service provider or bundle management server (SPB manager) will download to the SSP terminal, which can be read by the LBA of the SSP terminal. Based on the first bundle information, the LBA of the SSP terminal can receive the user's permission before receiving the second bundle information of the corresponding bundle, or can identify whether the user's permission and intention are required for operation / management after the bundle is installed. The first bundle information can be used by the LBA to display basic information of the bundle to the user before the bundle is installed. After the bundle is installed, the first bundle information can be managed by a loader (auxiliary platform bundle loader, SPBL) and can be updated by the service provider, the bundle management server (SPB manager), etc.

[0092] In the present disclosure, the encrypted second bundle information may include a bound auxiliary platform bundle image, a bound bundle (bound auxiliary platform bundle), an encrypted auxiliary platform bundle image, and an encrypted bundle (encrypted auxiliary platform bundle). The second bundle information may include the first bundle information. The second bundle information includes information required for bundle installation, and the SSP may install the bundle in the SSP by using data extracted from the second bundle information. A portion of the second bundle information may be encrypted into a session key generated by the SSP and the SPB manager.

[0093] In the present disclosure, the bundle information request function may include a function of requesting the first bundle information and the second bundle information of the bundle to be installed by the SSP terminal. The operation of requesting the first bundle information and the second bundle information of the bundle may be performed by sending a bundle information request function command to the SPB manager. The bundle information request function command may be transmitted by the SSP terminal to the SPB manager through the Si2 interface. The SSP terminal may request the first bundle information or the second bundle information by transmitting terminal information and an SSP credential to the SPB manager, the SSP credential including an SSP certificate, SSP information, and an SSP function (capability). The bundle information request function may be identified by using an identifier or a delimiter included in the command. In another example, the bundle information request function may be identified by defining different commands for the bundle information request function.

[0094] In describing the present disclosure, when it is determined that a detailed description about a related announced function or configuration unnecessarily obscures the main idea of ​​the present disclosure, the detailed description is omitted.

[0095] Various embodiments will be described hereinafter. An embodiment relates to a method in which, in a case where the SPB manager may not be able to process the bundle download when the SSP terminal attempts to download the bundle, the SSP terminal performs an eSIM profile download procedure.

[0096] Specifically, for the above-mentioned purpose, the present disclosure includes the following embodiments.

[0097] A method for transmitting eSIM functional capabilities including whether the SSP terminal holds an eSIM bundle or an eSIM activation code to an SPB manager when an SSP terminal requests a bundle download.

[0098] A method in which an SPB manager, in response to a bundle download request from an SSP terminal, determines whether the corresponding bundle is compatible with the SSP terminal.

[0099] A method in which an SPB manager sends an error message and a family identifier specific error code to an SSP manager to enable the SSP terminal to perform a handover to an eSIM profile download procedure in a case where the SPB manager may not be able to download a bundle to the SSP terminal due to not having a bundle that is compatible with the SSP terminal that has requested the bundle download.

[0100] A method in which during the bundle download process, the SSP terminal performs a switch to other operations, such as a switch to an eSIM profile process, by applying an eSIM activation code held by the SPB manager or a family identifier specific error code that has been sent by the SPB manager.

[0101] Hereinafter, various embodiments relate to a method in which the SSP terminal performs an eSIM profile download process in a case where the SPB manager may not be able to process the bundle download when the SSP terminal attempts to perform the bundle download. The embodiments will be described in detail with reference to the accompanying drawings.

[0102] Figure 1 is a diagram showing internal elements of an SSP terminal and interfaces between the elements according to an embodiment of the present disclosure.

[0103] refer to Figure 1 , the SSP terminal 101 may be composed of an SSP 131 and a local bundle assistant (LBA) 111 as terminal software. In addition, the SSP terminal 101 may include: a transceiver for sending / receiving signals to / from other terminals, base stations, servers, etc.; and a controller for controlling the overall operation of the SSP terminal 101. According to various embodiments, the controller may control the operation of the SSP terminal 101. The controller may include at least one processor. The controller may control the SSP 131 through the LBA 111.

[0104] The LBA 111 may include a function of a local profile assistant (LPA) 112 embedded therein. The SSP 131 is composed of a secondary platform bundle (SPB bundle), a main platform 135, and a main platform interface 134. The SPB loader (SPBL) 132 and the eSIM bundle 133 are a type of bundle. The LBA 111 and the SPBL 132 exchange packets through the first interface 122, and the LBA 111 can perform the following operations through the first interface.

[0105] -Get SSP information

[0106] - Sends bundle data to be installed in SSP to the loader

[0107] - Manage (activate, deactivate, delete, etc.) bundles installed in the SSP

[0108] The LPA 112 and the eSIM bundle 133 installed in the SSP 131 may exchange packets through the second interface 123 , and the LPA 112 may perform functions defined in GSMA SGP.22 with respect to the eSIM bundle 133 through the second interface 123 .

[0109] Figure 2 203 is a diagram showing an example of internal and external elements of a terminal for downloading a bundle package by an SSP terminal according to an embodiment of the present disclosure. The terminal 203 may correspond to Figure 1 SSP terminal 101. LBA 204 may correspond to Figure 1 LBA 111. SPB loader 206 may correspond to Figure 1 The bundle 207 may be a secondary platform bundle (SPB). For a description of the terminal 203, LBA 204, and SPB loader 206, refer to Figure 1 Embodiment of the invention.

[0110] refer to Figure 2 , the user 200 can select a service provided by the user 200 (e.g., a data service via a mobile communication network, etc.) in the service subscription process 210, and can subscribe to the service. In order to use the service provided by the service provider 201, the user 200 can selectively transmit to the service provider 201 an identifier (SSP ID) of the SSP 205 installed in the terminal 203 where the bundle is to be installed. According to an embodiment, in Figure 2 In the service subscription process 210, the user 200 may receive an SSP activation code in the form of a QR code from the service provider 201, which enables the bundle to be installed in the user terminal after subscribing to the service. According to an embodiment, the SSP activation code received by the user after subscribing to the telecommunication service may include information for downloading the telecommunication bundle and an eSIM activation code for downloading an eSIM profile instead of the telecommunication bundle.

[0111] In the bundle manufacturing demand transmission process 211, the service provider 201 and the SPB manager 202 may perform a bundle download preparation process. In the bundle manufacturing demand transmission process 211, the service provider 201 may selectively transmit to the SPB manager 202 an identifier (SSP ID) of the SSP 205 that is to install the bundle, and may transmit to the SPB manager 202 at least one of a bundle family identifier (SPB family ID) and a specific bundle identifier (SPBID) that can provide a service selected by a subscriber. In the bundle manufacturing demand transmission process 211, the SPB manager 202 may select one of a bundle having the transmitted specific bundle identifier or a bundle having a bundle family identifier, and may transmit the identifier of the selected bundle to the service provider 201. In the bundle manufacturing demand transmission process 211, the service provider 201 or the SPB manager 202 may generate a new bundle matching ID that can identify the selected bundle. In addition, the SPB manager 202 may connect and manage the transmitted SSP identifier (SSP ID) and the selected bundle. In the bundle manufacturing requirement transmission process 211, the SPB manager 202 may transmit the bundle management server address (SPB manager address) from which the selected bundle can be downloaded to the service provider 201. The bundle management server address may be the address of a specific or any bundle management server storing the prepared bundle, and may be the address of other bundle management servers that may store and obtain download information (server address, etc.) of the prepared bundle. When the service provider 201 requests the SPB manager 202 to prepare a telecom bundle in the bundle manufacturing requirement transmission process 211, information about an eSIM profile matching the corresponding telecom bundle may be provided together.

[0112] When a part of the bundle manufacturing demand transmission process 211 precedes the service subscription process 210, the service provider 201 may transmit the prepared bundle download information to the user 200 in the service subscription process 210. The bundle download information may selectively transmit at least one of a bundle management server address (SPB manager address) of the prepared bundle, a bundle matching ID of the prepared bundle, and a bundle family identifier (SPB family ID) of the prepared bundle.

[0113] refer to Figure 2, in the bundle information input process 231 to be downloaded, the bundle download information may be transmitted to the LBA 204 of the terminal 203. The bundle download information may be one of the address of the bundle management server to be accessed by the LBA 204 (SPB manager address), the bundle delimiter of the bundle prepared in the bundle manufacturing demand transmission process 211, and the bundle family identifier of the prepared bundle. The bundle delimiter may include at least one of the bundle event ID or the bundle matching ID generated in the bundle manufacturing demand transmission process 211. In addition, the bundle delimiter may include the bundle family identifier of the prepared bundle. The bundle event ID may include at least one of the bundle matching ID of the bundle prepared in the bundle manufacturing demand transmission process 211 and the address of the bundle management server. The user 200 may input (e.g., QR code scanning, direct text input, etc.) an SSP activation code to the LBA 204, or use push input through an information provision server (not shown) to input the bundle download information to the LBA 204. In addition, the LBA 204 may access an information provision server (not shown) pre-configured in the terminal 203 to receive bundle download information.

[0114] The download of the bundle from SPB manager 202 to SSP 205 may be implemented by functions and operations performed in interface 221 between SPB manager 202 and LBA 204 and interface 222 between LBA 204 and SPB loader 206. Interface 222 between LBA 204 and SPB loader 206 may correspond to Figure 1 The first interface 122.

[0115] Figure 3 is a diagram illustrating a process in which the SSP terminal 310 performs switching to an eSIM profile download process during a bundle download process according to an embodiment of the present disclosure.

[0116] Specifically, Figure 3 The case where the SSP terminal 310 requests a telecommunication bundle is specified.

[0117] refer to Figure 3 When the SPB manager 315 may not be able to process the bundle download request of the SSP terminal 310, the SPB manager transmits a family identifier specific error code 320 to the SSP terminal 310, and the SSP terminal 310 may attempt to perform eSIM profile download by using the response of the SPB manager 315.

[0118] In operation 301, the LBA 312 of the SSP terminal 310 may request a bundle download from the SPB manager 315. In operation 301, the method by which the LBA 312 obtains information required to request a bundle download may include a method in which the LBA 312 may: receive the content of the SSP activation code as a user input; scan the SSP activation code in the form of a QR code and receive it as an input; or receive relevant information sent from the service provider through other functions of the LBA 312. In operation 301, when requesting a bundle download, the LBA 312 may provide the SPB manager 315 with information of the SSP 311 and information of the SSP terminal 310.

[0119] The SSP information may include at least one of the following.

[0120] - Main platform information (manufacturer, manufacturer number, serial number, version information)

[0121] -SPB loader information (version information)

[0122] - List of bundles installed in the SSP

[0123] - List of eSIM bundles installed in the SSP

[0124] - List of bundles for a specific family identifier installed in the SSP

[0125] - Metadata list of bundles installed in the SSP

[0126] - Metadata list of eSIM bundles installed in the SSP

[0127] - Metadata list of bundles for a specific family identifier installed in the SSP

[0128] The terminal information may include at least one of the following.

[0129] -LBA version

[0130] - Version of the ETSI SSP TS 103 666-2iSSP standard document for implementing LBA

[0131] -LPA version

[0132] - Version of the GSMA SGP.22 standard document for implementing LPA

[0133] - Is it possible to install an eSIM profile

[0134] -Do you have an eSIM activation code?

[0135] - Is it possible to use a modem?

[0136] The process of performing operation 301 may be an operation before or after the SSP terminal 310 and the SPB manager 315 are mutually authenticated based on the digital certificate during the bundle download process.

[0137] In operation 302 , the SPB manager 315 may determine whether the bundle can be installed in the SSP terminal 310 based on the terminal information and the SSP information transmitted from the SSP terminal 310 through operation 301 .

[0138] In operation 302, the SPB manager 315 may determine as follows.

[0139] - Determines whether to request a bundle of supported family identifiers

[0140] - Based on the SSP information and the terminal information, determine whether the LBA version and loader (SPB loader) version in the SSP are supportable

[0141] - Based on the SSP information, determine whether the bundle held by the SPB manager 315 is compatible with the SSP terminal 310

[0142] Based on the determination, the SPB manager 315 may support the family identifier of the bundle requested by the SSP terminal 310, and when it is determined that the LBA and the version of the loader of the SSP terminal 310 are supportable and the requested bundle is compatible with the SSP terminal 310, the bundle download process may be continued by normally responding to the request of the SSP terminal 310. If it is determined that the bundle download process cannot be continued, the determination may be performed as follows.

[0143] - Based on the SSP information and the terminal information, determine whether the SSP terminal 310 holds the eSIM bundle 314

[0144] Based on the SSP information and the terminal information, determine whether the configuration file held by the SPB manager 315 can be installed in the eSIM bundle 314 of the SSP terminal 310

[0145] - Based on the SSP information and the terminal information, determine whether a specific profile can be installed in the eSIM bundle 314 of the SSP terminal 310

[0146] - Based on the SSP information and the terminal information, determine whether the SPB manager can install the bundle applet in the SSP terminal 310

[0147] When, based on the above determination, the SPB manager 315 determines that there is no bundle that the SSP terminal 310 can install, but the SSP terminal 310 can perform switching to eSIM profile download or applet download, according to operation 303, the SPB manager 315 can transmit a family identifier specific error code 320 to the SSP terminal 310.

[0148] The family identifier specific error code 320 may include at least one of the following information.

[0149] - Family identifier specific error code indicator

[0150] - The family identifier of the bundle

[0151] - "RSP Switch Indicator", indicating that switching to the eSIM profile download process is possible

[0152] - The contents of the eSIM activation code (SM-DP+ address, AC_TOKEN, SM-DP+ OID, etc.), which is the information required to perform the eSIM download

[0153] - An indicator notifying that the bundle download is not possible but the applet corresponding to the bundle can be downloaded

[0154] -Information required to execute the bundled mini-program download (SKMS address, mini-program information)

[0155] According to an embodiment, when the SSP terminal 310 requests a telecommunication bundle, but the SPB manager 315 wants to notify that bundle download is not possible and eSIM profile switching is possible, the SPB manager 315 can send a family identifier-specific error code (which includes a family identifier-specific error code indicator, a family identifier of the bundle, and an RSP switching indicator among multiple pieces of information), and can optionally send an eSIM activation code.

[0156] According to operation 304, based on the family identifier specific error code and error message sent by the SPB manager 315, the LBA 312 of the SSP terminal 310 may be determined as follows.

[0157] -Why the bundle download failed.

[0158] - A family identifier specific error code is transmitted from the SPB manager 315.

[0159] - The eSIM profile download may be attempted by using the family identifier specific error code transmitted by the SPB manager 315 .

[0160] -The bundle applet download may be attempted by using the family identifier specific error code transmitted by the SPB manager 315 .

[0161] - An eSIM profile download may be attempted by receiving as input an eSIM activation code included in an SSP activation code using LBA 312 .

[0162] According to operation 305 , the LBA 312 may prepare to download a configuration file by selecting one of the eSIM bundles 314 installed in the SSP 311 using a function of the LPA 313 .

[0163] When operation 305 has been successfully performed, according to operation 306, LPA 313 may request eSIM profile download from SPB manager 315 or SM-DP+ 316 by using information transmitted by LBA 312. In operation 306, the eSIM profile download protocol may comply with the GSMA SGP.22 standard.

[0164] According to an embodiment, in operation 305, although the error message transmitted from the SPB manager 315 does not include the eSIM activation code information, when Figure 2 As shown in the service subscription process 210 , when a user subscribes to a telecommunication service and then attempts to perform a bundle download by using an SSP activation code including an eSIM activation code, the LBA 312 may attempt an eSIM profile download process by transmitting the eSIM activation code information to the LPA 313 .

[0165] In operation 305, the case where the family identifier of the bundle requested by the SSP terminal 310 in operation 301 is not telecommunication may include the following cases.

[0166] -SM-DP+ 316 may be another server that supports the download of the applet within the bundle requested by the SSP terminal 310 in operation 301 .

[0167] -The host agent requesting the applet download may be another object within LBA 312 instead of LPA 313 .

[0168] In operation 306, the applet download protocol may conform to other standards.

[0169] Figure 4A 4 is a diagram illustrating a flowchart of a process in which the SSP terminal 400 receives a family identifier-specific error code from the SPB manager 404 according to an embodiment of the present disclosure.

[0170] Figure 4A Operations 411 - 414 are part of the process by which the SSP terminal 400 requests the bundle download from the SPB manager 404 .

[0171] refer to Figure 4A In operation 411, LBA 402 of SSP terminal 400 sends a function requesting SSP information for installing a bundle in SSP to SPB loader (SPBL) 401 in SSP. LBA 402 may send a family identifier of a bundle to be installed to SPBL 401. Upon receiving the SSP information request function, SPBL 401 may transmit SSP information to LBA 402 in operation 412.

[0172] In operation 413, LBA 402 may establish a transport layer security (TLS) connection with the server of SPB manager 404 which will request the bundle download.

[0173] In operation 414, LBA 402 may call the SPBM certificate request function from SPB manager 404. When the function is called, LBA 402 may transmit SSP information and terminal information to SPB manager 404. For the transmitted SSP information and terminal information, please refer to Figure 3 Operation 301.

[0174] In operation 415, the SPB manager 404 may determine whether the bundle can be installed in the SSP terminal 400. Regarding the determination performed by the SPB manager 404 in operation 415, reference may be made to the determination performed by the SPB manager 315 in operation 416. Figure 3 The determination performed in operation 302. In addition, in operation 415, SPB manager 404 may perform the following operations.

[0175] - Option to select a family identifier for the bundle.

[0176] - The object identifier of the management agent that can optionally manage the family identifier of the bundle.

[0177] -SPBM key generation certificate (CERT.SPBM.KA) and the certificate chain that verifies it.

[0178] - You can select the CI information of the certificate to be used by the SSP.

[0179] - Information that allows selection of the encryption algorithm to be used by the SSP for data encryption.

[0180] When the SPB manager 404 determines in operation 415 that the bundle can be installed in the SSP terminal 400, the SPB manager may send a response including the following information to the LBA 402 according to operation 416a.

[0181] - Family Identifier

[0182] -SPBM key generation certificate (CERT.SPBM.KA) and the certificate chain that verifies it

[0183] - CI information of the certificate to be used by the SSP

[0184] - Information about the encryption algorithm that will be used by the SSP to encrypt data

[0185] Additionally, in operation 416a, SPB manager 404 may send a response to LBA 402 that optionally includes encryption algorithm information to be used by the SSP.

[0186] When the SPB manager 404 has determined in operation 415 that the bundle may not be installed in the SSP terminal 400, the SPB manager may transmit an error message and a family identifier specific error code to the LBA 402 according to operation 416b. The content of the family identifier specific error code may be the same as Figure 3 The content of the family identifier specific error code 320 is the same as that of the family identifier specific error code 320. Upon receiving the response from the SPB manager 404 according to operation 416a, the LBA 402 may call an SSP credential request function from the SPBL 401. In the SSP credential request function of operation 416a, the LBA 402 may transmit the server credential to the SPBL 401, and the server credential may include at least one of the following.

[0187] - Family Identifier

[0188] -SPBM key generation certificate (CERT.SPBM.KA) and the certificate that verifies it

[0189] - CI information of the certificate to be used by the SSP

[0190] - Information about the encryption algorithm that will be used by the SSP to encrypt data

[0191] -Bundle code matching information (CODE_M)

[0192] The family identifier, the SPBM key generation certificate (CERT.SPBM.KA) and the certificate verifying the certificate, the CI information of the certificate to be used by the SSP, and the information of the encryption algorithm to be used by the SSP for data encryption may be the information that the SPB manager 404 has sent to the LBA 402 as a response in operation 416a.

[0193] Additionally, the server credential may optionally include a bundle code that matches the auxiliary information (challenge_S).

[0194] Upon receiving the SSP credential request function, SPBL 401 may generate SSP credentials based on the received server credentials according to operation 418. The SSP credential generation operation may include the following.

[0195] - Verify the SPBM key generation certificate (CERT.SPBM.KA)

[0196] - Select the certificate to be used for SPBL signing based on the CI information of the certificate to be used by the SSP

[0197] -Generate SPBL temporary key (temporary key pair)

[0198] - Generates ID_TRANSAC which can be used as session ID

[0199] - Generate a first session key (Session Key 1) based on the secret key of the SPBL temporary key (eSK.SPBL.KA) and the public key included in the SPBM key generation certificate

[0200] - Generates an sspImageSessionToken including the SPBL temporary key and generates an sspImageSessionTokenSignature signed by the secret key (SK.SPBL.DS) corresponding to the certificate (CERT.SPBL.DS) used for the SPBL signature on the sspImageSessionToken

[0201] - Generate a second SSP message. The second SSP message may include Figure 3 The SSP information and the main platform identifier mentioned in operation 301.

[0202] - Generate an sspToken including at least one of the bundle code matching information (CODE_M), the bundle code matching auxiliary information (challenge_S), and the generated second SSP information, and generate an sspTokenSignature signed by a secret key corresponding to the certificate (CERT.SPBL.DS) for the SPBL signature on the sspToken

[0203] -Generate the first integrity check information (sspH1) and the first encryption information (sspM1) by encrypting the certificate (CERT.SPBL.DS) used for SPBL signature by the generated first session key. When the first encryption information (sspM1) and the first integrity check information (sspH1) are generated, the generated sspToken and sspTokenSignature may be encrypted together with the certificate (CERT.SPBL.DS) used for SPBL signature.

[0204] - The generated sspToken and sspTokenSignature may be encrypted separately from the certificate used for the SPBL signature to be generated as the second encrypted information (sspM2) and the second integrity check information (sspH2).

[0205] -Generate an SSP credential including at least one of a certificate chain for SPBL signature (CERT.SPBL.DS), a generated sspImageSessionToken, a generated sspImageSessionTokenSignature, a generated sspToken, a generated sspTokenSignature, a generated first encryption information (sspM1), a generated first integrity check information (sspH1), a generated second encryption information (sspM2), and a generated second integrity check information (sspH2).

[0206] In operation 419, the SPBL 401 may send the generated SSP credential to the LBA 402 in response to the SSP credential request function. If an error occurs in any action of operation 418, the SPBL 401 may send an error message in response and complete the process.

[0207] In operation 419, upon receiving the SSP credential transmitted from SPBL 401, LBA 402 may call a bundle / metadata request function from SPB manager 404 according to operation 420. When LBA 402 calls the bundle / metadata request function, LBA 402 may transmit the following information to SPB manager 404.

[0208] - SSP credentials transmitted from SPBL 401

[0209] -Terminal information, including LBA version, LPA version, whether the eSIM profile can be installed, whether the eSIM activation code is available, and whether the modem can be used

[0210] When receiving the SSP credential and the terminal information transmitted from the LBA 402 in operation 420 , the SPB manager 404 may perform at least one of the following operations according to operation 421 based on the transmitted SSP credential and the terminal information.

[0211] - Includes SPB manager 315 in Figure 3 At least one of the decisions made in operation 302

[0212] - Generate the first session key by using the public key of the SPBL temporary key (ePK.SPBL.KA) and eSK.SPBM.KA (i.e. the private key paired with ePK.SPBM.KA, which is the public key of the SPBM key generation certificate)

[0213] - Decrypt the first encrypted message (sspM1) by using the first session key and verifying the sspTokenSignature

[0214] - Verify the certificate used for SPBL signing (CERT.SPBL.DS) and its certificate chain

[0215] - Verify the validity of the contents of sspImageSessionToken and sspImageSessionTokenSignature

[0216] - Verify the validity of the sspToken content and sspTokenSignature

[0217] - Determine if the bundle indicated by CODE_M present in sspToken is held

[0218] - Determine whether the bundle indicated by CODE_M present in sspToken can be installed in the SSP terminal

[0219] - Determine if the primary platform identifier is supported

[0220] In operation 421, when all operations of the SPB manager 404 have been performed without any verification failure, the SPB manager 404 may perform at least one of the following operations.

[0221] - Generate TIME_STAMP and encrypt it with the first session key

[0222] - Prepare metadata (bundle metadata) of the bundle (bundle specified by CODE_M) to be transmitted to the SSP terminal 400

[0223] -Generate SPBM temporary key pair (ePK.SPBM.KA, eSK.SPBM.KA)

[0224] - Generate the second session key by using the SPBM temporary private key (eSK.SPBM.KA) and the ePK.SPBL.KA extracted from the SSP credential

[0225] - Select the SPBM certificate used for signing and prepare a certificate chain that can verify the SPBM certificate used for signing

[0226] - Generates a SpbmToken including the generated SPBM temporary public key (ePK.SPBM.KA) and the ID_TRANSAC included in the received SSP credential

[0227] - Generate SpbmTokenSignature using the generated spbmToken as the secret key corresponding to the SPBM certificate used for signing

[0228] - Encrypt the image descriptor of the bundle to be transmitted by the second session key

[0229] - Encrypt the ARP token using the second session key

[0230] - Encrypting the segment descriptor structure of the bundle to be transmitted by the second session key. The segment descriptor structure may include key information that can decrypt the bundle segment into an installable form.

[0231] -Generate an encrypted bundle. The encrypted bundle may include bundle metadata, the SPBM certificate for signing, the SPBM certificate chain for signing, the generated spbmToken, the generated spbmTokenSignature, the encrypted TIME_STAMP, the ARP token and segment descriptor structure encrypted by the second session key, and the bundle segments to be transmitted to the terminal. The encrypted bundle may include a value indicating the segment descriptor structure and the number of segments.

[0232] According to operation 422a, after generating metadata (bundle metadata) and an encrypted bundle (encrypted secondary platform bundle), the SPB manager 404 may send a response including one of the generated bundle metadata and the generated encrypted bundle to the LBA 402 in response to a bundle / metadata request function.

[0233] In operation 421, when at least one operation of the SPB manager 404 fails to be verified, the SPB manager 404 may determine as follows.

[0234] - Determine the validity of the eSIM bundle installed in the SSP terminal

[0235] - Determine if it is possible to support profiles that can be installed in an eSIM bundle installed in an SSP terminal

[0236] - Determine if the SSP terminal holds the eSIM activation code

[0237] According to operation 422b, the SPB manager 404 may send an error message and a family identifier specific error code as a response to the bundle / metadata request function. The family identifier specific error code may correspond to Figure 3 The family identifier specific error code is 320.

[0238] In operation 421, when it is determined that the SSP terminal 400 does not have the capability to install the eSIM profile or the SPB manager 404 cannot support the eSIM profile of the SSP terminal 400, the SPB manager 404 may send only an error message without a family identifier specific error code as a response.

[0239] According to operations 416b and 422b, upon receiving the family identifier specific error code, LBA 402 may complete the bundle download process and perform the next operation according to the content of the family identifier specific error code. For example, the next operation may be to perform the eSIM profile download process or to perform the bundle applet download process.

[0240] Figure 4B is a diagram showing a flowchart of a process according to an embodiment of the present disclosure, in which the LBA 403 sends a notification message to the SPB manager 404, and in response thereto, when the SSP terminal 400 fails to install an encrypted bundle received from the SPB manager 404, the SSP terminal 400 receives a family identifier-specific error code.

[0241] Operations 420, 421, and 422a may be performed with Figure 4A same.

[0242] refer to Figure 4B Upon receiving the bundle (Binding Bundle) that has been encrypted by operation 422a, LBA 402 may transmit a first bundle installation command parameter, which is a part of the data of the bundle that has been encrypted in operation 423, to SPBL 401. The first bundle installation command parameter may include the following information.

[0243] - The bundle metadata included in the encrypted bundle received from the SPB manager 404 in operation 422a

[0244] - The SPBM certificate for signing and the SPBM certificate chain for signing included in the encrypted bundle received from SPB manager 404 in operation 422a

[0245] - The spbmToken and the spbmTokenSignature that sign the spbmToken included in the encrypted bundle received from the SPB manager 404 in operation 422a. The spbmTokenSignature can be verified by the SPBM certificate used for signing.

[0246] - Encrypted image descriptor and integrity check value

[0247] - Encrypted TIME STAMP and integrity check value

[0248] - Encrypted ARP token and integrity check value

[0249] Encryption algorithm used to encrypt image descriptors, TIME STAMPs, and ARP tokens

[0250] In operation 424, upon receiving the first bundle installation command parameter, SPBL 401 performs a first bundle installation command processing operation. The first bundle installation command parameter processing may include the following operations.

[0251] - Verify the SPB manager's certificate for signing (SPBM certificate for signing) and its certificate chain included in the first bundle installation command parameter. In operation 418, corresponding certificate verification may be performed by using the public key that has been used to verify the SPBM key formation certificate and its certificate chain.

[0252] - Verify the spbmTokenSignature included in the first bundle installation command parameters. The spbmTokenSignature can be verified by the public key of the SPBM certificate used for signing.

[0253] - For the same session, verify that the value of IdTransac in the spbmToken included in the first bundle installation command parameters is the same as the value of ID_TRANSAC generated in operation 418

[0254] - Generate a second session key by using the SPBL temporary private key (eSK.SPBL.KA) generated in operation 418 and the spbmToken included in the first bundle installation command parameter

[0255] - Decrypt the TIME STAMP encrypted by using the first session key generated in operation 418, and identify the integrity through the integrity check value

[0256] - Decrypt the image descriptor and ARP token encrypted by using the second session key and identify the integrity by the integrity check value of each of them

[0257] - Identify the bundle family identifier and bundle identifier in the decrypted image descriptor

[0258] -Store the bundle metadata included in the first bundle installation command parameters. Identify whether the bundle family identifier and bundle identifier in the bundle metadata are the same as the values ​​in the image descriptor

[0259] In operation 425, SPBL 401 may send a first bundle installation command response to LBA 403. When operation 424 has been successfully executed, SPBL 401 may send a message indicating that the first bundle installation command parameter processing has been performed normally to LBA 403 as a first bundle installation command response. When operation 424 has not been successfully executed, SPBL401 may send a message indicating that the first bundle installation command parameter processing has failed to LBA 403 as a first bundle installation command response. The first bundle installation command response may include the reason for the failure of the first bundle installation command parameter processing. The failure of the first bundle installation command parameter processing may occur because the SPBM certificate used for signing is invalid, the bundle identifier is incorrect, the bundle family identifier is incorrect, or the bundle to be installed is incompatible with the SSP.

[0260] In operation 426, upon receiving the first bundle install command response indicating that the first bundle install command process has been successfully executed, LBA 403 may transmit second bundle install command parameters as part of the encrypted bundle data to SPBL 401. The second bundle install command parameters may include the following information.

[0261] - Segment descriptor structure encrypted by the second session key

[0262] In operation 427, upon receiving the second bundle installation command parameter, the SPBL 401 may perform a second bundle installation command processing operation. The second bundle installation command parameter processing may include the following operations.

[0263] - Decrypt the segment descriptor structure encrypted by the second session key of the second bundle installation command by the second session key

[0264] - Get the key information of the decrypted bundle segment from the decrypted segment descriptor structure

[0265] In operation 428, SPBL 401 may send a second bundle installation command response to LBA 403. When operation 427 has been successfully executed, SPBL 401 may send a message indicating that the second bundle installation command parameter processing has been normally executed to LBA 403 as a second bundle installation command response. When operation 427 has not been successfully executed, SPBL 401 may send a message indicating that the second bundle installation command parameter processing has failed to LBA 403 as a second bundle installation command response. The second bundle installation command response may include the reason for the failure of the second bundle installation command parameter processing. The failure of the second bundle installation command parameter processing may occur because the decryption of the encrypted segment descriptor structure failed or the value of the decrypted segment descriptor structure is invalid.

[0266] In operation 429, upon receiving the second bundle install command response indicating that the second bundle install command process has been successfully executed, LBA 403 may transmit a third bundle install command parameter that is part of the encrypted bundle data to SPBL 401. The third bundle install command may include the following information.

[0267] -Bundle segment. The corresponding bundle segment may be decrypted by the key information that the SPBL 401 has acquired from the second bundle installation command parameter processing in operation 427, and thus may be applied to the bundle installation.

[0268] In operation 430, upon receiving the third bundle installation command parameter, SPBL 401 performs a third bundle installation command processing operation. The third bundle installation command parameter processing may include the following operations.

[0269] - decrypting the bundle segment included in the third bundle installation command parameter by using the bundle segment decryption key obtained from the second bundle installation command parameter processing

[0270] - Apply decrypted bundle segments to bundle installation

[0271] In operation 431, SPBL 401 may send a third bundle installation command response to LBA 403. When operation 430 has been successfully executed, SPBL 401 may send a message to LBA 403 indicating that the third bundle installation command parameter processing has been performed normally. When operation 430 has not been successfully executed, SPBL 401 may send a message to LBA 403 indicating that the third bundle installation command parameter processing has failed. The third bundle installation command response may include the reason why the third bundle installation command parameter processing failed. The reason why the third bundle installation command parameter processing failed may be a failure to decrypt a bundle segment, a failure to install a decrypted bundle segment in the SSP, an incompatibility of a decrypted bundle segment with the SSP, an incompatibility of an installed bundle with the SSP, an incompatibility of an installed bundle with the SSP, an incompatibility of an installed bundle with a valid format, or inoperability of an installed bundle.

[0272] LBA 402 and SPBL 401 may repeat operations 428-431 until all bundle segments included in the encrypted bundle received from SPB manager 404 are transferred. The encrypted bundle may include the number of bundle segments to be transferred.

[0273] Upon receiving the first bundle installation command response through operation 425, LBA 402 may transmit a notification message to SPB manager 404 according to operation 432a. According to the first bundle installation command response, the notification message may include the reason why the first bundle installation command parameter processing was successful or the first bundle installation command parameter processing failed. The first bundle installation command parameter processing failure may occur because the SPBM certificate used for signing is invalid, the bundle identifier is incorrect, the bundle family identifier is incorrect, or the bundle to be installed is incompatible with the SSP.

[0274] Upon receiving the second bundle installation command response through operation 428, LBA 402 may transmit a notification message to SPB manager 404 according to operation 432b. According to the second bundle installation command response, the notification message may include the reason for the success of the second bundle installation command parameter processing or the failure of the second bundle installation command parameter processing. The failure of the second bundle installation command parameter processing may occur because the decryption of the encrypted segment descriptor structure fails or the value of the decrypted segment descriptor structure is invalid.

[0275] Upon receiving the third bundle installation command response through operation 431, LBA 402 may transmit a notification message to SPB manager 404 according to operation 432c. According to the third bundle installation command response, the notification message may include the reason why the third bundle installation command parameter processing was successful or the third bundle installation command parameter processing failed, or the fact that all segments of the bundle were installed normally. The reason why the third bundle installation command parameter processing failed may include failure to decrypt a bundle segment, failure to install a decrypted bundle segment in the SSP, incompatibility of the decrypted bundle segment with the SSP, incompatibility of the installed bundle with the SSP, incompatibility of the installed bundle with the SSP, incompatibility of the installed bundle with the valid format, or inoperability of the installed bundle.

[0276] According to operation 433, the SPB manager 404 may process the content of the notification message transmitted by the LBA 402. The notification message transmitted by the LBA 402 may be one of operations 432a, 432b, and 432c. The notification message transmitted by the LBA 402 in operations 432a, 432b, and 432c may include terminal information, including some of the version of the LPA, whether an eSIM profile can be installed, whether an eSIM activation code is held, and whether a modem can be used. The notification message transmitted by the LBA 402 in operations 432a, 432b, and 432c may include information that has been Figure 3 The SSP information and terminal information transmitted in operation 301.

[0277] Based on the content of the notification message that SPB manager 404 has received, SPB manager 404 may determine as follows.

[0278] The bundle is usually installed in the SSP terminal 400 .

[0279] -Bundle installation failed in SSP terminal 400.

[0280] - The SPBL 401 of the SSP terminal 400 determines that the encrypted bundle is invalid.

[0281] - The SPBL 401 of the SSP terminal 400 determines that the encryption bundle is incompatible with the corresponding SSP and host platform.

[0282] - When the bundle to be installed is a telecom bundle and the bundle installation in the SSP terminal 400 fails, determining whether a configuration file can be installed in place of the telecom bundle

[0283] The process of determining whether SPB manager 404 can install a configuration file may include the following.

[0284] - Determine the validity of the eSIM bundle installed in the SSP terminal

[0285] - Determine if it is possible to support a profile that can be installed in an eSIM bundle installed in an SSP terminal

[0286] - Determine if the SSP terminal holds the eSIM activation code

[0287] According to operation 434, the SPB manager 404 may send a notification message response regarding the notification message transmitted from the LBA 402. In operation 434, the notification message response sent by the SPB manager 404 may include a family identifier specific error code. The family identifier specific error code may be associated with Figure 3 Based on the notification message response transmitted by SPB manager 404 in operation 434, LBA 402 may download the configuration file via eSIM Remote SIM Provisioning (RSP). Figure 5B An embodiment of downloading a configuration file to an eSIMRSP after receiving a notification message response is described in detail in FIG.

[0288] Figure 5A is a diagram illustrating the next operation when the LBA 502 of the SSP terminal 500 receives a family identifier specific error code transmitted from the SPB manager 504 during the bundle download process according to an embodiment of the present disclosure.

[0289] Specifically, Figure 5A An example of a situation is shown in which the SSP terminal 500 requests downloading of a telecommunication bundle.

[0290] refer to Figure 5A According to operation 511, LBA 502 may call a bundle download request function from SPB manager 504. The bundle download request function may be Figure 4A The SPBM certificate request function of operation 414 or Figure 4A Operation 420 is one of the bundle / metadata request functions.

[0291] In operation 511, although the SPB manager 504 receives the bundle download request from the LBA 502, the SPB manager may not continue the bundle download process, and in order to enable the SSP terminal 500 to perform the eSIM profile download process, the SPB manager 504 may send an error message and a family identifier-specific error code to the LBA 502 according to operation 512. Specifically, Figure 5A The case in which the SSP terminal 500 requests a telecom bundle is specified, and the family identifier specific error code sent in operation 512 may be referred to as a telecom family specific error code.

[0292] According to operation 513, upon receiving the telecom family specific error code, LBA 502 may complete the bundle download process and select an eSIM bundle capable of downloading the eSIM profile. The operation of selecting an eSIM bundle may include the following.

[0293] -Select the eSIM bundle installed in the SSP

[0294] - When the selected eSIM bundle is in a disabled state, the corresponding eSIM bundle is activated through LBA 502 and loader (SPB loader) 501

[0295] According to operation 514, LBA 502 enables LPA 503 to start the eSIM profile download process, and may transmit eSIM activation code information including SM-DP+ address, AC_TOKEN, SM-DP+OID, etc. according to operation 515. The information sent by LBA 502 to LPA 503 may indicate that LBA 502 has received the content of the eSIM activation code included in the SSP activation code as input, or the telecom family-specific error code that has been transmitted from SPB manager 504 in operation 512. The content of the telecom family-specific error code may include the following.

[0296] - "RSP Switch Indicator", indicating that switching to the eSIM profile download process is possible

[0297] -eSIM activation code information (fully qualified domain name (FQDN) of the SM-DP+ server (the server is used to provide eSIM profiles), AC_Token (MatchingID) that can indicate the eSIM profile to be downloaded, etc.)

[0298] According to an embodiment, when the SPB manager 504 does not directly hold the eSIM activation code information such as SM-DP+ and AC_Token, the SPB manager 504 may transmit a telecom family-specific error code consisting of an RSP switching indicator without including the contents of the eSIM activation code to the LBA 502.

[0299] Telecom family specific error codes may optionally include options defined in GSMA SGP.22, such as the object identifier of SM-DP+.

[0300] After operation 512 is performed, operations 514 and 515 may follow operation 513 .

[0301] After performing operations 513 , 514 , and 515 , according to operation 516 , the eSIM bundle and the LPA 503 may perform a profile download procedure defined in GSMA SGP.22 to download the eSIM profile to the eSIM bundle.

[0302] Figure 5B is a diagram illustrating the next operation when the LBA 502 of the SSP terminal 500 receives a family identifier specific error code transmitted from the SPB manager 504 during the bundle download process according to an embodiment of the present disclosure.

[0303] Specifically, Figure 5B An example of a situation is shown in which the SSP terminal 500 requests downloading of a telecommunication bundle.

[0304] refer to Figure 5B According to operation 511a, LBA 502 may transmit a notification message to SPB manager 504. Operation 511a may be Figure 4B Upon receiving the transmitted notification message, SPB manager 504 may respond to the notification message according to operation 512a. In operation 512a, the notification message response may include an error code specific to the family identifier. Operation 512a may be Figure 4B Operation 433.

[0305] Fig. 6Ais a diagram showing a flowchart of the operation of the SPB manager when the SPB manager receives a bundle download request from an SSP terminal according to an embodiment of the present disclosure, and Figure 6B is a diagram illustrating a flowchart of an operation of the SPB manager when the SPB manager receives a bundle download request from an SSP terminal according to an embodiment of the present disclosure.

[0306] Specifically, Fig. 6A Operations 602, 604, and 605 illustrate the operations performed by SPB manager 404. Figure 4A A specific embodiment of the actions of operation 421.

[0307] refer to Fig. 6A In operation 601, a bundle / metadata request may be received from an SSP terminal. When the bundle / metadata request is received from the SSP terminal, in operation 602, the SPB manager may determine whether the SPB manager holds the bundle requested by the SSP terminal. The process of operation 602 of determining whether the bundle is held may apply the values ​​of CODE_M and Challenge_S among the information that the SSP terminal has provided in operation 601. In addition, in operation 602, the SPB manager may determine whether the bundle requested by the SSP terminal is compatible with the SSP terminal. Information for corresponding determination may apply information of the SSP credential that has been provided by the SSP terminal.

[0308] Upon passing the determination of operation 602, the SPB manager may send a response including the SPBM key generation information and the bundle encrypted by the bundle / metadata request to the SSP terminal according to operation 603. The corresponding response may optionally include bundle metadata. Operation 603 may correspond to Figure 4A Operation 422a.

[0309] When the determination of operation 602 is not satisfied, the SPB manager may determine whether the bundle requested by the SSP terminal is a bundle switchable to eSIM profile download according to operation 604. The determination performed by the SPB manager in operation 604 may consist of some of the following.

[0310] -Whether the bundle requested by the SSP terminal matches a specific eSIM profile

[0311] -Whether the SSP manager has the function of separately providing a configuration file (first configuration file) included in the bundle requested by the SSP terminal

[0312] -Whether the SPB manager holds the activation code information that can download the first configuration file

[0313] - When the bundle installation fails due to the contract with the service provider who provides the bundle, does the SPB manager have a function to separately provide a configuration file to be provided (second configuration file)

[0314] -Whether the SPB manager holds the activation code information that can download the second configuration file

[0315] Upon the determination of operation 604, the SPB manager may determine whether the SSP terminal has the function of downloading the eSIM configuration file according to operation 605. The corresponding determination may include an operation of determining the validity of the eSIM bundle already installed in the SSP terminal based on the terminal information and SSP credentials provided by the SSP terminal.

[0316] Upon passing the determination of operation 605, the SPB manager may send an error message and a family identifier specific error code to the SSP terminal in operation 606. When the family identifier of the bundle requested by the SSP terminal is a telecom family identifier, the family identifier specific error code may be a telecom family specific error code. The contents of the telecom family specific error code may include the following.

[0317] -RSP indicator, indicating that switching to the eSIM profile download process is possible

[0318] - The fully qualified domain name (FQDN) of the SM-DP+ server, which is the server used to provision the eSIM profile

[0319] AC_Token (MatchingID) that indicates the eSIM profile to download

[0320] Telecom family specific error codes may optionally include options defined in GSMA SGP.22, such as the object identifier of SM-DP+.

[0321] According to operation 607, when the SPB manager fails the determination of operations 604 and 605, the SPB manager may send an error message to the SSP terminal as a response.

[0322] The bundle / metadata request received by the SPB manager in operation 601 may correspond to Figure 4A The bundle / metadata request is performed in operation 420 of .

[0323] also, Fig. 6A Operation 601 may correspond to Figure 4A In operation 414 of the present invention, the SPBM certificate request of the SSP terminal is received, and in this case, the actions of operations 602, 604 and 605 may be performed in Figure 4AA specific embodiment of the actions performed by the SPB manager in operation 415 of .

[0324] Figure 6B is a diagram illustrating actions additionally including a process in which an SPB manager determines whether an SSP terminal holds an eSIM activation code according to an embodiment of the present disclosure.

[0325] Figure 6B Operations 611, 612, 613, 614 and 615 may refer to Fig. 6A The actions of operations 601, 602, 603, 604 and 605.

[0326] refer to Figure 6B , when the SPB manager determines in operation 615 that the SSP terminal can download the eSIM configuration file, the SPB manager may determine whether the SSP terminal holds the eSIM activation code according to operation 616. The determination of operation 616 may include a process of identifying whether there is information indicating that the terminal holds the eSIM activation code among the terminal information and the SSP certificate that have been received from the SSP terminal in operation 611. According to operation 617, when it is determined that the SSP terminal holds the eSIM activation code, the SPB manager may send a family identifier specific error code including an RSP switchable indicator as a response.

[0327] When it is determined in operation 616 that the SSP terminal does not hold the eSIM activation code, according to operation 618, it may be determined whether the SPB manager holds the eSIM activation code that can be provided for the SSP terminal. The determination of operation 618 may include a process of determining whether the SPB manager holds the eSIM activation code for the eSIM profile that matches the bundle code matching information (CODE_M) of the bundle that the SSP terminal normally requests. When the SPB manager does not hold the eSIM activation code in operation 618, according to operation 617, the SPB manager may send a family identifier-specific error code including an RSP switchable indicator as a response. When the SPB manager holds the eSIM activation code in operation 618, the SPB manager may send a family identifier-specific error code as a response, wherein the family identifier-specific error code additionally includes the content of the held eSIM activation code.

[0328] Figure 6C is a diagram showing a flowchart of the operation of the SPB manager when a bundle installation failure notification message is received from an SSP terminal according to an embodiment of the present disclosure, and Fig.6D is a diagram illustrating a flowchart of an operation of an SPB manager when a bundle installation failure notification message is received from an SSP terminal according to an embodiment of the present disclosure. Figure 6C It can be in Figure 4BAn embodiment of the actions of processing the notification message performed by the SPB manager in operation 433, and Fig.6D It can be in Figure 4B An embodiment of the actions of processing the notification message performed by the SPB manager in operation 433.

[0329] Figure 6C Operation 601c can be Figure 4B One of operations 432a, 432b, or 432c.

[0330] Figure 6C Operations 604c and 605c can be performed with Fig. 6A Operations 604 and 605 are the same.

[0331] refer to Figure 6C When the SPB manager determines in operation 605c that the SSP terminal can download the eSIM configuration file, according to operation 606c, the SPB manager can transmit a notification message response to the LBA, the notification message response including a family identifier-specific error code, the family identifier-specific error code including information that enables the terminal to download the configuration file. The family identifier-specific error code of operation 606c can be Fig. 6A The family identifier specific error code is the same as described in operation 606 of FIG.

[0332] When it is not determined in operation 604c that the bundle can be switched to profile download, or in operation 605c, it is not determined that the SSP terminal has the function of downloading the eSIM profile, according to operation 607c, the SPB manager may send a notification message response to the LBA. The notification message response may include a confirmation message indicating that the notification message has been received normally.

[0333] Fig.6D Another embodiment is indicated in which when the SPB manager receives a bundle installation failure notification message from the SSP terminal, the SPB manager processes it.

[0334] Fig.6D Operation 601d may be Figure 4B One of operations 432a, 432b, or 432c.

[0335] Fig.6D Operations 614d, 615d, 616d and 618d may refer to Figure 6B Operations 614, 615, 616 and 618.

[0336] refer to Fig.6DWhen the SPB manager already knows the information indicating that the SSP terminal holds the eSIM activation code in operation 616d, or when the SPB manager does not hold the eSIM activation code information to be provided for the SSP terminal in operation 618d, the SPB manager may transmit a notification message response to the LBA according to operation 617d, the notification message response including a family identifier-specific error code with an RSP switchable indicator. The configuration of the family identifier-specific error code with an RSP switchable indicator may refer to Figure 6B Operation 617.

[0337] When the SPB manager holds the eSIM activation code information to be provided for the SSP terminal in operation 618d, the SPB manager may transmit a notification message response to the LBA according to operation 619d, the notification message response including an error code specific to the family identifier of the eSIM activation code. The configuration of the notification message response including the error code specific to the family identifier of the eSIM activation code may refer to Figure 6B Operation 619.

[0338] When it is not determined in operation 614d that the bundle can be switched to profile download, or in operation 615d, it is not determined that the SSP terminal has the function of downloading the eSIM profile, the SPB manager may send a notification message response to the LBA according to operation 620d. The notification message response may include a confirmation message indicating that the notification message has been received normally.

[0339] Fig. 7A is a diagram showing a flowchart of the operation when the LBA of the SSP terminal receives a response to a request that the LBA has sent to the SPB manager during the bundle download process according to an embodiment of the present disclosure, Figure 7BA and Figure 7BB is a diagram showing a flowchart of operations when an LBA of an SSP terminal receives a response to a request that the LBA has sent to an SPB manager during a bundle download process according to various embodiments of the present disclosure, and Figure 7CA and Figure 7CB is a diagram illustrating a flowchart of operations when an LBA of an SSP terminal receives a response to a request that the LBA has sent to an SPB manager during a bundle download process according to various embodiments of the present disclosure.

[0340] Specifically, Fig. 7A Operation 702 shows that when the LBA transmission is already Figure 4A An example of actions when the SPB manager sends a bundle / metadata request performed in operation 420 and receives a response to the bundle / metadata request from the SPB manager.

[0341] refer to Fig. 7A , in execution Figure 4A After operations 411 to 419, Fig. 7A , and the LBA may therefore call a bundle / metadata request function in operation 701. In operation 702, the LBA may receive a response including at least one of an encrypted bundle and bundle metadata from the SPB manager that has received the bundle / metadata request. When the LBA receives a response including at least one of an encrypted bundle and bundle metadata from the SPB manager that has received the bundle / metadata request, the LBA may continue to perform the bundle download process in operation 703. Operation 703 may include the following operations.

[0342] -LBA identification bundle metadata information.

[0343] -When LBA recognizes that the bundle metadata information is normal, the encrypted bundle and the bundle metadata are sent to the SPB loader to install the bundle in the SSP.

[0344] When the LBA does not receive a response to the bundle / metadata request (the response includes at least one of the encrypted bundle and the bundle metadata) in operation 702, in operation 704, it may be identified whether the response is a family identifier-specific error code including the content of the eSIM activation code. The family identifier-specific error code may refer to Figure 3 The description of the family identifier specific error code 320 described in the description. When the LBA receives an error message or unknown information without a family identifier specific error code as a response, the LBA can complete the bundle download process in operation 707.

[0345] When the response is a family identifier-specific error code including the eSIM activation code content, the LBA may perform the following actions in operation 705. Specifically, the following actions describe an embodiment of a case where the family identifier of the bundle is a telecom family identifier.

[0346] -Interpret the content of the family identifier specific error code and extract the content of the eSIM activation code

[0347] -Transmit the information required for the eSIM profile download process to the LPA (contents of the eSIM activation code)

[0348] - Select the eSIM bundle to which the eSIM profile will be downloaded, and when there is no enabled eSIM bundle, select and activate one of the installed eSIM bundles

[0349] After performing operation 705 , in operation 706 , the LBA and the LPA may perform an eSIM profile download procedure defined in GSMA SGP.22 by using the selected eSIM bundle.

[0350] According to an embodiment, Fig. 7A Operation 701 may be Figure 4A In this case, the determination in operation 702 may be made by determining whether the response of the SPB manager corresponds to the SPB manager's Figure 4A When the SPB manager's response to the SPBM certificate request function sent by the LBA according to operation 414 does not correspond to the response sent by the SPB manager in operation 416a, the action of the LBA may be performed according to the flowchart after operation 704. When the LBA receives the response that the SPB manager has sent in operation 416a as the response of the SPB manager to the SPBM certificate request, the LBA performs the next action in operation 417 according to the bundle download process.

[0351] According to an embodiment, Figure 7BA and Figure 7BB 2 is a diagram illustrating a process of performing switching to an eSIM profile download by using corresponding information when a response of an SPB manager includes an eSIM activation code, and performing switching to an eSIM profile download process by using an eSIM activation code held by a terminal when a response of an SPB manager does not include an eSIM activation code.

[0352] Figure 7BA and Figure 7BB The start is to execute in the SSP terminal Figure 4A The time before operation 414. Operation 711 reference Figure 4A Operation 414 of the embodiment. When a response according to operation 416a is received from the SPB manager in operation 712, operation 713 is performed. When a response according to operation 416b is received from the SPB manager in operation 712, operation 716 is performed.

[0353] Operations 713, 714 and 715 can refer to Fig. 7A Description of operations 701, 702 and 703.

[0354] In operation 716, the LBA may determine whether the SPB manager's response is a family identifier specific error code including an RSP switch indicator.

[0355] According to operation 717, when the response of the SPB manager is a family identifier specific error code including an RSP switching indicator, the LBA may determine whether the response includes the content of the eSIM activation code. When the response is a family identifier specific error code including the eSIM activation code, the LBA operates according to operation 718. Operation 718 may refer to Fig. 7A Operation 705.

[0356] When, in operation 716 , the response is not a family identifier specific error code including the RSP switching indicator, and in operation 717 , the response does not include the eSIM activation code, operation 720 may be performed.

[0357] Operation 720 may determine when the LBA is based on Figure 3 Operation 301 determines whether the SSP activation code information that has been applied when the bundle download process is performed at the beginning includes the eSIM activation code. When downloading the bundle, the determination of operation 720 may be a process of determining whether there is information that enables LBA to download the eSIM profile corresponding to the bundle to be downloaded.

[0358] When the LBA holds the eSIM activation code in operation 720 , the LBA transmits the eSIM activation code held by the LBA to the LPA according to operation 721 , and then may select an eSIM bundle that will receive the configuration file.

[0359] Operations 719 and 722 may refer to Fig. 7A Operations 706 and 707.

[0360] According to an embodiment, Figure 7CA and Figure 7CB is a diagram showing a process in which, when a response from an SPB manager includes an eSIM activation code, an LBA additionally determines whether there is an eSIM activation code already held by an SSP terminal, and when the SSP terminal holds the eSIM activation code, the LBA selects one of two pieces of information and attempts to perform eSIM profile download.

[0361] Figure 7CA and Figure 7CB The actions of operations 731, 732, 733, 734 and 735 may correspond to Figure 7BA and Figure 7BB The actions of operations 711, 712, 713, 714 and 715.

[0362] Figure 7CA and Figure 7CB The actions of operations 736, 737, 742 and 743 may correspond to Figure 7BA and Figure 7BB Operations 716, 717, 720 and 721.

[0363] When the LBA receives the family identifier specific error code including the eSIM activation code content as a response according to operation 737, the LBA may determine whether the SSP activation code information includes the eSIM activation code according to operation 738, wherein the SSP activation code information has been applied to the bundle download request. Operation 738 may refer to Figure 7BA and Figure 7BB Operation 720.

[0364] When the LBA holds the eSIM activation code in operation 738, the LBA may select one of the eSIM activation code that the LBA already holds and the eSIM activation code included in the family identifier specific error code received from the SPB manager to transmit the selected code to the LPA according to operation 739, and may select the eSIM bundle that has received the profile. In operation 739, the eSIM activation code that the LBA already holds and the eSIM activation code included in the family identifier specific error code that has been received from the SPB manager may be the same information.

[0365] When there is no eSIM activation code already held by the LBA in operation 738, operation 740 may be performed. The actions of operation 740 may refer to Figure 7BA and Figure 7BB Operation 718.

[0366] Operations 741 and 744 may refer to Fig. 7A Operations 706 and 707.

[0367] Fig. 8A is a diagram showing a flowchart of an operation when an LBA of an SSP terminal receives a response to a notification message that the LBA has sent to an SPB manager during a bundle download process according to an embodiment of the present disclosure, Figure 8B is a diagram showing a flowchart of an operation when an LBA of an SSP terminal receives a response to a notification message that the LBA has sent to an SPB manager during a bundle download process according to an embodiment of the present disclosure, and Figure 8CA and Figure 8CB is a diagram illustrating a flowchart of operations when an LBA of an SSP terminal receives a response to a notification message that the LBA has sent to an SPB manager during a bundle download process according to various embodiments of the present disclosure.

[0368] FIG. 8A to FIG. 8CA and Figure 8CB Operation 801 may be Figure 4B One of operations 432a, 432b, and 432c.

[0369] FIG. 8A to FIG. 8CA and Figure 8CB Operation 802 may be Figure 4B Operation 434.

[0370] Fig. 8A Operations 804, 805, 806 and 807 may refer to Fig. 7A Operations 704, 705, 706 and 707.

[0371] Figure 8B Operations 816, 817, 818, 819, 820, 821 and 822 may refer to Figure 7BA and Figure 7BB Operations 716, 717, 718, 719, 720, 721 and 722.

[0372] Figure 8CA and Figure 8CB Operations 836, 837, 838, 839, 840, 841, 842, 843, and 844 may refer to Figure 7CA and Figure 7CB Operations 736, 737, 738, 739, 740, 741, 742, 743 and 744.

[0373] Fig. 9 is a diagram showing a structure of a terminal according to an embodiment of the present disclosure.

[0374] refer to Fig. 9 , the terminal may include a transceiver 910, a controller 920, and a storage unit 930. In the present disclosure, the controller may be defined as a circuit, an application specific integrated circuit, or at least one processor.

[0375] The transceiver 910 may transmit / receive signals to / from other network entities. For example, the transceiver 910 may receive system information from a base station, and may receive a synchronization signal or a reference signal.

[0376] According to an embodiment suggested in the present disclosure, the controller 920 may control the overall operation of the terminal.

[0377] The storage unit 930 may store at least one of information transmitted / received via the transceiver 910 and information generated by the controller 920 .

[0378] Fig.10 is a diagram showing a structure of a server according to an embodiment of the present disclosure.

[0379] refer to Fig.10 , the server may include a transceiver 1010, a controller 1020, and a storage unit 1030. In the present disclosure, the controller may be defined as a circuit, an application specific integrated circuit, or at least one processor.

[0380] The transceiver 1010 may transmit / receive signals to / from other network entities. For example, the transceiver 1010 may transmit system information to a terminal, and may transmit a synchronization signal or a reference signal.

[0381] According to an embodiment suggested in the present disclosure, the controller 1020 may control the overall operation of the server.

[0382] The storage unit 1030 may store at least one of information transmitted / received via the transceiver 1010 and information generated by the controller 1020 .

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

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

[0385] It should be understood that the various embodiments of the present disclosure and the terms used therein are not intended to limit the technical features set forth herein to specific embodiments, but include various changes, equivalents and / or substitutions of the corresponding embodiments. With respect to the description of the accompanying drawings, similar reference numerals may be used to represent similar or related elements. It should be understood that the singular form of a noun corresponding to an item may include one or more of the things, unless the relevant context clearly indicates otherwise. In the present disclosure, each of the phrases such as "A or B", "at least one of A and / or B", "A, B or C" and "at least one of A, B and / or C" may include all possible combinations of items listed together in the corresponding one in the phrase. As used herein, terms such as "first", "second", "the first" and "the second" may modify the corresponding elements, regardless of order or importance, and may be used to simply distinguish the corresponding elements from other elements, and do not limit the elements. It should be understood that if an element (e.g., a first element) is referred to as "(functionally or communicatively) connected to" or "accessed" other elements (e.g., a second element), this means that the element may be connected to the other elements directly or via another element (e.g., a third element).

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

[0387] Various embodiments of the present disclosure may be implemented as software (e.g., a program), including one or more instructions stored in a machine-readable storage medium (e.g., an internal memory or an external memory) readable by a machine (e.g., a computer). For example, a machine is a device capable of calling at least one of one or more stored instructions from a storage medium and executing according to the called instructions, and may include a terminal according to various embodiments. When a command is executed by a processor, the processor may use or not use one or more other elements under the control of the processor to perform the function corresponding to the command. A command may include a code generated or executed by a compiler or an interpreter.

[0388] The machine-readable storage medium may be provided in the form of a non-transitory storage medium, wherein the term "non-transitory" simply means that the storage medium is a tangible device and does not include signals, but the term does not distinguish between a case where data is semi-permanently stored in the storage medium and a case where data is temporarily stored in the storage medium.

[0389] The methods according to various embodiments of the present disclosure may be included and provided in a computer program product. The computer program product may be traded as a product between a seller and a buyer. The computer program product may be distributed in the form of a machine-readable storage medium (e.g., a compact disc read-only memory (CD-ROM)), or via an application store (e.g., PlayStore). TM ) online distribution. If distributed online, at least a portion of the computer program product may be temporarily generated or at least temporarily stored in a storage medium (such as a manufacturer's server, a server of an application store, or a memory of a relay server). According to various embodiments, each element (e.g., a module or a program) may include a single entity or multiple entities, and one or more of the above-mentioned sub-elements may be omitted, or may be added to various embodiments. Alternatively or additionally, multiple elements (e.g., modules or programs) may be integrated into a single element. In this case, the integrated element may perform one or more functions of each of the multiple elements in the same or similar manner as they were performed by a corresponding one of the multiple elements before integration. According to various embodiments, the operations performed by a module, a program, or another element may be performed sequentially, in parallel, repeatedly, or heuristically, or one or more of the operations may be performed or omitted in a different order, or one or more other operations may be added.

[0390] While the present disclosure has been shown and described with reference to various embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made without departing from the spirit and scope of the present disclosure as defined by the appended claims and their equivalents.

Claims

1. A method performed by a server in a wireless communication system, the method comprising: receiving a first message requesting download of a bundle from a terminal, wherein the first message includes at least one of smart security platform SSP information and terminal information; Determining whether the bundle can be installed in a smart security platform SSP included in the terminal based on at least one of the smart security platform SSP information and the terminal information; If the bundle cannot be installed in the SSP included in the terminal, determining whether to switch from downloading the bundle to downloading an eSIM profile in an embedded subscriber identity module eSIM bundle included in the SSP based on at least one of the smart security platform SSP information and the terminal information; and If it is determined to switch from downloading the bundle to downloading the eSIM profile in the eSIM bundle included in the SSP, a second message including an error code specific to the family identifier is sent to the terminal, wherein the second message further includes an indicator indicating that it is possible to switch to downloading the eSIM profile, Among them, SSP information includes main platform information.

2. The method according to claim 1, wherein: The family identifier specific error code includes information about the configuration file download.

3. The method according to claim 1, wherein: The eSIM bundle is selected among the eSIM bundles installed in the SSP based on the family identifier specific error code.

4. The method according to claim 1, in, The SSP information also includes at least one of supplementary platform bundle SPB loader information, a list of eSIM bundles installed in the SSP, and The terminal information includes information on whether the eSIM configuration file can be installed.

5. A method performed by a terminal in a wireless communication system, the method comprising: Sending a first message to the server requesting download of the bundle package, wherein the first message includes at least one of smart security platform SSP information and terminal information; and receiving a second message from the server, the second message including a family identifier-specific error code if the bundle cannot be installed in a smart security platform SSP included in the terminal, and if it is determined to switch from downloading the bundle to downloading an eSIM profile in an embedded subscriber identity module eSIM bundle included in the SSP based on at least one of smart security platform SSP information and terminal information, wherein the eSIM profile is sent to the terminal, and the second message further includes an indicator indicating that it is possible to switch to downloading of the eSIM profile; and Download the eSIM profile in the eSIM bundle from the server, Wherein, based on at least one of the smart security platform SSP information and the terminal information, whether the bundle can be installed in the SSP included in the terminal is determined, Among them, SSP information includes main platform information. The method of claim 5 , wherein the family identifier-specific error code includes information about configuration file downloading.

7. The method according to claim 5, further comprising: The eSIM bundle is selected among the eSIM bundles installed in the SSP based on the family identifier specific error code.

8. The method according to claim 5, in, The SSP information also includes at least one of supplementary platform bundle SPB loader information, a list of eSIM bundles installed in the SSP, and The terminal information includes information on whether the eSIM configuration file can be installed.

9. A server, comprising: a transceiver configured to transmit or receive at least one signal; and at least one processor operatively coupled to the transceiver, Wherein, the at least one processor is configured as: receiving a first message requesting download of the bundle package from the terminal, wherein the first message includes at least one of smart security platform SSP information and terminal information, determining whether the bundle can be installed in a smart security platform SSP included in the terminal based on at least one of the smart security platform SSP information and the terminal information, If the bundle cannot be installed in the SSP included in the terminal, determining whether to switch from downloading the bundle to downloading an eSIM profile in an embedded subscriber identity module eSIM bundle included in the SSP based on at least one of the smart security platform SSP information and the terminal information, and If it is determined to switch from downloading the bundle to downloading the eSIM profile in the eSIM bundle included in the SSP, a second message including an error code specific to the family identifier is sent to the terminal, wherein the second message further includes an indicator indicating that it is possible to switch to downloading the eSIM profile, Among them, SSP information includes main platform information.

10. The server according to claim 9, wherein: The family identifier specific error code includes information about the configuration file download.

11. The server according to claim 9, wherein: The eSIM bundle is selected among the eSIM bundles installed in the SSP based on the family identifier specific error code.

12. The server according to claim 9, in, The SSP information also includes at least one of supplementary platform bundle SPB loader information, a list of eSIM bundles installed in the SSP, and The terminal information includes information on whether the eSIM configuration file can be installed.

13. A terminal, comprising: a transceiver configured to transmit or receive at least one signal; and at least one processor operatively coupled to the transceiver, Wherein, the at least one processor is configured as: Sending a first message to the server requesting download of the bundle package, wherein the first message includes at least one of smart security platform SSP information and terminal information, receiving a second message from the server, the second message including a family identifier-specific error code if the bundle cannot be installed in a smart security platform SSP included in the terminal, and if it is determined to switch from downloading the bundle to downloading an eSIM profile in an embedded subscriber identity module eSIM bundle included in the SSP based on at least one of smart security platform SSP information and terminal information, wherein the eSIM profile is sent to the terminal, and the second message further includes an indicator indicating that it is possible to switch to downloading the eSIM profile, and Download the eSIM profile in the eSIM bundle from the server, Wherein, based on at least one of the smart security platform SSP information and the terminal information, whether the bundle can be installed in the SSP included in the terminal is determined, Among them, SSP information includes main platform information.

14. The terminal of claim 13, wherein the family identifier-specific error code includes information on downloading of a configuration file.

15. The terminal according to claim 13, wherein: The at least one processor is further configured to select the eSIM bundle among eSIM bundles installed in the SSP based on the family identifier specific error code.

16. The terminal according to claim 13, in, The SSP information also includes at least one of supplementary platform bundle SPB loader information, a list of eSIM bundles installed in the SSP, and The terminal information includes information on whether the eSIM configuration file can be installed.

Images