KR20200130044A - Apparatus and methods for managing and verifying digital certificates - Google Patents

Abstract

According to some embodiments of the present disclosure, a certificate management and verification method by a terminal may comprise the steps of: acquiring certificate information which can be used when downloading and installing a specific bundle corresponding to at least one of a bundle family identifier and a bundle family manager identifier; transmitting, to a bundle management server, the certificate information corresponding to at least one identifier of the specific bundle family identifier and the bundle family manager identifier; and receiving, from the bundle management server, at least one of a certificate of the bundle management server, certificate information to be used by a smart secure platform (SSP), the bundle family identifier, and the bundle family manager identifier.

Description

Certificate management and verification method and device {APPARATUS AND METHODS FOR MANAGING AND VERIFYING DIGITAL CERTIFICATES}

The present disclosure relates to a certificate management and verification method and apparatus, and more specifically, a method and apparatus for selecting a valid certificate and certificate issuer information that can be used when downloading and installing a bundle between a terminal and a server and verifying the validity of the selected certificate It is about.

Efforts are being made to develop an improved 5G communication system or a pre-5G communication system in order to meet the increasing demand for wireless data traffic after the commercialization of 4G communication systems. For this reason, the 5G communication system or the pre-5G communication system is referred to as a communication system after a 4G network (Beyond 4G Network) or a system after an LTE system (Post LTE). In order to achieve a high data rate, the 5G communication system is being considered for implementation in the ultra-high frequency (mmWave) band (for example, the 60 gigabyte (60 GHz) band). In order to mitigate the path loss of radio waves in the ultra-high frequency band and increase the propagation distance of radio waves, in 5G communication systems, beamforming, massive array multiple input/output (MIMO), and full dimensional multiple input/output (FD-MIMO) ), array antenna, analog beam-forming, and large scale antenna technologies are being discussed. In addition, in order to improve the network of the system, in 5G communication system, advanced small cell, advanced small cell, cloud radio access network (cloud RAN), ultra-dense network , Device to Device communication (D2D), wireless backhaul, moving network, cooperative communication, CoMP (Coordinated Multi-Points), and interference cancellation And other technologies are being developed. In addition, in 5G systems, advanced coding modulation (ACM) schemes such as Hybrid FSK and QAM Modulation (FQAM) and SWSC (Sliding Window Superposition Coding), advanced access technologies such as Filter Bank Multi Carrier (FBMC), NOMA (non-orthogonal multiple access), and sparse code multiple access (SCMA) have been developed.

On the other hand, the Internet is evolving from a human-centered network in which humans generate and consume information, to an Internet of Things (IoT) network that exchanges and processes information between distributed components such as objects. Internet of Everything (IoE) technology, which combines IoT technology with big data processing technology through connection with cloud servers, is also emerging. In order to implement IoT, technology elements such as sensing technology, wired/wireless communication and network infrastructure, service interface technology, and security technology are required, and recently, a sensor network for connection between objects, machine to machine , M2M), and MTC (Machine Type Communication) technologies are being studied. In the IoT environment, intelligent IT (Internet Technology) services that create new value in human life by collecting and analyzing data generated from connected objects can be provided. IoT is the field of smart home, smart building, smart city, smart car or connected car, smart grid, healthcare, smart home appliance, advanced medical service, etc. through the convergence and combination of existing IT (information technology) technology and various industries. Can be applied to.

Accordingly, various attempts have been made to apply a 5G communication system to an IoT network. For example, technologies such as sensor network, machine to machine (M2M), and MTC (Machine Type Communication) are implemented by techniques such as beamforming, MIMO, and array antenna. There is. As the big data processing technology described above, a cloud radio access network (cloud RAN) is applied as an example of the convergence of 5G technology and IoT technology.

As described above and with the development of a mobile communication system, various services can be provided, and a method for effectively providing these services is required. More specifically, there is a need for a method and apparatus for selecting a valid certificate and certificate issuer information that can be used when downloading and installing a bundle between a terminal and a server, and verifying the validity of the selected certificate.

The disclosed embodiment may provide an apparatus and method capable of remotely installing a control module in a security module installed in an electronic device and providing security services through security information and the control module stored in the security module.

In addition, the disclosed embodiment may provide an apparatus and method for selecting and verifying a certificate to be used for downloading a bundle divided into a bundle family identifier or a bundle family identifier and a bundle family manager identifier different from each other between a terminal and a bundle management server.

According to some embodiments of the present disclosure, a method of managing and verifying a certificate of a terminal includes obtaining certificate information that can be used when downloading and installing a specific bundle corresponding to at least one of a bundle family identifier and a bundle family manager identifier. ; Transmitting, to a bundle management server, certificate information corresponding to at least one identifier of the specific bundle family identifier and the bundle family manager; And receiving, from the bundle management server, at least one of a certificate of the bundle management server, certificate information to be used by a Smart Secure Platform (SSP), the bundle family identifier, and the bundle family manager identifier.

Further, according to some embodiments of the present disclosure, at least one or more of a certificate of the bundle management server, certificate information to be used by the SSP (Smart Secure Platform), the bundle family identifier, and the bundle family manager identifier is pre-set in the SSP. Verifying based on the established bundle family identifier and certificate information for each bundle family manager identifier; Generating authentication information of the SSP using a bundle identifier and the bundle management server certificate; Transmitting the authentication information of the SSP to the bundle management server; Receiving authentication information of the bundle management server and a bundled bundle from the bundle management server; Verifying authentication information of the bundle management server; Decrypting the bundled bundle based on the verification result and installing the bundle in the SSP; And checking a bundle family identifier of the installed bundle.

In addition, a terminal according to some embodiments of the present disclosure includes: a transceiver; And obtaining certificate information that can be used when downloading and installing a specific bundle corresponding to at least one of the bundle family identifier and the bundle family manager identifier, and at least one of the specific bundle family identifier and the bundle family manager to the bundle management server. Transmitting certificate information corresponding to one or more identifiers, from the bundle management server, at least one of a certificate of the bundle management server, certificate information to be used by a Smart Secure Platform (SSP), the bundle family identifier, and the bundle family manager identifier It may include at least one or more processors that control to receive.

In addition, according to some embodiments of the present disclosure, the at least one processor includes at least one of a certificate of the bundle management server, certificate information to be used by the SSP (Smart Secure Platform), the bundle family identifier, and the bundle family manager identifier. Is verified based on the bundle family identifier and certificate information for each bundle family manager identifier set in the SSP, and using the bundle identifier and the bundle management server certificate, authentication information of the SSP is generated, and authentication of the SSP Send information to the bundle management server, receive authentication information and bundled bundles of the bundle management server from the bundle management server, verify authentication information of the bundle management server, and determine the bundled bundle based on the verification result. It is possible to decrypt and install the bundle in the SSP, and control to check the bundle family identifier of the installed bundle.

The technical problems to be achieved in the present disclosure are not limited to the technical problems mentioned above, and other technical problems that are not mentioned will be clearly understood by those of ordinary skill in the technical field to which the present disclosure belongs from the following description. I will be able to.

According to various embodiments of the present disclosure, a terminal may manage and verify a certificate.

1 is a diagram illustrating a mobile communication network connection method of a terminal using an SSP equipped with a telecom bundle having a profile according to some embodiments of the present disclosure.
2 is a conceptual diagram illustrating an internal structure of a Smart Secure Platform (SSP) according to some embodiments of the present disclosure.
3 is a hierarchy of certificates issued by a certificate issuer (CI) according to some embodiments of the present disclosure (Certificate Hierarchy or Certificate Chain), a public key included in each certificate, and a certificate issuer (Certificate). Issuer, CI) is a diagram showing an example of a configuration of a digital signature.
FIG. 4 is a hierarchy of certificates issued by a certificate issuer (CI) according to some embodiments of the present disclosure (Certificate Hierarchy or Certificate Chain), a public key included in each certificate, and a certificate issuer (Certificate). Issuer, CI) is a diagram showing an example of a configuration of a digital signature.
5 is a diagram illustrating examples of internal and external components of a terminal for downloading and installing a bundle through an SSP by a terminal according to some embodiments of the present disclosure.
6 is a diagram illustrating an example of a procedure in which a subscriber subscribes to a service through a service provider and prepares a bundle download by a service provider and a bundle management server according to some embodiments of the present disclosure.
7A is a diagram illustrating an example of a procedure for negotiating a certificate for selecting a certificate that can be used for mutual authentication and encryption between a terminal and a bundle management server according to some embodiments of the present disclosure.
7B is a diagram illustrating an example of a procedure for negotiating a certificate for selecting a certificate that can be used for mutual authentication and encryption between a terminal and a bundle management server according to some other embodiments of the present disclosure.
FIG. 8 is a diagram illustrating an example of a structure of certificate information generated by an SSP or a Secondary Platform Bundle Loader (SPBL) or transmitted to a bundle management server by a Local Bundle Assistant (LBA) according to some embodiments of the present disclosure.
9 is a diagram illustrating an example of a procedure for generating supportable certificate information set for a specific bundle family identifier and bundle family manager identifier according to a request of an LBA by an SSP of a terminal according to some embodiments of the present disclosure.
10 is a diagram illustrating an example of a procedure for downloading and installing a bundle from a bundle management server by a terminal according to some embodiments of the present disclosure.
11 is a diagram illustrating an example of a procedure for obtaining bundle download information from a bundle management server by a terminal according to some embodiments of the present disclosure.
12 is a diagram illustrating an example of a procedure for verifying a certificate used in a bundle download process by a bundle management server according to some embodiments of the present disclosure.
13 is a diagram illustrating a configuration of a terminal according to some embodiments of the present disclosure.
14 is a diagram illustrating a configuration of a bundle management server according to some embodiments of the present disclosure.

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

In describing embodiments of the present disclosure, descriptions of technical contents that are well known in the technical field to which the present disclosure belongs and are not directly related to the present disclosure will be omitted. This is to more clearly convey the gist of the present disclosure by omitting unnecessary description.

For the same reason, some components in the accompanying drawings are exaggerated, omitted, or schematically illustrated. In addition, the size of each component does not fully reflect the actual size. The same reference numerals are assigned to the same or corresponding components in each drawing.

Advantages and features of the present disclosure, and a method of achieving them will be apparent with reference to embodiments described later in detail together with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below, but may be implemented in a variety of different forms, only the present embodiments are intended to complete the present disclosure, and those of ordinary skill in the art to which the present disclosure pertains. It is provided to fully inform the scope of the disclosure, and the present disclosure is only defined by the scope of the claims. The same reference numerals refer to the same components throughout the specification.

At this time, it will be appreciated that each block of the flowchart diagrams and combinations of the flowchart diagrams may be executed by computer program instructions. Since these computer program instructions can be mounted on the processor of a general purpose computer, special purpose computer or other programmable data processing equipment, the instructions executed by the processor of the computer or other programmable data processing equipment are described in the flowchart block(s). Create a means to perform functions. These computer program instructions can also be stored in computer-usable or computer-readable memory that can be directed to a computer or other programmable data processing equipment to implement a function in a particular way, so that the computer-usable or computer-readable memory It is also possible to produce an article of manufacture containing instruction means for performing the functions described in the flowchart block(s). Computer program instructions can also be mounted on a computer or other programmable data processing equipment, so that a series of operating steps are performed on a computer or other programmable data processing equipment to create a computer-executable process to create a computer or other programmable data processing equipment. It is also possible for instructions to perform processing equipment to provide steps for executing the functions described in the flowchart block(s).

In addition, each block may represent a module, segment, or part of code that contains one or more executable instructions for executing the specified logical function(s). In addition, it should be noted that in some alternative execution examples, functions mentioned in blocks may occur out of order. For example, two blocks shown in succession may in fact be executed substantially simultaneously, or the blocks may sometimes be executed in reverse order depending on the corresponding function.

In this case, the term'~ unit' used in the present embodiment means software or hardware components such as FPGA or ASIC, and'~ unit' performs certain roles. However,'~ part' is not limited to software or hardware. The'~ unit' may be configured to be in an addressable storage medium, or may be configured to reproduce one or more processors. Thus, as an example,'~ unit' refers to components such as software components, object-oriented software components, class components and task components, processes, functions, properties, and procedures. , Subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, database, data structures, tables, arrays, and variables. The components and functions provided in the'~ units' may be combined into a smaller number of elements and'~ units', or may be further divided into additional elements and'~ units'. In addition, components and'~ units' may be implemented to play one or more CPUs in a device or a security multimedia card.

Specific terms used in the following description are provided to aid understanding of the present disclosure, and the use of these specific terms may be changed in other forms without departing from the technical spirit of the present disclosure.

SE (Secure Element) stores security information (e.g., mobile communication network access key, user identification information such as ID card/passport, credit card information, encryption key, etc.), and a control module that uses the stored security information (e.g. For example, it refers to a security module composed of a single chip that can install and operate network access control modules such as USIM, encryption modules, key generation modules, etc.). SE can be used in various electronic devices (e.g., smartphones, tablets, wearable devices, automobiles, IoT devices, etc.), and security services (e.g., mobile communication network access, payment, etc.) through security information and control modules. User authentication, etc.) can be provided.

