METHOD AND APPARATUS TO INSTALL AND MANAGE MULTIPLE eSIM PROFILES

Abstract

The present disclosure relates to a communication technique and a system for integrating a 5G communication system with IoT technology to support higher data transmission rates than those of 4G systems. The present disclosure may be applied to intelligent services (e.g., smart homes, smart buildings, smart cities, smart cars or connected cars, healthcare, digital education, retail, security and safety-related services, etc.) based on 5G communication technology and IoT-related technology. A method of a terminal in a wireless communication system is provided. The method comprises the steps of: transmitting an authentication request message including port identification information to a manager server; receiving an authentication response message from the manager server, which includes profile information for management and port information for management, generated based on the port identification information; and performing profile management based on the profile information for management and information regarding a port mapped to the profile for management. The present invention provides a method and apparatus for providing dual SIM functionality even in a terminal equipped with a single eUICC. In particular, according to one embodiment of the present invention, the invention includes a method of providing a terminal user with a screen that allows the user to determine the port to be used for Local Profile activation by considering the profile activation status of the eUICC and 'eSIM port Capability', or a method in which the terminal notifies a profile server of the terminal's 'eSIM port Capability' information, a method in which the profile server checks the 'eSIM port Capability' information and selects a profile to be processed for remote profile activation (RPM-Enable), a method in which the profile server transmits the profile information selected for the corresponding remote profile activation (RPM-Enable) to the terminal, and a method in which the terminal obtains information for determining the eSIM port to be used by the profile. Additionally, when the eUICC at the terminal receives a request for eUICC memory reset or profile status change, the invention may provide a method in which the eUICC selectively configures a REFRESH message and transmits it to the modem separately depending on whether the modem supports MEP.

Description

Technology Field

[0001] The present invention relates to a method and apparatus for establishing a communication connection by downloading and installing one or more communication services on a terminal in a wireless communication system. Furthermore, the present invention relates to a method and apparatus for remotely downloading and installing profiles on a terminal and managing a plurality of installed profiles. Background Technology

[0002] Efforts are being made to develop improved 5G communication systems or pre-5G communication systems to meet the increasing demand for wireless data traffic following the commercialization of 4G communication systems. For this reason, 5G communication systems or pre-5G communication systems are referred to as systems beyond 4G networks or systems following LTE (Long Term Evolution) systems. To achieve high data transmission rates, the implementation of 5G communication systems in the mmWave band (e.g., the 60 GHz band) is being considered. In order to mitigate path loss and increase the transmission distance of radio waves in the ultra-high frequency band, beamforming, massive array multiple input / output (massive MIMO), full-dimensional multiple input / output (Full Dimensional MIMO: FD-MIMO), array antenna, analog beam-forming, and large-scale antenna technologies are being discussed in 5G communication systems. In addition, to improve the system's network, technologies such as advanced small cells, advanced small cells, cloud radio access networks (cloud RAN), ultra-dense networks, device-to-device communication (D2D), wireless backhaul, moving networks, cooperative communication, Coordinated Multi-Points (CoMP), and interference cancellation are being developed in 5G communication systems.In addition, advanced coding modulation (ACM) methods such as FQAM (Hybrid FSK and QAM Modulation) and SWSC (Sliding Window Superposition Coding), as well as advanced access technologies such as FBMC (Filter Bank Multi Carrier), NOMA (non-orthogonal multiple access), and SCMA (sparse code multiple access), are being developed in 5G systems.

[0003] Meanwhile, the Internet is evolving from a human-centric network where humans generate and consume information into an IoT (Internet of Things) network that processes information by exchanging it among distributed components, such as objects. IoE (Internet of Everything) technology, which combines IoT with Big Data processing technologies through connections with cloud servers, is also emerging. To implement IoT, technological elements such as sensing technology, wired and wireless communication and network infrastructure, service interface technology, and security technology are required; consequently, technologies such as sensor networks, Machine-to-Machine (M2M) communication, and Machine-Type Communication (MTC) are currently being researched to facilitate the connection of objects. In an IoT environment, intelligent IT services that create new value for human life by collecting and analyzing data generated from connected objects can be provided. Through the convergence and integration of existing IT technologies with various industries, IoT can be applied to fields such as smart homes, smart buildings, smart cities, smart or connected cars, smart grids, healthcare, smart home appliances, and advanced medical services.

[0004] Accordingly, various attempts are being made to apply existing 4G and 5G communication systems to IoT networks. For example, technologies such as sensor networks, machine-to-machine (M2M) communication, and machine-type communication (MTC) are being implemented using 4G and 5G communication technologies such as beamforming, MIMO, and array antennas.

[0005] A UICC (Universal Integrated Circuit Card) is a smart card inserted into a mobile communication terminal or similar device, and is also referred to as a UICC card. The UICC may include a connection control module for connecting to a mobile communication operator's network. Examples of such connection control modules include USIM (Universal Subscriber Identity Module), SIM (Subscriber Identity Module), and ISIM (IP Multimedia Service Identity Module). A UICC containing a USIM is commonly referred to as a USIM card. Similarly, a UICC containing 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 the conventional sense to include UICC cards, USIM cards, and UICCs containing ISIM. That is, even if referred to as a SIM card, its technical application can be equally applied to USIM cards, ISIM cards, or general UICC cards.

[0006] The above SIM card stores the personal information of a mobile communication subscriber and enables secure mobile communication by performing subscriber authentication and generating a traffic security key when connecting to a mobile communication network.

[0007] The aforementioned SIM card is generally manufactured as a dedicated card for a specific mobile carrier at the request of that carrier during production. Authentication information for accessing the carrier's network, such as the USIM (Universal Subscriber Identity Module) application, IMSI (International Mobile Subscriber Identity), K value, and OPc value, is pre-loaded onto the card before shipment. Consequently, the manufactured SIM card is received by the mobile carrier and provided to subscribers; subsequently, if necessary, management functions such as the installation, modification, and deletion of applications within the UICC can be performed using technologies such as OTA (Over The Air). Subscribers can use the carrier's network and application services by inserting the UICC card into their mobile terminals. Furthermore, upon replacing the terminal, the authentication information, mobile phone numbers, and personal phonebooks stored on the UICC card can be transferred from the old terminal to the new terminal, allowing the new terminal to continue using the information.

[0008] However, the aforementioned SIM card presents an inconvenience for mobile device users in receiving services from other mobile carriers. Users of mobile devices face the inconvenience of having to physically obtain a SIM card to receive services from a mobile carrier. For example, when traveling to another country, users face the inconvenience of having to obtain a local SIM card to receive local mobile services. While roaming services resolve this inconvenience to some extent, there are also issues such as high fees and the inability to receive services if there is no contract between carriers.

[0009] Meanwhile, if the above SIM module is remotely downloaded and installed on the UICC card, this inconvenience can be largely resolved. That is, the user can download the SIM module of the mobile communication service they wish to use onto the UICC card at their desired time. Such a UICC card can also download and install multiple SIM modules and select only one of them for use. Such a UICC card may or may not be fixed to the terminal. In particular, a UICC that is fixed to the terminal is called an eUICC (embedded UICC); typically, an eUICC refers to a UICC card that is fixed to the terminal and allows for the remote download and selection of a SIM module. In the present invention, UICC cards that allow for the remote download and selection of a SIM module will be collectively referred to as eUICC. That is, among UICC cards that allow for the remote download and selection of a SIM module, both UICC cards fixed to the terminal and UICC cards that are not fixed will be collectively referred to as eUICC. Additionally, the term "Profile" will be used to collectively refer to the downloaded SIM module information.

[0010] Even if there is more than one profile within the eUICC mentioned above, only one can be enabled at a time. Therefore, even if a terminal supports two Baseband(s) and there are two or more profiles in the eUICC, the terminal cannot support the Dual SIM function, which allows two profiles to be used simultaneously on a single mobile phone. This can be resolved by equipping the terminal with two eUICC(s); however, since this requires the installation of an additional eUICC module and a physical interface to connect the eUICC module to the modem's Baseband, the terminal manufacturer must bear the cost associated with purchasing additional eUICC modules and physical pins for the physical interface. Furthermore, securing mounting space on the terminal due to the introduction of such modules and physical pins also becomes a problem. The problem to be solved

[0011] When attempting to activate a profile installed in an eUICC on a MEP-supported terminal locally by a user or remotely by a profile server, it is necessary to process the simultaneous activation of one or more profiles by additionally obtaining and combining certain information, such as the number of profiles that can be simultaneously activated provided by the terminal, the combination of Basebands supported by the modem, and whether the profile occupies and uses the Baseband.

[0012] Currently, in eUICC, only one eSIM profile can be activated at a time, so when Profile 1 is activated, if there is Profile 2 connected to the network, Profile 2 is deactivated, causing the communication connection of Profile 2 to be disconnected.

[0013] Meanwhile, since the eUICC is connected to one baseband of the modem through one physical interface, the eUICC does not distinguish between the eUICC memory reset message and the profile disabled message transmitted to the modem. However, in the case of a terminal that allows MEP, if these are not distinguished, there is a problem in that the modem can delete all cached data, including the cached data of Profile 2 stored in the modem, and this needs to be resolved. means of solving the problem

[0014] The technical problem that the present invention aims to solve is to provide a method and apparatus for installing, activating, and managing multiple profiles so that Dual SIM functionality can be provided even in a terminal equipped with a single eUICC in a communication system.

[0015] According to one embodiment of the present invention, a method for a terminal in a wireless communication system is provided. The method comprises: transmitting an authentication request message including port identification information to a manager server; receiving an authentication response message from the manager server including profile information for management and port information for management, generated based on the port identification information; and performing profile management based on the profile information for management and information regarding a port mapped to the profile for management.

[0016] In addition, according to another embodiment of the present invention, a terminal in a wireless communication system is provided. The terminal is characterized by comprising: a transceiver for transmitting and receiving signals; an embedded universal integrated circuit card (eUICC) for managing profiles; and a control unit for transmitting an authentication request message including port identification information to a manager server, receiving an authentication response message from the manager server including profile information for management and port information for management generated based on the port identification information, and controlling the performance of profile management based on the profile information for management and information regarding a port mapped to the profile for management.

[0017] In particular, the present invention includes the following embodiments for the above purpose.

[0018] - How the device informs the profile server of its 'eSIM port Capability' information

[0019] - How the profile server checks 'eSIM port Capability' information to select the profile to activate remotely and the eSIM port to activate the profile on

[0020] - A method of providing a terminal user with a screen that allows the terminal to determine the port to use by considering the eUICC profile activation status and 'eSIM port Capability', thereby enabling the terminal to determine the eSIM port to use by the profile.

[0021] - Method of transmitting the corresponding eSIM port information from the terminal's LPA to the eUICC

[0022] - Method to receive the corresponding port information and activate the profile on that port in eUICC

[0023] In addition, the present invention includes the following embodiments for the above purpose.

[0024] - A method in which, when the eUICC receives a message from the terminal's LPA in MEP mode regarding a request for an eUICC memory reset or profile state change, the eUICC distinguishes a message for refresh processing based on the state change within the eUICC according to the message received from the terminal's LPA and transmits it to the terminal's LPA or modem.

[0025] - A method in which a modem that receives the message via LPA or directly from eUICC operates differently depending on the received message and the port number included in the received message.

[0026] The technical problems to be solved by the present invention are not limited to those mentioned above, and other technical problems not mentioned will be clearly understood by those skilled in the art to which the present invention belongs from the description below. Effects of the invention

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

[0028] Dual SIM functionality can be provided, and manufacturing costs can be reduced as the introduction of an additional eUICC is unnecessary. The profile management server can obtain information on which eSIM port of the MEP terminal to activate the profile and request the profile activation process to the optimal port of the corresponding user terminal. Profile 1 and Profile 2, which are simultaneously activated in the eUICC, can operate within a single eUICC without mutual interference (such as the termination of network connection for Profile 2 due to the activation of Profile 1), so the carrier of Profile 1 or Profile 2 can provide stable network services. Brief explanation of the drawing

