KR102237840B1 - APPARATUS AND METHODS TO INSTALL AND MANAGE eSIM PROFILES - Google Patents

Abstract

The present disclosure relates to a communication technique and a system for fusing a 5G communication system with IoT technology to support a higher data rate after a 4G system. This disclosure is based on 5G communication technology and IoT-related technology, and intelligent services (e.g., smart home, smart building, smart city, smart car or connected car, healthcare, digital education, retail, security and safety related services, etc. ) Can be applied. The present invention discloses an apparatus and method for safely providing a profile to a terminal in a communication system.

Description

How and how to install and manage eSIM profiles {APPARATUS AND METHODS TO INSTALL AND MANAGE eSIM PROFILES}

The present invention relates to a method and apparatus for communication connection by downloading and installing a communication service in a terminal in a communication system. In addition, the present invention relates to a method and apparatus for downloading, installing, and managing a profile online in a communication system.

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 called 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 (eg, 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 transmission distance of radio waves, in 5G communication systems, beamforming, massive MIMO, and Full Dimensional MIMO (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) methods such as FQAM (Hybrid FSK and QAM Modulation) and SWSC (Sliding Window Superposition Coding), advanced access technologies such as FBMC (Filter Bank Multi Carrier), NOMA (non orthogonal multiple access), and sparse code multiple access (SCMA), and the like are being developed.

Meanwhile, the Internet is evolving from a human-centered network in which humans create and consume information, to an Internet of Things (IoT) network that exchanges and processes information between distributed components such as objects. IoE (Internet of Everything) technology, which combines IoT technology with big data processing technology through connection with cloud servers, is also emerging. In order to implement IoT, technological elements such as sensing technology, wired/wireless communication and network infrastructure, service interface technology, and security technology are required. , 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 machine type communication (MTC) are implemented by techniques such as beamforming, MIMO, and array antenna. There is. The application of a cloud radio access network (cloud RAN) as the big data processing technology described above can be said as an example of the convergence of 5G technology and IoT technology.

UICC (Universal Integrated Circuit Card) is a smart card inserted into a mobile communication terminal and used, and is also called a UICC card. An access control module for accessing the mobile communication service provider's network may be included in the UICC. Examples of such 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. In the following description of the present invention, the SIM card will be used in the usual sense including a UICC card, a USIM card, and a UICC including ISIM. That is, even for a SIM card, its technical application can be applied equally to a USIM card, an ISIM card, or a general UICC card.

The SIM card stores personal information of a mobile communication subscriber, and performs subscriber authentication and traffic security key generation when accessing a mobile communication network, thereby enabling safe mobile communication use.

At the time of proposing the present invention, the SIM card is generally manufactured as a dedicated card for the corresponding operator at the request of a specific mobile communication operator when the card is manufactured, and authentication information for network access of the corresponding operator, for example, USIM ( Universal Subscriber Identity Module) application, IMSI (International Mobile Subscriber Identity), K value, OPc value, etc. are loaded on the card in advance and shipped. Therefore, the manufactured SIM card is supplied by the mobile communication service provider and provided to the subscriber, and if necessary, management of the installation, modification, and deletion of applications in the UICC is also performed by using technology such as OTA (Over The Air). can do. Subscribers can insert the UICC card into their own mobile communication terminal to use the network and application services of the mobile communication service provider, and when the terminal is replaced, the UICC card is stored in the UICC card by moving and inserting the card from the existing terminal to the new terminal. Authentication information, mobile phone number, personal phone book, etc. can be used as it is in the new terminal.

However, the SIM card is inconvenient for a mobile communication terminal user to receive services from other mobile communication companies. A mobile communication terminal user is inconvenient in having to physically acquire a SIM card in order to receive a service from a mobile communication service provider. For example, when traveling to another country, it is inconvenient to obtain a local SIM card in order to receive local mobile communication services. In the case of a roaming service, the above inconvenience is solved to some extent, but there is also a problem in that the service cannot be received if there is no contract between the service provider and expensive rates.

On the other hand, when the SIM module is downloaded and installed remotely on a UICC card, such inconvenience can be largely solved. That is, the SIM module of the mobile communication service that the user wants to use at a desired time can be downloaded to the UICC card. Such a UICC card can also download and install a plurality of SIM modules, and select and use only one SIM module among them. Such a UICC card may or may not be fixed to the terminal. In particular, the UICC fixed to the terminal is called eUICC (embedded UICC). Typically, the eUICC refers to a UICC card that can be fixed to the terminal and used by remotely downloading and selecting a SIM module. In the present invention, a UICC card capable of remotely downloading and selecting a SIM module will be collectively referred to as eUICC. In other words, among UICC cards that can be selected by downloading a SIM module remotely, UICC cards that are fixed or not fixed to the terminal will be collectively used as eUICC. In addition, the SIM module information to be downloaded will be collectively used as the term eUICC profile.

The technical problem to be achieved by the present invention is to provide a method and an apparatus for communication connection by a terminal selecting a communication service in a communication system. In addition, the technical problem to be achieved by the present invention is to provide a method and apparatus for downloading, installing, and managing a profile for a terminal for communication connection in a communication system online. In addition, the technical problem to be achieved by the present invention is to provide an apparatus and method for safely providing a profile to a terminal in a communication system.

In particular, the present invention proposes a solution to the following parts for the above purpose.

-How the terminal transmits a message requesting profile download or remote profile management to the profile management server (SM-DP+)

-The profile management server (SM-DP+) selectively responds to profile download or profile remote management to the terminal, and the terminal returns reference information to be used when generating a profile download or profile remote management request message to be delivered to the next step. Way

-Message exchange procedure between the terminal and the profile management server (SM-DP+)

In the wireless communication system according to an embodiment of the present invention, the terminal displays the type of event (profile download or profile remote management) that the terminal wants to perform from the user and receives an input (User Interface). Includes, the profile management server (SM-DP+), an identifier (EID) of the eUICC in the terminal, an identifier (EventRequestType) indicating the type of event that the terminal intends to perform, and an identifier indicating whether the terminal allows remote profile management (RPMConfig). ), and a transmitter capable of transmitting one or more of an identifier (ICCID) of a profile to which the terminal is to perform profile remote management, and an identifier (OperatorID) of an operator currently providing a communication service to the terminal, and In response, the terminal includes a receiver capable of receiving one or more of the types and number of one or more events to be performed by the terminal and one or more events to be performed next from the profile management server (SM-DP+), and the terminal Includes an input unit (User Interface unit) that displays information on one or more events to be performed to a user and receives user's consent for the execution of the events. It includes a control unit that determines whether to proceed with or stops the execution of the event, and when it is determined to proceed with the execution of the event (that is, when there is user consent), and includes a control unit that performs the event, and reports the execution result of the event to the profile management server (SM -A control unit capable of transmitting a message requesting the next event to the profile management server (SM-DP+) according to the type and number of one or more events to be performed next by the terminal, including a control unit and a transmission unit that can be transmitted to DP+) And a transmission unit.

In a wireless communication system according to an embodiment of the present invention, the profile management server (SM-DP+) includes an event storage for storing an event (profile download or profile remote management) to be performed by the eUICC of the terminal, Including a control unit and a determination unit that can control and determine the priority of events stored in the event storage, an identifier (EID) of an eUICC in the terminal from the terminal, an identifier (EventRequestType) indicating the type of event that the terminal intends to perform, and Among the identifiers (RPMConfig) indicating whether the terminal allows remote profile management, the identifier of the profile to which the terminal is to perform remote profile management (ICCID), and the operator ID (OperatorID) currently providing communication services to the terminal. Includes a receiving unit capable of receiving one or more, including a receiving unit capable of receiving eUICC authentication information including a signature, and prioritizes the messages of the received terminal and events stored in the event storage of the profile management server (SM-DP+) Includes a determination unit that compares the rankings and selects one or more events to be performed by the terminal, and includes a determination unit that determines the type and number of one or more events to be performed next by the terminal among events stored in the event storage, and Including a transmitter capable of transmitting one or more of one or more events to be performed by the terminal and one or more types and numbers of one or more types and numbers to be performed next by the terminal, and a receiver capable of receiving a result of performing the event from the terminal , It characterized in that it comprises a receiver capable of receiving a message requesting the next event from the terminal.

The technical problems to be achieved in the present invention 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 invention belongs from the following description. I will be able to.

According to an embodiment of the present invention, in a communication system, the terminal informs the profile management server (SM-DP+) of the current user's input, and the terminal must perform the current profile download or profile remote management from the profile management server (SM-DP+). You can selectively receive events to be performed and receive guidance on events to be performed next. Through this, when one or more events (profile download or profile remote management) are waiting in the profile management server (SM-DP+), the terminal can automatically request and receive the next event and then perform it.

