KR20220153456A - APPARATUS AND METHOD FOR PROCESSING PROFILE DELETE NOTIFICATION WHILE CHANGING eUICC DEVICES - Google Patents

Abstract

The present disclosure relates to a communication technique and a system thereof, which converge a 5G communication system for supporting a higher data rate after a 4G system with IoT technology. The present disclosure provides intelligent services based on 5G communication technology and IoT-related technology (e.g., smart home, smart building, smart city, smart car or connected car, health care, digital education, retail, security and safety related service, etc.). The present disclosure relates to a method and apparatus for reinstalling a profile when changing an eUICC terminal, wherein a terminal that manages a profile for network connection using an eUICC in a wireless communication system according to one embodiment comprises: a transceiver; and at least one processer that receives a request to move the profile from a user, checks profile movement information, sends a message requesting an activation code to a profile server, receives the activation code and necessity of profile deletion from the profile server, deletes the profile, sends a deletion result of the profile to the profile server, forwards the activation code to another terminal, receives the activation code from another terminal, sends a message requesting a profile to a profile server using the activation code, receives a profile package from the profile server, and controls the terminal to install the profile package. According to one embodiment, provided is a method for a terminal to select a communication service and connect to a network in a communication system.

Description

Method and device for confirming profile deletion when changing eUICC terminal

The present invention relates to a method and apparatus for installing and managing an eUICC profile.

Efforts are being made to develop an improved 5G communication system or pre-5G communication system to meet the growing demand for wireless data traffic after the commercialization of the 4G communication system. For this reason, the 5G communication system or pre-5G communication system is being called a system after the 4G network (Beyond 4G Network) communication system or LTE system (Post LTE). In order to achieve a high data rate, the 5G communication system is being considered for implementation in a mmWave band (eg, a 60 gigabyte (60 GHz) band). In order to mitigate the path loss of radio waves and increase the propagation distance of radio waves in the ultra-high frequency band, beamforming, massive MIMO, and full dimensional MIMO (FD-MIMO) are used in 5G communication systems. ), array antenna, analog beam-forming, and large scale antenna technologies are being discussed. In addition, to improve the network of the system, in the 5G communication system, an evolved small cell, an advanced small cell, a cloud radio access network (cloud RAN), and an ultra-dense network , device to device communication (D2D), wireless backhaul, moving network, cooperative communication, coordinated multi-points (CoMP), and interference cancellation etc. are being developed. In addition, in the 5G system, FQAM (hybrid FSK and QAM modulation) and SWSC (sliding window superposition coding), which are advanced coding modulation (ACM) methods, and advanced access technologies such as FBMC (filter bank multi carrier) and NOMA (non-orthogonal multiple access) and SCMA (sparse code multiple access) are being developed.

On the other hand, the Internet is evolving from a human-centered connection network in which humans create and consume information to an Internet of Things (IoT) network in which information is exchanged and processed between distributed components such as objects. IoE (internet of everything) technology, in which IoT technology is combined with big data processing technology through connection with a cloud server, etc., is also emerging. In order to implement IoT, technology elements such as sensing technology, wired/wireless communication and network infrastructure, service interface technology, and security technology are required, and recently, sensor networks for connection between objects and machine to machine , M2M), and machine type communication (MTC) technologies are being studied. In the IoT environment, intelligent IT (internet technology) services that create new values in human life by collecting and analyzing data generated from connected objects can be provided. IoT is a field of smart home, smart building, smart city, smart car or connected car, smart grid, health care, smart home appliances, advanced medical service, etc. can be applied to

Accordingly, various attempts are being made to apply the 5G communication system to the IoT network. For example, 5G communication technologies such as sensor networks, machine-to-machine communication, and MTC are implemented by techniques such as beamforming, MIMO, and array antennas. The application of the cloud radio access network (cloud RAN) as the big data processing technology described above can be said to be an example of convergence of 5G technology and IoT technology.

As described above, as a variety of services can be provided according to the development of mobile communication systems, a method for effectively providing these services is required.

"UICC (Universal Integrated Circuit Card)" is a smart card used by inserting into a mobile communication terminal, etc., and is also referred to as a UICC card. The UICC may include an access control module for a terminal to access a network of a mobile communication service provider. Examples of such access control modules include Universal Subscriber Identity Module (USIM), Subscriber Identity Module (SIM), and IP Multimedia Service Identity Module (ISIM). A UICC including a USIM is also commonly referred to as a USIM card. Similarly, a UICC including a SIM module is also commonly referred to as a SIM card.

Among UICC cards, a UICC that is fixed to a terminal and used is called an embedded UICC (eUICC). Typically, an eUICC refers to a UICC card that is fixed to a terminal and can remotely download and select a SIM module. In addition, the SIM module information to be downloaded is collectively referred to as an eUICC profile or, more simply, a profile.

An object of the present invention is to effectively provide a service in a mobile communication system.

According to one embodiment disclosed in the present invention, it is possible to provide a method and apparatus for a terminal to connect to a network by selecting a communication service in a communication system.

According to one embodiment disclosed in the present invention, it is possible to provide a method and apparatus for downloading, installing, and managing a profile for a terminal to connect to a network in a communication system online.

According to an embodiment disclosed in the present invention, it is possible to provide a method and apparatus for efficiently re-downloading a profile installed by a terminal to connect to a network to another terminal in a communication system.

The present invention for solving the above problems is a control signal processing method in a wireless communication system, comprising: receiving a first control signal transmitted from a base station; processing the received first control signal; and transmitting a second control signal generated based on the processing to the base station.

In addition, a terminal for managing a profile for connecting to a network using an embedded universal integrated circuit card (eUICC) in a wireless communication system according to an embodiment of the present invention includes: a transceiver; and receives a request for moving the profile from the user, checks profile migration information, sends a message requesting an activation code to the profile server, and determines whether the profile server needs to delete the activation code and profile and optionally the result of profile deletion. Receives whether or not it can be transmitted through another terminal and the profile deletion result processing address, deletes the profile, sends the profile deletion result to the profile server, and optionally sends the profile deletion result to the activation code transmitted from the server. Combining all or part of the activation code, transmitting the activation code to another terminal, receiving the activation code from the other terminal, and using the activation code to send a message requesting a profile to a profile server, Optionally, at least one processor may include a profile deletion result in a profile request message, receive a profile package from the profile server, and control the terminal to install the profile package.

In a wireless communication system according to an embodiment, a profile server providing a terminal with a profile for network connection includes: a transceiver; and receiving a movement request message of the profile from the terminal, determining whether the profile is movable, generating an activation code capable of downloading the profile or a new profile, and displaying a state of the profile when the profile is movable. Set to a non-downloadable state, set the state of the new profile to a downloadable state when the profile cannot be moved, and determine whether the activation code and profile deletion are necessary and optionally transmitted through another terminal to the terminal. Transmits a message including whether the profile deletion result can be processed and the profile deletion result processing address, receives the profile deletion result from the terminal, changes the profile to a downloadable state, and downloads the profile from the terminal Receives a request message, determines whether the profile is in a downloadable state, transmits a profile package to the terminal if the profile is in a downloadable state, and transmits an error code or downloads the profile if the profile is in a downloadable state It may include at least one processor that controls the profile server to verify the profile deletion result included in the request and transmit an error code if the profile deletion result does not exist or the verification fails.

According to an embodiment of the present invention, a service can be effectively provided in a mobile communication system.

According to an embodiment of the present invention, when a terminal in a communication system intends to reinstall a profile installed in the terminal to another terminal, the activation code required for reinstallation of the profile is reissued from the profile server or the activation code necessary for reinstallation of the profile is received. Extract from the information stored in the terminal or profile, delete the profile to be moved first if necessary, deliver the profile deletion proof that can prove the profile deletion to the server, include the profile deletion proof in the activation code if necessary, and enter the activation code By transmitting to other terminals, the other terminals can efficiently download and install the profile from the profile server.

According to an embodiment of the present invention, when a profile server in a communication system receives a request from a terminal to re-install a profile installed in the terminal to another terminal, if the profile can be reused, the profile is set to a state in which download is not possible, and the terminal request deletion of the profile, request delivery of proof of profile deletion if necessary, prepare other profiles by setting them in a downloadable state if reuse of the profile is not possible, generate an activation code to download the prepared profile, , If the terminal deletes the profile, it is changed to a state in which the profile can be downloaded, thereby preventing the copying of the profile and processing the profile download safely.

