Method and apparatus for installing and managing multiple esim profiles

Abstract

This disclosure relates to a communication method and system for integrating fifth-generation (5G) communication systems, which support higher data rates than fourth-generation (4G) systems, with Internet of Things (IoT) technology. This disclosure can be applied to smart services based on 5G communication technology and IoT-related technologies, such as smart homes, smart buildings, smart cities, vehicle connectivity, healthcare, digital education, smart retail, security, and safety services. A method performed by a terminal in a wireless communication system is provided. The method includes: a Local Profile Assistant (LPA) identifying information associated with a target profile to be enabled; the LPA sending a first message for enabling the target profile to an embedded universal integrated circuit card (eUICC), the first message including a refresh flag and a port number corresponding to the target profile; if the refresh flag is set in the first message, a modem receiving a second message from the eUICC, including the port number, to initiate a modem status refresh; and if the refresh flag is not set in the first message, the modem receiving the port number from the LPA.

Description

Technical Field

[0001] This disclosure relates to methods and apparatus for establishing a connection communication by downloading and installing one or more communication services into a terminal in a wireless communication system. Furthermore, this disclosure relates to methods and apparatus for remotely downloading and installing profiles into a terminal and managing multiple installed profiles. Background Technology

[0002] To meet the ever-increasing demand for wireless data traffic since the deployment of 4G communication systems, efforts have been made to develop improved 5G or pre-5G communication systems. Therefore, 5G or pre-5G communication systems are also referred to as "Beyond 4G Network" or "Post LTE System." 5G communication systems are considered to be implemented in higher (mmWave) frequency bands, such as the 60GHz band, to achieve higher data rates. To reduce radio wave propagation loss and increase transmission distance, beamforming, massive MIMO, full-dimensional MIMO (FD-MIMO), array antennas, analog beamforming, and large antenna technology have been discussed in 5G communication systems. Furthermore, in 5G communication systems, development of system network improvements is underway, building upon advanced small cells, cloud radio access networks (RAN), ultra-dense networks, device-to-device (D2D) communication, wireless backhaul, active networks, cooperative communication, cooperative multipoint (CoMP), and receiver interference cancellation. In 5G systems, hybrid FSK and QAM modulation (FQAM) and sliding window superposition coding (SWSC) have been developed as advanced coding modulation (ACM), and filter bank multicarrier (FBMC), non-orthogonal multiple access (NOMA) and sparse code multiple access (SCMA) have been developed as advanced access technologies.

[0003] The internet, a human-centric network of connections where information is generated and consumed by humans, has evolved into the Internet of Things (IoT), in which distributed entities (such as things) exchange and process information without human intervention. The Internet of Everything (IoE), a combination of IoT technology enabled by cloud server connectivity and big data processing, has emerged. Sensor networks, machine-to-machine (M2M) communication, and machine-type communication (MTC) have been under close research recently, as the implementation of IoT requires technological elements such as sensing technology, wired / wireless communication and network infrastructure, service interface technology, and security technology. Such an IoT environment can provide intelligent internet technology services that create new value for human life by collecting and analyzing data generated in connected things. Through the convergence and combination of existing information technology (IT) with various industry applications, IoT can be applied to a wide range of fields, including smart homes, smart buildings, smart cities, smart or connected cars, smart grids, healthcare, smart appliances, and advanced medical services.

[0004] Consistent with this, various attempts have been made to apply 5G communication systems to IoT networks. For example, technologies such as sensor networks, machine-type communication (MTC), and machine-to-machine (M2M) communication can be implemented through beamforming, MIMO, and array antennas. The application of cloud radio access networks (RAN), as the big data processing technology described above, can also be seen as an example of the convergence between 5G and IoT technologies.

[0005] A Universal Integrated Circuit Card (UICC) is a smart card used by being inserted into mobile communication terminals, etc., and is also known as a UICC card. A UICC may include an access control module for accessing a mobile communication operator's network. Examples of access control modules may include a Universal Subscriber Identity Module (USIM), a Subscriber Identity Module (SIM), an IP Multimedia Service Identity Module (ISIM), etc. A UICC including a USIM is generally referred to as a USIM card. Similarly, a UICC including a SIM is generally referred to as a SIM card. In the following description, the term "SIM card" is used in a general sense to encompass UICC cards, USIM cards, and UICCs including ISIMs. That is, although a description is provided using a SIM card as an example, the technical application can be equally applied to USIM cards, ISIM cards, or general UICC cards. Summary of the Invention

[0006] Technical issues

[0007] The SIM card stores personal information associated with a mobile communication subscriber and performs subscriber authentication and traffic security key generation when accessing the mobile communication network, thereby enabling secure use of mobile communication.

[0008] When manufactured according to the request of the corresponding operator, the SIM card is made into a dedicated card for that specific mobile communication operator. When the SIM card is approved for sale, authentication information for accessing the corresponding operator's network, such as the Universal Subscriber Identity Module (USIM) application, International Mobile Subscriber Identity (IMSI), K-value, and OPC value, is pre-included in the card. Therefore, the manufactured SIM card is supplied to the corresponding mobile communication operator, who then provides it to subscribers. Later, if needed, the SIM card can use technologies such as Over-the-Air (OTA) to manage applications in the UICC, such as installation, calibration, and deletion. Subscribers insert the UICC card into their mobile communication terminals and use the corresponding mobile communication operator's network and application services. If a subscriber inserts a UICC card already inserted into an existing terminal into a new terminal, the subscriber can use the authentication information, mobile phone number, personal phone book, etc., stored in the UICC card as before.

[0009] However, with SIM cards, users of mobile communication terminals may find it difficult to receive services from other mobile communication operators. Users must obtain a physical SIM card to receive services from a mobile communication operator. For example, if a user travels to another country, they must have a SIM card from that country to receive local mobile communication services, which is inconvenient. Roaming services can solve this inconvenience. However, this is costly, or the service may not be available if there is no contract between communication operators.

[0010] This inconvenience can be greatly eliminated if the SIM module is remotely downloaded and installed into the UICC card. That is, the user can download the SIM module for the mobile communication service they expect to use at their desired time to the UICC card. The UICC card can download and install multiple SIM modules and can select and use one of them. The UICC card can be fixed to a terminal or not. Specifically, a UICC used in a terminal-fixed manner is called an embedded UICC (eUICC). Generally, an eUICC card is a UICC card used in a terminal-fixed manner and can remotely download and select SIM modules. In this disclosure, UICC cards capable of remotely downloading and selecting SIM modules are collectively referred to as eUICCs. That is, among UICC cards capable of remotely downloading and selecting SIM modules, both terminal-fixed and terminal-free UICC cards are collectively referred to as eUICCs. Furthermore, the SIM module information obtained through downloading is referred to as a "profile".

[0011] Although one or more profiles exist in the eUICC, only one profile can be enabled at a time. Therefore, even if a terminal supports two basebands and has two or more profiles in the corresponding eUICC, it cannot support dual SIM functionality where both profiles are enabled simultaneously in a single mobile phone. This limitation can be overcome by including two eUICCs in the terminal, but this requires an additional eUICC module and may necessitate connecting the eUICC module to the physical interface of the modem's baseband. Therefore, the terminal manufacturer must bear the overhead associated with purchasing the additional eUICC module and the physical pins for that physical interface. Furthermore, sufficient space must be allocated within the terminal to accommodate the corresponding module and physical pins.

[0012] The above information is provided for background purposes only to aid in understanding this disclosure. No decision has been made, nor is any claim made, regarding whether any content above is appropriate as prior art relative to this disclosure.

[0013] If the MEP-supported terminal expects to enable the configuration file installed in the eUICC via the user's local configuration file or via remote activation via the configuration file server, then it must perform the simultaneous activation of one or more configuration files by obtaining and combining predetermined information, such as the number of configuration files that can be enabled at the same time provided by the UE, the baseband combination that can be supported by the modem, whether the corresponding baseband is occupied and used by the configuration file, etc.

[0014] Currently, in the existing eUICC, only one eSIM profile can be enabled at a time. Therefore, if profile 2 is connected to the network when profile 1 is expected to be enabled, profile 2 can be disabled and its communication connection can be broken, which is a drawback.

[0015] The eUICC connects to a single baseband of the modem via a single physical interface, so messages associated with eUICC memory reset and messages associated with configuration file disabling are not processed separately. However, in the case of terminals that allow MEP, if messages associated with eUICC memory reset and messages associated with configuration file disabling are not processed separately, the modem may delete all cached data already stored in the modem, including cached data for configuration file 2, which is a drawback that must be overcome.

[0016] Solution to the problem

[0017] The subject of this disclosure is to provide methods and apparatus for installing, enabling, and managing multiple profiles, thereby enabling dual SIM functionality even in a terminal equipped with a single eUICC in a communication system.

[0018] In one embodiment, a method performed by a terminal in a wireless communication system is provided. The method includes: a Local Profile Assistant (LPA) identifying information associated with a target profile to be enabled; the LPA sending a first message for enabling the target profile to an embedded universal integrated circuit card (eUICC), the first message including a refresh flag and a port number corresponding to the target profile; if the refresh flag is set in the first message, a modem receiving a second message from the eUICC including the port number for initiating a modem status refresh; and if the refresh flag is not set in the first message, the modem receiving the port number from the LPA.

[0019] In one embodiment, a method is provided performed by an embedded universal integrated circuit card (eUICC) in a wireless communication system. The method includes: receiving a first message from a terminal's Local Profile Assistant (LPA) to enable a target profile, the first message including a refresh flag and a port number corresponding to the target profile; identifying whether the refresh flag is set in the first message; and if the refresh flag is set in the first message, sending a second message including the port number to the terminal's modem to initiate a modem status refresh.

[0020] In one embodiment, a terminal in a wireless communication system is provided. The terminal includes a Local Profile Assistant (LPA) and a modem. The LPA is configured to identify information associated with a target profile that is requested to be enabled, and to send a first message for enabling the target profile to an embedded universal integrated circuit card (eUICC). The first message includes a refresh flag and a port number corresponding to the target profile. The modem is configured to: if the refresh flag is set in the first message, receive a second message from the eUICC including the port number for initiating a modem status refresh; and if the refresh flag is not set in the first message, receive the port number from the LPA.

[0021] In one embodiment, an embedded universal integrated circuit card (eUICC) in a wireless communication system is provided. The UICC is configured to: receive a first message from a terminal's Local Profile Assistant (LPA) to enable a target profile, the first message including a refresh flag and a port number corresponding to the target profile; identify whether the refresh flag is set in the first message; and if the refresh flag is set in the first message, send a second message including the port number to the terminal's modem to initiate a modem status refresh.

[0022] According to one aspect of this disclosure, a method for a terminal in a wireless communication system is provided. The method may include: sending an authentication request message including port identity information to a manager server; receiving from the manager server an authentication response message including configuration file information for management generated based on the port identity information and port information for management; and performing configuration file management based on the configuration file information for management and information associated with a port mapped to the configuration file to be managed.

[0023] According to another aspect of this disclosure, a terminal in a wireless communication system is provided. The terminal may include: a transceiver configured to transmit or receive signals; an embedded universal integrated circuit card (eUICC) configured to manage configuration files; and a controller configured to perform control to: send an authentication request message including port identity information to a manager server; receive from the manager server an authentication response message including configuration file information for management generated based on the port identity information and port information for management; and perform configuration file management based on the configuration file information for management and information associated with ports mapped to the configuration file to be managed.

[0024] Specifically, in order to achieve the above objectives, this disclosure includes the following embodiments.

[0025] One method in which the terminal reports the terminal's "eSIM port capability" information to a configuration file server.

[0026] One method involves a profile server recognizing "eSIM port capability" information and remotely selecting the profile to be enabled and choosing the eSIM port on which the profile will be enabled.

[0027] - A method that provides a screen to the user of a terminal for determining the port to be used, taking into account the eUICC profile enable status and "eSIM port capability", and enables the terminal to determine the eSIM port to be used by the profile.

[0028] One method in which the terminal's LPA sends the corresponding eSIM port information to the eUICC.

[0029] One method is that eUICC receives the corresponding port information and enables the configuration file on the corresponding port.

[0030] In addition, in order to achieve the above objectives, this disclosure includes the following embodiments.

[0031] - A method in which, if the eUICC receives a message associated with an eUICC memory reset request or a configuration file state change request from the LPA of a terminal in MEP mode, the eUICC identifies a refresh message associated with a state change in the eUICC based on the message received from the LPA of the terminal and sends it to the LPA or modem of the terminal.

[0032] - A method in which a modem that receives a corresponding message directly from the eUICC or via the LPA performs different operations based on the received message and the port number included in the received message.

[0033] The technical subject matter of this disclosure is not limited to the technical subject matter mentioned above, and those skilled in the art can understand other technical subject matter not mentioned based on the description below.

[0034] Beneficial effects

[0035] According to embodiments of this disclosure, users can use dual SIM functionality in a terminal equipped with a single eUICC. Furthermore, terminal manufacturers can provide dual SIM functionality without additional enclosure space by connecting a single eUICC and a single physical pin to a modem (providing two or more basebands). Since an additional eUICC is not required, manufacturing costs can be saved.

[0036] The configuration file management server can obtain information associated with the eSIM port on which the configuration file will be enabled for the MEP terminal, and can request the corresponding terminal to enable the configuration file on the optimal port. Configuration file 1 and configuration file 2, which are enabled simultaneously in the eUICC, can run within a single eUICC without interfering with each other (such as the network access of configuration file 2 being terminated due to the activation of configuration file 1, etc.), so the communication operator of configuration file 1 or configuration file 2 can reliably provide network services. Attached Figure Description