1 is a diagram illustrating a method of connecting a terminal to a mobile communication network using a UICC equipped with a fixed profile.
2 is a diagram illustrating a message exchange procedure between a terminal and a profile server when one or more profiles are installed through a profile server.
3 is a diagram illustrating a message exchange procedure between a terminal and a profile server when one or more profiles are installed through a profile server and one or more profiles are remotely managed.
4 is a diagram illustrating a method of specifying an event type corresponding to a command input by a user when a terminal requests an event from a profile server according to an embodiment of the present invention.
5 is a diagram illustrating a method for a profile server to manage an event storage according to an embodiment of the present invention.
6 is a diagram illustrating a method of setting whether a profile server can batch transmit one or more events according to an embodiment of the present invention.
7 is a diagram illustrating a method of delivering an event to be performed when a profile server constructs an event response message according to an embodiment of the present invention.
8 is a diagram illustrating a method of delivering an event to be performed next when a profile server constructs an event response message according to an embodiment of the present invention.
9 is a diagram illustrating a procedure for configuring an event response message by a profile server according to an embodiment of the present invention.
10, 11, and 12 are diagrams illustrating a message procedure performed by sequentially receiving one or more events by a terminal and a profile server according to an embodiment of the present invention.
13 is a diagram illustrating a procedure for a terminal to request a'profile download' from a server and receive a response thereto according to an embodiment of the present invention.
14 is a diagram illustrating a procedure for a terminal to request'remote management of a profile' from a server and receive a response thereto according to an embodiment of the present invention.
15 is a diagram illustrating a procedure in which a terminal requests all kinds of events from a server and receives a response thereto according to an embodiment of the present invention.
16 is a diagram illustrating a method of sequentially processing events after obtaining data for all events by a terminal according to an embodiment of the present invention.
17 is a diagram illustrating a method of obtaining and processing data for each event by a terminal according to an order of reception of events according to an embodiment of the present invention.
18 is a diagram illustrating a method in which a profile server generates and attaches a separate signature to each profile remote management and profile summary information data according to an embodiment of the present invention.
19 is a diagram illustrating a method of specifying a processing order of each data while a profile server generates and attaches a separate signature to each profile remote management and profile summary information data according to an embodiment of the present invention.
FIG. 20 is a diagram illustrating a method in which a profile server generates and attaches a common signature to a part of each profile remote management and profile summary information data according to an embodiment of the present invention.
21 is a diagram illustrating a method of specifying a processing order of each data while a profile server creates and attaches a common signature to some of each profile remote management and profile summary information data according to an embodiment of the present invention.
22 and 23 are diagrams illustrating a signature generation and data arrangement method according to various embodiments of the present disclosure.
24A, 24B to 26 are diagrams illustrating a method of configuring a user interface (UI) in a terminal according to various embodiments of the present disclosure.
28 is a block diagram illustrating components of a terminal according to an embodiment of the present invention.
29 is a block diagram illustrating components of a server according to an embodiment of the present invention.

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

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

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

First, terms used in the present specification are defined.

In this specification, UICC is a smart card inserted and used in a mobile communication terminal, and stores personal information such as network access authentication information, phone book, and SMS of a mobile communication subscriber, and when accessing a mobile communication network such as GSM, WCDMA, LTE, etc. It refers to a chip that enables secure mobile communication by performing authentication and traffic security key generation. UICC is equipped with communication applications such as SIM (Subscriber Identification Module), USIM (Universal SIM), ISIM (IP Multimedia SIM), etc., depending on the type of mobile communication network the subscriber accesses. It can provide a high-level security function for mounting various application applications.

In the present specification, an eUICC (embedded UICC) is a security module in the form of a chip embedded in the terminal, not a removable type that can be inserted and removed in the terminal. eUICC can download and install a profile using OTA (Over The Air) technology. eUICC can be named as UICC, which allows profile download and installation.

In the present specification, the method of downloading and installing a profile using OTA technology in eUICC may also be applied to a detachable UICC that can be inserted and removed in a terminal. That is, in an embodiment of the present invention, it can be applied to a UICC that can be installed by downloading a profile using OTA technology.

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

In the present specification, a profile may mean packaging of an application, a file system, an authentication key value, etc. stored in the UICC in a software format.

In the present specification, the USIM Profile may have the same meaning as a profile or may mean that information included in a USIM application in the profile is packaged in a software form.

In the present specification, the profile providing server includes a function of generating a profile, encrypting the generated profile, generating a profile remote management command, or encrypting the generated profile remote management command, and SM-DP (Subscription Manager Data Preparation) , SM-DP+ (Subscription Manager Data Preparation plus), off-card entity of Profile Domain, Profile Encryption Server, Profile Creation Server, Profile Provisioner (PP), Profile Provider, PPC holder (Profile Provisioning Credentials) holder).

In this specification, the profile management server is SM-SR (Subscription Manager Secure Routing), SM-SR+ (Subscription Manager Secure Routing Plus), off-card entity of eUICC Profile Manager or PMC holder (Profile Management Credentials holder), EM (eUICC Manager) ) Can be expressed.

When referring to the profile providing server in the present specification, it may be collectively referred to as a combination of the functions of the profile management server. Accordingly, in various embodiments of the present invention, that is, in the following description, it is of course possible to perform the above operation in the profile management server with respect to the operation of the profile providing server. Similarly, it goes without saying that the operation described for the profile management server or the SM-SR may be performed in the profile providing server.

The term'terminal' as used herein 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 smartphone 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 this specification, the terminal may also be referred to as an electronic device.

In the present specification, the electronic device may have a built-in UICC that can be installed by downloading a profile. When the UICC is not embedded in the electronic device, the UICC physically separated from the electronic device may be inserted into the electronic device and connected to the electronic device. For example, in the form of a card, the UICC may be inserted into an electronic device. The electronic device may include the terminal, and in this case, the terminal may be a terminal including a UICC capable of downloading and installing a profile. The UICC may be embedded in the terminal, and when the terminal and the UICC are separated, the UICC may be inserted into the terminal, or inserted into the terminal to be connected to the terminal. A UICC that can be installed by downloading a profile may be referred to as eUICC, for example.

In the present specification, the terminal or electronic device may include software or applications installed in the terminal or electronic device to control the UICC or eUICC. The software or application may be referred to as, for example, Local Profile Assistant (LPA).

In this specification, the profile identifier is a Profile ID, ICCID (Integrated Circuit Card ID), Matching ID, Event ID, Activation Code, Activation Code Token, ISD-P Alternatively, it may be referred to as a factor matching a profile domain (PD). Profile ID may indicate a unique identifier of each profile. The profile identifier may include an address of a profile providing server (SM-DP+) capable of indexing a profile.

In this specification, the eUICC identifier (eUICC ID) may be a unique identifier of an eUICC embedded in the terminal, and may be referred to as an EID. In addition, when a provisioning profile is pre-loaded in the eUICC, it may be an identifier of a corresponding provisioning profile (Provisioning Profile ID). In addition, if the terminal and the eUICC chip are not separated as in the embodiment of the present invention, it may be a terminal ID. In addition, it may refer to a specific secure domain of the eUICC chip.

In the present specification, a profile container may be referred to as a profile domain. The profile container may be a security domain.

In this specification, an application protocol data unit (APDU) may be a message for a terminal to interwork with an eUICC. In addition, the APDU may be a message for the PP or PM to interwork with the eUICC.

In the present specification, Profile Provisioning Credentials (PPC) may be a means used for mutual authentication, profile encryption, and signature between the profile providing server and the eUICC. The PPC 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 a plurality of profile providing servers, different PPCs for each of the plurality of profile providing servers may be stored or used in the eUICC.

In the present specification, PMC (Profile Management Credentials) 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 a plurality of profile management servers, different PMCs for each of the plurality of profile management servers may be stored or used in the eUICC.

In this specification, the AID may be an application identifier. This value may be a separator that distinguishes different applications within eUICC.

In the present specification, an event may be a term collectively referring to Profile Download or Remote Profile Management or other profile or eUICC management/processing command. Profile Download can be mixed with Profile Installation. In addition, event type can be used as a term indicating whether a specific event is a profile download, remote profile management, or other profile or eUICC management/processing command. Class or OperationClass), Event Request Type, Event Class, Event Request Class, and the like.

In this specification, a profile package may be mixed with a profile or used as a term indicating a data object of a specific profile, and may be referred to as a Profile TLV or a Profile Package TLV (Profile Package TLV). When the profile package is encrypted using an encryption parameter, it may be referred to as a protected profile package (PPP) or a protected profile package TLV (PPP TLV). When the profile package is encrypted using an encryption parameter that can be decrypted only by a specific eUICC, it may be referred to as a bound profile package (BPP) or a bound profile package TLV (BPP TLV). The profile package TLV may be a data set representing information constituting a profile in a TLV (Tag, Length, Value) format.

In this specification, remote profile management (RPM) refers to profile remote management, remote management, remote management command, remote command, and remote profile management package. It may be named as (RPM Package), Profile Remote Management Package, Remote Management Package, Remote Management Command Package, and Remote Command Package. RPM changes the status of a specific profile (Enabled, Disabled, Deleted), or updates the content of a specific profile (e.g., Profile Nickname, Profile Metadata, etc.). Can be used for purposes. The RPM may include more than one remote management command, and in this case, the target profile of each remote management command may be the same or different for each remote management command.

In this specification, AKA may indicate authentication and key agreement, and may indicate an authentication algorithm for accessing 3GPP and 3GPP2 networks.

In this specification, K is an encryption key value stored in the eUICC used in the AKA authentication algorithm.

In this specification, OPc is a parameter value that can be stored in the eUICC used in the AKA authentication algorithm.

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

In the following description of the present invention, when it is determined that a detailed description of a related known function or configuration may unnecessarily obscure the subject matter of the present invention, a detailed description thereof will be omitted.

1 is a diagram illustrating a method of connecting a mobile communication network of a terminal using a UICC on which a profile fixed to the terminal is mounted.