1 is a diagram illustrating a method in which a terminal connects to a mobile communication network using a UICC (Universal Integrated Circuit Card) loaded with a fixed profile according to an embodiment of the present disclosure.
2 is a diagram illustrating a configuration of a system in which a terminal manages a profile installed in a first terminal according to a user's input and installs the profile in a second terminal according to an embodiment of the present disclosure.
3 is a diagram illustrating a procedure in which a first terminal receives an activation code through a profile server and transfers it to a second terminal to download a profile according to an embodiment of the present disclosure.
4 is a diagram illustrating a procedure of downloading a profile by a first terminal transferring an activation code stored in the first terminal to a second terminal according to an embodiment of the present disclosure.
5 is a block diagram illustrating components of a terminal according to an embodiment of the present disclosure.
6 is a block diagram illustrating components of a profile server according to an embodiment of the present disclosure.

Hereinafter, embodiments of the present disclosure 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 disclosure pertains and are not directly related to the present disclosure will be omitted. This is to more clearly convey the gist of the present disclosure without obscuring it by omitting unnecessary description.

For the same reason, in the accompanying drawings, some components are exaggerated, omitted, or schematically illustrated. Also, the size of each component does not entirely reflect the actual size. In each figure, the same reference number is assigned to the same or corresponding component.

Advantages and features of the present disclosure, and methods of achieving them, will become clear with reference to the embodiments described below in detail in conjunction with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below and may be implemented in various different forms, only the present embodiments make the disclosure of the present disclosure complete, and common knowledge in the art to which the present disclosure belongs. It is provided to fully inform the person who has the scope of the disclosure, and the disclosure is only defined by the scope of the claims. Like reference numbers designate like elements throughout the disclosure.

At this time, it will be understood that each block of the process flow chart diagrams and combinations of the flow chart diagrams can be performed by computer program instructions. These computer program instructions may be embodied in a processor of a general purpose computer, special purpose computer, or other programmable data processing equipment, so that the instructions executed by the processor of the computer or other programmable data processing equipment are described in the flowchart block(s). It creates means to perform functions. These computer program instructions may also be stored on a computer usable or computer readable storage medium that can be directed to a computer or other programmable data processing equipment to implement functionality in a particular way, such that the computer usable or computer readable The instructions stored on the storage medium are also capable of producing an article of manufacture containing instruction means for performing the functions described in the flowchart block(s). The computer program instructions can also be loaded on a computer or other programmable data processing equipment, so that a series of operational steps are performed on the computer or other programmable data processing equipment to create a computer-executed process to generate computer or other programmable data processing equipment. Instructions for performing processing equipment may also provide steps for performing the functions described in the flowchart block(s).

Additionally, each block may represent a module, segment, or portion of code that includes one or more executable instructions for executing specified logical function(s). It should also be noted that in some alternative implementations it is possible for the functions mentioned in the blocks to occur out of order. For example, two blocks shown in succession may in fact be executed substantially concurrently, or the blocks may sometimes be executed in reverse order depending on their function.

At this time, the term '~unit' used in this embodiment means software or a hardware component such as FPGA or ASIC, and '~unit' performs certain roles. However, '~ part' is not limited to software or hardware. '~ unit' may be configured to be in an addressable storage medium or configured to reproduce one or more processors. Therefore, as an example, '~unit' refers to components such as software components, object-oriented software components, class components, and task components, processes, functions, properties, and procedures. , subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, databases, data structures, tables, arrays, and variables. Functions provided within components and '~units' may be combined into smaller numbers of components and '~units' or further separated into additional components and '~units'. In addition, components and '~units' may be implemented to play one or more CPUs in a device or a secure multimedia card.

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

In the present disclosure, "UICC (Universal Integrated Circuit Card)" is a smart card used by inserting into a mobile communication terminal, etc., and is also called a UICC card.

UICC stores personal information such as network access authentication information, phonebook, SMS of mobile communication subscribers, and performs subscriber authentication and traffic security key generation when accessing mobile communication networks such as GSM, WCDMA, LTE, etc. to ensure safe mobile communication use. It means the chip that makes it possible.

The UICC may include a communication application or an access control module for a terminal to access a network of a mobile communication service provider. Examples of such communication applications or access control modules include Universal Subscriber Identity Module (USIM), Subscriber Identity Module (SIM), and IP Multimedia Service Identity Module (ISIM). In addition, the UICC can provide a high-level security function for loading various applications such as electronic wallet, ticketing, and electronic passport.

A UICC including a USIM is also commonly referred to as a USIM card. Similarly, a UICC including a SIM module is also commonly referred to as a SIM card.

In the present disclosure, "SIM card", "UICC card", "USIM card", and "UICC with ISIM" may be used in the same meaning. That is, the contents of the present disclosure may be equally applied to a SIM card, 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 to enable safe mobile communication use.

In general, a SIM card is manufactured as a dedicated card for a corresponding operator at the request of a specific mobile communication operator, and authentication information for network access of the operator, for example, USIM (Universal Subscriber Identity Module) application and IMSI (International Mobile Subscriber Identity), K value, OPc value, etc. are preloaded on the card and shipped. Therefore, the SIM card is delivered to the subscriber by the mobile communication operator, and then, if necessary, management such as installation, modification, and deletion of applications in the UICC can be performed by utilizing technologies such as OTA (Over The Air). Subscribers can use the mobile communication operator's network and application services by inserting a UICC card into their mobile communication terminal, and when replacing a terminal, by moving and inserting the UICC card from the existing terminal to a new terminal, authentication information stored in the UICC card, mobile communication Communication phone numbers, personal phone books, etc. can be used as they are in the new terminal.

However, SIM cards are inconvenient for mobile communication terminal users to receive services from other mobile communication operators. A user of a mobile communication terminal has the inconvenience of physically obtaining 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 to receive local mobile communication service. The roaming service solves some of the inconveniences, but the charges are relatively high, and there is a problem that the service cannot be received if there is no contract between telecommunication companies.

On the other hand, if the SIM module is remotely downloaded and installed on the UICC card, this inconvenience can be largely solved. That is, the SIM module of the mobile communication service to be used can be downloaded to the UICC card at a time desired by the user. Such a UICC card may be used by downloading and installing a plurality of SIM modules and selecting only one SIM module among them. This UICC card may or may not be fixed to the terminal. In particular, a UICC that is fixed to a terminal and used is called an eUICC (embedded UICC). In general, an eUICC refers to a UICC card that is fixed to a terminal and can remotely download and select a SIM module. In the present disclosure, a UICC card capable of remotely downloading and selecting a SIM module is referred to as an eUICC. That is, among UICC cards that can download and select a SIM module remotely, UICC cards that are fixed or not fixed to the terminal are collectively referred to as eUICC. In addition, the downloaded SIM module information is collectively referred to as an eUICC profile or, more simply, a profile.

In the present disclosure, “eUICC (embedded UICC)” is a non-detachable security module in the form of a chip embedded in a terminal that can be inserted into and removed from a terminal. eUICC can download and install profiles using OTA (Over The Air) technology. An eUICC can be named as a UICC capable of downloading and installing profiles.

In the present disclosure, the method of downloading and installing a profile to an eUICC using OTA technology can also be applied to a detachable UICC that can be inserted into and removed from a terminal. That is, the embodiment of the present disclosure can be applied to a UICC that can download and install a profile using OTA technology.

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

In the present disclosure, "profile" may mean that an application, a file system, an authentication key value, etc. stored in the UICC are packaged in a software form.

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

In the present disclosure, an operation of enabling a terminal to enable a profile means an operation of setting the terminal to receive a communication service through a communication service provider that provided the corresponding profile by changing the state of the corresponding profile to enabled. can do. A profile in an active state may be expressed as an “enabled profile”.

In the present disclosure, an operation of disabling a profile by a terminal means an operation of changing the state of a corresponding profile to a disabled state so that the terminal cannot receive communication services through a communication service provider that provided the corresponding profile. can do. A profile in a deactivated state may be expressed as a “disabled profile”.

In the present disclosure, an operation of deleting a profile by a terminal may mean an operation of changing the state of a corresponding profile to a deleted state so that the terminal cannot activate or deactivate the profile any more. . A profile in a deleted state may be expressed as a “deleted profile”.