[0029] FIG. 1a is a drawing showing the components of the present invention in a wireless communication system according to an embodiment of the present invention. Figure 1ba is a diagram showing the connection between the current v2 eUICC and the modem (case 1) that does not support MEP. Figure 1bb is a diagram showing the connection between the current v2 eUICC and the modem (case 2) that does not support MEP. Figure 1ca is a diagram showing the connection between the v3 eUICC and the modem (case 1) following the introduction of the Virtual Interface concept. Figure 1cb is a diagram showing the connection between the v3 eUICC and the modem (case 2) following the introduction of the Virtual Interface concept. FIG. 1da is a sequence example diagram showing how the ISD-R of the eUICC transmits a REFRESH message (case 1) to the modem to change the state of the Profile. Figure 1db is a sequence example diagram showing how the ISD-R of the eUICC transmits a REFRESH message (case 2) to the modem for memory reset. FIG. 1e is a sequence example diagram showing a method for processing local profile activation in a terminal to which the present invention is applied. FIG. 1fa is an example illustration of an implementation of a profile management screen (case 1) provided to a terminal user in an MEP-supported terminal to which the present invention is applied. FIG. 1fb is an example illustration of an implementation of a profile management screen (case 2) provided to a terminal user in an MEP-supported terminal to which the present invention is applied. FIG. 1fc is an example illustration of an implementation of a profile management screen (case 3) provided to a terminal user in an MEP-supported terminal to which the present invention is applied. FIG. 1fd is an example illustration of an implementation of a profile management screen (case 4) provided to a terminal user in an MEP-supported terminal to which the present invention is applied. FIG. 1g is a sequence example diagram showing a method for processing remote profile activation (RPM-Enable) in a terminal and profile server to which the present invention is applied. Figure 1h is an example diagram of the sequence for determining the processing of a received REFRESH Command at a modem. Figure 1ia is a diagram showing the Multi-Selected ISD-R among the connections between v3 eUICC and modems (case 1) following the introduction of the Virtual Interface concept. Figure 1ib is a diagram showing the Multi-Selected ISD-R among the connections between v3 eUICC and modems (case 2) following the introduction of the Virtual Interface concept. FIG. 1j is a diagram showing a terminal block configuration according to an embodiment of the present invention. FIG. 1k is a diagram showing a Refresh method that does not use a Proactive Command according to an embodiment of the present invention. FIG. 11 is a diagram illustrating a method in which a modem according to an embodiment of the present invention processes Proactive Commands received from a port for management purposes and a port for non-management purposes differently. Specific details for implementing the invention

[0030] The operating principles of the present disclosure will be described in detail below with reference to the attached drawings. In describing the present disclosure below, specific descriptions of related known functions or configurations will be omitted if it is determined that such detailed descriptions would unnecessarily obscure the essence of the present disclosure. Furthermore, the terms described below are defined in consideration of their functions in the present disclosure, and these may vary depending on the intentions or conventions of the user or operator. Therefore, their definitions should be based on the content throughout this specification. For the same reason, some components in the attached drawings may be exaggerated, omitted, or schematically depicted. Additionally, the size of each component does not entirely reflect its actual size. Identical or corresponding components in each drawing are assigned the same reference number. The advantages and features of the technical concept according to the present disclosure, and the methods for achieving them, will become clear by referring to the embodiments described in detail below in conjunction with the attached drawings. However, the present disclosure is not limited to the embodiments disclosed below but may be implemented in various different forms. These embodiments are provided merely to ensure that the present disclosure is complete and to fully inform those skilled in the art of the scope of the invention, and the present disclosure is defined only by the scope of the claims. Throughout the specification, the same reference numerals refer to the same components. Furthermore, in describing the present disclosure, if it is determined that a detailed description of a related function or configuration might unnecessarily obscure the essence of the technical concept according to the present disclosure, such detailed description is omitted. Additionally, the terms described below are defined considering their functions in the present disclosure, and these may vary depending on the intentions or conventions of the user or operator. Therefore, their definitions should be based on the content throughout the entire specification.

[0031] Hereinafter, the base station is an entity that performs resource allocation for terminals and may be at least one of a gNode B, eNode B, Node B, BS (Base Station), wireless access unit, base station controller, or a node on a network. The terminal may include a UE (User Equipment), MS (Mobile Station), cellular phone, smartphone, computer, or a multimedia system capable of performing communication functions. In this disclosure, the Downlink (DL) refers to the wireless transmission path of a signal transmitted by a base station to a terminal, and the Uplink (UL) refers to the wireless transmission path of a signal transmitted by a terminal to a base station. Furthermore, while LTE or LTE-A systems may be described as examples below, embodiments of this disclosure may also be applied to other communication systems having similar technical backgrounds or channel types. For example, 5th generation mobile communication technology (5G, new radio, NR) developed after LTE-A may be included in a system to which embodiments of this disclosure can be applied, and the 5G below may be a concept that includes existing LTE, LTE-A, and other similar services. Furthermore, the present disclosure may be applied to other communication systems with some modifications made at the discretion of a person with skilled technical knowledge, without departing significantly from the scope of the present disclosure. In this case, it will be understood that each block of the process flow diagrams and combinations of the flow diagrams may be executed by computer program instructions.

[0032] Since these computer program instructions can be loaded onto the processor of a general-purpose computer, a computer for special purposes, or other programmable data processing equipment, the instructions executed through the processor of the computer or other programmable data processing equipment create means for performing the functions described in the flowchart block(s). Since these computer program instructions can also be stored in computer-available or computer-readable memory that can be directed toward the computer or other programmable data processing equipment to implement functions in a specific way, the instructions stored in computer-available or computer-readable memory can also produce a manufactured item containing means of instruction for performing the functions described in the flowchart block(s). Since the computer program instructions can also be loaded onto the computer or other programmable data processing equipment, the instructions that perform a series of operation steps on the computer or other programmable data processing equipment to create a computer-executable process can also provide steps for performing the functions described in the flowchart block(s).

[0033] Additionally, each block may represent a module, segment, or part of code containing one or more executable instructions for executing a specific logical function(s). Also, it should be noted that in some alternative execution examples, the functions mentioned in the blocks may occur out of order. For example, two blocks described in succession may actually be executed substantially simultaneously, or the blocks may be executed in reverse order depending on the corresponding function. In this case, the term "part" as used in this embodiment refers to software or hardware components such as a Field Programmable Gate Array (FPGA) or an Application Specific Integrated Circuit (ASIC), and the "part" may perform certain roles. However, the meaning of "part" is not limited to software or hardware. The "part" may be configured to reside in an addressable storage medium or configured to run one or more processors. Accordingly, as an example, 'part' includes components such as software components, object-oriented software components, class components, and task components, as well as processes, functions, attributes, procedures, subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables. The functions provided within the components and 'parts' may be combined into a smaller number of components and 'parts' or further separated into additional components and 'parts'. Furthermore, the components and 'parts' may be implemented to utilize one or more CPUs within a device or secure multimedia card. Additionally, in an embodiment, 'part' may include one or more processors.

[0034] First, the terms used in this specification are defined.

[0035] In this specification, UICC refers to a chip that enables secure mobile communication by performing subscriber authentication and traffic security key generation when connected to a mobile communication system such as GSM, WCDMA, LTE, or 5G, by storing personal information such as network access authentication information, phone book, and SMS of a mobile communication subscriber, which is inserted into a mobile communication terminal. Depending on the type of mobile communication network connected by the subscriber, communication applications such as SIM (Subscriber Identification Module), USIM (Universal SIM), and ISIM (IP Multimedia SIM) are installed in the UICC, and it can also provide high-level security functions for the installation of various applications such as electronic wallets, ticketing, and electronic passports.

[0036] In this specification, eUICC (embedded UICC) is a security module embedded in a terminal that is not removable and can be inserted into or removed from the terminal. eUICC can download and install profiles using OTA (Over The Air) technology. eUICC may be referred to as a UICC capable of downloading and installing profiles.

[0037] In this specification, the method of downloading and installing a profile on an eUICC using OTA technology can also be applied to a detachable UICC that can be inserted into and removed from a terminal, as described above. For example, the embodiments of the present invention can be applied to a UICC capable of downloading and installing a profile using OTA technology.

[0038] In this specification, the term UICC may be used interchangeably with SIM, and the term eUICC may be used interchangeably with eSIM. In this specification, eUICC may be used interchangeably with UICC, and UICC may be used as a concept that encompasses eUICC. Meanwhile, UICC may be used interchangeably with SE as a type of SE (Secure Element).

[0039] In this specification, "Profile" may refer to an application, file system, authentication key value, etc., stored within the UICC packaged in the form of software. Additionally, the profile may be referred to as connection information.

[0040] In this specification, USIM Profile may have the same meaning as Profile or refer to information included in a USIM application within a Profile packaged in the form of software.

[0041] In this specification, the profile server is a server that provides functions for creating a profile, encrypting a created profile, creating a profile remote management command, encrypting a created profile remote management command, or supporting multiple profile activation of a terminal, and may be expressed as SM-DP (Subscription Manager Data Preparation), SM-DP+ (Subscription Manager Data Preparation plus), and SM-SR (Subscription Manager Secure Routing).

[0042] As used herein, the terms 'terminal' or 'device' may be referred to as a mobile station (MS), user equipment (UE), user terminal (UT), wireless terminal, access terminal (AT), terminal, subscriber unit, subscriber station (SS), wireless device, wireless communication device, wireless transmit / receive unit (WTRU), mobile node, mobile, or other terms. Various embodiments of a terminal may include a cellular telephone, a smartphone with wireless communication capabilities, a personal digital assistant (PDA) with wireless communication capabilities, a wireless modem, a portable computer with wireless communication capabilities, a shooting device such as a digital camera with wireless communication capabilities, a gaming device with wireless communication capabilities, a music storage and playback appliance with wireless communication capabilities, an internet appliance capable of wireless internet access and browsing, as well as portable units or terminals integrating combinations of such capabilities. Additionally, a terminal may include, but is not limited to, a Machine-to-Machine (M2M) terminal and a Machine-Type Communication (MTC) terminal / device. In this specification, the terminal may be referred to as an electronic device or simply a device. Additionally, in this specification, the term terminal may be used interchangeably with modem.

[0043] In this specification, the terminal or device may include software or an application installed within the terminal or device to control a UICC or an eUICC. The software or application may be referred to, for example, as a Local Profile Assistant (LPA). In this 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.

[0044] In this specification, an APDU (application protocol data unit) may be a message for a controller within a terminal or device to interact with an eUICC.

[0045] In this specification, "Profile Package" may be used interchangeably with "Profile" or as a term representing a data object of a specific profile, and may be named "Profile TLV" or "Profile Package TLV". The profile identifier may be referred to as an ICCID, which is the unique identification number of the profile. If the profile package is encrypted using encryption parameters, it may be named "Protected Profile Package (PPP)" or "Protected Profile Package TLV" (PPP TLV). If the profile package is encrypted using encryption parameters that can be decrypted only by a specific eUICC, it may be named "Bound Profile Package (BPP)" or "Bound Profile Package TLV" (BPP TLV). A profile package TLV may be a data set representing information constituting a profile in the TLV (Tag, Length, Value) format.

[0046] In this specification, AKA may represent Authentication and Key agreement and may represent an authentication algorithm for accessing 3GPP and 3GPP2 networks. K is a cryptographic key value stored in an eUICC used in the AKA authentication algorithm, and in this specification, OPc is a parameter value that can be stored in an eUICC used in the AKA authentication algorithm.

[0047] In this specification, NAA is a Network Access Application, and may be an application such as a USIM or ISIM stored in a UICC for connecting to a network. NAA may be a network access module.

[0048] In the present invention, End user, user, subscriber, service subscriber, and user may be used interchangeably as the user of the corresponding terminal.

[0049] In the present invention, the eSIM port refers to a virtual interface channel that uses multiplexing to divide the physical interface connected to the eUICC - modem, and may be used interchangeably with eSIM port, eSIM port, eSIM port, port, and SIM port.

[0050] In the present invention, the function of activating and managing multiple profiles existing in a single eUICC is collectively referred to as the Multiple Enabled Profile (MEP) function. Conventional eUICCs can only activate a maximum of one profile, so a single eUICC cannot support Dual SIM or Multi SIM functions. To support Dual SIM or Multi SIM functions with a single eUICC, a function is required to activate and manage multiple profiles within the single eUICC. An eUICC with an implemented MEP function may be referred to as an MEP-supported eUICC. A terminal including a modem with an implemented MEP function and terminal software capable of supporting it may be referred to as an MEP-supported terminal.