[0037] Figure 1 This is a diagram illustrating the structural elements of the present disclosure in a wireless communication system according to an embodiment.

[0038] Figure 2A This is a diagram illustrating the connection between a modem and a current v2 eUICC that does not support MEP (Case 1).

[0039] Figure 2B This is a diagram illustrating the connection between the modem and a current v2 eUICC that does not support MEP (Case 2).

[0040] Figure 3A This is a diagram illustrating the connection between a modem and a v3 eUICC (Case 1) introduced according to the concept of a virtual interface.

[0041] Figure 3B This is a diagram illustrating the connection between a modem and a v3 eUICC (Case 2) introduced according to the concept of a virtual interface.

[0042] Figure 4A This is a flowchart illustrating the method by which the eUICC's ISD-R sends a REFRESH message (Case 1) to the modem to change the state of the configuration file.

[0043] Figure 4B This is a flowchart illustrating the method by which the eUICC's ISD-R sends a REFRESH message for memory reset to the modem (Case 2).

[0044] Figure 4C This is a flowchart illustrating the method by which the eUICC's ISD-R sends a REFRESH message for memory reset to the modem (Case 2).

[0045] Figure 5 This is a flowchart illustrating a method for enabling a local configuration file in a processing terminal according to this disclosure.

[0046] Figure 6AThis is an illustration of an implementation example of a configuration file management screen (Case 1) provided by a MEP-supported terminal to a user of the terminal according to this disclosure.

[0047] Figure 6B This is an illustration of an implementation example of a configuration file management screen (case 2) provided by a MEP-supported terminal to a user of the terminal according to this disclosure.

[0048] Figure 6C This is an illustration of an implementation example of a configuration file management screen (case 3) provided by a MEP-supported terminal to a user of the terminal according to this disclosure.

[0049] Figure 6D This is an illustration of an implementation example of a configuration file management screen (case 4) provided by a MEP-supported terminal to a user of the terminal according to this disclosure.

[0050] Figure 7 This is a flowchart illustrating a method for handling remote configuration file enabling (RPM-Enable) by a terminal and a configuration file server according to this disclosure.

[0051] Figure 8A This is a flowchart illustrating the process for determining the received REFRESH command in a modem that has received the REFRESH command.

[0052] Figure 8B This is a flowchart illustrating the process for determining the received REFRESH command in a modem that has received the REFRESH command.

[0053] Figure 9A This is a diagram illustrating an example of a multi-selected ISD-R in the process of connecting a modem and v3 eUICC according to the concept of a virtual interface (Case 1).

[0054] Figure 9B This is an illustration of an example of multiple selectable ISD-Rs in the process of connecting a modem and v3 eUICC according to the concept of a virtual interface (Case 2).

[0055] Figure 10 This is an illustration of a block configuration of a terminal according to an embodiment of the present disclosure.

[0056] Figure 11 This is an illustration of a refresh method that does not use active commands according to an embodiment of the present disclosure.

[0057] Figure 12This is an illustration of a method by which a modem processes active commands received via a port for management purposes and active commands received via a port for purposes other than management, according to embodiments of the present disclosure. Detailed Implementation

[0058] Before proceeding with the detailed description below, it is advantageous to define certain words and phrases used throughout this patent document: the words “comprising” and “including” and their derivatives mean including but not limited to; the word “or” is inclusive, meaning and / or; the phrases “associated with” and “related to” and their derivative expressions can mean including, being included within, interconnected with, containing, being included in, connected to or connected with, able to communicate with, cooperate with, intersect with, juxtaposed with, near, bound to or together with, having, or possessing the characteristics of, etc.; and the word “controller” means any device, system or part thereof that controls at least one operation, such device being implemented by hardware, firmware or software or some combination of at least two of them. It should be noted that the functionality associated with any particular controller can be centralized or distributed, whether local or remote.

[0059] Furthermore, the various functions described below can be implemented or supported by one or more computer programs, each of which is formed by computer-readable programming code and embodied in a computer-readable medium. The terms "application" and "program" refer to one or more computer programs, software components, instruction sets, procedures, functions, objects, classes, instances, associated data, or portions thereof suitable for implementation by appropriate computer-readable program code. The phrase "computer-readable program code" includes any type of computer code, including source code, object code, and executable code. The phrase "computer-readable medium" includes any type of medium that can be accessed by a computer, such as read-only memory (ROM), random access memory (RAM), hard disk drive, compact disc (CD), digital video disc (DVD), or any other type of memory. "Non-transitory" computer-readable medium excludes wired, wireless, optical, or other communication links that transmit transient electrical signals or other signals. Non-transitory computer-readable medium includes media that permanently store data and media capable of storing data and subsequently overwriting it, such as rewritable optical discs or erasable memory devices.

[0060] Definitions of certain words and phrases appearing throughout this patent document are provided, and those skilled in the art will understand that, in many (if not most) cases, such definitions apply to both prior and future use of such defined words and phrases.

[0061] The following discussion Figures 1 to 12 The various embodiments used to describe the principles of this disclosure in this patent document are by way of illustration only and should not be construed in any way as limiting the scope of the invention. Those skilled in the art will understand that the principles of this disclosure can be implemented by any suitably arranged system or apparatus.

[0062] The operating principles of this disclosure will be described in detail below with reference to the accompanying drawings. In the following description of this disclosure, detailed descriptions of known functions or configurations incorporated herein will be omitted where such descriptions might unnecessarily obscure the subject matter of this disclosure. The terms used below are defined in consideration of the functions described in this disclosure and may vary depending on the user, user intent, or convention. Therefore, the definitions of these terms may be based on the entirety of this disclosure. For the same reason, some elements may be enlarged, omitted, or shown schematically in the drawings. Furthermore, the dimensions of each element do not perfectly reflect the actual dimensions. In the drawings, the same reference numerals are used for the same or corresponding elements. The advantages and features of this disclosure, and its implementation, will become apparent from the embodiments described in detail below with reference to the accompanying drawings. However, this disclosure is not limited to the embodiments set forth below, but can be implemented in various different forms. The following embodiments are provided merely to fully disclose this disclosure and to convey the scope of this disclosure to those skilled in the art, and this disclosure is limited only by the scope of the appended claims. Throughout this disclosure, the same or similar reference numerals denote the same or similar elements. Furthermore, in the following description of this disclosure, detailed descriptions of known functions or configurations incorporated herein will be omitted where such descriptions might unnecessarily obscure the subject matter of this disclosure. The terms used below are defined in consideration of the functions described in this disclosure and may vary depending on the user, user intent, or convention. Therefore, the definitions of these terms may be based on the entirety of this disclosure.

[0063] In the following text, a base station is the object that performs resource allocation for a terminal and can be at least one of a gNode B, eNodeB, Node B, base station (BS), radio access unit, base station controller, or node on a network. A terminal can include a user equipment (UE), mobile station (MS), cellular phone, smartphone, computer, or multimedia system capable of performing communication functions. In this disclosure, the downlink (DL) is the radio transmission path for signals transmitted from the base station to the terminal. The uplink is the radio transmission path for signals transmitted from the terminal to the base station. Furthermore, although embodiments of this disclosure have been described with reference to LTE or LTE-A systems, embodiments of this disclosure can be applied to other communication systems with similar technical backgrounds or employing similar channel types. For example, 5G mobile communication technology (5G, i.e., New Radio NR) developed after LTE-A can be included in systems applying embodiments of this disclosure. In the following text, 5G can be a concept that includes legacy LTE, LTE-A, and other similar services. Furthermore, modifications to this disclosure can be made by those skilled in the art without departing from its scope, and this disclosure can be applied to other communication systems. It should be understood here that each box in the flowchart diagram, as well as combinations of boxes in the flowchart diagram, can be implemented using computer program instructions.

[0064] These computer program instructions may be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing apparatus to produce a machine such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for performing the functions specified in one or more flowchart blocks. These computer program instructions may also be stored in a computer-usable or computer-readable storage medium that instructs the computer or other programmable data processing apparatus to operate in a particular manner such that the instructions stored in the computer-usable or computer-readable storage medium produce an article of writing comprising instruction means for performing the functions specified in one or more flowchart blocks. The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer-implemented process, such that the instructions, which execute on the computer or other programmable apparatus, provide steps for performing the functions specified in one or more flowchart blocks.

[0065] Furthermore, each box in the flowchart may represent a module, fragment, or portion of code, which includes one or more executable instructions for implementing the specified logical function(s). It should also be noted that in some alternative implementations, the functions shown in the boxes may not occur in this order. For example, depending on the function involved, two boxes shown successively may actually be executed substantially simultaneously, or the boxes may be executed in reverse order. As used herein, “cell” refers to a software or hardware element that performs a predetermined function, such as a field-programmable gate array (FPGA) or application-specific integrated circuit (ASIC). However, “cell” does not always have a meaning limited to software or hardware. A “cell” can be configured to be stored in addressable memory or to execute on one or more processors. Therefore, a “cell” (for example) includes software elements, object-oriented software elements, class elements or task elements, processes, functions, features, flows, subroutines, fragments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and parameters. The elements and functions provided by a “cell” can be combined into a smaller number of elements or “cells” or divided into a larger number of elements or “cells.” Furthermore, these elements and "units" can be implemented as one or more CPUs within a copying device or a secure multimedia card. Additionally, in embodiments, a "unit" may include one or more processors.

[0066] First, the terminology used in this disclosure will be defined.

[0067] In this disclosure, the UICC is a smart card used by being inserted into a mobile communication terminal. The UICC can be a chip storing personal information, such as network access authentication information, a phone book, and SMS messages associated with a mobile communication subscriber. When accessing mobile communication networks such as GSM, WCDMA, LTE, and 5G, the UICC performs subscriber authentication and traffic security key generation to support secure use of the mobile communication. The UICC can include communication applications such as a Subscriber Identity Module (SIM), a Universal SIM (USIM), or an IP Multimedia SIM (ISIM), depending on the type of mobile communication network accessed by the subscriber, or it can provide a high level of security for loading various applications (such as e-wallets, ticketing applications, e-passports, etc.).

[0068] In this disclosure, an embedded UICC (eUICC) is a security module embedded in a terminal, unlike a removable security module that can be plugged into or removed from the terminal. An eUICC can download and install configuration files using over-the-air (OTA) technology. An eUICC can refer to a UICC capable of downloading and installing configuration files.

[0069] The method for downloading and installing a configuration file using OTA technology according to this disclosure can be applied to removable UICCs that can be inserted into or removed from the terminal. For example, embodiments of this disclosure can be applied to UICCs that can download and install configuration files via OTA.

[0070] The term "UICC" in this disclosure is used interchangeably with the term "SIM," and the term "eUICC" is used interchangeably with the term "eSIM." In this disclosure, the term "eUICC" is used interchangeably with the term "UICC," and the term "UICC" can be used as a concept that includes "eUICC." UICC is a type of security element (SE), and the term "UICC" is used interchangeably with "SE."

[0071] In this disclosure, the configuration file is a software-formatted package containing the application, file system, authentication key values, and other information stored in UICC. Furthermore, the configuration file is also referred to as access information.

[0072] The USIM configuration file in this disclosure may have the same meaning as a configuration file, or it may be something that packages information in a USIM application incorporated into the configuration file in a software format.

[0073] In this disclosure, a configuration file server is a server that provides functionality to generate configuration files, encrypt generated configuration files, generate remote configuration file management commands, or encrypt generated remote configuration file management commands, or may include functionality to support multiple configuration file enablement for terminals. The configuration file server may be referred to as Subscription Manager Data Preparation (SM-DP), Subscription Manager Data Preparation Plus (SM-DP+), or Subscription Manager Secure Routing (SM-SR).

[0074] In this disclosure, the terms "terminal" or "device" may refer to 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 transceiver unit (WTRU), mobile node, mobile phone, or other names. Various examples of a terminal may include a cellular phone, a smartphone with wireless communication capabilities, a personal digital assistant (PDA) with wireless communication devices, a wireless modem, a portable computer with wireless communication capabilities, a photographic device (such as a digital camera with wireless communication capabilities), a game console with wireless communication capabilities, an appliance with wireless communication capabilities for storing and reproducing music, an internet appliance capable of wirelessly accessing and browsing the internet, and portable units or terminals including combinations of these capabilities. Furthermore, a terminal may include, but is not limited to, machine-to-machine (M2M) terminals and machine-type communication (MTC) terminals / devices. In this disclosure, a terminal may be referred to as an electronic device, or simply as a device. Furthermore, the term "terminal" in this disclosure may be used interchangeably with "modem."

[0075] In this disclosure, the terminal or device may include software or an application installed on the terminal or device for controlling the UICC or eUICC. This software or application may be referred to as, for example, a Local Profile Assistant (LPA). In this disclosure, the eUICC identifier (eUICC ID) may be a unique identifier for the eUICC embedded in the device and may be referred to as an EID.

[0076] In this disclosure, the Application Protocol Data Unit (APDU) may be a message used for interoperability between a controller in a terminal or device and the eUICC.