Referring to FIG. 1, the UICC 120 may be inserted into the terminal 110. In this case, the UICC may be detachable or may be unknown to the terminal. The fixed profile of the UICC on which the fixed profile is mounted means that “access information” for accessing a specific communication company is fixed. The access information may be, for example, a K or Ki value required to authenticate to the network along with the subscriber identifier, IMSI, and subscriber identifier.

Then, the terminal can perform authentication with the mobile communication company's authentication processing system (for example, HLR (home location register) or AuC) using the UICC. The authentication process may be an AKA (Authenticaiton and Key Agreement) process. After successful authentication, the terminal can use mobile communication services such as telephone or mobile data use by using the mobile communication network 130 of the mobile communication system.

2 is a diagram illustrating a message exchange procedure between the terminal 230 and the profile server 250 when one or more profiles are installed through a profile server.

Referring to FIG. 2, in step 201, the terminal 230 receives a "Add Profile" command from a user, and in step 203, a TLS connection and mutual authentication with the profile server 250 are performed (Mutual Authentication). can do. In step 205, the terminal may transmit the eUICC identifier (EID) of the terminal as a final procedure of the mutual authentication procedure. In step 207, the profile server may check a list of events to be installed in the corresponding terminal through the EID. In step 209, the profile server may select an event with the highest priority (install profile 1 in this embodiment) from the list of events. In step 211, the profile server may return the summary information of the selected profile to the terminal. In step 213, the terminal may obtain user consent for profile installation by showing the profile summary information to the user. In step 215, the terminal may transmit the user consent to the profile server to receive the profile package. In step 217, the terminal can successfully install the profile package, and transmit the result to the profile server in step 219.

In the profile package installation procedure, when one or more events are waiting in the profile server, it cannot be notified to the terminal that there are more events waiting in the profile server after execution and processing of a specific event. In addition, in order to install more than one profile, the user has to enter the "Add Profile" command several times in the terminal.

3 is a diagram illustrating a message exchange procedure between the terminal 230 and the profile server 250 when one or more profiles are installed through a profile server and one or more remote management is performed.

Referring to FIG. 3, in step 301, the terminal 230 receives a command "Add PRofile" from the user, and performs TLS connection and mutual authentication with the profile server 250 in step 303. can do. In step 305, the terminal may transmit the eUICC identifier (EID) of the terminal as a final procedure of the mutual authentication procedure. In step 307, the profile server may check a list of events (profile or remote management) to be installed in the corresponding terminal through the EID. In step 309, the profile server may select an event with the highest priority (remote management 1 in this embodiment) from the event list. In step 311, the profile server may return the selected remote management command to the terminal. In step 313, the terminal may execute the received remote management command. In step 315, the terminal may transmit the result of executing the remote management command to the profile server.

In the profile installation and remote management procedure, when one or more events are waiting in the profile server, it cannot be notified to the terminal that there are more waiting events in the profile server after execution and processing of a specific event. In addition, according to the present embodiment, even though the user issues the "Add Profile" command to the terminal in step 301, the terminal first receives the remote management command, which is the highest priority event, from the profile server. Since it performs an operation different from the intention of the user, there is room for confusion to the user.

4 is a diagram illustrating a method of specifying an event type corresponding to a command input by a user when the terminal 230 requests an event from the profile server 250 according to the application of the present invention.

Referring to FIG. 4, in step 401, the terminal may receive an “Add Profile” command from a user. In step 403 for the user input, the terminal may request an event by completing the TLS secure connection and mutual authentication procedure with the profile server, and specifying an event type corresponding to the profile download. In this case, the event type may be expressed as text ("ProfileDownload" in the present embodiment), or as a value of one of an enumerate corresponding thereto. For example, if the number strings "0, 1" correspond to "Profile Download" and "Profile Remote Management", respectively, the number "0" may be used instead of the text "ProfileDownload". In addition, in step 403, the terminal can notify the profile server whether the current user has activated (on) the profile remote management function of the terminal, or notify the operator ID (OperatorID) of the operator currently providing the communication service to the terminal. have. In step 405, the profile server may select a profile installation event having a high priority according to the request of the terminal. The event type, whether or not the profile management function is activated, a method of utilizing the operator identifier information by the profile server, and a method of managing the priority of an event will be described in detail in the following embodiments.

Further, referring to FIG. 4, in step 407, the terminal may receive a “Refresh Profile” command from the user. In step 409 for the user input, the terminal may request an event by completing the TLS secure connection and mutual authentication procedure with the profile server, and specifying an event type corresponding to the remote profile management. In this case, the event type may be expressed as text ("RPM" in the present embodiment) or as a value of one of an enumerate corresponding thereto. For example, if the number strings "0, 1" correspond to "download profile" and "remote profile management", respectively, the number "1" may be used instead of the text "RPM". In addition, in step 409, the terminal can notify the profile server whether the current user has activated (on) the profile remote management function of the terminal, or notify the operator ID (OperatorID) of the operator currently providing the communication service to the terminal. have. In step 411, the profile server may select a profile remote management event having a high priority according to the request of the terminal. The event type, whether the profile management function is activated, a method of using the operator identifier information by the profile server, and a method of managing the priority of an event will be described in detail in the following embodiments.

In addition, referring to FIG. 4, in step 413, the terminal may receive an “Update All” command from a user. In step 415 for the user input, the terminal may request an event by completing the TLS secure connection and mutual authentication procedure with the profile server, and specifying an event type corresponding to profile download and profile remote management. At this time, the event type is expressed as a single text ("ANY" in the present embodiment), or as one or more values of the corresponding number string, or the method used in the embodiment of downloading the profile or remotely managing the profile is applied in combination. Can be marked. For example, if the text of "ProfileDownload, RPM" is used instead of the text "ANY", or the numeric strings "0, 1, 2" correspond to'Profile Download','Profile Remote Management', and'All Events', respectively. The number '2' can be used, or the number string '0, 1'can be used. In addition, in step 415, the terminal can notify the profile server whether the current user has activated (on) the profile remote management function of the terminal, or notify the operator ID (OperatorID) of the operator currently providing the communication service to the terminal. have. In step 417, the profile server may select an event with a high priority (profile download or profile remote management) according to the request of the terminal. The event type, whether or not the profile management function is activated, a method of utilizing the operator identification information by the profile server, and a method of managing the priority of an event will be described in detail in the following embodiments.

5 is a diagram illustrating a method of managing an event storage by a profile server according to the application of the present invention.

Referring to FIG. 5, the profile server may manage event storage classified by an eUICC identifier (EID). One or more events ('profile download' or'profile remote management') to be performed by the corresponding eUICC (or terminal) may be stored in each event storage. In addition, the events stored in each event storage have respective priorities, and a method of calculating the priorities may follow one or a combination of two or more of the following examples, but is not limited to the following list.

-The order in which events were registered in the event repository

-Priority value assigned by a business operator when registering an event

-Type of event (for example, profile download may have a higher priority than profile remote management)

-Priority value determined and assigned by the profile server

In addition, when more than one event has the same priority, the profile server may sort the events in an arbitrary order. In the embodiment of the present invention, an example in which the priority of events is managed in the form of First-In First-Out (FIFO) according to the order in which events are registered in the event storage has been described, but as described above, the priority of each event It should be noted that can be calculated in a variety of ways.

6 is a diagram illustrating a method of setting whether a plurality of events can be transmitted in a bundle in one message when a profile server transmits one or more events to a terminal according to the application of the present invention.

Referring to FIG. 6, the profile server may manage a table for setting whether to bundle transmission of a specific event type with another event type for each event type.

Referring to FIG. 6A, the profile server may be configured to bundle and transmit all events regardless of the event type.

Referring to FIG. 6B, the profile server may be configured not to allow only to bundle and transmit profile remote management events, and to bundle and transmit profile download events, or to bundle and transmit a profile download event and profile remote management event.

Referring to FIG. 6C, the profile server may be configured not to allow only to bundle and transmit the profile remote management event and the profile download event, and to bundle and transmit the profile download events or to bundle and transmit the profile remote management events.

Referring to FIG. 6D, the profile server may not allow any events to be bundled and transmitted.

In the present embodiment, examples of two types of events have been described. However, as described above, when the number of event types is increased by three or more, the size of the chart may be increased accordingly. In addition, it should be noted that the setting of whether the bundle transmission is possible for each event type is not limited to the example of the bundle transmission setting for each event type shown in FIGS. 6A to 6D, and may be set differently according to a combination of events to be transmitted in a bundle.

7 is, according to the application of the present invention, with respect to the event request message of the terminal,'Current Events' to be currently processed by the terminal and'Next Events' waiting in the event storage When constructing a response message to be returned to the terminal by the profile server including', it is a diagram showing a method of constructing information of the'current event'.

Referring to FIG. 7, in step 701, the terminal 230 may transmit an event request message to the profile server 250. The configuration and detailed description of the event request message will be described with reference to the embodiment of FIG. 4. With respect to the event request message of the terminal, in step 703, the profile server stores one or more'Current Events' selected according to priority from the event storage, and event information remaining in the event storage excluding the event. By using, an event response message can be configured. In this case, the selection of the current event may be performed as follows according to the event type specified in the event request message of the terminal, the event storage status of the profile server, and whether to allow priority transmission.

The profile server may manage a priority setting table that allows whether an event of a lower priority can be transmitted to a terminal before an event of a higher priority according to each event type.