[0051] Furthermore, in describing the present invention, if it is determined that a detailed description of related known functions or configurations could unnecessarily obscure the essence of the invention, such detailed description is omitted.

[0052] The following describes an embodiment proposed through the drawings.

[0053] FIG. 1a is a drawing showing the components of the present invention in a wireless communication system according to an embodiment of the present invention.

[0054] The user (1a-01) requests the installation / activation / deactivation / update of a profile to the eUICC (1a-20) through the LPA (1a-05) of the terminal (1a-03) or a terminal application in which the LPA (1a-05) is implemented, or provides permission for the user to process Remote Profile Management (RPM) transmitted from the SM-DP+ (1a-40).

[0055] Remote Profile Management (RPM) is a collective term for 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. RPM may be requested by a telecommunications carrier, a service provider, or the owner of the terminal, and commands may be generated by SM-DP+ (1a-40). Upon receiving user input regarding a request for or permission for the management of the relevant profile, the LPA (1a-05) can manage / control the operation of the eUICC (1a-20) by transmitting a message to the eUICC (1a-20) according to the user input.

[0056] The communication modem (1a-15) of the terminal is a device that modulates and transmits a signal for information transmission and demodulates it to restore the original signal at the receiving end. In the case of a modem that supports MEP, two or more Baseband Processors (hereinafter Baseband) for wireless communication may be installed. The modem (1a-15) is connected to an eUICC by one physical pin (the ISO7816 standard is applied as a Smart Card Interface at the time of disclosing the present invention), and operates in such a way that when the modem transmits an APDU (Application Protocol Data Unit) Command through the interface, the eUICC (1a-20) responds with a result value.

[0057] Meanwhile, if the eUICC (1a-20) has a message to transmit to the modem (1a-15), it can send a response code (e.g., SW1 (Status word)=91, SW2=XX) indicating that the eUICC (1a-20) has a message to transmit as a reply to the APDU Command transmitted by the modem (1a-15). Through this, the eUICC (1a-20) can notify the modem (1a-15) so that the modem (1a-15) can receive this "message to be transmitted by the eUICC (1a-20) to the modem (1a-15)" through the basic channel.

[0058] The modem (1a-15) transmits a FETCH Command APDU to the eUICC (1a-20) via the basic channel, and the eUICC (1a-20) can transmit a Response APDU in response. At this time, a message to be transmitted from the eUICC, such as a Proactive Command, may be included in the Data portion. The Proactive Command may be, for example, a request for UICC Reset or Profile State Change processing. Further details regarding this will be described in detail in FIGS. 1d and 1h.

[0059] Meanwhile, the LPA (1a-05) is software that operates on a terminal platform, and the functions of the LPA may be partially integrated into the terminal platform. Messages transmitted from the LPA (1a-05) to the eUICC (1a-20) are finally transmitted to the eUICC (1a-20) via the terminal platform or the terminal platform and the modem (1a-15), and the eUICC (1a-20), upon receiving the message, performs profile management operations of the eUICC according to the command transmitted from the LPA.

[0060] In FIG. 1a, for the convenience of the following explanation, it is assumed that there are two profiles, Profile 1 and Profile 2, in the eUICC (1a-20), but it should be noted that this is not limited to this and more profiles may exist depending on the memory capability of the eUICC (1a-20). In an eUICC that supports MEP, Profile 1 (1a-25) and Profile 2 (1a-30) can be activated simultaneously, and in an eUICC that does not support MEP, only one of Profile 1 (1a-25) or Profile 2 (1a-30) can be activated.

[0061] ISD-R(1a-35) creates a new ISD-P (meaning a Security Domain for hosting profiles) and provides the necessary eUICC data and services required by the LPA function—e.g., local profile management, profile metadata information—to the LPA.

[0062] Meanwhile, the eUICC (1a-20) of the drawing (1a-03) may include, for convenience of explanation, an ECASD (Embedded UICC Controlling Authority Security Domain) and an eSIM platform, which are spaces for storing credentials required by the security domains of the eUICC, such as the Certificate Issuer's Root public Key for verifying SM-DP+ certificates and the eUICC manufacturer's keyset.

[0063] As described above, the SM-DP+ server (1a-40) refers to a server that includes the function of creating a profile, encrypting the created profile, creating a profile remote management command, encrypting the created profile remote management command, or supporting the activation of multiple profiles of the terminal. The LPA (1a-05) of the terminal (1a-03) receives the SM-DP+ remote management command from the SM-DP+ server (1a-40), obtains user consent through interaction with the user (1a-01), and then transmits the corresponding remote management command from the LPA (1a-05) to the eUICC (1a-20) to perform activation / deactivation / deletion / update processing.

[0064] The eUICC (1a-20) may be fixed to the terminal or detachable. If the eUICC (1a-20) is fixed to the terminal, it can be indicated as one of the entities of the terminal (1a-03); however, in this drawing, it is indicated as a separate entity (1a-03) from the terminal to include the detachable eUICC (1a-20).

[0065] Figures 1ba and 1bb are diagrams showing the connection between the current v2 eUICC and the modem that does not support MEP.

[0066] Currently, in v2 eUICC, only a single profile can be activated in the eUICC, and only local profile management by the user is possible without the intervention of SM-DP+ to handle activation / deactivation / deletion / update of installed profiles. In the case of a modem that does not support MEP (1b-01), it may have more than one baseband, considering cases such as when a physical SIM card is used simultaneously with the eUICC, but in this description, we will explain assuming one baseband.

[0067] During the initialization procedure between the terminal platform, Modem, and eUICC (terminal-card initialization), the terminal can create a channel for APDUs to transmit and receive data between the modem and eUICC at a specific time after receiving an ATR (Answer to Reset) from the eUICC.

[0068] In v2 eUICC(1b-15), only one profile can be activated at a time.

[0069] Csse1 (1b-100) in Fig. 1ba represents the case where Profile 1 (1b-20) is enabled and Profile 2 (1b-25) is disabled, and Case 2 (1b-200) in Fig. 1bb represents the case where Profile 1 (1b-20) is disabled and Profile 2 (1b-25) is enabled. Taking Case 1 (1b-100) as an example, when APDU transmission to the modem's Baseband is required from one of the enabled profiles, the eUICC (1b-15) can transmit the corresponding APDU through a single channel of the Physical Interface (1b-10) connected to the modem (1b-01).

[0070] Meanwhile, when ISD-R (1b-30) receives an ES10c.EnableProfile(Profile2) request from LPA for a change in the state of a profile, for example, from Case 1 (1b-100) to Case 2 (1b-200), ISD-R (1b-30) can send a REFRESH Proactive Command to the modem (1b-10) to delete the data of the existing cached profile and restart the application session.

[0071] Additionally, when the ISD-R (1b-30) receives a request from the LPA to reset the eUICC memory, the ISD-R (1b-30) can send an APDU to the modem (1b-10) as a REFRESH Proactive Command to delete the data of the existing cached UICC and restart the application session. The corresponding APDU sent by the ISD-R (1b-30) to the modem (1b-01) can also be transmitted through a single channel of the aforementioned Physical Interface (1b-10).

[0072] Figures 1ca and 1cb are diagrams illustrating the connection between a v3 eUICC and a modem following the introduction of the Virtual Interface concept.

[0073] The eUICC (1c-20) in FIG. 1ca and FIG. 1cb is assumed to be an eUICC that supports MEP functionality capable of activating multiple profiles simultaneously. Meanwhile, the modem (1c-01) is also assumed to be a modem that supports MEP functionality. In 1c, a situation with two Basebands and two activated profiles is explained as an example, and while a mapping switch between the Baseband and the eSIM port within the modem (1c-01) may be possible, in Case 1 and Case 2, the mapping of logical terminal endpoints within the modem (1c-01) is explained as Baseband 1 (1c-05)-Channel 1 (1-40) and Baseband 2 (1c-10)-Channel 2 (1-45).

[0074] As previously described in FIG. 1ba and FIG. 1bb, the current modem (1a-15) is connected to the eUICC (1a-20) via a single physical pin, and the modem and the eUICC transmit APDU commands using a single channel (1b-10) through that physical pin. The eUICC (1c-20) that supports MEP activates multiple profiles, and the activated profiles require APDU transmission with a specific baseband of the modem. Therefore, a concept can be introduced in which the Physical Interface (1c-15) for processing this is multiplexed to distinguish the APDU and transmit it through multiple channels (1c-40, 1c-45).

[0075] For convenience of explanation below, when MEP is supported, the channel will be designated as an eSIM port, and each channel will be designated as eSIM Port 1 (1c-40) and eSIM Port 2 (1c-45) and used as an eSIM port. After a UICC Reset or Profile Status Change, the terminal may create an APDU channel for transmission between the modem baseband and the eUICC during the initialization process between the terminal platform, the modem, and the eUICC. At this time, an ID for the eSIM port connected to each baseband may be set. The corresponding port ID can be set on the modem or the terminal platform and transmitted to the LPA. For convenience of explanation in this specification, the port ID is used interchangeably with the port number.

[0076] 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 equal to or less than the number of profiles that can be simultaneously activated in the eUICC. A profile can send APDU messages using one of the eSIM ports.

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

[0078] In Fig. 1cb Case 2 (1c-200), an APDU Command corresponding to the activated Profile 1 (1c-25) can be transmitted to Baseband 2 (1c-10) through eSIM port 2 (1c-45), and at the same time, an APDU Command corresponding to the activated Profile 2 (1c-30) can be transmitted to Baseband 1 (1c-05) through eSIM port 2 (1c-40).

[0079] The MEP-supported 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 APDU Commands to the modem for profile and eUICC status management. In this case, the ISD-R (1c-35) can transmit in two ways.

[0080] 1) Multi-Selected: During the initialization process between the eUICC and the terminal-card, the LPA or modem may determine the ISD-R (1c-35) by selecting it through multiple eSIM ports, or it may operate by selecting the ISD-R (1c-35) through multiple eSIM ports according to the configuration between the terminal and the card. This state can be called Multi-Selected. In the case of Multi-Selected, the LPA or modem may send a command APDU (command message) to the ISD-R (1c-35) through one of the selected eSIM ports, or transmit a command APDU for the purpose of checking whether there is an event that the ISD-R (1c-35) needs to process or an APDU that needs to be transmitted. The ISD-R (1c-35) can select a corresponding eSIM port depending on whether the command message received from the LPA or modem is a management message corresponding to Profile 1 (1c-25) or Profile 2 (1c-30), a management message corresponding to Profile 1 (1c-25) and Profile 2 (1c-30), or a message for the entire eUICC, and send an APDU containing a proactive command to that port. Alternatively, in the case of a Multi-selected ISD-R, the ISD-R may also send a management message corresponding to Profile 1 (1c-25) and Profile 2 (1c-30) or a message for the entire eUICC through the eSIM Port selected by the LPA or modem for the transmission of the command message. A diagram of the Multi-Selected is additionally illustrated in FIG. 1ia and FIG. 1ib.

[0081] 2) Non Multi-Selected: During the initialization process between the eUICC and the terminal-card, the LPA or modem may decide to select the ISD-R (1-35) using only one eSIM port, or it may operate to select the ISD-R (1c-35) using one eSIM port depending on the configuration between the terminal and the card. This state can be called Non Multi-Selected. In the case of Non Multi-Selected, APDU can be transmitted and received between the terminal and the ISD-R (1c-35) only through the single eSIM port that has been selected. The eSIM port used by the ISD-R may be the same as the eSIM port occupied by the profile, or it may be an independent eSIM port dedicated to the ISD-R. When ISD-R (1c-35) needs to send a response APDU containing a proactive command to a modem, if ISD-R (1c-35) sends the response APDU to the modem (1c-01) via the eSIM port selected by ISD-R (1c-35), the modem (1c-01) can interpret the information of the received response APDU and execute the requested command.

[0082] FIG. 1da is a sequence example diagram showing how the ISD-R of the eUICC transmits a REFRESH message (case 1) to the modem to change the state of the Profile.

[0083] Figure 1db is a sequence example diagram showing how the ISD-R of the eUICC transmits a REFRESH message (case 2) to the modem for memory reset.