In the present disclosure, an operation of enabling, disabling, or deleting a profile by a terminal sets the status of each profile to enabled, disabled, or deleted. Instead of changing immediately, each profile is first marked as to be enabled, to be disabled, or to be deleted, and the UICC of the terminal or terminal Changes each profile to enabled, disabled, or deleted after performing a specific operation (eg, performing a REFRESH or RESET command) It can also mean an action. The action of marking a specific profile as intended (i.e., to be enabled, to be disabled, or to be deleted) must be performed for one profile. It is not limited to displaying the scheduled status of, respectively, displaying one or more profiles with the same or different scheduled status, displaying one profile with one or more scheduled statuses, or displaying one or more profiles with one or more scheduled statuses, respectively, which are the same or different from each other. It is also possible to display status.

In addition, when the terminal displays one or more scheduled statuses for a certain profile, the two scheduled status indications may be integrated into one. For example, if a certain profile is marked as to be disabled and to be deleted, the profile may be collectively marked as to be disabled and deleted. .

In addition, the operation of displaying the expected status of one or more profiles by the terminal may be performed sequentially or simultaneously. In addition, an operation in which the terminal displays the expected state for one or more profiles and then changes the state of the actual profile may be performed sequentially or simultaneously.

In the present disclosure, the "profile providing server" may include a function of creating a profile, encrypting the created profile, generating a profile remote management command, or encrypting the generated profile remote management command. The profile providing server is 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 provider (Profile Provisioner, PP) , Profile Provider, PPC holder (Profile Provisioning Credentials holder).

In the present disclosure, a "profile management server" may include a function of managing a profile. 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), PP (Profile Manager), etc.

In the present disclosure, a profile providing server may mean a combination of functions of a profile management server. Accordingly, in various embodiments of the present disclosure, the operation of the profile providing server may be performed in the profile management server. Similarly, the operation of the profile management server or SM-SR may be performed in the profile providing server.

In the present disclosure, "opening mediation server" can be expressed as SM-DS (Subscription Manager Discovery Service), DS (Discovery Service), root opening mediation server (Root SM-DS), alternative opening mediation server (Alternative SM-DS) have. The opening mediation server may receive an event registration request (Register Event Request, Event Register Request) from one or more profile providing servers or opening mediation servers. In addition, one or more opening mediation servers may be used in combination. In this case, the first opening mediation server may receive an event registration request from the second opening mediation server as well as the profile providing server.

In the present disclosure, the profile providing server and the opening brokerage server may be used as a 'RSP (Remote SIM Provisioning) server'. The RSP server can be represented by SM-XX (Subscription Manager XX).

In the present disclosure, 'terminal' refers to a mobile station (MS), a user equipment (UE), a user terminal (UT), a wireless terminal, an access terminal (AT), a terminal, a subscriber unit, and 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. In one embodiment, the terminal is such as a cellular phone, a smart phone having a wireless communication function, a personal digital assistant (PDA) having a wireless communication function, a wireless modem, a portable computer having a wireless communication function, and a digital camera having a wireless communication function. It may include a photographing device, a gaming device having a wireless communication function, a music storage and reproducing home appliance having a wireless communication function, an Internet home appliance capable of wireless Internet access and browsing, as well as portable units or terminals incorporating combinations of such functions. can In addition, the terminal may include a machine to machine (M2M) terminal and a machine type communication (MTC) terminal/device, but is not limited thereto. In the present disclosure, a terminal may also be referred to as an electronic device.

In the present disclosure, an "electronic device" may have a built-in UICC capable of downloading and installing 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, the UICC in the form of a card can be inserted into an electronic device. The electronic device may include a terminal, and in this case, the terminal may be a terminal including a UICC capable of downloading and installing a profile. The UICC can be embedded in the terminal, and when the terminal and the UICC are separated, the UICC can be inserted into the terminal or inserted into the terminal and connected to the terminal. A UICC that can be installed by downloading a profile may be referred to as an eUICC, for example.

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

In the present disclosure, "profile identifier" means profile identifier (Profile ID), ICCID (Integrated Circuit Card ID), Matching ID, event identifier (Event ID), activation code (Activation Code), activation code token (Activation Code Token), command Matches Command Code, Command Code Token, Signed Command Code, Unsigned Command Code, ISD-P or Profile Domain (PD) It can be referred to as a factor that becomes. The profile identifier (Profile ID) may indicate a unique identifier of each profile. The profile identifier may further include the address of the profile providing server (SM-DP+) capable of indexing the profile. Also, the profile identifier may further include the signature of the profile providing server (SM-DP+).

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

In the present disclosure, a "profile container" may be referred to as a profile domain. A profile container may be a security domain.

In the present disclosure, "application protocol data unit (APDU)" may be a message for a UE to interwork with an eUICC. In addition, the APDU may be a message for a Profile Provider (PP) or a Profile Manager (PM) to interoperate with the eUICC.

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

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

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

In the present disclosure, an “event” may be a collective term for profile download, remote profile management, or other profile or eUICC management/processing commands. An event may be named a remote SIM provisioning operation (or RSP operation, or RSP operation) or an event record, and each event is a corresponding event identifier (Event Identifier). , Event ID, EventID) or matching identifier (Matching Identifier, Matching ID, MatchingID) and the address (FQDN, IP Address, or URL), the signature of the profile providing server (SM-DP+) or opening brokerage server (SM-DS), and at least one digital certificate of the profile providing server (SM-DP+) or opening brokerage server (SM-DS) It can be referred to as data that

Data corresponding to an event may be referred to as a “command code”. Part or all of the procedure using the command code may be referred to as "command code processing procedure" or "command code procedure" or "LPA API (Local Profile Assistant Application Programming Interface)". Profile Download can be used interchangeably with Profile Installation.

In addition, "Event Type" is a term that indicates whether a specific event is a profile download, remote profile management (eg, deletion, activation, deactivation, replacement, update, etc.), or other profile or eUICC management/processing commands. It can be used and can be named as operation type (Operation Type or OperationType), operation classification (Operation Class or OperationClass), event request type (Event Request Type), event classification (Event Class), event request classification (Event Request Class), etc. can An arbitrary event identifier (EventID or MatchingID) may indicate a path through which the terminal acquired the corresponding event identifier (EventID or MatchingID) or a purpose of use (EventID Source or MatchingID Source).

In the present disclosure, “profile package” may be used interchangeably with a profile or used as a term indicating a data object of a specific profile, and may be named Profile TLV or Profile Package TLV (Profile Package TLV). If the profile package is encrypted using an encryption parameter, it may be named a Protected Profile Package (PPP) or a Protected Profile Package TLV (PPP TLV). If the profile package is encrypted using encryption parameters that can only be decrypted by a specific eUICC, it may be named a bound profile package (BPP) or a bound profile package TLV (BPP TLV). The profile package TLV may be a data set expressing information constituting a profile in a tag, length, value (TLV) format.

In the present disclosure, "Local Profile Management (LPM)" refers to Profile Local Management, Local Management, Local Management Command, Local Command, and Local Profile. It can be named as LPM Package, Profile Local Management Package, LOCAL MANAGEMENT PACKAGE, Local Management Command Package, and Local Command Package. have. LPM changes the state (Enabled, Disabled, Deleted) of a specific profile through software installed on the terminal, or the contents of a specific profile (eg, Profile Nickname, Profile Metadata, etc.) ) can be used for updating. The LPM may include one or more local management commands, and in this case, the target profile of each local management command may be the same or different for each local management command.

In the present disclosure, "Remote Profile Management (RPM)" refers to Profile Remote Management, Remote Management, Remote Management Command, Remote Command, and Remote Profile. It can be named as RPM Package, Profile Remote Management Package, Remote Management Package, Remote Management Command Package, or Remote Command Package. have. RPM changes (updates) the status (Enabled, Disabled, Deleted) of a specific profile or changes (updates) the contents of a specific profile (eg, Profile Nickname, Profile Metadata, etc.) can be used for purposes. RPM may include one or more remote management commands, and in this case, the target profile of each remote management command may be the same or different for each remote management command.

In the present disclosure, a "certificate" or "digital certificate" refers to a mutual key based on an asymmetric key composed of a pair of a public key (PK) and a secret key (SK). It may indicate a digital certificate used for authentication (Mutual Authentication). Each certificate includes one or more public keys (Public Keys, PKs), a Public Key Identifier (PKID) corresponding to each public key, and an identifier of the Certificate Issuer (CI) that issued the corresponding certificate. (Certificate Issuer ID) and digital signature (Digital Signature).

In addition, "Certificate Issuer" may be named as Certification Issuer, Certificate Authority (CA), Certification Authority, and the like.

