Server, terminal, and control method

Abstract

A server (400) performs control to cause a new terminal (200') to download a profile that is to be set in a built-in type subscriber identification module (250) and to be deleted in an old terminal (200). The server (400) receives, from the new terminal (200'), information indicating whether the download is successful. When the download is unsuccessful, the server (400) performs transmission to cause the old terminal (200) to redownload the profile.

Description

Technical Field

[0001] The present invention relates to a server, a terminal, and a control method for performing wireless communication, and particularly to a server, a terminal, and a control method that support model change of a terminal equipped with an embedded subscriber identification module.

Background Art

[0002] In the GSM Association (GSMA), a Remote Subscriber Identity Module Provisioning (RSP) is defined to download from a network to a terminal a profile composed of data including subscriber information and an application for controlling the use of a communication service when concluding a contract for the use of the communication service (see Non-Patent Document 1).

[0003] In RSP, the terminal sets the downloaded profile in an embedded subscriber identification module (eSIM: Embedded Subscriber Identity Module). Thereby, the terminal can perform line activation processing at the time of concluding a contract for the use of a communication service via a network using the eSIM. Note that the software part where the profile can be rewritten is called an eSIM, while the hardware part is called an eUICC (Embedded Universal Integrated Circuit Card).

[0004] In actual use, it is necessary to activate specific subscriber information in the eSIM. From the terminal / NW (Network), the eSIM is recognized only as a SIM in which only the activated subscriber information is written, and when there is no activated subscriber information, it is recognized as a SIM without subscriber information.

Prior Art Documents

Non-Patent Documents

[0005]

Non-Patent Document 1

Summary of the Invention

[0006] In recent years, the number of terminals equipped with eSIM has been increasing. However, the specifications for changing the model of eSIM-equipped terminals are not currently defined.

[0007] However, for changing the model of eSIM-equipped terminals, since the subscriber information is wirelessly written to a new UIM (User Identity Module), the server needs to determine whether the download is possible and distinguish between the old and new models to prevent cloning and the like.

[0008] On the other hand, if the download fails on the new model, the line will be lost if there is no method to restore communication on the old model.

[0009] Therefore, the present invention has been made in view of such a situation, and an object thereof is to provide a server, a terminal, and a control method that can prevent cloning and the like and restore communication when the download fails on a new model for changing the model of an eSIM-equipped terminal.

[0010] A server (400) according to an aspect of the present invention includes a control unit (440) that controls a new terminal (200') to download a profile that is set in an embedded subscriber identification module (250) and deleted from an old terminal (200), a receiving unit (420) that receives information regarding the success or failure of the download from the new terminal (200'), and a transmitting unit (410) that transmits to cause the old terminal (200) to re-download the profile when the download fails.