[0084] According to an embodiment of the present invention, when an LPA receives a request from a terminal user to change the state of a profile installed on an eUICC (from Enabled to Disable, from Disabled to Enable), it may transmit an ES10c.EnableProfile or ES10c.DisableProfile message to the eUICC. While transmitting the message, the LPA may transmit (1d-05) a refreshFlag as an identifier to determine whether the eUICC should send a Proactive Command for REFRESH to the modem. The eUICC determines (1d-10) whether it is necessary to transmit REFRESH to the modem using the refreshFlag in the ES10c message, and if necessary, it may transmit a Proactive Command (a method in which the eUICC includes a message that needs to be transmitted in the message sent from the modem to the eUICC) containing information indicating that a refresh is required. This may be, for example, a REFRESH Proactive Command. Which message to send as a message indicating that a refresh is required can be determined based on whether the eUICC is currently operating as an MEP (1d-15) and whether the aforementioned ISD-R is multi-selected (1d-25).

[0085] During the process of establishing a connection by initializing between the terminal and the eUICC, the terminal modem may create an eSIM Port and transmit a Command APDU regarding the port open created by the modem to the eUICC, or transmit a Command explicitly indicating to the eUICC that it is operating in MEP mode. Alternatively, the terminal modem may confirm that MEP is supported in the ATR (Answer to Reset) received from the eUICC and inform the eUICC of the identification information regarding MEP support, thereby indicating to the eUICC that it should operate in MEP mode thereafter. Whether the eUICC is currently operating in MEP mode (1d-15) can be determined by the eUICC by receiving and processing the command regarding the eSIM Port open received from the aforementioned modem, by receiving a Command explicitly indicating that it is operating in MEP mode, or by the eUICC supporting MEP and processing the setting to MEP by receiving identification information regarding MEP support from the modem. Alternatively, if the eUICC contains mapping information between the profile and the port in the profile information collected or stored by the ISD-R, the eUICC may make a determination based on said mapping information. This process may be determined before initiating this procedure (1d-01).

[0086] For example, when processing a profile state change, a Proactive Command transmitted from the eUICC to the modem may include the following information. For the types of Proactive Commands, refer to the ETSI TS.102.223 standard, and for the processing of response APDUs containing proactive commands, refer to ETSI TS.102.221. As mentioned above, when the (e)UICC has a message to transmit to the terminal, a Proactive Command may be included and transmitted as data of the reply value to the FETCH Command transmitted by the UICC. A Proactive Command can be represented by a TLV (Type-Length-Value) configuration, and the Type and mode of the Proactive Command can be indicated by one of the data fields among the above Values. Referring to ETSI TS.102.223, a Proactive Command may have a structure as shown in Table 1 below.

[0087] [Table 1]

[0088]

[0089] In Table 1 above, the Command details field may be composed of TLVs as shown in Table 2 below.

[0090] [Table 2]

[0091]

[0092] Meanwhile, when a Proactive Command is transmitted including a port number, a new REFRESH mode or a new Proactive Type (or Type of command) (at a level equivalent to REFRESH) may be defined instead of the existing eUICC Profile State Change or UICC Reset mode.

[0093] 1) When a new Type of command is defined, instead of the REFRESH Type, 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. The 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 distinguish Reset using the Command Qualifier for that Type as follows.

[0094] - In the case of RESET (an example of a new type):

[0095] '00' = Platform Reset;

[0096] '01' = Port Reset

[0097] 2) When a new mode is added as one of the modes of REFRESH, it can be represented as a sub-identification value for Type=REFRESH using Command Qualifiers such as 0B and OC below.

[0098] - In the case of REFRESH:

[0099] '00' = NAA Initialization and Full File Change Notification;

[0100] '01' = File Change Notification;

[0101] '02' = NAA Initialization and File Change Notification;

[0102] '03' = NAA Initialization;

[0103] '04' = UICC Reset;

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

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

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

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

[0108] '09' = eUICC Profile State Change;

[0109] '0A' = Application Update;

[0110] '0B' = Port Reset

[0111] '0C' = Platform Reset

[0112] When defining a Type of Command or a new Mode, field(s) that indicate the port number(s) requiring Refresh processing or all may be added to the Value field of the Proactive Command.

[0113] 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 indicate the port number(s) or all. This can be done by adding field(s) that indicate the port number(s) or all requiring refresh processing as Values ​​within the TLV of the Proactive Command, or by adding a Value to one of the existing TLVs of the Proactive Command.

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

[0115] · If the eUICC does not operate as MEP: Select and transmit either eUICC Profile State Change or UICC Reset. In (1d-15), the case where the eUICC does not operate as MEP can be assumed to include both cases where the eUICC and Modem do not support MEP, or where they support it but the function is disabled. The case where they support it but the function is disabled may include the case where the modem has two Basebands, but one eUICC and one SIM card each occupy and use one Baseband.

[0116] · When eUICC operates as MEP and ISD-R is Multi-selected on the eSIM port:

[0117] eUICC may not use a single dedicated ISD-R port to transmit the efresh message, but instead select all ports connected to the profile where a change, such as a profile state, has occurred, and determine that the ISD-R transmits the Refresh message through each port (1d-27). In this case, the ISD-R of the eUICC may select one of the modes, eUICC Profile State Change or UICC Reset, through the port to perform the Refresh and transmit without a port number (1d-30).

[0118] · When eUICC operates as MEP and ISD-R is Multi-selected on the eSIM port:

[0119] Even if the ISD-R is multi-selected with eSIM ports, if you wish to send a refresh message to one of the ISD-R ports, you may send a message that includes the Port # to be refreshed (1d-35). Alternatively, if you wish to refresh multiple ports simultaneously, there may be multiple Port #s to be transmitted.

[0120] · When the eUICC operates as an MEP and the ISD-R does not support multi-selected eSIM ports: The eUICC's ISD-R may request a refresh for a specific port from a single transport port (1d-35). The requesting message may be, for example, a message such as a REFRESH proactive command. The port or eSIM port designated for ISD-R selection during the initialization process between the terminal and the eUICC may be referred to as the default port, default eSIM port, or ISD-R eSIM port. As previously mentioned, the corresponding ISD-R eSIM port may be an ISD-R dedicated port independent of the port used by the Profile, or it may be a port that shares the port with the Profile.

[0121] o Set the REFRESH mode to eUICC Profile State Change and transmit the modem including the port identifier to which REFRESH will be applied. Multiple port identifiers may be included and transmitted as the port identifier to which REFRESH will be applied.

[0122] o Set the REFRESH mode to UICC Reset and transmit the port identifier for which the modem will perform REFRESH. Multiple port identifiers may be included and transmitted for the application of REFRESH.

[0123] The modem that receives the transmission performs a predefined operation according to the command, and the operation of the modem will be described in detail later in Fig. 1h.

[0124] Meanwhile, when the eUICC receives ES10c. eUICCMemoryReset from the LPA (1d-45), the eUICC may request a REFRESH from the modem via a Proactive Command if there is one or more profiles active in the eUICC. Since all profiles active in the terminal must be disabled in the case of an eUICC Memory Reset, the eUICC may send a REFRESH Proactive Command to the modem in one of the following ways by considering the number of active profiles in addition to the REFRESH determination procedure for the aforementioned Profile Status Change.

[0125] 1. If the number of active profiles is 2 or more,

[0126] A. In cases where ISD-R cannot be multi-selected, depending on whether the eUICC setting is to be treated as a platform reset,

[0127] i. When processing as a platform reset, the ISD-R transmits to the modem a REFRESH command of eUICC Profile State Change or UICC Reset mode through one eSIM port, along with an identifier (e.g., All) meaning 'all eSIM ports' (1d-60). This may be a new REFRESH mode or a new Proactive Type (equivalent to REFRESH) meaning a command to execute the REFRESH command of eUICC Profile State Change or UICC Reset mode on all ports, which may be referred to as a platform reset, for example.

[0128] ii. If not processed as a platform reset, ISD-R transmits to the modem via a single eSIM port an eUICC Profile State Change or UICC Reset mode REFRESH command and an identifier representing multiple eSIM Port # Lists (e.g., #1, #2) (1d-73)

[0129] B. In the case where the ISD-R is multi-selectable and the ISD-R sends a Proactive Command-REFRESH (1d-65) per port to the modem to handle the eUICC Memory Reset

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

[0131] C. If the ISD-R is multi-selectable and one port is selected to transmit a Proactive Command-REFRESH (1d-65) to handle the eUICC Memory Reset on the ISD-R

[0132] i. Perform as (1d-60) or (1d-75)

[0133] 2. When one Profile is enabled,

[0134] A. Send a REFRESH Command to the modem using either the method of (1d-30) or (1d-35) described above.

[0135] When the MEP-supported eUICC performs a REFRESH to change the state of a profile as in Case 1 of Fig. 1da, the eUICC sends a REFRESH message depending on the situation among (1d-20), (1d-30), and (1d-35), and then the eUICC completes the process of changing the state of the corresponding profile after receiving a TERMINAL RESPONSE from the modem (if the eUICC profile state change was sent) or after being RESET (if the UICC reset was sent, in which case a TERMINAL RESPONSE may not be required).

[0136] In the case where an MEP-supported eUICC needs to send a REFRESH command to the modem for eUICC memory reset because there is an enabled profile in the eUICC as in Case 2 of FIG. 1db, the eUICC deletes all installed profiles regardless of whether they are enabled or disabled, and selects one of the methods (1d-30), (1d-35), (1d-60), (1d-70), or (1d-73) as described above to send a REFRESH proactive command to the modem. If there is no Enabled profile and only a deletion operation is performed, it is also possible not to send a REFRESH Proactive Command. Meanwhile, it should be noted that the above-mentioned operation of the eUICC sending a REFRESH Proactive Command including a port number to a specific port can be divided into the eUICC sending a request to perform a refresh including a port number from a single port, and the eUICC preparing and sending a REFRESH Proactive Command from the port number transmitted.

[0137] FIG. 1e is a sequence example diagram showing a method for processing local profile activation in a terminal to which the present invention is applied.

[0138] As mentioned above, v2 eUICCs that do not support MEP functionality are designed to allow only one profile to be enabled. Therefore, if there is an existing enabled profile, the existing enabled profile must be changed to a disabled state in order to enable another profile. However, in the case of eUICCs that support MEP functionality, when processing a profile enable command, there are instances where another currently enabled profile must not be disabled depending on the location of the eSIM port to be enabled. For example, if the eSIM has eSIM Port 1 and eSIM Port 2 and Profile 2 is currently enabled on eSIM Port 2, when enabling Profile 1 on eSIM Port 1, it must be ensured that Profile 2, which is currently enabled on eSIM Port 2, is not disabled.

[0139] In addition, if the terminal has basebands that support different Radio Access Technology (RAT), the eSIM ports are matched, and since the Radio Access Technology (RAT) available through the corresponding profile varies depending on the baseband, it is necessary to provide information that allows the user or server (in the case of RPM) to decide which eSIM port to match the profile to be activated. For example, if eSIM port 1 is matched with a baseband that supports a 4G network and eSIM port 2 is matched with a baseband that supports a 5G network, if the user or the server performing remote management knows this information, it can help in selecting the appropriate eSIM port to activate a specific profile.

[0140] The number of profiles simultaneously activated on the eUICC at a specific time can be limited to be equal to or less than the number of eSIM ports allocated by the eUICC. If profile activation is to be processed via the user or SM-DP+, the eUICC may reply to the LPA or SM-DP+ server with the maximum number of profiles that can be activated on the eUICC, taking into account the number of currently activated profiles and the number of eSIM ports.

[0141] The LPA or terminal software may use information transmitted from the eUICC (e.g., the number of eSIM ports allocated by the eUICC) as specific information to notify the user that the currently active profile needs to be deactivated.

[0142] Additionally, when an activation message including a port number is transmitted from the LPA to the eUICC, the eUICC that receives it processes the message and then sends a message regarding refresh processing including the port number, for example, a REFRESH proactive command, to the modem (1e-65), or sends a response message with the port number attached to it to the LPA (1e-90). The modem receives this from the eUICC or LPA and can perform a refresh on the corresponding port and process a reset on the corresponding port. FIG. 1e shows the sequence of the procedure for enabling a profile as an example of how a user (1e-01) manages a profile through the LPA (1e-05) in an MEP-supported terminal. In FIG. 1e, the eUICC (1e-10), modem (1e-15), and LPA (1e-05) are all MEP-supported.