SE can be divided into UICC (Universal Integrated Circuit Card), eSE (Embedded Secure Element), and SSP (Smart Secure Platform), which is an integrated form of UICC and eSE, and is removable depending on the type of connection or installation to an electronic device. ), fixed type (Embedded), and can be subdivided into integrated type (Integrated) that is integrated into a specific device or SoC (system on chip).

UICC (Universal Integrated Circuit Card) is a smart card inserted into a mobile communication terminal and used, and is also called a UICC card. The UICC may include an access control module for accessing the mobile communication service provider's network. Examples of access control modules include Universal Subscriber Identity Module (USIM), Subscriber Identity Module (SIM), and IP Multimedia Service Identity Module (ISIM). UICC with USIM is also commonly referred to as a USIM card. Similarly, a UICC including a SIM module is commonly referred to as a SIM card. On the other hand, the SIM module may be mounted when manufacturing the UICC or download the SIM module of the mobile communication service to be used at a time desired by the user to the UICC card. The UICC card can also download and install a plurality of SIM modules, and select and use at least one SIM module among them. Such a UICC card may or may not be fixed to the terminal. The UICC fixed to the terminal is called eUICC (embedded UICC), and in particular, a system-on-chip including a communication processor of the terminal, an application processor, or a single processor structure in which the two processors are integrated. The UICC built in (SoC) is sometimes referred to as iUICC (Integrated UICC). Typically, eUICC and iUICC may refer to a UICC card that is fixed to a terminal and used, and which can remotely download and select a SIM module. In the present disclosure, a UICC card capable of remotely downloading and selecting a SIM module is collectively referred to as eUICC or iUICC. That is, among UICC cards that can be selected by downloading a SIM module remotely, a UICC card that is fixed or not fixed to the terminal is collectively used as eUICC or iUICC. In addition, the SIM module information to be downloaded is collectively referred to as eUICC profile or iUICC profile, or more simply as a term of a profile.

eSE (Embedded Secure Element) refers to a fixed type SE that is fixed to an electronic device and used. eSE is usually manufactured exclusively for manufacturers at the request of the terminal manufacturer, and can be manufactured including an operating system and a framework. eSE remotely downloads and installs an applet-type service control module and can be used for various security services such as electronic wallets, ticketing, e-passports, and digital keys. In the present disclosure, the SE in the form of a single chip attached to an electronic device that can remotely download and install a service control module is collectively referred to as eSE.

SSP (Smart Secure Platform) is capable of integrated support for UICC and eSE functions on a single chip, removable (rSSP, Removable SSP), fixed (eSSP, Embedded SSP), and integrated (iSSP, Integrated SSP) built into the SoC. Can be divided into The SSP can be composed of one primary platform (PP) and at least one secondary platform bundle (SPB) operating on the PP, and the primary platform is a hardware platform and a low level operating system (LLOS). ), and the secondary platform bundle may include at least one of a High-level Operating System (HLOS) and an application running on the HLOS. Secondary platform bundles are also referred to as SPBs or bundles. The bundle accesses resources such as the central processing unit and memory of the PP through the Primary Platform Interface (PPI) provided by the PP, and can be run on the PP through this. The bundle can be equipped with communication applications such as SIM (Subscriber Identification Module), USIM (Universal SIM), ISIM (IP Multimedia SIM), and various application applications such as e-wallets, ticketing, e-passports, and digital keys. I can.

The SSP can be used for the above-described UICC or eSE depending on the bundles downloaded and installed remotely, and a plurality of bundles can be installed in a single SSP and operated at the same time to mix the uses of UICC and eSE. That is, when the bundle including the profile operates in the SSP, the SSP can be used for UICC to access the network of the mobile communication service provider. The UICC bundle may be operated by remotely downloading at least one profile, such as eUICC or iUICC, into the bundle and selecting it. In addition, when a bundle including a service control module equipped with an application application capable of providing services such as e-wallet, ticketing, e-passport, or digital key on the SSP operates in the SSP, the SSP can be used for the purpose of eSE. A plurality of service control modules may be installed and operated by being integrated into one bundle, or may be installed and operated as independent bundles.

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

In this disclosure, the SSP is a removable (rSSP, Removable SSP), a fixed type (eSSP, Embedded SSP), and an integrated type built into the SoC (iSSP, Integrated SSP) that can support integrated UICC and eSE functions on a single chip. It is a security module in the form of a chip that can be classified. The SSP can download and install a bundle from an external bundle management server (Secondary Platform Bundle Manager, SPB Manager) using OTA (Over The Air) technology.

In the present disclosure, the method of downloading and installing the bundle using OTA technology in the SSP includes a removable SSP (rSSP) that can be inserted and removed in a terminal, a fixed SSP (eSSP) installed in the terminal, and the SoC installed in the terminal. The same can be applied to the integrated SSP (iSSP).

In the present disclosure, the term UICC may be used interchangeably with SIM, and the term eUICC may be mixed with eSIM.

In the present disclosure, the secondary platform bundle (SPB) is driven by using the resources of the PP on the primary platform (PP) of the SSP.For example, the UICC bundle is an application or file stored in the existing UICC. It may mean that the system, authentication key value, etc., and the operating system (HLOS) in which they operate, are packaged in software form.

In the present disclosure, the USIM Profile may mean the same as a profile or may mean packaging information included in a USIM application in the profile in a software form.

In the present disclosure, the operation of enabling the bundle by the terminal or the external server is to change the state of the corresponding profile to the enabled state, so that the terminal provides a service (for example, a communication service through a communication service provider). , Credit card payment service, user authentication service, etc.). Bundles in the active state may be expressed as "enabled bundles". The bundle in the activated state may be stored in an encrypted state in a storage space inside or outside the SSP.

The bundle activated in the present disclosure is input outside the bundle (for example, user input, push, request of an application in the terminal, authentication request from a carrier, PP management message, etc.) or an operation inside the bundle (for example, timer, polling). ), it can be changed to the driving state (Active). The running bundle is loaded into the driving memory inside the SSP from the storage space inside or outside the SSP, and it can mean processing security information and providing security services to the terminal using the security control unit (Secure CPU) inside the SSP. have.

In the present disclosure, the operation of disabling a bundle by a terminal or an external server may mean an operation of changing the state of the bundle to a disabled state so that the terminal cannot receive the services provided by the bundle. have. The profile in the inactive state may be expressed as "disabled bundle". The bundle in the activated state may be stored in an encrypted state in a storage space inside or outside the SSP.

In the present disclosure, the operation of deleting a bundle by a terminal or an external server is an operation of changing the state of the bundle to a deleted state so that the terminal or the external server can no longer activate or deactivate the bundle. Can mean Bundles in the deleted state may be expressed as "deleted bundles".

In the present disclosure, the bundle management server generates a bundle at the request of a service provider or another bundle management server, encrypts the generated bundle, generates a bundle remote management command, or encrypts the generated bundle remote management command. It can provide a function to do. Bundle management servers that provide the above-described functions are SPB Manager (Secondary Platform Bundle Manager), RBM (Remote Bundle Manager), IDS (Image Delivery Server), SM-DP (Subscription Manager Data Preparation), SM-DP+ (Subscription Manager Data). Preparation plus), Manager Bundle Server, Managing SM-DP+ (Managing Subscription Manager Data Preparation plus), Bundle Encryption Server, Bundle Generation Server, Bundle Provisioner (BP), Bundle Provider, BPC holder (Bundle Provisioning) Credentials holder) can be expressed as at least one of.

In the present disclosure, the bundle management server may download, install, or update a bundle from the SSP, and may play a role of managing key and certificate settings for remotely managing the state of the bundle. Bundle management servers that provide the above-described functions include Secondary Platform Bundle Manager (SPBM), Remote Bundle Manager (RBM), Image Delivery Server (IDS), Subscription Manager Secure Routing (SM-SR), and Subscription Manager Secure Routing (SM-SR+). Plus), an off-card entity of eUICC Profile Manager, PMC holder (Profile Management Credentials holder), and EM (eUICC Manager).

In the present disclosure, the opening intermediary server is SPBM (Secondary Platform Bundle Manager), RBM (Remote Bundle Manager), SPBDS (Secondary Platform Bundle Discovery Sever), BDS (Bundle Discovery Sever), SM-DS (Subscription Manager Discovery Service), DS ( Discovery Service), Root SM-DS, and Alternative SM-DS. The opening brokerage server may receive an event registration request (Register Event Request, Event Register Request) from one or more bundle management servers or an opening brokerage server. In addition, one or more opening brokerage servers may be used in combination. In this case, the first opening brokerage server may receive an event registration request from not only the bundle management server but also the second opening brokerage server. In the present disclosure, the function of the opening brokerage server may be integrated into the bundle management server.

In the present disclosure, the bundle management server may collectively refer to a combination of a function of generating, encrypting, and transmitting a bundle or bundle remote management command, and a function of setting an SSP and managing an installed bundle. In addition, it may be collectively referred to as a combination of the functions of the activation brokerage server. Accordingly, in various embodiments of the present disclosure, operations of the bundle management server and the opening intermediary server may be performed in one bundle management server. In addition, each function may be separately performed by a plurality of separate bundle management servers. In addition, in the specification of the present disclosure, a bundle management server or an opening intermediary server may be expressed as a bundle server. The bundle server may be one of a bundle management server and an opening brokerage server, and may be a device including both a bundle management server and an opening brokerage server.

In this bulletin, the bundle management server and the opening intermediary server may be collectively referred to as SPBM or RBM. Also, the bundle server may be referred to as a bundle management server.

The term'terminal' used in the present disclosure refers to a mobile station (MS), a user equipment (UE), a user terminal (UT), a wireless terminal, an access terminal (AT), a terminal, and a subscriber unit. , A subscriber station (SS), a wireless device, a wireless communication device, a wireless transmit/receive unit (WTRU), a mobile node, a mobile or other terms. Various embodiments of the terminal include a cellular phone, a smart phone having a wireless communication function, a personal portable terminal (PDA) having a wireless communication function, a wireless modem, a portable computer having a wireless communication function, and a digital camera having a wireless communication function. Devices, gaming devices having a wireless communication function, music storage and playback appliances having a wireless communication function, Internet appliances capable of wireless Internet access and browsing, as well as portable units or terminals incorporating combinations of such functions. have. 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, the terminal may also be referred to as an electronic device.

In the present disclosure, an SSP capable of downloading and installing a bundle may be embedded in the electronic device. 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 and connected to the electronic device. For example, the SSP may be inserted into an electronic device in the form of a card. The electronic device may include a terminal, and in this case, the terminal may be a terminal including an SSP capable of downloading and installing a bundle. The SSP can be embedded in the terminal, and when the terminal and the SSP are separated, the SSP can be inserted into the terminal, inserted into the terminal, and connected to the terminal.

In the present disclosure, the terminal or electronic device may include software or applications installed in the terminal or electronic device to control the SSP. The software or application may be referred to as, for example, Local Bundle Assistant (LBA) or Local Bundle Manager (LBM).

In the present disclosure, the bundle identifier is referred to as a factor matching bundle identifier (SPB ID), bundle family identifier (SPB Family ID), bundle family manager identifier (SPB Family Custodian Object ID), bundle matching ID, and event identifier (Event ID). Can be. The bundle identifier (SPB ID) may indicate a unique identifier of each bundle. The bundle family identifier may indicate an identifier that distinguishes the type of a bundle (eg, a telecom bundle for accessing a mobile communication service network). In the present disclosure, the bundle family identifier may be referred to as spbFamilyId. The bundle family manager identifier may indicate an identifier that identifies a subject (eg, a communication service provider, a terminal manufacturer, a specific organization, etc.) managing the bundle family identifier. In the present disclosure, the bundle family manager identifier may be referred to as Oid. The bundle identifier can be used as a value that can index bundles in the bundle management server. In the present disclosure, the SSP identifier (SSP ID) may be a unique identifier of the SSP embedded in the terminal, and may be referred to as sspID. In addition, as in the embodiment of the present disclosure, when the terminal and the SSP chip are not separated, it may be a terminal ID. It may also refer to a specific bundle identifier (SPB ID) in the SSP. In more detail, it may refer to the bundle identifier of a management bundle or loader (SPBL, Secondary Platform Bundle Loader) that installs other bundles in the SSP and manages activation, deactivation, and deletion. The SSP may have a plurality of SSP identifiers, and the plurality of SSP identifiers may be values derived from a single unique SSP identifier.

In the present disclosure, a loader (SPBL, Secondary Platform Bundle Loader) may refer to a management bundle that installs another bundle in the SSP and manages activation, deactivation, and deletion. The LBA of the terminal or the remote server can 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.

In the present disclosure, BPC (Bundle Provisioning Credentials) may be a means used for mutual authentication, bundle encryption, and signature between the bundle management server and the SSP. A BPC may contain one or more of a symmetric key, a Rivest Shamir Adleman (RSA) certificate and private key, an elliptic curved cryptography (ECC) certificate and private key, a root certification authority (CA), and a certificate chain. I can. In addition, when there are multiple bundle management servers, different BPCs for each of the multiple bundle management servers can be stored or used in the SSP.

