CN117203997A

CN117203997A - Electronic device and method for installing configuration file of embedded subscriber identification module in electronic device

Info

Publication number: CN117203997A
Application number: CN202280029946.3A
Authority: CN
Inventors: 郑知恩; 潘亨鎭; 徐载弦; 朴知民; 尹叡振
Original assignee: Samsung Electronics Co Ltd
Current assignee: Samsung Electronics Co Ltd
Priority date: 2021-04-23
Filing date: 2022-04-21
Publication date: 2023-12-08

Abstract

An electronic device includes: at least one embedded universal integrated circuit card (eUICC) that each stores at least one piece of subscriber identity information; and at least one processor electrically connected to the eUICC. The at least one processor: controlling to transmit a first request message to a first server, the first request message including information regarding operations associated with eUICC-based subscriptions or line migration; and receiving a first response message from the first server according to the transmission of the first request message, wherein the first response message may include information indicating that the configuration file to be provided for the eUICC is not ready according to the first request information.

Description

Electronic device and method for installing configuration file of embedded subscriber identification module in electronic device

Technical Field

The present disclosure relates to an electronic device and a method for installing a profile of an embedded subscriber identity module (eSIM) in an electronic device.

Background

In a wireless communication system, an electronic device (e.g., a User Equipment (UE)) may access a wireless communication network and use voice communication or data communication services in a fixed location or in a mobile. In order to provide communication services to electronic devices, an appropriate authentication procedure is required. In general, a Universal Integrated Circuit Card (UICC) is inserted into an electronic device, and authentication is performed between the electronic device and a server of a Mobile Network Operator (MNO) through a Universal Subscriber Identity Module (USIM) installed in the UICC. In the case of global system for mobile communications (GSM), the UICC may be referred to as a Subscriber Identity Module (SIM), and in the case of Wideband Code Division Multiple Access (WCDMA), long Term Evolution (LTE), and New Radio (NR), the UICC is referred to as a USIM.

If the user of the electronic device subscribes to the wireless communication service provided by the mobile network operator, the mobile network operator may provide the user with a UICC (e.g., SIM card or USIM card). The user may insert the provided UICC into her electronic device. If the UICC is inserted into the electronic device, a USIM application installed in the UICC is executed, and an appropriate authentication procedure can be performed with a server of a mobile network operator storing the same value using an International Mobile Subscriber Identity (IMSI) value and an encryption key value for authentication stored in the UICC. After performing the appropriate authentication procedure, the wireless communication service may be used.

The UICC may be manufactured as a dedicated card for a specific communication carrier at the request of the specific communication carrier at the time of manufacturing the card, and may be equipped with authentication information (e.g., USIM application and subscriber identity ID (e.g., IMSI)) and encryption key (e.g., known K value or Ki value) for network connection of the corresponding communication carrier. The UICC may be provided to subscribers of the communication services through a corresponding communications operator, and later, if necessary, the communications operator may use techniques such as Over The Air (OTA) to install, modify and delete applications within the UICC. The user may insert the UICC into the terminal and use the network and application services of the corresponding communication operator. When replacing a terminal, the user may insert a removable UICC from the old terminal to the new terminal, thereby using the authentication information, phone number and personal contact information stored in the UICC on the new terminal.

Unlike UICCs that are specifically manufactured and distributed for a particular communication carrier, a user may purchase a particular UICC, or a user may subscribe to (or purchase) communication services after obtaining a UICC, and a user may subscribe to and cancel, provision services from a particular wireless communication carrier, or transfer to another communication carrier (e.g., subscription transfer). Accordingly, a method for remotely installing USIM applications and subscriber identity IDs and encryption keys of communication operators on UICCs, and securely and flexibly installing and managing authentication information of various communication operators has been proposed.

For example, a so-called embedded UICC (eUICC) has been proposed that is capable of remotely installing a profile for providing a communication service through a network without replacing the UICC even when a user changes a communication carrier. During the manufacturing process of the terminal, the eUICC can be manufactured as a pre-installed UICC that is fixed in the terminal in chip form. Accordingly, the eUICC can be used for various terminals that may have a structure in which it is not easy to install or remove the UICC, such as machine-to-machine (M2M) or device-to-device (D2D) terminals, and general-purpose wireless terminals such as mobile phones. The eUICC can also be referred to as an eSIM.

Disclosure of Invention

Technical problem

An eSIM equipped electronic device can download a configuration file to use the eSIM in various ways. For example, the electronic device may download the configuration file through a configuration file providing server (e.g., subscription manager data ready plus (SM-dp+)) after online subscription to the communication service.

When downloading a profile online, a communication carrier server (e.g., a profile information transfer server (e.g., an authorization server)) of a communication carrier requests a profile providing server (e.g., SM-dp+) to prepare a profile upon completion of subscription to a communication service. Thus, delays may occur in downloading the configuration file. In this case, when the profile providing server completes preparation of the profile, the communication carrier may notify the electronic device that the profile is ready by a push message.

If the electronic device fails to normally receive a push message indicating that the configuration file is ready, the electronic device may wait for the push message all the time, although the configuration file can be downloaded, resulting in a normal download failure. Since the communication carrier may not know whether the electronic device normally receives the push message, it does not retransmit the push message, and the electronic device may eventually wait for the push message indefinitely.

According to various embodiments of the present disclosure, there may be an electronic device capable of downloading a profile by allowing a profile check request through various User Interfaces (UIs) (e.g., status bars) even when the electronic device fails to normally receive a push message indicating that the profile is ready, and a method for installing a profile of an embedded SIM in the electronic device.

According to various embodiments of the present disclosure, when an electronic device sends a request for subscription or subscription transfer to a communication carrier server, if the communication carrier server provides web server-related information to the electronic device (e.g., if a web service or web page is provided through the web server), the communication carrier server may transmit a callback message (e.g., a JS callback message) to the electronic device. The electronic device may identify a readiness state (e.g., a deferred state or a readiness state of the configuration file) based on the callback message.

As another example, when the electronic device sends a request for subscription or subscription transfer to the communication carrier server, if the communication carrier server does not provide web server related information to the electronic device (e.g., unless web services or web pages are provided through the web server), the electronic device may not receive a callback message including a profile ready state from the communication carrier server. For example, since the electronic device does not receive the callback message from the communication carrier server, the electronic device may not recognize whether the profile download readiness state is delayed.

According to various embodiments, an electronic device and a method for installing a profile of an embedded SIM in an electronic device may be provided, in which when the electronic device transmits a subscription or a subscription transfer request, a communication carrier server includes information indicating whether the profile is ready in a message in response to the request, and transmits a response message so that the electronic device may recognize whether a profile download readiness state is delayed.

Technical solution

According to various embodiments, an electronic device may include: at least one embedded universal integrated circuit card (eUICC), each card storing at least one piece of subscriber identity information; and at least one processor electrically connected to the eUICC. The at least one processor may be configured to: in response to the transmission of the first request message, controlling transmission of the first request message to the first server, the first request message including information regarding operations related to the eUICC-based subscription or subscription transfer; and receiving the first response message from the first server. The first response message can include information indicating that a configuration file to be provided for the eUICC in response to the first request message is not ready.

According to various embodiments, an electronic device may include: at least one embedded universal integrated circuit card (eUICC), each card storing at least one piece of subscriber identity information; and at least one processor electrically connected to the eUICC. The at least one processor may be configured to: receiving a request for identifying a configuration file; obtaining address information corresponding to a profile providing server from a communication carrier server based on address information corresponding to the profile providing server that does not recognize the profile; transmitting a message for identifying a readiness of the profile to the profile providing server based on address information corresponding to the profile providing server; and based on identifying that the profile is ready, controlling downloading the profile from the profile providing server and storing the profile in the eUICC.

According to various embodiments, a method for installing a configuration file of an embedded SIM in an electronic device including at least one embedded universal integrated circuit card (eUICC) storing at least one subscriber identity information and at least one processor electrically connected to the eUICC may include: receiving a request for identifying a configuration file; obtaining address information corresponding to a profile providing server from a communication carrier server based on address information corresponding to the profile providing server that does not recognize the profile; transmitting a message for identifying a readiness of the profile to the profile providing server based on address information corresponding to the profile providing server; and based on identifying that the profile is ready, downloading the profile from the profile providing server and storing the profile in the eUICC.

Advantageous effects

According to various embodiments of the present disclosure, by allowing a user to directly attempt to identify a configuration file through a status bar request, the configuration file may be effectively downloaded even when the electronic device fails to normally receive a push message indicating that the configuration file is ready.

According to various embodiments of the present disclosure, when an electronic device transmits a request for subscription or subscription transfer to a communication carrier server, even when the communication carrier server does not provide information related to a web server to the electronic device, the configuration file can be downloaded without delay by including information indicating whether the configuration file is ready in a response message and transmitting the response message.

Other aspects, advantages, and salient features of the disclosure will become apparent to those skilled in the art from the following detailed description, which, taken in conjunction with the annexed drawings, discloses various embodiments of the disclosure.

Drawings

FIG. 1a is a block diagram illustrating an electronic device in a network environment according to an embodiment of the present disclosure;

FIG. 1b is a diagram illustrating a network environment including an electronic device according to an embodiment of the present disclosure;

FIG. 2 is a diagram illustrating a system for providing profile-based communication connections to electronic devices according to an embodiment of the present disclosure;

Fig. 3 is a block diagram showing a configuration of an electronic device according to an embodiment of the present disclosure;

fig. 4 is a view showing an internal structure of an embedded universal integrated circuit card (eUICC) according to an embodiment of the present disclosure;

FIG. 5 is a block diagram illustrating a network system for downloading configuration files according to an embodiment of the present disclosure;

FIG. 6 is a flowchart illustrating a method for downloading a configuration file according to an embodiment of the present disclosure;

fig. 7a and 7b are views illustrating user interfaces displayed on a screen of an electronic device according to various embodiments of the present disclosure;

fig. 8a and 8b are views illustrating user interfaces displayed on a screen of an electronic device according to various embodiments of the present disclosure;

FIG. 9 is a flowchart illustrating a method for downloading a configuration file according to an embodiment of the present disclosure;

fig. 10 is a view illustrating a user interface displayed on a screen of an electronic device according to an embodiment of the present disclosure;

FIG. 11 is a view showing a user interface displayed on a screen of an electronic device according to an embodiment of the present disclosure;

FIGS. 12a and 12b are flowcharts illustrating methods for downloading a configuration file according to various embodiments of the present disclosure;

fig. 13 is a view showing a user interface displayed on a screen of an electronic device according to an embodiment of the present disclosure;

FIG. 14 is a flowchart illustrating a method for downloading a configuration file according to an embodiment of the present disclosure;

FIG. 15 is a flowchart illustrating a method for downloading a configuration file according to an embodiment of the present disclosure;

FIG. 16 is a flowchart illustrating a method for downloading a configuration file according to an embodiment of the present disclosure; and is also provided with

Fig. 17 is a flowchart illustrating a method for downloading a configuration file according to an embodiment of the present disclosure.

Detailed Description

The following description is provided with reference to the accompanying drawings to assist in a comprehensive understanding of the various embodiments of the disclosure defined by the claims and their equivalents. The following description includes various specific details that facilitate understanding, but are merely to be considered exemplary. Accordingly, one of ordinary skill in the art will recognize that various changes and modifications of the various embodiments described herein can be made without departing from the scope and spirit of the present disclosure. In addition, descriptions of well-known functions and constructions may be omitted for clarity and conciseness.

The terms and words used in the following description and claims are not limited to written meanings, but are used only by the inventors to enable a clear and consistent understanding of the disclosure. Accordingly, it should be understood by those skilled in the art that the following description of the various embodiments of the present disclosure is provided for illustration purposes only and not for the purpose of limiting the disclosure as defined by the appended claims and their equivalents.

It should be understood that the singular forms "a", "an", and "the" include plural referents unless the context clearly dictates otherwise. Thus, for example, reference to a "component surface" includes reference to one or more such surfaces.

Fig. 1a is a block diagram illustrating an electronic device 101 in a network environment 100 according to various embodiments. Referring to fig. 1a, an electronic device 101 in a network environment 100 may communicate with the electronic device 102 via a first network 198 (e.g., a short-range wireless communication network) or with the electronic device 104 or server 108 via a second network 199 (e.g., a long-range wireless communication network). According to an embodiment, the electronic device 101 may communicate with the electronic device 104 via the server 108. According to an embodiment, the electronic device 101 may include a processor 120, a memory 130, an input module 150, a sound output module 155, a display module 160, an audio module 170, a sensor module 176, an interface 177, a connection 178, a haptic module 179, a camera module 180, a power management module 188, a battery 189, a communication module 190, a Subscriber Identity Module (SIM) 196, or an antenna module 197. In some embodiments, at least one (e.g., connection end 178) component may be omitted from electronic device 101, or one or more other components may be added to electronic device 101. According to embodiments, some (e.g., sensor module 176, camera module 180, or antenna module 197) components may be integrated into a single component (e.g., display module 160).

The processor 120 may execute, for example, software (e.g., program 140) to control at least one other component (e.g., hardware or software component) of the electronic device 101 coupled with the processor 120, and may perform various data processing or calculations. According to an embodiment, as at least part of data processing or computation, the processor 120 may store commands or data received from another component (e.g., the sensor module 176 or the communication module 190) in the volatile memory 132, process the commands or data stored in the volatile memory 132, and store the resulting data in the non-volatile memory 134. According to an embodiment, the processor 120 may include a main processor 121 (e.g., a Central Processing Unit (CPU) or an Application Processor (AP)), or an auxiliary processor 123 (e.g., a Graphics Processing Unit (GPU), a Neural Processing Unit (NPU), an Image Signal Processor (ISP), a sensor hub processor, or a Communication Processor (CP)), which may operate independently or in conjunction with the main processor 121. For example, when the electronic device 101 includes the main processor 121 and the auxiliary processor 123, the auxiliary processor 123 may be configured to use lower electronics than the main processor 121 or be designated for designated functions. The auxiliary processor 123 may be implemented separately from the main processor 121 or as part of the main processor 121.