[0143] The End User (1e-01) performs an activation command (1e-20) for a profile installed on the terminal through information displayed in the LPA (1e-05) or an application in which the LPA (1e-05) is integrated. An example of a screen displayed on the user screen when performing the activation command will be described later in FIG. 1f. In the LPA of the terminal or the corresponding implementation app (1e-05), the user may display at least one combination of information, such as a list of profiles installed on the eUICC and current status information of the corresponding profile, wireless access technology provided by the terminal modem per Baseband, eSIM port information matched for APDU transmission between the Baseband and the corresponding profile, and information regarding the occupancy status of the profile of the port(s) from the eUICC. At this time, the LPA may check the Profile Policy Rules of the profile and additionally display a warning message to the End User (1e-01), such as profile activation being impossible.

[0144] When a user (1e-01) decides to activate a specific profile 3 by selecting it based on the information displayed on the screen, the LPA (1e-05) sends the ES10c.EnableProfile(ISD-P AID (Issuer Security Domain - Profile Application ID) or ICCID (Profile ID), refreshFlag, Port number) (1e-30) command to the eUICC to activate the profile, including the port number matched to the selected Baseband. If the port number is not determined at that time, the message (1e-30) may be sent without the port number, or the eUICC may be sent with identification information instructing it to determine a port number and process it, and when the eUICC determines a port number, it may be sent to the LPA with this information included in the Response message (1e-90). Messages transmitted by the LPA to the eUICC are carried as data in the Command APDU transmitted from the modem to the eUICC, and messages transmitted by the eUICC to the LPA can be carried as data in the Response APDU. As mentioned earlier, it is also possible for the eUICC to use a special port number, such as -1, as an identifier to determine a port number. The refreshFlag is a response message sent from the card to the terminal that requests refresh processing, and can be additionally set and transmitted when, for example, the transmission of the REFRESH Proactive command is required. If the refreshFlag is not set, the terminal must satisfy the conditions for enabling the MEP through terminal implementation, such as terminating the application session for the port occupied between the UICC and the modem, closing the logical interface, or closing the channel, if there is an existing Enabled profile (1e-25).

[0145] When the eUICC (1e-10) receives the corresponding Enable profile command from the LPA (1e-05) (1e-30), the eUICC can perform a Disable procedure for the profile (named Profile 1) occupying the port and perform Enable processing on the port. In (1e-35), the ISD-R of the eUICC (1e-10) checks the activation status of the profile 3 to be activated and the existing profiles installed in the eUICC, as well as the PPR (Profile Policy Rules), to determine whether the profile 3 can be activated comprehensively, and if activation is not possible, it can send an error message to the user. When determining whether to enable Profile 3 in an eUICC (1e-10) that supports MEP (1e-35), if the eUICC intends to use a port that is already occupied by another profile, such as Profile 1, for the port to be enabled of Profile 3, the eUICC may determine that it must change the status of the profile to disabled and change Profile 3 to enabled, limited to Profile 1 which used the port, in order to process the activation of the port. If Profile 3 uses an empty port, the eUICC (1e-10) that supports MEP may proceed without performing other Profile Disabled procedures within the eUICC. In this embodiment, where a Refreshflag is set and involves a change in the status of the profile, the eUICC may send a command requesting a refresh to the modem to request an operation processing according to the processing of the profile status change.

[0146] For example, when using the REFRESH Proactive Command, the eUICC transmits the REFRESH proactive command to the modem as described in FIG. 1da and 1db, and the modem can process it as in FIG. 1h. Depending on the result of the modem processing the REFRESH, the eUICC receives a Terminal Response (when an eUICC Profile State Change is transmitted) or, after RESET (when UICC Reset is processed) (1e-70), matches the selected Profile 3 to the port number transmitted in (1a-30). If there is a profile that was enabled on that port (Profile 1 in the previous case), it disables it and performs Enable, or if Enable is performed on a previously unoccupied port, it performs Enable only Profile 3 (1e-75) to complete the process.

[0147] In the case where refreshFlag was not set in 1e-30, eUICC matches the selected profile 3 after (1e-35) to the port number transmitted in (1a-30), and if there was a profile that was enabled on that port (profile 1 in the previous case), disables it and performs Enable, or if Enable is performed on an unoccupied port, only profile 3 is enabled (1e-75) (1e-85).

[0148] The eUICC (1e-10) can send a reply (1e-90) to the LPA (1e-05) with the result of performing the procedure. The reply message may include port number(s) for which a port reset is required. Additionally, even if the message is received without the port number(s), it is possible for the LPA (1e-05) to determine the port number requiring a port reset, add it, and transmit it to the modem.

[0149] The LPA (1e-05) transmits to the modem (1e-15) a port number(s) received from the eUICC or added by the LPA, including the port number(s), thereby enabling the modem to perform a refresh such as an eUICC Profile State Change or UICC Reset, including deleting the cached value for the corresponding connected port due to a change in the profile state. Additionally, the modem can perform the UICC activation procedure including TERMINAL PROFILE defined in ETSI TS 102 221 clause 14.5.1 (1e-95). Subsequently, the LPA (1e-05) performs a network attach procedure (1e-100) on the Baseband connected to the port based on the information of the profile newly connected to the port. A method for transmitting a refresh command to the modem when the refreshFlag is not set will be described further in FIG. 1k.

[0150] Meanwhile, although not explicitly indicated in the diagram, when the ISD-R receives port information mapped to a profile from the LPA, the ISD-R updates the metadata of the corresponding profile. Subsequently, this information can be provided when the LPA requests it for local profile management or when the LPA requests it from SM-DP+ for remote profile management. The ISD-R can provide status information of installed profiles, mapping information between the profile and the port, and information on profiles activated in the eUICC. Additionally, the eUICC's ISD-R can add a Profile Policy Rule (PPR) to the profile metadata regarding whether the profile is usable in an MEP environment. This serves as specific information on whether the profile can be executed alone or in conjunction with other profiles upon installation or activation, allowing users or SM-DP+ servers to utilize this information.

[0151] Meanwhile, according to one embodiment of the present invention, a port number can be obtained from the LPA, and a profile management command message including the obtained port number can be transmitted to the eUICC. The eUICC can process the connection to the profile to the specified port number by checking information regarding the port number and refresh flag of the received message. At this time, if there is no received port number or if the eUICC has separate identification information regarding port settings, the eUICC can additionally determine and process the connection to the profile to a specific port. Additionally, depending on the status change of the profile, the eUICC can transmit the port number, including the port number, directly to the modem or to the LPA, and cause the modem to perform refresh processing for the received port number.

[0152] FIGS. 1fa, FIGS. 1fb, FIGS. 1fc, and FIGS. 1fd are example drawings of an implementation of a profile management screen provided to a terminal user in an MEP-supported terminal to which the present invention is applied.

[0153] As described above, through the LPA or the app screen implementing the LPA, the user can receive status information such as profiles installed on the eUICC and their activation / deactivation. Additionally, the MEP terminal provides information such as the capabilities of wireless access technologies per Baseband provided by the modem, information regarding which Baseband and which eSIM port is connected, and whether there is an active profile using that port (port occupancy). This allows the user to determine which port to specify on the eUICC to activate the profile through the screen. This information can be displayed to the user on the LPA or the app screen implementing the LPA for local profile management. For remote profile management (RPM) via the SM-DP+ server, this information can be transmitted along with the port capability of the deviceinfo in Fig. (1g). The SM-DP+ can then determine the port to handle profile activation / deactivation through a combination of this information and send it back to the terminal. In Fig. 1f, among the various combinations that can be displayed to the user

[0154] Representative combinations that can be provided are classified and indicated as Fig. 1fa Case 1 (1f-01), Fig. 1fb Case 2 (1f-05), Fig. 1fc Case 3 (1f-55), and Fig. 1fd Case 4 (1f-80). The explanation assumes a situation where 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.

[0155] As described above, the terminal can display some or all of the information to the user by combining at least one of the port information, profile status information, profile list, and available RAT information.

[0156] In the case of Case 1 (1f-01) of Fig. 1fa, if there is a profile 3 to be activated, since the profile supports only 4G in this example, if the user specifies a change in the status of the profile (1f-15), the terminal must change the status of profile 1 to disabled. Therefore, the terminal can obtain the user's consent by explicitly notifying the user (1f-20) and proceed with the subsequent procedure. Meanwhile, as described later in Fig. 1g, when processing with RPM, the information indicated in (1f-10) is transmitted to the SM-DP+ server as eSIM port Capability. Through the combination of the port occupancy status of the eSIM port Capability and RAT information by connected Baseband, SM-DP+ displays a screen such as (1f-23) to the user and obtains the user's consent to complete the subsequent RPM-Enabled procedure.

[0157] Fig. 1fb Case 2 (1f-05) is a case where the profile to be activated can support 4G or 5G wireless access technology. In this case, if the user wants to activate it, the terminal can configure a screen for additional selection (1f-40) so that the user can activate it on Port 1 or Port 2, receive the user's final selection, and output the result to display to the user. In the case of RPM-Enabled, the SM-DP+ server can arbitrarily designate one port by judging the selection of the highest wireless access technology through a combination of the port occupancy status of eSIM port Capability and RAT information per connected Baseband, and then issue a command for activation processing to that port (1f-23), or send a message for the user's additional selection or a URL containing that message to the terminal, and obtain the user's consent based on that information (1f-50, 1f-40), and after the server receives the information, perform profile activation processing on the finally selected port and display the result value to the user (1f-45).

[0158] Fig. 1fc Case 3 (1f-55) is a case where the wireless access technology (e.g., 4G) supported by Profile 3 to be enabled does not match the wireless access technology (e.g., 5G) supported by the Baseband connected to Port 2 which is not occupied. In this case, for example, Profile 1 occupying the port connected to 4G can be disabled and the port can be used. In this case, a screen configuration such as (1f-70) when Local Profile Enable is enabled, or (1f-75) when RPM-Enable is enabled, may be displayed.

[0159] Finally, Fig. 1fd Case 4 (1f-80) is a case where there is an unoccupied port within the eUICC and the wireless access technology supported by Profile 3 to be enabled matches the wireless access technology supported by the Baseband connected to the unoccupied Port 2, allowing Port 2 to be used without disabling other profiles. In this case, a screen configuration such as (1f-90) for Local Profile Enable or (1f-95) for RPM-Enable may be displayed.

[0160] FIG. 1g is a sequence example diagram showing a method for processing remote profile activation (RPM-Enable) in a terminal and profile server to which the present invention is applied.

[0161] In order to manage (activate / deactivate / delete / update) a profile downloaded to the terminal, a user may request a corresponding command from the eUICC (1g-10) via the terminal's LPA (1g-05) locally, and the LPA (1g-05), eUICC (1g-10), and modem (1g-15) may process this and send the result back to the user (1g-01) (1g-25). Since a detailed explanation of the Enable procedure for Local Profile Management was previously explained in FIG. 1e, a detailed explanation will be omitted. Meanwhile, the profile management server (1g-20) may, on behalf of the user (1g-01), refer to certain data received from the terminal and send a request (1g-30) to the terminal for the management (activate / deactivate / delete / update) of a profile already downloaded to the terminal remotely.

[0162] (1g-35) to (1g-80) are drawings illustrating examples of general procedures for a terminal according to an embodiment of the present disclosure to receive and process remote management commands from a profile server. In the drawings, procedures requiring modification compared to the existing ones are indicated when the terminal (1g-33) supports MEP (Multiple Enabled Profile). The terminal (1g-33) may be a terminal equipped with an eUICC (1g-35) and an LPA (1g-40) installed to control the eUICC (1g-35). Additionally, one or more profiles may be installed in the terminal or the eUICC (1g-35). Furthermore, each installed profile may have one or more profile servers capable of remotely controlling the corresponding profile. In the following description, an administrator profile server (managing SM-DP+) or SM-DP+ is used as an example of a profile server, but the profile server of the present invention is not limited thereto. The list of described administrator profile servers may include the address or unique identifier (object identifier) ​​of each administrator profile server written in the form of an IP address or FQDN. Additionally, although not shown in the drawing, a remote profile management command requested by a telecommunications carrier may be generated and waiting on the profile server (1g-45).

