KR20220018892A - METHOD AND APPARATUS TO INSTALL AND MANAGE MULTIPLE eSIM PROFILES - Google Patents

Abstract

The present invention relates to a method for installing and managing a plurality of eSIM profiles and a device thereof. A method of a terminal in a wireless communication system comprises the following steps of: transmitting an authentication request message to a manager server; receiving an authentication response message from the manager server; and performing profile management. Therefore, a communication service provider of profile 1 or profile 2 can provide a stable network service.

Description

METHOD AND APPARATUS TO INSTALL AND MANAGE MULTIPLE eSIM PROFILES

The present invention relates to a method and apparatus for establishing a communication connection by downloading and installing one or more communication services in a terminal in a wireless communication system. In addition, the present invention relates to a method and apparatus for remotely downloading and installing a profile in a terminal and managing a plurality of installed profiles.

Efforts are being made to develop an improved 5G communication system or pre-5G communication system in order to meet the increasing demand for wireless data traffic after commercialization of the 4G communication system. For this reason, the 5G communication system or the pre-5G communication system is called a system after a 4G network (Beyond 4G Network) communication system or a Long Term Evolution (LTE) system after (Post LTE). In order to achieve a high data rate, the 5G communication system is being considered for implementation in a very high frequency (mmWave) band (eg, such as a 60 gigabyte (60 GHz) band). In order to alleviate the path loss of radio waves and increase the propagation distance of radio waves in the ultra-high frequency band, in the 5G communication system, beamforming, massive MIMO, and Full Dimensional MIMO (FD-MIMO) are used. ), array antenna, analog beam-forming, and large scale antenna technologies are being discussed. In addition, for network improvement of the system, in the 5G communication system, an evolved small cell, an advanced small cell, a cloud radio access network (cloud radio access network: cloud RAN), an ultra-dense network (ultra-dense network) , Device to Device communication (D2D), wireless backhaul, moving network, cooperative communication, Coordinated Multi-Points (CoMP), and interference cancellation Technology development is underway. In addition, in the 5G system, advanced coding modulation (ACM) methods such as FQAM (Hybrid FSK and QAM Modulation) and SWSC (Sliding Window Superposition Coding), and advanced access technologies such as Filter Bank Multi Carrier (FBMC), NOMA (non orthogonal multiple access), and sparse code multiple access (SCMA) are being developed.

On the other hand, the Internet is evolving from a human-centered connection network where humans create and consume information to an Internet of Things (IoT) network that exchanges and processes information between distributed components such as objects. Internet of Everything (IoE) technology, which combines big data processing technology through connection with cloud servers, etc. with IoT technology, is also emerging. In order to implement IoT, technology elements such as sensing technology, wired and wireless communication and network infrastructure, service interface technology, and security technology are required. , M2M), and MTC (Machine Type Communication) are being studied. In the IoT environment, an intelligent IT (Internet Technology) service that collects and analyzes data generated from connected objects and creates new values in human life 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 appliance, advanced medical service, etc. can be applied to

Accordingly, various attempts are being made to apply the existing 4G and 5G communication systems to the IoT network. For example, 4G and 5G communication technologies such as sensor network, machine to machine (M2M), and MTC (Machine Type Communication) are developed by techniques such as beam forming, MIMO, and array antenna. it is being implemented.

A UICC (Universal Integrated Circuit Card) is a smart card inserted into a mobile communication terminal and used, and is also called a UICC card. An access control module for accessing a network of a mobile communication service provider may be included in the UICC. Examples of such an access control module include a Universal Subscriber Identity Module (USIM), a Subscriber Identity Module (SIM), and an IP Multimedia Service Identity Module (ISIM). A UICC including a USIM is usually called a USIM card. Similarly, a UICC including a SIM module is commonly referred to as a SIM card. In the following description of the present invention, the term "SIM card" will be used in a general sense including a UICC card, a USIM card, a UICC including an ISIM, and the like. That is, even for a SIM card, the technical application can be equally applied to a USIM card, an ISIM card, or a general UICC card.

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

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

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

On the other hand, when the SIM module is remotely downloaded and installed on the UICC card, this inconvenience can be largely solved. That is, a SIM module of a mobile communication service that a user wants to use at a desired time can be downloaded to the UICC card. Such a UICC card can also be used by downloading and installing a plurality of SIM modules, and selecting and using only one SIM module among them. Such a 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, the eUICC refers to a UICC card that is used by being fixed to the terminal, and can be selected by downloading a SIM module remotely. In the present invention, a UICC card that can be selected by downloading a SIM module remotely will be collectively referred to as eUICC. That is, among UICC cards that can be remotely downloaded and selected, UICC cards fixed to the terminal and UICC cards that are not fixed are collectively used as eUICCs. In addition, the downloaded SIM module information will be collectively used as the term Profile.

Even if there is more than one profile in the eUICC, only one profile can be enabled at the same time. Therefore, even if the terminal supports two baseband(s) and two or more profiles exist in the corresponding eUICC, the terminal cannot support the Dual SIM function that enables two profiles to be used simultaneously in one mobile phone. As a way to solve this problem, it is possible to mount two eUICC(s) in the terminal, but this requires an additional eUICC module and a physical interface to connect the eUICC module to the baseband of the modem. You have to bear the cost of purchasing a physical pin for the Physical Interface. In addition, securing the mounting space of the terminal according to the introduction of the module and the physical pin is also a problem.

When the MEP-supported terminal wants to activate the local profile by the user or remotely activate the profile installed in the eUICC by the profile server, the combination of the number of simultaneous activation profiles provided by the terminal and the baseband supported by the modem, and the corresponding baseband It is necessary to process simultaneous activation of one or more profiles by additionally acquiring and combining predetermined information such as whether it is occupied and used.

Currently, in eUICC, only one eSIM profile can be activated at the same time, so when profile 1 is activated, if there is profile 2 connected to the network, profile 2 is deactivated and the communication connection of profile 2 is cut off.

On the other hand, since the eUICC is connected to one baseband of the modem through one physical interface, the message about eUICC memory reset delivered by the eUICC to the modem and the message when the profile is disabled were not processed separately. However, in the case of an MEP-allowed terminal, if it is not processed separately, the modem has a problem in that it can delete all cached data including the cached data of profile 2 stored in the modem, and it is necessary to solve this problem.

An object of the present invention is to provide a method and apparatus for installing, activating, and managing a plurality of profiles so that even one eUICC-equipped terminal can provide a Dual SIM function in a communication system.

In particular, the present invention includes the following examples for the above purpose.

- How the terminal informs the profile server of the terminal's 'eSIM port Capability' information

- How the profile server checks 'eSIM port Capability' information to select a profile to remotely activate and an eSIM port to activate the profile

- Method of determining the eSIM port to be used by the profile by providing the terminal user with a screen to determine the port to use in consideration of the profile activation status of eUICC and 'eSIM port capability'

- How to transmit including the eSIM port information from the eUICC in the terminal's LPA

- How to receive the corresponding port information and activate the profile from the eUICC to the corresponding port

In addition, the present invention includes the following examples for the above purpose.

- When the eUICC receives an eUICC memory reset or profile status change request from the terminal, the eUICC classifies the REFRESH message and transmits it

- How the modem that received the message behaves differently depending on the message received

The technical problems to be achieved in the present invention are not limited to the technical problems mentioned above, and other technical problems not mentioned will be clearly understood by those of ordinary skill in the art to which the present invention belongs from the description below. will be able

According to an embodiment of the present invention, a user can use the Dual SIM function in a terminal equipped with one eUICC. In addition, the terminal manufacturer connects one eUICC and one physical pin to the modem (which provides two or more basebands) without additional terminal mounting space.

It can provide the Dual SIM function and eliminates the need to introduce an additional eUICC, thereby reducing manufacturing costs. The profile management server may obtain information on which eSIM port of the MEP terminal to activate the profile, and may request the user terminal to process the profile activation with an optimal port. Profile 1 and Profile 2, which are simultaneously activated in eUICC, can operate within a single eUICC without mutual interference (such as termination of Profile 2 network connection due to activation of Profile 1), so profile 1 or profile 2 telecommunication service providers can provide stable network services. can provide

1A is a diagram illustrating components of the present invention in a wireless communication system according to an embodiment of the present invention.
1ba is a diagram illustrating a connection (case 1) between a current v2 eUICC that does not support MEP and a modem.
FIG. 1bb is a diagram illustrating a connection (case 2) between a current v2 eUICC that does not support MEP and a modem.
1ca is a diagram illustrating a connection between a v3 eUICC and a modem (case 1) according to the introduction of the Virtual Interface concept.
1cb is a diagram illustrating a connection (case 2) between a v3 eUICC and a modem according to the introduction of the Virtual Interface concept.
FIG. 1da is a flowchart illustrating a method in which an ISD-R of an eUICC transmits a REFRESH message (case 1) to a modem to change a profile state.
FIG. 1db is a flowchart illustrating a method in which an ISD-R of an eUICC transmits a REFRESH message (case 2) to a modem for memory reset.
1E is a flowchart illustrating a method of processing Local profile activation in a terminal to which the present invention is applied.
1fa is an exemplary implementation diagram of a profile management screen (case 1) provided to a terminal user in an MEP support terminal to which the present invention is applied.
1fb is an exemplary implementation diagram of a profile management screen (case 2) provided to a terminal user in an MEP support terminal to which the present invention is applied.
1fc is an exemplary implementation diagram of a profile management screen (case 3) provided to a terminal user in an MEP support terminal to which the present invention is applied.
1fd is an exemplary implementation diagram of a profile management screen (case 4) provided to a terminal user in an MEP support terminal to which the present invention is applied.
1G is a flowchart illustrating a method of processing remote profile activation (RPM-Enable) in a terminal and a profile server to which the present invention is applied.
1H is an exemplary flowchart for determining processing in a modem that has received a received REFRESH Command.
FIG. 1ia is a diagram illustrating a Multi-Selected ISD-R among connections between a v3 eUICC and a modem (case 1) according to the introduction of the Virtual Interface concept.
1ib is a diagram illustrating Multi-Selected ISD-R among v3 eUICC and modem connection (case 2) according to the introduction of the Virtual Interface concept.
1J is a diagram showing the configuration of a terminal block according to an embodiment of the present invention.
1K is a diagram illustrating a Refresh method that does not use a Proactive Command according to an embodiment of the present invention.
11 is a diagram for a method of differently processing, by a modem, a Proactive Command received from a port for a management purpose and a port for a port other than the management purpose, according to an embodiment of the present invention.

Hereinafter, the operating principle of the present disclosure will be described in detail with reference to the accompanying drawings. In the following description of the present disclosure, if it is determined that a detailed description of a related well-known function or configuration may unnecessarily obscure the subject matter of the present disclosure, the detailed description thereof will be omitted. In addition, the terms to be described later are terms defined in consideration of functions in the present disclosure, which may vary according to intentions or customs of users and operators. Therefore, the definition should be made based on the content throughout this specification. For the same reason, some components are exaggerated, omitted, or schematically illustrated in the accompanying drawings. In addition, the size of each component does not fully reflect the actual size. In each figure, the same or corresponding elements are assigned the same reference numerals. Advantages and features of the technical idea according to the present disclosure, and a method 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, but may be implemented in various different forms, and only the present embodiments allow the present disclosure to be complete, and those of ordinary skill in the art to which the present disclosure pertains. It is provided to fully understand the scope of the invention, and the present disclosure is only defined by the scope of the claims. Like reference numerals refer to like elements throughout. In addition, in the description of the present disclosure, if it is determined that a detailed description of a related function or configuration may unnecessarily obscure the gist of the technical idea according to the present disclosure, the detailed description thereof will be omitted. In addition, the terms to be described later are terms defined in consideration of functions in the present disclosure, which may vary according to intentions or customs of users and operators. Therefore, the definition should be made based on the content throughout this specification.