[0011] A terminal (200) according to an aspect of the present invention includes a control unit (240) that deletes a profile set in an embedded subscriber identification module (250), and a receiving unit (220) that re-downloads the profile when another terminal (200') fails to download the profile. The control unit (240) re-sets the profile in the embedded subscriber identification module (200).

[0012] A communication method according to an aspect of the present invention includes a step of controlling a new terminal (200') to download a profile that is set in an embedded subscriber identification module (250) and deleted in an old terminal (200), a step of receiving information regarding the success or failure of the download from the new terminal (200'), and a step of transmitting to cause the old terminal (200) to re-download the profile when the download fails.

[0013] A communication method according to an aspect of the present invention includes a step of deleting a profile set in an embedded subscriber identification module (250), a step of re-downloading the profile when another terminal (200') fails to download the profile, and a step of re-setting the profile in the embedded subscriber identification module (200).

Brief Description of the Drawings

[0014]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Mode for Carrying Out the Invention

[0015] Hereinafter, embodiments will be described with reference to the drawings. In addition, the same or similar reference numerals are assigned to the same functions and configurations, and the description thereof will be omitted as appropriate.

[0016] (1) Overall schematic configuration of the communication system FIG. 1 is an overall schematic configuration diagram of the communication system 10 according to the present embodiment.

[0017] As shown in FIG. 1, the communication system 10 includes, as an example, a network 20 such as a 3GPP network, a network 30 such as a non-3GPP network, a radio base station 100, a terminal 200, a contract site 300, a subscription management (SM) server 400, an information management server 600, and a customer management system 500. The terminal is also referred to as User Equipment (UE). The contract site is also referred to as an operator or a communication carrier. Note that the specific configuration of the communication system 10 including the number of network devices (contract site 300, subscription management (SM) server 400, information management server 600, customer management system 500, etc.), the number of radio base stations, and the number of terminals is not limited to the example shown in FIG. 1. For example, the server on the network side may be only one device at the minimum for implementing the present invention. In the following embodiments, at least one device of the radio base station 100, the contract site 300, the subscription management (SM) server 400, the information management server 600, and the customer management system 500 may be omitted, and the function of the device may be held by other devices.

[0018] The network 20 is a network compliant with 5G (NR) (or 6G), such as a 3GPP network, and includes a Next Generation-Radio Access Network (NG-RAN, not shown) and a core network (5G-CN, not shown). The NG-RAN includes NG-RAN Nodes, specifically, radio base stations 100 (gNB or ng-eNB), and is connected to the 5G-CN (or 6G; the same applies hereinafter).

[0019] The radio base station 100 performs wireless communication compliant with NR to 6G between the radio base station 100 and the terminal 200.

[0020] The radio base station 100 and the terminal 200 can support Massive MIMO that generates a more directional beam by controlling radio signals transmitted from a plurality of antenna elements, carrier aggregation (CA) using a plurality of component carriers (CC), and dual connectivity (DC) that simultaneously transmits CCs between a plurality of NG-RAN Nodes and the terminal, as well as Integrated Access and Backhaul (IAB) in which the radio backhaul between radio communication nodes such as gNBs and the radio access to the UE are integrated. Note that the CC is also referred to as a carrier.

[0021] Note that the network 20 may be a network compliant with LTE instead of NR or 6G. In this case, the 3GPP network 20 includes an Evolved Universal Terrestrial Radio Access Network (E-UTRAN) and an Evolved Packet Core (EPC). The E-UTRAN includes radio base stations (eNB or en-gNB) and is connected to the EPC.

[0022] The network 30 is a non-3GPP network or the like, such as a wireless local area network (WLAN) like Wireless Fidelity (Wi-Fi), or a wired LAN. The network 30 is not particularly limited as long as it is a network through which the terminal 200 can access the contract site 300 using a Uniform Resource Locator (URL) or the like.

[0023] When subscribing to a communication service, the terminal 200 executes an RSP that downloads a profile composed of data including subscriber information and an application that controls the use of the communication service from the 3GPP network 20. The profile may be referred to as an in-service profile.

[0024] Subscriber information includes an International Mobile Subscriber Identifier (IMSI) uniquely assigned to a user who uses the communication service, a telephone number uniquely assigned to a user who uses the communication service, contract information including a fee plan applied to the terminal 200, and the like. The subscriber information is provided from the contract site 300.

[0025] In the RSP, when attaching to the 3GPP network 20, the terminal 200 may transmit, via the 3GPP network 20, a download request for a profile corresponding to an AC (Activation Code) received from the network 30 at the time of subscribing to the communication service, to the radio base station 100. When receiving a profile request from the terminal 200, the radio base station 100 may transmit (forward) it to the SM server 400.

[0026] In this embodiment, as will be described later, for the purpose of changing the terminal model, the old terminal 200 deletes the profile, while the new terminal 200' downloads the profile from the SM server 400 via the 3GPP network 20. The terminal 200 installs the downloaded profile in the embedded subscriber identification module (eSIM) 250 described later and activates the profile, thereby enabling the use of communication services in the 3GPP network 20. Note that in this embodiment, if the new terminal 200' fails to download the profile, the old terminal 200' can re-download the profile.

[0027] Note that in this embodiment, the profile may be able to transition between active and inactive states. For example, the old terminal 200 may keep the profile in an inactive state without deleting it until the new terminal 200' successfully downloads the profile, and the old terminal 200 may delete the profile after the new terminal 200' has successfully downloaded it. Note that the active or inactive state of the profile may be controllable by the network. For example, upon receiving instruction information from the network, the terminal 200 may control the active or inactive state of the profile according to the instruction information. Note that the network device that transmits the instruction information may be the information management server 600, the SM server 400, or other devices.

[0028] The contract site 300 is connected to a network (network 20 and / or network 30). When the contract site 300 receives contract information (IMEI, EID, etc.) based on a communication contract, it transmits the contract information to the customer management system 500, and the customer management system 500 may transmit a profile generation request to the SM server 400 based on the contract information. In addition, when changing the model in this embodiment, as an example, when the SM server 400 receives a model change request together with new model information (for example, information in which the identification information (e.g., EID (eUICC Identifier)) of the new terminal 200' and the old terminal 200 are associated) and transmits the new model information to the customer management system 500, the customer management system 500 may receive a profile generation request for requesting profile preparation for the new terminal 200'. This is not limited thereto, and information regarding model change may be transmitted to the SM server 400 via the contract site 300 or the customer management server 500. Note that the customer management system 500 may transmit at least the EID included in the contract information (further, an IMEI, a telephone number, etc. may be added) to the SM server 400. Detailed specific examples will be described later.

[0029] The SM server 400 is connected to a network (network 20 and / or network 30). When the SM server 400 receives a profile generation request, it generates a profile and transmits it to the terminal 200. In the present embodiment, the SM server 400 performs control to cause the new terminal 200' to download a profile that is set in the embedded subscriber identification module (250') and is deleted from the old terminal. For example, the SM server 400 transmits a profile to the new terminal 200' associated with the information about the old terminal 200 and / or to the old terminal 200 associated with the information about the new terminal 200' based on new model information or the like. More specifically, the SM server 400 may generate a profile for the new terminal 200' associated with the old terminal 200 EID based on download new model information or the like including a profile generation request for the new model. Also, when the download of the new terminal 200' fails, the SM server 400 may transmit a profile to the old terminal 200 associated with the new terminal 200' EID.

[0030] Note that the profile initially generated by the SM server 400 may be called a temporary profile. In this case, initially, the official profile is not transmitted to the new terminal 200' and the temporary profile is transmitted. When information on profile deletion is received from the old terminal 200 and / or when success information such as the download of the temporary profile is received from the new terminal 200', the official profile may be configured to be transmitted to the new terminal 200'. Note that the SM server 400 may transmit information (e.g., AC) including the SM address and the Matching ID (identifier associated with the profile) to the customer management server 500 or the like. The customer server 500 may transmit the AC to the contract site 300, and the contract site 300 may transmit the AC to the terminal 200 via the network 30.

[0031] Note that, as an example of the "server" in the present application, the SM server 400 is taken as an example in this embodiment for explanation, but it is not limited thereto. Other network devices (including the customer management system 500, the information management server 600, etc.) may perform part or all of the processing, and the functions can be arbitrarily distributed and implemented.

[0032] The customer management system 500 is connected to the network and manages contract information such as subscriber information. For example, based on the information at the time of contract for a mobile phone, the customer management system 500 holds contract information (for example, the IMEI, EID, etc. of the old and new terminals 200). Further, the customer management system 500 may transmit contract information and the like to the customer management server 500 or the SM server 400. Note that the entity that holds contract information and the like associated with the old and new terminals 200, the entity that receives a request for model change, and the entity that transmits instruction information and the like are arbitrary, and may be any one of, for example, the contract site 300, the SM server 400, the information management server 600, and the customer management system 500. For example, the information management server 600 is connected to the network and holds in a reference table the old and new terminal information that associates the information of the old terminal 200 (the IMEI, EID, etc. of the old terminal 200) with the information of the new terminal 200' (the IMEI, EID, etc. of the new terminal 200'), and may transmit the old and new terminal information to network devices such as the SM server 400 according to requests and inquiries from the network.

[0033] (2) Functional Block Configuration of the Communication System Next, the functional block configuration of the communication system 10 will be described. Specifically, the functional block configurations of the terminal 200 and the SM server 400 will be described. Hereinafter, only the parts related to the features in this embodiment will be described. Therefore, it goes without saying that the terminal 200 and the SM server 600 include other functional blocks that are not directly related to the features in this embodiment. Also, some or all of the functions of the contract site 300, the information management server 600, the customer management system 500, the SM server 400, the radio base station 100, etc. may be held on behalf of by other devices, and the other devices can have the following functional block configuration (transmission unit, reception unit, control unit) of the SM server 400.

[0034] For convenience, first, the functional block configuration diagram of the terminal 200 will be described. FIG. 2 is a functional block configuration diagram of the terminal 200. As shown in FIG. 2, the terminal 200 includes a wireless transmission unit 210, a wireless reception unit 220, and a control unit 240.

[0035] The wireless reception unit 220 receives a downlink signal (DL signal) conforming to NR (or 6G; the same applies hereinafter) from the radio base station 100. In this embodiment, the wireless reception unit 220 functions as a reception unit that receives a profile set in the eSIM from the network 20. More specifically, the wireless communication unit 220 of the new terminal 200' downloads, via the network 20, a profile (which may be the same profile) corresponding to the profile deleted (including the case where it will be deleted in the future) from the old terminal 200 from the SM server 400. Also, the wireless communication unit 220 of the old terminal 200 redownloads a profile (which may be the same profile) corresponding to the deleted profile when the download of the profile fails in the new terminal 200', etc.

[0036] The wireless transmission unit 210 transmits an uplink signal (UL signal) conforming to NR (or 6G) to the radio base station 100, the contract site 300, etc. In the present embodiment, the wireless transmission unit 210 functions as a transmission unit that transmits various types of information related to model change to the network 20 (or 30, the same hereinafter). For example, the wireless transmission unit 210 may transmit and receive model information (IMEI, EID, etc.) between the old and new terminals 200 / 200'. Thereby, information regarding the old and new terminals 200 / 200' can be linked, and information such as old and new terminal information in which the information (IMEI, EID, etc.) of the old terminal 200 and the information (IMEI, EID, etc.) of the new terminal 200' are associated can be generated. In addition, the wireless transmission unit 210 may transmit information regarding the contract to the contract site 300, etc. Further, the wireless transmission unit 210 may transmit profile acquisition instruction information to the new terminal 200'. Also, the wireless transmission unit 210 may transmit a profile download request, etc. to the SM server 400. Specific details will be described later.

[0037] Note that the wireless transmission unit 210 and the wireless reception unit 220 perform wireless communication via a control channel or a data channel.

[0038] The control channel includes a physical downlink control channel (PDCCH), a physical uplink control channel (PUCCH), a physical random access channel (PRACH), etc.

[0039] The data channel includes a physical downlink shared channel (PDSCH), a physical uplink shared channel (PUSCH), etc.

[0040] The control unit 240 has functions such as a Local Profile Assistant (LPA), downloads a profile from the SM server 400, and installs (configures) the profile in the eSIM 250. In the present embodiment, the control unit 240 of the old terminal 200 functions as a control unit that deletes the profile installed (configured) in the eSIM 250. Note that the control unit 240 of the old terminal 200 may reinstall (reconfigure) the redownloaded profile in the eSIM 250 based on profile redownload instruction information or the like due to a failure in downloading the profile in the new terminal 200'. Note that the control unit 240 may set the profile installed in the eSIM 250 to an active / inactive state based on instruction information or the like. For example, the control unit 240 of the old terminal 200 may set the profile to an inactive state until it receives a profile deletion request based on the successful download of the profile by the new terminal 200'.

[0041] Note that the eSIM 250 is a software part where the profile is written. The hardware part where the profile is written is called an embedded universal integrated circuit card (eUICC).

[0042] With the profile installed in the eSIM 250, the network (in other words, an external party or an administrator) can control the active / inactive state of the profile, that is, the available / unavailable state of the eSIM, without physically inserting or removing the subscriber identity module (SIM).

[0043] Note that if the activated profile does not exist in the eSIM 250, the eSIM 250 is recognized by the network side as a SIM in which the profile is not written.

[0044] The eSIM 250 is in a non-removable form from the terminal 200, but is not limited thereto and may be in a removable form from the terminal 200.

[0045] In addition, the control unit 240 controls each functional block that constitutes the terminal 200. The control unit 240 executes an operation to attach to the 3GPP network 20.

[0046] FIG. 3 is a functional block configuration diagram of the SM server 400. As shown in FIG. 3, the SM server 400 includes a transmission unit 410, a reception unit 420, and a control unit 440.

[0047] The reception unit 420 receives various types of information (e.g., new model information, model change requests, old and new terminal information, profile download requests, profile deletion notifications, etc.) via the network. In particular, in the present embodiment, the reception unit 420 functions as a reception unit that receives information regarding the success or failure of profile download from the new terminal 200. Further, the reception unit 420 may query a reference table such as the customer management system 500 or the information management server 600 in which the old and new terminal information is held for information (IMEI, EID, etc.) of the terminal 200 that sent the request, and receive information (IMEI, EID, etc.) of the corresponding (i.e., old and new linked) terminal 200'.

[0048] The transmitting unit 410 transmits various types of information (e.g., profiles, query information, requests, instruction information, etc.) via a network. In the present embodiment, the transmitting unit 410 may query the reference table in which the old and new terminal information is held for information (IMEI, EID, etc.) of the user (the managed person) of the terminal 200 that has transmitted the request, and transmit a profile or the like to the terminal 200' with the corresponding terminal information (IMEI, EID, etc.). Further, the transmitting unit 410 may transmit instruction information for controlling the active or inactive state of the profile to the terminal 200. For example, before transmitting a profile to the new terminal 200', the transmitting unit 410 may transmit instruction information for controlling the profile of the old terminal 200 to an inactive state to the old terminal 200. Then, when the download of the profile is successful on the new terminal 200', the transmitting unit 410 may transmit instruction information for deleting the profile of the old terminal 200 to the old terminal 200. On the other hand, when the download of the profile fails on the new terminal 200', the transmitting unit 410 may transmit instruction information for restoring the profile of the old terminal 200 to an active state to the old terminal 200.

[0049] The control unit 440 controls each functional block that constitutes the information management server 600. In the present embodiment, the control unit 140 functions as a control unit that generates a profile and controls the download state, installation (setting) state, or active / inactive state of the profile in the new and old terminals 200 / 200'. For example, the control unit 440 functions as a control unit that controls the new terminal 200' to download a profile that is set in the eSIM and deleted in the old terminal 200' (including cases where it will be deleted in the future and cases where it has already been deleted). In particular, the control unit 440 controls so that no clone terminals with the same profile are generated in other terminals during a model change. For this reason, in the case of a model change, when the profile is deleted or becomes inactive in one terminal, the control unit 440 controls the other terminal to download the profile, and when the download of the profile fails in the other terminal (including installation failure and activation failure), the control unit 440 may control the one terminal to re-download or activate the profile. Note that the control unit 440 may identify the new and old corresponding terminals by referring to the new and old terminal information held in a reference table such as the SM server 400.

[0050] (3) Operation of the communication system Next, the operation of the communication system 10 related to the new and old model changes will be described. Specifically, as Example 1, operation examples when the download of the profile is successful and when it fails will be described with reference to FIGS. 4 and 5, respectively. Also, as another example (Example 2), operation examples when the download of the profile is successful and when it fails will be described with reference to FIGS. 6 and 7, respectively. Needless to say, the present embodiment is not limited to these specific examples.

[0051] (3.1) Example 1 FIG. 4 is a diagram showing the flow of various information in the communication system 10. FIG. 5 is a diagram showing the operation sequence in the communication system 10.

[0052] As shown in Fig. 4, first, the new terminal 200' transmits the model information (IMEI, EID, etc.) of the new terminal 200' to the old terminal 200 (SA-1). Note that the communication means between the new terminal 200' and the old terminal 200 is arbitrary, and information may be transmitted and received using a short-range communication technology such as Bluetooth.

[0053] Then, the old terminal 200 transmits a model change request (which may include the model information of the old terminal 200) to the SM server 400 together with the new model information of the new terminal 200' (SA-2).

[0054] Then, the SM server 400 transmits the received new model information (which may include the model information of the old terminal) to the customer management system 500 (SA-3).

[0055] Then, the customer management system 500 transmits a profile request for the new terminal 200' to the SM server 400 (SA-4). Note that the customer management system 500 may transmit a profile request to the SM server 400 only when there is a contract corresponding to the received new model information with reference to the contract information it holds.

[0056] Then, as a pre-step before transmitting the newly generated profile to the new terminal 200', the SM server 400 transmits a model change response instructing the old terminal 200 to delete the profile (SA-5).

[0057] Then, the old terminal 200 deletes the profile based on the profile deletion instruction (SA-6).

[0058] Then, the old terminal 200 transmits a profile deletion notification setting a model change flag (for example, setting 0 to 1) to the SM server 400 (SA-7).

[0059] Then, the old terminal 200 transmits instruction information instructing the new terminal 200' to acquire the profile (SA-8).

[0060] Based on the received profile acquisition instruction information, the new terminal 200' sends a profile acquisition request (download request) to the SM server 400 (SA-9).

[0061] Based on the download request for the profile from the new terminal 200', the SM server 400 sends the profile to the new terminal 200' (SA-10).

[0062] When the new terminal 200 downloads the profile, it sets the profile in the eSIM and completes the line activation (SA-11).

[0063] Then, the new terminal 200 sends a completion notification indicating the successful profile setting to the SM server 400 (SA-12).

[0064] Then, the SM server 400 causes the model change flag of the new terminal 200' to transition to completed (for example, 0→1). Note that the method of setting the old and new model change flags by the SM server 400 is arbitrary. For example, the SM server 400 may manage the state where the terminal has downloaded the profile, installed (set) it, or activated it as 1, and manage the state where the terminal has deleted the profile, uninstalled it, or is in an inactive state as 0. And the SM server 400 controls so that the old and new flags do not become set simultaneously (in this case, 1).

[0065] For example, when the flag of the old terminal is set, the SM server 400 controls so as not to transition the new terminal to the state where the flag is set. And when the flag of the old terminal transitions to the state where it is down, the SM server 400 performs control to transition the new terminal to the state where the flag is set. And if the transition to the state where the flag of the new terminal is set fails, the SM server performs control to transition the old terminal back to the state where the flag is set.

[0066] By preventing the co-occurrence of flags, it is possible to prevent the occurrence of cloning or the like in the case of changing the model of an eSIM-equipped terminal. Also, by preventing the state where the flags both go down, when the profile setting fails on one model, communication can be restored on the other terminal.

[0067] Note that the management by this flag is just an example, and in two or more terminals, it is possible to prevent the state where the same profile is available simultaneously, and if it is possible to prevent the state where a certain profile becomes unavailable on any terminal, this embodiment can be implemented with arbitrary information management or the like.

[0068] Here, FIG. 5 is a flowchart showing an operation example when the new terminal 200' fails to download a profile in the above. Since SA-1 to SA-10 are the same as above, the description is omitted.

[0069] As shown in SA-14 of FIG. 5, when the new terminal 200' fails to download a profile from the SM server 400 (SA-14), the new terminal 200' transmits an error response indicating the download failure (which may include new model information) to the SM server 400 (SA-15).

[0070] The SM server 400 that has received the error response (SA-16) transmits re-download instruction information for prompting re-download to the corresponding old terminal 200 based on the old and new terminal information (SA-17).

[0071] Thereby, the old terminal 200 can restore the communication line by downloading and setting the profile again from the SM server 400 (SA-19) (SA-19).

[0072] (3.2) Embodiment 2 Regarding eSIM, the user may input contract information or the like on the contract site 300. Therefore, subsequently, as Embodiment 2, an operation example of a communication system including the contract site 300 will be described with reference to FIGS. 6 (when successful) and 7 (when failed).

[0073] As shown in FIG. 6, first, the old terminal 200 sends contract information to the contract site 300 (SB-1). In this embodiment, this contract information is contract information regarding model change, and as an example, it may include model information (IMEI, EID, etc.) of the old terminal and the new terminal 200'.

[0074] Then, the contract site 300 sends the contract information to the customer management server 500 (SB-2).

[0075] Then, the customer management server 500 sends information (e.g., EID information) linking the model information of the old and new terminals to the SM server 400 (SB-3).

[0076] Then, when the old and new terminals 200 access the SM server 400 (SB-4, 5), the SM server 400 sends the profile to the new model 200' (SB-5). At this time, the SM server 400 may send instruction information to deactivate the profile of the old terminal to the old terminal 200.

[0077] Then, when receiving a notification of completion of profile installation from the new terminal 200' (SA-7), the SM server 400 sends a notification instructing the old terminal 200 to delete the profile (SB-8), and at the same time, sends instruction information to cause the customer management server 500 to delete the old model contract information (SB-9).

[0078] On the other hand, as shown in FIG. 7, when receiving an error notification of failed profile installation (SB-10) from the new terminal 200' (SA-11), or when not receiving a notification of completion of installation for a certain period (SA-12), the SM server 400 sends a notification instructing the old terminal 200 to re-download the profile (SB-14).

[0079] The above is an operation example of this embodiment. As described above, the management method can be arbitrarily implemented as long as it is possible to prevent the profiles from not being available simultaneously and from becoming unavailable on any terminal. For example, the download success notification of the profile may be interpreted or paraphrased as the installation success notification of the profile or the activation success notification of the profile. Similarly, the download failure notification of the profile may be interpreted or paraphrased as the installation failure notification of the profile or the activation failure notification of the profile.

[0080] Similarly, causing the old terminal to delete the profile may be interpreted or paraphrased as uninstalling the profile or deactivating the profile. Also, causing the old terminal to re-download the profile may be interpreted or paraphrased as reinstalling the profile or activating the profile.

[0081] (4) Operations and effects According to the above-described embodiment, control is performed to cause the new terminal (200’) to download the profile that is set in the embedded subscriber identification module (250) and is deleted from the old terminal (200). When information regarding the success or failure of the download is received from the new terminal (200’), if the download fails, it is transmitted to cause the old terminal (200) to re-download the profile.

[0082] Thereby, regarding the model change of the eSIM-equipped terminal, by preventing the same profile from being available simultaneously, it is possible to prevent cloning and the like, and by preventing the state where the same profile cannot be used on any terminal, communication can be restored even when the download fails on the new model.

[0083] Also, according to this embodiment, when the server receives information on download failure or when information on download success is not received, the server transmits the profile to the old terminal.

[0084] As a result, not only when there is an explicit notification from the new terminal that the profile cannot be used, but also when the profile implicitly becomes unavailable from the new terminal, the use of the profile on the old terminal can be restored.

[0085] In addition, according to the present embodiment, the information regarding the success or failure of the download includes information regarding the terminal, and the server transmits the profile to the new terminal associated with the information regarding the old terminal or the old terminal associated with the information regarding the new terminal.

[0086] As a result, the server can transfer the profile from the old terminal to the new terminal or restore the use of the profile from the new terminal to the old terminal when the use of the profile fails on the new terminal, etc., by referring to the information linked with the old and new terminal information.

[0087] In addition, according to the present embodiment, when the download of the profile is successful, the server performs a process of deleting the information regarding the old terminal.

[0088] As a result, when the model change is successful, by deleting the contract information, etc., regarding the old terminal that has become unnecessary, it is possible to contribute to securing resources and reducing the management cost of unnecessary personal information.

[0089] (5) Other Embodiments As described above, the content of the present invention has been described in accordance with the embodiments. However, it is obvious to those skilled in the art that the present invention is not limited to these descriptions, and various modifications and improvements are possible.

[0090] The block diagrams (FIGS. 2 and 3) used in the description of the above-described embodiments show blocks in terms of functions. These functional blocks (components) are realized by any combination of at least one of hardware and software. Also, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one physically or logically combined device, or two or more physically or logically separated devices may be directly or indirectly (for example, using wired, wireless, etc.) connected and realized using these multiple devices. The functional block may be realized by combining software with the above one device or the above multiple devices.

[0091] Functions include, but are not limited to, judgment, decision, determination, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, solution, selection, selection, establishment, comparison, assumption, expectation, regarded as, notification (broadcasting), notification (notifying), communication (communicating), forwarding, configuration (configuring), reconfiguration (reconfiguring), allocation (allocating, mapping), assignment (assigning), etc. For example, a functional block (component) that functions as transmission is referred to as a transmitting unit or a transmitter. As described above, the realization method is not particularly limited in any case.

[0092] Furthermore, the above-described radio base station 100, terminal 200, contract site 300, SM server 400, customer management system 500, and information management server 600 may function as a computer that performs the processing of the wireless communication method of the present disclosure. FIG. 8 is a diagram showing an example of the hardware configuration of the device. As shown in FIG. 8, the device may be configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, and a bus 1007, etc.

[0093] In the following description, the term "device" can be read as a circuit, device, unit, etc. The hardware configuration of the device may be configured to include one or more of each device shown in the figure, or may be configured without including some devices.

[0094] Each functional block of the device is realized by any hardware element of the computer device or a combination of such hardware elements.

[0095] Also, each function in the device is realized by causing a predetermined software (program) to be loaded onto hardware such as the processor 1001 and the memory 1002, so that the processor 1001 performs calculations, controls communication by the communication device 1004, or controls at least one of reading and writing data in the memory 1002 and the storage 1003.

[0096] The processor 1001 controls the entire computer by operating, for example, an operating system. The processor 1001 may be constituted by a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic device, registers, and the like.

[0097] Further, the processor 1001 reads a program (program code), software module, data, etc. from at least one of the storage 1003 and the communication device 1004 into the memory 1002, and executes various processes according to these. As the program, a program that causes the computer to execute at least a part of the operations described in the above embodiments is used. Furthermore, the above various processes may be executed by one processor 1001, or may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. Note that the program may be transmitted from a network via a telecommunication line.

[0098] The memory 1002 is a computer-readable recording medium and may be composed of at least one of, for example, Read Only Memory (ROM), Erasable Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), Random Access Memory (RAM), etc. The memory 1002 may also be referred to as a register, cache, main memory (primary storage device), etc. The memory 1002 can store a program (program code), software module, etc. that can execute the method according to an embodiment of the present disclosure.