In the present disclosure, Profile Management Credentials (PMC) may be a means used for mutual authentication between the profile management server and the eUICC, encrypting and signing transmission data. The PMC may contain one or more of a symmetric key, an RSA certificate and private key, an ECC certificate and private key, a root CA, and a certificate chain. In addition, when there are multiple profile management servers, different PMCs for each of the plurality of profile management servers can be stored or used in the eUICC.

In the present disclosure, an event may be a term collectively referring to a bundle download, a remote bundle management, or a management/processing command of other bundles or SSPs. Event (Event) may be named as a remote bundle provisioning operation (Remote Bundle Provisioning Operation, or RBP operation, or RBP Operation) or event record (Event Record), and each event (Event) corresponding to the event identifier (Event Identifier) , Event ID, EventID) or matching identifier (Matching Identifier, Matching ID, MatchingID), and at least one address (FQDN, IP Address, or URL) or each server identifier of the bundle management server or opening brokerage server where the event is stored It may be referred to as containing data. Bundle Download can be mixed with Bundle Installation. In addition, Event Type can be used as a term indicating whether a specific event is a bundle download, remote bundle management (e.g., delete, activate, deactivate, replace, update, etc.), or other bundle or SSP management/handling command. And, it may be named as an operation type (Operation Type or OperationType), an operation classification (Operation Class or OperationClass), an event request type, an event class, an event request class, etc. .

In the present disclosure, a bundle image or image may be mixed with a bundle or may be used as a term indicating a data object of a specific bundle, and may be referred to as a bundle TLV or a bundle image TLV (Bundle Image TLV). . When the bundle image is encrypted using an encryption parameter, it may be referred to as a protected bundle image (PBI) or a protected bundle image TLV (PBI TLV). When the bundle image is encrypted using an encryption parameter that can be decrypted only by a specific SSP, it may be referred to as a bound bundle image (BBI) or a bundled bundle image TLV (BBI TLV). The bundle image TLV may be a data set representing information constituting a profile in a TLV (Tag, Length, Value) format.

In the present disclosure, local bundle management (LBM) is a bundle local management, local management, local management command, local command, local bundle management package It may be called (LBM Package), Bundle Local Management Package, Local Management Package, Local Management Command Package, and Local Command Package. LBM changes the status of a specific bundle (Enabled, Disabled, Deleted) through software installed on the terminal, or the contents of a specific bundle (e.g., bundle nickname, bundle metadata, etc.) ) Can be used for updating. The LBM may include more than one local management command, and in this case, the bundles subject to each local management command may be the same or different for each local management command.

In the present disclosure, remote bundle management (RBM) is a bundle remote management, remote management, remote management command, remote command, and remote bundle management package. It can be named as (RBM Package), Bundle Remote Management Package, Remote Management Package, Remote Management Command Package, and Remote Command Package. RBM changes the state of a specific bundle (Enabled, Disabled, Deleted), or updates the contents of a specific bundle (eg, bundle nickname, bundle metadata, etc.). Can be used for purposes. The RBM may contain more than one remote management command, and the bundles subject to each remote management command may be the same or different for each remote management command.

In the present disclosure, a target bundle may be used as a term referring to a bundle that is a target of a local management command or a remote management command.

In the present disclosure, a certificate or digital certificate is an asymmetric key-based mutual authentication consisting of a pair of a public key (PK) and a secret key (SK). ) May represent a digital certificate used for. Each certificate includes one or more public keys (PK), a public key identifier (PKID) corresponding to each public key, and the identifier of the certificate issuer (CI) that issued the certificate. (Certificate Issuer ID) and digital signature (Digital Signature) may be included. In addition, the certificate issuer may be referred to as a certification issuer, a certificate authority (CA), a certification authority, or the like. In the present disclosure, a public key (PK) and a public key identifier (Public Key ID, PKID) are a specific public key, a certificate including the public key, or a part of a specific public key or a certificate including the public key. A part or a result of an operation of a specific public key (e.g., hash), or an operation result (e.g., hash) of a certificate containing the public key, or a part of a specific public key It has the same meaning as an operation result (eg, hash) value, or an operation result (eg, hash) value of a part of the certificate containing the corresponding public key, or the storage space in which data is stored. Can be used interchangeably.

In this disclosure, certificates (primary certificates) issued by one certificate issuer are used to issue other certificates (secondary certificates), or secondary certificates are used to jointly issue third or more certificates. In this case, the correlation between the corresponding certificates can be named as a certificate chain or certificate hierarchy. In this case, the CI certificate used for issuing the initial certificate is the root of certificate and the highest certificate. , Root CI, Root CI Certificate, Root CA, Root CA Certificate, etc.

In the present disclosure, a service provider may indicate a business entity that issues a request to a bundle management server to request a bundle generation, and provides a service to a terminal through the bundle. For example, it may represent a mobile operator that provides a communication network access service through a bundle equipped with a communication application, and a business support system (BSS), an operational support system, OSS), Point of Sale Terminal, and other IT systems can all be collectively referred to. In addition, in the present disclosure, the service provider is not limited to expressing only one specific business entity, and may be used as a term referring to a group or association or consortium of one or more businesses or an agency representing the group or association. In addition, in this disclosure, a service provider may be named as an operator (Operator or OP or Op.), a bundle owner (BO), an image owner (Image Owner, IO), etc., and each service provider is a name and/or unique At least one or more identifiers (Object Identifier, OID) may be set or assigned. If the service provider refers to a group or association or agency of one or more businesses, the name or unique identifier of any group or association or agency is shared by all businesses belonging to that group or association, or by all businesses working with the agency. It may be a name or a unique identifier.

In the present disclosure, AKA may indicate authentication and key agreement, and may indicate an authentication algorithm for accessing 3GPP and 3GPP2 networks.

In the present disclosure, K (or K value) may be an encryption key value stored in the eUICC used in the AKA authentication algorithm.

In the present disclosure, OPc may be a parameter value that can be stored in eUICC used in the AKA authentication algorithm.

In the present disclosure, the NAA is a network access application, and may be an application program such as USIM or ISIM for accessing a network by being stored in the UICC. NAA may be a network access module.

In the present disclosure, the telecom bundle may be a bundle equipped with at least one NAA or a function to download and install at least one NAA remotely. In the present disclosure, the telecom bundle may include a telecom bundle identifier indicating this.

Further, in describing the present disclosure, when it is determined that a detailed description of a related known function or configuration may unnecessarily obscure the subject matter of the present disclosure, the detailed description thereof will be omitted.

Hereinafter, various embodiments of a method and apparatus for installing and managing a bundle online through a remote server will be described.

1 is a diagram illustrating a mobile communication network connection method of a terminal using an SSP equipped with a telecom bundle having a profile according to some embodiments of the present disclosure.

As shown in FIG. 1, the SSP 120 may be embedded in the SoC 130 of the terminal 110. In this case, the SoC 130 may be a communication processor, an application processor, or a processor in which the two processors are integrated. In addition, the SSP 120 may be a detachable type 122 in the form of an independent chip without being integrated into the SoC, or may be a built-in type 124 previously built into the terminal 110.

A bundle with a profile installed may mean that it contains'access information' that allows access to a specific communication company. For example, the access information may be a K or Ki value required to authenticate to a network together with an International Mobile Subscriber Identity (IMSI) that is a subscriber identifier and a subscriber identifier.

The terminal 110 authenticates with the mobile communication company's authentication processing system (eg, HLR (Home Location Register) or AuC (Authentication Center)) using at least one of the telecom bundles 140 and 150 installed in the SSP 120. Can be done. For example, the authentication process may be an AKA (Authentication and Key Agreement) process. If the authentication is successful, the terminal 110 can use a mobile communication service such as telephone or mobile data using the mobile communication network 160 of the mobile communication system. Each of the two telecom bundles 140 and 150 can store different authentication information, and the terminal 110 can use a mobile communication network by operating the two telecom bundles 140 and 150 simultaneously or in time division according to the setting. .

In addition, the terminal 110 uses the payment bundle 170 installed in the SSP 120 to make online payment or an external credit card through a terminal app.

Offline payment through a PoS (Point of Sale) device can be used, and the identity of the terminal owner can be authenticated using the electronic identification card bundle 180.

2 is a conceptual diagram illustrating an internal structure of a Smart Secure Platform (SSP) according to some embodiments of the present disclosure.

In FIG. 2, the SSP 210 may be composed of one primary platform (PP) 220 and at least one or more secondary platform bundles (SPBs) 230 and 240 operating thereon. . The primary platform 220 may include hardware (not disclosed) and at least one lower level operating system (LLOS) 222. The secondary platform bundle 230 may include a high-level operating system (HLOS) 232 and at least one or more applications 234 operating thereon. Each secondary platform bundle (230, 240) uses a primary platform interface (PPI) 250 to access the central processing unit, memory, etc. of the primary platform 220, and through this, the SSP 210 ) Can be driven.

3 is a hierarchy of certificates issued by a certificate issuer (CI) according to some embodiments of the present disclosure (Certificate Hierarchy or Certificate Chain), a public key included in each certificate, and a certificate issuer (Certificate). Issuer, CI) is a diagram showing an example of the configuration of a digital signature. In the present disclosure, a certificate issuer (CI) may be used interchangeably with a certificate authority (CA).

3, a certificate issuer (CI) generates a public key (313) and a secret key (Secret Key) to be used by the certificate issuer (CI), and among them, a public key (313) is You can create a CI certificate (Certificate Issuer Certificate, CI Certificate, 311) by including it in the certificate and attach a digital signature (Digital Signature, 315) created using your secret key to your certificate. have.

In addition, referring to FIG. 3, the CI certificate 311 may be used to issue 391 the certificate 331 of the object 1. Object 1 may be, for example, a bundle management server (SPBM). Object 1 creates a public key (Public Key, 333) and a secret key (Secret Key) to be used by the object 1, of which the object 1 certificate 331 is created by including the public key (Public Key, 333) in its certificate. can do. Object 1 may request a certificate issuer (CI) to receive a certificate issuer's digital signature (CI Digital Signature, 335) using the certificate issuer's CI Secret Key. At this time, the object 1 certificate 331 is the certificate issuer's identifier 337 corresponding to the certificate issuer's public key (CI Public Key, 313) that should be used when verifying the certificate issuer's digital signature 335 included in the corresponding certificate. ) Can be included. The certificate issuer's identifier 337 may include at least one of a certificate issuer's public key identifier (CI Public Key ID) and a CI identifier (CI ID, CI Object ID, Object Universally Unique Identifier, Object UUID).

Further, referring to FIG. 3, the CI certificate 311 may be used to issue 393 the certificate 351 of the object 2. Object 2 may be, for example, an SSP maker. Object 2 generates a public key (Public Key, 353) and a secret key (Secret Key) to be used by the object 2, of which the object 2 certificate 351 is created by including the public key (Public Key, 353) in its certificate. can do. Object 2 may request a certificate issuer to receive the certificate issuer's digital signature (CI Digital Signature, 355) using the certificate issuer's CI Secret Key. At this time, the object 2 certificate 351 is an identifier of the certificate issuer corresponding to the certificate issuer's public key (CI Public Key, 313) that should be used when verifying the certificate issuer's digital signature 355 included in the certificate. 357). The certificate issuer's identifier 357 may include at least one of a certificate issuer's public key identifier (CI Public Key ID) and a CI identifier (CI ID, CI Object ID, Object Universally Unique Identifier, Object UUID). The certificate issuer signatures 335 and 355 included in the object 1 certificate 331 and the object 2 certificate 351 may have different values, but the public key identifier 357 of the certificate issuer may have the same value.

In addition, referring to FIG. 3, the certificate 351 of object 2 may be used to issue 395 the certificate 371 of object 3. Object 3 may be, for example, an SSP manufactured by an SSP maker or a secondary platform bundle loader (SPBL) mounted inside the SSP. Object 3 generates a public key (Public Key, 373) and a secret key (Secret Key) to be used by itself, of which, the object 3 certificate 351 is included by including the public key (Public Key, 373) in its certificate. Can be generated. Object 3 may request object 2 to receive a digital signature 375 of object 2 by using the secret key of object 2. In this case, the object 3 certificate 271 includes an identifier 377 corresponding to the public key 253 of object 2 to be used when verifying the signature 375 of object 2 included in the certificate. I can. The identifier 377 may include at least one of an issuer's public key ID and an issuer identifier (Object ID, Object Universally Unique Identifier, Object UUID).

In addition, although not shown in FIG. 3, at least one certificate sub-issuer (Sub Certificate Issuer, Sub CI, or Sub Certificate Authority, Sub CA) may exist between the certificate issuer (CI) and Object 1 and Object 2. The sub-issuer certificate may be issued by a certificate issuer (CI) using the CI certificate 311, or another certificate sub-issuer may be issued using his/her sub-issuer certificate. Certificate sub-issuers can issue Object 1 or Object 2 certificates using their sub-issuer certificates.