In the present disclosure, "Public Key (PK)" and "Public Key ID (PKID)" refer to a specific public key or a certificate including the corresponding public key, or a part of a specific public key or a corresponding public key. A part of the included certificate, or the calculated result (e.g., hash) value of a specific public key, or the calculated value (e.g., hash) of a certificate that includes the public key, or a specific public key Refers to a storage space in which data are stored, for example, the calculation result (eg, hash) value of a part of a key or the calculation result (eg, hash) value of a part of a certificate including a corresponding public key. can be used interchangeably with the same meaning.

In this disclosure, certificates (primary certificates) issued by one certificate issuer are used to issue other certificates (secondary certificates), or secondary certificates are used to issue tertiary or more certificates in conjunction. In this case, the correlation between the corresponding certificates can be named as Certificate Chain or Certificate Hierarchy, and in this case, the CI certificate used to issue the first certificate is the Root of Certificate , Root CI, Root CI Certificate, Root CA, Root CA Certificate, etc.

In the present disclosure, "mobile operator" may represent a business that provides communication services to terminals, and includes a business supporting system (BSS), an operational supporting system (OSS), It can collectively refer to a POS terminal (point of sale terminal) and other IT systems. In addition, in the present disclosure, a communication service provider is not limited to expressing only one specific business providing communication services, but a term that refers to a group or association or consortium of one or more businesses or a representative representing the group or association. may also be used as In addition, in the present disclosure, a telecommunications operator is an operator (operator, OP, or Op.), a mobile network operator (MNO), a mobile virtual network operator (MVNO), and a service provider (service provider or SP) , profile owner (PO), etc., and each communication service provider may set or be assigned at least one name and/or unique identifier (object identifier: OID) of the communication service provider. If a telecommunications carrier refers to a group of more than one entity or entity or agency, the name or unique identifier of any group or entity or entity shall be shared by all entities belonging to, or collaborating with, that group or entity. name or unique identifier.

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

In the present disclosure, "K" is an encryption key value stored in the eUICC used in the AKA authentication algorithm.

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

In the present disclosure, "NAA" is a Network Access Application (Network Access Application) application program, and may be an application program such as USIM or ISIM stored in the UICC to access a network. NAA may be a network access module.

In the present disclosure, an “indicator” may be used to express that a certain function, setting, or operation is required or not required, or may be used to express the corresponding function, setting, or operation itself. In addition, in the present disclosure, a marker is expressed in various forms such as a string or an alphanumeric string, a true/false operator (boolean - TRUE or FALSE), a bitmap, an array, a flag, and the like. may be used, and other expressions having the same meaning may be used interchangeably.

Hereinafter, a method and apparatus for installing and managing an eUICC profile of the present disclosure will be described with reference to FIGS. 1 to 6.

1 is a diagram illustrating a mobile communication network connection method of a terminal using a UICC in which a fixed profile is loaded in the terminal according to an embodiment of the present disclosure.

As shown in FIG. 1 , the UICC 120 may be inserted into the terminal 110 . For example, the UICC 120 may be removable or pre-embedded in a terminal.

The fixed profile of the UICC loaded with the fixed profile means that 'access information' that can access a specific carrier is fixed. For example, the access information may be a K or Ki value required to authenticate to the network together with IMSI, which is a subscriber identifier, and subscriber identifier.

The terminal 110 according to various embodiments may perform authentication with a mobile communication service provider's authentication processing system (eg, home location register (HLR) or AuC) using the UICC 120 . For example, the authentication process may be an Authentication and Key Agreement (AKA) process. If the authentication is successful, the terminal can use a mobile communication service such as a phone call or mobile data using the mobile communication company network 130 of the mobile communication system.

2 is a diagram illustrating a configuration of a system in which a terminal manages a profile installed in a first terminal according to a user's input and installs the profile in a second terminal according to an embodiment of the present disclosure.

As shown in FIG. 2 , eSIMs 211 and 221 are mounted on the terminals 210 and 220, and profiles (not shown) may be installed on the eSIMs 211 and 221. In addition, LPAs 212 and 222 may be installed in the terminals 210 and 220 . The eSIMs 211 and 221 may be controlled by the LPAs 212 and 222 . The user 200 may control the profiles installed in the eSIMs 211 and 221 of each terminal through the LPAs 212 and 222 .

The user 200 may receive a communication service from a service provider (hereinafter referred to as “communication service provider” or “business operator” 250). To this end, a profile (not shown) of the operator 250 may be installed in the first terminal 210 . The user 200 may, for example, attempt to re-install the profile installed on the first terminal 210 on the second terminal 220 when the second terminal 220 is newly purchased.

The operator 250 is connected to the first profile server 230 and the second profile server 240, the LPA 212 of the first terminal 210 is connected to the first profile server 230, and The LPA 222 of the second terminal 220 may be connected to the second profile server 240 . At this time, the first profile server 230 and the second profile server 240 may be the same as or different from each other. In addition, when one or more operator servers are included in the configuration, each operator server may be connected to each separate profile server, or at least one operator server may be connected to the same profile server. In addition, although FIG. 2 shows a case where each of the profile servers 230 and 240 is configured as a single server for convenience, one or more profile servers (SM-DP+) may be included in the server configuration according to implementations and embodiments, and a specific profile One or more open mediation servers (SM-DS) that assist in creating a connection between the server and the terminal may be included in the server configuration. It should be noted that the configuration of various servers as described above may be simply indicated as a single profile server in the drawings below.

Detailed operation and A message exchange procedure will be described in detail with reference to drawings to be described later.

3 is a diagram illustrating a procedure in which a first terminal receives an activation code through a profile server and transfers it to a second terminal to download a profile according to an embodiment of the present disclosure.

In FIG. 3 , configuration and description of the user 200 , the first terminal 210 , the second terminal 220 , the profile server 230 , and the operator 250 will be referred to FIG. 2 . For example, the user 200, the first terminal 210, the second terminal 220, the profile server 230, and the business operator 250 are the user 200, the first terminal 210, It may correspond to the second terminal 220, the first profile server 230, and the operator 250. In addition, the notification receiving server (300, Notification Receiver) is a server to which the profile deletion result of the first terminal 210 is to be delivered, verifies the result, and can deliver the verification result to the business operator 250 and the profile server 230. have. In addition, although FIG. 3 shows one notification receiving server 300 for convenience of drawing, the notification receiving server 300 includes a profile server 230 and another profile server (eg, the second profile server in FIG. 2). (240) or a third profile server (not shown in the figure) may be at least one.

Referring to FIG. 3 , in step 301, the user 200 may request the first terminal 210 to transfer the first profile. To this end, the user 200 can check information on the first profile (profile metadata) and information that a user who intends to move the first profile should be aware of through the first terminal 210 . Information about the first profile and information to be noted by a user who wants to move the first profile may be stored in the first terminal 210 or the first profile.

Information on the first profile may include, for example, the name or logo of the operator 250, a profile policy, and the like. Information to be noted by the user who intends to move the first profile may include, for example, the remaining number of profile movements permitted by the business operator 250 or the cost the user must pay for profile movement.

Also, in the first terminal 210 or the first profile, at least one address of a profile server to be accessed by the terminal to move the profile may be stored. A profile server that the terminal must access to move the profile may be, for example, the profile server 230 .

In step 303, the first terminal 210 may request the profile server 230 to move the first profile. Step 303 uses, for example, at least one of an initiate authentication message, a terminal authentication request message, and a transfer request message, and/or a device change. ) or by further transmitting an operation type set as a transfer profile. The procedure of requesting the movement of the first profile in step 303 may include transmitting at least a profile identifier (ICCID) of the first profile.

In addition, the first terminal 210 may deliver a certificate that can be used for mutual authentication between the profile server 230 and the eSIM 211 mounted on the first terminal 210 in step 303, and the certificate hierarchy structure of the corresponding certificate At least one of the above certificates may be selectively delivered. The certificate may be the certificate of the eSIM 211 shown in FIG. 2 mounted in the first terminal 210 . Also, in step 303, the first terminal 210 uses a part or all of the data transmitted when requesting the movement of the first profile and the private key paired with the public key included in the certificate of the eSIM 211 to generate the generated data. It can be delivered with a digital signature.

In step 305, the profile server 230 and the operator 250 may check the possibility of moving the first profile. If the first profile can be moved to another terminal, the profile server 230 and the operator 250 can prepare for reuse of the first profile. At this time, the prepared first profile may be set to a state in which download is not yet possible in order to prevent the profile from being duplicated. Step 305 is, for example, a download order message, a confirm order message, a remote management order message, a release order message, or a handle notification. ) It may be performed using at least one or more of