[0099] The storage 1003 is a computer-readable recording medium and may be composed of at least one of, for example, optical discs such as Compact Disc ROM (CD-ROM), hard disk drives, flexible disks, magneto-optical disks (e.g., compact discs, digital versatile discs, Blu-ray (registered trademark) discs), smart cards, flash memories (e.g., cards, sticks, key drives), floppy (registered trademark) disks, magnetic strips, etc. The storage 1003 may also be referred to as an auxiliary storage device. The above-mentioned recording medium may be, for example, a database, a server, or other appropriate media including at least one of the memory 1002 and the storage 1003.

[0100] The communication device 1004 is hardware (a transmission / reception device) for performing communication between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, a network controller, a network card, a communication module, etc.

[0101] The communication device 1004 may be configured to include, for example, a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. in order to implement at least one of Frequency Division Duplex (FDD) and Time Division Duplex (TDD).

[0102] The input device 1005 is an input device that receives external input (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.). The output device 1006 is an output device that performs external output (for example, a display, a speaker, an LED lamp, etc.). Note that the input device 1005 and the output device 1006 may have an integrated configuration (for example, a touch panel).

[0103] Also, each device such as the processor 1001 and the memory 1002 is connected by a bus 1007 for communicating information. The bus 1007 may be configured using a single bus, or may be configured using different buses for each device.