The auxiliary processor 123, instead of the main processor 121, may control at least some of the functions or states associated with at least one of the components of the electronic device 101 (e.g., the display module 160, the sensor module 176, or the communication module 190) when the main processor 121 is in an inactive (e.g., sleep) state, or the auxiliary processor 123 together with the main processor 121 may control at least some of the functions or states associated with at least one of the components of the electronic device 101 (e.g., the display module 160, the sensor module 176, or the communication module 190) when the main processor 121 is in an active state (e.g., executing an application). According to an embodiment, the auxiliary processor 123 (e.g., an image signal processor or a communication processor) may be implemented as part of another component (e.g., the camera module 180 or the communication module 190) that is functionally related to the auxiliary processor 123. According to an embodiment, the auxiliary processor 123 (e.g., a neural processing unit) may include hardware structures designated for artificial intelligence model processing. The artificial intelligence model may be generated by machine learning. Such learning may be performed, for example, by the electronic device 101 performing artificial intelligence or via a separate server (e.g., server 108). The learning algorithm may include, but is not limited to, for example, supervised learning, unsupervised learning, semi-supervised learning, or reinforcement learning. The artificial intelligence model may include a plurality of artificial neural network layers. The artificial neural network may be a Deep Neural Network (DNN), a Convolutional Neural Network (CNN), a Recurrent Neural Network (RNN), a limited Boltzmann machine (RBM), a Deep Belief Network (DBN), a bi-directional recurrent deep neural network (BRDNN), a deep Q network, or a combination of two or more thereof, but is not limited thereto. Additionally or alternatively, the artificial intelligence model may include software structures in addition to hardware structures.

The memory 130 may store various data used by at least one component of the electronic device 101 (e.g., the processor 120 or the sensor module 176). The various data may include, for example, software (e.g., program 140) and input data or output data for commands associated therewith. Memory 130 may include volatile memory 132 or nonvolatile memory 134.

The program 140 may be stored as software in the memory 130 and may include, for example, an Operating System (OS) 142, middleware 144, or applications 146.

The input module 150 may receive commands or data from outside the electronic device 101 (e.g., a user) to be used by other components of the electronic device 101 (e.g., the processor 120). The input module 150 may include, for example, a microphone, a mouse, a keyboard, keys (e.g., buttons), or a digital pen (e.g., a stylus).

The sound output module 155 may output a sound signal to the outside of the electronic device 101. The sound output module 155 may include, for example, a speaker or a receiver. Speakers may be used for general purposes, such as playing multimedia or playing recordings. The receiver may be used to receive an incoming call. Depending on the embodiment, the receiver may be implemented as a separate speaker or as part of a speaker.

The display module 160 may visually provide information to the outside (e.g., user) of the electronic device 101. The display 160 may include, for example, a display, a hologram device, or a projector, and a control circuit for controlling a corresponding one of the display, the hologram device, and the projector. According to an embodiment, the display 160 may include a touch sensor configured to detect a touch, or a pressure sensor configured to measure the intensity of force generated by a touch.

The audio module 170 may convert sound into electrical signals and vice versa. According to an embodiment, the audio module 170 may obtain sound via the input module 150, or output sound directly (e.g., wired) or wirelessly coupled with the electronic device 101 via the sound output module 155 or headphones of an external electronic device (e.g., the electronic device 102).

The sensor module 176 may detect an operational state (e.g., electronic or temperature) of the electronic device 101 or an environmental state (e.g., a state of a user) external to the electronic device 101 and then generate an electrical signal or data value corresponding to the detected state. According to an embodiment, the sensor module 176 may include, for example, a gesture sensor, a gyroscope sensor, an atmospheric pressure sensor, a magnetic sensor, an acceleration sensor, a grip sensor, a proximity sensor, a color sensor, an Infrared (IR) sensor, a biometric sensor, a temperature sensor, a humidity sensor, or an illuminance sensor.

Interface 177 can support one or more specified protocols for directly (e.g., wired) or wirelessly coupling electronic device 101 with an external electronic device (e.g., electronic device 102). According to an embodiment, interface 177 may include, for example, a High Definition Multimedia Interface (HDMI), a Universal Serial Bus (USB) interface, a Secure Digital (SD) card interface, or an audio interface.

The antenna module 197 may transmit or receive signals or power to or from the outside (e.g., an external electronic device). According to an embodiment, the antenna module 197 may include an antenna including a radiator formed of a conductor or conductive pattern formed on a substrate, such as a Printed Circuit Board (PCB). According to an embodiment, the antenna module 197 may include a plurality of antennas (e.g., an antenna array). In this case, at least one antenna suitable for a communication scheme used in a communication network (e.g., the first network 198 or the second network 199) may be selected from among a plurality of antennas by, for example, the communication module 190. Signals or electrons may then be transmitted or received between the communication module 190 and an external electronic device via the selected at least one antenna. According to an embodiment, other parts than the radiator, such as a Radio Frequency Integrated Circuit (RFIC), may also be formed as part of the antenna module 197.

According to various embodiments, antenna module 197 may form a millimeter wave antenna module. According to an embodiment, a millimeter wave antenna module may include: a printed circuit board, an RFIC disposed on or adjacent to a first surface (e.g., a bottom surface) of the printed circuit board and capable of supporting a specified high frequency band (e.g., a millimeter wave band), and a plurality of antennas (e.g., array antennas) disposed on or adjacent to a second surface (e.g., a top surface or a side surface) of the printed circuit board and capable of transmitting or receiving signals of the specified high frequency band.

At least some of the above components may be coupled to each other and communicate signals (e.g., commands or data) therebetween via an inter-peripheral communication scheme (e.g., bus, general Purpose Input and Output (GPIO), serial Peripheral Interface (SPI), or Mobile Industrial Processor Interface (MIPI)).

According to an embodiment, commands or data may be sent or received between the electronic device 101 and the external electronic device 104 via the server 108 coupled with the second network 199. The external electronic devices 102 or 104 may each be the same or different types of equipment as the electronic device 101. According to embodiments, all or some of the operations to be performed at the electronic device 101 may be performed at one or more external electronic devices 102, 104, or 108. For example, if the electronic device 101 should perform a function or service automatically or in response to a request from a user or another apparatus, the electronic device 101 may request one or more external electronic devices to perform at least a portion of the function or service without performing the function or service, or may request one or more external electronic devices to perform at least a portion of the function or service in addition to performing the function or service. The external electronic device or devices receiving the request may perform at least a portion of the function or the requested service, or additional functions or additional services related to the request, and transmit the result of the performance to the electronic device 101. The electronic device 101 may provide the results, with or without further processing of the results, as at least a portion of the reply to the request. For this purpose, for example, cloud computing, distributed computing, mobile Edge Computing (MEC), or client-server computing techniques may be used. The electronic device 101 may provide ultra-low latency services using, for example, distributed computing or mobile edge computing. In another embodiment, the external electronic device 104 may include an internet of things (IoT) apparatus. Server 108 may be an intelligent server using machine learning and/or neural networks. According to an embodiment, the external electronic device 104 or the server 108 may be included in the second network 199. The electronic device 101 may be applied to smart services (e.g., smart home, smart city, smart car, or healthcare) based on 5G communication technology or IoT-related technology.

Fig. 1b is a view illustrating a network environment including an electronic device according to an embodiment of the present disclosure. Referring to fig. 1b, the network may include an electronic device 101, a first communication network 111a, and/or a second communication network 112a, according to various embodiments of the disclosure.

According to an embodiment of the present disclosure, the electronic apparatus 101 may operate as an electronic apparatus supporting a Dual SIM Dual Standby (DSDS) mode or a Dual SIM Dual Active (DSDA) mode of two SIMs in one device. For example, the electronic device 101 may include a first SIM 111 and an eSIM 201. The first SIM 111 may be a rsvi. For example, the electronic device 101 may be equipped with a SIM card. Hereinafter, for convenience of description, the SIM card will be referred to as a SIM. The electronic device 101 may comprise a slot (not shown) for receiving the first SIM 111. Although not shown, the electronic device 101 may receive two or more SIMs according to embodiments of the present disclosure. In this case, the electronic device 101 may include a plurality of slots for receiving a plurality of SIMs.

According to various embodiments of the present disclosure, the first SIM 111 is a SIM of a mobile network operator subscribed to the first communication network 111 a. The electronic device 101 may access the first communication network 111a using the first SIM 111 to receive wireless communication services. According to various embodiments of the present disclosure, the electronic device 101 may include an embedded subscriber identity module (eSIM) 201. esims may be referred to as euiccs. The electronic device 101 may receive wireless communication services by accessing the second communication network 112a via the eSIM 201. The first communication network 111a and the second communication network 112a may be provided by the same communication carrier, or may be provided separately by different communication carriers.

Fig. 2 is a diagram illustrating a system for providing profile-based communication connections to electronic devices according to an embodiment of the present disclosure.

Referring to fig. 2, a system 200 may include an electronic device 101, a subscription manager discovery service (SM-DS) server 210, a SM-dp+ server 220, an MNO server 230, and a communication service server 240, according to various embodiments of the present disclosure.

According to various embodiments of the present disclosure, the electronic device 101 (e.g., the electronic device 101 of fig. 1 b) can include an eSIM 201. For ease of description, although not shown, the electronic device 101 may include at least one slot for receiving at least one rSIM. According to various embodiments of the present disclosure, the electronic device 101 may include or receive N (N is a natural number) SIMs (esims or rsims) and may perform a handoff to use some of them. The combination of N SIMs is not limited and the number is also not limited.

According to various embodiments of the present disclosure, the eSIM 201 can be inserted into the electronic device 101, provided integrally with the electronic device 101, or implemented to be accessible by the electronic device 101. In accordance with various embodiments of the present disclosure, eSIM 201 can allow electronic device 101 to use information in eSIM 201 (e.g., a profile including Universal Subscriber Identity Module (USIM) information) to perform authentication with a server of a communication carrier (mobile network operator (MNO)). In accordance with embodiments of the present disclosure, eSIM 201 may be referred to as a Subscriber Identity Module (SIM) card for the global system for mobile communications (GSM), or as a USIM card for Wideband Code Division Multiple Access (WCDMA), LTE, and NR, and may also be referred to in other different terms depending on the communication scheme. For example, if the user of the electronic device 101 subscribes to a wireless communication service provided by a communication carrier, the electronic device 101 may use information in the eSIM 201 (e.g., the IMSI value and the encryption key K used for authentication) to perform an appropriate authentication procedure with a server of the communication carrier storing the same value, and then use the wireless communication service. For example, a suitable authentication procedure may be Authentication and Key Agreement (AKA) authentication. Other authentication schemes may also be used.

According to various embodiments of the present disclosure, eSIM201 may be manufactured as a dedicated card for a particular communications carrier at the request of the particular communications carrier at the time of manufacturing the card, and may be equipped with authentication information (e.g., USIM application and subscriber identification ID (e.g., IMSI)) and encryption keys (e.g., known K or Ki values) for the corresponding communications carrier network connection. Applications (or information) in eSIM201 can be installed, modified, deleted, or updated as necessary using techniques such as Over The Air (OTA).

In accordance with various embodiments of the present disclosure, eSIM201 can download and/or store information for providing communication services in the form of a configuration file. According to embodiments of the present disclosure, the configuration file may be installed or stored during manufacture of the eSIM201, or may be downloaded by the terminal in an OTA scheme and installed or stored in the eSIM 201. For example, the configuration files may include a provisioning configuration file and an operation configuration file. Those of ordinary skill in the art will appreciate that the electronic device 101 may download the operating profile over a Wi-Fi short range connection or an internet connection even when the provisioning profile is not installed, and the provisioning profile need not necessarily be installed on the electronic device 101. For example, the operation profile may be a profile including subscriber identification information about a user of the electronic device, and the provisioning profile may include information (hereinafter referred to as "first information") for downloading subscriber identity information or a profile including subscriber identity information (hereinafter referred to as "first subscriber identity information") in the electronic device (hereinafter referred to as "first operation profile"). The electronic device can download the first operating profile based on the first information about the provisioning profile in the eSIM 201.

According to various embodiments of the present disclosure, the electronic device 101 can receive the communication service using subscriber identity information (hereinafter referred to as 'second subscriber identity information') of an operation profile (hereinafter referred to as 'second operation profile') installed or stored in the eSIM 201. For example, the profile including subscriber identification information may be a SIM profile.

According to an embodiment of the present disclosure, the operation profile may include network access authentication information of a subscriber, a telephone book of the subscriber, personal information of the subscriber (e.g., short Message Service (SMS)), a subscribed communication carrier name, an available service, an available data amount, a fee, or a service providing speed, or information for allowing secure use of wireless communication by performing subscriber authentication and traffic security key generation when accessing a wireless communication network such as GSM, WCDMA, LTE or NR, in addition to subscriber identification information.

According to various embodiments of the present disclosure, the first information for downloading data (e.g., the first operational profile) including the first subscriber identity information may include communication session information for downloading a specified first communication connection of the first operational profile. For example, the communication session information may include subscription manager discovery service (SM-DS) server 210 access information for downloading the first operation profile or information about a communication carrier network available for the SM-DS server 210 access.

According to various embodiments of the present disclosure, the SM-DS server 210 may provide the address of the SM-dp+ server 220 to the electronic device 101 for downloading the first operational profile based on the provisioning profile.

According to various embodiments of the present disclosure, subscription manager data preparation plus (SM-dp+) server 220 may be a profile provisioning server, an off-card entity of a profile domain, a profile encryption server, a profile generation server, a profile provider, or a profile provider. The SM-dp+ server 220 can perform the first communication contact 22 with the electronic device 101 through the wireless communication network according to the provisioning profile from the electronic device 101 based on the first communication connection request, and can provide the first operation profile to the electronic device 101 through the first communication contact 22. According to various embodiments of the present disclosure, the wireless communication network may be a particular node of the wireless communication network. For example, the wireless communication network may be a base station, a subscriber information management node or a mobility management node of the wireless communication network. According to embodiments of the present disclosure, the wireless communication network may include a Home Location Register (HLR) and/or an authentication center (AuC) server, which the electronic device 101 accesses to perform a subscriber authentication function, and through the access after authentication, the wireless communication network may be connected to a communication service server 240 capable of providing a communication service such as voice communication or data communication.

According to various embodiments of the present disclosure, the Mobile Network Operator (MNO) server 230 may be a server associated with a mobile communications network operator. According to various embodiments of the present disclosure, MNO server 230 may request subscription manager discovery service plus (SM-ds+) server 220 to prepare at least one profile (or profile package) (e.g., a first operational profile) associated with at least one subscriber identity information (e.g., a first subscriber identity information) and transmit information associated with the first operational profile to SM-ds+ server 220. According to an embodiment of the present disclosure, the MNO server 230 may transmit a signal for updating and managing the first operational profile to the SM-ds+ server 220. The MNO server 230 can perform a second communication connection 24 between the electronic device 101 and the communication services server 240 through a second operational profile installed in the eSIM 201 of the electronic device 101.