In step 305, the profile server 230 and the business operator 250 further generate, if necessary, some or all of information about the first profile (profile metadata) and/or information that the user who wants to move the first profile should be aware of. or can be changed. Information on the first profile may include, for example, the name or logo of the operator 250, a profile policy, and the like. Information to be noted by the user who intends to move the first profile may include, for example, the remaining number of profile movements permitted by the business operator 250 or the cost the user must pay for profile movement.

In addition, the profile server 230 and the operator 250 may further generate an activation code for downloading the first profile again. The activation code may include at least the address of the profile server 230 where the first profile is stored and an event identifier (MatchingID) connected to the first profile. Although the first profile is represented as being stored in the profile server 230 for convenience in the drawing, the first profile may be stored in a profile server different from the profile server 230 . For example, the second profile server 240 of FIG. 2 may be used.

In step 305, if the first profile cannot be moved to another terminal, the profile server 230 and the operator 250 may prepare a new second profile. Step 305 is, for example, a download order message, a confirm order message, a remote management order message, a release order message, or a handle notification. ) It may be performed using at least one or more of

In step 305, the profile server 230 and the business operator 250, if necessary, inform the user who wants to move the profile information (profile metadata), the information about the second profile (profile metadata), and/or the first profile. Some or all of the information to be done can be further created or changed. The information on the first profile or the information on the second profile may include, for example, the name or logo of the operator 250 that provided each profile, a profile policy, and the like. Information to be noted by the user who intends to move the first profile may include, for example, the remaining number of profile movements permitted by the business operator 250 or the cost the user must pay for profile movement.

In addition, the first profile server 230 and the operator 250 may further generate an activation code for downloading the prepared second profile. The activation code may include at least the address of the profile server 230 where the second profile is stored and an event identifier (MatchingID) connected to the second profile. Although the second profile is represented as being stored in the profile server 230 for convenience in the drawing, the second profile is stored in a profile server different from the profile server 230, for example, the second profile server 240 in FIG. may be stored.

Also, in step 305, the profile server 230 may selectively store the certificate of the eSIM 211 loaded in the first terminal 210 transmitted in step 303 and the certificate on the certificate hierarchy of the corresponding certificate. In addition, the profile server 230 may selectively store the public key of the certificate of the eSIM 211 mounted on the first terminal 210 transmitted in step 303 .

In step 307, the profile server 230 may deliver an activation code for downloading the profile prepared in step 305 to the first terminal 210, and may further notify that the first profile needs to be deleted. The method of notifying that the first profile needs to be deleted may include, for example, transmitting a first profile deletion request (delete profile) flag, transmitting a first profile reuse (reuse profile) flag, or A method of not transmitting a do not delete profile flag or not transmitting a new profile flag may be used.

In addition, when it is further notified in step 307 that the first profile needs to be deleted, the deletion result of the first profile of the first terminal 210 transmitted through the second terminal 220 can be optionally processed. can be notified. A method for notifying that the deletion result of the first profile of the first terminal 210 transmitted through the second terminal 220 can be processed is, for example, a profile deletion notification support flag (delete notification support) flag) or not transmitting the profile deletion notification confirmation flag (delete notification not supported) may be used.

In addition, in step 307, when it is known that the deletion result of the first profile of the first terminal 210 transmitted through the second terminal 220 can be processed, the first profile transmitted through the second terminal 220 is known. At least one address of the notification receiving server 300 to process the deletion result of the first profile of the terminal 210 may be selectively included. As a method of notifying the address of the notification receiving server 300, for example, a method such as transmitting the FQDN, IP Address, or URL of the address of the notification receiving server 300 may be used. If the notification receiving server 300 is the same as the profile server 230 or the profile servers 230 and 240 storing the first or second profile in step 305, the address of the notification receiving server 300 may not be selectively notified. can

In addition, in step 307, the profile server 230, if necessary, transmits part or all of information about the second profile (profile metadata) and/or information to be known to the user downloading the second profile to the first terminal 210. ) can be further informed. When the first terminal 210 further receives information on the second profile and/or information to be noted by the user downloading the second profile, the first terminal 210 transmits some or all of the information to the user ( 200) and consent of the user 200 may be input.

In step 309, the first terminal 210 may delete the first profile according to the request of the profile server 230 and generate a delete notification to be notified to at least one notice receiving server set in the first profile. have. If it is necessary to deactivate the first profile before deleting the first profile, the first terminal 210 may deactivate the profile. In this case, the first terminal 210 sends information to at least one notification receiving server set in the first profile. You can create deactivation results to be notified. The deactivation result and deletion result of the first profile may include at least the profile identifier (ICCID) of the first profile. The result of deactivation and deletion of the first profile may include a certificate of the eSIM 211 installed in the first terminal 210 and a certificate of the certificate hierarchy of the corresponding certificate. In addition, the first profile deactivation result and deletion result may include a digital signature generated using a private key paired with a public key included in the certificate of the eSIM 211 .

Step 309 may be performed using, for example, at least one of a disable profile message, a delete profile message, and a retrieve notifications list message.

In step 311, the first terminal 210 may notify a server having a recipient address included in the result of deactivation and deletion generated in step 309 of the result of deactivation and deletion of the first profile. 3 shows that the first terminal 210 notifies the profile server 230 and the notification receiving server 300 of the deactivation result and the deletion result for convenience of drawing, but the deactivation result and the deletion result are different from the profile server. (For example, the second profile server 240 shown in FIG. 2 or the third profile server not shown), and the deactivation result and the deletion result may be delivered separately.

Step 311 may be performed using, for example, a handle notification message. Also, when the first profile is already in a deactivated state, the first terminal 210 may omit the operation of deactivating the first profile and the operation of notifying the profile server 230 of the result of the deactivation in step 309 . In step 311, each server notified of the result verifies the result, and may forward the verification result to the first terminal 210, operator 250, profile server 230, and other profile servers not shown in FIG. .

In step 311, the profile server 230 may confirm that the first terminal 210 has deleted the first profile, and may set the first or second profile prepared in step 305 to be downloadable. Also, the profile server 230 may selectively notify the first terminal 210 that the first or second profile is in a downloadable state.

In step 313, the first terminal 210 selectively generates a new activation code including an activation code capable of downloading the profile prepared in step 305 known in step 307 and a result of deleting the first profile generated in step 309. can do.

In step 313, the first terminal 210 notifies in step 307 that the profile server 230 can process the deletion result of the first profile of the first terminal 230 transmitted through the second terminal 220. In one case, the generation of a new activation code can be performed. In step 307, it is known that the profile server 230 can process the deletion result of the first profile of the first terminal 230 transmitted through the second terminal 220, but in step 311, the result of deleting the first profile When the notification is successfully performed, the first terminal 210 may selectively perform step 313. The first terminal 210 may perform step 313 regardless of the notification of the profile server 230 or the notification processing of the deletion result of the first profile.

In addition, in step 307, when the address of the notification receiving server to process the deletion result of the first profile of the first terminal 210 delivered through the second terminal 220 is known, the first terminal 210 performs step 309. Among the results of deleting the first profile generated in , a result of deleting the first profile having the same recipient address as the address of the known notification receiving server may be included in the new activation code.

Also, in step 313, the address of the notification receiving server to process the deletion result of the first profile of the first terminal 210 transmitted through the second terminal 220 in step 307 is known to the first terminal 210. , If the first profile deletion result including the same notification receiving address does not exist, a new activation code may not be generated.

In addition, in step 313, the address of the notification receiving server to process the deletion result of the first profile of the first terminal 210 transmitted through the second terminal 220 in step 307 is not known to the first terminal 210. If there is no result of deleting the first profile, or if there is no result of deleting the first profile including the same address as the notification receiving address, the first terminal 210 determines the result of deleting the first profile that satisfies the following conditions among the results of deleting the first profile generated in step 309. can be included in the new activation code.

- Among the results of deleting the first profile, the sequence number is small

- Among the results of deleting the first profile, the recipient address is the same as the address of the profile server 230

- Among the first profile deletion results, the recipient address is the same as the address of the profile server included in the activation code that can download the profile prepared in step 305.

- Random selection among the results of deleting the first profile