Hereinafter, the base station, as a subject performing resource allocation of the terminal, may be at least one of gNode B, eNode B, Node B, a base station (BS), a radio access unit, a base station controller, or a node on a network. The terminal may include a user equipment (UE), a mobile station (MS), a cellular phone, a smart phone, a computer, or a multimedia system capable of performing a communication function. In the present disclosure, a downlink (DL) is a wireless transmission path of a signal transmitted from a base station to a terminal, and an uplink (UL) is a wireless transmission path of a signal transmitted from the terminal to a base station. In addition, although LTE or LTE-A system may be described below as an example, embodiments of the present disclosure may be applied to other communication systems having a similar technical background or channel type. For example, 5G mobile communication technology (5G, new radio, NR) developed after LTE-A may be included in a system to which embodiments of the present disclosure can be applied, and 5G below is the existing LTE, LTE-A and It may be a concept that includes other similar services. In addition, the present disclosure may be applied to other communication systems through some modifications within a range that does not significantly depart from the scope of the present disclosure as judged by a person having skilled technical knowledge. At this time, it will be understood that each block of the flowchart diagrams and combinations of the flowchart diagrams may 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, such that the instructions performed by the processor of the computer or other programmable data processing equipment are not described in the flowchart block(s). It creates a means to perform functions. These computer program instructions may also be stored in a computer-usable or computer-readable memory that may direct a computer or other programmable data processing equipment to implement a function in a particular manner, and thus the computer-usable or computer-readable memory. It is also possible that the instructions stored in the flow chart block(s) produce an article of manufacture containing instruction means for performing the function described in the flowchart block(s). The computer program instructions may also be mounted on a computer or other programmable data processing equipment, such that a series of operational steps are performed on the computer or other programmable data processing equipment to create a computer-executed process to create a computer or other programmable data processing equipment. It is also possible that instructions for performing the processing equipment 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 also possible for the functions recited in blocks to occur out of order. For example, two blocks shown one after another may in fact be performed substantially simultaneously, or it is possible that the blocks are sometimes performed in the reverse order according to the corresponding function. At this time, the term '~ unit' used in this embodiment means software or hardware components such as FPGA (Field Programmable Gate Array) or ASIC (Application Specific Integrated Circuit), and '~ unit' refers to what roles can be done However, '-part' is not limited to software or hardware. '~' may be configured to reside on an addressable storage medium or may be configured to refresh one or more processors. Accordingly, as an example, '~' indicates components such as software components, object-oriented software components, class components, and task components, and processes, functions, properties, and procedures. , subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, databases, data structures, tables, arrays, and variables. The functions provided in the components and '~ units' may be combined into a smaller number 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 secure multimedia card. Also, in an embodiment, '~ unit' may include one or more processors.

First, terms used in this specification are defined.

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

In the present specification, an eUICC (embedded UICC) is a security module embedded in a terminal, not a removable type that can be inserted and removed from the terminal. eUICC can be installed by downloading a profile using OTA (Over The Air) technology. The eUICC can be named as a UICC that can download and install a profile.

In the present specification, the method for downloading and installing a profile by using the OTA technology in the eUICC may be applied to a removable UICC that can be inserted and removed from the terminal as described above. For example, in an embodiment of the present invention, it can be applied to a UICC that can be installed by downloading a profile using OTA technology.

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

In the present specification, a profile may mean that an application, a file system, an authentication key value, etc. stored in the UICC are packaged in software form. Also, the profile may be named as access information.

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

In the present specification, the profile server creates a profile, encrypts the generated profile, generates a profile remote management command, provides a function to encrypt the generated profile remote management command, or includes a function to support multiple profile activation of the terminal. As a server that can be used, it can be expressed as Subscription Manager Data Preparation (SM-DP), Subscription Manager Data Preparation plus (SM-DP+), or Subscription Manager Secure Routing (SM-SR).

As used herein, the term 'terminal' or 'device' is a mobile station (MS), user equipment (UE), user terminal (UT), wireless terminal, access terminal (AT), terminal, subscriber unit. may be referred to as a (Subscriber Unit), Subscriber Station (SS), wireless device, wireless communication device, Wireless Transmit/Receive Unit (WTRU), mobile node, mobile or other terms. . Various embodiments of the terminal include 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. devices, gaming devices with wireless communication capabilities, music storage and playback appliances with wireless communication capabilities, Internet home appliances with wireless Internet access and browsing, as well as portable units or terminals incorporating combinations of such functions. have. In addition, the terminal may include a machine to machine (M2M) terminal and a machine type communication (MTC) terminal/device, but is not limited thereto. In this specification, the terminal may be referred to as an electronic device or simply a device.

In the present specification, the terminal or device may include software or an application installed in the terminal or device to control the UICC or eUICC. The software or application may be referred to as, for example, a Local Profile Assistant (LPA). In the present specification, the eUICC identifier (eUICC ID) may be a unique identifier of the eUICC embedded in the terminal, and may be referred to as an EID.

In the present specification, an application protocol data unit (APDU) may be a message for a terminal or a controller in a device to interwork with the eUICC.

In the present specification, a profile package may be used interchangeably with a profile or as a term indicating a data object of a specific profile, and may be named as Profile TLV or Profile Package TLV. The profile identifier is a unique identification number of the profile and may be referred to as ICCID. When the profile package is encrypted using an encryption parameter, it may be named as a Protected Profile Package (PPP) or a Protected Profile Package TLV (PPP TLV). When the profile package is encrypted using an encryption parameter that can only be decrypted by a specific eUICC, it may be named as 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 TLV (Tag, Length, Value) format.

In this specification, AKA may indicate authentication and key agreement, and may indicate an authentication algorithm for accessing 3GPP and 3GPP2 networks. K is an encryption key value stored in the eUICC used for the AKA authentication algorithm, and OPc is a parameter value that can be stored in the eUICC used for the AKA authentication algorithm in this specification.

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

In the present invention, end user, user, subscriber, service subscriber, and user may be used interchangeably as a user of a corresponding terminal.

In the present invention, eSIM port refers to a virtual interface channel used by multiplexing and dividing a physical interface connected to an eUICC-modem, and may be used in combination with an eSIM port, an eSIM port, an eSIM port, a port, and a SIM port.

In the present invention, a function for activating and managing a plurality of profiles existing in a single eUICC is collectively referred to as a Multiple Enabled Profile (MEP) function. In the conventional eUICC, only one profile can be activated, so a single eUICC cannot support a Dual SIM or Multi SIM function. In order to support the Dual SIM or Multi SIM function with a single eUICC, a function to activate and manage multiple profiles in a single eUICC is required. An eUICC in which the MEP function is implemented may be referred to as an MEP support eUICC. A terminal including a modem in which the MEP function is implemented and terminal software capable of supporting the modem may be referred to as an MEP support terminal.

And, in describing the present invention, when it is determined that a detailed description of a related known function or configuration may unnecessarily obscure the gist of the present invention, the detailed description thereof will be omitted.

Hereinafter, an embodiment proposed through the drawings will be described.

1A is a diagram illustrating components of the present invention in a wireless communication system according to an embodiment of the present invention.

The user 1a-01 installs/activates/deactivates/updates the profile in the eUICC 1a-20 through the terminal application in which the LPA 1a-05 or the LPA 1a-05 of the terminal 1a-03 is implemented. It requests or provides the user's permission for Remote Profile Management (RPM) processing transmitted from SM-DP+ (1a-40).

Remote Profile Management (RPM) collectively refers to a series of procedures in which profile installation/activation/deactivation/deletion and other functions are performed by commands transmitted from SM-DP+ (1a-40) to the terminal. The RPM may be requested by a communication operator, a service provider, or the owner of the terminal, and a command may be generated by the SM-DP+ (1a-40). The LPA (1a-05), which has received a user input for request or permission for management of the corresponding profile, transmits a message to the eUICC (1a-20) according to the user input to manage / can be controlled

The communication modem 1a-15 of the terminal modulates and transmits a signal to transmit information and demodulates the receiving side to restore the original signal. Two or more can be mounted. The modem 1a-15 is connected to the eUICC and one physical pin (Smart Card Interface conforming to ISO7816 standard at the time of initiating the present invention), and the modem transmits an APDU (Application Protocol Data Unit) command through the interface. In response to this, the eUICC 1a-20 operates in a manner that responds to the result value.

On the other hand, when the eUICC 1a-20 has a message to be transmitted to the modem 1a-15, in response to the APDU Command transmitted from the modem 1a-15, the eUICC 1a-20 has a message to be transmitted. The indicated response code (eg, SW1 (Status word) = 91, SW2 = XX) can be returned (transmitted). Through this, the eUICC 1a-20 enables the modem 1a-15 to receive this "message to be transmitted by the eUICC 1a-20 to the modem 1a-15" through the basic channel. ) can be informed.

The modem 1a-15 may transmit a FETCH Command APDU to the eUICC 1a-20 through the basic channel, and the eUICC 1a-20 may transmit a response APDU thereto. At this time, a message to be transmitted from the eUICC, for example, a Proactive Command may be included in the Data part and transmitted. The Proactive Command may be, for example, a request for UICC Reset or Profile State Change processing. An additional description thereof will be described in detail with reference to FIGS. 1D and 1H.

Meanwhile, the LPA 1a-05 is software operating on the terminal platform, and some functions of the LPA may be integrated into the terminal platform. The message transmitted from the LPA (1a-05) to the eUICC (1a-20) is finally transmitted (1a-20) to the eUICC via the terminal platform or terminal platform and modem (1a-15), and the eUICC receiving the message Steps 1a-20 perform the profile management operation of the eUICC according to the command transmitted from the LPA.

In FIG. 1a, it is assumed that two Profiles, Profile 1 and Profile 2, exist in the eUICC (1a-20) for convenience of explanation below, but the description is not limited thereto. It should be noted that many profiles may exist. Profile 1 (1a-25) and Profile 2 (1a-30) can be activated at the same time in an MEP-supported eUICC. In the case of an eUICC that does not support MEP, either Profile 1 (1a-25) or Profile 2 (1a-30) can be activated at the same time. A profile may be activated.

ISD-R (1a-35) creates a new ISD-P (meaning Security Domain for hosting of profiles) and required eUICC data and services required by the LPA function - eg local profile management, metadata of profiles information- to the LPA.

Meanwhile, although not indicated in the eUICC 1a-20 of this figure 1a-03 for convenience of explanation, Credentials required by the security domains of the eUICC, for example, Certificate Issuer's Root for verifying the SM-DP+ certificate It may include an Embedded UICC Controlling Authority Security Domain (ECASD), an eSIM platform, etc., which is a space for storing a public key, a keyset of an eUICC manufacturer, and the like.