[0104] Furthermore, the device may be configured to include hardware such as a microprocessor, a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Programmable Logic Device (PLD), a Field Programmable Gate Array (FPGA), etc., and some or all of the functional blocks may be realized by the hardware. For example, the processor 1001 may be implemented using at least one of these hardware components.

[0105] Also, the notification of information is not limited to the aspects / embodiments described in the present disclosure, and other methods may be used. For example, the notification of information may be implemented by physical layer signaling (e.g., Downlink Control Information (DCI), Uplink Control Information (UCI)), upper layer signaling (e.g., RRC signaling, Medium Access Control (MAC) signaling, broadcast information (Master Information Block (MIB), System Information Block (SIB))), other signals, or a combination thereof. Also, RRC signaling may be referred to as an RRC message, and may be, for example, an RRC connection setup message, an RRC connection reconfiguration message, etc.

[0106] Each aspect / embodiment described in the present disclosure may be applied to at least one of a system using Long Term Evolution (LTE), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, 4th generation mobile communication system (4G), 5th generation mobile communication system (5G), Future Radio Access (FRA), New Radio (NR), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, Ultra Mobile Broadband (UMB), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, Ultra-WideBand (UWB), Bluetooth (registered trademark), other suitable systems, and a next-generation system extended based thereon. Also, a plurality of systems may be combined (e.g., a combination of at least one of LTE and LTE-A and 5G, etc.) and applied.