[0077] In this disclosure, the term "configuration package" can be used interchangeably with "configuration file" or can be used as a term to refer to a data object of a specific configuration file. A configuration package can be referred to as a configuration file TLV or configuration file package TLV. The configuration file identifier can be a unique identifier number for the configuration file and can be referred to as an ICCID. If the configuration package is encrypted using encryption parameters, the encrypted configuration package can be referred to as a protected configuration file package (PPP) or a protected configuration file package TLV (PPP TLV). If the configuration package is encrypted using encryption parameters that are only decrypted using a specific eUICC, then the encrypted configuration package can be referred to as a bound configuration file package (BPP) or a bound configuration file package TLV (BPPTLV). A configuration file package TLV can be a dataset that expresses the information of the configuration file in the form of TLV (label, length, value).

[0078] In this disclosure, "AKA" represents authentication and key negotiation, and can be an authentication algorithm used for accessing 3GPP and 3GPP2 networks. K represents the encryption key value, which is used in the AKA authentication algorithm and stored in the eUICC. In this disclosure, OPc is a parameter value used in the AKA authentication algorithm and can be stored in the eUICC.

[0079] In this disclosure, "NAA" refers to a network access application, and can be an application stored in the UICC and used for network access, such as USIM or ISIM. The NAA can also be a network access module.

[0080] In this disclosure, end users, users, subscribers and service subscribers can be used interchangeably with users of the corresponding terminals.

[0081] In this disclosure, the eSIM port can be a virtual interface channel that shares the physical interface between the eUICC and the modem by multiplexing the physical interface. The eSIM can be used interchangeably with the eSIM port, port, and SIM port.

[0082] In this disclosure, the ability to enable and manage multiple profiles included in a single eUICC is generally referred to as a Multiple Enable Profile (MEP) function. A conventional eUICC can only enable one profile at a time, and therefore cannot support dual-SIM or multi-SIM functionality from a single eUICC. To support dual-SIM or multi-SIM functionality using a single eUICC, the single eUICC needs the ability to enable and manage multiple profiles. An eUICC implementing MEP functionality can be referred to as a MEP-enabled eUICC. A terminal including a modem implementing MEP functionality and terminal software capable of supporting MEP functionality can be referred to as a MEP-enabled terminal.

[0083] Furthermore, in the following description of this disclosure, detailed descriptions of known functions and configurations incorporated herein may be omitted where such detailed descriptions would make the subject matter of this disclosure considerably uncertain.

[0084] The proposed embodiments will be described below with reference to the accompanying drawings.

[0085] Figure 1 This is a diagram illustrating the structural elements of the present disclosure in a wireless communication system according to an embodiment.

[0086] User 1-01 can use LPA 1-05 of terminal 1-03 or a terminal application that has implemented LPA 1-05 to request the installation / enable / disable / update of the configuration file in eUICC 1-20, or can provide a user license for remote configuration file management (RPM) processing transmitted from SM-DP+1-40.

[0087] Remote Profile Management (RPM) is a series of processes for installing, enabling, disabling, and deleting profiles, and performing other functions on the profiles based on commands sent from the SM-DP+1-40 to the terminal. RPMs can be requested by communication operators, service providers, or terminal owners, and commands can be generated by the SM-DP+1-40. The LPA 1-05, which receives user input associated with requests or permissions for the management of a corresponding profile, can manage or control the operation of the eUICC 1-20 by sending messages to the eUICC 1-20 based on that user input.

[0088] The terminal's communication modem 1-15 is a device that modulates and transmits signals for sending information and demodulates the modulated signals back to the original signals at the receiving end. In the case of an MEP-supported modem, two or more baseband processors (hereinafter referred to as baseband) may be included for wireless communication. Modem 1-15 is connected to the eUICC and a single physical pin (at the time of providing this disclosure, a smart card interface with the ISO7816 standard is used), and if the modem sends an Application Program Protocol Data Unit (APDU) command via the corresponding interface, then eUICC 1-20 sends the resulting value as a response.

[0089] If eUICC 1-20 has a message to send to modem 1-15, then eUICC 1-20 can send (transmit) a response code (e.g., SW1 (Status word) = 91, SW2 = XX), thereby indicating that eUICC 1-20 has a message to send and that the message is a response to an APDU command sent by modem 1-15. Through the above operation, eUICC 1-20 can notify modem 1-15, enabling modem 1-15 to receive the "message that eUICC 1-20 wants to send to modem 1-15" via the basic channel.

[0090] Modem 1-15 sends a FETCH command APDU to eUICC 1-20 via this basic channel, and eUICC 1-20 can respond by sending a response APDU. In this example, the message to be sent by the eUICC, such as an active command, can be included in the data portion and can be sent. This active command could be a request to reset the UICC or change its configuration file state. (See reference...) Figures 4A to 4C as well as Figure 8A and Figure 8B A more detailed description of it will be provided.

[0091] LPA 1-05 can be software operating on a terminal platform, and the functionality of the LPA can be partially integrated into the terminal platform. Messages sent by LPA 1-05 to eUICC 1-20 can ultimately be sent to eUICC 1-20 via the terminal platform or via the terminal platform and modem 1-15, and eUICC 1-20, upon receiving the corresponding message, can perform configuration file management according to the commands sent from the LPA.

[0092] Although for ease of description, it is assumed that there are two configuration files in eUICC 1-20, namely configuration file 1 and configuration file 2, as shown below. Figure 1 However, this is not the only possibility. It is understood that, depending on the capabilities of eUICC 1-20, eUICC 1-20 may include more configuration files. In MEP-supported eUICC, configuration files 1.1-25 and 2.1-30 can be enabled simultaneously. In eUICC that does not support MEP, only one of configuration files, either 1.1-25 or 2.1-30, can be enabled.

[0093] The issuer security domain root (ISD-R) 1-35 can generate new issuer security domain profiles (ISD-P) (e.g., security domains for hosting profiles) and can provide the LPA with the eUICC data and services required for LPA functionality (e.g., local profile management and profile metadata information).

[0094] Although not shown for ease of description, eUICC 1-20 in the figure may include an embedded UICC control authorization security domain (ECASD), which is used to store the credentials required for the security domain of the eUICC (e.g., the root public key of the certificate issuer for verifying the SM-DP+ authentication certificate, the key set of the eUICC manufacturer, etc., the space for the eSIM platform, etc.).

[0095] SM-DP+ server 1-40 is a configuration file server. As mentioned above, a configuration file server can be a server that includes functions such as generating configuration files, encrypting the generated configuration files, generating remote configuration file management commands, or encrypting the generated remote configuration file management commands, or it can be a server that includes functions such as supporting the enabling of multiple configuration files on the terminal. Terminal 1-03's LPA 1-05 receives SM-DP+ remote management commands from SM-DP+ server 1-40, obtains user consent through interaction with user 1-01, and transmits the corresponding remote management commands to eUICC 1-20, thereby processing the enabling / disabling / deleting / updating.

[0096] The eUICC 1-20 may be provided either as fixed to a terminal or as detachable. Considering the fixed-to-terminal form, the eUICC 1-20 may be exemplified as one of the entities of terminal 1-03. However, the eUICC is shown as a separate entity to include the case of the detachable eUICC 1-20 in this disclosure.

[0097] Figure 2A and Figure 2B This is an example illustrating the connection between a modem and a current v2 eUICC that does not support MEP.

[0098] In the current v2 eUICC, only a single profile can be enabled within the eUICC, and local profile management by users without SM-DP+ intervention is allowed to handle enabling / disabling / deleting / updating previously installed profiles. If a physical SIM is used with the eUICC, the modem 2-01, which does not support MEP, may include one or more basebands. However, in this disclosure, the description is provided assuming the use of a single baseband.

[0099] During the initialization process between the terminal platform, modem, and eUICC (initialization between the terminal and the card), the terminal can generate a channel for APDU after receiving a reset response (ATR) from the eUICC, so as to transmit data between the modem and the eUICC at a specific point in time.

[0100] In v2 eUICC 2-15, only one configuration file can be enabled at a time.

[0101] Figure 2A Case 1 2-100 is the case where configuration file 1 2-20 is enabled and configuration file 2 2-25 is disabled. Figure 2B Case 2 2-200 is the case where profile 1 2-20 is disabled and profile 2 2-25 is enabled. According to Case 1 2-100, if a single enabled profile needs to send APDUs to the modem's baseband, then eUICC 2-15 sends the corresponding APDUs via a single channel connected to physical interface 2-10 of modem 2-01.

[0102] If ISD-R 2-30 receives an ES10c.EnableProfile(Profile2) request from LPA for a change in profile state (e.g., from case 1 2-100 to case 2 2-200), then ISD-R 2-30 can send an APDU to modem 2-10 as a REFRESH active command to delete previously cached data of the profile and restart the application session.

[0103] Furthermore, if the ISD-R 2-30 receives a request from the LPA for resetting the eUICC memory, the ISD-R 2-30 can send an APDU to the modem 2-10 as a REFRESH active command to delete previously cached data in the UICC and restart the application session. APDUs sent by the ISD-R 2-30 to the modem 2-01 can also be sent via a single channel of the physical interface 2-10.

[0104] Figure 3A and Figure 3B This is an example illustrating the connection between a modem and a v3eUICC, based on the concept of a virtual interface.

[0105] Figure 3A and Figure 3B Assume that eUICC 3-20 is an eUICC that supports MEP functionality, enabling multiple profiles simultaneously. Furthermore, assume that modem 3-01 is a modem that supports MEP functionality. Figure 3A and Figure 3B The description is provided using the example of two basebands and two enabled profiles. Although there may be mapping switching between the baseband and eSIM port in modem 3-01, cases 1 and 2 describe the logical terminal endpoint mapping in modem 3-01 using baseband 1 3-05-channel 1 1-40 and baseband 2 3-10-channel 2 1-45 as examples.

[0106] like Figure 2A and Figure 2B As described above, the current modem 1-15 is connected to the eUICC 1-20 via a single physical pin, and the corresponding modem and eUICC can send APDU commands via a single channel 2-10 using their respective physical pins. The MEP-enabled eUICC 3-20 can enable multiple profiles, and the enabled profiles may require APDU transmissions using the modem's baseband. Therefore, to address this, a concept can be adopted that multiplexes physical interface 3-15 and sends APDUs individually via multiple channels 3-40 and 3-45.

[0107] In the following text, for ease of description, if MEP is supported, the channel will be referred to as an eSIM port. The channel is referred to as an eSIM port, for example, eSIM port 1 3-40 and eSIM port 2 3-45. After a UICC reset or configuration file state change, the terminal can generate an APDU channel for transmission between the modem baseband and eUICC during the initialization process between the terminal platform, modem, and eUICC. In this example, the terminal can set an ID for each eSIM port connected to the baseband. The corresponding port ID can be set in the modem or terminal platform, and this port ID can be transmitted to the LPA. In this disclosure, for ease of description, port ID and port number can be used interchangeably.

[0108] The modem may include as many eSIM ports as the baseband. However, the number of eSIM ports utilized by the eUICC3-20 may be less than or equal to the number of profiles that can be enabled simultaneously in the corresponding eUICC. Profiles may use one of the eSIM ports to send APDU messages.

[0109] according to Figure 3A In case 1 3-100, the APDU command corresponding to enable configuration file 1 3-25 can be sent to baseband 1 3-05 via eSIM port 1 3-40, and at the same time, the APDU command corresponding to enable configuration file 2 3-30 can be sent to baseband 2 3-10 via eSIM port 2 3-45.

[0110] according to Figure 3B In case 2 3-200, the APDU command corresponding to enable configuration file 1 3-25 can be sent to baseband 2 3-10 via eSIM port 2 3-60, and at the same time, the APDU command corresponding to enable configuration file 2 3-30 can be sent to baseband 1 3-05 via eSIM port 2 3-55.

[0111] The MEP-supported modem 3-01 can process APDU commands sent via each eSIM port differently by identifying the baseband to which the corresponding APDU command is connected. The ISD-R 3-35 may need to send APDU command 3-50 to the modem to manage the profile and eUICC status. In this example, the ISD-R 3-35 can perform this sending via two schemes.

[0112] 1) Multiple Selection Scheme: The LPA or modem can determine whether to select the ISD-R 3-35 via multiple eSIM ports during the initialization process between the eUICC and the terminal card, or it can operate to select the ISD-R 3-35 using multiple eSIM ports based on the settings between the terminal and the card. This scheme is called the multiple selection scheme. In the multiple selection scheme, the LPA or modem can send a command APDU (command message) to the ISD-R 3-35 via one of the selected eSIM ports, or it can send a command APDU to identify whether the ISD-R 3-35 has an event to process or an APDU to send. The ISD-R 3-35 can select the corresponding eSIM port based on whether the command message received from the LPA or modem corresponds to a management message in profile 1 3-25 or profile 2 3-30, or a management message in both profile 1 3-25 and profile 2 3-30, or a message associated with the entire eUICC, and can respond by sending an APDU including an active command via the selected port. Alternatively, even in the case of ISD-R with multiple selectable schemes, ISD-R can also send management messages corresponding to profiles 13-25 and 23-30, or messages associated with the entire eUICC, via the eSIM port selected by the LPA or modem for command message transmission. Figure 9A and Figure 9B An additional example of multiple candidate options is shown in the figure.