In addition, although not shown in FIG. 3, at least one certificate sub-issuer (Sub Certificate Issuer, Sub CI, or Sub Certificate Authority, Sub CA) may exist between the object 2 and the object 3. The sub-issuer certificate may be issued by object 2 using the object 2 certificate 351, or another certificate sub-issuer may be issued using his/her sub-issuer certificate. Certificate sub-issuers can issue Object 3 Object 2 certificates using their sub-issuer certificates.

Referring to FIG. 3, the extended setting values 317, 339, 359, or 379 of each of the certificates 311, 331, 351 or 371 are the bundle family identifiers (SPB Family) of bundles that can be downloaded and installed with the corresponding certificate. ID) or a bundle family identifier (SPB Family ID) and a bundle family manager identifier (SPB Family Custodian Object ID).

The object 1 certificate 331, the object 2 certificate 351, and the object 3 certificate 371 shown in the example of FIG. 3 may all have the same CI certificate 311 as the highest certificate or the root of certificate. have. Accordingly, in order for Object 1, Object 2, and Object 3 to authenticate each other, the CI certificate 311 or the CI public key 313 included therein may be required. More specifically, in the example of FIG. 3, in order for object 1 and object 2 to authenticate each other using a digital certificate and signature, object 1 is the signature of object 2 and the object 2 certificate 351 and CI public key 313 Is required, and object 2 may require a signature of object 1, object 1 certificate 331, and CI public key 313. In addition, in the example of FIG. 3, in order for object 1 and object 3 to authenticate each other using a digital certificate and signature, object 1 is the signature of object 3 and the object 3 certificate 371 and object 2 certificate 351 and CI A public key 313 is required, and object 3 may require a signature of object 1, an object 1 certificate 331, and a CI public key 313. In this case, with respect to the object 3 certificate 371, the object 2 certificate 351 may be referred to as a certificate sub-issuer (Sub Certificate Issuer, Sub CI, or Sub Certificate Authority, Sub CA) certificate.

FIG. 4 is a hierarchy of certificates issued by a certificate issuer (CI) according to some embodiments of the present disclosure (Certificate Hierarchy or Certificate Chain), a public key included in each certificate, and a certificate issuer (Certificate). Issuer, CI) is a diagram showing an example of the configuration of a digital signature.

Referring to FIG. 4, a CI certificate 421 or an object 2 certificate 451 may be used to issue (497) and (499) a connection certificate 441. In addition, the CI certificate 421 and the object 2 certificate 451, and sub-issuer certificates (not shown) that may exist between the object 2 certificate 451 and the object 3 certificate 471 are the connection certificate 441 Can be used to issue. The connection certificate 441 may receive a digital signature 445 using the issuer's secret key. In this case, the connection certificate 441 may include an identifier 447 corresponding to the issuer's public key that should be used when verifying the signature 445 included in the corresponding certificate. The identifier 447 may include at least one of an issuer's public key ID and an issuer identifier (Object ID, Object Universally Unique Identifier, Object UUID). The public key 443 of the connection certificate 441 is a value corresponding to the issuer identifier 447 of the object 1 certificate 431, or a sub-issuer certificate that may exist between the CI certificate 411 and the object 1 certificate 431 It may be a value corresponding to the issuer identifiers of (not shown). The extended setting value 449 of the connection certificate 441 is the bundle family identifier (SPB Family ID) or the bundle family identifier (SPB Family ID) of the bundle authorized by the issuer so that Object 1 can download to Object 3 with the corresponding certificate. It may include a bundle family manager identifier (SPB Family Custodian Object ID).

Referring to FIG. 4, the extended setting value (417, 427, 439, 449, 459 or 479) of each of the certificates (411, 421, 431, 441, 451 or 471) is a bundle that can be downloaded and installed with the corresponding certificate. Bundle family identifier (SPB Family ID) or bundle family identifier (SPB Family ID) and bundle family manager identifier (SPB Family Custodian Object ID) may be included.

In addition, although not shown in FIG. 4, at least one certificate sub-issuer (Sub Certificate Issuer, Sub CI, or Sub Certificate Authority, Sub CA) may exist between the certificate issuer (CI) and Object 1 and Object 2. The sub-issuer certificate may be issued by a certificate issuer (CI) using the CI certificate 311, or another certificate sub-issuer may be issued using his/her sub-issuer certificate. Certificate sub-issuers can issue Object 1 or Object 2 certificates using their sub-issuer certificates. The extended setting value of the sub-issuer certificate includes the bundle family identifier (SPB Family ID) or the bundle family identifier (SPB Family ID) and the bundle family manager identifier (SPB Family Custodian Object ID) of the bundle that can be downloaded and installed with the corresponding certificate. can do.

In addition, although not illustrated in FIG. 4, at least one certificate sub-issuer (Sub Certificate Issuer, Sub CI, or Sub Certificate Authority, Sub CA) may exist between the object 2 and the object 3. The sub-issuer certificate may be issued by object 2 using the object 2 certificate 351, or another certificate sub-issuer may be issued using his/her sub-issuer certificate. Certificate sub-issuers can issue Object 3 Object 2 certificates using their sub-issuer certificates.

Referring to FIG. 4, the illustrated object 1 certificate 431 and object 2 certificate 451 may each have different CI certificates 411 and 421 as the highest certificate or root of certificate. Accordingly, the CI certificate 411 and the CI public key 413 included therein may be required for the object 2 and the object 3 to authenticate the object 1. In addition, the CI certificate 421 and the CI public key 423 included therein may be required for the object 1 to authenticate the object 2 and the object 3. More specifically, in the example of FIG. 4, in order for object 1 and object 2 to authenticate each other using a digital certificate and signature, object 1 is the signature of object 2 and the object 2 certificate 451 and CI public key 423 Is required, and object 2 may require a signature of object 1, object 1 certificate 431 and CI public key 413. In addition, in the example of FIG. 3, in order for object 1 and object 3 to authenticate each other using a digital certificate and signature, object 1 is used to sign object 3, object 3 certificate 471, object 2 certificate 451, and CI. A public key 423 is required, and object 3 may require a signature of object 1, an object 1 certificate 431, and a CI public key 413.

Referring to FIG. 4, in order for object 3 to authenticate object 1, a connection certificate 441 and a CI certificate 421 and or a public key 423 included therein may be required. More specifically, in the example of FIG. 4, in order for object 3 to authenticate object 1 using the digital certificate and signature of object 1, object 3 is the signature of object 1, object 1 certificate 431 and connection certificate 441 And the CI public key 423 may be required. In addition, the connection certificate 441, the object 2 certificate 451, and the CI certificate 421 and the public key 423 included therein may be required for the object 3 to authenticate the object 1. More specifically, in the example of FIG. 4, in order for object 3 to authenticate object 1 using the digital certificate and signature of object 1, object 3 is the signature of object 1, object 1 certificate 431, connection certificate 441, The object 2 certificate 451 and the CI public key 423 may be required.

5 is a diagram illustrating examples of internal and external components of a terminal for downloading and installing a bundle to an SSP by a terminal according to some embodiments of the present disclosure.

In FIG. 5, the terminal 510 may be a terminal equipped with an SSP 530 and an LBA 512 for controlling the SSP 530. The SSP 530 may be embedded in the terminal 510 or may be detachable. The SSP 530 may include a primary platform 531, a secondary platform bundle loader (SPBL) 533, and one or more secondary platform bundles 535, 537, or 539. In addition, the secondary platform bundle 535, 537, or 539 is not installed inside the SSP 530 at the time of terminal shipment, but may be downloaded and installed remotely after shipment.

Further, referring to FIG. 5, each bundle may have a different bundle family identifier or bundle family identifier and bundle family manager identifier 541 or 542. The SSP 530 or SPBL 533 may store and manage a certificate setting 551 that is allowed to be used to download and install a bundle having different bundle family identifiers or bundle family identifiers and bundle family manager identifiers. The LBA 512 may request the certificate setting 551 from the SSP 530 or the SPBL 533, and the certificate setting may be duplicated and stored in the LBA 512.

Referring to FIG. 5, the SSP 530 or the SPBL 533 may store and manage certificate information 552, 553, or 554 to which different family identifiers and different bundle family manager identifiers are assigned. The certificate information 552, 553, or 554 to which the family identifier and the bundle family manager identifier are assigned may be used to download a bundle including the assigned family identifier and the bundle family identifier. The SSP 530 or the SPBL 533 may refuse to download and install a bundle that does not include the family identifier and the bundle family identifier assigned to the corresponding certificate information 552, 553, or 554.

Referring to FIG. 5, different bundle family identifiers are assigned to the SSP 530 or SPBL 533, and certificate information 555 or 556 to which the bundle family manager identifier is not assigned may be stored and managed. The certificate information 555 or 556 to which the family identifier is assigned may be used to download a bundle including the assigned family identifier.

Referring to FIG. 5, the SSP 530 or the SPBL 533 may store and manage the bundle family identifier and certificate information 557 to which the bundle family manager identifier is not assigned.

In FIG. 5, the certificate information 552, 553, 554, 555, 556, 557 stored and managed by the SSP 530 or the SPBL 533 is a CI certificate or a public key identifier of a CI certificate in FIGS. It may be a certificate existing on the certificate hierarchy issued by a certificate issuer (CI) or a public key identifier of the corresponding certificate. When downloading and installing a bundle from the bundle management server 551 or 553, the SSP 430 or SPBL 433 is the bundle family identifier assigned to the bundle or the bundle family identifier and the certificate information set in the bundle family manager identifier. Select and transmit the information to the bundle management server (551 or 553). The certificate information may be the certificate or public key of the certificate issuer (CI) of the certificate hierarchy, and the identifier corresponding to the certificate and public key (e.g., CI ID, CI ID, CI Object ID, Object Universally Unique Identifier, Object UUID, CI Public Key ID).

6 is a diagram illustrating an example of a procedure in which a subscriber subscribes to a service through a service provider and prepares a bundle download by a service provider and a bundle management server according to some embodiments of the present disclosure.

In FIG. 6, the terminal 600 may be a terminal equipped with an SSP 610 and an LBA 620 for controlling the SSP 610. In addition, although not shown in the drawing, a bundle requested by the service provider 640 may be generated and waiting in the bundle management server 650, and the service provider 640 may be configured with a bundle identifier (SPB ID) and a bundle family of the generated bundle. It may have at least one of an identifier (SPB Family ID), a bundle family manager identifier (SPB Family Custodian Object ID), and an address of the bundle management server 650 (SPBM Addr).

Referring to FIG. 6, a subscriber 630 may select and subscribe to a service (eg, a data service through a mobile communication network) provided by the service provider 640 in step 6001. At this time, the subscriber 630 can selectively transmit the identifier (SSP ID) of the SSP 610 installed in the terminal 600 to install the bundle to the service provider 640 in order to use the service provided by the service provider 640. have.

In step 6003, the service provider 640 and the bundle providing server 650 may perform a bundle download preparation procedure. In step 6003, the service provider 640 may selectively transmit the identifier (SSP ID) of the SSP 610 to which the bundle is to be installed to the bundle management server 650, and provide a service selected by the subscriber among the bundles prepared in the server. At least one of a specific bundle identifier (SPB ID), a bundle family identifier (SPB Family ID), and a bundle family manager identifier (SPB Family Custodian Object ID) may be transmitted to the bundle management server 650. In step 6003, the bundle management server 650 may select one of a bundle having a specific bundle identifier, a bundle having a bundle family identifier, a bundle having a bundle family identifier and a bundle family manager identifier, and service the selected bundle identifier. It can be delivered to the provider 640. The service provider 640 or the bundle providing server 650 may newly generate a bundle matching ID capable of distinguishing the selected bundle. In addition, the bundle providing server 650 may connect and manage the transmitted SSP identifier (SSP ID) and the selected bundle. In step 6003, the bundle management server 650 may deliver a bundle management server address (SPBM Addr) capable of downloading the selected bundle. In this case, the bundle management server address may be the address of itself or another bundle management server in which the prepared bundle is stored, and may be an address of another bundle management server capable of storing and obtaining download information (server address, etc.) of the prepared bundle.

Referring to FIG. 6, in step 6005, the service provider 640 may transmit prepared bundle download information to the subscriber 630. Bundle download information optionally selects at least one of the bundle management server address (SPBM Addr) where the bundle is prepared, the bundle matching ID of the prepared bundle, the bundle family identifier (SPB Family ID) of the prepared bundle, and the bundle family manager identifier (SPB Family Custodian ID). Can be delivered.