Referring to FIG. 7A, even if the profile download event has a lower priority than the profile remote management event, it may be transmitted to the terminal with priority if requested by the terminal. However, if the profile remote management event has a lower priority than the profile download event, even if the terminal requests It can be set so that it cannot be transmitted to the terminal first. At this time, if the event priorities of the event storage are arranged in the same order as in the embodiment of the profile server 250, the profile download event (Profile1) corresponding to the third priority is the first when the terminal requests by specifying the profile download event. The profile remote management events (RPM1 and RPM2) corresponding to the second and second priorities may be selected prior to and transmitted to the terminal through the'Current Event' field. In this case, the remaining events (RPM1, RPM2, RPM3, Profile2) may be included in the'Next Events' and transmitted according to the embodiment of FIG. 8 to be described later.

Referring to FIG. 7B, except for the priority of the event, any event may be set such that no event can be transmitted with priority over other events. At this time, if the event priorities of the event storage are arranged in the same order as in the embodiment of the profile server 250, even if the terminal explicitly requests the profile download event, the profile remote management event (RPM1), which is the highest priority event, must be performed first. Therefore, the'Current Event' field becomes an empty field and no event may be transmitted to the terminal. In this case, the remaining events (RPM1, RPM2, Profile1, RPM3, Profile2) may be included in the'Next Events' and transmitted according to the embodiment of FIG. 8 to be described later.

In the embodiments of FIGS. 7A to 7B, a case in which only one event is selected according to whether or not to set priority transmission is described for the'current event', but this may be the case in which one or more events are selected as described above in the embodiment of FIG. It should be noted that there is. For example, in addition to the embodiment of FIG. 7A, as in the embodiment of FIG. 6A, when a bundle transmission of profile download events is enabled, the'Current Events' field in step 703a of FIG. 7A has two profiles. Download events (Profile1, Profile2) may be transmitted simultaneously.

8 is, according to the application of the present invention, with respect to the event request message of the terminal,'Current Events' to be currently processed by the terminal and'Next Events' waiting in the event storage A diagram showing a method of configuring information of'Next Events' when configuring a response message to be returned by the profile server to the terminal including'.

Referring to FIG. 8, in step 801, the terminal 230 may transmit an event request message to the profile server 250. The configuration and detailed description of the event request message will be described with reference to the embodiment of FIG. 4. With respect to the event request message of the terminal, in step 803, the profile server stores one or more'Current Events' selected from the event storage according to priority, and information of the events remaining in the event storage excluding the corresponding event. By using, an event response message can be configured. At this time, with respect to the selection of the current event, the present embodiment shows a case in which one remote management event (RPM1) is selected according to the request of the terminal. It should be noted that more than one event may be selected, and the event type specified in the event request message of the terminal may be retrieved from the event storage and transmitted prior to the highest priority event, as in the embodiment of FIG. 7. In addition, information of the next event may be compositely configured using one or more of the following information elements, and the usable information elements are not limited thereto.

-Event type of the event with the highest priority among remaining events

-Event type of one or more remaining events

-Presence of one or more remaining events

-The number of each event type when categorizing the remaining events by event type

For example, in the embodiment of FIG. 8, when only the event type of the event with the highest priority is returned, the event response message may be configured as follows.

-Current Events = RPM1, Next Events = "RPM"

As another example, in the embodiment of FIG. 8, when an event type of all remaining events is returned, the event response message may be configured as follows.

-Current Events = RPM1, Next Events = "RPM, ProfileDownload, RPM, ProfileDownload"

As another example, in the embodiment of FIG. 8, when the remaining events are categorized by event type and the number of each event type is returned, the event response message may be configured as follows.

-Current Events = RPM1, Next Events = "RPM (2), ProfileDownload (2)"

As another example, in the embodiment of FIG. 8, when replying that one or more remaining events remain regardless of the event type, the event response message may be configured as follows.

-Current Events = RPM1, Next Events = TRUE

In the above embodiment, text ("RPM" or "ProfileDownload") is used to indicate the event type. However, as described above in the embodiment of FIG. 4, not only text but also a number string may be used. In addition, when it is desired to notify the terminal of the existence of one or more events regardless of the event type, a binary identifier (Boolean) having TRUE/FALSE may be used instead of text or number strings.

9, according to the application of the present invention, a profile server configures an event response message to an event request message of a terminal with reference to whether the event bundle transmission and event priority transmission described in the embodiments of FIGS. 6 to 8 are set. It is a diagram showing the procedure to do.

Referring to FIG. 9, in step 901, the profile server may receive an event request message from a terminal. In the event request message, the type of event requested by the terminal according to the above-described embodiment of FIG. 4 and whether a profile remote management function is activated/deactivated (On/Off) in the current terminal may be specified.

After the execution of step 901 or if the verification of step 913 fails, in step 903, the profile server prioritizes events in the event storage corresponding to the eUICC of the terminal that transmitted the event request message according to the embodiment of FIG. They can be sorted in order of ranking.

In step 905, the profile server checks whether the type of the highest priority event in the event storage matches the event type requested by the terminal in step 901.

If the verification procedure in step 905 fails or the verification procedure in step 909 is successful, in step 907, the profile server checks the event corresponding to the event type requested by the terminal in step 905 according to the embodiment of FIG. 7 described above. Make sure you can send the event prior to my highest priority event.

If the verification procedure in step 907 is successful, in step 915, the profile server searches the event storage for an event with the highest priority among the events corresponding to the event type requested by the terminal.

If the verification procedure in step 905 is successful, or after step 915 is performed, the profile server in step 909 indicates that the event is a profile remote management event, and at the same time, the profile remote management function of the current terminal is displayed in the event request message of the terminal received in step 901. Check if it is inactive (Off).

If the verification procedure in step 909 fails, the profile server extracts the event from the event storage according to the above-described embodiment of FIG. 7 and adds the event to the'Current Events' field.

After the execution of step 911, in step 913, the profile server checks whether other events can be bundled with the corresponding event according to the embodiment of FIG. 6 described above.

If the verification procedure in step 913 fails or the verification procedure in step 907 fails, in step 917, the profile server configures a'Next Events' field according to the embodiment of FIG. 8 described above.

After step 917 is performed, in step 919, the profile server may transmit an event response message consisting of'Current Events' and'Next Events' to the terminal. If the transmission of the event response message fails, or when a response to the failure of processing the event response message is received from the terminal in the future, the profile server will restore the event extraction operation in the event storage in step 911 performed more than once. I can.

10 is a diagram illustrating an example of a procedure in which the terminal 230 sequentially receives and performs one or more events from the profile server 250 according to the application of the present invention. In this embodiment, a profile corresponding to ICCID1 is installed/activated on the terminal, the remote profile management function of the terminal is activated (On), the event storage of the profile server is arranged according to the event registration time order, and the profile remote Management events cannot be transmitted in batches, but profile download events are transmitted in batches, and any event out of priority cannot be transmitted in priority, and the configuration of'Next Event' lists only the event type of the highest priority event in the event repository. Assume the case.

Referring to FIG. 10, in step 1001, the terminal may receive a command for “Add Profile” from a user.

In step 1003, the terminal performs a TLS secure connection and mutual authentication procedure with the profile server, and may request a profile download event from the profile server according to the user's request according to the above-described embodiment of FIG. 4.

In step 1005, the profile server may notify the terminal that one or more profile remote management events are waiting together with the profile download event (ICCID2), which is the highest priority event of the event storage, according to the above-described embodiments of FIGS. 6 to 9.

In step 1007, the terminal may install a profile (ICCID2) according to the received profile download event.

In step 1009, the terminal may transmit the execution result (that is, the profile installation result (ICCID2 Installation Result)) to the profile server for the performed profile download event.

In step 1011, the profile server may notify the terminal that the event execution result has been successfully received. In addition, the profile server may notify the terminal of'Next Events' remaining in the event storage in step 1011 as well as step 1005. The two types of messages for notifying the'Next Events' are complementary to each other, and the'next event' may be notified to both messages, or the'next event' may be notified only in one of the two messages. When'next event' is announced to both messages, the list of'next event' included in the two messages may be different. For example, when the priority of events in the event storage of the profile server is changed during the execution of steps 1007 to 1009 after the message transmission in step 1005, the list of'next events' included in the message in step 1011 may be changed.

In step 1013, the terminal may re-request an event to be performed next to the profile server according to the list of'next events' notified by the profile server in steps 1005 to 1011. When transmitting the re-request message, if the TLS secure connection and mutual authentication procedure between the terminal and the profile server in step 1003 are still valid, the terminal may omit the TLS secure connection and mutual authentication procedure with the profile server. In addition, if necessary, the terminal may inform the user that the event is to be requested from the profile server, and may transmit the event request message to the profile server after obtaining the user's consent. If the user does not agree, the terminal can terminate the procedure without requesting an additional event. In addition, if the next event to be performed according to the'next event' list is a profile remote management event, the identifier of the profile to be targeted for the event is not clear, so the event request type (EventReqType) is set to profile remote management. And the profile identifier may not be specified. The method of not specifying the profile identifier may transmit a NULL string or may not transmit the profile identifier field.

In step 1015, the profile server may notify the terminal that one or more profile remote management events are waiting together with the profile remote management event (Update ICCID1), which is the highest priority event of the event storage, according to the above-described embodiments of FIGS. 6 to 9. have.

In step 1017, the terminal may manage the profile (change the content of the profile corresponding to ICCID1) according to the received profile remote management event.

In step 1019, the terminal may transmit the execution result (ie, profile change result (ICCID1 Update Result)) to the profile server for the performed profile remote management event.