[0163] The profile server (1g-45) can transmit a profile remote management command to the LPA (1g-40) in step (1g-60). For example, in step (1g-60), the profile server (1g-45) may use an authenticate client response message containing at least one remote management command and the digital signature of the profile server (1g-45). The digital signature of the profile server (1g-45) may be calculated based on at least one remote management command. Although this drawing illustrates an example where only one "Enable Profile" remote management command is transmitted in step (1g-60), it should be noted that, as described above, more than one remote management command may be transmitted, and various types of remote management commands, such as "Disable Profile" and "Delete Profile," may be transmitted instead of necessarily being the "Enable Profile" remote management command.

[0164] Referring to FIG. 1g, in step (1g-50), a Common Mutual Authentication procedure can be performed between the terminal (1g-33) and the profile management server (1g-45). Step (1g-50) may include a TLS connection based on server authentication. Additionally, step (1g-50) may further include, for example, at least one step of transmitting and receiving an initial authentication request, an initial authentication response, and an authenticate client request message. Additionally, step (1g-50) may be a procedure integrated with part or all of step (1g-60).

[0165] In the procedure, ES9+.AuthenticateClient(transactionId, authenticateServerResponse) can transmit to SM-DP+(1g-45) a terminal authentication request message that includes the LPA (1g-40) and eUICC (1g-35) of the terminal (1g-33) and some information collected from within the terminal. The authenticateServerResponse may include euiccInfo2 and deviceinfo. euiccinfo2 refers to information about the eUICC (1g-35) defined in SGP.22, and deviceinfo refers to information about the terminal (1g-33) defined in SGP.22. The SM-DP+(1g-45) may use part or all of the euiccinfo2 and deviceinfo information received as a terminal authentication request as some information to determine whether to perform an RPM for a profile already installed on the MEP terminal. The terminal may also send a message (1g-55) containing deviceinfo as part of the attributes of ES9+.AuthenticateClient(transactionId, authenticateServerResponse) or as a separate message to SM-DP+ (1g-45).

[0166] In the euiccinfo2 transmitted by the terminal, the eUICC Capability may be indicated as an eUICC that supports MEP, and the deviceinfo of (1g-55) may include one or more pieces of information regarding the port identification and port in the eSIM port capability of the deviceinfo, such as a port number, an IMEI (international mobile equipment identities) number mapped to the port, and Radio Access Technologies information for the baseband used by the port. Alternatively, the terminal (1g-33) may generate Deviceinfo mapped to each baseband according to the number of basebands in the terminal and transmit it to (1g-55) including one or more pieces of deviceinfo. For example, in the case of a terminal that supports Dual SIM, two pieces of DeviceInfo may be generated and transmitted. The port capability information of the deviceinfo transmitted by the terminal may be indicated by extending the deviceinfo as follows, for example. For example, as shown in Table 3 below, the range of the Port Index is indicated as 1..MaxNumOfPort, but the Port Index may be any number designated by the terminal.

[0167] [Table 3]

[0168]

[0169] The RAT (Radio Access Technologies) information supported by the indicated port capability may be identical to or a subset of the RAT (Radio Access Technologies) of deviceCapabilities. Meanwhile, when two DeviceInfos are generated and transmitted, it may be indicated that two DeviceInfos are transmitted as shown in Table 4 below.

[0170] [Table 4]

[0171]

[0172] Considering compatibility with SM-DP+(1g-45) that does not support MEP and is capable of performing RPM, in the case of a Dual SIM terminal, the terminal may also process the information by selecting the primary eSIM port information based on the terminal or user's choice and transmitting it as deviceinfo, while distinguishing and transmitting other eSIM port information as additional deviceinfo. Additionally, the terminal may include eSIM port information in the message of the (1g-55) stage and transmit it to SM-DP+(1g-45) only for the purpose of RPM operation. In this case, the terminal may also collect eSIM port information and include the collected eSIM port information in deviceInfo and transmit it to SM-DP+(1g-45) only when it intends to transmit CtxParamForCommonAuthentication, which is included in the Authentication Client Request, with operationType=rpm.

[0173] If the SM-DP+(1g-45) that receives the port information is an SM-DP+(1g-45) that supports both MEP and RPM, the SM-DP+(1g-45) can determine the number of ports and whether each port is occupied by another profile based on the Port Capability provided by the terminal, determine which port to request an Enabled command for, and then transmit an RPM Command to the terminal. If all ports are occupied by profiles, the SM-DP+(1g-45) may additionally transmit to the terminal (1g-35) a message stating that all ports are occupied and cannot be enabled, along with port information that must be vacated for enabling, so that the user can process the Disabled procedure (1g-65) for the profile connected to the port locally.

[0174] In case (1g-65), for example, if the user disables the local profile at the terminal by receiving the message, the terminal (1g-40) may request a retry for receiving the RPM message by sending the result to the server (1g-45) again, or it may process subsequent procedures by restarting the initial RPM request. As described above, the terminal (1g-33) may match the Baseband and port, configure deviceinfo with each Baseband information, and send one or more deviceinfos to SM-DP+. If the SM-DP+ (1g-45) that receives the deviceinfo(s) information is an SM-DP+ (1g-45) that supports RPM but does not support MEP, the SM-DP+ (1g-45) may select one of the deviceinfos and request the terminal LPA (1g-40) to perform RPM-Enabled processing based on the deviceinfo.

[0175] The LPA (1g-40) that receives the RPM request can transmit a profile remote management command to the eUICC (1g-35) in step (1g-70). In step (1g-70), the LPA (1g-40) can use a remote management input request (load RPM package request) message that includes, for example, at least one remote management command and the digital signature of the profile server (1g-45), and the LPA can specify and transmit information about the eSIM port to be connected when the profile is enabled for MEP support. The remote management input request message transmitted from the LPA to the eUICC may include part or all of the terminal authentication response message (1g-60).

[0176] The remote management input request message (load RPM package request) transmitted from LPA (1g-40) to eUICC (1g-35) may be a message such as ES10b.LoadRpmPackage (smdpSigned3, smdpSignature3, [eSIM port number]) or ES10b.LoadRpmPackage (smdpSigned3, smdpSignature3)+[eSIM port number].

[0177] 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) may be included in the reply within the smdpSigned3 signed by SM-DP+ (for example, as part of the command of the RpmPackage parameter within smdpSigned3, or included as an additional parameter outside the RpmPackage within smdpSigned3), or it may be added outside of smdpSigned3 and replied.

[0178] If the eSIM Port information is outside of smdpSigned3, it is possible for the LPA to modify it either on its own or based on the user's choice. SM-DP+ (1g-45) may implicitly indicate that the port number can be changed by the user or terminal settings by adding the port number to be used outside of smdpSigned3 and replying. When SM-DP+ (1g-45) adds the port number to be used outside of smdpSigned3 and transmits it to the LPA (1g-40) as a terminal authentication response message (1g-60), after the RPM processing is finished, the LPA (1g-40) can notify SM-DP+ (1g-45) of the final specified port number by replying to SM-DP+ with HandleNotification (Load RPM Package Result (OK+[Port #]) (1g-80) including the port number.

[0179] It is also possible to send an authentication response message (1g-60) from SM-DP+ (1g-45) to LPA (1g-40) without eSIM Port information. For example, if the Device Info transmitted from the terminal to SM-DP+ (1g-45) in (1g-55) is sent without information identifying MEP support, or if SM-DP+ (1g-45) receives information regarding MEP support but does not support it, the terminal authentication response message (1g-60) transmitted from SM-DP+ (1g-45) to LPA (1g-40) may be delivered to eUICC without eSIM Port.

[0180] In this case, the LPA (1g-40) may add eSIM Port information to activate the profile and transmit it to the eUICC (1g-35), or if the LPA (1g-40) does not add eSIM Port information, the eUICC (1g-35) may determine the eSIM port.

[0181] When the LPA adds eSIM Port information, the eSIM Port number may be added as an optional parameter to smdpSigned3 and smdpSignature3 in the LoadRpmPackageRequest message transmitted from the LPA (1g-40) to the eUICC (1g-35), or the eSIM Port number may be added as an optional parameter outside the LoadRpmPackageRequest message.

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

[0183] When adding eSIM Port information in the LPA (1g-40), it may decide for itself which eSIM Port to activate the corresponding profile and transmit it to the eUICC (1g-35). For example, the LPA can check the Radio Access Technology (RAT) information supported by each Baseband and the empty eSIM Ports not occupied by the profile through the Device Capability of DeviceInfo2 obtained from the terminal, select one of the empty eSIM Ports, add the selected empty eSIM Port number to smdpSigned3 and smdpSignature3 of LoadRpmPackageRequest, and transmit it to the eUICC (1g-35). In particular, if the RAT supported by each Baseband is the same, the LPA may arbitrarily select one of the empty eSIM Ports where the profile is not activated.

[0184] Alternatively, the LPA (1g-40) may obtain user input regarding which eSIM Port to activate the corresponding profile and transmit it to the eUICC (1g-35). For example, the LPA (1g-40) may provide a UI requesting the user to select an eSIM Port (or desired RAT) to use, and transmit the selected eSIM Port number to the smdpSigned3 and smdpSignature3 of the LoadRpmPackageRequest according to the user's selection and transmit it to the eUICC (1g-35).

[0185] The terminal (1g-33) may specify a default port according to the terminal settings or the port information mapped to the Baseband of the corresponding deviceinfo, and when the LPA (1g-40) requests an ES10b.LoadRpmPackage Request to the eUICC for Enable processing, the LPA may add the information and request the eUICC (1g-35) as ES10b.LoadRpmPackage Request (RPM Enable Profile) + eSIM port# or ES10b.LoadRpmPackage Request (RPM Enable Profile + eSIM port#) (1g-75) as before.

[0186] There may also be instances where eSIM Port information is changed by the LPA (1g-40). For example, port information may be transmitted from SM-DP+ (1g-45) to the LPA (1g-40), but it may be impossible to deactivate the profile activated on that port. In this case, if the LPA receives an error message from the eUICC (1g-35) stating that activation is not possible on that port, the LPA (1g-40) may set the Port by adding another eSIM port as an optional parameter, either through user input or by itself, and transmitting it back to the eUICC. For example, if the RATs supported by the terminal's Basebands are all the same, it may add another eSIM port by itself changing it as an optional parameter.