Also, in step 313, the first terminal 210 may include all or part of the selected first profile deletion result in the new activation code. In this case, the first terminal 210 may include in the new activation code only a part of the eSIM 211 certificate and certificates in the certificate hierarchy of the corresponding certificate in the transmitted first profile deletion result. In addition, the first terminal 210 generates a deletion result for device change, including a first profile deletion result excluding the eSIM 211 certificate and certificates in the certificate hierarchy of the corresponding certificate (Delete Notification for Device Change) and the deletion result for the corresponding device change can be included in the new activation code.

In steps 315 and 317 , the first terminal 210 may transmit the activation code transmitted in step 307 or the activation code generated in step 313 to the second terminal 220 .

As an example of the first terminal 210 passing the activation code to the second terminal 220, in step 315, the first terminal 210 converts the activation code into an image form such as a QR code or converts it into a string form to display the screen. and notify the user that the activation code is ready.

In step 317 , the user 200 may input the activation code displayed on the screen of the first terminal 210 to the second terminal 220 . Various methods may be used to input the activation code, such as taking an image such as a QR code with a camera or inputting a string with a keyboard. In addition, when the first terminal 210 and the second terminal 220 are connected to each other through short-range communication (eg, Bluetooth, NFC, WiFi, WiFi Direct, etc.), the first terminal 210 in step 315 The activation code may be directly transmitted to the second terminal 220 without being output on the screen.

In step 319, the second terminal 220 may request the profile server 230 to download the profile. Step 319 may be performed using, for example, at least one of an initiate authentication message, an authenticate client message, and a transfer request message. Step 319 may include a procedure in which the second terminal 220 transmits the event identifier (MatchingID) included in the activation code to the profile server 230 . In step 319, the second terminal 200 may use WiFi or an Internet tethering function provided by the first terminal 210 to connect to the Internet. In step 319, when the activation code transmitted from the first terminal 210 includes the first profile deletion result, the second terminal 220 selectively transfers the corresponding first profile deletion result to the profile server 230. can be included as In step 319, if the second terminal 220 includes a procedure for transmitting the first profile deletion result, but the profile server 230 does not support processing of the first profile deletion result, the profile server 230 returns an error code may be returned and the operation may be terminated, or it may proceed to a later step without an error reply.

In step 321, the profile server 230 may first check whether the profile is in a downloadable state. If it is impossible to download the profile because it is not confirmed through steps 309 to 311 that the first profile has been deleted from the first terminal, the profile server 230 may return an error code and terminate the operation. If the profile can be downloaded, the profile server 230 may deliver profile metadata and information that the user downloading the first profile should be aware of to the second terminal 220. . Information about the profile may include, for example, the name or logo of the business operator 250, a profile policy, and the like. Information that the user downloading the profile should be aware of may include, for example, the remaining number of profile transfers allowed by the business operator 250 or the cost the user has to pay for profile transfer.

In step 321, if it is impossible to download the profile because it cannot confirm that the first profile has been deleted from the first terminal through steps 309 to 311, the profile server 230 sends the second terminal 220 in step 319. The transmitted first profile deletion result can be checked. In step 313, when the first terminal 210 includes only a part of the first profile deletion result, that is, a part other than the eSIM 211 certificate and a certificate in the certificate hierarchy of the corresponding certificate, in the activation code, the profile server 230 performs a step 305 The first profile deletion result may be restored to enable signature verification of the eSIM 211 by combining the certificate of the eSIM 211 stored in the step, the certificate in the certificate hierarchy of the corresponding certificate, and the delivered first profile deletion result. .

Also, in step 321 , the profile server 230 may verify the transmitted result of deleting the first profile or the result of deleting the restored first profile. In addition, when the first terminal 210 includes the deletion result for device change in the activation code in step 313, the profile server 230 uses the certificate public key of the eSIM 211 stored in step 305. Thus, the deletion result for the device change can be verified. If the notification receiving address of the first profile deletion result is not the address of the profile server 230, the first profile deletion result is transferred to the notification receiving server 300 of the corresponding notification receiving address, and the notification receiving server 300 verifies The verification result may be returned to the profile server 230 by performing.

If, in step 321, the profile server 230 failed to verify the first profile deletion result, or received a verification error result or failed to receive a verification result from another notice receiving server 300, or the corresponding notice receiving server 300 When the first profile deletion result cannot be delivered, the profile server 230 may return an error code and terminate the operation. If the verification of the result of deleting the first profile is successfully performed, the profile server 230 transmits information about the profile (profile metadata) and information that the user downloading the profile should be aware of to the second terminal 220. can be conveyed Information about the profile may include, for example, the name or logo of the business operator 250, a profile policy, and the like. Information that the user downloading the profile should be aware of may include, for example, the remaining number of profile transfers allowed by the business operator 250 or the cost the user has to pay for profile transfer.

In step 323, the user 200 may check information about the profile and information that the user downloading the profile should be aware of, and agree to install the profile. The operation of agreeing to the installation of the profile is an operation of selecting "Yes/No", inputting the password set by the user 200, or inputting biometric information such as the user's 200 fingerprint or iris. can

In step 325, the second terminal 220 may notify the profile server 230 that the user 200 agrees to download the profile and request a profile package.

In step 327, the profile server 230 may deliver the profile package for the profile to the second terminal 220.

In step 329, the second terminal 220 may install a profile using a profile package for the profile.

4 is a diagram illustrating a procedure of downloading a profile by a first terminal transferring an activation code stored in the first terminal to a second terminal according to an embodiment of the present disclosure.

In FIG. 4 , configuration and description of the user 200 , the first terminal 210 , the second terminal 220 , the profile server 230 , and the operator 250 will be referred to FIG. 2 . For example, the user 200, the first terminal 210, the second terminal 220, the profile server 230, and the business operator 250 are the user 200, the first terminal 210, It may correspond to the second terminal 220, the first profile server 230, and the operator 250. In addition, the configuration and description of the notification receiving server (300, Notification Receiver) will be referred to FIG. 3.

Referring to FIG. 4 , in step 401, the user 200 may request the first terminal 210 to transfer the first profile. To this end, the user 200 can check information on the first profile (profile metadata) and information that a user who intends to move the first profile should be aware of through the first terminal 210 . Information about the first profile and information to be noted by a user who wants to move the first profile may be stored in the first terminal 210 or the first profile. Information on the first profile may include, for example, the name or logo of the operator 250, a profile policy, and the like. Information to be noted by the user who intends to move the first profile may include, for example, the remaining number of profile movements permitted by the business operator 250 or the cost the user must pay for profile movement.

In addition, the first terminal 210 to the first profile may store an activation code to be used by the terminal for profile migration and information indicating that the first profile needs to be deleted for profile migration. . The activation code to be used by the terminal to move the profile may be, for example, an activation code that was used when the first profile was installed in the first terminal in the past. Information indicating that the first profile needs to be deleted for profile movement is, for example, a first profile delete request flag (delete profile flag) is set, or a first profile reuse (reuse profile flag) It can be expressed using a method such as is set, a do not delete profile flag is not set, or a new profile flag is not set.

In addition, when information indicating that the first profile needs to be deleted is stored, information indicating that the deletion result of the first profile of the first terminal 210 can be transmitted through the second terminal 220 and processed. may be stored. Information indicating that the deletion result of the first profile of the first terminal 210 transmitted through the second terminal 220 can be transmitted through the second terminal 220 and processed, for example, a profile deletion notice A method such as a flag for supporting confirmation (delete notification support) is set or a flag for not supporting profile deletion notification support (delete notification not supported) is not set may be used.

In addition, when information indicating that the deletion result of the first profile of the first terminal 210 can be transmitted and processed through the second terminal 220 is set, the first profile transmitted through the second terminal 220 is set. At least one address of the notification receiving server 300 to process the deletion result of 1 profile may be optionally included. As a method of notifying the address of the notification receiving server 300, for example, a method such as transmitting the FQDN, IP Address, or URL of the address of the notification receiving server 300 may be used.

In step 403, the first terminal 210 may call an activation code to be used by the terminal to move the profile stored in the first terminal 210 to the first profile. The activation code may include at least the address of the profile server 230 where the first and second profiles are stored, and an event identifier (MatchingID) connected to the first and second profiles. At this time, the first and second profiles stored in the profile server 230 may be set to a state in which download is not yet possible. In addition, the first terminal 210 may transmit information indicating that the first profile needs to be deleted and the deletion result of the first profile of the first terminal 210 may be transmitted and processed through the second terminal 220. The address of the notification receiving server 300 that will process the information representing the first profile and the deletion result of the first profile can be called.