Referring to FIG. 6, bundle download information may be transmitted to the LBA 620 of the terminal 600 in step 6006. The bundle download information includes the address of the bundle management server to which the LBA 620 will access (SPBM Addr), the bundle identifier of the bundle prepared in step 6003, the bundle family identifier of the prepared bundle (SPBM Family ID), and the bundle family manager identifier (SPB Family Custodian). Object ID) may be at least one. The bundle identifier may include at least one of a bundle matching ID or a bundle event ID generated in step 6003. In addition, the bundle identifier may include at least one of a bundle family identifier and a bundle family manager identifier (SPB Family Custodian Object ID) of the prepared bundle. The bundle Event ID may include at least one of a bundle matching ID of a bundle prepared in step 6003 and an address of a bundle management server. Bundle download information is input by the subscriber 630 to the LBA 620 (for example, QR code scanning, direct text input, etc.), or by using a push input through an information providing server (not shown), the LBA 620 Can be entered in In addition, the LBA 620 may access the information providing server (not shown) set in the terminal 600 in advance to receive bundle download information.

7A is a diagram illustrating an example of a procedure for negotiating a certificate for selecting a certificate that can be used for mutual authentication and encryption between a terminal and a bundle management server according to some embodiments of the present disclosure.

Referring to FIG. 7A, in step 7001, the LBA 720 may request certificate information set in the SSP 710. In step 7001, the LBA 720 may optionally include a bundle family identifier, and may optionally include a bundle family manager identifier to request certificate information set in the SSP 710.

In step 7001, the LBA 720 may request the SSP 710 for certificate information that the SSP 710 can use to download and install a bundle having a specific bundle family identifier and a specific bundle family manager identifier. In step 7001, the LBA 720 may request certificate information from the SSP 710 including a specific bundle family identifier and a specific bundle family manager identifier. In addition, in step 7001, the LBA 720 may request the SSP 710 for certificate information that the SSP 710 can use to download and install a bundle having a specific bundle family identifier. In step 7001, the LBA 720 may request certificate information from the SSP 710 including a specific bundle family identifier. In addition, in step 7001, the LBA 720 may request the SSP 710 for certificate information that the SSP 710 can use to download and install the bundle without the bundle family identifier and the bundle family manager identifier.

Referring to FIG. 7, the SSP 710 includes certificate information (SpbmVerification) and bundle management server that the SSP 710 can use to verify the bundle management server for each bundle family identifier and bundle family manager identifier (7101 and 7102). Certificate information (SpblVerification) that can be used to verify the SSP may be set. In addition, a bundle family identifier is assigned to the SSP 710, and certificate information 7200 to which the bundle family manager identifier is not assigned may be set. In addition, certificate information 7300 to which a bundle family identifier and a bundle family manager identifier are not assigned may be set in the SSP 710.

Certificate information (SpbmVerification) that the SSP can use to verify the bundle management server means certificate information that the SSP 710 can use to verify the validity of the certificate, certificate chain and signature presented by the bundle management server 750 can do. Certificate information (SpblVerification) that the bundle management server can use to verify the SSP is used by the bundle management server 750 to verify the validity of the certificate issued to the SSP 710, the chain of the corresponding certificate, and the signature generated by the SSP. It can mean certificate information that can be used.

Referring to FIG. 7A, in step 7002, the SSP 710 extracts the bundle family identifier provided by the LBA 720 and the certificate information set in the bundle family manager identifier to generate SSP certificate information (sspCiInfo), and step 7003 At, SSP certificate information (sspCiInfo) may be delivered to the LBA 720. The SSP certificate information (sspCiInfo) includes certificate information (SpbmVerification) that the SSP set in the bundle family identifier, the bundle family manager identifier, the corresponding bundle family identifier, and the bundle family manager identifier can use to verify the bundle management server and the bundle management server is SSP. Certificate information (SpblVerification) that can be used to verify the data may be included. In addition, in step 7001, when the bundle family identifier and the bundle family manager identifier are not transmitted from the LBA 720 to the SSP 710, SSP certificate information (sspCiInfo) including all certificate information may be generated.

In addition, although not shown in FIG. 7A, in step 7003, the SSP 710 stores SSP version information including at least one of version information of a primary platform included in the SSP 710 and version information of a standard standard supported by the loader. ).

In addition, in step 7003, the SSP 710 may transmit an identifier (eg, Part Number (PN)) indicating design and setting information of the SSP 710 to the LBA 720.

In addition, although not shown in FIG. 7A, in step 7003, the LBA 720 includes a specific bundle manager identifier or bundle family identifier and bundle family manager identifier based on the certificate information received from the SSP 710 or the previously stored certificate setting information of the SSP. SSP certificate information (SspCiInfo) can be generated by extracting the certificate information of the SSP allocated to

In addition, after completing step 7002 in FIG. 7A and before step 7003, the SSP 710 may inform the LBA 720 that step 7002 is completed. In addition, after receiving that step 7002 is completed, the LBA 720 may request the SSP 710 to deliver the information generated in step 7002 before step 7003.

Referring to FIG. 7A, in step 7004, the LBA 720 and the bundle management server 750 may perform TLS (Transport Layer Security) connection. The TLS connection in step 7004 may use a server authentication method in which the LBA 720 verifies the identity of the bundle management server 750 among TLS connection methods. When the LBA 720 verifies the identity of the bundle management server 750 upon TLS connection in step 7004, the bundle management server 750 may submit a TLS certificate to the LBA 720. At least one CI certificate or public key for validating the TLS certificate may be stored in the LBA 720 to the terminal 700. When one or more Sub CI certificates are required to validate the TLS certificate of the bundle management server 750, the bundle management server 750 may submit one or more Sub CI certificates together with the TLS certificate to the LBA 720 in step 7004. have. After the TLS connection is established, all messages between the LBA 720 and the bundle management server 750 may be protected by the TLS security procedure.

In step 7005, the LBA 720 may request the bundle management server 750 to start certificate negotiation. In step 7005, the LBA 720 may transmit certificate information supported by the SSP 720 to the bundle management server 750 based on the SSP certificate information (sspCiInfo) of the SSP 720 checked in step 7003. In addition, although not shown in FIG. 7A, in step 7005, the LBA 720 may additionally transmit SSP version information to the bundle management server 750. In addition, although not shown in FIG. 7A, in step 7005, the LBA 720 may additionally transmit the design and setting information identifier (eg, Part Number (PN)) of the SSP 710 to the bundle management server 750. have.

Although not shown in FIG. 7A, the bundle management server 750 includes information (SpbmVerification) and bundle management on the CI certificate or certificate sub-issuer certificates used to issue a certificate to the bundle management server for each bundle family identifier and bundle family manager identifier. Certificate information (SpblVerification) of the SSP certificate issuance CI or certificate sub-issuances that the server trusts may be set. The bundle management server 750 transfers the corresponding certificate to the SSP 710 and the LBA 720 for mutual authentication in the information (SpbmVerification) of one CI certificate or certificate sub-issuer certificates used to issue a certificate to the bundle management server. Can provide.

In addition, the certificate information (SpblVerification) of the SSP certificate issuance CI or certificate sub-issuances trusted by the bundle management server 750 means certificate information that enables the bundle management server 750 to verify the validity of the certificate provided by the SSP. It may mean that the SSP certificate present in the corresponding certificate hierarchy can be verified when it is transmitted to the bundle management server 750 through the LBA 720 for mutual authentication between the SSP and the bundle management server. In this case, the certificate information may include at least one of a public key ID of a certificate issuer and a certificate identifier (Certificate ID, Object ID, Object Universally Unique Identifier, Object UUID).

In step 7006, the bundle management server 750 performs a comparison with the certificate information set in the bundle management server 750 and the certificate information of the SSP based on the SSP certificate information (sspCiInfo) of the SSP 710 transmitted in step 7005, and , The selected bundle family identifier, the bundle family manager identifier, the bundle management server 750 certificate to be transmitted to the terminal 700, and certificate information (sspCiToBeUsed) to be used by the SSP may be selected.

At this time, the bundle management server 750 certificate to be delivered to the terminal 700 may be a certificate for a key agreement (CERT.SPBM.KA) or a certificate for a digital signature (CERT.SPBM.DS). In addition, the bundle management server 750 certificate to be delivered to the terminal 700 is provided to the bundle management server and certificate information (SpbmVerification) that the SSP transmitted to the bundle management server 750 in step 7005 can use to verify the bundle management server. It may be a bundle management server certificate that exists in at least one certificate hierarchy among common information (SpbmVerification) of the CI certificate used to issue the certificate or the information on the certificate sub-issuer certificates (SpbmVerification).

The certificate information (sspCiToBeUsed) to be used by the SSP is the certificate information (SpblVerification) that the bundle management server delivered to the bundle management server 750 can use to verify the SSP in step 7005 and the SSP certificate issuance CI that the bundle management server trusts. It may include at least one of common certificate information of certificate information (SpblVerification) of certificate sub-issuers.

In step 7007, the bundle management server 750 may return the bundle management server certificate and certificate information selected in step 7006 to the LBA 720. The information returned to the LBA 720 in step 7007 may include at least one of a bundle management server certificate that the SSP 710 selected in step 7006 can verify, certificate information to be used by the SSP, a bundle family identifier, and a bundle family manager identifier. . In addition, when one or more Sub CI certificates are required to determine whether the bundle management server certificate is valid, the information returned to the LBA 720 may include one or more Sub CI certificates together with the bundle management server certificate.

In addition, the information returned to the LBA 720 in step 7007 may include a server challenge (spbmChallange) that can be selectively used by the SSP and the bundle management server for mutual authentication after step 7007. In addition, the information returned to the LBA 720 in step 7007 may optionally include a digital signature of the delivered bundle management server to ensure the integrity of the returned information. In this case, it is necessary to determine whether the digital signature is valid. Bundle management server certificate (CERT.SPBM.DS) for signing can be included together. In this case, the signing bundle management server certificate (CERT.SPBM.DS) may be a certificate that exists in the same CI hierarchy as the certificate selected in step 7006. In addition, when one or more Sub CI certificates are required to determine whether the bundle management server certificate is valid, the information returned to the LBA 720 may include one or more Sub CI certificates together with the bundle management server certificate.

7B is a diagram illustrating an example of a procedure for negotiating a certificate for selecting a certificate that can be used for mutual authentication and encryption between a terminal and a bundle management server according to some other embodiments of the present disclosure.

Referring to FIG. 7B, in step 15101, the LBA 15020 may request the SSP 15010 to request a design and configuration information identifier (eg, Part Number (PN)) of the SSP 15010.

Referring to FIG. 7B, in step 15102, the SSP 15010 extracts an identifier indicating design and configuration information, and in step 15103, the SSP 15020 may transmit the corresponding information to the LBA 15020. In addition, although not shown in FIG. 7B, in step 15102, the SSP 15010 includes SSP version information including at least one of version information of the standard standard supported by the primary platform and the loader included in the SSP 15010. ).

Referring to FIG. 7B, in step 15104, the LBA 15020 and the bundle management server 15050 may perform TLS (Transport Layer Security) connection. The TLS connection in step 15104 may use a server authentication method in which the LBA 15020 checks the identity of the bundle management server 15050 among TLS connection methods. Upon TLS connection in step 15104, when the LBA 15020 checks the identity of the bundle management server 15050, the bundle management server 15050 may submit a TLS certificate to the LBA 15020. At least one CI certificate or public key for validating the TLS certificate may be stored in the LBA 15020 to the terminal 15000. When one or more Sub CI certificates are required to validate the TLS certificate of the bundle management server 15050, the bundle management server 15050 may submit one or more Sub CI certificates together with the TLS certificate to the LBA 15020 in step 15104. have. After the TLS connection is established, all messages between the LBA 15020 and the bundle management server 15050 may be protected by the TLS security procedure.

In step 15105, the LBA 15020 may request the bundle management server 15050 to start certificate negotiation. In step 15105, the LBA 15020 transmits at least one of the design and setting information identifier (for example, Part Number (PN)) of the SSP 15010 checked in step 15103, the bundle family identifier, and the bundle family manager identifier, to the bundle management server 15050. ). In step 15105, the LBA 15020 may additionally transmit SSP version information to the bundle management server 15050.

In step 15106, the bundle management server 15050 uses the design and configuration information identifier of the SSP 15010 transmitted in step 15105 to transfer the certificate setting information of the SSP 15010 to the bundle management server 15050 itself or a third party. It can be obtained from storage (not shown). In this case, the bundle management server 15050 may acquire a corresponding bundle family identifier of the SSP 15010 and certificate information of the SSP allocated to the bundle family manager identifier by additionally using the bundle family identifier and the bundle family manager identifier. The bundle management server 15050 compares the certificate information set in the bundle management server 15050 with the certificate information of the SSP, and transmits the selected bundle family identifier, the bundle family manager identifier, and the terminal 15010 to the bundle management server 15050 You can select a certificate, certificate information to be used by SSP (sspCiToBeUsed), etc.

In step 15107, the bundle management server 15050 may return the bundle management server certificate and certificate information selected in step 15106 to the LBA 15020. The information returned to the LBA 15020 in step 15107 may include at least one of a bundle management server certificate that the SSP 15010 selected in step 15106 can verify, certificate information to be used by the SSP, a bundle family identifier, and a bundle family manager identifier. . In addition, when one or more Sub CI certificates are required to determine whether the bundle management server certificate is valid, the information returned to the LBA 15020 may include one or more Sub CI certificates together with the bundle management server certificate.