[0107] The processing procedures, sequences, flowcharts, etc. of each aspect / embodiment described in the present disclosure may be reordered as long as there is no contradiction. For example, regarding the methods described in the present disclosure, the elements of various steps are presented using an exemplary order and are not limited to the specific order presented.

[0108] Specific operations assumed to be performed by a base station in the present disclosure may, in some cases, be performed by its upper node. In a network consisting of one or more network nodes having a base station, it is clear that various operations performed for communication with a terminal can be performed by at least one of the base station and other network nodes other than the base station (for example, but not limited to, MME or S-GW, etc.). Although the case where there is one other network node other than the base station is exemplified above, a combination of a plurality of other network nodes (for example, MME and S-GW) may also be possible.

[0109] Information, signals (such as information) can be output from an upper layer (or lower layer) to a lower layer (or upper layer). They may also be input and output via a plurality of network nodes.

[0110] The input and output information may be stored in a specific location (for example, memory) or may be managed using a management table. The input and output information can be overwritten, updated, or appended. The output information may be deleted. The input information may be transmitted to other devices.

[0111] The determination may be made by a value represented by 1 bit (0 or 1), by a Boolean value (true or false), or by a numerical comparison (for example, comparison with a predetermined value).

[0112] Each aspect / embodiment described in the present disclosure may be used alone, in combination, or switched and used during execution. Also, notification of predetermined information (for example, notification of "being X") is not limited to being explicitly performed, and may be performed implicitly (for example, by not performing notification of the predetermined information).