According to various embodiments of the present disclosure, the communication service server 240 may be a server providing a communication service. According to various embodiments of the present disclosure, the communication service may be a service associated with transmitting or receiving data over a wireless communication network. According to embodiments of the present disclosure, a communication service may include a service associated with transmission or reception of another profile (or data) that does not include subscriber identity information in addition to a download operation profile (e.g., a first operation profile that includes first subscriber identity information). For example, the communication service server 240 may include a service server associated with various data transmissions and receptions, such as a server associated with each of various applications, a push server, a search server, or a marketplace server. The communication service through the communication service server 240 may include various services such as data transmission/reception through an application, notification reception, push message reception, link reception and access, or service request.

According to various embodiments of the present disclosure, upon requesting a service associated with the transmission or reception of a profile (or data) that does not include subscriber identity information, the electronic device 101 may perform the second communication connection 24 with the communication service server 240 based on the second operational profile.

According to various embodiments of the present disclosure, the SM-DS server 210, the SM-dp+ server 220, the MNO server 230, or the communication service server 240 are merely examples of an implementation of a server for performing each function, which may be referred to by other names, and each of the SM-DS server 210, the SM-dp+ server 220, the MNO server 230, or the communication service server 240 may include one or more servers. Some or all of the SM-DS server 210, the SM-dp+ server 220, the MNO server 230, or the communication service server 240 may be configured as one integrated server. According to various embodiments of the present disclosure, an electronic device (e.g., the electronic device 101 of fig. 1a or 1b or the electronic device 101 of fig. 2) may include: a display (e.g., display module 160 of fig. 1 a); a communication module (e.g., communication module 190 of fig. 1 a); an embedded subscriber identity module (e.g., subscriber identity module 196 of fig. 1a or eSIM 201 of fig. 2) that stores first information associated with a first communication connection for downloading data including first subscriber identity information for accessing at least one communication service providing server; a memory (e.g., memory 130 of fig. 1a or memory 211 of fig. 2); and a processor (e.g., processor 120 of fig. 1 a) electrically connected to the display, the communication module, and the memory. The processor may be configured to: performing, using the communication module, a first communication connection for downloading data including first subscriber identity information based on the first information, the first communication connection being terminated upon a request to transmit or receive data not including the first subscriber identity information during the first communication connection; and performing transmission or reception of data by performing a second communication connection based on the second subscriber identity information.

According to various embodiments of the present disclosure, the first information may include a provisioning profile, and the data including the first subscriber identification information may include a first operation profile.

According to various embodiments of the present disclosure, a processor may be configured to: when the subscriber identity module does not include second subscriber identity information when requesting to transmit or receive data during the first communication connection, displaying, via the display, that there is no second operational profile corresponding to the second subscriber identity information.

According to various embodiments of the present disclosure, the processor may be further configured to display a purchase screen associated with the second operational profile when the second operational profile is not present.

According to various embodiments of the present disclosure, the processor may be configured to perform the second communication session based on a previously used second operational profile.

According to various embodiments of the present disclosure, the processor may be configured to perform the second communication session based on a second operational profile selected by the user.

According to various embodiments of the present disclosure, the processor may be configured to display, via the display, at least one indicator indicating the first communication connection based on the provisioning configuration file.

According to various embodiments of the present disclosure, the at least one indicator may include at least one type of a Service Provider Name (SPN), a Radio Access Technology (RAT), and a Received Signal Strength Indicator (RSSI).

According to various embodiments of the present disclosure, the processor may be configured to select a provisioning profile associated with a network connected through the communication module.

According to various embodiments of the present disclosure, the processor may be configured to select a provisioning profile associated with a network being connected based on at least one of a Public Land Mobile Network (PLMN) identifier, a Mobile Country Code (MCC), and area information regarding the network being connected through the communication module.

Fig. 3 is a block diagram showing a configuration of an electronic device according to an embodiment of the present disclosure.

Referring to fig. 3, the electronic device 101 of fig. 1a or 1b or the electronic device 101 of fig. 2 may include a processor 120, an eSIM 201, a communication module 190, a display module 160, and an input module 150, according to various embodiments of the present disclosure. For ease of description, although not shown, the electronic device 101 may include two or more slots capable of receiving two or more rSIMs.

According to various embodiments of the present disclosure, the processor 120 (e.g., the processor 120 of fig. 1 a) may include one or more processors (e.g., the primary processor 121 and the secondary processor 123 or the application processor and the communication processor of fig. 1 a), and according to embodiments of the present disclosure, may include a Local Profile Assistant (LPA) 312 (e.g., an LPAd (device)). According to various embodiments of the present disclosure, when the processor 120 includes a plurality of processors, a portion of the LPA 312 may be included in some of the plurality of processors and another portion of the LPA 312 may be included in other of the plurality of processors. According to various embodiments of the present disclosure, the LPA 312 can be included in the eSIM 201, and in this case, the LPA 312 can be referred to as an LPAe (eUICC).

According to various embodiments of the present disclosure, the LPA 312 can perform communication with a server to support profile download, installation, and management operations for the eSIM 201, or can perform operations that provide a user interface required in the profile download, installation, and management operations. LPA 312 can be a module that operates in electronic device 101 to provide Local Discovery Service (LDS) 31, local Profile Download (LPD) 33, and Local User Interface (LUI) 35.

According to various embodiments of the present disclosure, the LDS 31 may perform an operation of receiving an address of the SM-ds+ server 220 capable of downloading an operation profile based on a provisioning profile from the SM-DS server 210 and communicate with the SM-DS server 210.

According to various embodiments of the present disclosure, LPD 33 may perform a first communication connection 22 with SM-ds+ server 220 through a wireless communication network based on an address of SM-ds+ server 220, and perform an operation of receiving a first operation profile from SM-ds+ server 220 through first communication connection 22. According to various embodiments of the present disclosure, LPD 33 may support network-initiated profile download, enable, disable, delete, or Profile Policy Rule (PPR) download operations, or may support profile enable, disable, delete, or eUICC reset operations by an electronic device.

According to various embodiments of the present disclosure, LUI 35 may perform operations of providing various user interfaces when downloading an operation profile. According to embodiments of the present disclosure, LUI 35 may support data exchange between LDS 31 and LPD 33, and may include a UI to communicate user input to LDS 31 or LPD 33.

According to embodiments of the present disclosure, the processor 120 can perform communication services using (or by executing) the LPA 312 based on information stored in the eSIM 201. For example, the processor 120 can perform a first communication connection with the SM-ds+ server 220 through the communication module 190 using the LPA 312 based on the provisioning configuration file stored in the eSIM 201 to download a configuration file (e.g., a first operational configuration file) that includes first subscriber identity information. When a request is made to transmit or receive a profile or data that does not include subscriber identity information during a first communication connection using LPA 312, processor 120 may terminate the first communication connection and perform a second communication connection based on the second subscriber identity information to transmit or receive the profile or data that does not include subscriber identity information.

According to various embodiments of the present disclosure, an eSIM 201 (e.g., subscriber identification module 196 of fig. 1a or eSIM 201 of fig. 2) can include one or more profiles as information for receiving communication services. The configuration file may refer to a package in the form of software of at least one of an application, a file system, and an authentication key value stored in the eSIM 201. For example, the configuration files may include a provisioning configuration file and an operation configuration file. The operation profile may include subscriber identification information, and may further include network access authentication information of a subscriber, a telephone book of the subscriber, personal information of the subscriber (e.g., SMS), a subscribed communication carrier name, an available service, an available data amount, a fee or a service providing speed, or information for allowing secure use of wireless communication by performing subscriber authentication and traffic security key generation when accessing a wireless communication network such as GSM, WCDMA, LTE or NR. According to embodiments of the present disclosure, the operational profile may include a SIM profile. For example, the SIM profile may include a SIM file system (main file (MF), dedicated File (DF), basic file (EF)). The subscriber identity information (IMSI) value may be stored in a base file.

According to various embodiments of the present disclosure, the provisioning profile may be a profile that includes first information for downloading a first operational profile in the electronic device. For example, the first information may include communication session information specifying a first communication connection for downloading the first operational profile. For example, the communication session information may include SM-DS server (e.g., SM-DS server 210 of fig. 2) access information for downloading the first operational profile, and may include information about a communication carrier network available for SM-DS server access.

According to various embodiments of the present disclosure, the communication module 190 (e.g., the communication module 190 of fig. 1 a) may perform a first communication based on a provisioning profile or a second communication based on a second operational profile. At least one screen associated with the first communication based on the provisioning profile or the second communication based on the second operational profile may be displayed on the display module 160.

The LPA 312 has been described as being included in the processor 120 according to embodiments of the present disclosure, but at least some of the functions of the LPA 312 may be performed by the processor 120 or a separate LPA 312 may operate with the processor 120. For example, LPA 312 may be included in a program (e.g., program 140 of fig. 1 a) and may be loaded onto processor 120 and executed. The LPA 312, when loaded on the processor 120 and executed, may be understood as the operation of the processor 120. According to various embodiments of the present disclosure, the functional modules (e.g., LDS 31, LPD 33, or LUI 35) included in LPA 312 are illustratively partitioned and may not be limited to being represented as other functional modules. According to various embodiments of the present disclosure, LPA 312 can be included in eSIM 201.

Fig. 4 is a view illustrating an internal structure of an eUICC according to an embodiment of the present disclosure.

Referring to fig. 4, according to an embodiment of the present disclosure, the eUICC 401 (e.g., eSIM 201 of fig. 2 or 3) can be in the form of a card or chip and can install at least one configuration file 410, 420, and 430 in the form of software. According to various embodiments of the present disclosure, each of the one or more profiles 410, 420, and 430 may be a provisioning profile or an operational profile. At least one configuration file 410, 420, and 430 can operate on an eUICC Operating System (OS) 450. Each of the at least one configuration files 410, 420, and 430 may be enabled or disabled by a processor or LPA (e.g., LPA 312 of fig. 3 or LPA 480 of fig. 4). According to embodiments of the present disclosure, one configuration file 410 may be in an enabled state while the remaining configuration files 420 and 430 may be in a disabled state. According to various embodiments of the present disclosure, two or more profiles may be in an enabled state.

According to various embodiments of the present disclosure, the eUICC Operating System (OS) 450 of the eUICC 401 can include a profile policy enabler 452, a profile package interpreter 454, and a telecommunications framework 456. According to embodiments of the present disclosure, profile policy enabler 452 may manage policy rules (profile policy rules (PPRs)) for each of one or more profiles 410, 420, and 430. According to embodiments of the present disclosure, the profile package interpreter 454 may unpack the profile package received from the SM-DP 220 in a form that may be installed in the eUICC 401. According to embodiments of the present disclosure, the telecommunications framework 556 can perform functions associated with communication of applications in the eUICC 401. According to various embodiments of the present disclosure, the eUICC 401 can include a release Fang Anquan domain root (ISD-R) 460 and an eUICC control rights security domain (ECASD) 470. According to embodiments of the present disclosure, the ISD-R460 can manage at least one profile 410, 420, and 430 installed in the eUICC 401. For example, ISD-R460 may include LPA service 462. The LPA service 462 can manage at least one profile 410, 420, and 430 installed in the eUICC 401 through an interface with a processor or LPA (e.g., LPA 312 of fig. 3 or LPA 480 of fig. 4). According to embodiments of the present disclosure, the ECASD 470 can perform security processing on at least one profile 410, 420, and 430 installed in the eUICC 401.

According to various embodiments of the present disclosure, each of the at least one configuration file 410, 420, and 430 may include: ISD-P410-1, 420-1 or 430-1; MNO-SD 410-2, 420-2 or 430-2; supplemental Security Domains (SSDs) 410-3, 420-3, or 430-3; a control rights security domain (CASD) 410-4, 420-4 or 430-4, applet 410-5, 420-5 or 430-5; a Network Access Application (NAA) 410-6, 420-6 or 430-6; file systems 410-7, 420-7, or 430-7; or profile metadata 410-8, 420-8, or 430-8.

According to embodiments of the present disclosure, ISD-P410-1, 420-1 or 430-1 may include information for decoding and interpreting a profile package and, in cooperation with profile package interpreter 454, may be used for unpacking and installing a profile package received from SM-dp+220.

According to embodiments of the present disclosure, the MNO-SD 410-2, 420-2 or 430-2 may include an OTA key for an MNO and may include information for providing a secure OTA channel capable of communicating with the MNO.

According to embodiments of the present disclosure, supplemental Security Domains (SSDs) 410-3, 420-3, or 430-3 and Control Authority Security Domains (CASDs) 410-4, 420-4, or 430-4 may include information for performing security processing on configuration files.

According to embodiments of the present disclosure, the applet 410-5, 420-5, or 430-5 may include various application information associated with a user of the profile.

According to embodiments of the present disclosure, a Network Access Application (NAA) 410-6, 420-6 or 430-6 may include application information that allows a profile to access a network.

According to embodiments of the present disclosure, file system 410-7, 420-7, or 430-7 may include a file system associated with each piece of information in a configuration file.

According to embodiments of the present disclosure, profile metadata 410-8, 420-8, or 430-8 may also be referred to as profile records, and may include metadata information about the text-form profile. The metadata information may include at least one of an Integrated Circuit Card ID (ICCID) of a profile, a profile name, a profile providing a name of an MNO, a profile nickname of a user, an icon, a profile category, notification profile information, profile owner information, or Profile Policy Rules (PPR).

In accordance with various embodiments of the present disclosure, as a profile identifier, the ICCID of a profile may indicate a unique identifier for each profile. The name of the profile may include the name of each profile. The profile providing the name of the MNO may include the name of the communication carrier providing the profile. The user's profile nickname may comprise a user-specified profile nickname. The icons may include icons corresponding to configuration files. The profile category may include information indicating whether the profile type is a provisioning profile or an operational profile. The notification configuration information may include an address of a server (e.g., SM-dp+ server 220) for receiving the notification. The profile owner information may include Mobile Country Code (MCC), mobile Network Code (MNC), and Group Identifier (GID) 1 or 2 information associated with the profile owner. For example, the MCC may be a code for identifying a country and the MNC may be a code for identifying a mobile communication operator. GID 1 or 2 may be code region information for identifying a group or region to which the profile belongs. The region information may include a group having a plurality of countries. The Profile Policy Rules (PPR) may include policy rule information for managing the profile.