[0113] 2) Non-Multiple Selection Scheme: The LPA or modem can determine that the ISD-R 3-35 is selected via a single eSIM port during the initialization process between the eUICC and the terminal card, or can operate to select the ISD-R 3-35 using a single eSIM port based on the settings between the terminal and the card. This scheme is called the non-multiple selection scheme. In the non-multiple selection scheme, APDUs can be sent or received between the terminal and the ISD-R 3-35 only via the selected single eSIM port. The eSIM port used by this ISD-R can be equivalent to the eSIM port occupied by the configuration file, or it can be a separate ISD-R-dedicated eSIM port. When the ISD-R 3-35 needs to send a response APDU including an active command to the modem, if the ISD-R 3-35 sends the response APDU to the modem 3-01 via the eSIM port selected by the ISD-R 3-35, then the modem 3-01 can interpret the information associated with the received response APDU and can execute the requested command.

[0114] Figure 4AThis is a flowchart illustrating the method by which the eUICC's ISD-R sends a REFRESH message (Case 1) to the modem to change the state of the configuration file.

[0115] Figure 4B and Figure 4C A flowchart is shown illustrating the method by which the eUICC's ISD-R sends a REFRESH message for memory reset to the modem (Case 2).

[0116] According to embodiments of this disclosure, if the LPA receives input from a user of the terminal requesting a change in the status of a profile installed in the eUICC (enabled to disabled or disabled to enabled), the LPA can send an ES10c.EnableProfile message or an ES10c.DisableProfile message to the eUICC. When sending the corresponding message, the LPA can include a refreshFlag as an identifier in the message, which is used to determine whether the eUICC needs to send an active command associated with REFRESH to the modem, and send the message in operation 4-05. In operation 4-10, the eUICC determines whether to send REFRESH to the modem based on the refreshFlag in the corresponding ES10C message. If REFRESH needs to be sent, the eUICC can include information indicating that a refresh is required as an active command (providing a response scheme including the message that the eUICC needs to send in response to a message sent by the modem to the eUICC) and send it out. For example, this could be an active REFRESH command. The message used to indicate that a refresh is needed can be determined based on whether eUICC is currently working in MEP mode in operation 4-15 and whether ISD-R multi-selection is available (or whether ISD-R is subject to multi-selection) in operation 4-25.

[0117] During the initial connection establishment process between the terminal and the eUICC, the terminal modem may generate an eSIM port and send an APDU command associated with opening the generated port to the eUICC, or it may send an explicit command to the eUICC indicating that it is operating in MEP mode. Alternatively, the terminal modem may identify MEP support based on a reset response (ATR) received from the eUICC and may send identification information indicating MEP support to the eUICC, thereby notifying the eUICC that it needs to operate in MEP mode from now on. Whether the eUICC is currently operating in MEP mode in operations 4-15 can be determined by the eUICC based on whether the eUICC can receive and implement the command associated with opening the eSIM port received from the modem, whether the eUICC has received an explicit command indicating that it is operating in MEP mode, or whether the eUICC supports MEP, has received identification information from the modem indicating that it supports MEP and has configured itself to operate in MEP mode. Alternatively, if the configuration file information collected or collected and stored by ISD-R includes information associated with the mapping between configuration files and ports, then eUICC can perform determination based on the corresponding mapping information. This process can be determined before the procedure begins with operation 4-01.

[0118] When the configuration file status is changed, the active commands sent by the eUICC to the modem may include the information below. The type of active command may be based on ETSI TS 102.223. Response APDUs including active commands can be processed according to ETSI TS 102.221. As described above, if the (e)UICC has a message to send to the terminal, the active command can be included as data in the response value sent from the UICC in response to the FETCH command, and it can be sent. Active commands can be expressed in the form of Type-Length-Value (TLV), and the type and mode of the active command can be indicated by a data field in the value. Referring to ETSI TS.102.223, active commands can have the structure shown in Table 1 below.

[0119] Table 1

[0120] describe Terms and Conditions M / O / C Min length Active UICC command tags 9.2 M Y 1 Length (A+B+C+...+N) - M Y 1 or 2 Command details 8.6 M Y A Device Identity 8.7 M Y B Value C Value...N

[0121] In Table 1, the "Command Details" field can be provided in TLV format as shown in Table 2 below.

[0122] Table 2

[0123]

[0124]

[0125] If an active command including (multiple) port numbers is sent, a new REFRESH mode or a new active type (or a new command type) can be defined (at the level equal to REFRESH), which contrasts with existing eUICC profile state changes or existing UICC reset modes.

[0126] 1) If a new command type is defined, there can be a UICC reset value associated with a specific port or a value for a new type defined for eUIC profile state changes, instead of the REFRESH type. The new type for eUICC profile state changes can be a type such as "Platform Reset" or "Port Reset". Alternatively, the new command type can be defined as "Reset" and can be categorized based on the command qualifiers of the corresponding type.

[0127] - In the case of RESET (example of new type):

[0128] ●"00" = Platform reset;

[0129] ●"01" = Port Reset

[0130] 2) If a new mode is added as one of the "REFRESH" modes, then the new mode can be expressed as a subordinate identifier value of Type=REFRESH using command qualifiers such as 0B or 0C.

[0131] - In the case of REFRESH:

[0132] ●"00" = NAA initialization and full file change notification;

[0133] ●"01" = Document Change Notification;

[0134] ●"02" = NAA initialization and file change notification;

[0135] ●"03" = NAA initialization;

[0136] ●"04" = UICC reset;

[0137] ●"05" = NAA application reset, applicable only to 3G platforms;

[0138] ●"06" = NAA Session Reset, applicable only to 3G platforms;

[0139] ●"07" = 3GPP reserved ("Roaming Operation" REFRESH support);

[0140] ●"08" = 3GPP reserved (for roaming operations of I-WLAN);

[0141] ●"09" = eUICC configuration file status changed;

[0142] ●"0A" = Application Update;

[0143] ●"0B" = Port Reset

[0144] ●"0C" = Platform Reset

[0145] When defining a command type or new mode, you can add a field indicating the port number(s) that need to be refreshed or indicating "all" as the field for the value of an active command.

[0146] 3) One or more port numbers or "all" can be reported using one of the existing patterns in the REFRESH state without adding a new pattern. The field indicating the port number(s) or "all" that need to be refreshed can be added or provided as a value of the TLV of an active command, or it can be reported by adding a value to one of the TLVs of an existing active command.

[0147] In this disclosure, although the operation of UICC reset mode and eUIC profile state change mode in various REFRESH modes is illustrated as representative embodiments, the scope of this disclosure is not limited thereto.

[0148] • Cases where eUICC does not operate in MEP mode:

[0149] The eUICC selects and sends either an eUICC profile state change or a UICC reset in the usual manner. In operation 4-15, if the eUICC is not operating in MEP mode, it can be assumed that the eUICC and modem do not support MEP, or that the eUICC and modem support MEP but do not use the corresponding function (disabled). The situation where the eUICC and modem support MEP but do not use the corresponding function (disabled) can include situations where two basebands exist in the modem, but respectively, one eUICC occupies and uses one baseband and one SIM card occupies and uses the other baseband.

[0150] • When eUICC operates in MEP mode and ISD-R performs multiple selection of the eSIM port:

[0151] To send a refresh message, the eUICC can determine which ports to select for connection to the profile whose state has changed (as opposed to using a single dedicated ISD-R port), allowing the ISD-R to send the refresh message via each port in operation 4-27. In this example, the eUICC's ISD-R can select either the eUICC profile state change mode or the UICC reset mode, and can perform the transmission via the port to be refreshed in operation 4-30 without a port number. Alternatively, although the ISD-R performs multiple selections of eSIM ports, if the ISD-R expects to send a refresh-related message to one of its ISD-R ports, then in operation 4-35, the port number # of the port to be refreshed can be added to the message and sent. Alternatively, if the ISD-R expects to refresh multiple ports, then multiple port numbers # can be sent.

[0152] • When eUICC operates in MEP mode and ISD-R does not support multiple selection of eSIM ports:

[0153] The eUICC's ISD-R can request a refresh of a specific port in a single transmit port in Operations 4-35. For example, the request message can be a REFRESH active command. The port or eSIM port designated for selecting ISD-R during initialization between the terminal and the eUICC can be referred to as the default port, default eSIM port, or ISD-R eSIM port. As mentioned above, the ISD-R eSIM port can be a dedicated ISD-R port independent of the port used in the configuration file, or it can be a port shared with the configuration file.

[0154] The eUICC's ISD-R can set the REFRESH mode to the eUICC profile state change mode and send a message including the port identifiers of the ports to which the modem needs to apply REFRESH. In this example, multiple port identifiers of the ports to which REFRESH will be applied can be included and sent.

[0155] The eUICC ISD-R can set the REFRESH mode to UICC reset mode and send a message including the port identifiers of the ports to which the modem needs to apply REFRESH. In this example, multiple port identifiers of the ports to which REFRESH will be applied can be included and sent.

[0156] The modem that receives the message can perform a previously defined operation according to the corresponding command, and will refer to... Figure 8A and Figure 8B Describe the operation of the modem in detail.

[0157] In the case where the eUICC receives an ES10c.eUICCMemoryReset from the LPA during operations 4-45, if one or more enabled profiles exist in the eUICC, the eUICC can request a REFRESH from the modem using an active command. In the case of an eUICC memory reset, all enabled profiles for that terminal need to be disabled. Therefore, in addition to the determination process associated with REFRESH based on profile state changes, considering the number of enabled profiles, the eUICC can send an active REFRESH command to the modem using one of the following methods.

[0158] 1. Situations where there are two or more enabled configuration files.

[0159] >A. If ISD-R cannot implement multiple selection schemes, then the operation is performed based on whether a platform reset is performed according to the eUICC settings.

[0160] >>i. If a platform reset is performed, then ISD-R may add an identifier indicating "all eSIM ports" (e.g., "all") when sending a REFRESH command in eSIM profile state change or UICC reset mode to the modem via a single eSIM port in Operations 4-60. This could be a new REFRESH mode or a new active type (at the level equal to REFRESH), which is a command that implements a REFRESH command in eUICC profile state change mode or UICC reset mode for all ports, and this situation can be referred to as (e.g.) a platform reset.