[0113] Software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc., whether called software, firmware, middleware, microcode, a hardware description language, or by any other name.

[0114] Also, software, instructions, information, etc. may be transmitted and received via a transmission medium. For example, when software is transmitted from a website, server, or other remote source using at least one of wired technologies (such as coaxial cable, optical fiber cable, twisted pair, Digital Subscriber Line (DSL), etc.) and wireless technologies (such as infrared, microwave, etc.), at least one of these wired and wireless technologies is included within the definition of the transmission medium.

[0115] The information, signals, etc. described in the present disclosure may be represented using any of a variety of different technologies. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc., which may be referred to throughout the above description, may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, optical fields or photons, or any combination thereof.

[0116] In addition, with respect to the terms described in the present disclosure and the terms necessary for understanding the present disclosure, they may be replaced with terms having the same or similar meanings. For example, at least one of a channel and a symbol may be a signal (signaling). Also, a signal may be a message. Further, a component carrier (CC) may be referred to as a carrier frequency, a cell, a frequency carrier, or the like.

[0117] The terms "system" and "network" used in the present disclosure are used interchangeably.

[0118] Also, the information, parameters, etc. described in the present disclosure may be represented using absolute values, relative values from a predetermined value, or corresponding other information. For example, a radio resource may be indicated by an index.

[0119] The names used for the above-described parameters are not limiting in any way. Furthermore, mathematical formulas and the like using these parameters may be different from those explicitly disclosed in the present disclosure. Since various channels (e.g., PUCCH, PDCCH, etc.) and information elements can be identified by any suitable names, the various names assigned to these various channels and information elements are not limiting in any way.

[0120] In the present disclosure, terms such as "Base Station (BS)", "radio base station", "fixed station", "NodeB", "eNodeB (eNB)", "gNodeB (gNB)", "access point", "transmission point", "reception point", "transmission / reception point", "cell", "sector", "cell group", "carrier", and "component carrier" may be used interchangeably. The base station may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.