SM-DP + server (1a-40), as described above, the profile server includes a function of creating a profile, encrypting a created profile, generating a profile remote management command, or encrypting a generated profile remote management command, Or, it means a server including a function to support the activation of multiple profiles of the terminal. After the LPA 1a-05 of the terminal 1a-03 receives the SM-DP+ remote management command from the SM-DP+ server 1a-40 and obtains user consent through interaction with the user 1a-01, By transmitting the corresponding remote management command from the LPA (1a-05) to the eUICC (1a-20), activation/deactivation/deletion/update processing can be performed.

The eUICC 1a-20 may be fixed to the terminal or may be removable. Considering the form fixed to the terminal, the eUICC 1a-20 may be expressed as one of the entities of the terminal 1a-03, but in this figure to include the removable eUICC 1a-20, a separate entity from the terminal ( 1a-03), respectively.

1ba and 1bb are diagrams illustrating a connection between a current v2 eUICC that does not support MEP and a modem.

Currently, in the v2 eUICC, only a single (one) profile can be activated in the eUICC, and only the user's local profile management is possible without SM-DP+'s intervention to handle activation/deactivation/deletion/update of pre-installed profiles. In the case of a modem that does not support MEP (1b-01), one or more basebands may be provided in consideration of a case where a physical SIM card is used simultaneously with an eUICC, etc., but in this description, one baseband is assumed.

After UICC Reset or Profile Status Change, the terminal may create an APDU channel transmitted between the modem baseband and the eUICC in the process of initializing between the terminal platform-Modem-eUICC.

In v2 eUICC (1b-15), only one profile can be activated at the same time.

Csse1 (1b-100) in FIG. 1ba is when Profile 1 (1b-20) is activated, Profile 2 (1b-25) is deactivated, and Case 2 (1b-200) in FIG. 1bb is Profile 1 (1b-20) This deactivation, Profile 2 (1b-25), is activated. To explain Case 1 (1b-100), if APDU transmission is required in the baseband of the modem in one activated profile, the eUICC (1b-15) has a Physical Interface (1b-10) connected to the modem (1b-01). The corresponding APDU can be transmitted through a single channel of

On the other hand, the ISD-R (1b-30) receives the ES10c.EnableProfile(Profile2) request from the LPA to change the state of the profile, for example, from Case 1 (1b-100) to Case 2 (1b-200). In this case, the ISD-R 1b-30 may transmit the data deletion processing of the profile cached existing in the modem 1b-10 and a REFRESH Proactive Command for restarting the application session.

In addition, when the ISD-R (1b-30) receives a request for eUICC memory reset from the LPA, the ISD-R (1b-30) processes the data deletion of the UICC cached in the modem (1b-10) and resumes the application session. An APDU for start may be transmitted as a REFRESH Proactive Command. The corresponding APDU that the ISD-R (1b-30) transmits to the modem (1b-01) may also be transmitted through a single channel of the aforementioned physical interface (1b-10).

1ca and 1cb are diagrams illustrating a connection between a v3 eUICC and a modem according to the introduction of the Virtual Interface concept.

The eUICC 1c-20 of FIGS. 1ca and 1cb assumes an eUICC supporting the MEP function capable of simultaneously activating a plurality of profiles. On the other hand, it is assumed that the modem 1c-01 also supports the MEP function. In 1c, a situation in which there are 2 basebands and 2 active profiles is described as an example, and a mapping switch between the baseband and eSIM port in the modem (1c-01) may also be possible, but in this case 1 and 2, the modem (1c-01) The mapping of my logical terminal endpoint will be described as an example of Baseband 1 (1c-05) - Channel 1 (1-40), Baseband 2 (1c-10) - Channel 2 (1-45).

As described above in FIGS. 1ba and 1bb, the current modem 1a-15 is connected to the eUICC 1a-20 through one physical pin, and the modem and the eUICC use a single channel through the corresponding physical pin ( 1b-10) to transmit the APDU Command. The eUICC (1c-20) supporting MEP activates multiple profiles, and the activated profile requires a specific baseband of the modem and APDU transmission. Therefore, the concept of multiplexing the Physical Interface (1c-15) for processing this, classifying APDUs and transmitting them through multiple channels (1c-40, 1c-45) can be introduced.

For convenience of explanation below, when MEP is supported, channels are named eSIM ports, and each channel is named eSIM port 1 (1c-40) and eSIM port 2 (1c-45) and used as eSIM ports. After UICC Reset or Profile Status Change, the terminal can create an APDU channel transmitted between the modem baseband and the eUICC in the initialization process between the terminal platform and the Modem-eUICC. can The corresponding port ID can be set in the modem or terminal platform and delivered to the LPA. Port ID is used interchangeably with port number for convenience of description in this specification.

The modem may have as many eSIM ports as the number of basebands, but the number of eSIM ports used in the eUICC 1c-20 may be the same as or smaller than the number of profiles that can be simultaneously activated in the corresponding eUICC. The profile may transmit an APDU message using one of the corresponding eSIM ports.

In the case of Case 1 (1c-100) of Figure 1ca, the APDU Command corresponding to the activated Profile 1 (1c-25) may be transmitted to Baseband 1 (1c-05) through the eSIM port 1, and at the same time, the activated The APDU Command corresponding to Profile 2 (1c-30) may be transmitted to Baseband2 (1c-10) through eSIM port 2 (1c-45).

In Figure 1cb Case 2 (1c-200), the APDU Command corresponding to the activated Profile 1 (1c-25) can be transmitted to Baseband2 (1c-10) through the eSIM port 2 (1c-45), and at the same time it is activated The APDU Command corresponding to Profile 2 (1c-30) may be transmitted to Baseband 1 (1c-05) through eSIM port 2 (1c-40).

The MEP-supporting modem 1c-01 can distinguish and process which baseband the APDU command transmitted to each eSIM port is connected to. Meanwhile, the ISD-R 1c-50 needs to transmit the APDU Command to the modem for profile and eUICC status management. In this case, the ISD-R (1c-35) can be transmitted in two ways.

One) Multi-Selected: LPA or modem can SELECT ISD-R (1c-35) through a plurality of eSIM ports during the eUICC initialization process. This state can be called Multi-Selected. In case of Multi-Selected, LPA or modem sends APDU command to ISD-R(1c-35) through one of eSIM port that performed SELECT, or event or transmission that ISD-R(1c-35) needs to process. A Command APDU that checks whether there is an APDU to be done can be transmitted. ISD-R(1c-35) determines whether the command received from LPA or modem is a management message corresponding to Profile 1 (1c-25) or Profile 2 (1c-30), Profile 1 (1c-25) and Profile 2 ( Depending on whether it is a management message corresponding to 1c-30) or a message for the entire eUICC, the eSIM port corresponding to each can be selected and the APDU containing the proactive command can be returned to the corresponding port. Alternatively, even in case of multi-selected ISD-R, ISD-R sends management messages corresponding to Profile 1 (1c-25) and Profile 2 (1c-30) through ISD-R of the eSIM port selected by LPA or modem or It is also possible to transmit a message for the entire eUICC.

2) Non Multi-Selected: LPA or modem can select ISD-R (1-35) with only one eSIM port during the eUICC initialization process. This state can be called Non Multi-Selected. In the case of Non Multi-Selected, the APDU command can be transmitted to the ISD-R (1c-35) only through one eSIM port on which the SELECT is performed. In addition, it is possible to transmit a Command APDU that checks whether there is an event to be processed by the ISD-R (1c-35) or an APDU to be transmitted through only one eSIM port that has performed SELECT. The eSIM Port used by ISD-R may be the same as the eSIM port occupied by the profile, or it may be an independent ISD-R dedicated eSIM Port. If the ISD-R (1c-35) needs to transmit an APDU with a proactive command, the modem interprets the received command information if it sends a proactive APDU command to the modem (1c-01) through the eSIM port on which the SELECT was performed. to execute the requested command.

FIG. 1da is a flowchart illustrating a method in which an ISD-R of an eUICC transmits a REFRESH message (case 1) to a modem to change a profile state.

FIG. 1db is a flowchart illustrating a method in which an ISD-R of an eUICC transmits a REFRESH message (case 2) to a modem for memory reset.

According to an embodiment of the present invention, the LPA may transmit an ES10c.EnableProfile or ES10c.DisableProfile message to the eUICC upon receiving a request for changing the state of the profile installed in the eUICC from the terminal user (Enabled in Disabled and Disabled). . While transmitting the message, the LPA can transmit (1d-05) including refreshFlag as an identifier that determines whether the eUICC should send the Proactive Command for REFRESH to the modem. eUICC uses refreshFlag in the corresponding ES10C message. The eUICC determines whether or not the REFRESH is transmitted to the modem (1d-10). ) to transmit a REFRESH APDU Command. Which message to transmit as the corresponding REFRESH message may be determined depending on whether the eUICC is currently operating as an MEP (1d-15) and whether the aforementioned ISD-R is multi-selected (1d-25).

In the initialization process of establishing a connection between the terminal and the eUICC, the terminal modem creates an eSIM Port and sends a command for connecting the port to the eUICC to the eUICC By confirming that the ATR received from the eUICC supports MEP and informing the eUICC of identification information on supporting MEP, it is possible to inform the eUICC that it should operate in the MEP mode thereafter. Whether the current eUICC operates as MEP (1d-15) is determined by the eSIM port connection command received from the above-mentioned modem by the eUICC, or a comment explicitly indicating to the eUICC that it operates as MEP, or the ATR received from the eUICC. It is confirmed that MEP is supported in , and the eUICC receives identification information on supporting MEP and processes the setting by MEP, which can be determined by the eUICC. Alternatively, if the profile information that the eUICC collects or collects and stores by the ISD-R includes profile and port mapping information, the eUICC may determine based on the mapping information. This process can be determined before starting this procedure (1d-01).

The Proactive Command transmitted to the modem when processing the profile status change may include the following information and refer to the ETSI TS 102 223 standard. As described above, (e) when there is a message to be transmitted to the terminal by the UICC, the Proactive Command may be included as data of a reply value to the FETCH Command transmitted from the UICC and transmitted. The Proactive Command can be represented by the configuration of Type-Length-Value (TLV), and one data field among the Values can indicate the type and mode of the Proactive Command. Referring to ETSI TS.102.223, the Proactive command may have a structure as shown in Table 1 below.

[Table 1]

In Table 1, the Command details field may consist of TLVs as shown in Table 2 below.

[Table 2]

On the other hand, when the Proactive Command is transmitted including the port number, a new REFRESH mode or (equivalent to REFRESH level) new Proactive Type (or Type of command) may be defined rather than the existing eUICC Profile State Change or UICC Reset mode. have.

1) When a new Type of command is defined, it may have a value defining a new UICC Reset value for a specific port or a new Type for eUICC Profile State Change processing instead of the REFRESH Type. A new type for eUICC Profile State Change processing may be a Type such as Platform Reset or Port Reset. Alternatively, it may be possible to set the new Type of command as Reset, and to distinguish and indicate Reset as a Command Qualifier for the corresponding Type as follows.

- In case of RESET (an example of a new type):

'00' = Platform Reset;

'00' = Platform Reset;

'01' = Port Reset

'01' = Port Reset

2) When a new mode is added as one mode of REFRESH, it can be expressed as a lower identification value for Type=REFRESH with a Command Qualifier such as 0B and OC below.

- If REFRESH:

'00' = NAA Initialization and Full File Change Notification;

'00' = NAA Initialization and Full File Change Notification;

'01' = File Change Notification;

'01' = File Change Notification;

'02' = NAA Initialization and File Change Notification;

'02' = NAA Initialization and File Change Notification;

'03' = NAA Initialization;

'03' = NAA Initialization;

'04' = UICC Reset;

'04' = UICC Reset;

'05' = NAA Application Reset, only applicable for a 3G platform;

'05' = NAA Application Reset, only applicable for a 3G platform;

'06' = NAA Session Reset, only applicable for a 3G platform;

'06' = NAA Session Reset, only applicable for a 3G platform;

'07' = Reserved by 3GPP ("Steering of Roaming" REFRESH support);

'07' = Reserved by 3GPP ("Steering of Roaming" REFRESH support);

'08' = Reserved by 3GPP (Steering of Roaming for I-WLAN);

'08' = Reserved by 3GPP (Steering of Roaming for I-WLAN);

'09' = eUICC Profile State Change;

'09' = eUICC Profile State Change;

'0A' = Application Update;

'0A' = Application Update;

'0B' = Port Reset

'0B' = Port Reset

'0C' = Platform Reset

'0C' = Platform Reset

In the case of defining the Type of Command or a new Mode, a field(s) that can inform the port number(s) or all for which refresh processing is required may be added as a field of Value of Proactive Command.

3) Without adding a new mode, it is also possible to set the Type of Command to REFRESH and use one of the existing modes to inform the port number(s) or all. This is a value in the TLV of Proactive Command, and it is provided by adding field(s) that can inform the number(s) or all of the ports that need refresh processing. Alternatively, it may be possible to inform by adding a Value value in one of the Values among the TLVs of the existing Proactive Command.

In this specification, an operation using UICC Reset and eUICC Profile State Change mode among various modes of REFRESH is described as a representative embodiment, but the scope of the present invention is not limited thereto.

· If eUICC does not operate as MEP: In the same way, either eUICC Profile State Change or UICC Reset is selected and transmitted. In (1d-15), when eUICC does not operate as MEP, it can be assumed that both eUICC and Modem do not support MEP or support the MEP but do not use the corresponding function (disabled). Supported but not using the function (disabled) may include a case in which the modem has two basebands, but one eUICC and one SIM card occupy and use one baseband each.

· When eUICC operates as MEP and ISD-R multi-selects eSIM port:

Select all the relevant ISD-R ports and transmit REFRESH (1d-27), and the ISD-R of eUICC selects either eUICC Profile State Change or UICC Reset through the REFRESH port and transmits (1d-30)

· When eUICC operates as MEP and ISD-R multi-selects eSIM port:

Even if the ISD-R eSIM port is multi-selected, if you want to transmit a REFRESH to one of the ISD-R ports, select one of the eUICC Profile State Change or UICC Reset to which the REFRESH Port # is added (1d-35) ). Alternatively, in the case of simultaneously REFRESHing a plurality of ports, the number of transmitted Port #s may be plural.

· When eUICC operates as MEP and ISD-R does not support multi-selected eSIM port: ISD-R of eUICC can send (1d-35) a REFRESH proactive command to the default port or default eSIM port as follows: have. The port or eSIM port designated for ISD-R selection in the initialisation process of the terminal and eUICC may be called a default port, default eSIM port, or ISD-R eSIM port. As described above, the corresponding ISD-R eSIM Port may be an ISD-R dedicated port independent of the port used by the Profile, or may be a port used by sharing a port with the Profile.

o The mode of REFRESH is set to eUICC Profile State Change, and the modem transmits the port identifier to which the REFRESH is to be applied. Port identifiers to which REFRESH is to be applied can be transmitted with multiple included

o Set the REFRESH mode to UICC Reset, and transmit the port identifier for the modem to perform the REFRESH. Port identifiers to which REFRESH is to be applied can be transmitted with multiple included

The modem that has received the transmission performs a predefined operation according to the corresponding command, and the operation of the modem will be described later in detail with reference to FIG. 1H .

On the other hand, eUICC is ES10c. In the case of receiving the eUICCMemoryReset from the LPA (1d-45), the eUICC may request a REFRESH from the modem with the Proactive Command when there is at least one profile activated in the eUICC. In the case of eUICC Memory Reset, all profiles activated in the terminal must be disabled, so the eUICC uses one of the following methods in consideration of the number of additionally activated profiles in the REFRESH determination procedure for the above-described Profile Status Change. Commands can be sent to the modem.

One. If the number of activated profiles is 2 or more,

A. When multi-selected is not possible for ISD-R, depending on whether the setting of eUICC is to be processed as a platform reset,

i. In case of processing with platform reset, ISD-R adds eUICC Profile State Change or REFRESH command in UICC Reset mode and an identifier (eg All) meaning 'all eSIM Ports' through one eSIM port and transmits it to the modem ( 1d-60). This may be a new REFRESH mode or a new Proactive Type (equivalent to REFRESH), which means a command to execute the REFRESH command of the eUICC Profile State Change or UICC Reset mode to all ports, which may be referred to as a platform reset, for example.

ii. If it is not processed by Platform Reset, ISD-R sends the eUICC Profile State Change or UICC Reset mode REFRESH command and identifiers meaning multiple eSIM Port # Lists (eg #1, #2) through one eSIM port. Add and send to modem (1d-73)

B. In case that ISD-R can be multi-selected and Proactive Command-REFRESH is transmitted (1d-65) for each port to the modem to process eUICC Memory Reset in ISD-R.

i. ISD-R transmits the REFRESH command of eUICC Profile State Change or UICC Reset mode to the modem through two eSIM ports simultaneously or sequentially (1d-70)

C. In case ISD-R can be multi-selected and ISD-R selects one port to process eUICC Memory Reset and transmits Proactive Command-REFRESH (1d-65)

i. Do as (1d-60) or (1d-75)

2. If 1 Profile is Enabled,

A. Transmitting a REFRESH command to the modem by one of the methods of (1d-30) or (1d-35) described above

When the MEP support eUICC performs REFRESH to change the profile state as in Case 1 of FIG. 1da, the eUICC transmits a REFRESH message depending on the situation among (1d-20), (1d-30), and (1d-35). After this, eUICC receives TERMINAL RESPONSE (in case of sending eUICC profile state change) from the modem or after being reset (in case of sending UICC reset, TERMINAL RESPONSE may not be necessary in this case.) The process of changing the state of the profile is completed do.

When the MEP-supported eUICC has an enabled profile in the eUICC as shown in Case 2 of FIG. 1db and it is necessary to transmit a REFRESH command to the modem for eUICC memory reset, the eUICC deletes all installed Profiles regardless of whether they are enabled or disabled, and As shown, select one of (1d-30), (1d-35), (1d-60), (1d-70), and (1d-73) to send a REFRESH proactive command to the modem, and if there is no Enabled profile, If only the delete operation is performed, the operation without sending the REFRESH Proactive Command is also possible.

1E is a flowchart illustrating a method of processing Local profile activation in a terminal to which the present invention is applied.

As described above, v2 eUICC that does not support the MEP function is designed to enable only one profile to be enabled. If there is an previously enabled profile, the previously enabled profile is disabled to activate another profile. ) should be changed to However, in the case of eUICC supporting the MEP function, when processing a profile activation command, depending on the location of the eSIM port to activate the profile, there may be cases in which other currently activated profiles should not be deactivated. For example, if eSIM has eSIM port 1 and eSIM port 2, and Profile 2 is currently enabled in eSIM port 2, if Profile 1 is additionally enabled in eSIM port 1, Profile2 currently enabled in eSIM port 2 It should be handled so that it does not process Disabled.

In addition, if the terminal has a baseband supporting different RATs, the eSIM port is matched and the radio access technology (RAT) that can be provided through the profile varies according to the baseband, so which profile to activate? It is necessary to provide information so that the user or the server (at RPM) can decide whether to match the eSIM port. For example, if eSIM port 1 is matched with a baseband that supports 4G networks and eSIM port 2 is matched with a baseband that supports 5G networks, if a user or a server performing remote management knows this information, a specific profile It can help you select the appropriate eSIM port to enable.

The number of profiles simultaneously active in the eUICC at a specific time may be limited to be equal to or smaller than the number of eSIM ports allocated by the eUICC. If the user or SM-DP+ wants to process profile activation, eUICC sets the maximum number of profiles that can be activated in eUICC considering the number of currently activated profiles and the number of eSIM ports as LPA or SM-DP+ server. can reply to

The LPA or terminal software may utilize information transmitted from the eUICC (eg, the number of eSIM ports allocated by the eUICC) as predetermined information for the LPA to notify the user that the currently activated profile needs to be deactivated.

FIG. 1e shows a procedure for enabling a profile as an example of a method for a user 1e-01 to manage a profile through an LPA 1e-05 in an MEP support terminal. In FIG. 1E , a case in which the eUICC 1e-10, the modem 1e-15, and the LPA 1e-05 all support MEP will be described as an example.

The end user 1e-01 performs an activation command for the profile installed in the terminal through the information displayed on the LPA 1e-05 or the application in which the LPA 1e-05 is integrated (1e-20). An example of a screen displayed on the user's screen in executing the corresponding activation command will be described later with reference to FIG. 1F. In the terminal's LPA or the corresponding implementation app (1e-05), the user can provide wireless access technology for each baseband of the terminal modem from the terminal in addition to the list of profiles installed in the eUICC and the current profile status information, and the corresponding baseband and APDU transmission. For this purpose, information such as eSIM port information matched for this purpose and information such as the occupancy status of the profile of the corresponding port from the eUICC may be displayed. At this time, the LPA may check the Profile Policy Rules of the profile and additionally display a warning message such as profile activation impossible to the end user (1e-01).

When the user (1e-01) selects a specific profile 3 and decides to activate it through the information displayed on the screen, the LPA (1e-05) includes the port number matched to the selected baseband and ES10c.Enable for profile activation in the eUICC. (ISD-P AID (Issuer Security Domain - Profile Application ID) or ICCID (Profile ID), refreshFlag, Port number) (1e-30) Transmits the command. refreshFlag is additionally set and transmitted when a REFRESH Proactive command is required. If refreshFlag is not set, the terminal sets the conditions for enabling the Enabled profile in MEP, such as UICC - application session termination for the port occupied between modems and logical channel close, if there is an existing Enabled profile through terminal implementation. It must satisfy (1e-25).

When eUICC (1e-10) receives the corresponding Enable profile command from LPA (1e-05) (1e-30), eUICC performs the Disable procedure for the profile (named profile 1) occupying the corresponding port, Enable processing can be performed with the corresponding port. In (1e-35), the ISD-R of the eUICC (1e-10) activates the profile 3 comprehensively by checking the activation status and PPR (Profile Policy Rules) of the profile 3 to be activated and the existing profiles installed in the eUICC. It can determine whether it can be done, and if activation is not possible, an error message can be returned to the user. In determining (1e-35) whether the corresponding profile 3 is activated in the eUICC (1e-10) supporting MEP, if you want to use the port occupied by the existing profile in the eUICC for the activation of profile 3, the eUICC It can be determined that the profile status is changed to disable and profile 3 is changed to enabled status by limiting to Profile1 that used the corresponding port. If profile 3 occupies an empty port, this MEP-supported eUICC 1e-10 may proceed without performing other Profile Disabled procedures in the eUICC. By sending an eUICC REFRESH proactive command to the modem, it is possible to request processing of profile state changes.