[0161] >>ii. If a platform reset is not performed, then ISD-R may add an identifier indicating a list of multiple eSIM ports (e.g., #1 and #2) when sending a REFRESH command for eUICC profile status change or UICC reset mode to the modem via a single eSIM port in Operation 4-73.

[0162] >B. If the ISD-R is capable of implementing multiple selection schemes, the ISD-R sends an active command REFRESH to the modem for each port in Operations 4-65 to implement an eUICC memory reset.

[0163] >>i.ISD-R can send REFRESH commands for eUICC profile status change or UICC reset mode to the modem simultaneously or sequentially via two eSIM ports in Operations 4-70.

[0164] >C. If the ISD-R is subject to multiple selection, the ISD-R performs an eUICC memory reset by sending an active command REFRESH through a single port selection in operations 4-58.

[0165] >>i. Operations 4-60 or 4-73 can be performed.

[0166] 2. Enabling a configuration file

[0167] A. Send a REFRESH command to the modem according to one of the steps 4-30 or 4-35 described above.

[0168] If MEP supports eUICC for refreshing, then... Figure 4A If the state of the configuration file is changed as described in Case 1, then eUICC can send a REFRESH message in Operations 4-20, 4-30 or 4-35 as appropriate, and can receive a TERMINAL RESPONSE from the modem (in the case of a change in the eUICC configuration file state) or can be reset (in the case of a UICC reset, a TERMINAL RESPONSE is not required) and can complete the change in the state of the corresponding configuration file.

[0169] If due to like Figure 4B In Scenario 2, where an enabled profile exists in the eUICC, requiring the MEP to send a REFRESH command to the modem to reset the eUICC memory, the eUICC can delete everything regardless of whether the installed profile is enabled or disabled. A REFRESH active command can be sent to the modem by selecting one of operations 4-30, 4-35, 4-60, 4-70, and 4-73 as described above. If no enabled profile exists and only deletion is performed, the eUICC does not need to send a REFRESH active command. In the above description, sending a REFRESH active command, including a port number, via a specific port can include the eUICC sending a refresh request, including a port number, via a port, and the eUICC preparing and sending a REFRESH active command via the port corresponding to the port number being sent.

[0170] Figure 5 This is a flowchart illustrating a method for enabling a local configuration file in a processing terminal according to this disclosure.

[0171] As mentioned above, the v2 eUICC, which does not support MEP functionality, is designed to enable only one profile. If a pre-enabled profile exists, the v2 eUICC needs to change the status of the enabled profile to disabled in order to enable the other profile. However, when the eUICC that supports MEP functionality executes the profile enable command, depending on the location of the eSIM port where the profile will be enabled, there may be situations where the eUICC should not disable the currently enabled profile. For example, if the eSIM includes eSIM port 1 and eSIM port 2, and profile 2 is currently enabled on eSIM port 2, if the eUICC additionally enables profile 1 on eSIM port 1, then the eUICC can perform the process of not disabling profile 2 currently enabled on eSIM port 2.

[0172] Furthermore, if the terminal has a baseband that supports different Radio Access Technologies (RATs), the RATs available via the corresponding profile may differ depending on the baseband and the matching eSIM port. Therefore, information is needed that the user or server (in the case of RPM) can use when determining which profile to enable will match their eSIM port. For example, if eSIM port 1 matches a baseband supporting 4G networks and eSIM port 2 matches a baseband supporting 5G networks, the information mentioned above can be helpful in selecting the appropriate eSIM port for enabling a specific profile if the user or server performing remote management is aware of this information.

[0173] The number of profiles simultaneously enabled in the eUICC at a given point in time can be limited to be less than or equal to the number of eSIM ports allocated by the eUICC. If it is expected that profiles will be enabled by the user or SM-DP+, the eUICC can send the maximum number of profiles that can be enabled in the eUICC to the LPA or SM-DP+ server, taking into account the number of currently enabled profiles and the number of eSIM ports.

[0174] The LPA or terminal software can use information passed by the eUICC (e.g., the number of eSIM ports allocated by the eUICC) as information to use when the LPA notification requires disabling the currently enabled profile.

[0175] Furthermore, if the LPA sends an enable message including the port number to the eUICC, the eUICC receiving the message can process it and can send a refresh-related message including the port number to the modem in operations 5-65 (e.g., a REFRESH active command), or can send a response message with the port number in operations 5-90. The modem can receive one of the messages from the eUICC or the LPA, perform a refresh for the corresponding port, or reset the corresponding port. Figure 5 This is a flowchart illustrating the process of enabling a configuration file, serving as an example of how user 5-01 manages configuration files in the MEP support terminal using LPA 5-05. (See also...) Figure 5 The description provides the scenario where all eUICC 5-10, modem 5-15, and LPA 5-05 support MEP.

[0176] In operation 5-20, end user 5-01 executes the enable command associated with the configuration file installed in the terminal based on information displayed by LPA 5-05 or an application that implements and integrates LPA 5-05. (See also...) Figures 6A to 6D This describes an example of the screen displayed on the user's screen when the corresponding enable command is executed. In addition to displaying a list of profiles installed in the eUICC and their current status information, the LPA 5-05 or the corresponding application on the terminal can also display one or more of the following information: radio access technology provided for each baseband of the terminal's modem, matching eSIM port information for APDU transmission between the baseband and the corresponding profile, and the profile occupancy status of (multiple) ports obtained from the eUICC. In this example, the LPA can identify the profile policy rules and can additionally display warning messages, such as a message indicating that profile enable is unavailable, to the user.

[0177] If user 5-01 selects and confirms enabling a specific profile, such as profile 3, via the information displayed on the screen, then LPA 5-05 can send an ES10c.EnableProfile(ISD-P AID (Publisher Security Domain - Profile Application ID) or ICCID (Profile ID), refreshFlag, port number) command to eUICC in operation 5-30, including the port number matching the selected baseband. If the port number is not determined at the corresponding time, LPA 5-05 can send the message of operation 5-30 without a port number, or it can send the message of operation 5-30 with identification information indicating that eUICC needs to determine the port number and perform processing. If eUICC determines the port number, eUICC can include the port number in a response message, and can send that message as a response to LPA in operation 5-90. Messages sent by LPA to eUICC can be sent by including them in the data of the command APDU sent by the modem to eUICC. Messages sent by eUICC to LPA can be sent by including them in a response APDU. A specific port number (e.g., -1) can be used as an identifier to indicate that the eUICC needs to determine the port number. If a response message sent to the terminal via the card requests a refresh, for example, if a REFRESH active command is required, then refreshFlag can be additionally set and sent. If refreshFlag is not set, and a previously enabled profile exists, the terminal may need to meet the conditions for enabling the profile in MEP mode, such as terminating the application session associated with the port occupied between the UICC and the modem via the terminal's implementation, shutting down a logical interface or channel, etc.

[0178] If eUICC 5-10 receives a corresponding profile enable command from LPA 5-05 in Operation 5-30, eUICC can perform the process of disabling the profile (profile 1) occupying the corresponding port and can perform the enable process for the corresponding port. In Operation 5-35, eUICC 5-10's ISD-R can identify the corresponding profile 3 to be enabled, the enable status of the profiles pre-installed in eUICC, and the profile policy rules (PPR), and can comprehensively determine whether the enable of corresponding profile 3 is available. If enable is unavailable, ISD-R can send an error message to the user in response. When eUICC 5-10 with MEP support determines whether the enable of corresponding profile 3 is available in Operation 5-35, if the port on which profile 3 is expected to be enabled is already occupied by another profile (e.g., profile 1), eUICC can determine to change the status of profile 1, which is already using the corresponding port, to disabled and change the status of profile 3 to enabled to process the enable on the corresponding port. If profile 3 uses an empty port, then MEP-enabled eUICC 5-10 can be enabled without performing the process of disabling another profile in the eUICC. In embodiments where refreshFlag is set and a profile state change is performed, the eUICC can send a command to the modem requesting a refresh and can request processing of operations associated with the profile state change.

[0179] For example, when using the REFRESH active command, the corresponding eUICC can be as follows: Figure 4A and Figure 4B As described above, sending a REFRESH active command to the modem enables the modem to perform actions such as... Figure 8A and Figure 8B The process described herein. Based on the result obtained after the modem processes the corresponding REFRESH, the eUICC can receive a terminal response in operations 5-70 (if an eUICC profile state change is sent) or a RESET (if a UICC reset is processed), and can match the selected profile 3 to the port number sent in operations 1-30. If a previously enabled profile (profile 1) exists on the corresponding port, the eUICC can disable that profile and perform the enabling process. If the enabling process is performed on an unoccupied port, the eUICC can enable only the corresponding profile 3 in operations 5-75 and complete the process.

[0180] If refreshFlag was not set in operation 5-30, then eUICC can match the selected profile 3 to the port number sent in operation 1-30 after operation 5-35. If a previously enabled profile (profile 1) exists on the corresponding port, then eUICC can disable that profile and perform the enabling process. If eUICC performs the enabling process on an unused port, then eUICC can enable only the corresponding profile 3 in operation 5-85.

[0181] eUICC 5-10 can send the result of the corresponding procedure as a response to LPA5-05 in Operation 5-90. The corresponding message sent in response may include the port(s) number(s) that require port reset. Furthermore, even if a message without a corresponding port(s) number is received, LPA 5-05 can determine the port(s) that require port reset, include the port(s) number in the message, and send the message to the modem.

[0182] LPA 5-05 may include a message containing port(s) received from the eUICC or determined and added by the LPA, and send the message to modem 5-15, enabling the modem to perform a refresh, such as an eUICC profile state change or UICC reset, for example, deleting the cached value associated with the corresponding connected port based on the profile state change. Furthermore, the modem may perform the TERMINAL PROFILE procedure as defined in section 14.5.1 of ETSI TS 102 221 in operation 5-95. Next, in the baseband connected to the corresponding port, LPA 5-05 may perform a network attachment procedure in operation 5-100 based on information associated with the profile of the newly connected port. If refreshFlag is not set, then... Figure 11 The method of sending a REFRESH command to a modem is described in detail.

[0183] Although not shown in the diagram, if ISD-R receives port information associated with a port mapped to a configuration file from LPA, ISD-R can update the metadata of the corresponding configuration file with that information. This information can be provided when LPA requests information from ISD-R for local configuration file management or when LPA requests information for remote configuration file management for SM-DP+. ISD-R can provide status information of the installed configuration files, mapping information between the corresponding configuration files and ports, and information associated with configuration files enabled in eUICC. Furthermore, eUICC's ISD-R can provide LPA with information related to whether a configuration file can be executed independently or in conjunction with another configuration file when it is installed or enabled by additionally specifying a Configuration File Policy Rule (PPR) in the configuration file's metadata, indicating whether the configuration file is available in the MEP environment. Therefore, users or the SM-DP+ server can use this information.

[0184] According to an embodiment, the LPA can obtain a port number and send a configuration file management command message including the obtained port number to the eUICC. The eUICC can identify the information associated with the refreshFlag and the port number in the received message and can connect to the configuration file using the specified port number. In this example, if no port number is received or the eUICC has separate identification information associated with the configured port, the eUICC can additionally determine the configuration file's connection on a specific port and perform processing. Furthermore, the eUICC can directly send a message including the port number to the modem or the LPA based on changes in the configuration file status, causing the modem to perform a refresh on the port corresponding to the received port number.

[0185] Figure 6A , Figure 6B , Figure 6C and Figure 6D This is an illustration of an implementation example of a configuration file management screen provided to an end user by a MEP support terminal according to this disclosure.

[0186] As described above, via the LPA or the application screen implementing the LPA, users can receive information associated with the profile installed in the eUICC, as well as profile status information (such as enabled / disabled status). Furthermore, the MEP terminal provides the capability for radio access technology for each baseband in the modem, information associated with which baseband is connected to which eSIM port, and information associated with the existence of an enabled profile using the corresponding port (whether the port is occupied). Therefore, users can determine the port used to enable a profile in the eUICC via the corresponding screen. The corresponding information can be information displayed to the user via the LPA or the application screen implementing the LPA for local profile management. For remote profile management (RPM) via the SM-DP+ server, this corresponding information can be... Figure 7 The deviceinfo port capabilities are sent together, and based on the combination of corresponding information, SM-DP+ can determine which ports to enable / disable on the configuration file and can send it as a response to the terminal. Figure 6A , Figure 6B , Figure 6C and Figure 6D This shows a representative combination of various combinations that can be displayed to the user: Figure 6A Case 1 6-01 Figure 6B Case 2 6-05 Figure 6C Cases 36-55 and Figure 6D Cases 4, 6-80 will be described, and will be provided under the assumption that eSIM port 1 is connected to the modem’s 4G-enabled baseband and eSIM port 2 is connected to the modem’s 5G-enabled baseband.

[0187] The terminal can combine port information, configuration file status information, configuration file list, and at least one piece of information that can be provided in RAT, and can present all or part of the combination to the user.

[0188] In expectation Figure 6A In scenario 1 (6-01), if configuration file 3 is enabled and the user specifies a change in the status of the corresponding configuration file as shown in Figure 6-15, the terminal needs to change the status of configuration file 1 to disabled, because configuration file 3 only supports 4G in this example. Therefore, the terminal may need to explicitly notify its user, as shown in Figure 6-20, to obtain user consent before proceeding with the next steps. (See the reference below.) Figure 7In the case of RPM as described, the information shown in Figure 6-10 can be sent to the SM-DP+ server as eSIM port capability. Based on the combination of the RAT information of each connected baseband and the port occupancy status of the eSIM port capability, SM-DP+ can display screen 6-23 to the user, obtain the user's consent, and complete the RPM-Enable process.

[0189] Figure 6B Scenario 2, 6-05, describes the scenario where the desired profile is enabled to support 4G or 5G radio access technologies. In this example, if the user wishes to enable the profile, the terminal can be configured with a screen, as shown in Figure 6-40, allowing the user to make additional choices. The user may enable the profile for port 1 or port 2, and the terminal can receive the user's final selection, output the corresponding result, and display it to the user. With RPM-Enabled, the SM-DP+ server can determine a single port based on a combination of RAT information for each connected baseband and port occupancy status of the eSIM port capability, for example, selecting the highest radio access technology, and can provide a command associated with enabling on the corresponding port, as shown in Figure 6-23. Alternatively, the SM-DP+ server can send a message associated with additional user selections or a URL including the corresponding message to the terminal. The terminal can obtain user consent based on the corresponding information, as shown in Figures 6-50 and 6-40, and the server can receive this consent. The server can then enable the profile on the finally selected port and display the corresponding result value to the user, as shown in Figure 6-45.

[0190] Figure 6C Case 3 (6-55) is a situation where the radio access technology (e.g., 4G) supported by the desired configuration file 3 does not match the radio access technology (e.g., 5G) supported by the baseband connected to the unused port 2. In this example, configuration file 1, which occupies the port connected to 4G, is disabled, and the corresponding port can be used. In this example, with the local configuration file enabled, the screen shown in Figure 6-70 can be configured and displayed. Alternatively, with RPM-Enabled, the screen shown in Figure 6-75 can be configured and displayed.

[0191] Figure 6DCase 4 (6-80) describes a situation where an unused port exists in the eUICC, and it is expected that the radio access technology supported by the enabled profile 3 matches the radio access technology supported by the baseband connected to the unused port 2. Therefore, the corresponding port 2 can be used without disabling another profile. In this example, with the local profile enabled, the screen shown in Figure 6-90 can be configured and displayed. Alternatively, with RPM-Enabled, the screen shown in Figure 6-95 can be configured and displayed.

[0192] Figure 7 This is a flowchart illustrating a method for handling remote configuration file enabling (RPM-Enable) by a terminal and a configuration file server according to this disclosure.

[0193] To manage (enable / disable / delete / update) configuration files downloaded to the terminal, method 7-25 can be performed, in which the user sends the corresponding command to the eUICC 7-10 via the terminal's LPA 7-05 at the local level, and the LPA 7-05, eUICC 7-10, and modem 7-15 can process it and send the result as a response to the user 7-01. (See also...) Figure 5 A detailed description of the enabling process (enabling) in local configuration file management is provided, therefore its description will be omitted. The configuration file management server 7-20 can, instead of user 7-01, remotely send requests to the terminal 7-30 to manage (enable / disable / delete / update) configuration files pre-downloaded in the terminal, based on specific data sent from the terminal.

[0194] Reference numerals 7-35 or 7-80 illustrate an example of the normal process by which a terminal according to an embodiment of the present disclosure receives and processes remote management commands from a profile server. If the terminal 7-33 supports a Multiple Enabled Profile (MEP) mode, the process that needs to be changed compared to the previous one is shown in the corresponding figures. The terminal 7-33 may be a terminal that includes an eUICC 7-35 and has an LPA 7-40 installed for controlling the eUICC 7-35. Furthermore, one or more profiles may be installed in the terminal or the eUICC 7-35. In addition, in each installed profile, one or more profile servers capable of remotely controlling the corresponding profile may be specified. Although an example of a manager profile server (which manages SM-DP+) or SM-DP+ is shown below as a profile server, the profile server of the present disclosure is not limited to this. The list of specified manager profile servers may include the address or unique identifier (object identifier) ​​of each manager profile server written in the form of an IP address or FQDN. Although not shown in the figures, remote profile management commands requested by the communication operator may be generated and ready for use in the profile server 7-45.

[0195] In operation 7-60, configuration file server 7-45 can send the remote configuration file management command to LPA7-40. For example, configuration file server 7-45 can use an authenticated client response message in operation 7-60 that includes at least one remote management command and the digital signature of configuration file server 7-45. The digital signature of configuration file server 7-45 can be calculated based on at least one remote management command. Although the diagram illustrates an example of sending only a single "Enable Configuration File" remote management command in operation 7-60, one or more remote management commands can be sent. It should be understood that the command does not necessarily have to be an "Enable Configuration File" remote management command, but can be various types of remote management commands, such as "Disable Configuration File," "Delete Configuration File," etc.

[0196] refer to Figure 7 Operation 7-50 can perform a common mutual authentication process between terminal 7-33 and configuration file management server 7-45. Operation 7-50 may include a TLS connection based on server authentication. Furthermore, for example, it may include sending and receiving at least one or more operations such as initiating an authentication request message, initiating an authentication response message, and authenticating a client request message. Additionally, operation 7-50 may be an operation partially or entirely integrated with operation 7-60.

[0197] In the corresponding process, the ES9+.AuthenticateClient(transactionId,authenticateServerResponse) message, which includes predefined information collected from LPA 7-40, eUICC 7-35, and the terminal itself, can be sent as an authentication client request message to SM-DP+7-45. The corresponding authenticateServerResponse may include euiccInfo2 and deviceinfo. EuiccInfo2 represents information associated with eUICC 7-35 as defined in SGP.22. Deviceinfo represents information associated with terminal 7-33 as defined in SGP.22. The corresponding SM-DP+7-45 may use all or part of the euiccinfo2 and deviceinfo received as an authentication client request as specific information for determining whether to execute the RPM associated with the configuration file pre-installed in the MEP terminal. The terminal may send message 7-55 to SM-DP+7-45, which includes either a portion as an attribute of ES9+.AuthenticateClient(transactionId,authenticateServerResponse) or deviceinfo as a separate message.

[0198] The euiccinfo2 sent from the terminal specifies that the eUICC is an eUICC capability that the MEP supports. In the case of deviceinfo in operation 7-55, the eSIM port capability of deviceinfo may include one or more of the following: port number, International Mobile Equipment Identity (IMEI) number mapped to the corresponding port, and radio access technology information of the baseband used by the corresponding port, as port identity information and port-specific information. Alternatively, terminal 7-33 may generate deviceinfo mapped to each baseband in the terminal based on the number of basebands, which may include one or more deviceinfos, and may send them in operation 7-55. For example, in the case of a terminal supporting dual SIMs, the terminal may generate two deviceinfos and send them. For example, the port capability information of the deviceinfo sent by the terminal may be expanded and specified as described below. Although, as an example, the range of the port index is specified as 1.MaxNumOfPort as shown in Table 3 below, the port index may be a specific number specified by the terminal.

[0199] Table 3

[0200]

[0201]

[0202] The supported Radio Access Technology (RAT) information for the port capabilities may be equivalent to or a subset of the Radio Access Technology (RAT) for the device capabilities. If two deviceinfo entries are generated and sent, then it is specified that two deviceinfo entries will be sent as shown in Table 4 below.

[0203] Table 4

[0204]

[0205]

[0206] Considering the compatibility of SM-DP+7-45, which can perform RPM but does not support MEP, dual-SIM terminals can select the primary eSIM port information to use based on the terminal's or user's choice. This information can be sent as `deviceinfo`, and other eSIM port information can be sent separately as additional `deviceinfo` messages. Furthermore, only in the case of RPM operation, the terminal can include the eSIM port information in the Operation 7-55 message and send it to SM-DP+7-45. In this example, the terminal collects the eSIM port information, includes it in the `deviceinfo`, and sends it to SM-DP+7-45 only when it expects to send `CtxParamForCommonAuthentication` included in the authentication client request used for transmission by setting `operationType=rpm`.

[0207] If the SM-DP+7-45 receiving the corresponding port information is an SM-DP+7-45 that supports both MEP and RPM, then the SM-DP+7-45 can identify the number of ports, determine whether each port is occupied by another profile based on the port capabilities provided by the terminal, identify the port on which an enable command will be requested, and send an RPM command to the terminal. If all profiles on all ports are occupied, then the SM-DP+7-45 can send a message to terminal 7-35 indicating that all ports are occupied and enable is unavailable, and can additionally send port information associated with ports that need to be cleared for enable to terminal 7-35, allowing the user to perform a disable process on the profiles connected to the corresponding ports at the local level in operation 7-65.

[0208] In operation 7-65, if the user receives the corresponding message and executes the local configuration file to disable it, then terminal 7-40 can send the corresponding result to server 7-45 to request a retry in receiving RPM messages or to restart the initial RPM request, and can proceed with subsequent processes. As mentioned above, terminal 7-33 can match baseband and port, configure deviceinfo based on each baseband information, and send one or more deviceinfo messages to SM-DP+. If SM-DP+ 7-45, upon receiving the corresponding (multiple) deviceinfo messages, does not support MEP but supports RPM, then SM-DP+ 7-45 can select one of the (multiple) deviceinfo messages and can request terminal LPA 7-40 to implement RPM-Enable based on the corresponding deviceinfo message.

[0209] The LPA 7-40, receiving the PRM request, can send a remote profile management command to the eUICC 7-35 in operation 7-70. In operation 7-70, the LPA 7-40 can use, for example, a remote management input request (RPM packet load request) message including at least one remote management command and the digital signature of the profile server 7-45, and the LPA can explicitly specify and send information associated with the eSIM port to be connected when the corresponding profile is enabled, to support MEP. The remote management input request message passed from the LPA to the eUICC can include all or part of the authenticated client response message from operation 7-60.

[0210] The remote management input request message (load RPM package request) sent from LPA 7-40 to eUICC 7-35 can be a message such as ES10b.LoadRpmPackage(smdpSigned3,smdpSignature3,[eSIM port number]) or ES10b.LoadRpmPackage(smdpSigned3,smdpSignature3)+[eSIM port number].

[0211] Remote management commands (e.g., configuration file enable / disable / delete commands, etc.) can be included in the RpmPackage signed by SM-DP+ with smdpsigned3. eSIM port information selected by SM-DP+7-45 can be included in SM-DP signed with smdpSigned3 and can be sent as a response (e.g., as part of a command included as a parameter in the RpmPackage of smdpSigned3 or as an additional parameter outside the RpmPackage of smdpSigned3), or it can be added outside of smdpSigned3 and sent as a response.

[0212] If the eSIM port information is located outside of smdpSigned3, the LPA can correct the information independently or according to the user's selection. SM-DP+7-45 can add the port number of the port to be used outside of smdpSigned3 and send it as a response, implicitly indicating that the corresponding port number can be changed by the user or the terminal. When SM-DP+7-45 adds the port number of the port to be used outside of smdpSigned3 and sends it as an authentication client response message in operation 7-60 to LPA 7-40, LPA 7-40 can include the port number in HandleNotification (Load RPM Packet Result (OK+[Port#])) after RPM processing and can send it as a response in operation 7-80, thereby notifying SM-DP+7-45 of the finally specified port number.

[0213] In Operation 7-60, SM-DP+7-45 can send an authentication response message without eSIM port information to LPA 7-40 as a response. For example, if the deviceinfo sent by the terminal to SM-DP+7-45 in Operation 7-55 does not include identification information associated with MEP support, or if SM-DP+7-45 receives information associated with MEP support but does not support MEP, then the authentication client response message sent by SM-DP+7-45 to LPA 7-40 in Operation 7-60 can be sent to eUICC without eSIM port information.

[0214] In this example, LPA 7-40 adds eSIM port information associated with the eSIM port on which the configuration file will be enabled and sends a message to eUICC 7-35, or if LPA 7-40 does not add eSIM port information, then eUICC 7-35 determines the eSIM port.

[0215] When eSIM port information is added to the LPA, the eSIM port number is added as an additional optional parameter besides smdpSigned3 and smdpSignature3, and can be sent as a LoadRpmPackageRequest message from LPA7-40 to eUICC 7-35. Alternatively, the eSIM port number can be added as an optional parameter outside of the LoadRpmPackageRequest message and can be sent thereas.

[0216] This can be a message such as ES10b.LoadRpmPackage(smdpSigned3, smdpSignature3, [eSIM port number]) or ES10b.LoadRpmPackage(smdpSigned3, smdpSignature3) + [eSIM port number] as described above. If the eSIM port is explicitly specified outside of smdpsigned3, then signature verification is performed in operation 7-73 of eUICC for SM-DP+, excluding the eSIM port. Therefore, although the eSIM port information is changed by LPA, this may not be processed as an error in eUICC.

[0217] When adding eSIM port information to LPA 7-40, LPA can autonomously determine the eSIM port to be enabled on the corresponding profile and send it to eUICC 7-35. For example, LPA can identify the Radio Access Technology (RAT) information supported by each baseband and the empty eSIM ports not occupied by profiles based on the device capabilities obtained from deviceinfo2 of the terminal. It can select one of the empty eSIM ports, add the port number of the selected empty eSIM port to smdpSigned3 and smdpSignature3 of LoadRpmPackageRequest, and send it to eUICC 7-35. In particular, if the RATs supported by each baseband are equivalent, LPA can randomly select one of the empty eSIM ports on which a profile is not enabled.

[0218] Alternatively, LPA 7-40 can obtain user input associated with the eSIM port on which the corresponding profile will be enabled and send it to eUICC 7-35. For example, LPA 7-40 can provide a UI that requests the user to select the eSIM port to use (or the desired RAT), add the eSIM port number of the selected eSIM port to smdpSigned3 and smdpSignature3 of LoadRpmPackageRequest based on the user's selection, and send it to eUICC 7-35.

[0219] Terminal 7-33 can specify a default port based on the information associated with the port mapped to the baseband in the corresponding deviceinfo or according to the terminal settings. When sending the ES10b.LoadRpmPackage request for enabling processing to eUICC, LPA 7-40 can add the corresponding information and can send the ES10b.LoadRpmPackage request (RPM enabling configuration file) + eSIM port # or the ES10b.LoadRpmPackage request (RPM enabling configuration file + eSIM port #) (7-75) to eUICC 7-35 in operation 7-75.

[0220] eSIM port information can be changed by the LPA 7-40. For example, even though a message including port information is sent from SM-DP+7-45 to LPA 7-40, disabling the configuration file enabled on the corresponding port may be unavailable. In this example, if the LPA receives an error message from eUICC 7-35 indicating that enabling the corresponding port is unavailable, the LPA 7-40 can add another eSIM port as an optional parameter, either independently or based on user input, and can resend the message to set the port. For example, if all RATs supported by the terminal's baseband are equivalent, the LPA can independently change the eSIM port by adding another eSIM port as an optional parameter.

[0221] Although eSIM port information exists in smdpSigned3 included in ES10b.LoadRpmPackag, there may be a situation where LPA 7-40 fails to recognize it and can add an eSIM port number and send it to eUICC 7-35. In this instance, eUICC 7-35 can attempt to preferentially use the profile of the eSIM port added by LPA 7-40, and in response, can send the port information associated with the port on which the profile is finally enabled as an andleNotification (Load RPM Packet Result (OK+[port#])) in operation 7-80.

[0222] If an enable request without port information is sent from the LPA to the eUICC 7-35, the MEP supports the eUICC 7-35 specifying a default port when performing port startup between the platform-modem-eUICC, and establishing a connection to the corresponding port if an enable request is received from the LPA. As another example, if an empty eSIM port exists at the time the eUICC receives the enable request, the eUICC can perform enable on the corresponding port.

[0223] As mentioned above, if the LPA receives a configuration file enable command without port information, the LPA can add a specific port number and request enable processing from the eUICC. Alternatively, even if the LPA receives a configuration file enable command with port information, it can change the port number if enable is unavailable on the corresponding port and send it to the eUICC. Or, if the LPA receives a configuration file enable command without a port number, MPE supports eUICC 7-35, which allows specifying a specific port and performing a connection. All of these methods are applicable to the reference... Figure 5 The described local configuration file is enabled.

[0224] In operation 7-73, eUICC 7-35 can verify the digital signature of the configuration file server 7-45 received in operation 7-70. Digital signature verification can be calculated based on one or more remote management commands received in operation 7-60. If digital signature verification is successfully performed, then for one or more remote management commands received in operation 7-60, eUICC 7-35 can identify whether the configuration file server 7-45 that sent the remote management command is designated as the management configuration file server for the target configuration file of each remote management command. For example, a remote management command can take different configuration files installed in eUICC as the target configuration file, and the target configuration file for the corresponding remote management command can be identified based on the configuration file ID (or ICCID) in the corresponding remote management command.

[0225] eUICC 7-35 can execute one or more remote management commands received in operation 7-60 against a target configuration file for remote management commands, wherein the configuration file server 7-45 that sends the remote management commands is designated as the management configuration file server for the target configuration file. If eUICC 7-35 receives one or more remote management commands, it can repeatedly execute each remote management command. After executing each remote management command, eUICC 7-35 can generate remote management input results (RPM package loading results).

[0226] If the eSIM port information is included in smdpsigned3, then the LPA should not be able to change the corresponding value included in smdpsigned3 in the meantime. However, if the LPA changes this value, the signature verification on the SM-DP+ may fail in operation 7-73, and the eUICC may send an error as a response. In other words, if the SM-DP+ specifies eSIM port #1 in smdpSigned3 and sends it to the LPA as a response, and the LPA changes eSIM port #1 to eSIM port #2 in the meantime, then the eUICC that eventually receives eSIM port #2 may send an error as a response. That is to say, the eSIM port included in smdpSigned3 can be specified by the SM-DP+, and the LPA should not be allowed to add or change the eSIM port.

[0227] When the LPA adds an eSIM port number and sends the message to the eUICC, the LPA needs to perform processing to add the new eSIM port parameter while the integrity protection of smdpSignature3 remains unchanged. If the LPA specifies the eSIM port outside of smdpsigned3 without modifying the signature value and rpmpackge received from SM-DP and sends it to the eUICC, then the eSIM port can be excluded when the eUICC performs signature verification on SM-DP+.

[0228] If each remote management operation is successfully executed, the remote management input result associated with one or more remote management commands received by the eUICC 7-35 may include "OK", in the form of a string containing at least one character or a numeric string containing at least one digit, or may additionally include and send the port number. If each remote management operation fails, the result may include an error code indicating the reason for the failure, and the error code may be provided in the form of a string containing at least one character or a numeric string containing at least one digit. This figure illustrates that the remote management command received in operation 7-60 is "Configuration File Enabled", and the eUICC 7-35 successfully enables the target file and produces the result "OK" in operation 7-73. In operation 7-75, the eUICC 7-35 sends the remote management input result as a response to LPA 7-40. The eUICC 7-35 may use a remote management input response (Load RPM Packet Response) message in operation 7-75, which includes, for example, at least one remote management input result.

[0229] In operation 7-80, LPA 7-40 can send remote management input results (results of loading RPM packets) to profile server 7-45. For example, LPA 7-40 can use a notification processing message (processing notification) in operation 7-80. The notification processing message can include all or part of the remote management input response message from operation 7-75. The remote management input response message can include information associated with the eSIM port on which profiles are enabled and can be sent as a response in operation 7-75.

[0230] Figure 8A and Figure 8B A flowchart is shown of the process for determining the received REFRESH command in a modem that has received the REFRESH command.

[0231] When the UICC Card Application Kit (CAT) needs to receive a Reset Response (ATR) or perform UICC initialization, the UICC Reset REFRESH command can be used. At the time of this disclosure, if the modem receives the corresponding request, it can terminate all application sessions with the UICC card, delete the UICC's cached values, and request the UICC to perform a reset, causing the UICC to perform the reset and send an ATR in response. Through these operations, the modem and eUICC can begin a new card session, and the modem completes the REFRESH implementation without sending a Terminal Response to the eUICC. A detailed description of UICC reset will be understood with reference to TS102.223.

[0232] If the modem receives a REFRESH command indicating an eUICC profile state change, it can perform an application session termination procedure and delete all cached values ​​associated with the corresponding profile stored in the modem. The card can maintain logical channel 0 for transmission to the ISD-R, shut down all other channels, and restore the default state defined in ETSI TS 102 221 after UICC activation and ATR. If the corresponding processing is complete, the modem can send a TERMINAL RESPONSE to the eUICC.

[0233] At the time of this disclosure, if eUICC processing is enabled or disabled, then eUICC can choose to either change the eUICC profile state or reset the UICC and send it to the modem. Since a single profile exists in the eUICC so far, no problem arises even if either of these commands is received and a reset is performed in software (terminal operation upon receiving an eUICC profile state change or initialization in software upon receiving a UICC reset), or a hard reset is performed by turning off all power to the device and restoring the initialization state using the reset pin, etc.

[0234] However, when multiple profiles are enabled, for example, in eUICC where both profile 1 and profile 2 are enabled simultaneously, if the operations mentioned above are performed to change the state of profile 1, the network connection for profile 2 may be lost, which is a drawback. Therefore, as... Figure 4A and Figure 4B The method described herein illustrates how the eUICC sends a REFRESH message based on its status. If the modem receives a REFRESH command from the eUICC in operation 8-05, and the modem is not currently operating in MEP mode, then upon receiving a change in the eUICC profile status or a UICC reset, the modem can execute the corresponding command in the normal manner in operation 8-15.

[0235] Operations 8-10, where the modem is currently operating in MEP mode, can be considered as a case where the terminal has already performed the initialization process for eUICC MEP and eUICC. In this example, if multiple profile eSIM ports are generated, each eSIM port can be mapped to a specific baseband in the modem, or this mapping can be omitted. Next, the profile enabled on a specific eSIM port can send an APDU, including active commands, to the modem via the corresponding eSIM port. The modem can identify the eSIM port through which it sends the received APDU and apply the APDU to the memory area or baseband mapped to the corresponding eSIM port to perform operations corresponding to the content of the received APDU.

[0236] As described above, if the ISD-R in the eUICC is subject to multiple selections from multiple eUICC ports (if the LPA selects the ISD-R via multiple generated eSIM ports, and each eSIM port has multiple logical channels for performing APDU transmission and reception with the ISD-R), then the ISD-R can transmit active commands to the modem via each eSIM port. Depending on whether the eUICC and the modem currently meet Operations 8-10 and 8-20, and based on the active commands received by the modem, the operation of the modem can be changed, and may include at least one of the following five conditions.

[0237] like Figure 4A and Figure 4B As described above, when sending an active command that includes (multiple) port numbers or "all", the active command can be defined as a new mode of REFRESH active command or a new type of command.

[0238] For example, an active command can be defined as a platform reset mode (including "all") or port reset mode (including (multiple) port numbers) according to a "Reset" active command, or it can be defined as a form in which a field or value indicating (multiple) port numbers is included in an existing "REFRESH" active command. Although the accompanying drawings are provided as an example of the REFRESH active command, the scope of this disclosure is not limited thereto.

[0239] Case 1 can begin when the terminal receives a response message from eUICC including the port number.

[0240] 1. In operation 8-20, the MEP modem supports multiple selected ISD-R processing and in operation 8-30, the information associated with the port or "all" is not included in the received message.

[0241] A. Implement active commands received via the eSIM port. If the instruction relates to a refresh associated with a profile state change, it can be the REFRESH active command associated with an eUICC profile state change or UICC reset in Operation 8-35 (Soft Reset).

[0242] 2. In operation 8-20, the MEP modem supports multiple selected ISD-R processing and in operation 8-30, the information associated with (multiple) ports or "all" is included in the REFRESH command.

[0243] A. Based on the determination in operations 8-40, 8-50, and 8-60, execute one of operations 8-45, 8-55, and 8-65.

[0244] 3. Among them, the MEP modem does not support multiple selected ISD-R processing 8-20 and receives REFRESH commands including UICC reset + all port identifiers via a specific eSIM port in operation 8-40.

[0245] A. Perform a hard reset (power-based or reset pin-based reset) in operation 8-45.

[0246] 4. Among them, the MEP modem does not support multiple selected ISD-R processing 8-20 and the case in operation 8-50 where a REFRESH command including eUICC profile status change + all port identifiers is received via a specific eSIM port.

[0247] A. Perform a REFRESH (soft reset on all ports) on all ports in Operation 8-55.

[0248] 5. Among them, operations 8-60 include REFRESH commands via a specific eSIM port, which include changes to the eUICC profile status or UICC resets and port ID information.

[0249] A. Perform a REFRESH (soft reset) on the port corresponding to the included port ID in operation 8-65. Multiple port IDs may exist. If multiple port IDs are included, then a REFRESH can be performed on the port corresponding to the included port ID.

[0250] If it is determined that multiple selected ISD-Rs are not supported in operation 8-20, and no information associated with the port number or "all" is received, then the terminal may perform operation 8-15 or operation 8-35 according to the implementation method.

[0251] If multiple port numbers are received, the modem can perform a network disconnect procedure for each port in the order they are received, clearing the cached values ​​in each port and starting a new card session by resetting the corresponding port. Furthermore, if the received ports are occupying the network, the modem can perform a network disconnect procedure for all ports simultaneously, clearing the cached values ​​in each port and starting a new card session by resetting each port. Operations 8-70 also apply when the terminal (via the LPA's terminal frame) sends a request including multiple port numbers to the modem, directly requesting the modem to perform a reset.

[0252] If ISD-R is selected via a single port, then a refresh of the port corresponding to the included port ID can be performed, for example, as follows.

[0253] - The modem can identify the corresponding port ID information, perform UICC reset on the corresponding port, and send reset commands to the corresponding port.

[0254] - The modem can identify the corresponding port ID information and request polling from the corresponding port, thereby performing UICC reset or eUICC profile state change on the corresponding port in a conventional manner.

[0255] Although not shown in the diagram, the ISD-R can be selected by a single port, such as... Figure 3A and Figure 3B As described above. In this example, the port using ISD-R can be considered as a port used to manage other ports. The modem can handle active commands received via the port for management purposes differently from active commands received via the port for other purposes. (See also...) Figure 12 Describe it in detail.

[0256] Figure 9A and Figure 9B This is an illustration showing an example of multiple selectable ISD-Rs in the process of connecting modems and v3 eUICC based on the concept of a virtual interface.

[0257] Figure 9A and 9B eUICC 9-20 is assumed to be an eUICC that supports MEP functionality, enabling multiple profiles simultaneously. Modem 9-01 is also assumed to be a modem that supports MEP functionality. Figure 9 provides a description with an example of two basebands and two enabled profiles. Although there may be mapping switching between the baseband and eSIM port in modem 9-01, cases 1 and 2 illustrate the logical terminal endpoint mapping in modem 9-01 using baseband 1 9-05-channel 1 9-40 and baseband 2 9-10-channel 2 9-45 as examples.

[0258] like Figure 2A and Figure 2B As described above, the current modem 1-15 is connected to the eUICC 1-20 via a single physical pin, and the corresponding modem and eUICC can transmit APDU commands via a single channel 2-10 using the corresponding physical pin. The MEP-enabled eUICC 9-20 can enable multiple profiles, and the corresponding enabled profile may require APDU transmission using a specific baseband of the modem. Therefore, to address this, a concept can be adopted that multiplexes the physical interface 9-15 and transmits APDUs individually via multiple channels 9-40 and 9-45.

[0259] In the following text, for ease of description, if MEP is supported, the channels will be referred to as eSIM ports. The channels are designated eSIM port 1 (9-40) and eSIM port 2 (9-45), and these channels are used as eSIM ports. After a UICC reset or configuration file state change, the terminal can generate APDU channels for transmission between the modem baseband and the eUICC during the initialization process between the modem and the eUICC. In this example, the terminal can set an ID for the eSIM port connected to each baseband. The corresponding port ID can be set in the modem or terminal platform, and this port ID can be transmitted to the LPA. In this disclosure, for ease of description, port IDs and port numbers can be used interchangeably.

[0260] A modem may include as many eSIM ports as the baseband. However, the number of eSIM ports utilized by eUICC9-20 may be less than or equal to the number of profiles that can be enabled simultaneously in the corresponding eUICC. Profiles may use one of the eSIM ports to transmit APDU messages.

[0261] according to Figure 9A In case 1 9-100, the APDU command corresponding to the enable configuration file 1 9-25 can be sent to the baseband 1 9-05 via the eSIM port 1 9-40, and at the same time, the APDU command corresponding to the enable configuration file 2 9-30 can be sent to the baseband 2 9-10 via the eSIM port 2 9-45.

[0262] according to Figure 9B In case 2 9-200, the APDU command corresponding to enable configuration file 1 9-25 can be sent to baseband 2 9-10 via eSIM port 2 9-55, and at the same time, the APDU command corresponding to enable configuration file 2 9-30 can be sent to baseband 1 9-05 via eSIM port 2 9-60.

[0263] The MEP-supported modem 9-01 can process APDU commands sent via each eSIM port differently by recognizing the baseband to which the corresponding APDU command will be connected. The ISD-R 9-35 may need to send command APDUs to the modem to manage the state of eUICC and profiles.

[0264] The LPA or modem can determine, based on the eSIM initialization process or prior settings, whether to allow selection of the ISD-R 9-35 via multiple eSIM ports. This is known as multiple selection state. In multiple selection state, messages can be sent to or received from the ISD-R 9-35 via an eSIM port selected and determined by the LPA or modem among the eSIM ports. Depending on whether the received message corresponds to a management message in Profile 1 9-25 or Profile 2 9-30, or is a message associated with the entire eUICC, the ISD-R 9-35 can select the appropriate eSIM port and can send a response APDU, including active commands, via the corresponding port.

[0265] Figure 10 This is an illustration showing the block configuration of a terminal according to an embodiment.

[0266] refer to Figure 10 The terminal includes a controller 10-10, a transceiver 10-05, a display 10-15, and an eUICC 10-20. As described above, the eUICC 10-20 can be configured within the terminal, or it can be configured as a separate entity or configured by being inserted into the terminal.

[0267] Transceiver 10-05 may correspond to the modem in this disclosure and may perform signal transmission and reception with SM-DP+.

[0268] The controller of terminal 10-10 can control the operation and state of all terminal elements in this disclosure, thereby enabling operation according to embodiments of this disclosure. For example, the controller can control at least one of the LPA, modem, and eUICC, thereby enabling operation according to embodiments of this disclosure.

[0269] Displays 10-15 may display to the user all or part of port information, configuration file status information, configuration file list, available RAT information, etc., according to embodiments of the present disclosure.

[0270] The eUICC 10-20 is controlled by the LPA or controller 10-10, and the eUICC in the embodiments of this disclosure can execute each management command and can send active commands to the modem, etc.

[0271] Figure 11 This is an illustration of a refresh method that does not use active commands according to an embodiment of the present disclosure.

[0272] Figure 11 This is a flowchart illustrating, schematically, the process by which user 11-01 manages configuration files using LPA 11-05 in the MEP support terminal. It will be assumed that... Figure 11 The description is provided assuming that the LPA 11-05, Modem 11-10, and eUICC 11-15 all support MEP.

[0273] In operation 11-20, end user 11-01 can execute management commands associated with the profile installed in the terminal based on information displayed in LPA 11-05 or in an application that integrates LPA 11-05. An example of the screen displayed on the user's screen when executing the corresponding management command has been described with reference to Figure 6. As described in the figure, when sending an ES10c command without the refreshFlag parameter, the terminal may optionally identify in operation 11-25 whether the corresponding terminal meets the state that supports it before sending the ES10c command. For example, as defined in GSMA SGP.22, if a previously enabled profile exists, the met state could be the termination of an application associated with the port occupied between the UICC and the modem, or the closure of a logical channel, etc.

[0274] If user input or an RPM command is received, the LPA can send an ES10c command to the eUICC in operation 11-40. In operation 11-45, the eUICC receiving the corresponding message can verify the status used to process the corresponding command (such as the status information of the corresponding configuration file or configuration file policy rules). The eUICC needs to identify the status when receiving the corresponding command, as defined in GSMA SGP.22, and can send an error message as a response if a problem occurs. Although for ease of description, the command in the ES10c command that causes a change in the configuration file status is called a configuration file status change related command, the ES10c command can be one of ES10c.enableProfile, ES10c.disableProfile, ES10c.deleteProfile, and ES10c.euiccMemoryReset.

[0275] To send proactive commands, Card Application Kit (CAT) support is required on the corresponding port, and CAT is not supported on the port used by ISD-R. In this example, the LPA can send configuration file state change related commands without the refreshFlag parameter. Furthermore, although CAT is supported, the eUICC does not request the modem to process refresh; instead, the LPA is requested to perform the processing, and the modem performs the processing according to the implementation method adopted by the terminal. This corresponds to situations where... Figure 5The example shown illustrates the case where refreshFlag is absent when the configuration file is enabled. The eUICC receiving a configuration file state change-related command without a refreshFlag parameter can, in operations 11-50, perform the processing operation associated with the state change in the corresponding configuration file (e.g., enabling, disabling, or deleting the configuration file), and the eUICC or LPA can send information associated with the port identified as needing refresh to the modem, thereby enabling the modem to perform a refresh. This method may include one of the following.

[0276] Alt1: This refers to the method of adding (multiple) port numbers that need to be refreshed in LPA and sending them to the modem.

[0277] eUICC can send the result of processing the corresponding ES10c command as a response to the LPA. The LPA can determine and store the port(s) that need to be refreshed at a specific time point after receiving the user input, and can add the port(s) that need to be refreshed in operation 11-60 and send the corresponding refresh command to the modem. If the modem receives the corresponding refresh command, it can perform refresh processing on the corresponding port(s) or at the platform level in operation 11-65. The modem can perform UICC reset or eUICC profile state change on the port(s) targeted by the refresh request, such as... Figure 8A and Figure 8B As described above, and if an identifier indicating all ports is included, then a reset of the entire platform can be performed in a manner similar to the current UICC reset.

[0278] The method by which the LPA determines the port(s) number(s) that need to be refreshed can be one of the following methods.

[0279] ● Enabling / disabling / deleting configuration files on specific ports: including the port number in the ES10c command in operation 11-40.

[0280] ● Additional determination when enabling a profile on a specific port: The profile to be enabled may be a profile that was previously enabled on another port. In this example, in addition to the port number included in the ES10c command in Operation 11-40, a refresh needs to be performed on all ports on which the corresponding profile is already enabled. The port number on which the corresponding profile is already enabled can be determined by the LPA based on one or a combination of the following options: an error message received from eUICC between Operations 11-45 and Operations 11-50 indicating that the profile is on another port and the additional port number included, or information associated with the port on which the corresponding profile is previously enabled and obtained in advance via GetProfileInfo()11-30 to implement the ES10c command11-35.

[0281] ● In the case of eUICC memory reset: In the case of sending eUICC memory reset in operation 11-40, depending on the LPA settings, the LPA may determine to use an identifier indicating all ports (e.g., "all") instead of using the information 11-35 associated with the ports enabled for each profile and sent in response via GetProfileInfo().

[0282] Alt2: eUICC adds the (multiple) port numbers that need to be refreshed and sends them to the LPA, and the LPA sends the corresponding information to the modem.

[0283] eUICC can process commands associated with the target profile and can send a result including the port number that needs to be refreshed as a response in operations 11-70. This can be the processing result of an ES10c-based command and can be the number of all ports that have changed in the profile-port mapping. For example, at least one of the following cases can be included and sent as a response: either a profile enabled on the port has been changed or a profile enabled on the port has been disabled. Alternatively, a new identifier indicating that all ports need to be reset at the platform level can be included and sent as a response. eUICC can include at least one of the information described above and can send it as a response to the LPA. If the LPA that receives the information transmits the information associated with the port that needs to be refreshed to the modem, then the modem can perform a refresh on the corresponding port as described in Alt 1 in operations 11-80 or can perform a refresh at the platform level.

[0284] Alt3: The eUICC adds the port numbers (multiple) that need to be refreshed and sends them to the LPA, and the modem parses the corresponding messages in the middle to perform a refresh on the ports (multiple) corresponding to the port numbers (multiple) that need to be refreshed.

[0285] eUICC can process commands associated with the target profile and can send a response including the port numbers that need to be refreshed in operations 11-85. This can be the processing result of an ES10c-based command and can be the numbers of all ports that have changed in the profile-port mapping. For example, at least one of the following cases can be included and sent as a response: a profile enabled on a port has been changed or a profile enabled on a port has been disabled. Alternatively, a new identifier indicating that all ports need to be reset at the platform level can be included and sent as a response.

[0286] The MEP modem can parse all APDU messages between the LPA and ISD-R and identify their content. Alternatively, the eUICC can add an indicator to the corresponding response message, instructing the corresponding MEP modem to parse the message and identify its content, and send it in operation 11-85. If the eUICC sends the corresponding message to the LPA in operation 11-85, the modem interprets the corresponding message included in the APDU transmitted between the eUICC and the card, causing the modem to perform a refresh on the corresponding port in operation 11-90 as described in Alt1, or a refresh at the platform level. In this example, the modem can optionally add the result associated with the completion of the corresponding processing to the message sent from the eUICC and send it to the LPA in operation 11-95.

[0287] Figure 12 This is an illustration of a method by which a modem processes active commands received via a port for management purposes and active commands received via a port for other purposes, according to embodiments of the present disclosure.

[0288] Figure 12The description is provided under the assumption that eSIM port 0 (12-20) is a port accessible only by the ISD-R and is used for management purposes, and that eSIM port 1 (12-30) is considered to not affect other ports and is not used for management. When the ISD-R in eUICC 12-01 sends an active command including (multiple) port numbers or all (all) ports to the modem via eSIM port 0 (12-20) in operation 12-40, if the modem recognizes that the received active command is an active command including (multiple) port numbers or all (all) ports, then the modem can... Figure 8A and Figure 8B The implementation corresponds to the active command. If the port number received in operation 12-40 is #1, then modem 12-10 can send a polling message associated with the existence of a message to be retrieved in operation 12-70, or modem 12-10 can fully execute the reset procedure associated with port 1 and send a reset command associated with the corresponding port. Although eUICC 12-10 receives a reset command in operation 12-70, if the corresponding port number is different from the port number included in the active command sent in operation 12-40, then eUICC 12-10 can additionally send an associated error as a response to modem 12-10, thereby reporting that the modem needs to resend a reset command with the port number included in the active command sent in operation 12-40.

[0289] In the case where the ISD-R in eUICC 12-01 sends an active command to the modem via eSIM port 1 12-30 that includes (multiple) port numbers or all (all) ports, if the modem recognizes that the received active command is an active command that includes (multiple) port numbers or all (all) ports, then the modem may refuse to process the corresponding command and may return the associated error in operation 12-70.

[0290] In the detailed embodiments described above in this disclosure, the elements included in this disclosure are expressed in a singular or plural form according to the described detailed embodiments. However, the singular or plural forms are chosen appropriately for the purposes of description, and this disclosure is not limited to elements expressed in a singular or plural form. Thus, an element expressed in a plural form may also include a single element, or an element expressed in a singular form may include multiple elements.

[0291] Although specific embodiments have been described in the Detailed Description section of this disclosure, various modifications and variations can be made thereto without departing from the scope of this disclosure. Therefore, the scope of this disclosure should not be defined as limited to the described embodiments, but should be defined by the appended claims and their equivalents.

[0292] Although this disclosure has been described with reference to various embodiments, various changes and modifications will be apparent to those skilled in the art. It is intended that this disclosure include such changes and modifications that fall within the scope of the appended claims.

Claims

1. A method performed by a device in a wireless communication system, the method comprising: The local profile assistant (LPA) in the device identifies information associated with the target profile to be enabled; The LPA sends a message to the embedded universal integrated circuit card eUICC in the device to enable the target profile. The message includes a refresh flag indicating whether a refresh active command associated with a target port corresponding to the target profile is required and the port number of the target port. as well as When the refresh flag indicates a request for the active refresh command, the active refresh command is obtained from the eUICC by the baseband-related components in the device.

2. The method according to claim 1, further comprising: Based on obtaining the refresh active command. The baseband-related components send a terminal response message to the eUICC; or The target port is reset by the baseband-related components. The target configuration file is enabled on the target port.

3. The method according to claim 1, wherein, The message used to enable the target configuration file is sent on a predetermined port different from the target port.

4. The method according to claim 1, wherein, The information associated with the target configuration file to be enabled is obtained based on user input.

5. The method according to claim 1, wherein, The device supports multiple enabled configuration files.

6. A method performed by an embedded general-purpose integrated circuit card (eUICC) in a device of a wireless communication system, the method comprising: A message for enabling a target profile is obtained from the Local Profile Assistant (LPA) in the device. The message includes a refresh flag indicating whether a refresh active command associated with a target port corresponding to the target profile is required, and the port number of the target port. as well as When the refresh flag indicates a request for the refresh active command, the refresh active command is sent to the baseband-related components in the device.

7. The method according to claim 6, further comprising: Based on sending the aforementioned refresh active command: The target configuration file is enabled on the target port when a terminal response message is received from the baseband-related component or after the target port is reset.

8. The method according to claim 6, wherein, The message used to enable the target configuration file is obtained on a predetermined port different from the target port.

9. The method according to claim 7, wherein, Enabling the target profile on the target port further includes: disabling the other profile and enabling the target profile on the target port if another profile is currently enabled on the target port.

10. The method according to claim 6, wherein, The eUICC supports multiple enabled configuration files.

11. A device in a wireless communication system, the device comprising a Local Profile Assistant (LPA) and baseband-related components: in, The LPA is configured as follows: Identify the information associated with the target configuration file to be enabled, and A message is sent to the embedded universal integrated circuit card (eUICC) in the device to enable the target profile. The message includes a refresh flag indicating whether a refresh active command associated with a target port corresponding to the target profile is required, and the port number of the target port. The baseband-related components are configured as follows: If the refresh flag indicates a request for the refresh active command, the refresh active command is obtained from the eUICC.

12. The device according to claim 11, wherein, The baseband-related components are also configured to: Based on obtaining the refresh active command: Send a terminal response message to the eUICC, or Reset the target port, and The target configuration file is enabled on the target port.

13. The device according to claim 11, wherein, The message used to enable the target configuration file is sent on a predetermined port different from the target port.

14. The device according to claim 11, wherein, The information associated with the target configuration file to be enabled is obtained based on user input.

15. The device according to claim 11, wherein, The device supports multiple enabled configuration files.

16. An embedded universal integrated circuit card (eUICC) in a device of a wireless communication system, the eUICC comprising: interface; and The controller is configured as follows: A message for enabling a target profile is obtained from the Local Profile Assistant (LPA) in the device. The message includes a refresh flag indicating whether a refresh active command associated with a target port corresponding to the target profile is required, and the port number of the target port. as well as When the refresh flag indicates a request for the refresh active command, the refresh active command is sent to the baseband-related components in the device.

17. The eUICC according to claim 16, wherein, The controller is also configured to: Based on sending the aforementioned refresh active command: The target configuration file is enabled on the target port when a terminal response message is received from the baseband-related component or after the target port is reset.

18. The eUICC according to claim 16, wherein, The message used to enable the target configuration file is obtained on a predetermined port different from the target port.

19. The eUICC according to claim 17, wherein, The controller is also configured to disable the other configuration file and enable the target configuration file on the target port if the other configuration file is currently enabled on the target port.

20. The eUICC according to claim 16, wherein, The eUICC supports multiple enabled configuration files.

Images