In addition, the information returned to the LBA 15020 in step 15107 may include a server challenge (spbmChallange) that can be selectively used by the SSP and the bundle management server for mutual authentication after step 15107. In addition, the information returned to the LBA 15020 in step 15107 may optionally include a digital signature of the delivered bundle management server to ensure the integrity of the returned information. In this case, it is necessary to determine whether the digital signature is valid. Bundle management server certificate (CERT.SPBM.DS) for signing can be included together. In this case, the signing bundle management server certificate (CERT.SPBM.DS) may be a certificate that exists on the same CI hierarchy as the certificate selected in step 15106. In addition, when one or more Sub CI certificates are required to determine whether the bundle management server certificate is valid, the information returned to the LBA 15020 may include one or more Sub CI certificates together with the bundle management server certificate.

FIG. 8 is a diagram illustrating an example of the structure of SSP certificate information generated by an SSP or SPBL or transmitted by an LBA to a bundle management server according to some embodiments of the present disclosure.

Referring to FIG. 8, SSP certificate information may be included in SSP information (SspInfo, 801) transmitted from the SSP to the bundle management server. The SSP certificate information may include basic certificate information (SspGeneralCryptoInfo, 811), bundle family certificate information (SspFamilyCryptoInfo, 833), and bundle family manager certificate information (SspOidCryptoInfo, 835 or 837). The SSP certificate information may include a bundle family certificate information block (SspFamilyCryptoInfoblock, 831), and the bundle family certificate information block 831 may include bundle family certificate information 833 and bundle family manager certificate information 835 or 837. I can.

Referring to FIG. 8, the basic certificate information 811 may include a bundle family identifier stored and managed in the SSP and certificate information to which a bundle family manager identifier is not assigned. In this case, the certificate information may include certificate information (SpbmVerification) that can be used by the SSP to verify the bundle management server and certificate information (SpblVerification) that can be used by the bundle management server to verify the SSP.

Referring to FIG. 8, the bundle family certificate information block 831 may include at least one bundle family identifier. The bundle family certificate information 833 may selectively include certificate information to which a bundle family identifier is assigned and to which a bundle family manager identifier is not assigned among certificate information stored in the SSP. The bundle family certificate information 833 is assigned a bundle family identifier included in the bundle family certificate information block 831 or the bundle family identifier included in the bundle family certificate information 833 among the certificate information stored in the SSP, and the bundle family manager Certificate information to which an identifier is not assigned may be optionally included. At this time, the certificate information may include certificate information (SpbmVerification) that can be used by the SSP to verify the bundle management server and certificate information (SpblVerification) that can be used by the bundle management server to verify the SSP.

Referring to FIG. 8, the bundle family manager certificate information 835 may include at least one bundle family manager identifier. The bundle family manager certificate information 835 may selectively include a bundle family identifier and certificate information to which the bundle family manager is assigned, among certificate information stored in the SSP. The bundle family manager certificate information 835 is the bundle family identifier included in the bundle family certificate information block 831 or the bundle family identifier and bundle family manager certificate information included in the bundle family certificate information 833 among the certificate information stored in the SSP. Certificate information assigned to the bundle family manager identifier included in 835 may be optionally included. At this time, the certificate information may include certificate information (SpbmVerification) that can be used by the SSP to verify the bundle management server and certificate information (SpblVerification) that can be used by the bundle management server to verify the SSP.

Referring to FIG. 8, SSP information 801 may include one or more bundle family certificate information blocks 831 or 851. More specifically, the SSP information 801 does not include the bundle family certificate information block 831 or 851 and the bundle family certificate information block 831 or at least one according to the settings of the SSP (7101, 7102, 7200, 7300). It can include more than one. Further, the bundle family certificate information block 831 may include one or more bundle family manager certificate blocks 835 or 837.

9 is a diagram illustrating an example of a procedure in which an SSP of a terminal generates supportable certificate information set for a specific bundle family identifier or a specific bundle family identifier and a bundle family manager identifier according to a request from an LBA according to some embodiments of the present disclosure. It is a drawing. 9 may correspond to an embodiment of a detailed procedure of step 7002 of FIG. 7A.

Referring to FIG. 9, in step 9001, the SSP may receive a request for certificate information from the LBA. In step 9003, the SSP may determine whether a specific bundle family identifier and a bundle family manager identifier are included in the certificate information request transmitted from the LBA.

If a specific bundle family identifier and bundle family manager identifier are included in the certificate information request, the SSP proceeds to step 9101 to determine whether the corresponding bundle family identifier and bundle family manager identifier are supported. That is, it may be determined whether the certificate information set in the bundle family identifier and the bundle family manager identifier exists. For example, referring to FIG. 7A, when a bundle family identifier and a bundle family manager identifier are input as shown in (FID1, Oid1), the SSP may determine that the corresponding bundle family identifier and the bundle family manager identifier are supported. Alternatively, when the bundle family identifier and the bundle family manager identifier are input, such as (FID2, Oid6), the SSP may determine that the corresponding bundle family identifier and the bundle family manager identifier, especially the bundle family identifier, are not supported. If the certificate information exists in step 9101, in step 9102, the SSP includes the bundle family identifier, the bundle family manager identifier, the bundle family identifier, and the certificate information set in the bundle family manager identifier. ) Can be created. In addition, the SSP may include a corresponding bundle family identifier in the bundle family certificate block 831 of the SSP information 801 posted in FIG. 8. In addition, the bundle family manager certificate information 835 may be generated by including the corresponding bundle family manager identifier in the bundle family manager certificate information 835 and including the bundle family identifier and certificate information set in the bundle family manager identifier.

Referring to FIG. 9, when there is no certificate information set in the bundle family identifier and the bundle family manager identifier in operation 9101, it may be determined whether certificate information including the bundle family identifier exists in operation 9103. For example, referring to FIG. 7A, when a bundle family identifier and a bundle family manager identifier are input, such as (FID2, Oid6), the SSP does not support the bundle family identifier and the bundle family manager identifier, especially the bundle family identifier. After determining, it proceeds to step 9103. Thereafter, in step 9103, the SSP determines that only the corresponding bundle family identifier is supported, and may select a value set in (FID2, *). If the certificate information exists in step 9103, in step 9104, the SSP may generate the SSP information 801 posted in FIG. 8 including the bundle family identifier and certificate information set in the bundle family identifier. In addition, the SSP may include a corresponding bundle family identifier in the bundle family certificate block 831 of the SSP information 801 posted in FIG. 8. In addition, bundle family certificate information 833 may be generated including certificate information set in the bundle family identifier.

Referring to FIG. 9, when there is no certificate information set in the bundle family identifier in step 9103, the SSP in step 9105 includes the bundle family identifier and certificate information to which the bundle family manager identifier is not assigned, and the SSP posted in FIG. Information 801 can be generated. For example, referring to FIG. 7A, when a bundle family identifier and a bundle family manager identifier are input as shown in (FID3, OID1), the SSP determines that the bundle family identifier does not also support, and values set in (*, *) You can choose. In addition, basic certificate information 811 may be generated including a bundle family identifier stored and managed in the SSP and certificate information to which a bundle family manager identifier is not assigned.

Referring to FIG. 9, if the bundle family manager identifier does not exist in step 9003, the SSP may determine whether the bundle family identifier is included in the certificate information request transmitted from the LBA in step 9005. For example, referring to FIG. 7A, when only the FID is input, the SSP does not have an Oid, so the operation may proceed to step 9005.

When only a specific bundle family identifier is included in the certificate information request in step 9005, in step 9201, the SSP may determine whether a certificate configuration including the corresponding bundle family identifier exists. For example, referring to FIG. 7A, when only FID2 is input, the SSP may determine whether SSP configuration information having FID2, for example, 7102 or 7200 exists. The certificate setting including the bundle family identifier may refer to certificate information to which the corresponding bundle family identifier and the bundle family manager identifier are assigned, or certificate information to which the bundle family identifier is assigned and the bundle family manager identifier is not assigned.

In step 9201, if there is certificate information set in the bundle family identifier and at least one bundle family manager identifier, SSP information posted in FIG. 8 including the bundle family identifier, bundle family manager identifier, and set certificate information ( 801) can be created. In addition, the SSP may include a corresponding bundle family identifier in the bundle family certificate block 831 of the SSP information 801 posted in FIG. 8. In addition, at least one bundle family manager certificate information 835 may be generated including the bundle family manager identifier, the bundle family identifier, and certificate information set in the bundle family manager identifier. In addition, when at least a plurality of certificate information is mapped to the bundle family manager identification information, a plurality of bundle family manager certificate information 835 may be generated.

In addition, in step 9201, if the bundle family identifier is assigned and there is certificate information to which the bundle family manager identifier is not assigned, in step 9202, the SSP includes the corresponding certificate information and the SSP information 801 posted in FIG. Can be generated. The SSP may include a corresponding bundle family identifier in the bundle family certificate block 831 of the SSP information 801 posted in FIG. 8. In addition, bundle family certificate information 833 may be generated including certificate information set in the bundle family identifier.

In step 9201, if the certificate setting including the bundle family identifier does not exist, the SSP is the SSP information posted in FIG. 8 including the bundle family identifier and certificate information to which the bundle family manager identifier is not assigned in step 9203. 801 can be created. In addition, basic certificate information 811 may be generated including a bundle family identifier stored and managed in the SSP and certificate information to which a bundle family manager identifier is not assigned.

9, when the bundle family identifier does not exist in step 9005, for example, if there is no input, the SSP generates SSP information 801 including all certificate information set in the SSP in step 9007. I can.

10 is a diagram illustrating an example of a procedure in which a terminal downloads and installs a bundle from a bundle management server according to some embodiments of the present disclosure.

Referring to FIG. 10, bundle download information may be transmitted to the LBA 1020 of the terminal 1000 in step 10001. The bundle download information includes the address of the bundle management server to which the LBA 820 will access (SPBM Addr), the bundle identifier of the prepared bundle, the bundle family identifier of the prepared bundle (SPB Family ID), and the bundle family manager identifier of the prepared bundle (SPB Family Custodian Object). ID) may be at least one of. The bundle identifier may include at least one of a bundle matching ID and a bundle event ID. Also, the bundle identifier may include a bundle family identifier and a bundle family manager identifier of the prepared bundle. The bundle Event ID may include at least one of a bundle matching ID and an address of a bundle management server. Bundle download information is input by the subscriber 1030 to the LBA 1020 (eg, QR code scanning, direct text input, etc.), or the LBA 1020 using a push input through an information providing server (not shown). Can be entered in In addition, the LBA 1020 may access the information providing server (not shown) previously set in the terminal 1000 to receive bundle download information.

In step 10002, the terminal 1000 and the bundle management server 1050 may perform a procedure of negotiating a certificate for selecting a certificate that can be used for mutual authentication and encryption with each other. The operation of step 10002 may correspond to the operation of FIG. 7A.

In step 10003, the LBA 1020 may request SSP authentication information (SSP Credential) from the SSP 1010. In this case, the LBA 1020 may request SSP authentication information including the bundle matching ID. In addition, the LBA 1020 is a bundle family identifier (spbFamilyId) of a bundle to be additionally downloaded, a bundle family manager identifier (Oid), a certificate of the bundle management server 1050, certificate information to be used by the SSP (sspCiToBeUsed), and the bundle management server. At least one of the server challenges (spbmChallenge) may be selectively delivered to the SSP 1010. In this case, the SPBM certificate may be data including a key agreement certificate (CERT.SPBM.DS) or a temporary public key for a key agreement of a bundle management server that can be used to generate a session key.

In step 10103, the SSP 1010 includes certificate information (SpbmVerification) that the SSP 1010 can use to verify the bundle management server for each set bundle family identifier and bundle family manager identifier and the bundle management server verifies the SSP. Bundle support is possible by comparing the available certificate information (SpblVerification) with the certificate of the bundle management server 1050 delivered from the LBA 1020 in step 10003, the certificate information to be used by the SSP, the bundle family identifier, and the bundle family manager identifier Whether it can be verified.

In step 10004, the SSP 1010 may generate a session key (ShKey01) with the bundle management server 1050. The SSP 1010 may generate an SSP temporary public key (ePK.SSP.KA) and an SSP temporary secret key (eSK.SSP.KA). In addition, the SSP 1010 extracts the public key for Key Agreement (PK.SPBM.KA) from the certificate of the bundle management server 850 delivered in step 10001 or 10002 or 10003, and discloses the Key Agreement for the bundle management server. A session key (ShKey01) can be generated through a key generation function (KDF) using a key (PK.SPBM.KA) and an SSP temporary secret key (eSK.SSP.KA). In this case, the SSP 1010 may use a key generation function defined in BSI TR 03111 as a key generation function, and the session key may be composed of 128 bits or 256 bits.