In step 1021, the profile server may notify the terminal that the event execution result has been successfully received. In addition, the profile server may notify the terminal of the'next event' remaining in the event storage in step 1015 as well as step 1021, similar to the procedure of step 1011 described above. For a detailed description of the configuration of the'next event' list, refer to the description of step 1011.

In step 1023, the terminal may re-request an event to be performed next to the profile server according to the list of'next events' announced by the profile server in steps 1015 to 1021, similar to the procedure of step 1013 described above. For a detailed description of TLS, secure connection and user agreement, refer to the description of step 1013. In addition, if the next event to be performed according to the'next event' list is a profile remote management event, the identifier of the profile to be targeted for the event is not clear, so the event request type (EventReqType) is set to all events ("ANY ") and may not specify the profile identifier (ProfileID). For a method of specifying'all events', refer to the above-described embodiment of FIG. 4. In addition, it will be easily understood that the subsequent procedure may be performed through repetition of steps 1001 to 1023 described above.

11 is a diagram illustrating an example of a procedure in which the terminal 230 sequentially receives and performs one or more events from the profile server 250 according to the application of the present invention. In this embodiment, a profile corresponding to ICCID1 is installed/activated on the terminal, the remote profile management function of the terminal is activated (On), the event storage of the profile server is arranged according to the event registration time order, and the profile remote Management events can be transmitted in batches, but profile download events cannot be transmitted in batches, and any event out of priority transmission is not possible, and the configuration of'next event' describes the type and number of all events in the event repository. Assume the case.

Referring to FIG. 11, in step 1101, the terminal may select a specific profile (ICCID1 in this embodiment) from a user and receive a command for “Refresh Profile”.

In step 1103, the terminal performs a TLS secure connection and mutual authentication procedure with the profile server, and may request a profile remote management event from the profile server according to the user's request according to the embodiment of FIG. 4 described above.

In step 1105, the profile server searches for a profile download event, which is the highest priority event in the event storage, according to the above-described embodiments of FIGS. 6 to 9, and the event does not correspond to the event type (profile remote management) requested by the terminal. Since priority transmission out of priority is not possible, no event is delivered, and one profile download event and three profile remote management events are pending using the'next event' list.

In step 1107, the terminal informs the user who issued the profile update command to the user who issued the profile update command according to the received'next event' list, and asks for the user's consent. I can. If the user does not agree, the terminal can terminate the procedure without any additional operation.

In step 1109, the terminal may re-request an event to be performed next to the profile server according to the'next event list' announced by the profile server in step 1105 and the user consent received in step 1107. When this re-request message is transmitted, at least one of the TLS secure connection or mutual authentication procedure between the terminal and the profile server in step 1103 has already been terminated, or a new event request message is sent as a new transaction ID according to the policy of the profile server. If it is to be distinguished, the terminal can perform a new TLS secure connection and mutual authentication procedure with the profile server.

In step 1111, the profile server uses the'next event' list together with the profile download event (ICCID2), which is the highest priority event of the event storage, according to the above-described embodiments of FIGS. 6 to 9 It can notify the terminal that is waiting. In this embodiment, a profile package is transmitted in response to an immediate response to step 1109. However, as shown in the example of FIG. 2, the profile metadata is first transmitted (step 211), and the profile is installed. After obtaining the user consent again (step 213), the terminal may request the profile package from the profile server (step 215), and transmit the profile package to the terminal. In this case, the additional user consent may be integrated with the user consent in step 1107.

In step 1113, the terminal may install a profile (ICCID2) according to the received profile download event (more specifically, a profile package).

In step 1115, the terminal may transmit the execution result (that is, the profile installation result (ICCID2 Installation Result)) to the profile server for the performed profile download event.

In step 1119, the profile server may notify the terminal that the event execution result has been successfully received. In addition, although not shown in this drawing, the profile server may repeat the'next event' list in step 1111 in step 1119, similar to the embodiment of FIG. 10 described above.

In step 1119, the terminal may re-request an event to be performed next to the profile server according to the'next event' list notified by the profile server in steps 1111 to 1117, similar to the procedure of step 1109 described above. For a detailed description of TLS, secure connection and user agreement, refer to the description of step 1109. In addition, if the next event to be performed according to the'next event' list is a profile remote management event, the identifier of the profile to be targeted for the event is not clear, so the event request type (EventReqType) is set to all events ("ANY It can be set to ").

In step 1121, the profile server bundles other profile remote management events (Enable ICCID2, Disable ICCID1) with the profile remote management event (Update ICCID1), which is the highest priority event of the event storage, according to the embodiments of FIGS. 6 to 9 described above. Can be transmitted. In addition, since there is no pending event in the event storage after the bundle transmission of the corresponding profile remote management events, it is possible to announce that there is nothing in the'next event' list ("Nothing More"). The method of notifying that the'next event' list is empty is to use text, use NULL data, omit the'next event' list itself, or that the remaining events are 0 for all event types, as in the present embodiment. You can use a method such as announcing.

In step 1123, the terminal may sequentially process the received profile remote management events. In addition, it will be easily understood that the subsequent procedure may be performed through repetition of steps 1101 to 1123 described above.

12 is a diagram illustrating an example of a procedure in which the terminal 230 sequentially receives and performs one or more events from the profile server 250 according to the application of the present invention. In this embodiment, a profile corresponding to ICCID1 is installed/activated on the terminal, the remote profile management function of the terminal is activated (On), the event storage of the profile server is arranged according to the event registration time order, and any event Also, it is assumed that bundled transmission is not possible, and only the profile remote management event can be transmitted prior to the profile download event when requested by the terminal, and the configuration of'next event' is assumed to describe only the event type of the highest priority event in the event repository. .

Referring to FIG. 12, in step 1201, the terminal may select a specific profile (ICCID1 in this embodiment) from a user and receive a command for “Refresh Profile”.

In step 1203, the terminal performs a TLS secure connection and mutual authentication procedure with the profile server, and may request a profile remote management event from the profile server according to the user's request according to the above-described embodiment of FIG. 4.

In step 1205, the profile server searches for a profile download event that is the highest priority event of the event storage according to the above-described embodiments of FIGS. 6 to 9, and the event does not correspond to the event type (profile remote management) requested by the terminal. , Since the profile remote management event can be transmitted with priority out of priority, the event with the highest priority (Update ICCID1 in this embodiment) among the events matching the event type (profile remote management) requested by the terminal from the event storage is prioritized. I can. In addition, the profile server may notify the terminal that a profile download event, which is the highest priority event, is waiting in the event storage except for the corresponding event by using the'next event' list.

In step 1207, the terminal may perform the received profile remote management event. Subsequently, the report on the execution result of the profile remote management event may be omitted if necessary.

In step 1209, the terminal may inform the user who issued the profile update command to the user who issued the profile update command according to the received'next event' list, and obtain the user's consent. . If the user does not agree, the terminal can terminate the procedure without any additional operation.

In step 1211, the terminal may re-request an event to be performed next to the profile server according to the list of'next events' notified by the profile server in step 1205. When this re-request message is transmitted, at least one of the TLS secure connection or mutual authentication procedure between the terminal and the profile server in step 1203 has already been terminated, or a new event request message is sent as a new transaction ID according to the policy of the profile server. If it is to be distinguished, the terminal can perform a new TLS secure connection and mutual authentication procedure with the profile server.

In step 1213, the profile server uses the'next event' list together with the profile download event (ICCID2), which is the highest priority event of the event storage, according to the above-described embodiments of FIGS. 6 to 9, and uses two profile remote management events. It can notify the terminal that is waiting. In this embodiment, a profile package is transmitted in response to an immediate response to step 1211. However, as in the example of FIG. 2 above, profile metadata is first transmitted (step 211), and profile installation is performed. After obtaining the user consent again (step 213), the terminal may request the profile package from the profile server (step 215), and transmit the profile package to the terminal. In this case, the additional user consent may be integrated with the user consent in step 1209.

In step 1215, the terminal may install a profile (ICCID2) according to the received profile download event (more specifically, a profile package).

In step 1217, the terminal may transmit the execution result (ie, the profile installation result (ICCID2 Installation Result)) to the profile server for the performed profile download event.

In step 1219, the profile server may notify the terminal that the event execution result has been successfully received. In addition, although not shown in this drawing, the profile server may repeat the'next event' list of step 1113 in step 1219, similar to the embodiment of FIG. 10 described above.

In step 1221, the terminal may re-request an event to be performed next to the profile server according to the'next event' list notified by the profile server in steps 1213 to 1219, similar to the procedure of step 1211 described above. For a detailed description of TLS, secure connection and user agreement, refer to the description of step 1211. In addition, if the next event to be performed according to the'next event' list is a profile remote management event, the identifier of the profile to be targeted for the event is not clear, so the event request type (EventRqeType) is set to all events ("ANY It can be set to ").

In step 1223, the profile server waits for the profile remote management event using the'next event' list together with the profile remote management event (Enable ICCID2), which is the highest priority event of the event storage, according to the above-described embodiments of FIGS. 6 to 9 You can notify the terminal that it is in progress.

In step 1225, the terminal may manage a profile (activate ICCID2) according to the received profile remote management event. In addition, the subsequent procedure may be performed through repetition of steps 1201 to 1225 described above.

Meanwhile, FIG. 13 is a procedure in which the terminal 230 requests the profile server 250 to'download a profile' and receives a response thereto when a profile is installed through a profile server according to another embodiment of the present invention. It is a figure showing.