The eUICC may transmit a REFRESH proactive command to the modem as described above in FIGS. 1da and 1db, so that the modem can process it as shown in FIG. 1h. Depending on the result of processing the REFRESH in the modem, the eUICC receives a Terminal Response (when eUICC Profile State Change is transmitted) or selects Profile 3 (1a-70) after RESET (when UICC Reset is processed) (1a- 30), if there was a profile that was enabled in the corresponding port (profile 1 in the previous case), it is processed as Disabled and Enable is performed, or if Enable is performed with a previously unoccupied port, Only Profile 3 is completed by performing Enable(1e-75).

If refreshFlag was not set in 1e-30, eUICC matches profile 3 selected after (1e-35) with the port number transmitted in (1a-30), and if there is a profile that was enabled in the corresponding port (Profile 1 in the previous case) If it is processed as Disabled and Enable is performed, or if Enable is performed with a previously unoccupied port, Enable (1e-75) is performed (1e-85) only for the corresponding Profile 3.

The eUICC 1e-10 may reply 1e-90 to the LPA 1e-05 as a result of performing the corresponding procedure. The returned message may be returned including port number(s) for which port reset is required. In addition, even if received without the corresponding port number(s), the LPA (1e-05) determines the port number that requires a port reset, a method of adding it is also possible.

LPA (1e-05) is received from eUICC or transmitted to the modem (1e-15) including the port number(s) added by the LPA. command, and the modem can perform the UICC activation procedure including TERMINAL PROFILE procedure defined in ETSI TS 102 221 clause 14.5.1 (1e-95). Thereafter, the LPA (1e-05) performs a network attach procedure (1e-100) based on the information of the profile newly connected to the port in the baseband connected to the corresponding port. A method of transmitting a Refresh command to the modem when the refreshFlag is not set will be further described later with reference to FIG. 1K .

On the other hand, although not detailed in the drawings, when ISD-R receives port information mapped to a profile from LPA, ISD-R updates the metadata of the corresponding profile, and then LPA to ISD-R for local profile management Information may be requested or provided when LPA requests information for remote profile management from SM-DP+. ISD-R may provide status information of the installed profile, mapping information of the corresponding profile and port, and information of the activated profile in the eUICC. In addition, when a profile is installed or activated by additionally indicating the operator policy (PPR, Profile Policy Rule) on whether the profile can be used in the MEP environment in the metadata of the profile, it is necessary to determine whether the profile can be executed alone or together with other profiles. As information, the ISD-R of eUICC provides the information to the LPA, and the user or the SM-DP+ server can utilize the information.

1fa, 1fb, 1fc, and 1fd are exemplary implementation views of a profile management screen provided to a terminal user in an MEP support terminal to which the present invention is applied.

As described above, through the LPA or LPA-implemented app screen, the user can receive status information such as the profile installed in the eUICC and activation/deactivation of the profile. Capabilities and which baseband - By providing information such as information on which eSIM port is connected to and whether there is an active profile using the port (port occupancy or not), the user can specify which port in eUICC through the screen to profile You can decide whether to activate it or not. The information is information that can be shown to the user on the screen of the LPA or LPA-implemented app for local profile management, and for remote profile management (RPM) through the SM-DP+ server, the information is It is transmitted like port capability, and SM-DP+ may determine a port to process activation/deactivation of a profile through a combination of corresponding information and return it to the terminal. In FIG. 1f, among several combinations that can be displayed to the user,

The representative combinations that can be provided are divided into Figure 1fa Case 1 (1f-01), Figure 1fb Case 2 (1f-05), Figure 1fc Case 3 (1f-55), and Figure 1fd Case 4 (1f-80). It is assumed that eSIM Port 1 is connected to the modem's 4G supported baseband and eSIM Port 2 is connected to the modem's 5G supported baseband.

As described above, the terminal may indicate to the user a part or all of the synthesis of port information, profile state information, profile list, RAT information that can be provided, and the like.

If there is a profile 3 to be activated in Case 1 (1f-01) of FIG. 1fa, the profile is a profile that supports only 4G in this example, so if the user specifies the status change of the profile (1f-15), the terminal is profile 1 Since the status of is to be changed to inactive, the user can be explicitly informed (1f-20) to obtain the user's consent to handle the subsequent procedure. On the other hand, in the case of processing with RPM as will be described later in FIG. 1G, the information indicated in (1f-10) is transmitted to the SM-DP+ server as the eSIM port capability, and the port occupancy status of the eSIM port capability and the RAT for each connection baseband Through the combination of information, SM-DP+ displays a screen such as (1f-23) to the user, and after obtaining the user's consent, the RPM-Enabled procedure can be completed.

1fb Case 2 (1f-05) is a case in which the profile to be activated can support 4G or 5G wireless access technology. Therefore, it is possible to configure a screen for additional selection (1f-40) to receive the user's final selection and to output the corresponding result to display to the user. In case of RPM-Enabled, SM-DP+ server randomly designates one port through judgment such as selecting the highest wireless access technology through the combination of the port occupancy status of eSIM port capability and RAT information for each connection baseband and then transfers to the corresponding port By issuing a command for activation processing (1f-23) or sending a message for the user's additional selection or a URL including the message to the terminal, the terminal obtains the user's consent based on the information (1f-50, 1f-40) and the server receives the transmission, the profile activation process is performed to the last selected port, and the result value can be displayed to the user (1f-45).

1fc Case 3 (1f-55) is a case where there is an unoccupied port in the eUICC, but the radio access technology supported by the profile 3 to be activated does not match the radio access technology supported by the baseband connected to the unoccupied port 2 . In this case, profile 1 occupying the current port can be disabled and the port can be used. In this case, in case of local profile Enable (1f-70), or in case of RPM-Enable (1f-75) You can also indicate the same screen composition.

Finally, in Figure 1fd Case 4 (1f-80), there is an unoccupied port in the eUICC, and the wireless access technology supported by the profile 3 to be activated matches the wireless access technology supported by the baseband connected to the unoccupied port 2, This is the case where the corresponding port 2 can be used without disabling the profile. In this case, a screen such as (1f-90) in case of Local Profile Enable, or a screen configuration such as (1f-95) in case of RPM-Enable may be indicated.

1G is a flowchart illustrating a method of processing remote profile activation (RPM-Enable) in a terminal and a profile server to which the present invention is applied.

For the management (activation/deactivation/deletion/update) of the profile downloaded to the terminal, the user locally requests the corresponding command to the eUICC(1g-10) through the terminal's LPA(1g-05) to LPA(1g-05) , eUICC (1g-10), and modem (1g-15) process this and return a result to the user (1g-01) (1g-25). Since the detailed description of the Enable procedure of Local Profile Management has been previously described with reference to FIG. 1E, a detailed description thereof will be omitted. On the other hand, the profile management server (1g-20) refers to the predetermined data transmitted from the terminal on behalf of the user (1g-01) to remotely manage (activate/deactivate/delete/update) the previously downloaded profile to the terminal. A request (1g-30) may be transmitted to the terminal.

(1g-35) to (1g-80) are diagrams illustrating examples of a general procedure for a terminal to receive and process a remote management command from a profile server according to an embodiment of the present disclosure. In the drawing, when the terminal (1g-33) supports MEP (Multiple Enabled Profile), a procedure that needs to be changed compared to the existing one is indicated. The terminal 1g-33 may be a terminal in which an eUICC 1g-35 is mounted and an LPA 1g-40 for controlling the eUICC 1g-35 is installed. In addition, one or more profiles may be installed in the terminal to the eUICC (1g-35). In addition, each installed profile may have one or more profile servers that can remotely control the profile. Hereinafter, a manager profile server (managing SM-DP+) or SM-DP+ will be described as an example of the profile server, but the profile server of the present invention is not limited thereto. The list of listed administrator profile servers may include addresses or unique identifiers (object identifiers) of each administrator profile server written in the form of an IP Address or FQDN. Also, although not shown in the drawing, the profile server 1g-45 may generate a remote profile management command requested by the telecommunication service provider and wait.

The profile server 1g-45 may transmit a profile remote management command to the LPA 1g-40 in step (1g-60). For example, the profile server 1g-45 includes at least one remote management command and a digital signature of the profile server 1g-45 in step (1g-45). ) message is available. The digital signature of the profile server 1g-45 may be calculated based on at least one remote management command. Although this figure shows an example in which only one "Enable Profile" remote management command is transmitted in step (1g-60), as described above, more than one remote management command may be transmitted, and must be "Enable Profile" It should be noted that various types of remote management commands such as “Disable Profile” and “Delete Profile” may be transmitted rather than the “Enable Profile” remote management command.

Referring to FIG. 1G , in step (1g-50), a common mutual authentication procedure between the terminal 1g-33 and the profile management server 1g-45 may be performed (1g-50). Step (1g-50) may include a TLS connection based on server authentication. In addition, step (1g-50), for example, at least one or more steps of transmitting and receiving an authentication start request (initiate authentication request), an authentication start response (initiate authentication response), and a terminal authentication request (authenticate client request) message may include more. Also, step (1g-50) may be a procedure integrated with some or all of steps (1g-60).

In the procedure, ES9+.AuthenticateClient(transactionId, authenticateServerResponse) including LPA(1g-40) and eUICC(1g-35) of the terminal (1g-33), and predetermined information collected inside the terminal as a terminal authentication request message in the procedure It can transmit to SM-DP+ (1g-45). The authenticateServerResponse may include euiccInfo2 and deviceinfo. Euiccinfo2 means information on the eUICC (1g-35) defined in SGP.22, deviceinfo means information on the corresponding terminal (1g-33) defined in SGP.22, and the corresponding SM-DP+ (1g-45) is Part or all of the euiccinfo2 and deviceinfo information received as a terminal authentication request may be utilized as predetermined information for determining the performance of the RPM for the profile installed in the MEP terminal. The terminal may transmit a message (1g-55) including deviceinfo as some properties of ES9+.AuthenticateClient(transactionId, authenticateServerResponse) or a separate message to SM-DP+ (1g-45).

In euiccinfo2 transmitted by the terminal, MEP-supported eUICC may be indicated as the capability of eUICC, and deviceinfo of (1g-55) is port identification and predetermined information about the port in the eSIM port capability of the deviceinfo. The mapped IMEI (international mobile equipment identities) number may include one or more pieces of Radio Access Technologies information of a baseband used by a corresponding port. Alternatively, the terminal (1g-33) may generate Deviceinfo mapped to each baseband for each number of basebands in the terminal and transmit it in (1g-55) including one or more deviceinfo. For example, in the case of a terminal supporting Dual SIM, two DeviceInfos may be generated and transmitted. As an example, the port capability information of deviceinfo transmitted by the terminal may be expressed by extending deviceinfo as follows. For example, as shown in Table 3 below, although the range of the Port Index is expressed as 1..MaxNumOfPort, the Port Index may be an arbitrary number designated by the terminal.

[Table 3]

RAT (Radio Access Technologies) information supported by the indicated port capability may be the same as or a subset of RAT (Radio Access Technologies) of deviceCapabilities. On the other hand, when two DeviceInfos are generated and transmitted, it can be expressed that two DeviceInfos are transmitted as shown in Table 4 below.