[0121] A base station can accommodate one or more (e.g., three) cells (also called sectors). When a base station accommodates multiple cells, the entire coverage area of the base station can be divided into multiple smaller areas, and each smaller area can also provide communication services by a base station subsystem (e.g., a small indoor base station (Remote Radio Head: RRH)).

[0122] The term "cell" or "sector" refers to part or all of the coverage area of at least one of the base station and the base station subsystem that provides communication services within this coverage.

[0123] In the present disclosure, terms such as "Mobile Station (MS)", "user terminal", "User Equipment (UE)", and "terminal" may be used interchangeably.

[0124] A mobile station may also be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable term.

[0125] At least one of the base station and the mobile station may also be referred to as a transmitting device, a receiving device, a communication device, etc. Note that at least one of the base station and the mobile station may be a device mounted on a moving body, the moving body itself, etc. The moving body may be a vehicle (e.g., a car, an airplane, etc.), a moving body that moves unmanned (e.g., a drone, a self-driving vehicle, etc.), or a robot (humanoid or non-humanoid). Note that at least one of the base station and the mobile station also includes a device that does not necessarily move during communication operation. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.

[0126] Also, the base station in the present disclosure may be read as a mobile station (user terminal, the same hereinafter). For example, for a configuration in which communication between the base station and the mobile station is replaced with communication between a plurality of mobile stations (which may be referred to as, for example, Device-to-Device (D2D), Vehicle-to-Everything (V2X), etc.), each aspect / embodiment of the present disclosure may be applied. In this case, the functions of the base station may be configured as functions of the mobile station. Also, terms such as "uplink" and "downlink" may be read as terms corresponding to communication between terminals (e.g., "side"). For example, an uplink channel, a downlink channel, etc. may be read as a side channel.

[0127] Similarly, the mobile station in the present disclosure may be read as a base station. In this case, the functions of the mobile station may be configured as functions of the base station.

[0128] The wireless frame may be composed of one or more frames in the time domain. Each of the one or more frames in the time domain may be called a subframe.

[0129] The subframe may further be composed of one or more slots in the time domain. The subframe may have a fixed time length (e.g., 1 ms) independent of numerology.

[0130] Numerology may be communication parameters applied to at least one of transmission and reception of a certain signal or channel. Numerology may indicate, for example, at least one of subcarrier spacing (SCS), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI), number of symbols per TTI, wireless frame configuration, specific filtering processing performed by the transceiver in the frequency domain, specific windowing processing performed by the transceiver in the time domain, etc.

[0131] The slot may be composed of one or more symbols (Orthogonal Frequency Division Multiplexing (OFDM) symbols, Single Carrier Frequency Division Multiple Access (SC-FDMA) symbols, etc.) in the time domain. The slot may be a time unit based on numerology.

[0132] The slot may include a plurality of mini-slots. Each mini-slot may be composed of one or more symbols in the time domain. Also, the mini-slot may be called a sub-slot. The mini-slot may be composed of a smaller number of symbols than the slot. The PDSCH (or PUSCH) transmitted in a time unit larger than the mini-slot may be called PDSCH (or PUSCH) mapping type A. The PDSCH (or PUSCH) transmitted using the mini-slot may be called PDSCH (or PUSCH) mapping type B.

[0133] The radio frame, sub-frame, slot, mini-slot, and symbol all represent time units when transmitting signals. Different names corresponding to each of them may also be used.

[0134] For example, one sub-frame may be called a transmission time interval (TTI), or a plurality of consecutive sub-frames may be called TTI, or one slot or one mini-slot may be called TTI. That is, at least one of the sub-frame and TTI may be the sub-frame (1 ms) in the existing LTE, or a period shorter than 1 ms (for example, 1 - 13 symbols), or a period longer than 1 ms. Note that the unit representing TTI may be called a slot, mini-slot, etc. instead of a sub-frame.

[0135] Here, TTI refers to, for example, the minimum time unit for scheduling in wireless communication. For example, in the LTE system, the base station performs scheduling to allocate radio resources (frequency bandwidth, transmission power, etc. that can be used in each user terminal) to each user terminal in units of TTI. Note that the definition of TTI is not limited to this.

[0136] The TTI may be a transmission time unit such as a channel-encoded data packet (transport block), code block, codeword, etc., or may be a processing unit such as scheduling and link adaptation. When the TTI is given, the time interval (e.g., number of symbols) in which a transport block, code block, codeword, etc. are actually mapped may be shorter than the TTI.

[0137] Note that when one slot or one mini-slot is called a TTI, one or more TTIs (i.e., one or more slots or one or more mini-slots) may be the minimum time unit for scheduling. Also, the number of slots (mini-slots) constituting the minimum time unit for the scheduling may be controlled.

[0138] A TTI having a time length of 1 ms may be called a normal TTI (TTI in LTE Rel.8-12), normal TTI, long TTI, normal subframe, normal subframe, long subframe, slot, etc. A TTI shorter than the normal TTI may be called a shortened TTI, short TTI, partial TTI (partial or fractional TTI), shortened subframe, short subframe, mini-slot, sub-slot, slot, etc.

[0139] Note that a long TTI (e.g., normal TTI, subframe, etc.) may be read as a TTI having a time length exceeding 1 ms, or a short TTI (e.g., shortened TTI, etc.) may be read as a TTI having a TTI length less than that of the long TTI and not less than 1 ms.

[0140] A resource block (RB) is a resource allocation unit in the time domain and the frequency domain, and in the frequency domain, it may include one or a plurality of consecutive subcarriers. The number of subcarriers included in the RB may be the same regardless of the numerology, for example, it may be 12. The number of subcarriers included in the RB may be determined based on the numerology.

[0141] Also, the time domain of the RB may include one or more symbols and may have a length of 1 slot, 1 mini-slot, 1 sub-frame, or 1 TTI. 1 TTI, 1 sub-frame, etc. may each be composed of one or more resource blocks.

[0142] Note that one or more RBs may be referred to as Physical Resource Block (PRB), Sub-Carrier Group (SCG), Resource Element Group (REG), PRB pair, RB pair, etc.

[0143] Also, a resource block may be composed of one or more Resource Elements (REs). For example, 1 RE may be a radio resource area of 1 sub-carrier and 1 symbol.