[0187] There may be cases where the eSIM port information is present in smdpSigned3 included in ES10b.LoadRpmPackage, but 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) attempts to activate the profile prioritizing the eSIM port added by the LPA (1g-40) and processes it, and as described below, must reply with the port information where the final profile is activated via andleNotification (Load RPM Package Result (OK+[Port #]) (1g-80).

[0188] Meanwhile, in the case where an activation request is transmitted from the LPA to the eUICC (1g-35) without port information, the MEP-supported eUICC (1g-35) may designate a default port when performing port initiation with the eUICC between the platform-modem-eUICC of the terminal mentioned above, and then process the connection to that port when an activation request comes from the LPA. As another example, if there is an empty eSIM port at the time the eUICC receives the activation request, it may be possible to enable that port.

[0189] As described above, when an LPA receives a profile activation command without port information, it requests activation processing from the eUICC by adding a specific port number, or when the LPA receives the command with port information but cannot activate the corresponding port, the LPA changes the port number and transmits it to the eUICC, or when the MEP-supported eUICC (1g-35) receives the command without a port number, it connects by arbitrarily assigning a specific port. This method is also commonly applicable to the local profile activation mentioned in 1e.

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

[0191] For the target profile of the remote management command, which is listed as an administrator profile server by the profile server (1g-45) that transmitted the remote management command, the eUICC (1g-35) can execute one or more remote management commands received in the operation (1g-60). If one or more remote management commands are received, the eUICC (1g-35) may execute each remote management command repeatedly. After executing each remote management command, the eUICC (1g-35) can generate a remote management input result (load RPM package result).

[0192] If eSIM Port information is contained within smdpsigned3, the LPA must not be able to change the corresponding value contained within smdpsigned3 in transit. If the LPA changes it, the eUICC must return an error because the signature verification step (1g-73) of SM-DP+ by the eUICC will fail. In other words, if SM-DP+ sends back to the LPA with eSIM Port #1 specified in smdpSigned3, and the LPA changes it to eSIM Port #2 in transit, the eUICC that finally receives it must return an error. That is, the eSIM Port included in smdpSigned3 must be specified by SM-DP+, and the LPA must not add or change it.

[0193] When LPA adds an eSIM Port number and transmits it to eUICC, LPA must process it so that the new eSIM Port parameter can be added while maintaining the integrity protection of smdpSignature3. As mentioned above, if LPA passes the eSIM Port to eUICC by specifying it outside of smdpsigned3 without modifying the signature value of the rpmpackage received from SM-DP, the eSIM Port can be excluded from the signature verification part of SM-DP+ and eUICC.

[0194] The remote management input result for one or more remote management commands received by the eUICC (1g-35) may include at least one "OK" in the form of a string or a corresponding number sequence if each remote management is successful, and may additionally include and transmit a Port number. If each remote management fails, it may include at least one error code that caused the failure in the form of a string or a corresponding number sequence. This drawing illustrates a case where the remote management command received in step (1g-60) is "Enable Profile," and in step (1g-73), the eUICC (1g-35) succeeds in enabling the target profile and generates an "OK" result. In step (1g-75), the eUICC (1g-35) may reply the remote management input result to the LPA (1g-40). eUICC (1g-35) can use, for example, a remote management input response (load RPM package response) message containing at least a remote management input result in step (1g-75).

[0195] In step (1g-80), the LPA (1g-40) can transmit a remote management input result (load RPM package result) to the profile server (1g-45). In step (1g-80), the LPA (1g-40) can, for example, use a handle notification message. The handle notification 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 include information about the eSIM Port where the profile is activated.

[0196] Figure 1h is an example diagram of the sequence for determining the processing of a received REFRESH Command at a modem.

[0197] The UICC Reset REFRESH Command can be used when the UICC's CAT (Card Application Toolkit) needs to receive an ATR (Answer to Reset) or when the UICC initialization process needs to be performed. When the modem receives such a request at the time the present invention is disclosed, the modem performs the procedure to terminate all application sessions with the UICC card, deletes the cached value for the UICC, and requests a reset from the UICC, causing the UICC to perform the reset and return an ATR. Through this, the modem and the 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 in TS102.223.

[0198] Meanwhile, 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 corresponding profile stored in the modem. Then, the Card closes all channels except Logical channel 0, which is used for transmission with ISD-R, and restores the "default state after UICC activation and ATR" defined in ETSI TS 102 221. Once this process is completed, the modem sends a TERMINAL RESPONSE to the eUICC.

[0199] At the time of disclosing the present invention, when the eUICC processes the activation or deactivation of a profile, it may select and transmit either an eUICC Profile State Change or a UICC Reset to the modem. Since only one profile has existed within the eUICC until now, no problem has occurred even if either of the two commands is received to perform a software reset (terminal operation upon receiving an eUICC Profile State Change, or the terminal performing software initialization upon receiving a UICC Reset), or to perform a hard reset by turning off all power to the device via a Reset PIN, etc., and restoring it to an initial state.

[0200] However, when multiple profiles are active, for example, when profile 1 and profile 2 are simultaneously active within the eUICC, if the above operation is used to process the state change of profile 1, a problem may occur where the network of profile 2 is disconnected. Therefore, as described above in FIG. 1da and 1db, a method is disclosed in which the eUICC transmits a REFRESH message depending on the situation. When the modem receives a REFRESH Command from the eUICC (1h-05), if the modem is not currently operating as an MEP, the modem can perform the corresponding Command as in the conventional manner (1h-15) upon receiving an eUICC Profile State Change or UICC Reset.

[0201] The situation in which the modem is currently operating in MEP mode (1h-10) can be considered as the case where the terminal has performed an initialization procedure with eUICC and eUICC MEP. In this case, if multiple profile eSIM ports have been created, each eSIM port may be mapped to a specific baseband within the modem or may not be mapped. Subsequently, the profile activated on a specific eSIM port can transmit an APDU containing a Proactive Command to the modem through that eSIM port, and the modem can perform an action corresponding to the contents of the received APDU by applying it to the memory area or baseband mapped to that eSIM port, depending on which eSIM port the received APDU was transmitted through.

[0202] Meanwhile, as described above, when the ISD-R in the eUICC is multi-selected by multiple eSIM ports (where LPA selects the ISD-R through each eSIM port where multiple eSIM ports are created, and there are logical channel(s) capable of transmitting and receiving the ISD-R and APDU for each eSIM port), the ISD-R can transmit a Proactive Command to the modem through each eSIM port. Depending on whether the current state of the eUICC and the modem satisfies (1h-10) and (1h-20) and the Proactive Command received by the modem, the operation of the modem may vary and may include at least one of the following five cases.

[0203] Meanwhile, as described above in FIG. 1da and FIG. 1db, when a Proactive Command including port number(s) or all is transmitted, it may also be defined as a REFRESH Proactive Command of a new mode or a new type.

[0204] For example, the Proactive Command may be defined in a form such as the Platform reset mode (where 'all' is present) or Port reset mode (where port number(s) are included) of the "Reset" Proactive Command, or it may be a case where a field or value representing port number(s) is included in the existing "REFRESH" Proactive Command. Although the REFRESH Proactive Command is described as an example in this drawing, the scope of the present invention is not limited thereto.

[0205] Meanwhile, the following procedure 1 may be initiated when the terminal receives an eUICC response message including a port number.

[0206] 1. If the MEP modem supports multi-selected ISD-R processing (1h-20) and the received message does not contain information about Port or All (1h-30),

[0207] A. Execute the Proactive Command received via the transmitted eSIM port. If it is a refresh for a profile state change, this may be a REFRESH Proactive Command for an eUICC Profile State Change or UICC Reset (Soft Reset) (1h-35).

[0208] 2. If the MEP modem supports multi-selected ISD-R processing (1h-20) and the received REFRESH Command contains information about Port(s) or All (1h-30),

[0209] A. Based on the judgments below regarding (1h-40), (1h-50), and (1h-60), perform one of the methods (1h-45), (1h-55), or (1h-65).

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

[0211] A. Perform a hard reset (a reset performed via power or the reset pin) (1h-45).

[0212] 4. If the MEP modem does not support multi-selected ISD-R processing (1h-20) and a REFRESH Command containing an eUICC Profile State Change plus all port identifiers is received on a specific eSIM port (1h-50),

[0213] A. Perform REFRESH on all ports (Soft Reset on all ports) (1h-55).

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

[0215] A. Perform a refresh (Soft Reset) on the included Port identifiers (1h-65). There may be multiple Port identifiers, and if multiple Port identifiers are included, perform a refresh on the included Port identifiers.

[0216] If the result of determining whether Multi-Selected ISD-R is supported (1h-20) is that it is not supported and it is received without information on the port number or All, it is possible to operate as in (1h-15) or process as in (1h-35) depending on the terminal implementation.

[0217] If multiple port numbers are received, the modem may perform a network detach procedure for each port in the order of reception, delete the cached values ​​in the ports, and then start a new card session by resetting the corresponding ports. Additionally, if the received ports are occupying the network, the modem may perform a batch network detach procedure, delete the cached values ​​in the ports in batches, and then start a new card session by resetting the ports. This applies equally when a terminal (terminal Framework via LPA) directly requests a reset from the modem including multiple port numbers (1h-70).

[0218] In the case where ISD-R is selected through only one port, a refresh for the included Port identifier may be possible, for example, in the following cases.

[0219] - The modem checks the corresponding port identifier information, performs a UICC reset on the corresponding port, and sends a reset command to that port.

[0220] - The modem checks the corresponding port identifier information and requests polling to that port to process the existing UICC Reset or eUICC Profile State Change on that port.

[0221] Meanwhile, although not described in detail in this drawing, as described in FIG. 1ca and FIG. 1cb, the ISD-R can be selected through only one port. In this case, it can be said that the port used for the ISD-R is used as a port for managing other ports. The modem may process Proactive Commands received from the management port and other ports differently. This will be described in further detail in FIG. 1l.

[0222] FIGS. 1ia and FIGS. 1ib illustrate the connection between the v3 eUICC and the modem following the introduction of the Virtual Interface concept. This is a diagram showing the Multi-Selected ISD-R.

[0223] The eUICC (1i-20) in the corresponding drawings (1ia, 1ib) is assumed to be an eUICC that supports MEP functionality capable of activating multiple profiles simultaneously. Meanwhile, the modem (1i-01) is also assumed to be a modem that supports MEP functionality. In 1i, the situation with two Basebands and two activated profiles is explained as an example, and while a mapping switch between the Baseband and the eSIM port within the modem (1i-01) may be possible, in Case 1 and Case 2, the mapping of logical terminal endpoints within the modem (1i-01) is explained as Baseband 1 (1i-05) - Channel 1 (1-40) and Baseband 2 (1i-10) - Channel 2 (1-45).

[0224] As previously described in FIG. 1ba and FIG. 1bb, the current modem (1a-15) is connected to the eUICC (1a-20) via a single physical pin, and the modem and the eUICC transmit APDU commands using a single channel (1b-10) through that physical pin. The eUICC (1i-20) that supports MEP activates multiple profiles, and the activated profiles require APDU transmission with a specific baseband of the modem. Therefore, a concept can be introduced in which the Physical Interface (1i-15) for processing this is multiplexed to distinguish the APDU and transmit it through multiple channels (1i-40, 1i-45).

[0225] For convenience of explanation below, when MEP is supported, the channel will be designated as an eSIM port, and each channel will be designated as eSIM Port 1 (1i-40) and eSIM Port 2 (1i-45) and used as an eSIM port. After a UICC Reset or Profile Status Change, the terminal may generate an APDU channel for transmission between the modem baseband and the eUICC during the initialization process between the modem and the eUICC, and at this time, an ID for the eSIM port connected to each baseband may be set. The corresponding port ID can be set on the modem or terminal platform and transmitted to the LPA. For convenience of explanation in this specification, the port ID is used interchangeably with the port number.

[0226] The modem may have as many eSIM ports as the number of basebands, but the number of eSIM ports used in the eUICC (1i-20) may be equal to or less than the number of profiles that can be simultaneously activated in the eUICC. A profile can send APDU messages using one of the eSIM ports.

[0227] In the case of Case 1 (1i-100) of Fig. 1ia, an APDU Command corresponding to the activated Profile 1 (1i-25) can be transmitted to Baseband 1 (1i-05) through eSIM port 1, and at the same time, an APDU Command corresponding to the activated Profile 2 (1i-30) can be transmitted to Baseband 2 (1i-10) through eSIM port 2 (1i-45).

[0228] In Fig. 1ib Case 2 (1i-200), APDU commands corresponding to the activated Profile 1 (1i-25) can be transmitted to Baseband 2 (1i-10) through eSIM port 2 (1i-45), and at the same time, APDU commands corresponding to the activated Profile 2 (1i-30) can be transmitted to Baseband 1 (1i-05) through eSIM port 2 (1i-40).

[0229] The MEP-supported 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 Command APDU to the modem for profile and eUICC status management.

[0230] The LPA or modem may determine, through the eUICC initialization process or preset, that it allows the selection of the ISD-R (1i-35) to multiple eSIM ports. This state may be called Multi-Selected. In the case of Multi-Selected, the LPA or modem may exchange messages with the ISD-R (1i-35) through one of the eSIM ports selected and determined by the LPA or modem. Depending on whether the received message is a management message corresponding to Profile 1 (1i-25) or Profile 2 (1i-30), or a message for the entire eUICC, the ISD-R (1i-35) may select an appropriate eSIM port and send a Response APDU containing a proactive Command to that port.

[0231] FIG. 1j is a diagram showing a terminal block configuration according to an embodiment of the present invention.

[0232] Referring to FIG. 1j, the terminal may be configured to 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 inside the terminal, or it may be configured as a separate entity from the terminal or inserted into the terminal.

[0233] The transmitting and receiving unit (1j-05) may correspond to a modem in the present invention and can transmit and receive signals with SM-DP+.

[0234] The control unit (1j-10) of the terminal can perform operations according to embodiments of the present invention by controlling the state and operation of all terminal components in the present invention. For example, operations according to embodiments of the present invention can be performed by controlling at least one of an LPA, a modem, and an eUICC.

[0235] The display unit (1j-15) can display to the user, in part or in whole, a comprehensive collection of port information, profile status information, profile list, and available RAT information according to an embodiment of the present invention.

[0236] The eUICC (1j-20) is controlled by the LPA or the control unit (1j-10), and in an embodiment of the present invention, the eUICC performs each management command and can transmit the Proactive Command to a modem, etc.

[0237] FIG. 1k is a diagram showing a Refresh method that does not use a Proactive Command according to an embodiment of the present invention.

[0238] FIG. 1k schematically illustrates the sequence of managing profiles through an LPA (1k-05) by a user (1k-01) in an MEP-supported terminal. The example described in FIG. 1k is that the LPA (1k-05), modem (1k-10), and eUICC (1k-15) all support MEP.

[0239] The End User (1k-01) performs a management command (1k-20) for a profile installed on the terminal through information displayed in the LPA (1k-05) or an application in which the LPA (1k-05) is integrated. An example of a screen displayed on the user screen when performing the management command is described above in FIG. 1f. In the case where the ES10c. Command is transmitted without the RefreshFlag parameter as in the figure, the terminal may selectively check (1k-25) whether the terminal meets the conditions to support it before transmitting the ES10c. Command. This may be, for example, the termination of an application session for a port occupied between the UICC and the modem, or a logical channel close, when there is an existing Enabled profile as defined in GSMA SGP.22.

[0240] When the LPA receives user input or RPM command, it may send an ES10c command to the eUICC (1k-40). Upon receiving the message, the eUICC may verify the state for processing the command, such as the profile state information or Profile Policy Rule that the eUICC needs to check when receiving the command, as defined in GSMA SGP.22 (1k-45), and if there is a problem, it may send an error message. Among the above ES10c commands, the commands that cause a change in the profile state are labeled as Profile State Change Related Commands in this drawing for convenience of explanation, but the ES10c commands may be one of ES10c.enableProfile, ES10c.disableProfile, ES10c.deleteProfile, or ES10c.euiccMemoryReset.

[0241] To transmit a Proactive Command, the corresponding Port must support the Card Application Toolkit, and it is possible that the port used by the ISD-R does not support the corresponding CAT. In this case, the LPA may transmit the command without the refreshFlag parameter when transmitting the Profile State Change Related Command. Additionally, even if the CAT is supported, depending on the terminal implementation, it may be possible for the LPA to receive the processing request and for the modem to process the refresh, rather than the eUICC requesting the modem to process it. This corresponds to the case where there is no refreshFlag during the Profile activation processing in Fig. 1e. Upon receiving the Profile State Change Related Command without the refreshFlag parameter, the eUICC may perform an internal processing operation regarding the corresponding profile state change (e.g., profile activation, deactivation, or deletion, etc.) (1k-50), and then transmit port information requiring a refresh to the modem based on a determination by the eUICC or LPA, thereby enabling the modem to perform the refresh processing. This method may include one of the following.

[0242] Alt1: Method to add port number(s) required for Refresh in LPA and send to the modem.

[0243] The eUICC can return the processing result for the corresponding ES10c. Command to the LPA. At a specific point in time after receiving the user's input, the LPA can determine and store which port number(s) require refresh, and upon receiving the message, request the corresponding Refresh command from the modem by adding the port number(s) requiring refresh (1k-60). When the modem receives the Refresh command, it can perform Refresh processing at the port(s) or platform level (1k-65). As previously described in FIG. 1h, the modem can perform a UICC Reset or an eUICC Profile State Change on the requested port(s), and if an identifier representing all ports is included, it can perform a Reset on the entire platform similar to the current UICC Reset.

[0244] The way the LPA determines what to input for the port number(s) requiring a refresh can be one of the following.

[0245] For enabling / disabling / deleting a specific port in a profile: Port number included in ES10c. Command (1k-40)

[0246] Additional determination in the case of activation processing on a specific port of a profile: The profile to be activated may be a port that is already activated on another port. In this case, in addition to the Port number included in ES10c.Command (1k-40), all ports where the profile was previously activated may need to be refreshed. The LPA may determine the number of the previously activated port by one of the following: an error message indicating that the profile received from eUICC between (1k-45) and (1k-50) is on a different port and the additionally included port number, or information about the port where the profile was previously activated (1k-35) obtained through GetProfileInfo() (1k-30) prior to executing ES10c.command, or a combination of both.

[0247] In the case of eUICC memory reset processing: When an eUICC memory reset is transmitted in (1k-40), the LPA may, depending on the LPA's configuration, decide to use an identifier representing all ports (e.g., all) instead of utilizing the profile-specific active port information (1k-35) returned from GetProfileInfo().

[0248] Alt2: A method in which the eUICC adds the port number(s) required for Refresh and sends them to the LPA, and the LPA retransmits the corresponding information to the modem.

[0249] The eUICC can process a command for the Target Profile and reply (1k-70) including the port number requiring refresh as a result of the processing. This may be the number(s) of all ports where there is a change in the profile and port mapping as a result of processing through the ES10c. Command. For example, it may reply including one or more cases where the profile activated on the port has been changed or disabled. Alternatively, it may reply including a new identifier indicating all ports that require platform-level reset processing. The eUICC may reply to the LPA including at least one of the above information. When the LPA receiving this transmits the information regarding the ports requiring refresh to the modem, the modem can perform the refresh processing on the corresponding ports or platform-level refresh processing (1k-80) as described above in Alt 1.

[0250] Alt3: A method in which the eUICC adds the port number(s) required for Refresh and transmits them to the LPA, and the modem parses the message in the middle to process the port number(s) requiring Refresh.

[0251] eUICC can process a Command for a Target Profile and return (1k-85) including the port number requiring Refresh as a result of processing. This may be the number(s) of all ports for which there is a change in the profile and port mapping as a result of processing via the ES10c Command. For example, it may return including one or more cases where the profile enabled on the port has changed or has been disabled. Alternatively, it may return including a new identifier representing all ports indicating that platform-level Reset processing is required.

[0252] The MEP modem can parse all APDU messages between the LPA and ISD-R in the middle to understand their contents, or the eUICC can transmit an indicator outside the reply message indicating that the MEP modem needs to parse and understand the message contents (1k-85). When the eUICC transmits the message to the LPA (1k-85), the modem in the middle can interpret the message included in the APDU() transmitted between the eUICC and the card, and perform Refresh processing at the corresponding ports or platform level as described above in Alt 1 (1k-80). In this case, the modem may optionally add the result of the completion of the processing to the eUICC and transmit it to the LPA (1k-95).

[0253] FIG. 11 is a diagram illustrating a method in which a modem according to an embodiment of the present invention processes Proactive Commands received from a port for management purposes and a port for non-management purposes differently.

[0254] In FIG. 11, it is assumed that eSIM Port 0 (1l-20) is a management port accessible only to ISD-R, and eSIM Port 1 (1l-30) is a non-management port that must not affect other ports. If, in eUICC (1l-01), ISD-R transmits a Proactive Command containing port number(s) or all ports (all) to the modem (1l-40) through eSIM Port 0 (1l-20), and the modem checks the received Proactive Command and finds that there is a Proactive Command containing port number(s) or all ports (all), the modem can perform processing for the Proactive Command as described above in FIG. 1h. If the port number received from (1l-40) is #1, the modem (1l-10) may send a Polling message to (1l-70) asking if there is a message to FETCH, or the modem (1l-10) may send a Reset Command for the port after performing all Reset processing procedures for port 1. If the eUICC (1l-10) receives a Reset Command from (1l-70) but the port number is different from the port number included in the Proactive Command sent from (1l-40) in the eUICC (1l-01), the eUICC (1l-10) may additionally reply to the modem (1l-10) with an error regarding this so that the modem should send a Reset Command again to the port number included in the Proactive Command sent from (1l-40).

[0255] If the ISD-R in eUICC (1l-01) transmits a Proactive Command (1l-60) to the modem through eSIM Port 1 (1l-30) containing port number(s) or all ports, the modem checks the received Proactive Command and, if it is a Proactive Command containing port number(s) or all ports, the modem may reject the processing and return an error to (1l-70).

[0256] In the specific embodiments of the present disclosure described above, the components included in the present disclosure are expressed in a singular or plural form according to the specific embodiments presented. However, the singular or plural expression is selected to suit the situation presented for convenience of explanation, and the present disclosure is not limited to singular or plural components; even if a component is expressed in the plural, it may be composed of a singular form, and even if a component is expressed in the singular form, it may be composed of a plural form.

[0257] Meanwhile, although specific embodiments have been described in the detailed description of the present disclosure, it is understood that various modifications are possible within the scope of the present disclosure. Therefore, the scope of the present disclosure should not be limited to the described embodiments, but should be defined by the claims set forth below as well as equivalents thereof.

Claims

Claim 1 A method performed by a device in a wireless communication system, comprising: identifying information associated with a target profile that needs to be activated by a local profile assistant (LPA) of the device; transmitting a first message for activating the target profile, which includes a refresh flag indicating whether a refresh operation of a target port corresponding to the target profile is required, and a port number of the target port, by the LPA, to an embedded universal integrated circuit card (eUICC) of the device; receiving a second message from the eUICC to trigger a refresh operation of the target port by a baseband component of the device when the refresh flag indicates that a refresh operation of the target port is required; and, based on receiving the second message, transmitting a terminal response message to the eUICC by the baseband component or resetting the target port by the baseband component. Claim 2 A method according to claim 1, characterized in that the target profile is activated on the target port. Claim 3 A method according to claim 1, characterized in that the first message is transmitted over a predetermined port different from the target port. Claim 4 A method according to claim 1, characterized in that information associated with the target profile that needs to be activated is obtained based on user input. Claim 5 A method according to claim 1, characterized in that the device supports a plurality of activated profiles. Claim 6 A method performed by an eUICC (embedded universal integrated circuit card) of a device in a wireless communication system, comprising: receiving from a local profile assistant (LPA) of the device a first message including a refresh flag indicating whether a refresh operation of a target port corresponding to the target profile is required to activate the target profile, and a port number of the target port; transmitting a second message to a baseband component of the device to trigger a refresh operation of the target port when the refresh flag indicates that a refresh operation of the target port is required; and activating the target profile when a terminal response message is received from the baseband component or after the target port has been reset, based on the transmission of the second message. Claim 7 A method according to claim 6, characterized in that the target profile is activated on the target port. Claim 8 A method according to claim 6, characterized in that the first message is received on a predetermined port different from the target port. Claim 9 In claim 6, the step of activating the target profile comprises, if another profile is currently active on the target port, deactivating the other profile and activating the target profile on the target port. Claim 10 A method according to claim 6, characterized in that the eUICC supports a plurality of activated profiles. Claim 11 A device in a wireless communication system comprises an LPA (local profile assistant); and a baseband component, wherein the LPA is configured to transmit to an eUICC (embedded universal integrated circuit card) of the device a first message for activating the target profile, which includes a refresh flag indicating whether a refresh operation of the target port corresponding to the target profile is required and a port number of the target port, and the first message for activating the target profile, which includes information associated with the target profile that needs to be activated and a refresh flag indicating whether a refresh operation of the target port is required; and the baseband component is configured to receive from the eUICC a second message for triggering a refresh operation of the target port when the refresh flag indicates that a refresh operation of the target port is required, and, based on receiving the second message, transmit a terminal response message to the eUICC or reset the target port. Claim 12 A device according to claim 11, characterized in that the target profile is activated on the target port. Claim 13 A device according to claim 11, characterized in that the first message is transmitted over a predetermined port different from the target port. Claim 14 A device according to claim 11, characterized in that information associated with the target profile that needs to be activated is obtained based on user input. Claim 15 In claim 11, the device is characterized by supporting a plurality of activated profiles. Claim 16 An eUICC (embedded universal integrated circuit card) of a device in a wireless communication system is characterized by receiving a first message from a local profile assistant (LPA) of the device, the first message including a refresh flag indicating whether a refresh operation of a target port corresponding to the target profile is required to activate the target profile, and the port number of the target port; transmitting a second message to a baseband component of the device to trigger a refresh operation of the target port when the refresh flag indicates that a refresh operation of the target port is required; and configuring the device to activate the target profile upon receiving a terminal response message from the baseband component or after the target port has been reset, based on the transmission of the second message. Claim 17 In claim 16, the eUICC is characterized in that the target profile is activated on the target port. Claim 18 In claim 16, the eUICC is characterized in that the first message is received on a predetermined port different from the target port. Claim 19 In claim 16, the eUICC is characterized by being configured to disable the other profile and enable the target profile on the target port when the other profile is currently active on the target port. Claim 20 In claim 16, the eUICC is characterized by supporting a plurality of activated profiles.

Images