[Table 4]

Considering compatibility with SM-DP+ (1g-45) that does not support MEP capable of performing RPM, in the case of a Dual SIM terminal, the terminal selects the main eSIM port information according to the terminal or user selection and transmits it to deviceinfo, and the Other eSIM port information can also be processed as additional deviceinfo and transmitted separately. In addition, the terminal may transmit the message of step (1g-55) including eSIM port information to SM-DP+ (1g-45) only for RPM operation. At this time, only when the terminal intends to transmit by setting CtxParamForCommonAuthentication, which is included in the Authentication Client Request, to operationType=rpm, the terminal collects eSIM port information and includes the collected eSIM port information in deviceInfo to include SM-DP+ (1g- 45) is also possible.

If the SM-DP+ (1g-45) that received the corresponding port information is SM-DP+ (1g-45) that supports both MEP and RPM, SM-DP+ (1g-45) uses the port from the port capability provided by the terminal. By determining the number of and each port occupied by other profiles, it is possible to determine which port to request the Enabled command to, and then transmit the RPM Command to the terminal. If all the port profiles are in the occupied state, SM-DP+ (1g-45) additionally displays a message stating that all ports are occupied and cannot be enabled to the terminal (1g-35) and port information that must be empty for enable. It may be transmitted to the terminal (1g-35) and provided for the user to process (1g-65) the Disabled procedure of the profile connected to the corresponding port in Local.

As an example in (1g-65), if the user processes the local profile disabled in the terminal by receiving the corresponding message, the terminal 1g-40 transmits the corresponding result to the server 1g-45 again to receive the RPM message. It may also be possible to request a retry or restart the initial RPM request to handle the subsequent procedure. The terminal 1g-33 may match the baseband and port as described above, configure deviceinfo with each baseband information, and transmit deviceinfo to one or more SM-DP+. When SM-DP+ (1g-45) that has received the deviceinfo(s) information is SM-DP+ (1g-45) that supports RPM that does not support MEP, SM-DP+ (1g-45) is in deviceinfo It is also possible to select one and request RPM-Enabled processing to the terminal LPA (1g-40) based on the deviceinfo.

The LPA (1g-40) receiving the RPM request can transmit the profile remote management command to the eUICC (1g-35) in step (1g-70). LPA (1g-40) in step (1g-70), for example, a remote management input request (load RPM) including at least one or more remote management commands and a digital signature of the profile server (1g-45) (digital signature) package request) message, and LPA can specify and transmit information about the eSIM port to connect to when the corresponding profile is enabled for MEP support. The remote management input request message transferred from the LPA to the eUICC may include part or all of the terminal authentication response message 1g-60.

The remote management input request message (load RPM package request) sent from LPA(1g-40) to eUICC(1g-35) is ES10b.LoadRpmPackage (smdpSigned3, smdpSignature3, [eSIM port number]) or ES10b.LoadRpmPackage (smdpSigned3, smdpSignature3) )+[eSIM port number].

Remote management commands such as Profile enabled/disabled/delete may be included in the RpmPackage of smdpsigned3 signed by SM-DP+. The eSIM port information selected by SM-DP+ (1g-45) is included in smdpSigned3 signed with SM-DP+ and replies (for example, as part of the command of RpmPackage parameter in smdpSigned3, or as an additional parameter outside RpmPackage in smdpSigned3); Alternatively, it may be added outside smdpSigned3 and reply.

If the eSIM Port information is outside smdpSigned3, it is also possible to modify the LPA by itself or according to the user's selection. SM-DP+(1g-45) adds the port number to be used outside smdpSigned3 and replies by adding the corresponding port number. may implicitly indicate that it is possible to change by the user or terminal setting. In the case of adding a port number to be used outside smdpSigned3 in the terminal authentication response message (1g-60) in SM-DP+ (1g-45) and delivering it to the LPA (1g-40), the RPM processing is finished and the LPA (1g-40) is By replying (1g-80) a HandleNotification (Load RPM Package Result (OK+[Port #])) to SM-DP+ including the port number, the finally designated port number can be informed to SM-DP+ (1g-45).

It may also be possible to reply (1g-60) an authentication response message without eSIM port information from SM-DP+ (1g-45) to LPA (1g-40). For example, in (1g-55), Device Info transmitted from the terminal to SM-DP+ (1g-45) is sent without information identifying MEP support, or SM-DP+ (1g-45) is sent to MEP support In the case of receiving the information on the terminal authentication response message (1g-60) transmitted from the SM-DP+ (1g-45) to the LPA (1g-40), it may be transmitted to the eUICC without the eSIM port.

In this case, LPA(1g-40) adds eSIM port information to activate the profile and delivers it to eUICC(1g-35), or if LPA(1g-40) does not add eSIM port information, eUICC(1g) -35) to determine the eSIM port may also be possible.

When LPA adds eSIM port information, it is a message of LoadRpmPackageRequest transmitted from LPA (1g-40) to eUICC (1g-35). It is transmitted by adding the eSIM port number as an additional optional parameter to smdpSigned3, smdpSignature3, or It is also possible that the eSIM port number is added as an optional parameter outside the message and delivered.

This may be a message such as the aforementioned ES10b.LoadRpmPackage (smdpSigned3, smdpSignature3, [eSIM port number]) or ES10b.LoadRpmPackage (smdpSigned3, smdpSignature3)+[eSIM port number]. If the eSIM Port is specified outside of smdpsigned3, signature verification must be processed except for the eSIM Port in the step (1g-73) for calculating the SM-DP+ signature verification in the eUICC. Therefore, even if eSIM Port information is changed by LPA, it should not be treated as an error in eUICC.

In case of adding eSIM port information in LPA (1g-40), it is also possible to determine which eSIM port to activate the corresponding profile on and deliver it to the eUICC (1g-35). For example, LPA checks RAT (Radio Access Technology) information supported by baseband and empty eSIM Ports that are not occupied by the profile through the Device Capability of DeviceInfo2 obtained from the terminal, selects one of the empty eSIM Ports, and It can be delivered to eUICC (1g-35) by adding the selected empty eSIM port number to smdpSigned3, smdpSignature3. In particular, when the RAT supported by each baseband is the same, the LPA may arbitrarily select one of the empty eSIM ports for which the profile is not activated.

Alternatively, the LPA (1g-40) may obtain a user input on which eSIM port to activate the corresponding profile and transmit it to the eUICC (1g-35). For example, LPA(1g-40) provides a UI that requests the user to select the eSIM Port (or desired RAT) to use. 35) is also possible.

The terminal (1g-33) designates the default port with port information mapped to the baseband of the deviceinfo or according to the terminal setting, and when the LPA (1g-40) requests the ES10b.LoadRpmPackage Request for Enabled processing from the eUICC, the LPA You can also request eUICC (1g-35) with ES10b.LoadRpmPackage Request (RPM Enable Profile)+ eSIM port# or ES10b.LoadRpmPackage Request (RPM Enable Profile + eSIM port#) (1g-75) as before by adding the corresponding information. have.

An example in which eSIM Port information is changed by the LPA (1g-40) may also be possible. For example, although port information is included from SM-DP+ (1g-45) and transmitted to the LPA (1g-40), there may be a case where it is impossible to deactivate a profile activated in the corresponding port. In this case, when the LPA receives a reply message from the eUICC (1g-35) about not being able to activate with the corresponding port, the LPA (1g-40) adds another eSIM port as an optional parameter by user input or itself, and then re-eUICC You can also set the port by sending it to . For example, if all RATs supported by the basebands of the terminal are the same, it can be added by changing another eSIM port to an optional parameter.

Although there is eSIM port information in smdpSigned3 included in ES10b.LoadRpmPackage, the LPA (1g-40) does not recognize it and adds the eSIM port number and transmits it to the eUICC (1g-35). In this case, the eUICC (1g-35) prioritizes the eSIM port added in the LPA (1g-40) and attempts to activate the profile, and as described below, the final profile activated port information is returned to andleNotification (Load RPM Package Result) You should reply with (OK+[Port #]) (1g-80).

On the other hand, when an activation request is transmitted from the LPA to the eUICC (1g-35) without port information, in the MEP-supported eUICC (1g-35), when performing the eUICC and port initiation between the platform-modem-eUICC of the above-mentioned terminal, the default If one port is designated and an activation request comes from the LPA, it may be possible to process the connection to the corresponding port. As another example, if there is an empty eSIM port at the time when the eUICC receives an activation request, it may be possible to enable the corresponding port.

As described above, when LPA receives a profile activation command without port information, it requests activation processing by adding a specific port number to the eUICC, or even if the LPA receives port information, it cannot be activated on the corresponding port. Even if the number is changed and delivered to the eUICC or received from the LPA without a port number, the method for the MEP-supported eUICC (1g-35) to randomly designate a specific port and connect can be commonly applied to the activation of the local profile mentioned in 1e. .

Meanwhile, in step (1g-73), the eUICC 1g-35 may verify the digital signature of the profile server 1g-45 received in step (1g-70). Verification of the digital signature may be calculated based on at least one or more remote management commands received in step (1g-60). If the verification of the digital signature is successful, the eUICC (1g-35), for one or more remote management commands received in step (1g-60), transmits the remote management command to the profile server (1g-45) that transmits each remote management command. You can check whether it is listed as the administrator profile server of the target profile of For example, the remote management command may target different profiles installed in the eUICC, and the target profile of the corresponding remote management command may be identified through a profile identifier (profile ID or ICCID) in the remote management command.

For the target profile of the remote management command in which the profile server (1g-45) that sent the remote management command is described as the administrator profile server, the eUICC (1g-35) receives one or more remote management commands received in operation (1g-60). command can be executed. When one or more remote management commands are received, the eUICC (1g-35) may repeatedly execute each remote management command. After each remote management command is executed, the eUICC (1g-35) may generate a remote management input result (load RPM package result).

If eSIM Port information is included in smdpsigned3, LPA should not be able to change the value included in smdpsigned3 in the middle. If the LPA has changed this, the eUICC must return an error because the step (1g-73) of verifying the SM-DP+ signature in the eUICC fails. In other words, when SM-DP+ returns to LPA by designating eSIM Port #1 in smdpSigned3 and LPA changes to eSIM Port #2 in the middle, the eUICC that finally received it must return an error. That is, the eSIM port included in smdpSigned3 must be designated by SM-DP+, and LPA must not be added or changed.

When LPA adds eSIM port number and transmits it to eUICC, LPA must process so that new eSIM port parameters can be added while maintaining the integrity protection of smdpSignature3. As described above, when the LPA specifies the eSIM Port outside smdpsigned3 and passes it to the eUICC without modifying the rpmpackge and signature value received from SM-DP, the eSIM Port can be excluded from the signature verification part of SM-DP+ and eUICC.

The remote management input result for one or more remote management commands received by the eUICC (1g-35) is, when each remote management is successful, “No abnormality (OK)” in the form of at least one string or a corresponding numeric string. may be included, and may additionally include a port number for transmission. When each remote management fails, at least one error code causing the failure may be included in the form of a string or a number string corresponding thereto. In this figure, the remote management command received in step (1g-60) is "Enable Profile", and in step (1g-73), eUICC (1g-35) succeeds in enabling the target profile and says " A case in which a result of "No abnormality (OK)" is shown. In step (1g-75), the eUICC (1g-35) may return the remote management input result to the LPA (1g-40). In step (1g-75), the eUICC (1g-35) may use, for example, a remote management input response (load RPM package response) message including at least a remote management input result.

In step (1g-80), the LPA (1g-40) may deliver the remote management input result (load RPM package result) to the profile server (1g-45). The LPA (1g-40) may use, for example, a handle notification message in step (1g-80). The notice processing message may include part or all of the remote management input response message of step (1g-75). As in step (1g-75), the remote management input response message may be returned with information on the eSIM port for which the profile is activated.

1H is an exemplary flowchart for determining processing in a modem that has received a received REFRESH Command.

UICC Reset REFRESH Command can be used when UICC's CAT (Card Application Toolkit) needs to receive ATR (Answer to Reset) or UICC initialization process needs to be performed. When the modem receives the request at the time the present invention is disclosed, the modem performs all application session termination procedures with the UICC card, deletes the cached value for the UICC, and requests a reset to the UICC to cause the UICC to Perform a reset and have the ATR reply. Through this, the modem and eUICC start a new card session, and the modem completes the procedure without sending a TERMINAL RESPONSE to the eUICC after completing the REFRESH. For a detailed description of this, refer to UICC Reset of TS102.223.

On the other hand, when the modem receives the eUICC Profile State Change REFRESH Command, the modem performs the application session termination procedure and deletes all cached values for the profile stored in the modem. Logical channel 0 is left and all other channels are closed to restore the "default state after UICC activation and ATR" defined in ETSI TS 102 221. When the process is completed, the modem sends a TERMINAL RESPONSE to the eUICC.

At the time of disclosing the present invention, when the eUICC processes activation or deactivation of a profile, it can select and transmit one of eUICC Profile State Change or UICC Reset to the modem. Up to now, there is only one profile in eUICC, so it is possible to receive a command among the two to receive a software reset (the terminal operation when receiving the eUICC Profile State Change, or the terminal performing software initialization when UICC Reset is received) case) or a hard reset that resets the device by turning off all power to the device and restoring it to the initial state through a reset PIN, etc., no problem occurred.

However, if multiple profiles are activated, for example, profile 1 and profile 2 are activated in eUICC at the same time, when the above operation is used to process the status change of profile 1, the network of profile 2 may be disconnected. As described above in FIGS. 1da and 1db, a method for eUICC to transmit a REFRESH message according to a situation has been disclosed. When the modem receives the REFRESH command from the eUICC (1h-05), if the modem is not currently operating as MEP, the modem performs the command as before (1h-15) upon receiving the eUICC Profile State Change or UICC Reset can do.

The situation in which the modem is currently operating as the MEP (1h-10) may be regarded as a case in which the terminal performs the initialization procedure with the eUICC and the eUICC MEP. In this case, when a plurality of profile eSIM ports are created, each eSIM port may be mapped to a specific baseband in the modem or may not be mapped. After that, the profile activated on a specific eSIM port can transmit an APDU including Proactive Command to the modem through the corresponding eSIM port. By applying to the baseband, an operation corresponding to the content of the received APDU can be performed.

On the other hand, when ISD-R in eUICC is multi-selected by multiple eSIM ports as described above (LPA selects ISD-R through eSIM ports created in plurality, and ISD-R and APDU for each eSIM port) If logical channel(s) that can transmit/receive data exist), ISD-R can transmit Proactive Command to the modem through each eSIM port. Depending on the satisfaction of (1h-10) and (1h-20) of the current status of the eUICC and the modem, and depending on the Proactive Command received by the modem, the operation of the modem may vary, including one of the following 5 cases can do.