In step 405, the first terminal 210 may delete the first profile and create a deletion result to be notified to at least one notice receiving server set in the first profile. If it is necessary to deactivate the first profile before deleting the first profile, the first terminal 210 may deactivate the profile. In this case, the first terminal 210 sends information to at least one notification receiving server set in the first profile. You can create deactivation results to be notified. The deactivation result and deletion result of the first profile may include at least the profile identifier (ICCID) of the first profile. The result of deactivation and deletion of the first profile may include a certificate of the eSIM 211 installed in the first terminal 210 and a certificate of the certificate hierarchy of the corresponding certificate. In addition, the first profile deactivation result and deletion result may include a digital signature generated using a private key paired with a public key included in the certificate of the eSIM 211 . Step 405 may be performed using, for example, at least one of a disable profile message, a delete profile message, and a retrieve notifications list message. Step 405 may be performed when information indicating that the first profile needs to be deleted is stored or regardless of the information.

In step 407, the first terminal 210 may notify a server having a recipient address included in the result of deactivation and deletion generated in step 309 of the result of deactivation and deletion of the first profile. 4 shows that the first terminal 210 notifies the profile server 230 and the notification receiving server 300 of the deactivation result and the deletion result for convenience of drawing, but the deactivation result and the deletion result are different from the profile server. (For example, the second profile server 240 shown in FIG. 2 or the third profile server not shown), and the deactivation result and the deletion result may be delivered separately. Step 407 may be performed using, for example, a handle notification message. Also, when the first profile is already in a deactivated state, in step 407, the first terminal 210 may omit the operation of deactivating the first profile and the operation of notifying the profile server 230 of the result of the deactivation.

In step 407, the profile server 230 and the operator 250 may check the possibility of moving the first profile. If the first profile can be moved to another terminal, the profile server 230 and the operator 250 can prepare for reuse of the first profile. Step 407 is, for example, a download order message, a confirm order message, a rpm order message, a release order message, or a handle notification. ) It may be performed using at least one or more of

In step 407, the profile server 230 may confirm that the first terminal 210 has deleted the first profile, and set the first to second profiles to be downloadable. In addition, the profile server 230 may notify the first terminal 210 that the first and second profiles are downloadable. If deletion of the first profile is not confirmed in step 407, the profile server 230 may set the first to second profiles to be undownloadable or maintain the existing settings.

In step 409, when information indicating that the deletion result of the first profile can be transmitted and processed through the second terminal 220 is set, the first terminal 210 displays the information of the first profile generated in step 405. You can optionally generate a new activation code containing the deletion result. The first terminal 210 may selectively generate a new activation code including the result of deleting the first profile generated in step 405 regardless of the setting.

In addition, in step 409, if the address of the notification receiving server 300 to process the deletion result of the first profile delivered through the second terminal 220 has been set, the first terminal 210 is generated in step 405. A result of deleting the first profile whose recipient address included in the result of deleting the first profile is the same as the address of the set notification receiving server may be included in the new activation code.

Also, in step 409, the first terminal 210 receives the same notification receiving address, although the address of the notification receiving server 300 to process the deletion result of the first profile transmitted through the second terminal 220 has been set. If the result of deleting the first profile does not exist, a new activation code may not be generated.

Also, in step 409, the first terminal 210 has not set the address of the notification receiving server 300 to process the deletion result of the first profile transmitted through the second terminal 220, or has been set. If there is no first profile deletion result including the same notification receiving address, the first terminal 210 assigns the first profile deletion result satisfying the following condition among the first profile deletion results generated in step 309 to the new activation code. can include

- Among the results of deleting the first profile, the sequence number is small

- Among the results of deleting the first profile, the recipient address is the same as the address of the profile server 230

- Among the results of deleting the first profile, the recipient address is the same as the address of the profile server included in the activation code that the terminal must use to move the profile stored in the first profile.

- Random selection among the results of deleting the first profile

In addition, in step 409, the first terminal 210 may include all or part of the selected first profile deletion result in the new activation code. In this case, the first terminal 210 may include in the new activation code only a part of the eSIM 211 certificate and certificates in the certificate hierarchy of the corresponding certificate in the transmitted first profile deletion result. In addition, the first terminal 210 generates a deletion result for device change (Delete Notification for Device Change) including a first profile deletion result excluding the eSIM 211 certificate and certificates in the certificate hierarchy of the corresponding certificate. and the deletion result for the corresponding device change can be included in the new activation code.

In step 411, the first terminal 210 converts the activation code into an image form such as a QR code or into a string form, outputs the converted code to the screen, and notifies the user that the activation code is ready.

In step 413 , the user 200 may input the activation code displayed on the screen of the first terminal 210 to the second terminal 220 . Various methods may be used to input the activation code, such as taking an image such as a QR code with a camera or inputting a string with a keyboard. In addition, when the first terminal 210 and the second terminal 220 are connected to each other through short-range communication (eg, Bluetooth, NFC, WiFi, WiFi Direct, etc.), the first terminal 210 receives an activation code. It may be directly transmitted to the second terminal 220 without being output on the screen.

In step 415, the second terminal 220 may request download of the first and second profiles from the profile server 230. Step 415 may be performed using, for example, at least one of an initiate authentication message, an authenticate client message, and a transfer request message. Step 415 may include a procedure in which the second terminal 220 transmits the event identifier (MatchingID) included in the activation code to the profile server 230 .

In step 415, the second terminal 200 may use WiFi or an Internet tethering function provided by the first terminal 210 to connect to the Internet. In step 415, when the activation code transmitted from the first terminal 210 includes the first profile deletion result, the second terminal 220 performs a procedure for transmitting the first profile deletion result to the profile server 230. may optionally be included. In step 415, if the second terminal 220 includes a procedure for transmitting the first profile deletion result, but the profile server 230 does not support processing of the first profile deletion result, the profile server 230 returns an error code may be returned and the operation may be terminated, or it may proceed to a later step without an error reply.

In step 417, the profile server 230 may first check whether the first profile is in a downloadable state. If, through steps 405 to 407, it is not confirmed that the first profile has been deleted from the first terminal, and the prepared first to second profiles cannot be downloaded, the profile server 230 returns an error code and ends the operation. can do. If the profile can be downloaded, the profile server 230 may deliver profile metadata and information to be noted by the user downloading the profile to the second terminal 220 . Information about the profile may include, for example, the name or logo of the business operator 250, a profile policy, and the like. Information that the user downloading the profile should be aware of may include, for example, the remaining number of profile transfers allowed by the business operator 250 or the cost the user has to pay for profile transfer.

In step 417, if it is impossible to download the profile because it cannot confirm that the first profile has been deleted from the first terminal through steps 405 to 407, the profile server 230 sends the second terminal 220 in step 417. The transmitted first profile deletion result can be checked. In step 417, when the first terminal 210 includes only a part of the first profile deletion result, that is, a part other than the eSIM 211 certificate and the certificate in the certificate hierarchy of the corresponding certificate, in the activation code, the profile server 230 The certificate of the eSIM 211 stored in the step of providing 1 profile to the first terminal 210 (not shown, prior to step 401), the certificate in the certificate hierarchy of the corresponding certificate, and the delivered first profile deletion result are combined. A result of deleting the first profile may be restored so that the signature of the eSIM 211 can be verified.

Also, in step 417 , the profile server 230 may verify the transmitted result of deleting the first profile or the result of deleting the restored first profile. In addition, in step 409, when the first terminal 210 includes the deletion result for device change in the activation code, the profile server 230 provides the first profile to the first terminal 210 (not shown, 401 The deletion result for the device change may be verified using the certificate public key of the eSIM 211 stored in the previous step). If the notification receiving address of the first profile deletion result is not the address of the profile server 230, the first profile deletion result is transferred to the notification receiving server 300 of the corresponding notification receiving address, and the notification receiving server 300 verifies The verification result may be returned to the profile server 230 by performing.

If, in step 417, the profile server 230 failed to verify the first profile deletion result, received a verification error result or failed to receive a verification result from another notice receiving server 300, or the corresponding notice receiving server 300 When the first profile deletion result cannot be delivered, the profile server 230 may return an error code and terminate the operation. If the verification of the result of deleting the first profile is successfully performed, the profile server 230 transmits information about the profile (profile metadata) and information that the user downloading the profile should be aware of to the second terminal 220. can be conveyed Information about the profile may include, for example, the name or logo of the business operator 250, a profile policy, and the like. Information that the user downloading the profile should be aware of may include, for example, the remaining number of profile transfers allowed by the business operator 250 or the cost the user has to pay for profile transfer.