According to various embodiments of the present disclosure, the electronic device 101 can use the profile category information of the profile metadata 410-8, 420-8, or 430-8 included in each of the at least one profile 410, 420, or 430 included in the eUICC 401 to identify whether it is a provisioning profile or an operational profile, and enable or disable each of the provisioning profile or the operational profile through the LPA (LPA 312 of fig. 3 or LPA 480 of fig. 4).

Fig. 5 is a block diagram illustrating a network system for downloading configuration files according to an embodiment of the present disclosure. Referring to fig. 5, a network system may include an electronic device 101 and a communication carrier server 500 according to various embodiments of the present disclosure. The communication carrier server 500 may include a profile information transfer server 520, a profile providing server 530, an authentication server 540, or a carrier management server 550. According to various embodiments of the present disclosure, the communications carrier server 500 may or may not include a web server 510. For example, at least one of the web server 510, the profile information transfer server 520, the profile providing server 530, the authentication server 540, or the operator management server 550 may be included in the communication operator server 500 managed by the communication operator. The operator management server 550 may include, but is not limited to, a service support system (BSS) or an Operation Support System (OSS). According to various embodiments of the present disclosure, the web server 510 and the profile information transfer server 520 may be servers managed by the same communication carrier or different communication carriers. According to various embodiments of the present disclosure, the profile information transfer server 520 and the profile providing server 530 may be servers managed by the same communication carrier or different communication carriers. eSIM 201 can be inserted or embedded in electronic device 101. The configuration files may be downloaded and installed in the eSIM 201. According to an embodiment to be described later, the service client 202 may be installed in the electronic apparatus 101 for communication with the communication carrier server 500.

According to various embodiments of the present disclosure, the electronic device 101 may access the profile information delivery server 520 through, for example, the service client 202, and may access the web server 510 through the accessed profile information delivery server 520. For example, when the electronic device 101 accesses the profile information delivery server 520, the profile information delivery server 520 may authenticate the electronic device 101 or a user of the electronic device 101 through the operator management server 550 or the authentication server 540 and perform a qualification check. If the electronic device 101 or a user of the electronic device 101 is normally authenticated and determined to be eligible, the profile information transfer server 520 may transmit information for accessing the web server 510 to the electronic device 101. The electronic device 101 may access the web server 510 using information for accessing the web server 510 received through the profile information delivery server 520. According to various embodiments of the present disclosure, the electronic device 101 may request a subscription, an opening, or a subscription transfer through a web page provided by the web server 510, and according to another embodiment of the present disclosure, may request a subscription, an opening, or a subscription transfer through the profile information transfer server 520 without the web server 510. For example, when the communication carrier server 500 does not include the web server 510 or includes the web server 510 but provides information related to the web server 510 (e.g., address information about the web server 510) (e.g., when web services or web pages are not provided through the web server), the electronic device 101 may request subscription, opening, or subscription transfer through the profile information transfer server 520. According to various embodiments of the present disclosure, web server 510 may provide a User Interface (UI) or web page for profile information delivery server 520. For example, the electronic device 101 may request a subscription, opening, or subscription transfer for a particular profile through a web page provided from the web server 510. According to various embodiments of the present disclosure, profile information delivery server 520 may provide communication line management and creation, service control, and status information. The profile information transfer server 520 may be referred to as an authorization server or an authorization configuration server, but is not limited thereto. For example, profile information transfer server 520 may include an authorization server or an authorization configuration server set forth in GSMA standard document ts.43. In the standard document, the term 'authorization' may refer to the applicability, availability, or status of a desired service before providing the service (e.g., communication service) to a user of the electronic device 101. For example, the profile information delivery server 520 may perform a function of delivering profile related information (e.g., profile download information or profile download related information) provided to the electronic device 101. In the following description, profile information may include information related to a profile, and for convenience of description, it is referred to as profile download information or profile download related information. The profile information transfer server 520 may include, but is not limited to, a Discovery and Push Function (DPF), a subscription manager discovery service (SM-DS), a subscription manager secure routing (SM-SR), a subscription manager secure routing plus (SM-SR+), an off-card entity of an eUICC profile manager or profile management credential holder (PMC holder) or an EUICC Manager (EM).

According to various embodiments of the present disclosure, the profile providing server 530 may perform functions of managing and downloading profiles. For example, profile provisioning server 530 may include, but is not limited to, subscription manager data preparation (SM-DP), subscription manager data preparation plus (SM-dp+), off-card entity of profile domain, profile encryption server, profile generation server, profile Provider (PP)), profile provider, or profile provisioning credential holder (PPC holder).

Fig. 6 is a flowchart illustrating a method for downloading a configuration file according to an embodiment of the present disclosure. Referring to fig. 6, according to various embodiments of the present disclosure, the electronic device 101 may access the web server 510 through a profile information transfer server 520 of the communication carrier server 500. In operation 602, the electronic device 101 may request a new eSIM profile, or request a subscription, opening, or subscription transfer to a new communication service, through a web page provided by the web server 510. For example, electronic device 101 may transmit a message including a subscription-related operation (e.g., subscription, open, or subscription transfer) through a web page provided by web server 510, and according to various embodiments of the present disclosure, the transmission of the message including the subscription-related operation may follow the process set forth in GSMA standard document TS, but is not limited thereto. For example, the electronic device 101 may request the profile information delivery server 520 (e.g., an authorization server) to perform a qualification check according to the procedure set forth in the standard document TS.43. In response to the request, the profile information delivery server 520 may transmit a profile query to another server (e.g., the operator management server 550 (e.g., BSS or OSS)) in the communication operator server 500, thereby checking eligibility. After the eligibility check is completed, the profile information transfer server 520 may transmit the check result to the electronic device 101. The electronic device 101 may recognize that the eligibility check is completed normally and may request that the profile information delivery server 520 perform a subscription-related operation (e.g., subscription, open, or subscription transfer).

According to various embodiments of the present disclosure, the profile information transfer server 520 of the communication carrier server 500 may authenticate the electronic device 101 or a user of the electronic device 101 through the authentication server 540.

In accordance with various embodiments of the present disclosure, in operation 604, the profile information delivery server 520 may prepare a profile by the electronic device 101 requesting the profile providing server 530 in response to a request for a subscription-related operation (e.g., subscription, open, or subscription transfer). The information transmitted from the profile information delivery server 520 to the profile providing server 530 according to the profile preparation request may include an eUICC discriminator (e.g., EUICC Identifier (EID)), information about the profile information delivery server, profile discriminator or profile request time, profile installation key, information about the electronic device 101, or eUICC information. The profile differentiator may be referred to as a profile identifier (profile ID), integrated Circuit Card ID (ICCID), ISD-P, or factor matching profile field (PD). The profile identifier may indicate a unique identifier for each profile. The eUICC identifier (euiccid) can be a unique identifier of the eSIM 201 (or eUICC) embedded in the electronic device 101 and can be referred to as an EID. For example, when provisioning profiles are pre-provisioned in the eUICC, the eUICC ID can be an identifier of the corresponding provisioning profile (profile ID of the provisioning profile). For example, when the electronic device 101 and the eSIM 201 are not separated, the eUICC ID can be the ID of the electronic device 101. The eUICC ID can refer to a specific security domain of the eUICC chip.

In accordance with various embodiments of the present disclosure, the profile information delivery server 520 may notify the electronic device 101 of the profile ready state when the profile providing server 530 prepares the profile in operation 606. The message for notifying the profile ready state may include a callback message (e.g., a Java Script (JS) callback message). For example, when the electronic device 101 terminates a web page provided by the web server 510, a callback message may be transmitted, but is not limited thereto.

According to various embodiments of the present disclosure, the callback message transmitted from the profile information transfer server 520 to the electronic device 101 may be implemented in the form of "onplane selected completed (servicestatus=9, smdpAddress or activation code)". The callback message may include service state information, an address (or address information) of the profile providing server (e.g., SM-dp+220) 530, or an activation code. For example, service status information (ServiceStatus) may be denoted as 9 to indicate that the configuration file is delayed, and service status information may be denoted as 1 to indicate that the configuration file is ready. According to various embodiments of the present disclosure, the activation code may include information corresponding to an address of the profile providing server 530. The electronic device 101 may identify the address of the profile providing server 530 based on the activation code.

In accordance with various embodiments of the present disclosure, the profile providing server 530 may prepare a profile in operation 608. For example, when a profile identifier (e.g., ICCID) value is transferred to a profile preparation request, the profile providing server 530 may prepare a profile corresponding to the profile identifier. As another example, if a profile identifier does not exist, one or more of the profile request type, information about the electronic device 101, information about the eUICC, and information about the eUICC identifier may be used to differentiate profiles, and a profile differentiator may be specified. Further, when the eUICC discriminator is included in the profile preparation request, the profile providing server 530 can download and install the specified profile later only in the specific eUICC. When the eUICC discriminator is not included in the profile preparation request, the profile providing server 530 can prepare the profile without associating the specified profile with a particular eUICC, and allow it to download the profile with the profile associated with the eUICC when an appropriate request including the eUICC discriminator is later received from the electronic device 101.

Further, when the profile preparation request includes a profile installation key, the profile providing server 530 may associate and manage the profile installation key with a specific profile, and download the specific profile when the electronic device 101 later requests to download the profile with the profile installation key. The profile installation key may be referred to as an event identifier (EventID), a match identifier (MatchingID), or an activation code token (activation code token or AC token). In contrast, in the case where the profile preparation request does not include the profile installation key, the profile providing server 530 itself may generate the profile installation key in the profile preparation process, and after the profile preparation, the profile providing server 530 may transmit the profile installation key to the profile information transmitting server 520.

In accordance with various embodiments of the present disclosure, the profile providing server 530 may transmit profile download information (or profile download-related information) to the profile information transmitting server 520 in operation 610. The transfer of the profile download information may be to register the profile download information with the profile information transfer server 520. The profile information delivery server 520 may receive the profile download information and register the received profile download message. When so registered, the profile download information may be stored in the profile information delivery server 520. For example, the profile download information may include at least one of an address of the profile providing server 530, a profile installation key, or eUICC information. The address of the profile providing server 530 may include at least one of a server address in the form of a Fully Qualified Domain Name (FQDN), an address in the form of a fully Uniform Resource Locator (URL), or an Internet Protocol (IP) server address. The eUICC information can be a specific EID or a value or EID in which the hash function operation result is provided to the specific EID. The hash function operation of the EID refers to a calculation included in the hash operation. For example, the hash function may be performed once or twice on the EID, or on the cryptographic information together with the EID, as a factor of the hash function may be added. The password may be a value that is transmitted to the user.

Fig. 7a and 7b are views illustrating user interfaces displayed on a screen of an electronic device according to various embodiments of the present disclosure.

Referring to fig. 7a, in accordance with various embodiments of the present disclosure, before receiving a push message indicating that a profile is ready (or in a state in which push information indicating that a profile is ready is not received) in operation 612 described below, the electronic device 101 may request downloading of the profile through a SIM card management screen 710 for downloading of eSIM profiles. For example, if a menu item 711 (e.g., "add mobile package") is selected to add a profile on the SIM card management menu 710 shown in fig. 7a, an add profile screen 720 may be displayed as shown in fig. 7 b. Referring to fig. 7b, when a menu item 711 for adding a profile is selected, the add profile screen 720 may include a screen 721 for identifying a profile ready state. For example, when the menu item 711 for adding a profile is selected, the electronic device 101 may transmit a profile check request message to the profile providing server 530. According to various embodiments of the present disclosure, when the electronic device 101 does not recognize the address of the profile providing server 530 (e.g., when the address of the profile providing server 530 is not stored in the memory of the electronic device 101 (e.g., memory 130 of fig. 1 a)), the electronic device 101 may send a request for profile download information to the profile information transfer server 520. The profile information delivery server 520 may deliver profile download information to the electronic device 101 in response to the request. The profile download information transmitted from the profile information delivery server 520 to the electronic device 101 may include the address of the profile providing server 530. According to various embodiments of the present disclosure, the electronic device 101 may send a request for a profile to the profile providing server 530 based on the address of the profile providing server 530. According to various embodiments of the present disclosure, if the configuration file is ready in the configuration file providing server 530, the electronic device 101 may download the configuration file from the configuration file providing server 530 even before receiving the push message.

According to various embodiments of the present disclosure, if the profile download information is transmitted or registered to the profile information transmission server 520 in operation 610, the profile download message may be transmitted to the electronic device 101 to which the eUICC corresponding to the eUICC information is connected. For example, the profile information transmitting server 520 of the communication carrier server 500 may transmit profile download information to the electronic device 101 through a push message in operation 612. For example, profile information delivery server 520 may deliver the push message to electronic device 101 via a web push server (not shown). According to various embodiments of the present disclosure, push messages may be implemented in the form shown in table 1 below.

TABLE 1

In table 1, "downloadInfo" may refer to an address or an activation code of the profile providing server 530 (e.g., SM-dp+220). According to various embodiments of the present disclosure, "notify event" in table 1 may include information or an identifier (e.g., "ready_to_download_profile") indicating a profile ready state or a profile download ready state. According to various embodiments of the present disclosure, when the communication carrier server 500 provides a profile through the plurality of profile providing servers 530, the address of the profile providing server 530 may not be included in the push message. For example, when the address of the profile providing server 530 is not stored in a memory (e.g., memory 130 of fig. 1 a) or the push message does not include the address of the profile providing server 530, or when the callback message indicating the notification of the profile ready state of operation 606 does not include the address of the profile providing server 530, the electronic device 101 may send a request for profile download information (e.g., information corresponding to the address of the profile providing server 530) to the profile information transfer server 520 in operation 614. In operation 616, the profile information transfer server 520 may transfer the profile download information to the electronic device 101 in response to the request. The profile download information transmitted from the profile information delivery server 520 to the electronic device 101 may include information corresponding to the address of the profile providing server 530 (e.g., a server address of FQDN type, an address of full URL type, or an IP server address or an activation code).

Fig. 8a and 8b are views illustrating user interfaces displayed on a screen of an electronic device according to various embodiments of the present disclosure.

Referring to fig. 8a, in accordance with various embodiments of the present disclosure, when the electronic device 101 receives a push message and recognizes that the configuration file is ready through a "notify event" included in the push message, the electronic device 101 may display a notification (or notification bar) on the screen.