Referring to FIG. 13, in step 1301, the terminal 230 may transmit a'arbitrary character string (Challenge)' to the profile server 250. The communication of step 1301 may be protected through HTTPS or TLS secure connection. In step 1303, the profile server 250 may transmit a'arbitrary character string (Challenge)' to the terminal 230 along with the server's signature. In step 1305, the terminal 230 may transmit a terminal authentication request message to the profile server 250. Specifically, the terminal 230 may transmit information about a specific event type (OperationType) requested together with a signature of the terminal 230 by using a terminal authentication request message to the profile server 250. In this example, a case in which a profile is waiting in the event storage 270 of the profile server and the terminal requests'Profile DL' will be described. The message exchange procedure between the terminal 230 and the profile server 250 in steps 1303 to 1305 may be referred to as a mutual authentication procedure. In step 1307, the profile server 250 may transmit a terminal authentication response message to the terminal 230. Specifically, the profile server 250, as requested by the terminal 230 in step 1305, includes profile summary information (Profile Metadata) and a one-time public key as part of preparation for profile download. The terminal authentication response message may be transmitted to the terminal 230. The profile summary information may include a name of a service provider, information on a logo and rate plan set by the service provider, and the like. In step 1309, the terminal 230 may receive an End User Consent for profile installation based on the profile summary information received in step 1307. When the user agrees to the profile installation, the terminal 230 may transmit a one-time public key to the profile server 250 in step 1311. In step 1313, the terminal 230 and the profile server 250 combine the one-time public key exchanged in steps 1307 to 1311 and the corresponding one-time private key to obtain a session key. Can be generated. In step 1315, the profile server 250 may return the encrypted profile package to the terminal 230 using the session key generated in step 1313. Thereafter, in step 1317, the terminal 230 may decrypt and install the encrypted profile package.

The profile download procedure, as described in steps 1311 to 1315, is performed once between the terminal 230 and the profile server 250 in order to receive the profile package required for the actual profile installation, compared to the profile remote management procedure to be described later. Additional message exchange is required.

14 is a diagram illustrating a procedure in which the terminal 230 requests'remote management of a profile' from the profile server 250 and receives a response to the request when performing remote management through a profile server.

Referring to FIG. 14, in step 1401, the terminal 230 may transmit a'arbitrary character string (Challenge)' to the profile server 250. The communication in step 1401 may be protected through HTTPS or TLS secure connection. In step 1403, the profile server 250 may transmit a'arbitrary character string (Challenge)' to the terminal 230 along with the server's signature. In step 1405, the terminal 230 may request the profile server 250 for a specific event type (OperationType) together with the terminal's signature. In this example, a case where a remote management command is waiting in the event storage 270 of the profile server and the terminal 230 requests'Profile Remote Management (RPM)' will be described. In steps 1403 to 1405, a message exchange procedure between the terminal 230 and the profile server 250 may be referred to as a mutual authentication procedure. In step 1407, the profile server 250 may transmit a package (RPM Command Package) including a profile remote management command to the terminal 230 as requested by the terminal 230 in step 1405. In step 1409, the terminal 230 may receive an End User Consent for profile management based on the remote profile management received in step 1407. If the user agrees to the remote profile management, the terminal 230 may perform a remote profile management command in step 1411.

In the profile remote management procedure, since the terminal 230 can receive all profile remote management commands in step 1407, the terminal corresponding to steps 1311 to 1315 of FIG. 13 compared to the profile download procedure described above in FIG. 13 ( 230) and the profile server 250 does not require an additional one-time message exchange.

15 is a procedure in which the terminal 230 requests all kinds of events from the profile server 250 and receives a response to the request when two profiles are installed through a profile server and remote management is performed twice It is a figure showing.

Referring to FIG. 15, in step 1501, the terminal 230 may transmit a'arbitrary character string (Challenge)' to the profile server 250. The communication in step 1501 may be protected through HTTPS or TLS secure connection. In step 1503, the profile server 250 may transmit a'arbitrary string (Challenge)' to the terminal 230 along with the server's signature. In step 1505, the terminal 230 may request the profile server 250 for a specific event type (OperationType) together with a signature of the terminal. In this example, a case where two remote management commands and two profiles are waiting in the event storage 270 of the profile server, and the terminal requests'all types' will be described. The message exchange procedure between the terminal 230 and the profile server 250 in steps 1503 to 1505 may be referred to as a mutual authentication procedure. In step 1507, the profile server 250 may simultaneously transmit profile remote management 1, profile summary information 1, profile remote management 2, and profile summary information 2, as requested by the terminal 230 in step 1505. In step 1509, the terminal 230 may receive an End User Consent for profile management and installation based on the profile remote management or profile summary information received in step 1507.

After step 1509, if the user agrees, the terminal 230 must perform a remote management and profile installation procedure for each profile. At this time, profile remote management (profile remote management 1 and profile remote management 2) can be performed immediately after step 1509, while profile installation (profile summary information 1 and profile summary information 2) is performed for each profile installation. As described above in step 1315, a profile package must be secured by performing one additional message exchange between the terminal 230 and the profile server 250. A detailed method for the terminal 230 to sequentially process profile remote management and profile installation will be described in detail with reference to FIGS. 16 to 17.

In addition, each profile summary information and profile remote management data in step 1507 need to be accompanied by a signature of the profile server 250 for the terminal 230 to verify data integrity. At this time, if the signature for the profile summary information data and the method for generating the signature for the profile remote management data (for example, a digital signature algorithm or a type of a digital certificate for signature) are different, the profile server 250 generates the signature and the data By appropriately adjusting the arrangement, the terminal 230 can easily verify the signature and support processing each data. A method in which the profile server 250 generates a digital signature and places data will be described in detail with reference to FIGS. 18 to 21.

16 is a diagram illustrating a method of sequentially processing events after obtaining data for all events by the terminal 230 according to the application of the present invention.

Referring to FIG. 16, in step 1601, the terminal 230 and the profile server 250 may perform a mutual authentication procedure. For a detailed description of the mutual authentication procedure and the operation request message of the terminal 230, the description of steps 1503 to 1505 of FIG. 15 will be referred to. In step 1603, the profile server 250 may transmit profile remote management 1, profile summary information 1, profile remote management 2, and profile summary information 2 at the same time. In step 1605, the terminal 230 may receive an End User Consent for remote profile management and installation based on the profile remote management or profile summary information received in step 1603. If the user agrees, the terminal 230 may request profile package 1 and profile package 2 corresponding to profile summary information 1 and profile summary information 2 in steps 1607 to 1609, respectively, and receive them from the profile server 250. . Thereafter, the terminal 230 performs the remote profile management 1 in step 1611, installs the profile package 1 in step 1613, and installs the profile package 1 in step 1615, according to the data processing order specified by the profile server 250 in step 1603. You can perform management 2 and install profile package 2 in step 1617.

In the above procedure, for all types of events received in step 1603, the terminal 230 collectively secures data necessary for processing each event (ie, a profile package for profile installation) in steps 1607 to 1609, In step 1603, the profile server 250 may perform remote profile management and profile installation according to the specified data processing order.

FIG. 17 is a diagram illustrating a method of obtaining and processing data for each event by the terminal 230 according to the application of the present invention.

Referring to FIG. 17, in step 1701, the terminal 230 and the profile server 250 may perform a mutual authentication procedure. For a detailed description of the mutual authentication procedure and the operation request message of the terminal 230, the description of steps 1503 to 1505 of FIG. 15 will be referred to. In step 1703, the profile server 250 may simultaneously transmit profile remote management 1, profile summary information 1, profile remote management 2, and profile summary information 2. In step 1705, the terminal 230 may receive an End User Consent for remote profile management and installation based on the profile remote management or profile summary information received in step 1703. If the user agrees, the terminal 230 performs profile remote management 1 in step 1707 according to the data processing order specified by the profile server 250 in step 1703, and the profile corresponding to profile summary information 1 in step 1709. Receive package 1, install profile package 1 in step 1711, perform remote profile management 2 in step 1713, receive profile package 2 corresponding to profile summary information 2 in step 1715, and install profile package 2 in step 1717. I can.

In the above procedure, the terminal 230 performs remote profile management first without securing additional data, according to the data processing order specified by the profile server 250 in step 1703 for all types of events received in step 1703, If necessary, as in step 1709 or 1715, a profile package may be additionally obtained from the profile server 250 to process profile installation.

18 is, according to the application of the present invention, when the profile server 250 transmits profile remote management or profile summary information to the message of the profile server 250 in steps 1603 of FIG. 16 to 1703 of FIG. 17 , A diagram showing a method of generating and attaching a separate signature to each profile remote management and profile summary information data.

Referring to FIG. 18, the profile server 250 may generate digital signatures 1803 and 1811 for 1801 profile remote management 1 data and 1809 profile remote management 2 data, respectively. In addition, the profile server 250 may generate digital signatures of 1807 and 1815 for 1805 profile summary information 1 data and 1813 profile summary information 2 data, respectively. In this case, even if the profile server 250 does not specify the processing order of each data, the terminal 230 may process the data in the order of receiving the data from the profile server 250. In this embodiment, the terminal 230 may process data in the order of profile remote management 1, profile summary information 1, profile remote management 2, and profile summary information 2.

In the above configuration, the profile server 250 has an advantage of being able to utilize various types of digital certificates and algorithms used to generate signatures for each data, since each data is accompanied by a separately distinguished signature.