Meanwhile, as described above in FIGS. 1da and 1db, when the port number(s) or all are included in the Proactive Command and transmitted, a REFRESH Proactive Command of a new mode or a new type may be defined. For example, the Proactive Command is the same as the Platform reset mode (if there is all) or the Port reset mode (if port number(s) is included) of the Reset Proactive Command, or indicates the port number(s) in the existing REFRESH Proactive Command. It can be either field or value included. In this drawing, the REFRESH Proactive Command is described as an example, but the scope of the present invention is not limited thereto.

One. If the MEP modem supports multi-selected ISD-R processing (1h-20) and there is no information about Port or All (1h-30) in the REFRESH Command,

A. Execute requested REFRESH Command on the eSIM port of the transmitted channel (Soft Reset) (1h-35).

2. If the MEP modem supports multi-selected ISD-R processing (1h-20) and there is information about Port(s) or All (1h-30) in the REFRESH Command,

A. Perform one of (1h-45), (1h-55), (1h-65) through the judgments of (1h-40), (1h-50), (1h-60) below.

3. When the MEP modem does not support multi-selected ISD-R processing (1h-20) and a REFRESH command is received with UICC Reset + all port identifiers to a specific eSIM port (1h-40),

A. Perform Hard Reset (reset through power or reset PIN) (1h-45).

4. When the MEP modem does not support multi-selected ISD-R processing (1h-20) and a REFRESH Command is received with eUICC Profile State Change + all port identifiers to a specific eSIM port (1h-50),

A. Perform REFRESH for all ports (Soft Reset for all ports) (1h-55).

5. When REFRESH Command is received with port identification information included in eUICC Profile State Change or UICC Reset to a specific eSIM port (1h-60),

A. Perform REFRESH (Soft Reset) for the included Port identifier (1h-65). There may be a plurality of port identifiers, and if a plurality of port identifiers are included, REFRESH is performed on the included port identifiers.

As a result of determining whether Multi-Selected ISD-R is supported (1h-20), it is not supported, and if it is received without information on port number or All, it operates as (1h-15) or (1h- 35) is also possible.

If a plurality of port numbers are included and received, the modem performs a network detach procedure for each port according to the received order, deletes the cached values in the ports, and then resets the corresponding port to a new card. You can also start a session. Also, if the received port occupies the network, the modem may perform a batch network detach procedure, delete all cached values in the ports, and then start a new card session through reset for each port. This can be equally applied even when a reset is requested from the terminal (the terminal framework through the LPA) directly to the modem including a plurality of port numbers (1h-70).

In the case where ISD-R is selected through only one port, the refresh of the included port identifier may be possible, for example, in the following case.

- The modem checks the port identifier information, processes UICC Reset for the port, and sends a reset command to the port.

- The modem checks the port identifier information and requests polling to the corresponding port to process the existing UICC Reset or eUICC Profile State Change at the corresponding port.

Meanwhile, although not described in detail in this drawing, ISD-R may be selected through only one port as described in FIGS. 1ca and 1cb. In this case, it can be said that the port used for ISD-R is used as a port for management purposes for other ports. The modem may handle different Proactive Commands received from the port for management and ports other than those for management. This will be described in further detail in FIG. 11 .

1ia and 1ib show the connection between the v3 eUICC and the modem according to the introduction of the Virtual Interface concept It is a diagram showing the Multi-Selected ISD-R.

The eUICC 1i-20 of the corresponding drawings 1ia and 1ib assumes an eUICC supporting the MEP function capable of simultaneously activating a plurality of profiles. On the other hand, it is assumed that the modem 1i-01 also supports the MEP function. In 1i, a situation where there are 2 basebands and 2 active profiles will be described as an example, and a mapping switch between the baseband and eSIM port in the modem (1i-01) may also be possible, but in this case 1 and case 2, the modem (1i-01) The mapping of my logical terminal endpoint is described as an example of Baseband 1 (1i-05) - Channel 1 (1-40), Baseband 2 (1i-10) - Channel 2 (1-45).

As described above in FIGS. 1ba and 1bb, the current modem 1a-15 is connected to the eUICC 1a-20 through one physical pin, and the modem and the eUICC use a single channel through the corresponding physical pin ( 1b-10) to transmit the APDU Command. The eUICC (1i-20) supporting MEP activates multiple profiles, and the activated profile requires a specific baseband of the modem and APDU transmission. Therefore, the concept of multiplexing the Physical Interface (1i-15) for processing this, dividing the APDU and transmitting it through multiple channels (1i-40, 1i-45) can be introduced.

For convenience of explanation below, when MEP is supported, channels are named eSIM ports, and each channel is named eSIM port 1 (1i-40) and eSIM port 2 (1i-45) and used as eSIM ports. After UICC Reset or Profile Status Change, the UE may create an APDU channel transmitted between the modem baseband and eUICC in the process of initialization between Modem-eUICC, and at this time, the ID for the eSIM port connected to each baseband may be set. . The corresponding port ID can be set in the modem or terminal platform and delivered to the LPA. Port ID is used interchangeably with port number for convenience of description in this specification.

The modem may have the number of eSIM ports as many as the number of basebands, but the number of eSIM ports utilized by the eUICC 1i-20 may be the same as or smaller than the number of profiles that can be simultaneously activated in the corresponding eUICC. The profile may transmit an APDU message using one of the corresponding eSIM ports.

1ia Case 1 (1i-100), the APDU Command corresponding to the activated Profile 1 (1i-25) can be transmitted to the Baseband 1 (1i-05) through the eSIM port 1, and at the same time the activated The APDU Command corresponding to Profile 2 (1i-30) may be transmitted to Baseband2 (1i-10) through eSIM port 2 (1i-45).

In Figure 1ib Case 2 (1i-200), the APDU Command corresponding to the activated Profile 1 (1i-25) can be transmitted to Baseband2 (1i-10) through the eSIM port 2 (1i-45), and at the same time it is activated The APDU Command corresponding to Profile 2 (1i-30) may be transmitted to Baseband 1 (1i-05) through eSIM port 2 (1i-40).

The MEP-supporting modem 1i-01 can distinguish and process which baseband the APDU command transmitted to each eSIM port is connected to. Meanwhile, the ISD-R 1i-50 needs to transmit an APDU Command to the modem for profile and eUICC status management.

The LPA or modem may SELECT the ISD-R (1i-35) through a plurality of eSIM ports during the eUICC initialization process. This state can be called Multi-Selected. In case of Multi-Selected, LPA or modem must send APDU command to ISD-R(1i-35) through one of eSIM port that performed SELECT or event to be processed by ISD-R(1i-35). Polling can be performed to check whether there is an APDU to be used. The ISD-R (1i-35) selects an appropriate eSIM port according to whether the received command is a management message corresponding to Profile 1 (1i-25) or Profile 2 (1i-30), or a message for the entire eUICC. A proactive APDU command can be sent to the corresponding port.

1J is a diagram showing the configuration of a terminal block according to an embodiment of the present invention.

Referring to FIG. 4A , the terminal may include a control unit 1j-10, a transceiver unit 1j-05, a display unit 1j-15, and an eUICC 1j-20. As described above, the eUICC 1j-20 may be configured to be included in the terminal, or may be configured as an entity separate from the terminal or inserted into the terminal.

The transceiver 1j-05 may correspond to a modem in the present invention, and may transmit/receive signals to and from SM-DP+.

The control unit 1j-10 of the terminal may perform the operations according to the embodiments of the present invention by controlling the states and operations of all terminal components in the present invention. For example, an operation according to an embodiment of the present invention may be performed by controlling at least one of LPA, modem, and eUICC.

The display unit 1j-15 may display part or all of a summary of port information, profile state information, a profile list, and available RAT information according to an embodiment of the present invention to the user.