[0144] A Bandwidth Part (BWP) (which may also be called a partial bandwidth, etc.) may represent a subset of consecutive common resource blocks (common RBs) for a certain numerology in a certain carrier. Here, the common RB may be specified by the index of the RB based on the common reference point of the carrier. A PRB is defined within a certain BWP and may be numbered within that BWP.

[0145] The BWP may include a BWP for UL (UL BWP) and a BWP for DL (DL BWP). One or more BWPs may be set within one carrier for a UE.

[0146] At least one of the set BWPs may be active, and the UE may not be assumed to transmit and receive a predetermined signal / channel outside the active BWP. Note that "cell", "carrier", etc. in the present disclosure may be read as "BWP".

[0147] The structures such as the above-mentioned radio frames, sub-frames, slots, mini-slots, and symbols are merely illustrative. For example, the number of sub-frames included in a radio frame, the number of slots per sub-frame or radio frame, the number of mini-slots included in a slot, the number of symbols and RBs included in a slot or mini-slot, the number of sub-carriers included in an RB, and the number of symbols, symbol length, Cyclic Prefix (CP) length, etc. within a TTI can be variously changed.

[0148] The terms "connected" and "coupled", or any variations thereof, mean any direct or indirect connection or coupling between two or more elements, and can include the presence of one or more intermediate elements between two elements "connected" or "coupled" to each other. The coupling or connection between elements can be physical, logical, or a combination thereof. For example, "connected" may be read as "accessed". As used in this disclosure, two elements can be considered to be "connected" or "coupled" to each other using at least one of one or more electric wires, cables, and printed electrical connections, and also, by way of some non-limiting and non-exhaustive examples, electromagnetic energy having wavelengths in the radio frequency region, microwave region, and optical (both visible and invisible) region.

[0149] The reference signal can also be abbreviated as Reference Signal (RS) and may be called a Pilot depending on the applicable standard.

[0150] As used in this disclosure, the description "based on" does not mean "based only on" unless otherwise specified. In other words, the description "based on" means both "based only on" and "based at least on".

[0151] Any reference in this disclosure to an element using terms such as "first", "second", etc. does not generally limit the quantity or order of those elements. These terms can be used in this disclosure as a convenient way to distinguish between two or more elements. Thus, the reference to the first and second elements does not mean that only two elements can be employed there, or that the first element must precede the second element in any way.

[0152] In this disclosure, when terms such as "include", "including" and their variants are used, these terms are intended to be inclusive, similar to the term "comprising". Further, the term "or" used in this disclosure is not intended to be an exclusive disjunction.

[0153] In this disclosure, for example, when articles are added by translation, as in the case of a, an and the in English, this disclosure may include that the nouns following these articles are in the plural form.

[0154] As used herein, the terms "determining" and "deciding" may encompass a wide variety of operations. "Determining" and "deciding" may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up (e.g., searching a table, database, or other data structure), ascertaining, and considering something as having been "determined" or "decided". "Determining" and "deciding" may also include receiving (e.g., receiving information), transmitting (e.g., transmitting information), inputting, outputting, accessing (e.g., accessing data in a memory), and considering something as having been "determined" or "decided". "Determining" and "deciding" may further include resolving, selecting, choosing, establishing, comparing, and considering something as having been "determined" or "decided". That is, "determining" and "deciding" may include considering something as having been "determined" or "decided" based on some operation. Also, "determining (deciding)" may be construed as "assuming", "expecting", "considering", etc.

[0155] As used in this disclosure, the term "A and B are different" may mean "A and B are different from each other". Note that the term may also mean "A and B are each different from C". Terms such as "separated", "coupled", etc. may be construed in the same manner as "different".

[0156] As described in detail above, it is obvious to those skilled in the art that the present disclosure is not limited to the embodiments described in the present disclosure. The present disclosure can be implemented in modified and changed forms without departing from the spirit and scope of the present disclosure defined by the claims. Therefore, the description of the present disclosure is for the purpose of illustration and does not have any limiting meaning for the present disclosure.

Explanation of Signs

[0157] 10 Communication system 20 (3GPP) network 30 (Non-3GPP) network 100 Radio base station 200 Terminal 210 Wireless transmission unit 220 Wireless reception unit 250 eSIM 240 Control unit 300 Contract site 400 Subscription (SM) management server 410 Transmission unit 420 Reception unit 440 Control unit 500 Customer management system 600 Information management server 1001 Processor 1002 Memory 1003 Storage 1004 Communication device 1005 Input device 1006 Output device 1007 Bus

Claims

1. A control unit that controls the new terminal to download the profile deleted from the old terminal, which is set in the embedded subscriber identification module; A receiving unit that receives information regarding the success or failure of the download from the new terminal; A transmitting unit that transmits the profile to the old terminal in order to cause the old terminal to download it again when the download fails; A server comprising the above.

2. The server according to claim 1, wherein the transmitting unit transmits the profile to the old terminal when the receiving unit receives information of download failure or when the receiving unit does not receive information of download success.

3. The information regarding the success or failure of the download includes information regarding the terminal, The server according to claim 1 or 2, wherein the transmitting unit transmits the profile to the new terminal associated with the information regarding the old terminal or the old terminal associated with the information regarding the new terminal.

4. The server according to any one of claims 1 to 3, wherein the control unit deletes information regarding the old terminal when the download is successful.

5. A terminal, comprising: A control unit that deletes the profile set in the embedded subscriber identification module; A receiving unit that redownloads the deleted profile when another terminal fails to download the profile of the terminal; The control unit resets the profile in the embedded subscriber identification module. A terminal.

6. A control method performed by a server, comprising: A step of controlling the new terminal to download the profile deleted from the old terminal, which is set in the embedded subscriber identification module; A step of receiving information regarding the success or failure of the download from the new terminal; A step of transmitting the profile to the old terminal in order to cause the old terminal to download it again when the download fails. A control method including the above steps.

7. A control method performed by a terminal, comprising: A step of deleting the profile set in the embedded subscriber identification module; A step of redownloading the deleted profile when another terminal fails to download the profile of the terminal; A step of resetting the profile in the embedded subscriber identification module. A control method including the above steps.

Images