In step 10005, the SSP 1010 may generate SSP authentication information (SSP Credential). In step 8002, the SSP 1010 encrypts the SSP certificate (CERT.SSP.DS) existing in the hierarchy of the certificate negotiated with the bundle management server 1050 using the session key (ShKey01) generated in step 10004 to encrypt the SSPToken01. Can be generated. At this time, the SSP certificate may be a digital signature certificate. In addition, the SSP 1010 may generate SSPToken01 by encrypting the SSP identifier (SSP ID) together with the SSP certificate (CERT.SSP.DS).

In addition, in step 10005, the SSP 1010 may generate SSPToken02 by including at least one Transaction ID indicating a current session, a bundle matching ID, and an SSP temporary public key (ePK.SSP.KA). In this case, the SSP 1010 may optionally include a bundle management server challenge (spbmChallenge) to generate SSPToken02. In addition, the SSP 1010 may generate the SSPToken02 including a digital signature of the SSP capable of verifying the integrity of the information included in the SSPToken02 with the SSP certificate (CERT.SSP.DS) included in the SSPToken01. SSPToken01 and SSPToken02 may be transferred from the SSP 1010 to the LBA 1020. In step 10005, the SSP 1010 may store at least one of a bundle family identifier, a bundle family manager identifier, and used certificate information of the current session in connection with the Transaction ID of the current session.

In addition, the SSP 1010 may inform the LBS 1020 that a result for at least one of steps 10103, 10004, 0, and 10005 is generated due to the request of the LBA 1020 transmitted in step 10003. In addition, the LBA 1020 may confirm that the result is generated in step 10005 and request the SSP 1010 to transmit the information generated in step 10005. The SSP 1010 may transmit SSP authentication information (SSP Credential) to the LBA 1020 in step 10105.

In step 10006, the terminal 1000 may transmit SSP authentication information (SSP Credential) to the bundle management server 1050. Further, in step 10006, the LBA 1020 and the bundle management server 1050 may perform TLS connection. The TLS connection in step 10006 may use a server authentication method in which the LBA 1020 checks the identity of the bundle management server 1050 among TLS connection methods. In step 8005, the terminal 1000 may transmit SSPToken01 and SSPToken02 to the bundle management server 1050. In addition, the terminal 1000 may transmit the SSP Maker certificate (CERT.SM.DS) to the bundle management server 1050 for validity of the SSP certificate included in SSPToken01. If one or more Sub CI certificates are required to validate the SSP Maker certificate (CERT.SM.DS), in step 10006, the terminal 1000 sends one or more Sub CI certificates together with the SSP Maker certificate to the bundle management server 1050. Can be submitted.

In step 10007, the bundle management server 1050 may verify SSP authentication information (SSP Credential). In step 10007, the bundle management server 850 is a key paired with the SSP temporary public key (ePK.SSP.KA) included in SSPToken02 and the key agreement public key (PK.SPBM.KA) of the bundle management server 1050. The session key (ShKey01) can be generated through the Key Derivation Function (KDF) using the Agreement secret key (SK.SPB.KA). In this case, the bundle management server 1050 may use a key generation function defined in BSI TR 03111 as a key generation function, and the session key (ShKey01) may be configured with 128 bits or 256 bits. In step 10007, the bundle management server 1050 may extract the SSP certificate (CERT.SSP.DS) by decrypting the SSPToken01 using the session key (ShKey01). In addition, in step 8006, the SSP certificate may be verified using the SSP Maker certificate transmitted from the LBA 1020. The bundle management server 1050 may extract the SSP public key (PK.SSP.DS) from the SSP certificate (CERT.SSP.DS) and verify the digital signature of the SSP included in SSPToken02.

In step 10008, the bundle management server 1050 may generate a session key for use with the SSP 1010. The bundle management server 1050 may generate an SPBM temporary public key (ePK.SPBM.KA) and an SPBM temporary secret key (eSK.SPBM.KA). In addition, the bundle management server 1050 uses the SSP temporary public key (ePK.SSP.KA) and SPBM temporary secret key (eSK.SPBM.KA) verified in step 10007 to generate a key function (Key Derivation Function, KDF). Session key (ShKey02) can be generated through. At this time, the key generation function defined in BSI TR 03111 may be used as the key generation function, and the session key may be composed of 128 bits or 256 bits.

In step 10008, the bundle management server 1050 may generate an SPBMToken. The SPBMToken generated by the bundle management server 1050 may include at least one SPBM temporary public key (ePK.SPBM.KA) and Transaction ID, and may include a digital signature of SPBM that can verify the integrity of the information. have.

In step 10008, the bundle management server 1050 may generate a bundled bundle by encrypting all or part of the bundle with a session key (ShKey02) so that the bundle can be decrypted only by the SSP 1010.

In step 10007 or step 10008, the bundle management server may generate bundle metadata (not shown). The bundle metadata may include at least one of a bundle family identifier and a bundle family manager identifier of a bundle. Also, the bundled bundle or bundle may include at least one of a bundle family identifier and a bundle family manager identifier of a corresponding bundle.

In step 10009, the bundle management server 1050 may deliver the SPBMToken and the bound bundle to the LBA 1020. In this case, the bundle management server 1050 may deliver bundle metadata. At this time, the bundle management server 1050 includes a bundle management server certificate (CERT.SPBM.DS) for verifying the digital signature of the bundle management server included in the SPBMToken, and the SPBMToken and a bundled bundle with the LBA 1020. Can be delivered. When one or more Sub CI certificates are required to validate the bundle management server certificate (CERT.SPBM.DS), in step 10009, the bundle management server 1050 transfers one or more Sub CI certificates along with the bundle management server certificate to the LBA (1020). ) Can be submitted. The LBA 1020 may transmit the information to the SSP 1010 to request verification and bundle installation.

In step 10010, the SSP 1010 may verify the SPBM Token. In step 10010, the SSP 1010 verifies the validity of the bundle management server certificate (CERT.SPBM.DS), and uses the bundle management server public key (PK.SPBM.DS) included in the certificate to be included in the bundle included in the SPBMToken. The digital signature of the management server can be verified. In addition, the SSP 1010 may verify the validity of the SPBMToken by comparing whether the Transaction ID generated by the SSP 1010 in step 10005 and the Transaction ID included in the SPBMToken are the same. In addition, the SSP 1010 uses the SSP temporary secret key (eSK.SSP.KA) and the bundle management server temporary public key (ePK.SPBM.KA) included in the SPBMToken to use the Key Derivation Function (KDF). Through this, a session key (ShKey02) can be generated. At this time, the key generation function defined in BSI TR 03111 may be used as the key generation function, and the session key may be composed of 128 bits or 256 bits. In step 10009, the SSP 1010 may decrypt the bound bundle using the session key (ShKey02) and install the bundle in the SSP 1010. In step 10010, when installing the bundle, a user (End User, not shown) may additionally receive a bundle installation confirmation according to a setting value of at least one of the terminal 0100, the SSP 1010, and the LBA 1020. In step 10010, the SSP 1010 may transmit the bundle installation result to the LBA 1020.

In step 10011, the SSP 1010 may compare the bundle family identifier stored in step 10003 with the bundle family identifier of the installed bundle, and if they are the same, transmit the installation completion result to the LBA 1020. If the two identifiers do not match, the installed bundle may be deleted or a state of being disabled may be set and the result may be transmitted to the LBA 1020.

11 is a diagram illustrating an example of a procedure for verifying a certificate used by a bundle management server in a bundle download process according to some embodiments of the present disclosure. 11 is a diagram illustrating an example of a procedure corresponding to step 10103 of FIG. 10.

Referring to FIG. 11, in step 11001, the SSP may receive a command for generating SSP authentication information (SSP Credential) from the LBA. The information delivered from the LBA in step 11001 includes at least one of the bundle family identifier (spbFamilyId) of the bundle to be downloaded, the bundle family manager identifier (Oid), the certificate of the bundle management server 1050, and certificate information to be used by the SSP (sspCiToBeUsed). can do. In addition, when one or more Sub CI certificates are required to determine whether the bundle management server certificate is valid, one or more Sub CI certificates may be included together with the bundle management server certificate.

Referring to FIG. 11, in step 11003, the SSP stores the bundle family identifier and bundle family manager identifier, the bundle family identifier and bundle family manager identifier included in the certificates, the certificate and certificate information to be used by the SSP in the SSP. Information and comparison can be verified. In step 11101, the SSP may extract the bundle family identifier and bundle family manager identifier setting values from the transmitted certificates. That is, the SSP may extract FID and Oid values, and there may be a plurality of these values. In step 11103, the SSP determines whether there is a common value between the bundle family identifier extracted from each certificate and the bundle family manager identifier setting value. In this case, there may be a plurality of common values. If the common value does not exist in step 11103, the SSP may determine that the bundle family identifier and the bundle family manager identifier of the certificates of the bundle management server delivered by the LBA are invalid, generate a verification failure error, and terminate the verification process.

Referring to FIG. 11, if a common value exists in step 11103, in step 11105, the SSP includes the bundle family identifier and bundle family manager identifier transmitted in step 11001, the common bundle family identifier, and bundle family manager identifier checked in step 11103. It can be determined whether the same value exists in the set value. If the same value does not exist in step 11105, the SSP may determine that the bundle family identifier and the bundle family manager identifier of the certificates of the bundle management server delivered by the LBA are invalid, generate a verification failure error, and terminate the verification process.

Referring to FIG. 11, when the same value exists in step 11105, in step 11107, the SSP checks whether the bundle family identifier identified in step 11105 and the certificate assigned to the bundle family manager identifier exist. In addition, if the bundle family identifier and the bundle family manager identifier are not included in the certificates delivered from the LBA in step 11101, the SSP may not perform steps 11103 and 11105. In step 11107, the SSP may check whether the bundle family identifier transferred in step 11001 and the certificate assigned to the bundle family manager identifier exist. If the certificate setting exists in the SSP, in step 11009, the SSP can verify the certificate delivered in step 11001 using at least one of the certificate information (SpbmVerification) that can be used to verify the bundle management server of the certificate setting. have. In addition, it can be determined whether at least one value of the certificate information (SpblVerification) that can be used by the bundle management server of the certificate setting to verify the SSP matches the certificate information (sspCiToBeUsed) to be used by the SSP delivered in step 11001. .

Referring to FIG. 11, in step 11107, if the bundle family identifier and the certificate settings assigned to the bundle family manager identifier do not exist in the SSP, the SSP can check whether a certificate setting assigned to the bundle family identifier exists. have. If the certificate setting exists in the SSP, in step 11009, the SSP verifies the transmitted certificate in step 11001 using at least one of the certificate information (SpbmVerification) that can be used to verify the bundle management server of the certificate setting. can do. In addition, it can be determined whether at least one value of the certificate information (SpblVerification) that can be used by the bundle management server of the certificate setting to verify the SSP matches the certificate information (sspCiToBeUsed) to be used by the SSP delivered in step 11001. .

Referring to FIG. 11, when there is no certificate setting assigned to a corresponding bundle family identifier in step 11107, the SSP may check whether there is a bundle family identifier and certificate information to which the bundle family manager identifier is not assigned. If there is a certificate setting in the SSP, in step 11009, the SSP can verify the delivered certificate in step 11001 using at least one of the certificate information (SpbmVerification) that can be used to verify the bundle management server of the certificate setting. have. In addition, it may be determined whether at least one value of the certificate information (SpblVerification) that can be used by the bundle management server of the certificate setting to verify the SSP matches the certificate information (sspCiToBeUsed) to be used by the SSP delivered in step 11001. .

Referring to FIG. 11, if the verification of certificates or certificate information to be used by the SSP fails in step 11009, the SSP determines that the certificate of the bundle management server delivered by the LBA is not valid, generates a verification failure error, and terminates the verification process. I can.

12 is a diagram illustrating an example of a procedure for verifying a certificate used in a bundle download process by a bundle management server according to some embodiments of the present disclosure. 12 is a diagram illustrating an example of a procedure corresponding to step 10010 of FIG. 10.

Referring to FIG. 12, the SSP may receive a bundle installation command from the LBA in step 12001. In this case, the information transmitted from the LBA may include at least one of the SPBM token and a bound bundle, bundle metadata, and a certificate of the bundle management server shown in step 10009 of FIG. 10. In addition, when one or more Sub CI certificates are required to determine whether the bundle management server certificate is valid, one or more Sub CI certificates may be included together with the bundle management server certificate. In addition, the bundle metadata or the bundled bundle may include a bundle family identifier or bundle family identifier of a current bundle, and a bundle family manager identifier.

Referring to FIG. 12, in step 12002, the SSP may call at least one of a bundle family identifier, a bundle family manager identifier, and a certificate setting stored in a current download session. The information may be stored in connection with a Transaction ID indicating a current session. Alternatively, in step 12002, the SSP may load the bundle metadata delivered in step 12001, the bundle family identifier included in the bundled bundle, and the certificate settings assigned to the bundle family manager identifier.