When the user slides on the upper end of the screen of the electronic device 101, a notification screen 810 may be displayed as shown. For example, the notification screen 810 may indicate a function of the app related to "SIM card manager" and may include "add mobile package" information related to profile download in the function. For example, the electronic device 101 may identify that the profile is ready by pushing a message, and may display a message indicating that the profile is ready (e.g., "your mobile package is ready. The notification screen 810 may include a button 811 (e.g., "add") for performing a function for downloading a configuration file.

When the user selects the button 811 for performing the function for downloading the profile, the electronic device 101 may transmit a request for the profile to the profile providing server 530 using the address of the profile providing server 530 and the profile installation key included in the profile download information in operation 618 according to various embodiments of the present disclosure.

Referring to fig. 8b, if it is recognized that the profile is ready in the profile providing server 530 according to the profile request, a profile download screen 820 may be displayed. For example, profile download screen 820 may include a query screen 821 of profile download progress (e.g., "add package to your phone. When the user selects an identification button 822 (e.g., "add and use it immediately") for requesting download on the query screen 821 of the profile download progress, a profile download request to the profile providing server 530 may be performed. The status bar 810 or 820 shown in fig. 8a or 8b may be referred to as a navigation bar, a quick panel, a notification bar, or a pop-up window according to various embodiments of the present disclosure, but is not limited thereto. For example, in operation 620, the electronic device 101 may download the configuration file from the configuration file providing server 530 by selecting the confirm button 822 for requesting download shown in fig. 8 b. According to various embodiments of the present disclosure, the electronic device 101 may obtain an IP address from a domain name server using the FQDN address of the profile providing server included in the profile download information and request to provide the profile to the IP address. According to various embodiments of the present disclosure, the electronic device 101 may transmit the profile installation key directly to the profile providing server 530 or provide the installation key to the profile providing server 530 after the profile providing server 530 is authenticated by the authentication server 540.

According to various embodiments of the present disclosure, the profile providing server 530 may perform an authentication process and then, in operation 620, download the profile to the electronic device 101. In operation 622, the electronic device 101 can download and install the configuration file to the eSIM 201 (e.g., eUICC). The electronic device 101 may activate the profile after installing the profile. Through profile activation, a subscription, open, or subscription transfer process for using communication services through profile download to the electronic device 101 may be completed. The electronic device 101 can use the mobile communication network after authenticating with the mobile communication system using the profile installed in the eSIM 201.

According to various embodiments of the present disclosure, the profile providing server 530 may be a server operated by a manufacturer of the mobile communication carrier or eSIM 201 (or eUICC), and the profile information transfer server 520 may be a server operated by a manufacturer of the mobile communication carrier or eUICC or electronic device. In profile download using an eUICC, it may not be possible to determine which network operator's profile to download at the time of eUICC manufacture. For example, the profile may be determined according to which network operator's communication services the user subscribes to. For example, a user must access a server operated by a network operator of a subscribed communication service and download a configuration file. However, since such information is unknown at the time of the eUICC creation, as described above, the address of the profile providing server 530 can be obtained for profile download.

According to various embodiments of the present disclosure, when the push message is not transmitted in operation 612, the electronic device 101 may not know whether the profile providing server 530 is ready for the profile and wait for the push message all the time, so that the profile cannot be downloaded normally. Since the communication carrier may not know whether the electronic device normally receives the push message, it does not retransmit the push message, and the electronic device may eventually wait for the push message indefinitely.

According to various embodiments described below, even when an electronic device fails to normally receive a push message indicating that a configuration file is ready, it can normally download the configuration file by allowing a configuration file check request to be performed via a status bar (e.g., notification bar), as in the embodiments described below.

Fig. 9 is a flowchart illustrating a method for downloading a configuration file according to an embodiment of the present disclosure. In fig. 9, a detailed description of the same or similar operation as that of fig. 6 is not given. Referring to fig. 9, according to various embodiments of the present disclosure, the electronic device 101 may access the web server 510 through a profile information transfer server 520 of the communication carrier server 500. For example, when the electronic device 101 accesses the profile information delivery server 520, the profile information delivery server 520 may authenticate the electronic device 101 or a user of the electronic device 101 through the authentication server 540 and perform a qualification check. If the electronic device 101 or a user of the electronic device 101 is normally authenticated and determined to be eligible, the profile information transfer server 520 may transmit information for accessing the web server 510 to the electronic device 101. The electronic device 101 may access the web server 510 using information for accessing the web server 510 received through the profile information delivery server 520. According to various embodiments of the present disclosure, the electronic device 101 may request a subscription, an opening, or a subscription transfer through a web page provided by the web server 510, and according to another embodiment of the present disclosure, may request a subscription, an opening, or a subscription transfer through the profile information transfer server 520 without the web server 510. In operation 902, the electronic device 101 may request a new eSIM profile, or request a subscription, opening, or subscription transfer to a new communication service, through a web page provided by the web server 510. For example, electronic device 101 may transmit a message including a subscription-related operation (e.g., subscription, open, or subscription transfer) through a web page provided by web server 510, and according to various embodiments of the present disclosure, the transmission of the message including the subscription-related operation may follow the process set forth in GSMA standard document TS, but is not limited thereto. According to various embodiments of the present disclosure, the profile information transfer server 520 of the communication carrier server 500 may authenticate the electronic device 101 or a user of the electronic device 101 through the authentication server 540.

In accordance with various embodiments of the present disclosure, in operation 904, profile information delivery server 520 may prepare a profile by electronic device 101 requesting that profile providing server 530 respond to a request for a subscription-related operation (e.g., subscription, open, or subscription transfer). The information transmitted from the profile information delivery server 520 to the profile providing server 530 according to the profile preparation request may include an eUICC discriminator (e.g., EUICC Identifier (EID)), information about the profile information delivery server, profile discriminator or profile request time, profile installation key, information about the electronic device 101, or eUICC information.

In accordance with various embodiments of the present disclosure, in operation 906, the profile information delivery server 520 may notify the electronic device 101 of the profile ready state while the profile providing server 530 prepares the profile. The message for notifying the profile ready state may include a callback message (e.g., a JS callback message). For example, when the electronic device 101 terminates a web page provided by the web server 510, a callback message may be transmitted, but is not limited thereto.

According to various embodiments of the present disclosure, the callback message transmitted from the profile information transfer server 520 to the electronic device 101 may be implemented in the form of "onplane selected completed (servicestatus=9, smdpAddress or activation code)". The callback message may include service state information, an address of the profile providing server (e.g., subscription manager data preparation platform (SM-DP) +220) 530, or an activation code. For example, service status information (ServiceStatus) may be denoted as 9 to indicate that the configuration file is delayed, and service status information may be denoted as 1 to indicate that the configuration file is ready. According to various embodiments of the present disclosure, the activation code may include information corresponding to an address of the profile providing server 530. The electronic device 101 may identify the address of the profile providing server 530 based on the activation code.

Fig. 10 is a view illustrating a user interface displayed on a screen of an electronic device according to an embodiment of the present disclosure. Fig. 11 is a view illustrating a user interface displayed on a screen of an electronic device according to an embodiment of the present disclosure.

Referring to fig. 10 and 11, if the electronic device 101 recognizes that the profile is in a deferred state due to the profile not being ready through service state information included in the callback message, the electronic device 101 may display a profile ready state on a screen in operation 908 according to various embodiments of the present disclosure. For example, the electronic device 101 may display a message indicating the status of the profile delay on the screen through the pop-up window 1000 (e.g., "we are setting your package on the server. You will be notified when it is ready to add to your phone"), as shown in fig. 10. The pop-up window 1000 may include a confirm button 1001 (e.g., "OK"), and when the user selects the confirm button 1001, a notification screen 1100 shown in fig. 11 may be displayed on the screen of the electronic device 101. For example, the notification screen 1100 may include a status check button 1101 (e.g., a "check status") capable of identifying a status of the download of the configuration file. The following describes the description of the status check button 1101.

In accordance with various embodiments of the present disclosure, the profile providing server 530 may prepare a profile in operation 910. For example, when a profile identifier (e.g., ICCID) value is transferred to a profile preparation request, the profile providing server 530 may prepare a profile corresponding to the profile identifier.

In accordance with various embodiments of the present disclosure, the profile providing server 530 may transmit profile download information to the profile information transmitting server 520 in operation 912. The transfer of the profile download information may be to register the profile download information with the profile information transfer server 520. The profile information delivery server 520 may receive the profile download information and register the received profile download message. When so registered, the profile download information may be stored in the profile information delivery server 520. For example, the profile download information may include at least one of an address of the profile providing server 530, a profile installation key, or eUICC information. The address of the profile providing server 530 may include at least one of a server address in the form of a Fully Qualified Domain Name (FQDN), an address in the form of a fully Uniform Resource Locator (URL), or an Internet Protocol (IP) server address. The eUICC information can be a specific EID or a value or EID in which the hash function operation result is provided to the specific EID. The hash function operation of the EID refers to a calculation included in the hash operation. For example, the hash function may be performed once or twice on the EID, or on the cryptographic information together with the EID, as a factor of the hash function may be added. The password may be a value that is transmitted to the user.

According to various embodiments of the present disclosure, if profile download information is transmitted or registered to the profile information transmission server 520, a profile download message can be transmitted to the electronic device 101 to which the eUICC corresponding to the eUICC information is connected.

According to various embodiments of the present disclosure, if the profile download is ready in the profile providing server 530, the profile information transfer server 520 of the communication carrier server 500 may transfer the profile download information to the electronic device 101 through a push message in operation 914. For example, profile information delivery server 520 may deliver the push message to electronic device 101 via a web push server (not shown). The electronic device 101 may receive the push message and identify that the profile download is ready.

According to various embodiments of the present disclosure, a push message may not be normally transmitted to the electronic device 101 according to the state of the network or the state of the communication carrier server 500. When the push message is not transmitted in operation 914, the electronic device 101 may not know whether the profile providing server 530 is ready for the profile and wait for the push message all the time.

According to various embodiments of the present disclosure, since the electronic device 101 keeps the notification screen 1100 shown in fig. 11 even when no push message is received, it can recognize a profile ready state through the notification screen 1100. For example, when the user selects the status check button 1101 (e.g., "check status") of the notification screen 1100, the electronic device 101 may determine the selection of the check button 1101 as a profile check request in operation 916. According to various embodiments of the present disclosure, in accordance with the profile inspection request, in operation 922, the electronic device 101 may transmit the profile inspection request to the profile providing server 530. The profile check request may be implemented in the form of "poll SM-dp+", but is not limited thereto. According to various embodiments of the present disclosure, in operation 922, the electronic device 101 may transmit a profile check request to the profile providing server 530 periodically or when a set condition is satisfied.

According to various embodiments of the present disclosure, when the address of the profile providing server 530 is not stored in the memory of the electronic device 101 (e.g., the memory 130 of fig. 1 a) or the address of the profile providing server 530 is not received from the profile information delivery server 520, the electronic device 101 may send a request for profile download information to the profile information delivery server 520 in operation 918. In operation 920, the profile information delivery server 520 may deliver profile download information to the electronic device 101 in response to the request. The profile download information transmitted from the profile information delivery server 520 to the electronic device 101 may include information corresponding to the address of the profile providing server 530 (e.g., a server address of FQDN type, an address of full URL type, or an IP server address or an activation code).

Operations 918 and 920 may be omitted when the address of the profile providing server 530 is stored in a memory of the electronic device 101 (e.g., memory 130 of fig. 1 a), according to various embodiments of the present disclosure. For example, when a callback message (e.g., JS callback message) indicating a profile ready state is received from the profile information delivery server 520 in operation 906 described above, the electronic device 101 may identify address information about the profile providing server (e.g., SM-dp+220) 530 included in the callback message and store the address information about the profile providing server 530 in a memory (e.g., memory 130 of fig. 1 a).

If the electronic device 101 transmits a profile inspection request to the profile providing server 530 in operation 922, the profile providing service 530 may transmit a profile inspection result to the electronic device 101 in operation 924 according to various embodiments of the present disclosure. For example, when the profile is ready in the profile providing server 530, a message (e.g., "successful poll SM-dp+") corresponding to the profile being ready may be transmitted as the profile check result. Conversely, if the profile is not ready in the profile providing server 530, a message corresponding to the profile preparation being delayed (e.g., "failed poll SM-dp+") may be transmitted as the profile check result.

According to various embodiments of the present disclosure, when the electronic device 101 receives a message corresponding to the configuration file being ready (e.g., "successfully polls SM-dp+") as a configuration file check result, the configuration file download screen 820 described above in connection with fig. 8b may be displayed. For example, profile download screen 820 may include a query screen 821 of profile download progress (e.g., "add package to your phone. When the user selects an identification button 822 (e.g., "add and use it immediately") for requesting download on the query screen 821 of the profile download progress, a profile download request to the profile providing server 530 may be performed.

If the electronic device 101 determines that the profile is ready according to the transmitted profile inspection result in operation 924, the electronic device 101 may download the profile from the profile providing server 530 in operation 926 according to various embodiments of the present disclosure. According to various embodiments of the present disclosure, the electronic device 101 can download and install a configuration file to the eSIM 201 (e.g., eUICC). In operation 928, the electronic device 101 may activate the profile after installing the profile. By the profile activation, an opening process for using the communication service by downloading the profile to the electronic device 101 may be completed. The electronic device 101 can use the mobile communication network after authenticating with the mobile communication system using the profile installed in the eSIM 201.

Fig. 12a and 12b are flowcharts illustrating methods for downloading a configuration file according to various embodiments of the present disclosure. Referring to fig. 12a and 12b, in operation 1202, the electronic device 101 (e.g., the processor 120 of fig. 1 a) may request a subscription, open, or subscription transfer through a web page.

In accordance with various embodiments of the present disclosure, in operation 1204, the electronic device 101 may receive a callback message indicating a delay in profile generation. In operation 1206, based on the received callback message, the electronic device 101 may display a pop-up message (e.g., notification screen) indicating the profile ready state. For example, the electronic apparatus 101 may display the notification screen shown in fig. 10 and 11.

In accordance with various embodiments of the present disclosure, in operation 1208, the electronic device 101 may drive a first timer and a second timer. The first timer may include a timer configured to prevent repeated execution of the profile check request for a predetermined time. The second timer may include a timer for setting the duration of the notification screen shown in fig. 11. For example, the first timer may be set to 1 minute and the second timer may be set to 24 hours, but this is not limited thereto.

According to various embodiments of the present disclosure, the electronic device 101 may determine whether a profile status check request input from a user is received in operation 1210 according to selection of the status check button 1101 (e.g., a "check status") of fig. 11. If it is determined in operation 1210 that the profile status check request has not been received (no in operation 1210), the electronic device may wait until the profile status check request is received. When a profile status check request is received in operation 1210 (yes in operation 1210), the electronic device 101 may identify whether the first timer has expired in operation 1212. According to various embodiments of the present disclosure, when the status check button 1101 (e.g., the "check status") of fig. 11 is selected, driving of the first timer may be started.

When the first timer has not expired in operation 1212 ("no" in operation 1212), the electronic device 101 may wait until the first timer expires. When the first timer expires (yes in operation 1212), the electronic device 101 may transmit a profile check request to the profile providing server 530 in operation 1214. According to various embodiments of the present disclosure, when the status check button 1101 of fig. 11 is selected again after expiration of the first timer, the first timer may be driven again as described above.

In accordance with various embodiments of the present disclosure, in operation 1218, the electronic device 101 may receive a response to the profile inspection request from the profile providing server 530. Based on the response to the profile check request, in operation 1220, the electronic device 101 may determine whether the profile is ready. As a result of the determination in operation 1220, if it is determined that the profile is ready (yes in operation 1220), the electronic device 101 may display a profile download request screen as shown in fig. 8a and 8b in operation 1222. The electronic device 101 may send a request for a profile download to the profile providing server 530 and may download a corresponding profile in operation 1224.

As a result of the determination in operation 1220, if it is determined that the configuration file is not ready ("no" in operation 1220), the electronic device 101 may determine whether the second timer expires in operation 1226. As a result of the determination, if the second timer has not expired (no in operation 1226), the electronic apparatus 101 may always display a pop-up message indicating the profile ready state displayed in operation 1206, and proceed to operation 1210. As a result of the determination, if the second timer expires (yes in operation 1226), the electronic device 101 may delete the pop-up message indicating the profile ready state in operation 1228 and may display the profile error message 1300 as shown in fig. 13 in operation 1230.

Fig. 13 is a view illustrating a user interface displayed on a screen of an electronic device according to an embodiment of the present disclosure.

Referring to fig. 13, a profile error message 1300 may include a message indicating that a profile was not downloaded normally (e.g., "out of question") and may include a confirm button 1301.

Fig. 14 is a flowchart illustrating a method for downloading a configuration file according to an embodiment of the present disclosure. Referring to fig. 14, in accordance with various embodiments of the present disclosure, in operation 1410, the electronic device 101 (e.g., the processor 120 of fig. 1 a) may receive a request (or a profile check request) to identify a profile before receiving a message corresponding to the profile being ready (or in a state where a push message corresponding to the profile being ready is not received). For example, the request to identify the configuration file may be received through a user interface (e.g., screen 1100 of FIG. 11) displayed on a display (e.g., display module 160 of FIG. 1 a) of the electronic device 101.

In accordance with various embodiments of the present disclosure, in operation 1420, unless address information corresponding to the profile providing server is not identified, the electronic device 101 may obtain information (e.g., a server address of FQDN type, an address of full URL type, or an IP server address, or an activation code) corresponding to an address of the profile providing server (e.g., the profile providing service 530 of fig. 5) from the communication carrier server.

In accordance with various embodiments of the present disclosure, in operation 1430, the electronic device 101 may transmit a message to the profile providing server identifying the profile. According to various embodiments of the present disclosure, if the profile providing server is in a profile ready state according to the transmission of the profile inspection request, the electronic device 101 may download the profile from the profile providing server in operation 1440.

Fig. 15 is a flowchart illustrating a method for downloading a configuration file according to an embodiment of the present disclosure. Referring to fig. 15, according to various embodiments of the present disclosure, the electronic device 101 may access the web server 510 through a profile information transfer server 520 of the communication carrier server 500. The electronic device 101 can request a new eSIM profile, or request a subscription, opening, or subscription transfer to a new communication service, through a web page provided by the web server 510. For example, electronic device 101 may transmit a message including a subscription-related operation (e.g., subscription, open, or subscription transfer) through a web page provided by web server 510, and according to various embodiments of the present disclosure, the transmission of the message including the subscription-related operation may follow the process set forth in GSMA standard document TS, but is not limited thereto.

For example, in operation 1502, the electronic device 101 may send a request for a qualification check to the profile information delivery server 520 (e.g., an authorization server) according to the procedure set forth in the standard document ts.43. The request for eligibility check may be transmitted in either the GET scheme or the POST scheme. For example, the electronic apparatus 101 may include any one of the ODSA operations shown in table 2 below in the request message, and transmit the request message to the profile information delivery server 520 according to the on-device service activation (ODSA) procedure set forth in the standard document ts.43.

TABLE 2

Referring to table 2 above, in operation 1502, the electronic device 101 may request a qualification check by transmitting a request message including "checkeligitity" as operation information to the profile information delivery server 520 (e.g., authorization server) according to the procedure set forth in the standard document ts.43. According to various embodiments of the present disclosure, the request message for the eligibility check may further include identification information (e.g., IMEI or UUID) or an authentication token of the electronic device 101. In accordance with various embodiments of the present disclosure, in operation 1504, the profile information delivery server 520 may transmit a profile query to an operator management server 550 (e.g., BSS or OSS). The profile query may include subscription identification information (e.g., "SubscriptionID"). In operation 1506, the carrier management server 550 may transmit a profile reply to the profile information delivery server 520 in response to receiving the profile query. In operation 1508, the profile information transfer server 520 may transmit a response message (e.g., a "200OK" message) to the electronic device 101 for the eligibility check request in response to receipt of the profile reply. For example, when the eligibility check of the electronic device 101 is completed normally, the response message may indicate that status information about the electronic device 101 is displayed as "enabled".

In accordance with various embodiments of the present disclosure, if the eligibility check is complete, in operation 1510, the electronic device 101 may request subscription, provisioning, or subscription transfer by transmitting a subscription-related operation request message including "management subscription" in table 2 above as operation information to the profile information delivery server 520 (e.g., authorization server) according to the procedure set forth in standard document ts.43. According to various embodiments of the present disclosure, the subscription-related operation request message may further include identification information (e.g., IMEI or UUID) or an authentication token of the electronic device 101. According to various embodiments of the present disclosure, the subscription-related operation request message may further include type information of table 3 below as parameter information.

TABLE 3 Table 3

Referring to table 3, the subscription-related operation request message including "management subscription" of table 2 above as operation information may include at least one parameter of "subscription", "unsubscribe", "change subscription", "transfer subscription", or "update subscription". For example, when the subscription-related operation request message includes "subscription," it can be a request to activate subscription to an eSIM. When the subscription-related operation request message includes "unsubscribe," it may be a request to cancel a subscription to an eSIM. When the subscription-related operation request message includes "change subscription," it can be a request to manage subscription information present in the eSIM. When the subscription-related operation request message includes "transfer subscription," it may be a request to transfer subscription information present in the eSIM to another electronic device 101 or another eSIM. When the subscription-related operation request message includes "update subscription," it may be a request for notifying the communication network of subscription information updates of the eSIM.

In accordance with various embodiments of the present disclosure, in operation 1512, the profile information delivery server 520 may transmit a subscription query to an operator management server 550 (e.g., BSS or OSS). The subscription query may include subscription identification information (e.g., "SubscriptionID") or IMEI. In operation 1514, the carrier management server 550 may transmit a subscription answer message to the profile information delivery server 520 in response to receipt of the subscription query. According to various embodiments of the present disclosure, the subscription response message may include address information (e.g., URL information) for accessing the web server 510. In operation 1516, the profile information delivery server 520 may transmit a response message (e.g., a "200OK" message) to the electronic device 101 for the subscription-related operation request in response to the subscription response message.

According to various embodiments of the present disclosure, the response message to the subscription-related operation request may further include subscription result information ("SubscriptionResult") of table 4 below as parameter information.

TABLE 4 Table 4

According to various embodiments of the present disclosure, referring to table 4, the response message (e.g., a "200OK" message) to the subscription-related operation request may include at least one parameter of "continue browsing web pages", "download configuration files", "complete", or "delay downloading". For example, when the type information included in the subscription-related operation request message of the above-described operation 1510 corresponds to "subscription" or "change subscription", the response message (e.g., a "200OK" message) to the subscription-related operation request of operation 1516 may include at least one parameter among "continue browsing web pages", "download profile", and "delay download". When the type information included in the subscription-related operation request message of the above-described operation 1510 corresponds to "update subscription", a response message (e.g., a "200OK" message) to the subscription-related operation request of operation 1516 may include "complete" as a parameter.

According to various embodiments of the present disclosure, referring to table 4, when the response message for the subscription-related operation request in operation 1516 includes "continue browsing web pages", address information (e.g., URL) for accessing the web server 510 may be further included. When the response message to the subscription-related operation request of operation 1516 includes "download profile", the profile providing server 530 is in a profile ready state, and may further include address information about the profile providing server 530. When the response message to the subscription-related operation request of operation 1516 includes "complete," the configuration file has been downloaded to the electronic device 101 so that further operations may not be required.

When the response message to the subscription-related operation request in operation 1516 includes a "delayed download," it may indicate that the configuration file is not ready in the configuration file providing server 530, according to various embodiments of the present disclosure. According to various embodiments of the present disclosure, the embodiment of fig. 15 is an embodiment in which subscription is requested through a web page provided from the web server 510. The response message to the subscription-related operation request may include "continue browsing web pages", and may further include address information (e.g., URL information) for accessing the web server 510.

In accordance with various embodiments of the present disclosure, in operation 1518, the electronic device 101 may access the web server 510 based on address information for accessing the web server 510 included in a response message to the subscription-related operation request from the profile information delivery server 520. In operation 1520, the electronic apparatus 101 may request subscription through a web page provided from the web server 510. In operation 1522, the web server 510 may transmit an active subscription message to the operator management server 550 based on the subscription information requested from the electronic device 101. In operation 1524, in response to receipt of the active subscription message, the operator management server 550 may send a request for profile preparation to the profile providing server 530 to prepare a profile corresponding to the request from the electronic device 101. In operation 1526, the profile providing server 530 may prepare the profile in response to the request. In operation 1528, the profile providing server 530 may transmit the profile information to the operator management server 550. For example, the profile information may include profile ready state related information (e.g., profile download ready or profile download delay).

In accordance with various embodiments of the present disclosure, in operation 1530, the operator management server 550 may transmit an active subscription answer message to the web server 510 in response to the active subscription request from the web server 510. In operation 1532, the web server 510 may transmit a completion flow message to the electronic device 101. According to various embodiments of the present disclosure, profile information delivery server 520 may notify electronic device 101 of a profile ready state while profile provisioning server 530 prepares a profile, as described above in connection with fig. 6. The message for notifying the profile ready state may include a callback message (e.g., a Java Script (JS) callback message). For example, when the electronic device 101 terminates a web page provided by the web server 510, a callback message may be transmitted, but is not limited thereto.

According to various embodiments of the present disclosure, if the electronic device 101 recognizes that the configuration file is in a deferred state due to the configuration file not being ready through the service state information included in the callback message, the electronic device 101 may display the configuration file ready state on the screen as described above. For example, the electronic device 101 may display a message on the screen indicating the status of the profile delay through the pop-up window 1000 (e.g., "we are setting your package on the server. You will be notified when it is ready to add to your phone"), as described above in connection with fig. 10. The pop-up window 1000 may include a confirm button 1001 (e.g., "OK"), and when the user selects the confirm button 1001, a notification screen 1100 shown in fig. 11 may be displayed on the screen of the electronic device 101. For example, the notification screen 1100 may include a status check button 1101 (e.g., a "check status") capable of identifying a status of the download of the configuration file.

In accordance with various embodiments of the present disclosure, the profile information transfer server 520 of the communication carrier server 500 may inform the electronic device 101 that the profile download is ready in operation 1534. For example, profile information delivery server 520 may deliver the push message to electronic device 101 via a web push server (not shown). According to various embodiments of the present disclosure, push messages may be implemented in the form shown in table 1 above.

In accordance with various embodiments of the present disclosure, in operation 1536, the electronic device 101 may download a configuration file from the configuration file providing server 530 based on address information about the configuration file providing server 530. In operation 1538, the electronic device 101 can install the profile in the eSIM 201 (e.g., eUICC) and activate the installed profile. Through profile activation, a subscription, open, or subscription transfer process for using communication services through profile download to the electronic device 101 may be completed. The electronic device 101 can use the mobile communication network after authenticating with the mobile communication system using the profile installed in the eSIM 201.

As described above in connection with fig. 15, the electronic apparatus 101 may perform a subscription, opening, or subscription transfer process through a web page provided from the web server 510 provided by the communication carrier. In accordance with various embodiments of the present disclosure, a method of the electronic device 101 performing a subscription, an open, or a subscription transfer procedure when a communication carrier does not provide information related to the web server 510 (e.g., address information about the web server 510) is described in connection with fig. 16 and 17. In the following description of fig. 16 and 17, a description overlapping with that of fig. 15 will be omitted.

Fig. 16 is a flowchart illustrating a method for downloading a configuration file according to an embodiment of the present disclosure. Referring to fig. 16, according to various embodiments of the present disclosure, the electronic device 101 can request a new eSIM profile, or request a subscription, opening, or subscription transfer to a new communication service, through the profile information transfer server 520 of the carrier server 500. For example, electronic device 101 may transmit a message including a subscription-related operation (e.g., subscription, open, or subscription transfer) to profile information delivery server 520, and according to various embodiments of the present disclosure, the transmission of the message including the subscription-related operation may follow the process set forth in GSMA standard document TS, but is not limited thereto.

For example, in operation 1602, the electronic device 101 may send a request for a qualification test to the profile information delivery server 520 (e.g., an authorization server) according to the procedure set forth in the standard document TS.43. The request for eligibility check may be transmitted in either the GET scheme or the POST scheme. For example, the electronic apparatus 101 may include any one of the ODSA operations shown in table 2 above in the request message, and transmit the request message to the profile information delivery server 520 according to the on-device service activation (ODSA) procedure set forth in the standard document ts.43. For example, in operation 1602, the electronic device 101 may request a qualification check by transmitting a request message including "checkeligitity" as operation information to the profile information delivery server 520 (e.g., an authorization server) according to the procedure set forth in the standard document ts.43. According to various embodiments of the present disclosure, the request message for the eligibility check may further include identification information (e.g., IMEI or UUID) or an authentication token of the electronic device 101.

In accordance with various embodiments of the present disclosure, in operation 1604, the profile information delivery server 520 may transmit a profile query to an operator management server 550 (e.g., BSS or OSS). The profile query may include subscription identification information (e.g., "SubscriptionID"). In operation 1606, the carrier management server 550 may transmit a profile answer to the profile information delivery server 520 in response to receiving the profile query. In operation 1608, the profile information delivery server 520 may transmit a response message (e.g., a "200OK" message) to the electronic device 101 for the eligibility check request in response to receipt of the profile answer. For example, when the eligibility check of the electronic device 101 is completed normally, the response message may indicate that status information about the electronic device 101 is displayed as "enabled".

According to various embodiments of the present disclosure, if the qualification checking is completed, the electronic device 101 may request subscription, provisioning, or subscription transfer by transmitting a subscription-related operation request message including "management subscription" in table 2 above as operation information to the profile information transfer server 520 (e.g., an authorization server) according to the procedure set forth in the standard document ts.43 in operation 1610. According to various embodiments of the present disclosure, the subscription-related operation request message may further include identification information (e.g., IMEI or UUID) or an authentication token of the electronic device 101. According to various embodiments of the present disclosure, the subscription-related operation request message may further include type information of table 3 above as parameter information.

In accordance with various embodiments of the present disclosure, in operation 1612, profile information delivery server 520 may transmit a subscription query to operator management server 550 (e.g., BSS or OSS). The subscription query may include subscription identification information (e.g., "SubscriptionID") or IMEI. In operation 1614, in response to receipt of the subscription query, operator management server 550 may send a request for profile preparation to profile provisioning server 530 to prepare a profile corresponding to the subscription-related operation request from electronic device 101. In operation 1616, the profile providing server 530 may prepare a profile in response to the request. In operation 1618, the profile providing server 530 may transmit the profile information to the operator management server 550. For example, the profile information may include profile ready state related information (e.g., profile download ready or profile download delay).

In accordance with various embodiments of the present disclosure, in operation 1620, the operator management server 550 may transmit a subscription answer message to the profile information delivery server 520 in response to the transmission of the subscription query from the profile information delivery server 520. In accordance with various embodiments of the present disclosure, in operation 1622, the profile information transfer server 520 may transmit a response message (e.g., a "200OK" message) to the electronic device 101 for the subscription-related operation request in response to the subscription response message.

According to various embodiments of the present disclosure, the response message to the subscription-related operation request may further include subscription result information ("SubscriptionResult") of table 4 above as parameter information.

According to various embodiments of the present disclosure, when the profile is ready in the profile providing server 530, a response message (e.g., a "200OK" message) to the subscription-related operation request may include "download profile" as a parameter. According to various embodiments of the present disclosure, when a response message (e.g., a "200OK" message) to the subscription-related operation request includes "download profile" as a parameter, information for accessing the profile providing server 530 may be further included. For example, the information for accessing the profile providing server 530 may include an address (or address information) of the profile providing server (e.g., SM-ds+220) 530 or an activation code for identifying the address information. According to various embodiments of the present disclosure, the activation code may comprise any of the activation codes set forth in GSMA standard document ts.43. For example, the activation code may include at least one of an address of SM-ds+220 (530), an activation code token, or a subscription manager data ready identification (SMDPid).

In accordance with various embodiments of the present disclosure, in operation 1624, the electronic device 101 may download a profile from the profile providing server 530 based on information for accessing the profile providing server 530 (e.g., an address (or address information) of the profile providing server (e.g., SM-dp+220 (530)) or an activation code for identifying the address information), in operation 1626, the electronic device 101 may install the profile in the eSIM 201 (e.g., eUICC) and activate the installed profile.

Fig. 17 is a flowchart illustrating a method for downloading a configuration file according to an embodiment of the present disclosure. Referring to fig. 17, according to various embodiments of the present disclosure, the electronic device 101 can request a new eSIM profile, or request a subscription, opening, or subscription transfer to a new communication service, through the profile information transfer server 520 of the carrier server 500. For example, electronic device 101 may transmit a message including a subscription-related operation (e.g., subscription, open, or subscription transfer) to profile information delivery server 520, and according to various embodiments of the present disclosure, the transmission of the message including the subscription-related operation may follow the process set forth in GSMA standard document TS, but is not limited thereto.

For example, in operation 1702, the electronic device 101 may send a request for a qualification test to the profile information delivery server 520 (e.g., an authorization server) according to the procedure set forth in the standard document ts.43. The request for eligibility check may be transmitted in either the GET scheme or the POST scheme. For example, the electronic apparatus 101 may include any one of the ODSA operations shown in table 2 above in the request message, and transmit the request message to the profile information delivery server 520 according to the on-device service activation (ODSA) procedure set forth in the standard document ts.43. For example, in operation 1702, the electronic device 101 may request a qualification check by transmitting a request message including "checkeligitity" as operation information to the profile information delivery server 520 (e.g., an authorization server) according to the procedure set forth in the standard document ts.43. According to various embodiments of the present disclosure, the request message for the eligibility check may further include identification information (e.g., IMEI or UUID) or an authentication token of the electronic device 101.

In accordance with various embodiments of the present disclosure, in operation 1704, the profile information delivery server 520 may transmit a profile query to an operator management server 550 (e.g., BSS or OSS). The profile query may include subscription identification information (e.g., "SubscriptionID"). In operation 1706, the carrier management server 550 may transmit a profile answer to the profile information delivery server 520 in response to receiving the profile query. In operation 1708, the profile information delivery server 520 may transmit a response message (e.g., a "200OK" message) to the electronic device 101 for the qualification request in response to receipt of the profile reply. For example, when the eligibility check of the electronic device 101 is completed normally, the response message may indicate that status information about the electronic device 101 is displayed as "enabled".

According to various embodiments of the present disclosure, if the qualification check is completed, the electronic device 101 may request subscription, provisioning, or subscription transfer by transmitting a subscription-related operation request message including "management subscription" in table 2 above as operation information to the profile information transfer server 520 (e.g., authorization server) according to the procedure set forth in the standard document ts.43 in operation 1710. According to various embodiments of the present disclosure, the subscription-related operation request message may further include identification information (e.g., IMEI or UUID) or an authentication token of the electronic device 101. According to various embodiments of the present disclosure, the subscription-related operation request message may further include type information of table 3 above as parameter information.

In accordance with various embodiments of the present disclosure, in operation 1712, profile information delivery server 520 may transmit a subscription query to operator management server 550 (e.g., BSS or OSS). The subscription query may include subscription identification information (e.g., "SubscriptionID") or IMEI. In operation 1714, in response to receipt of the subscription query, operator management server 550 may send a request for profile preparation to profile provisioning server 530 to prepare a profile corresponding to the subscription-related operation request from electronic device 101. In operation 1716, the profile providing server 530 may prepare a profile in response to the request. In operation 1718, the profile providing server 530 may transmit the profile information to the operator management server 550. For example, the profile information may include profile ready state related information (e.g., profile download ready or profile download delay).

In accordance with various embodiments of the present disclosure, in operation 1720, the operator management server 550 may transmit a subscription answer message to the profile information delivery server 520 in response to the transmission of the subscription query from the profile information delivery server 520. In operation 1722, the profile information delivery server 520 may transmit a response message (e.g., a "200OK" message) to the electronic device 101 for the subscription-related operation request in response to the subscription response message. Operations 1718 and 1720 may be omitted, or operation 1722 may be performed regardless of operations 1718 and 1720, according to various embodiments of the present disclosure. For example, in response to receiving a subscription-related operation request from the electronic device 101 in operation 1710, the profile information delivery server 520 may transmit a subscription query in operation 1712 and a response message (e.g., a "200OK" message) to the subscription-related operation request in operation 1722 before receiving the subscription answer message in operation 1720. According to various embodiments of the present disclosure, the response message to the subscription-related operation request may further include subscription result information ("SubscriptionResult") of table 4 above as parameter information. According to various embodiments of the present disclosure, when the profile download is ready in the profile providing server 530, a response message (e.g., a "200OK" message) to the subscription-related operation request may include "download profile" as a parameter, as described above in connection with operation 1622 of fig. 16. When the response message (e.g., a "200OK" message) to the subscription-related operation request includes "download profile" as a parameter, information for accessing the profile providing server 530 may be further included. For example, the information for accessing the profile providing server 530 may include an address (or address information) of the profile providing server (e.g., SM-ds+220) 530 or an activation code for identifying the address information. According to various embodiments of the present disclosure, as described above in connection with operation 1624 of fig. 16, the electronic device 101 may download the configuration file from the configuration file providing server 530 based on information for accessing the configuration file providing server 530, e.g., an address (or address information) of the configuration file providing server (e.g., SM-dp+220 (530) or an activation code for identifying the address information).

According to various embodiments of the present disclosure, when the profile is not ready in the profile providing server 530, a response message (e.g., a "200OK" message) to the subscription-related operation request may include "delayed download" as a parameter. According to various embodiments of the present disclosure, when a response message (e.g., a "200OK" message) to a subscription-related operation request includes "delayed download" as a parameter, it may periodically or at the request of the user identify a profile ready state from the profile providing server 530, as described above in connection with fig. 6, 7a, 7b, 8a, 8b, 9, 10, 11, 12a, 12b, 13 and 14.

For example, as shown in fig. 17, when information related to the web server 510 (e.g., address information about the web server 510) is not provided from the communication carrier server 500 to the electronic device 101, the electronic device may not receive a callback message including a profile ready state from the communication carrier server. For example, since the electronic device does not receive the callback message from the communication carrier server, the electronic device may not recognize whether the profile download readiness state is delayed.

According to various embodiments of the present disclosure, as shown in fig. 17, when the electronic device 101 transmits a subscription-related operation request to the communication carrier server 500 (e.g., the profile information delivery server 520), a response to the request transmitted from the communication carrier server 500 (e.g., the profile information delivery server 520) may include information indicating that the profile ready state is delayed and transmitted (e.g., "delayed download"), so that the electronic device 101 may recognize the profile ready state, as shown in operation 1722.

According to various embodiments of the present disclosure, if the electronic device 101 identifies the profile delay state as profile download ready incomplete by a parameter included in a response message to the subscription-related operation request, the electronic device 101 may display the profile ready state on the screen as described above in connection with operation 908 of fig. 9. For example, the electronic device 101 may display a message on the screen indicating the status of the profile delay through the pop-up window 1000 (e.g., "we are setting your package on the server. You will be notified when it is ready to add to your phone"), as described above in connection with fig. 10. The pop-up window 1000 may include a confirm button 1001 (e.g., "OK"), and when the user selects the confirm button 1001, a notification screen 1100 may be displayed on the screen of the electronic device 101, as described above in connection with fig. 11. For example, the notification screen 1100 may include a status check button 1101 (e.g., a "check status") capable of identifying a status of the download of the configuration file.

In accordance with various embodiments of the present disclosure, the electronic device 101 may identify a profile download ready state or identify address information about the profile providing server 530 by transmitting a service related data request message to the profile information delivery server 520 in operation 1724. For example, according to the procedure set forth in the standard document ts.43, the electronic device 101 may transmit a service-related data request message including "AcquireConfiguration" of table 2 as operation information to the profile information transmission server 520 (e.g., an authorization server). According to various embodiments of the present disclosure, the service related data request message may further include identification information (e.g., IMEI or UUID) or an authentication token of the electronic device 101.

In accordance with various embodiments of the present disclosure, in operation 1726, profile information transfer server 520 may transmit a subscription status query (e.g., a "subscription status query") message to operator management server 550. In operation 1728, the carrier management server 550 may transmit a response message (e.g., a "subscription status answer") to the subscription status query message to the profile information delivery server 520. In operation 1730, in response to receipt of the subscription status response message, the profile information delivery server 520 may transmit a response message (e.g., a "200OK" message) to the electronic device 101 for the service-related data request. According to various embodiments of the present disclosure, the electronic device 101 may identify the profile ready state with reference to parameters included in a response message to the service related data request. For example, when a parameter included in the response message indicates "active", it may be identified as a status in which the profile download is not ready or in which the profile download is ready but the profile may not be active. When the response message of operation 1730 includes address information regarding the profile providing server 530, the electronic device 101 may access the profile providing server 530 using the address information regarding the profile providing server 530 according to various embodiments of the present disclosure.

The operations 1724, 1726, 1728, and 1730 described above may be omitted according to various embodiments of the present disclosure. For example, when address information about the profile providing server 530 is identified through operation 1722, operations 1724, 1726, 1728, and 1730 may be omitted. As another example, when the electronic device 101 may not be able to identify address information regarding the profile providing server 530, it may be implemented to perform operation 1724 periodically or based on a set condition. For example, upon receiving a user input from a user identifying a profile download readiness state, the electronic device 101 may be triggered by the user input and perform operation 1724. As another embodiment of the present disclosure, after receiving the response message in operation 1722, the electronic device 101 may drive the timer and transmit a polling message if a time (e.g., 30 seconds) set when the timer is driven elapses. According to various embodiments of the present disclosure, when the parameter included in the response message of operation 1730 indicates "active", it may be identified as a state in which the profile download preparation is incomplete or a state in which the profile has been downloaded but not activated.

In accordance with various embodiments of the present disclosure, if the profile is ready in the profile providing server 530, the profile information delivery server 520 may identify a profile ready state in operation 1732. In accordance with various embodiments of the present disclosure, in operation 1734, the profile information delivery server 520 may transmit a push message to the electronic device 101 in response to identifying the profile ready state. For example, profile information delivery server 520 may deliver the push message to electronic device 101 via a web push server (not shown).

When the electronic device 101 fails to recognize the address of the profile providing server 530, the electronic device 101 may transmit a service-related data request message to the profile information delivery server 520 in operation 1736 according to various embodiments of the present disclosure. Operation 1736 may correspond to the request for profile download information of operation 614 described above with reference to fig. 6. For example, according to the procedure set forth in the standard document ts.43, the electronic device 101 may transmit a service-related data request message including "AcquireConfiguration" of table 2 as operation information to the profile information transmission server 520 (e.g., an authorization server). According to various embodiments of the present disclosure, the service related data request message may further include identification information (e.g., IMEI or UUID) or an authentication token of the electronic device 101.

In accordance with various embodiments of the present disclosure, in operation 1738, the profile information delivery server 520 may transmit a subscription status query (e.g., a "subscription status query") message to the operator management server 550. In operation 1740, the operator management server 550 may transmit a response message (e.g., a "subscription status answer") to the subscription status query message to the profile information delivery server 520. In operation 1742, in response to receipt of the subscription status response message, the profile information delivery server 520 may transmit a response message (e.g., a "200OK" message) to the electronic device 101 for the service-related data request. For example, the response message of operation 1742 may correspond to the transfer of the profile download information of operation 616 described above with reference to fig. 6.

According to various embodiments of the present disclosure, the electronic device 101 may identify the profile ready state with reference to parameters included in a response message to the service related data request. For example, when a parameter included in the response message indicates "activated", it may be identified that the configuration file is ready. According to various embodiments of the present disclosure, the response message (e.g., a "200OK" message) may further include information for accessing the profile providing server 530. For example, the information for accessing the profile providing server 530 may include an address (or address information) of the profile providing server (e.g., SM-ds+220) 530 or an activation code for identifying the address information. According to various embodiments of the present disclosure, the activation code may comprise any of the activation codes set forth in GSMA standard document ts.43. For example, the activation code may include at least one of an address of SM-ds+220 (530), an activation code token, or an SMDPid. Operations 1736, 1738, 1740, and 1742 may be omitted when address information regarding the profile providing server 530 has been identified prior to operation 1736 according to various embodiments of the present disclosure.

In accordance with various embodiments of the present disclosure, the electronic device 101 may download a configuration file from the configuration file providing server 530 based on information (e.g., an address (or address information) for accessing the configuration file providing server 530 or an activation code for identifying the address information) in operation 1744 the electronic device 101 may install the configuration file in an eSIM 201 (e.g., eUICC) and activate the installed configuration file in operation 1746 the electronic device 101 may complete a subscription, provisioning, or subscription transfer procedure for using a communication service by downloading the configuration file to the electronic device 101, the electronic device 101 may use a mobile communication network after authentication with the mobile communication system using the configuration file installed in the eSIM 201.

According to various embodiments of the present disclosure, the first response message may include information indicating that the configuration file is not ready based on the first server not providing the electronic device with web server-related information for the subscription or subscription transfer.

According to various embodiments of the present disclosure, the at least one processor may be further configured to: controlling transmission of a second request message to the first server including information related to the service status request based on a first response message including information indicating that a configuration file to be provided for the eUICC is not ready; and receiving a second response message from the first server. The second response message may include address information corresponding to a second server providing the profile.

According to various embodiments of the present disclosure, the at least one processor may be further configured to: receiving a request for identifying a configuration file; transmitting a third request message for identifying a download readiness of the profile to a second server providing the profile in response to receiving the request for identifying the profile; receiving a third response message from the second server in response to the transmission of the third request message; and controlling a request to download the configuration file to the second server based on a third response message including information indicating that the configuration file is ready.

According to various embodiments of the present disclosure, the electronic device may further include a touch screen. The at least one processor may be further configured to receive, via the touch screen, a request for identifying a configuration file.

According to any of the various embodiments of the present disclosure, an electronic device may include: at least one embedded universal integrated circuit card (eUICC), each card storing at least one piece of subscriber identity information; and at least one processor electrically connected to the eUICC. The at least one processor may be configured to: receiving a request for identifying a configuration file; obtaining address information corresponding to a profile providing server from a communication carrier server based on address information corresponding to the profile providing server that does not recognize the profile; transmitting a message for identifying a readiness of the profile to the profile providing server based on address information corresponding to the profile providing server; and based on identifying that the profile is ready, controlling downloading the profile from the profile providing server and storing the profile in the eUICC.

According to various embodiments of the present disclosure, the at least one processor may be further configured to: a request to identify a configuration file is received before a message corresponding to the configuration file ready is received.

According to various embodiments of the present disclosure, a message corresponding to profile readiness may be received by a push message.

According to various embodiments of the present disclosure, the at least one processor may be further configured to obtain address information corresponding to the profile providing server from the authorization server.

According to various embodiments of the present disclosure, the at least one processor may be further configured to: receiving information about a profile ready state from an authorization server in response to a request for at least one of subscription, opening, or subscription transfer of a communication service; and controlling to display a popup window indicating that the generation of the profile is delayed based on identifying that the generation of the profile is delayed from the received information about the ready state of the profile.

According to various embodiments of the present disclosure, a request to identify a configuration file may be received through a pop-up window.

According to various embodiments of the present disclosure, the at least one processor may be further configured to: driving a first timer; identifying whether the first timer expires based on receiving a request for identifying the configuration file through the pop-up window; and based on identifying that the first timer expires, transmitting a message identifying a profile ready state.

According to various embodiments of the present disclosure, the at least one processor may be further configured to: driving a second timer; and controlling a pop-up window in which generation of the deletion instruction profile is delayed based on the identification of the expiration of the second timer.

According to various embodiments of the present disclosure, the at least one processor may be further configured to: based on identifying that the configuration file is ready, a message is received from the configuration file providing server indicating that the configuration file is ready.

According to various embodiments of the present disclosure, a method for installing a profile of an embedded SIM in an electronic device including at least one embedded universal integrated circuit card (eUICC) storing at least one subscriber identity information and at least one processor electrically connected to the eUICC may include: receiving a request for identifying a configuration file; obtaining address information corresponding to a profile providing server from a communication carrier server based on address information corresponding to the profile providing server that does not recognize the profile; transmitting a message for identifying a readiness of the profile to the profile providing server based on address information corresponding to the profile providing server; and based on identifying that the profile is ready, downloading the profile from the profile providing server and storing the profile in the eUICC.

According to various embodiments of the present disclosure, the method may further include receiving, via the touch screen, a request for identifying the configuration file.

According to various embodiments of the present disclosure, the method may further comprise: a request to identify a configuration file is received before a message corresponding to the configuration file ready is received.

According to various embodiments of the present disclosure, the method may further include obtaining address information corresponding to the profile providing server from the authorization server.

According to various embodiments of the present disclosure, the method may further comprise: receiving information about a profile ready state from an authorization server in response to a request for at least one of subscription, opening, or subscription transfer of a communication service; and if it is recognized that the generation of the profile is delayed according to the received information on the ready state of the profile, displaying a popup window indicating that the generation of the profile is delayed.

According to various embodiments of the present disclosure, the method may further comprise: driving a first timer; if a request for identifying a configuration file is received through the pop-up window, identifying whether the first timer expires; and if the first timer expires, transmitting a message identifying a profile ready state.

According to various embodiments of the present disclosure, the method may further comprise: driving a second timer; and if the second timer expires, deleting a pop-up window indicating that the generation of the configuration file is delayed.

According to various embodiments of the present disclosure, the method may further comprise: if the configuration file is ready, a message is received from the configuration file providing server indicating that the configuration file is ready.

The electronic device according to embodiments of the present disclosure may be one of various types of electronic devices. The electronic device may include, for example, a portable communication device (e.g., a smart phone), a computer device, a portable multimedia device, a portable medical device, a camera, a wearable device, or a household appliance. According to the embodiments of the present disclosure, the electronic device is not limited to those described above.

It should be understood that the various embodiments of the disclosure and the terminology used therein are not intended to limit the technical features described herein to the particular embodiments, and include various modifications, equivalents, or alternatives to the respective embodiments. With respect to the description of the drawings, like reference numerals may be used to refer to like or related elements. It is to be understood that the singular form of a noun corresponding to an item may include one or more things unless the relevant context clearly dictates otherwise. As used herein, each of the phrases such as "a or B", "at least one of a and B", "at least one of a or B", "A, B or C", "at least one of A, B and C", and "at least one of A, B or C" may include all possible combinations of items listed together in a respective one of the phrases. As used herein, terms such as "1 st" and "2 nd," or "first" and "second" may be used to simply distinguish one element from another element and do not limit the element in other respects (e.g., importance or order). It will be understood that if the terms "operatively" or "communicatively" are used or the terms "operatively" or "communicatively" are not used, then if an element (e.g., a first element) is referred to as being "coupled to," "connected to," or "connected to" another element (e.g., a second element), it is intended that the element may be directly (e.g., wired) connected to, wireless connected to, or connected to the other element via a third element.

As used herein, the term "module" may include units implemented in hardware, software, or firmware, and may be used interchangeably with other terms (e.g., "logic," "logic block," "portion," or "circuitry"). A module may be a single integral component or a minimal unit or portion thereof adapted to perform one or more functions. For example, according to an embodiment, a module may be implemented in the form of an Application Specific Integrated Circuit (ASIC).

The various embodiments set forth herein may be implemented as software (e.g., a program) comprising one or more instructions stored on a storage medium (e.g., internal memory or external memory) readable by a machine (e.g., a host device or a device performing tasks). For example, a processor of a machine (e.g., a host device or device executing a task) may invoke at least one of the one or more instructions stored in the storage medium and execute it with or without one or more other components under the control of the processor. This allows the machine to be operated according to the at least one instruction invoked to perform at least one function. The one or more instructions may include code generated by a compiler or code executed by an interpreter. The machine-readable storage medium may be provided in the form of a non-transitory storage medium. Wherein the term "non-transitory" merely means that the storage medium is a tangible device and does not include signals (e.g., electromagnetic waves), but the term does not distinguish between locations where data is semi-permanently stored in the storage medium and locations where data is temporarily stored in the storage medium.

According to an embodiment, a method according to various embodiments of the present disclosure may be included and provided in a computer program product. The computer program product may be traded as an article between a seller and a buyer. The computer program product may be distributed in the form of a machine-readable storage medium, such as a compact disk read only memory (CD-ROM), or via an application Store (e.g., a Play Store ^TM ) The computer program product may be published (e.g., downloaded or uploaded) online, or may be distributed (e.g., downloaded or uploaded) directly between two user devices (e.g., smartphones). At least some of the computer program product may be temporarily generated if published online, or at least some of the computer program product may be stored at least temporarily in a machine readable storage medium, such as the memory of a manufacturer's server, an application store's server, or a forwarding server.

Each of the above-described components (e.g., modules or programs) may include a single entity or multiple entities, according to embodiments. According to various embodiments, one or more of the above-described components may be omitted, or one or more other components may be added. Alternatively or additionally, multiple components (e.g., modules or programs) may be integrated into a single component. In this case, according to various embodiments, the integrated component may still perform one or more functions of each of the plurality of components in the same or similar manner as the plurality of components performed by the respective one of the plurality of components prior to integration. According to various embodiments, operations performed by a module, a program, or another component may be performed sequentially, in parallel, repeatedly, or in a heuristic manner, or one or more operations may be performed in a different order or omitted, or one or more other operations may be added.

While the present disclosure has been shown and described with reference to various embodiments thereof, it will be understood by those skilled in the art that various changes in form and details may be made therein without departing from the spirit and scope of the present disclosure as defined by the appended claims and their equivalents.

Claims

1. An electronic device, comprising:

at least one embedded universal integrated circuit card eUICC, each eUICC storing at least one piece of subscriber identity information; and

at least one processor electrically connected to the eUICC,

wherein the at least one processor is configured to:

based on the eUICC, control transmitting a first request message to a first server, the first request message including information regarding operations related to subscription or subscription transfer, and

in response to the transmission of the first request message, receiving a first response message from the first server,

wherein the first response message includes information indicating that a configuration file to be provided for the eUICC is not ready in response to the first request message.

2. The electronic device of claim 1, wherein the first response message includes information indicating that the profile is not ready based on the first server not providing web server-related information to the electronic device for the subscription or the subscription transfer.

3. The electronic device according to claim 1,

wherein the at least one processor is further configured to:

controlling transmission of a second request message to the first server including information related to a service status request based on the first response message including information indicating that a configuration file to be provided for the eUICC is not ready, and

receiving a second response message from the first server in response to the transmission of the second request message,

wherein the second response message includes address information corresponding to a second server providing the configuration file.

4. The electronic device of claim 1, wherein the at least one processor is further configured to:

a request is received for identifying the configuration file,

transmitting a third request message for identifying a download readiness of the profile to a second server providing the profile in response to receiving the request for identifying the profile,

receiving a third response message from the second server in response to the transmission of the third request message, and

based on a third response message including information indicating that the configuration file is ready, control requests the download of the configuration file from the second server.

5. The electronic device of claim 4, further comprising a touch screen,

wherein the at least one processor is further configured to receive, via the touch screen, a request for identifying the profile.

6. An electronic device, comprising:

at least one processor electrically connected to the eUICC,

wherein the at least one processor is configured to:

a request is received for identifying a configuration file,

obtaining, from a communication carrier server, address information corresponding to a profile providing server that provides the profile, based on the address information corresponding to the profile providing server not being identified;

transmitting a message for identifying a preparation state of the profile to the profile providing server based on the address information corresponding to the profile providing server; and

based on identifying that the profile is ready, the profile is downloaded from the profile providing server and stored in the eUICC.

7. The electronic device of claim 6, further comprising a touch screen,

8. The electronic device of claim 6, wherein the at least one processor is further configured to: a request to identify a profile is received before a message corresponding to the profile ready is received.

9. The electronic device of claim 8, wherein a message corresponding to the profile ready is received by a push message.

10. The electronic device of claim 6, wherein the at least one processor is further configured to obtain the address information corresponding to the profile providing server from an authorization server.

11. The electronic device of claim 10, wherein the at least one processor is further configured to:

receiving information about a profile ready state from the authorization server in response to a request for at least one of subscription, opening, or subscription transfer for a communication service, and

based on identifying from the received information regarding the profile ready state that the generation of the profile is delayed, controlling the display of a pop-up window indicating that the generation of the profile is delayed.

12. The electronic device of claim 11, wherein a request to identify the profile is received through the pop-up window.

13. The electronic device of claim 12, wherein the at least one processor is further configured to:

the first timer is driven to be in a state of being,

based on receiving a request for identifying the configuration file through the pop-up window, identifying whether the first timer has expired, and

a message identifying the profile ready state is transmitted based on identifying that the first timer expires.

14. The electronic device of claim 11, wherein the at least one processor is further configured to:

driving a second timer, and

and controlling to delete the pop-up window indicating that the generation of the configuration file is delayed based on the identification of the expiration of the second timer.

15. A method for installing a profile of an embedded subscriber identity module, SIM, in an electronic device comprising at least one embedded universal integrated circuit card, eUICC, storing at least one subscriber identity information and at least one processor electrically connected to the eUICC, the method comprising:

receiving a request for identifying a configuration file;

Obtaining address information corresponding to a profile providing server that provides the profile from a communication carrier server based on not identifying the address information corresponding to the profile providing server;

transmitting a message for identifying a preparation state of the profile to the profile providing server based on address information corresponding to the profile providing server; and