The eUICC 1j-20 is controlled by the LPA or the controller 1j-10, and in an embodiment of the present invention, the eUICC may perform each management command and transmit a Proactive Command to a modem or the like.

1K is a diagram illustrating a Refresh method that does not use a Proactive Command according to an embodiment of the present invention.

FIG. 1K schematically shows an order in which a user 1k-01 manages a profile through an LPA 1k-05 in an MEP support terminal. A case in which the LPA 1k-05, the modem 1k-10, and the eUICC 1k-15 in FIG. 1K all support MEP will be described as an example.

The end user (1k-01) executes (1k-20) the management command of the profile installed in the terminal through the information displayed on the LPA (1k-05) or the LPA (1k-05) integrated application. An example of a screen displayed on a user screen in executing a corresponding management command has been described above with reference to FIG. 1F. As in this figure, ES10c. If the command is transmitted without the RefreshFlag parameter, the UE may use ES10c. Prior to transmitting the command, it may be selectively checked (1k-25) whether the corresponding terminal satisfies the state for supporting it. For example, as defined in SGP.22, when there is an existing Enabled profile, UICC - application session termination for the port occupied between modems, logical channel close, etc. may be.

Upon receiving user input or RPM comment, LPA can transmit (1k-40) ES10c Command to eUICC. Upon receiving the command as defined in SGP.22, the eUICC that has received the message verifies the status for processing the command, such as the profile policy rule or status information of the profile that the eUICC needs to check (1k-45) So, if there is a problem, an error message can be returned. The ES10c. Among the commands, the Commands that cause the profile state change are denoted as Profile State Change Related Commands for convenience of explanation in this drawing, but ES10c. Commands may be one of ES10c.enableProfile, ES10c.disableProifle, ES10c.deleteProifle, and ES10c.euiccMemoryReset.

In order to transmit Proactive Command, the relevant port must support Card Application Toolkit, and it is possible that the port used by ISD-R does not support the corresponding CAT. In this case, when transmitting the Profile State Change Related Command, the LPA may transmit the command without the refreshFlag parameter. This corresponds to the case where there is no refreshFlag in the Profile activation process in FIG. 1E . After receiving the Profile State Change Related Command without the refreshFlag parameter, the eUICC performs the processing action within the eUICC for the profile state change (eg, activates, deactivates, or deletes the profile, etc.) (1k-50), then eUICC or LPA It can be processed so that the modem can perform the refresh process by transmitting the port information that is determined and needed to be refreshed to the modem. The method may include one of the following.

Alt1: How to send to the modem by adding the required port number(s) to Refresh in LPA.

eUICC corresponds to LPA ES10c. The processing result for the command can be returned. LPA determines and stores the port number(s) required for Refresh at a specific point in time after receiving the user's input. You can request a Refresh command (1k-60). When the modem receives the refresh command, it can perform refresh processing (1k-65) at the corresponding port(s) or platform level. The modem can perform UICC Reset or eUICC Profile State Change for the requested port(s) as described above in FIG. 1h, and when an identifier meaning all ports is included, similarly to the current UICC Reset, the entire platform Reset can also be performed.

The way the LPA determines what to enter as the port number(s) that need refresh may be one of the following:

프로파일의 특정 포트로 활성화/비활성화/삭제 처리인 경우: ES10c. Command (1k-40)에 포함된 Port 번호

In case of enabling/disabling/deleting processing with a specific port in the profile: ES10c. Port number included in Command (1k-40)

프로파일의 특정 포트로 활성화 처리인 경우에 추가적인 판단: 해당 활성화를 처리할 프로파일이 다른 포트에 기 활성화된 포트일 수 있다. 이 경우, ES10c. Command (1k-40)에 포함된 Port 번호에 추가적으로 해당 프로파일이 기 활성화 되었던 포트를 모두 Refresh 처리해야 할 수 있다. 상기 기 활성화 되었던 포트의 번호는, eUICC로부터 (1k-45)와 (1k-50)사이에 eUICC로부터 수신된 프로파일이 다른 포트에 있음을 나타내는 에러 메시지 및 추가적으로 포함된 포트의 번호, 또는, ES10c.command를 수행하기에 앞서 GetProfileInfo() (1k-30)을 통해 획득한 정보로써 해당 프로파일이 기 활성화된 포트의 정보(1k-35) 중의 하나 또는 이 둘의 조합으로 LPA가 판단할 수 있다.

Additional determination in the case of activation processing with a specific port of a profile: The profile for processing the activation may be a port previously activated on another port. In this case, ES10c. In addition to the port number included in the command (1k-40), it may be necessary to refresh all ports for which the profile was previously activated. The number of the previously activated port is an error message indicating that the profile received from the eUICC between (1k-45) and (1k-50) is in another port from the eUICC and the number of the additionally included port, or ES10c. As information obtained through GetProfileInfo() (1k-30) prior to executing the command, the LPA can determine one of the information (1k-35) of the port for which the corresponding profile is already activated, or a combination of these two.

eUICC 메모리 Reset 처리인 경우: (1k-40)에서 eUICC 메모리 Reset을 전송하는 경우에, LPA는 LPA의 설정에 따라, GetProfileInfo()로부터 회신된 프로파일별 활성화된 포트의 정보(1k-35)를 활용하는 대신, 모든 Port를 나타내는 식별자 (예를 들어, all)를 사용하는 것으로 판단할 수도 있다.

In case of eUICC memory reset processing: When eUICC memory reset is transmitted in (1k-40), LPA utilizes information (1k-35) of the activated port for each profile returned from GetProfileInfo() according to the LPA setting. Instead, it may be determined to use an identifier (eg, all) indicating all ports.

Alt2: How to add port number(s) required for Refresh in eUICC and transmit it to LPA, and LPA retransmits the information to the modem.

In eUICC, it is possible to process the command for the target profile and reply (1k-70) including the port number that requires Refresh as a result of the processing. This is ES10c. As a result of processing through the command, it can be the number(s) of all ports with changes in the profile and port mapping. For example, you can reply with one or more of the cases in which the profile activated for the port has been changed or has been deactivated. Alternatively, a reply may be returned including a new identifier indicating all ports indicating that platform-level reset processing is required. The eUICC may return to the LPA including at least one of the above information. When the LPA that has received this transmits the port information required for the corresponding refresh to the modem, the modem can perform refresh processing (1k-80) on the corresponding ports or platform level as described above in Alt1.

Alt3: When eUICC adds the port number(s) required for Refresh and sends it to LPA, the modem parses the message in the middle to refresh the port number(s) required for Refresh.

In eUICC, it is possible to process the command for the target profile and reply (1k-85) including the port number that requires Refresh as a result of the processing. This is ES10c. As a result of processing through the command, it can be the number(s) of all ports with changes in the profile and port mapping. For example, you can reply with one or more of the cases in which the profile activated for the port has been changed or has been deactivated. Alternatively, a reply may be returned including a new identifier indicating all ports indicating that platform-level reset processing is required.

The MEP modem can understand the contents by parsing all APDU messages between LPA and ISD-R in the middle, or the eUICC can send an indicator that the MEP modem parses and needs to understand the message contents by adding an indicator outside the corresponding reply message. Yes (1k-85). When the eUICC transmits the message to the LPA (1k-85), the modem interprets the message included in the APDU() transmitted between the eUICC and the card in the middle, and as described above in Alt 1 in the modem, the corresponding ports or platforms Level refresh processing can be performed (1k-80). In this case, the modem may optionally add a result of completion of the corresponding processing to the eUICC and transmit it to the LPA (1k-95).

11 is a diagram of a method for a modem to differently process a Proactive Command received from a port for a management purpose and a port for a port other than a management purpose according to an embodiment of the present invention.

In Figure 1l, it is assumed that eSIM Port 0 (1l-20) is a port for management purposes that can only be accessed by ISD-R, and eSIM Port 1 (1l-30) is a port for non-management purposes that should not affect other ports. Assume and explain. If, in eUICC (1l-01), ISD-R sends Proactive Command including port number(s) or all ports (all) to (1l-40) to the modem through eSIM Port 0 (1l-20). In this case, as a result of the modem checking the received Proactive Command, if there is a Proactive Command including port number(s) or all ports (all), the modem processes the corresponding Proactive Command as described above in FIG. 1h can be performed. If the port number received from (11-40) is #1, the modem 11-10 transmits a polling message as to whether there is a message to be FETCHed to (11-70) or the modem 11-10 After performing all reset processing procedures for this port 1, it is also possible to transmit a reset command for the corresponding port. If the eUICC (1l-10) receives the Reset Command as (11-70), but it is different from the port number included in the Proactive Command transmitted from the eUICC (11-01) to (1l-40), eUICC ( 1l-10) may additionally reply to the modem 1l-10 with this error to inform the modem that it should transmit the Reset Command to the port number included in the Proactive Command transmitted from (11-40) again. can

If, in eUICC (11-01), ISD-R transmits (1l-60) a Proactive Command including port number(s) or all ports (all) to the modem through eSIM Port 1 (1l-30) As a result, the modem checks the received Proactive Command. If it is a Proactive Command including port number(s) or all ports (all), the modem rejects the process and returns an error as (11-70). can do.

In the specific embodiments of the present disclosure described above, components included in the present disclosure are expressed in the singular or plural according to the specific embodiments presented. However, the singular or plural expression is appropriately selected for the context presented for convenience of description, and the present disclosure is not limited to the singular or plural component, and even if the component is expressed in plural, it is composed of the singular or singular. Even an expressed component may be composed of a plurality of components.

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

Claims (8)

A method of a terminal in a wireless communication system, comprising:
transmitting, to the manager server, an authentication request message including port identification information;
receiving, from the manager server, an authentication response message generated based on the port identification information, including profile information for management and port information for management; and
The method of a terminal comprising the step of performing profile management based on the profile information for the management and information on the port mapped to the profile for the management. The method of claim 1,
The port identification information is
A method of a terminal, characterized in that it may include at least one of port number information, IMEI (international mobile equipment identities) information mapped to a port, and Radio Access Technologies (RAT) information of a baseband used by the port . The method of claim 1,
The method of the terminal, characterized in that it further comprises the step of transmitting, to the manager server, a management processing response message including the management result and the port identification information on which the management was performed. The method of claim 1,
The step of performing profile management based on the profile information for the management and information on the port mapped to the profile for the management includes:
checking a profile for the mapped port; and
and performing a management command related to the verified profile based on a management command included in the authentication response message. In a terminal in a wireless communication system,
a transceiver for transmitting and receiving a signal;
an embedded universal integrated circuit card (eUICC) that manages a profile; and
Transmitting an authentication request message including port identification information to the manager server, and from the manager server, an authentication response message including profile information for management and port information for management, generated based on the port identification information and a control unit configured to control to perform profile management based on the profile information for the management and information on the port mapped to the profile for the management. 6. The method of claim 5,
The port identification information is
The terminal, characterized in that it may include at least one of port number information, IMEI (international mobile equipment identities) information mapped to the port, and Radio Access Technologies (RAT) information of a baseband used by the port. 6. The method of claim 5,
The control unit is
The terminal, characterized in that it controls to transmit a management processing response message including the management result and the port identification information on which the management is performed, to the manager server. 6. The method of claim 5,
The control unit is
Checking the profile for the mapped port, based on the management command included in the authentication response message, characterized in that the control to perform a management command related to the identified profile terminal.

Images