In step 419, the user 200 may check information about the profile and information that the user downloading the profile should be aware of, and agree to install the profile. The operation of agreeing to the installation of the profile is an operation of selecting "Yes/No", inputting the password set by the user 200, or inputting biometric information such as the user's 200 fingerprint or iris. can

In step 421, the second terminal 220 may notify the profile server 230 that the user 200 has agreed to download the profile and request a profile package.

In step 423, the profile server 230 may deliver the profile package for the profile to the second terminal 220.

In step 425, the second terminal 220 may install the profile using a profile package for the profile.

5 is a block diagram illustrating components of a terminal according to an embodiment of the present disclosure.

Each of the terminals described in the present disclosure (the first terminal 210, the second terminal 220, and the terminals described without attaching reference numbers) may correspond to the first terminal or the second terminal described in FIG. 2 . The first terminal 210 and the second terminal 220 may be an embodiment of the terminal of FIG. 2, and expressions of “first” and “second” are used to indicate that each terminal is physically different from each other. It just happened.

As shown in FIG. 5 , a terminal may include a transceiver 510 and a processor 520 . Also, the terminal may include a UICC 530. For example, the UICC 530 may be inserted into the terminal or may be an eUICC built into the terminal.

The transceiver 510 may transmit and receive signals, information, data, and the like to and from the profile server.

The transceiver 510 according to an embodiment of the present disclosure transmits a message requesting an activation code to the profile server, receives the activation code and whether or not the profile needs to be deleted from the profile server, and transmits the profile deletion result to the profile server. can

The transceiver 510 according to an embodiment of the present disclosure may transmit a message requesting a profile to a profile server using an activation code and receive a profile package.

Meanwhile, the processor 520 is a component for overall control of the terminal. The processor 520 may control the overall operation of the terminal according to various embodiments of the present disclosure. The processor 520 may be referred to as a control unit. According to an embodiment of the present disclosure, the processor 520 may include at least one or more processors.

The processor 520 according to an embodiment of the present disclosure receives a profile move request from a user, checks profile move information, transmits a message requesting an activation code to the profile server, and deletes the activation code and the profile from the profile server. The terminal may be controlled to receive whether or not it is necessary, delete the profile, transmit the profile deletion result to the profile server, and transfer the activation code to another terminal.

The processor 520 according to an embodiment of the present disclosure receives an activation code from another terminal, transmits a message requesting a profile to a profile server using the activation code, receives a profile package from the profile server, and receives a profile package. You can control the terminal to install.

The UICC 530 according to an embodiment of the present disclosure may download a profile and install the profile. Also, the UICC 530 may manage profiles.

The UICC 530 may operate under the control of the processor 520 . Alternatively, the UICC 530 may include a processor or controller for installing a profile, or an application may be installed. Some of the applications may be installed in the processor 520 .

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

6 is a block diagram illustrating components of a profile server according to an embodiment of the present disclosure.

Each of the profile servers described in the present disclosure (the first profile server 230, the second profile server 240, and servers described without reference numerals) may correspond to the profile server described in FIG. 2 . The first profile server 230 and the second profile server 240 may be one embodiment of the server of FIG. 2, and expressions of “first” and “second” indicate that each profile server is physically different from each other. It is only used to indicate.

Referring to FIG. 6 , the profile server may include a transceiver 610 and a processor 620 .

The transmission/reception unit 610 may transmit and receive signals, information, data, and the like with terminals or service providers.

The transceiver 610 according to an embodiment of the present disclosure receives a profile transfer request message from a terminal, transmits a message including an activation code and whether or not a profile deletion is necessary to the terminal, and receives a profile deletion message from the terminal, A profile download request message may be received from the terminal, a profile package may be transmitted to the terminal when the profile is in a downloadable state, and an error code may be transmitted when the profile is in a downloadable state.

Meanwhile, the processor 620 is a component for overall control of the profile server. The processor 620 may control the overall operation of the profile server according to various embodiments of the present disclosure. The processor 620 may be referred to as a control unit. According to one embodiment of the present disclosure, the processor 620 may include at least one or more processors.

The processor 620 according to an embodiment of the present disclosure receives a profile move request message from the terminal, determines whether the profile can be moved, generates an activation code capable of downloading the profile, and if the profile can be moved, the profile Set the status to a non-downloadable status, set the status of the profile to a downloadable status if the profile cannot be moved, send a message including an activation code and profile deletion necessity to the terminal, and profile deletion result from the terminal , changes the profile to a downloadable state, receives a profile download request message from the terminal, determines whether the profile is in a downloadable state, transmits a profile package to the terminal if the profile is in a downloadable state, and If the download is impossible, the profile server can be controlled to send an error code.

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

According to an embodiment of the present disclosure, in a wireless communication system, a terminal may receive a user's request to re-install a profile installed in the terminal to another terminal for network connection. In addition, the terminal may request an activation code for downloading a profile from a profile server or read an activation code stored in the terminal by referring to profile movement information stored in the terminal. In addition, the terminal may delete a profile to be moved by referring to a request of a profile server or profile movement information stored in the terminal. In addition, the terminal may transmit the activation code received from the profile server or stored in the terminal to another terminal through a user's input, if necessary. In addition, the terminal can download the profile from the profile server using the activation code.

According to an embodiment of the present disclosure, in a wireless communication system, a profile server may generate a profile for a terminal to connect to a network and an activation code required for profile download. In addition, the profile server determines whether the profile can be moved in response to the profile move request received from the terminal, and if the profile can be moved, transmits an activation code for downloading the profile to be moved and a profile deletion request to the terminal, When the profile cannot be moved, an activation code for downloading a new profile is transmitted to the terminal, a result of deleting the profile to be moved is received from the terminal, the profile is changed to a downloadable state, and a profile download request is received from the terminal, It is determined whether the profile is downloadable, and if the profile is downloadable, the profile may be transmitted to the terminal.

In the specific embodiments of the present disclosure described above, components included in the disclosure are expressed in singular or plural numbers according to the specific embodiments presented. However, the singular or plural expressions are selected appropriately for the presented situation for convenience of explanation, and the present disclosure is not limited to singular or plural components, and even components expressed in plural are composed of the singular number or singular. Even the expressed components may be composed of a plurality.

Meanwhile, in the detailed description of the present disclosure, specific embodiments have been described, but various modifications are possible without departing from the scope of the present disclosure. Therefore, the scope of the present disclosure should not be limited to the described embodiments and should not be defined, but should be defined by not only the scope of the claims to be described later, but also those equivalent to the scope of these claims.

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

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

Various embodiments of the present disclosure provide software (eg, a program) including instructions stored in a machine-readable storage media (eg, internal memory or external memory) readable by a machine (eg, a computer). A device is a device capable of calling a stored command from a storage medium and operating according to the called command, and is a device according to various embodiments of the present disclosure (eg, the first terminal 210 and the second terminal 210). Terminal 220) When a command is executed by a processor (eg, the processor 520 of FIG. 9 or the processor 620 of FIG. 10), the processor directly or other components under the control of the processor A function corresponding to a command may be performed using . A command may include code generated or executed by a compiler or an interpreter.

The device-readable storage medium may be provided in the form of a non-transitory storage medium. Here, 'non-temporary' only means that the storage medium does not contain a signal and is tangible, but does not distinguish whether data is stored semi-permanently or temporarily in the storage medium.

Methods according to various embodiments disclosed in the present disclosure may be provided by being included in a computer program product. Computer program products may be traded between sellers and buyers as commodities. The computer program product may be distributed in the form of a device-readable storage medium (eg compact disc read only memory (CD-ROM)) or online through an application store (eg Play Store™). In the case of online distribution, at least a part of the computer program product may be temporarily stored or temporarily created in a storage medium such as a manufacturer's server, an application store server, or a relay server's memory.

Each component (eg, module or program) according to various embodiments may be composed of a single object or a plurality of objects, and some sub-components among the aforementioned sub-components may be omitted, or other sub-components may be used. It may be further included in various embodiments. Alternatively or additionally, some components (eg, modules or programs) may be integrated into one entity and perform the same or similar functions performed by each corresponding component prior to integration. According to various embodiments, operations performed by modules, programs, or other components are executed sequentially, in parallel, iteratively, or heuristically, or at least some operations are executed in a different order, are omitted, or other operations are added. It can be.

Claims (1)

A control signal processing method in a wireless communication system,
Receiving a first control signal transmitted from a base station;
processing the received first control signal; and
and transmitting a second control signal generated based on the processing to the base station.

Images