Referring to FIG. 12, in step 12003, the SSP may verify one or more Sub CI certificates together with the bundle management server certificate and the bundle management server certificate delivered from the LBA. In step 12101, the SSP may extract the bundle family identifier and bundle family manager identifier setting values from the transmitted certificates. That is, the SSP may extract FID and Oid values, and there may be a plurality of these values. In step 12103, the SSP determines whether a common value between the bundle family identifier extracted from each certificate and the bundle family manager identifier setting value exists. In this case, there may be a plurality of common values. If the common value does not exist in step 12103, the SSP may determine that the bundle family identifier and the bundle family manager identifier of the certificates of the bundle management server delivered by the LBA are invalid, generate a verification failure error, and terminate the verification process.

Referring to FIG. 12, if a common value exists in step 12103, in step 12105, the SSP includes the bundle metadata delivered in step 12001 or the bundle family identifier included in the bundled bundle, the bundle family manager identifier, and the common bundle identified in step 12103. It can be determined whether the same value exists in the family identifier and the bundle family manager identifier setting value. In step 12105, if the same value does not exist, the SSP may determine that the bundle family identifier and the bundle family manager identifier of the certificates of the bundle management server delivered by the LBA are not valid, may generate a verification failure error, and terminate the verification process.

Referring to FIG. 12, if the same value exists in step 12105, in step 12107, the SSP includes the bundle family identifier and bundle family manager identifier identified in step 12105, and the bundle family identifier and bundle stored in the current download session loaded in step 12002. You can check whether the family manager identifier matches. In addition, if the bundle family identifier and the bundle family manager identifier are not included in the certificates delivered from the LBA in step 12101, the SSP may not perform steps 12103 and 12105. In step 12107, the SSP matches the bundle metadata delivered in step 12001 or the bundle family identifier included in the bundled bundle, the bundle family manager identifier, and the bundle family identifier stored in the current download session and the bundle family manager identifier loaded in step 12002. You can check whether or not.

In step 12107, if the two values do not match, the SSP may determine that the bundle family identifier and the bundle family manager identifier of the certificates of the bundle management server delivered by the LBA are not valid, generate a verification failure error, and terminate the verification process. .

Referring to FIG. 12, it may be determined whether the bundle family identifier and the bundle family manager identifier checked in step 12105 in step 12107 match the bundle family identifier and bundle family manager identifier stored in the current download session loaded in step 12002. . In addition, in step 12009, the SSP may verify the certificates of the bundle management server delivered in step 12001 by using the certificate information (SpbmVerification) that can be used to verify the bundle management server among the certificate settings imported in step 12002.

Referring to FIG. 12, when verification of certificates or certificate information to be used by the SSP fails in step 12009, the SSP determines that the certificate of the bundle management server delivered by the LBA is not valid, generates a verification failure error, and terminates the verification process. I can.

13 is a diagram illustrating a configuration of a terminal according to some embodiments of the present disclosure.

As shown in FIG. 13, the terminal may include a transceiver 13010 and at least one processor 13020. In addition, the terminal may include an SSP (13030). For example, the SSP 13030 may be inserted into the terminal or may be embedded in the terminal. The at least one processor 13020 may be referred to as a control unit.

However, the configuration of the terminal is not limited to FIG. 13, and may include more or fewer components than the components illustrated in FIG. 13. According to some embodiments, the transmission/reception unit 13010, at least one processor 13020, and a memory (not shown) may be implemented in the form of one chip. In addition, when the SSP 13030 is embedded, it may be implemented in the form of a single chip, including the SSP 13030. According to some embodiments, the transmission/reception unit 13010 may transmit and receive signals, information, data, etc. according to various embodiments of the present disclosure to and from a bundle management server. The transceiver 13010 may include an RF transmitter that up-converts and amplifies a frequency of a transmitted signal, and an RF receiver that amplifies a received signal with low noise and down-converts a frequency. However, this is only an embodiment of the transmission/reception unit 13010, and components of the transmission/reception unit 13010 are not limited to the RF transmitter and the RF receiver. In addition, the transmission/reception unit 13010 may receive a signal through a wireless channel, output it to the at least one processor 13020, and transmit a signal output from the at least one processor 13020 through a wireless channel.

According to some embodiments, the transmission/reception unit 13010 may receive a certificate of the bundle management server, CI information to be used by the SSP 13030, a bundle family identifier, a bundled bundle, and the like from the bundle management server. In addition, the transmission/reception unit 13010 may transmit CI information corresponding to a specific bundle family identifier, authentication information of the SSP 13030, and the like to the bundle management server.

On the other hand, at least one processor 13020 is a component for overall control of the terminal. The at least one processor 13020 may control the overall operation of the terminal according to various embodiments of the present disclosure as described above.

Meanwhile, the SSP 13030 may include a processor or controller for installing and controlling a bundle, or may have an application installed.

According to some embodiments, at least one processor or controller in the SSP 13030 checks CI (Certificate Issuer) information that can be used when downloading and installing a specific bundle corresponding to a specific bundle family identifier, and is preset in the SSP. At least one of a bundle management server certificate, CI information to be used by the SSP, and bundle family identifiers transmitted based on CI information for each bundle family identifier that is present may be verified.

In addition, according to some embodiments, at least one processor 13020 controls the transmission/reception unit 13010 to transmit CI information corresponding to a specific bundle family identifier to the bundle management server, and the bundle management server's certificate , CI information to be used by the Smart Secure Platform (SSP), and at least one of a bundle family identifier may be received.

The SSP 13030 according to various embodiments may download a bundle and install the bundle. In addition, the SSP 13030 may manage a bundle.

In addition, according to some embodiments, the SSP 13030 may operate under the control of the processor 13020. Alternatively, the SSP 13030 may include a processor or controller for installing and controlling a bundle, or may have an application installed. Some or all of the applications may be installed in the SSP 13030 or a memory (not shown).

Meanwhile, the terminal may further include a memory (not shown), and may store data such as a basic program, an application program, and setting information for the operation of the terminal. In addition, the memory is a flash memory type, a hard disk type, a multimedia card micro type, a card type memory (eg, SD or XD memory, etc.), and magnetic Memory, magnetic disk, optical disk, RAM (Random Access Memory, RAM), SRAM (Static Random Access Memory), ROM (Read-Only Memory, ROM), PROM (Programmable Read-Only Memory), EEPROM (Electrically Erasable Programmable Read- Only Memory) may include at least one storage medium. In addition, the processor 13020 may perform various operations using various programs, contents, data, etc. stored in the memory.

14 is a diagram illustrating a configuration of a bundle management server according to an embodiment of the present disclosure.

According to some embodiments, the bundle management server may include a transceiver 14010 and at least one processor 14020. However, the configuration of the bundle management server is not limited to FIG. 14, and may include more or fewer components than the components illustrated in FIG. 14. According to some embodiments, the transmission/reception unit 14010, at least one processor 14020, and a memory (not shown) may be implemented in the form of one chip.

According to some embodiments, the transmission/reception unit 14010 may transmit and receive signals, information, data, etc. according to various embodiments of the present disclosure with a terminal, a subscriber, or a service provider. For example, the transmission/reception unit 14010 receives a specific bundle family identifier or certificate information corresponding to the bundle family manager identifier and the bundle family manager identifier from the terminal, and the authentication information of the SSP, and the certificate of the bundle management server and the SSP You can send the certificate information to be used, the bundle family identifier, and the bundled bundle.

The transceiver 14010 may include an RF transmitter that up-converts and amplifies a frequency of a transmitted signal, and an RF receiver that amplifies a received signal with low noise and down-converts a frequency. However, this is only an embodiment of the transmission/reception unit 14010, and components of the transmission/reception unit 14010 are not limited to the RF transmitter and the RF receiver. In addition, the transmission/reception unit 14010 may receive a signal through a wireless channel, output it to the at least one processor 14020, and transmit a signal output from the at least one processor 1402 through a wireless channel.

Meanwhile, at least one processor 14020 is a component for overall control of the bundle management server. The processor 14020 may control the overall operation of the bundle management server according to various embodiments of the present disclosure as described above. The at least one processor 14020 may be referred to as a control unit.

According to some embodiments, the at least one processor 14020 selects a certificate of the bundle management server to be transmitted to the terminal and certificate information to be used by the SSP of the terminal, and verifies the SSP Credential of the terminal, SPBMToken and Bound Bundle can be created.

In addition, according to some embodiments, the at least one processor 14020 transmits a certificate of the bundle management server, certificate information to be used by the SSP, a bundle family identifier, a bundled bundle, etc. to the terminal, and corresponds to a specific bundle family identifier from the terminal. The transceiver 14010 may be controlled to receive certificate information, SSP authentication information, and the like.

Meanwhile, the bundle management server may further include a memory (not shown), and may store data such as a basic program, an application program, and setting information for the operation of the bundle management server. In addition, the memory is a flash memory type, a hard disk type, a multimedia card micro type, a card type memory (eg, SD or XD memory, etc.), and magnetic Memory, magnetic disk, optical disk, RAM (Random Access Memory, RAM), SRAM (Static Random Access Memory), ROM (Read-Only Memory, ROM), PROM (Programmable Read-Only Memory), EEPROM (Electrically Erasable Programmable Read- Only Memory) may include at least one storage medium. In addition, the processor 14020 may perform various operations using various programs, contents, data, etc. stored in the memory.

In the above-described specific embodiments of the present disclosure, components included in the disclosure are expressed in the singular or plural according to the presented specific embodiments. However, the singular or plural expression is selected appropriately for the situation presented for convenience of description, and the present disclosure is not limited to the singular or plural constituent elements, and even constituent elements expressed in plural are composed of the singular or singular. Even the expressed constituent elements may be composed of pluralities.

Meanwhile, although specific embodiments have been described in the detailed description of the present disclosure, various modifications are possible without departing from the scope of the present disclosure. Therefore, the scope of the present disclosure is limited to the described embodiments and should not be determined, and should be determined by the scope of the claims as well as the equivalents of the claims to be described later.

Various embodiments of the present disclosure and terms used therein are not intended to limit the technology described in the present disclosure to a specific embodiment, and should be understood to include various modifications, equivalents, and/or substitutes of the corresponding embodiment. In connection with the description of the drawings, similar reference numerals may be used for similar elements. Singular expressions may include plural expressions unless the context clearly indicates otherwise. In this disclosure, expressions such as "A or B", "at least one of A and/or B", "A, B or C" or "at least one of A, B and/or C" are all of the items listed together It can include possible combinations. Expressions such as "first", "second", "first" or "second" can modify the corresponding elements regardless of their order or importance, and are only used to distinguish one element from another. The components are not limited. When any (eg, first) component is referred to as being “(functionally or communicatively) connected” or “connected” to another (eg, second) component The element may be directly connected to the other component, or may be connected through another component (eg, a third component).

The term "module" used in the present disclosure includes a unit composed of hardware, software, or firmware, and may be used interchangeably with terms such as, for example, logic, logic blocks, parts, or circuits. A module may be an integrally configured component or a minimum unit or a part of one or more functions. For example, the module may be configured as an application-specific integrated circuit (ASIC).

Various embodiments of the present disclosure include a machine-readable storage media (for example, a software (for example, a computer) including instructions stored in an internal memory or an external memory. For example, a program) may be implemented as a device that calls a stored command from a storage medium and is capable of operating according to the called command, and may include a terminal 250 according to various embodiments. When an instruction is executed by a processor (for example, the processor 820 of FIG. 8 or the processor 920 of FIG. 9), the processor directly or by using other components under the control of the processor The instruction may include code generated or executed by a compiler or interpreter.

A storage medium that can be read by a device may be provided in the form of a non-transitory storage medium. Here, "non-transitory" means that the storage medium does not contain signals and is tangible, but does not distinguish between semi-permanent or temporary storage of data in the storage medium.

A method according to various embodiments disclosed in the present disclosure may be included in a computer program product and provided. Computer program products can be traded between sellers and buyers as commodities. The computer program product can be distributed online in the form of a device-readable storage medium (e.g., compact disc read only memory (CD-ROM)) or through an application store (e.g., Play StoreTM). have. In the case of online distribution, at least some of the computer program products may be temporarily stored or temporarily generated in a storage medium such as a server of a manufacturer, a server of an application store, or a memory of a relay server.

Each of the constituent elements (eg, a module or a program) according to various embodiments may be composed of a singular or a plurality of entities, and some sub-elements of the aforementioned sub-elements are omitted, or other sub-elements May be further included in various embodiments. Alternatively or additionally, some constituent elements (eg, a module or a program) may be integrated into a single entity to perform the same or similar functions performed by each corresponding constituent element prior to the consolidation. Operations performed by modules, programs, or other components according to various embodiments may be sequentially, parallel, repetitively or heuristically executed, or at least some operations may be executed in a different order, omitted, or other operations may be added. I can.

Claims (1)

In the terminal certificate management and verification method,
Obtaining certificate information that can be used when downloading and installing a specific bundle corresponding to at least one of the bundle family identifier and the bundle family manager identifier;
Transmitting, to a bundle management server, certificate information corresponding to at least one identifier of the specific bundle family identifier and the bundle family manager; And
Receiving, from the bundle management server, at least one of a certificate of the bundle management server, certificate information to be used by a Smart Secure Platform (SSP), the bundle family identifier, and the bundle family manager identifier, and certificate management of the terminal And verification method.

Images