19 is, according to the application of the present invention, when the profile server 250 transmits profile remote management or profile summary information to the message of the profile server 250 in steps 1603 of FIG. 16 to 1703 of FIG. 17 , It is a diagram showing a method of generating and attaching a separate signature to each profile remote management and profile summary information data, and specifying the processing order of each data.

Referring to FIG. 19, the profile server 250 may generate digital signatures 1903 and 1911 for 1901 profile remote management 1 data and 1909 profile remote management 2 data, respectively. In addition, the profile server 250 may generate digital signatures of 1907 and 1915 for 1905 profile summary information 1 data and 1913 profile summary information 2 data, respectively. Additionally, the profile server 250 may specify the processing order of each data. As an example, in this embodiment, the profile server 250 transmits four data, 1901 profile remote management 1 data is the first of four (1/4), 1905 profile summary information 1 data is the second of four ( 2/4), 1909 profile remote management 2 data can be specified in each data as the third (3/4) of the four data, and 1913 profile summary information 2 data is the fourth (4/4) of the four data.

In the above configuration, the profile server 250 has an advantage of being able to utilize various types of digital certificates and algorithms used to generate signatures for each data, since each data is accompanied by a separately distinguished signature. In addition, since the profile server 250 separately specifies the processing order of each data, there is an advantage of being able to freely control the transmission order of data. In this case, the present exemplary embodiment in which the profile server 250 specifies the processing order of data is not limited to FIG. 19, and the exemplary embodiment of FIG. 18, in which data is processed in the order of reception, may also specify the processing order of data.

FIG. 20 shows, according to the application of the present invention, when the profile server 250 transmits profile remote management or profile summary information to the message of the profile server 250 in steps 1603 of FIG. 16 to 1703 of FIG. 17 , It is a diagram showing a method of generating and attaching a common signature to some of the remote management of each profile and profile summary information data.

Referring to FIG. 20, the profile server 250 may generate a digital signature of 2011 for all of the 2001 profile remote management 1 data and the 2009 profile remote management 2 data. In addition, the profile server 250 may generate a digital signature of 2015 for all of the 2005 profile summary information 1 data and the 2013 profile summary information 2 data. In this case, even if the profile server 250 does not specify the processing order of each data, the terminal 230 may process the data in the order of receiving the data from the profile server 250. In this embodiment, the terminal 230 may process data in the order of profile remote management 1, profile summary information 1, profile remote management 2, and profile summary information 2.

In the above configuration, it should be noted that the data for which the profile server 250 generates a common signature is not necessarily limited to the same type of data. For example, FIG. 20 illustrates a case in which a common signature is generated by dividing profile remote management and profile summary information, but the profile server 250 uses the same signature generation method (ie, signature generation algorithm and digital certificate). You can create a common signature. In the above configuration, since the profile server 250 can omit the signature for data sharing the signature, the amount of data transmitted from the profile server 250 to the terminal 230 can be reduced. In the configuration of FIG. 20, after receiving the entire data of the profile server 250, the terminal 230 needs to separately collect data to be signed in order to verify the signature. In this embodiment, the terminal 230 must selectively collect the 2001 profile remote management 1 data received first and the 2009 profile remote management 2 data thirdly received in order to verify the signature of 2011, and the signature of 2015 In order to verify the data, the secondly received 2005 profile summary information 1 data and the fourth received 2013 profile summary information 2 data must be selectively collected.

21 is, when the profile server 250 transmits profile remote management or profile summary information to the message of the profile server 250 in steps 1603 of FIG. 16 to 1703 of FIG. 17 according to the application of the present invention. , It is a diagram showing a method of creating and attaching a common signature to some of the remote management of each profile and profile summary information data, and specifying the processing order of each data.

Referring to FIG. 21, the profile server 250 may generate 2111 digital signatures for all 2101 profile remote management 1 data and 2109 profile remote management 2 data. In addition, the profile server 250 may generate a digital signature of 2115 for all of the 2105 profile summary information 1 data and the 2113 profile summary information 2 data. Additionally, the profile server 250 may specify the processing order of each data. As an example, in this embodiment, the profile server 250 transmits four data, 2101 profile remote management 1 data is the first of four (1/4), 2105 profile summary information 1 data is the second of four ( 2/4), 2109 profile remote management 2 data can be specified in each data as the third (3/4) of the four, and 2113 profile summary information 2 the fourth of the four (4/4).

As in the case of FIG. 20, it should be noted that the data for which the profile server 250 generates a common signature in the configuration of FIG. 21 is not necessarily limited to data of the same type. In the above configuration, since the profile server 250 can omit the signature for data sharing the signature, the amount of data transmitted from the profile server 250 to the terminal 230 can be reduced. In addition, since the profile server 250 separately specifies the processing order of each data, there is an advantage of being able to freely control the transmission order of data. For example, in the embodiment of FIG. 20, the profile server 250 removes the procedure for selecting and collecting data for signature verification by the terminal 230, and 2101 profile remote management 1 data and 2109 sharing a 2111 signature. Profile remote management 2 data may be placed immediately before 2111 signature, and 2105 profile summary information 1 data and 2113 profile summary information 2 data sharing 2115 signatures may be placed immediately before 2115 signature. At this time, the terminal 230 processes the data in the order of profile remote management 1, profile summary information 1, profile remote management 2, profile summary information 2 in the order of data processing specified by the profile server 250 after signature verification of 2111 and 2115 can do.

It should be noted that the signature generation and data arrangement embodiments of FIGS. 18 to 21 may be used in parallel with the procedures of FIGS. 16 to 17. In this case, the procedure of verifying each signature of FIGS. 18 to 21 may be selectively performed at a necessary time in the procedures of FIGS. 16 to 17. Some of the specific embodiments are as follows, but are not limited to the following embodiments, and may be performed when signature verification is required according to the implementation of the terminal 230.

FIG. 22 illustrates an embodiment of using the signature generation and data arrangement method of FIG. 18 in the procedure of FIG. 17. In this case, descriptions and reference numbers for the above-described procedures in FIGS. 17 and 18 are omitted, and it is assumed that the terminal 230 receives a message in the form of 2290 from the profile server 250 in step 2201. Terminal 230 receives the user consent (End User Consent) in step 2203, verifies the signature of 2205, performs remote profile management 1 in step 2207, verifies the signature of 2209, and profile summary information in step 2211 Receive profile package 1 corresponding to 1, install profile package 1 in step 2213, verify the signature of 2215, perform remote profile management 2 in step 2217, verify the signature of 2219, and verify the profile in step 2221 Profile package 2 corresponding to summary information 2 may be received, and profile package 2 may be installed in step 2223.

23 illustrates another embodiment of the case where the signature generation and data arrangement method of FIG. 18 is used in the procedure of FIG. 16. In this case, descriptions and reference numbers for the above-described procedures in FIGS. 16 and 18 are omitted, and it is assumed that the terminal 230 receives a message in the form of 2290 from the profile server 250 in step 2301. The terminal 23 receives an End User Consent in step 2303, verifies the signature of 2305, receives the profile package 1 corresponding to the profile summary information 1 in step 2307, and verifies the signature of 2309, In step 2311, profile package 2 corresponding to profile summary information 2 is received, the signature of 2313 is verified, profile remote management 1 is performed in step 2315, profile package 1 is installed in step 2317, and the signature of 2319 is verified. And, in step 2321, profile remote management 2 may be performed, and in step 2323, profile package 2 may be installed.

As described above, the verification of the signature among the data received by the terminal 230 can be performed at a time when the terminal 230 is required after receiving the data, so it is performed prior to the procedure for receiving the End User Consent. It could be. As an example, although a separate drawing is not shown, in the case of using the signature generation and data arrangement method of FIG. 21 in the procedure of FIG. 16, the terminal 230 may perform the 2111 signature of FIG. 21 after step 1603 of FIG. And 2115 verifying the signature, and performing steps 1605 and subsequent steps of FIG. 16.

As another example, a separate drawing is not shown, but in the case of using the signature generation and data arrangement method of FIG. 19 in the procedure of FIG. 17, the terminal 230 is The 1903 signature is verified, the 1707 step of FIG. 17 is performed, the 1907 signature of FIG. 19 is verified, the 1709 to 1711 steps of FIG. 17 are performed, the 1911 signature of FIG. 19 is verified, and the FIG. Step 1713 of 17 may be performed, the signature 815 of FIG. 19 may be verified, and steps 1715 to 1717 of FIG. 17 may be performed.

24A, 24B to 26 show that the terminal 230 in the procedure of FIGS. 16 to 17 configures a user interface (UI) to receive an End User Consent in step 1605 or 1705. Various embodiments of the method are shown. In the embodiments corresponding to FIGS. 24A and 24B to 26 to be described later, profile remote management 1 (2710), profile summary information 1 (2730), profile remote management 2 (2750), and profile summary as shown in FIG. 27 Assuming that the data of information 2 (1670) is received, profile 0 is installed and activated in the terminal 230, and profile remote management 1 (2710) is'Profile 0 update (2711)','Profile 0' Inactivation (2713)' includes a remote command, profile summary information 1 (2730) includes data for'profile 1 installation (1631)', and profile remote management 2 (2760) includes'profile 1 update (2751). )','Profile 1 Activation (2753)','Profile 0 Deletion (2755)' remote commands are included, and Profile Summary Information 2 (2770) contains data for'Profile 2 Installation (2771)'. Assume the case.

Referring to FIGS. 24A and 24B, when the terminal 230 receives data as shown in FIG. 27, the terminal 230 provides a user interface in the form of 2401 in FIG. 24A or 2403 in FIG. 24B. Can be printed. In message 2401 or 2403, the terminal 230 may sequentially output all procedures included in the data of FIG. 27 to obtain user consent. The order in which each procedure is output may follow the order in which the terminal 230 receives each procedure or the order in which the terminal 230 processes each procedure. Consent to each procedure may require individual user checks, such as 2401, and may require consent from users who integrate the whole, such as 2403. In addition, although not separately shown in FIGS. 24A and 24B, the terminal 230 additionally displays the name, logo, and service charge of the service provider for the profile subject to each procedure, or separates the user or service provider. A user interface for inputting a password or personal identification number (PIN), etc. can be additionally output.

Referring to FIG. 25, when the terminal 230 receives data as shown in FIG. 27, the terminal 230 may output a user interface such as 2501 to the user. In the 2501 message, the terminal 230 classifies and outputs the procedures included in the data of FIG. 27 for each profile subject to each procedure, and obtains the user's consent. In addition, although not separately shown in FIG. 25, the terminal 230 may request individual user consent for sets of procedures classified for each profile, similar to message 1301 of FIGS. 24A and 24B. In addition, although not separately shown in FIG. 25, the terminal 230 additionally displays the name, logo, service charge, etc. of the service provider for the profile subject to each procedure, or a separate password or password set by the user or the service provider. A user interface for inputting a Personal Identification Number (PIN), etc. can be additionally output.

Referring to FIG. 26, when the terminal 230 receives data as shown in FIG. 27, the terminal 230 may output a user interface such as 1501 to the user. In the 1501 message, the terminal 230 classifies and outputs the procedures included in the data of FIG. 27 by type of each procedure, and obtains the user's consent. Also, although not separately shown in FIG. 26, the terminal 230 may request individual user consent for sets of procedures classified for each type, similar to message 2401 of FIGS. 24A and 24B. In addition, although not separately shown in FIG. 26, the terminal 230 additionally displays the name, logo, service charge, etc. of the service provider for the profile subject to each procedure, or a separate password or password set by the user or the service provider. A user interface for inputting a Personal Identification Number (PIN), etc. can be additionally output.

It should be noted that the user interface corresponding to FIGS. 24A and 24B to 26 may be applied to all embodiments to which FIGS. 16 to 17 are applied. Therefore, it goes without saying that the user interface corresponding to FIGS. 24A and 24B to 26 may be equally applied to a procedure for obtaining user consent in steps 2203 or 2303 of the embodiments of FIGS. 22 to 23.

Meanwhile, FIG. 28 is a diagram illustrating a terminal 2800 according to an embodiment of the present invention.

Referring to FIG. 28, the terminal 2800 may include a transmission/reception unit 2810 and a control unit 2820. In addition, the terminal 2800 may include a UICC 2830. The UICC 2830 may be inserted into the terminal 2800 or may be an eUICC embedded in the terminal 2800.

The transceiving unit 2810 may transmit and receive signals, information, and data.

Meanwhile, the controller 2820 may control the overall operation of the terminal 2800. The controller 2820 may control the overall operation of the terminal 2800 according to the embodiment of the present invention as described above.

In addition, the UICC 2830 may download the profile and install the profile. In addition, the UICC 2830 may manage the profile. The UICC 2830 may operate under the control of the controller 2820. Alternatively, the UICC 2830 may include a processor or controller for installing a profile, or may have an application installed.

Meanwhile, FIG. 29 is a diagram illustrating the components of the server 2900 according to an embodiment of the present invention. For example, the server 2900 may be a profile server.

The server 2900 may include a transmission/reception unit 2910 and a control unit 2920.

The transceiving unit 2910 may transmit and receive signals, information, and data. For example, the transceiving unit 2910 may transmit a profile to the terminal.

Meanwhile, the control unit 2920 is a component for overall control of the server 2900. The controller 2920 may control the overall operation of the server 2900 according to the embodiment of the present invention as described above.

In the specific embodiments of the present invention described above, the constituent elements included in the invention are expressed in the singular or plural according to the presented specific embodiment. However, the singular or plural expression is selected appropriately for the situation presented for convenience of description, and the present invention 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 invention, various modifications are possible without departing from the scope of the present invention. Therefore, the scope of the present invention is limited to the described embodiments and should not be determined, and should be determined by the scope of the claims and equivalents as well as the scope of the claims to be described later.

110: terminal 120: UICC
130: mobile communication network

Claims (20)

In a method performed by a terminal in a wireless communication system,
Transmitting, to a server, a first message related to an operation type requested by the terminal and including first information indicating profile download;
Receiving, from the server, first data for an operation of downloading the profile and a second message including a signature of the server for the first data, based on the first information;
Transmitting, to the server, a third message related to an operation type requested by the terminal and including second information indicating remote profile management (RPM); And
Receiving, from the server, a fourth message including second data for operation of the RPM and a signature of the server for the second data, based on the second information,
Wherein the second data includes an RPM package, and the RPM package includes an RPM command. The method of claim 1,
The first data includes information indicating that the RPM package is pending,
The second data further includes information indicating that another RPM package is waiting. The method of claim 1,
The RPM package includes a plurality of RPM commands including the RPM command based on the priority of the plurality of RPM commands,
The above method,
Receiving the user input that is a combined input for the RPM package as a user input for executing the plurality of RPM commands included in the RPM package; And
And executing an operation based on the user input. The method of claim 3,
If more than one RPM command is waiting in the server, the priority of the more than one RPM command is determined by an operator's request. The method of claim 1,
If more than one profile downloads are waiting on the server, the priority of the more than one profile downloads is determined by an operator's request. In a method performed by a server in a wireless communication system,
Receiving, from a terminal, a first message related to an operation type requested by the terminal and including first information instructing to download a profile;
Transmitting, to the terminal, a second message including first data for the profile download operation and a signature of the server for the first data, based on the first information;
Receiving, from the terminal, a third message related to an operation type requested by the terminal and including second information indicating remote profile management (RPM); And
Transmitting, to the terminal, a fourth message including second data for operation of the RPM and a signature of the server for the second data, based on the second information,
Wherein the second data includes an RPM package, and the RPM package includes an RPM command. The method of claim 6,
The first data includes information indicating that the RPM package is pending,
The second data further includes information indicating that another RPM package is waiting. The method of claim 6,
The RPM package includes a plurality of RPM commands including the RPM command based on the priority of the plurality of RPM commands,
An operation corresponding to the plurality of RPM commands included in the RPM package is performed by a user input executing the plurality of RPM commands, and the user input is a combined input to the RPM package. To do, the way. The method of claim 8,
If more than one RPM command is waiting in the server, the priority of the more than one RPM command is determined by an operator's request. The method of claim 6,
If more than one profile downloads are waiting on the server, the priority of the more than one profile downloads is determined by an operator's request. In the terminal of the wireless communication system,
A transmission/reception unit; And
Including a control unit,
The control unit:
To the server, transmits a first message including first information related to an operation type requested by the terminal and instructing to download a profile,
Receiving, from the server, a second message including first data for an operation of downloading the profile and a signature of the server for the first data, based on the first information,
To the server, transmits a third message including second information related to an operation type requested by the terminal and indicating a remote profile management (RPM),
It is set to receive, from the server, a fourth message including second data for operation of the RPM and a signature of the server for the second data, based on the second information,
The second data includes an RPM package, and the RPM package includes an RPM command. The method of claim 11,
The first data includes information indicating that the RPM package is pending,
The second data further includes information indicating that another RPM package is waiting. The method of claim 11,
The RPM package includes a plurality of RPM commands including the RPM command based on the priority of the plurality of RPM commands,
The control unit:
As a user input for executing the plurality of RPM commands included in the RPM package, receiving the user input, which is a combined input for the RPM package,
The terminal, characterized in that further configured to execute an operation based on the user input. The method of claim 13,
If more than one RPM command is waiting in the server, the priority of the more than one RPM command is determined by an operator's request. The method of claim 11,
If more than one profile downloads are waiting in the server, the priority of the more than one profile downloads is determined by an operator's request. In the server of the wireless communication system,
A transmission/reception unit; And
Including a control unit,
The control unit:
Receiving from a terminal, a first message including first information related to an operation type requested by the terminal and instructing to download a profile,
To the terminal, first data for the profile download operation and a second message including a signature of the server for the first data are transmitted based on the first information,
Receiving, from the terminal, a third message including second information related to an operation type requested by the terminal and indicating a remote profile management (RPM),
It is configured to transmit, to the terminal, a fourth message including second data for operation of the RPM and a signature of the server for the second data, based on the second information,
The second data includes an RPM package, and the RPM package includes an RPM command. The method of claim 16,
The first data includes information indicating that the RPM package is pending,
The second data further includes information indicating that another RPM package is waiting. The method of claim 16,
The RPM package includes a plurality of RPM commands including the RPM command based on the priority of the plurality of RPM commands,
An operation corresponding to the plurality of RPM commands included in the RPM package is performed by a user input executing the plurality of RPM commands, and the user input is a combined input to the RPM package. As a server. The method of claim 18,
If more than one RPM command is waiting in the server, the priority of the more than one RPM command is determined by an operator's request. The method of claim 16,
If more than one profile downloads are waiting in the server, the priority of the more than one profile downloads is determined by an operator's request.

Images