Communication device and communication method

Abstract

To propose a highly convenient communication apparatus and communication method.SOLUTION: A communication apparatus has a function related to storage and deletion of a profile regarding wireless communication. The communication apparatus includes: a determination unit configured to determine whether or not an end condition of use of the profile is satisfied; and an output control unit configured to execute an inquiry about deletion of the profile via a user interface when the end condition is satisfied.SELECTED DRAWING: Figure 11

Description

[Technical Field]

[0001] The present disclosure relates to a communication device and a communication method. [Background technology]

[0002] In many cases, communication devices such as smartphones can use predetermined wireless communications (e.g., cellular networks) by inserting a SIM (Subscriber Identity Module) card that stores information related to wireless communications (e.g., subscriber information) into the communication device. In recent years, communication devices that support eSIM (Embedded SIM) have become increasingly popular as communication devices that support RSP (Remote SIM Provisioning). [Prior art documents] [Non-patent literature]

[0003] [Non-Patent Document 1] SGP.21 V2.4, “RSP Architecture”, GSM Association, 03 August 2021 Summary of the Invention [Problem to be solved by the invention]

[0004] RSP-compatible communication devices allow wireless communication information (hereinafter referred to as a profile) to be rewritten without replacing the SIM card. This profile can be downloaded from a server on the network. Therefore, the widespread use of RSP is expected to lead to increased use of temporary wireless communication limited to a specific location and / or period.

[0005] While RSP improves the convenience of communication devices, it can also cause inconvenience to communication devices. For example, because multiple profiles can be stored in a communication device, unnecessary profiles may remain in the communication device.

[0006] Therefore, the present disclosure proposes a highly convenient communication device and communication method.

[0007] It should be noted that the above problem or object is merely one of multiple problems or objects that can be solved or achieved by multiple embodiments disclosed in this specification. [Means for solving the problem]

[0008] In order to solve the above problem, one form of communication device according to the present disclosure is a communication device having functions for saving and deleting profiles related to wireless communication, and is equipped with a determination unit that determines whether a termination condition for use of the profile is met, and an output control unit that, when the termination condition is met, executes an inquiry regarding the deletion of the profile via a user interface. [Brief explanation of the drawings]

[0009] [Figure 1] FIG. 10 is a diagram showing a state in which a plurality of profiles remain in a terminal device. [Figure 2] FIG. 1 is a diagram illustrating a configuration example of a communication system according to an embodiment of the present disclosure. [Figure 3] FIG. 2 is a diagram illustrating a configuration example of a server according to an embodiment of the present disclosure. [Figure 4] FIG. 1 is a diagram illustrating a configuration example of a terminal device according to an embodiment of the present disclosure. [Figure 5] 1 is a diagram illustrating an example of an RSP architecture configuration applied to a communication system according to an embodiment of the present invention. [Figure 6] 10 is a flowchart illustrating an example of an end condition setting process. [Figure 7] FIG. 10 is a diagram illustrating an example of a user interface for guiding to a list screen of installed profiles. [Figure 8] FIG. 10 is a diagram illustrating an example of a user interface for inquiring whether or not to set an end condition. [Figure 9] FIG. 10 is a diagram illustrating an example of a user interface for setting an end condition. [Figure 10]FIG. 10 is a diagram illustrating an example of a user interface for notifying a user of a termination condition. [Figure 11] 10 is a flowchart illustrating an example of a profile management process. [Figure 12] FIG. 10 is a diagram illustrating an example of a user interface for inquiring of a user about deleting a profile. [Figure 13] FIG. 10 is a diagram showing another example of a user interface for inquiring of a user about deleting a profile. [Figure 14] FIG. 10 is a diagram showing another example of a user interface for inquiring of a user about deleting a profile. [Figure 15] FIG. 10 is a diagram showing another example of a user interface for inquiring of a user about deleting a profile. [Figure 16] FIG. 10 is a diagram showing another example of a user interface for inquiring of a user about deleting a profile. [Figure 17] FIG. 10 is a diagram showing another example of a user interface for inquiring of a user about deleting a profile. [Figure 18] FIG. 10 illustrates additional requirements for profile metadata. [Figure 19] FIG. 1 illustrates additional requirements for LPA. DETAILED DESCRIPTION OF THE INVENTION

[0010] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings. In the following embodiments, the same components are designated by the same reference numerals, and redundant description will be omitted.

[0011] Furthermore, in this specification and drawings, multiple components having substantially the same functional configuration may be distinguished by adding different numbers after the same reference symbol. For example, multiple components having substantially the same functional configuration may be distinguished as necessary, such as terminal devices 201 and 202. However, if there is no need to particularly distinguish between multiple components having substantially the same functional configuration, only the same reference symbol is used. For example, if there is no need to particularly distinguish between terminal devices 201 and 202, they will simply be referred to as terminal device 20.

[0012] One or more embodiments (including examples and modifications) described below can be implemented independently. However, at least a portion of the embodiments described below may be implemented in appropriate combination with at least a portion of another embodiment. These embodiments may include novel features that are different from one another. Therefore, these embodiments may contribute to solving different purposes or problems and may produce different effects.

[0013] <<1. Overview>> Terminal devices that support Remote SIM Provisioning (RSP) are becoming increasingly popular. For example, in recent years, terminal devices that support Embedded SIM (eSIM) are becoming increasingly popular. RSP-compatible terminal devices allow wireless communication information (hereinafter referred to as a profile) to be rewritten without replacing the SIM card.

[0014] Here, a profile is information related to wireless communication, and is data that records information about the service provider (carrier) and subscriber information (for example, the ICCID assigned to the eSIM). The ICCID (IC Card Identifier) ​​is a unique number used to identify the profile.

[0015] The profile may be an eSIM profile. The eSIM profile is a profile used in an eSIM-enabled communication device. For example, the eSIM profile is a combination of data and applications to be provisioned on an eUICC for the purpose of providing services. An eUICC (Embedded UICC) is a UICC (Universal Integrated Circuit Card) that enables local management of profiles in a secure manner. In the following description, the eSIM profile may be simply referred to as a profile.

[0016] This profile can be downloaded from a server on the network. Therefore, as RSP becomes more widespread, it is expected that the use of temporary wireless communications limited in location and / or time will increase. While RSP improves the convenience of communication devices, it can also make communication devices inconvenient. For example, because multiple profiles can be stored in a terminal device, unnecessary profiles may remain in the communication device.

[0017] For example, suppose an event organizer distributes a two-dimensional code (e.g., a QR code (registered trademark)) of an eSIM profile that enables the use of local 5G at the event venue, and a user uses the two-dimensional code to download the eSIM profile to their terminal device. Since local 5G cannot be used outside the event venue, the downloaded eSIM profile should no longer be necessary once the user leaves the event venue. However, if the user does not delete this eSIM profile, it will remain in the terminal device.

[0018] Also, suppose an eSIM profile that enables wireless communication of a specified amount of data is distributed in a magazine supplement or on a website, and a user downloads the eSIM profile to their terminal device. Once the specified amount of data has been used, the downloaded eSIM profile should no longer be needed. However, if the user does not delete the eSIM profile, the profile will remain in the terminal device.

[0019] FIG. 1 shows a diagram in which multiple profiles remain in a terminal device. In the example of FIG. 1, the profiles stored in the terminal device, their status (enabled / disabled), and profile type (downloadable SIM (e.g., eSIM)) are displayed on a display provided on the terminal device. AAA., BBB., CCC., DDD., EEE., and FFF. each indicate a profile. The profile status and type are displayed directly below each profile. Here, a profile status of "disabled" indicates that the corresponding profile is not enabled (not currently in use) in the terminal device. Furthermore, a profile status of "enabled" indicates that the corresponding profile is enabled (currently in use) in the terminal device. In other words, the profile status of "enabled" or "disabled" does not directly relate to whether or not there is a current line contract with an operator corresponding to the profile. Therefore, in the example of Figure 1, for example, Profile AAA, Profile BBB, and Profile CCC, which have an "invalid" profile status, remain in the terminal device even though at least one of them may no longer be usable (e.g., unable to communicate data) due to contract expiration, non-compliance with terms of use, etc. Having unused profiles remain in the terminal device can cause inconvenience to the user, such as causing the next profile download to fail.

[0020] Therefore, in this embodiment, the above problem is solved as follows.

[0021] The terminal device of this embodiment has a function for saving and deleting profiles related to wireless communication. For example, the terminal device of this embodiment has an LPA (Local Profile Assistant) for managing eSIM profiles. The LPA has a function for recording multiple profiles in the terminal device (for example, the memory of the eUICC).

[0022] The terminal device of this embodiment is configured to determine whether a condition for terminating the use of a profile is met. The termination condition may include at least one of the following: the expiration date set in the profile has been reached; the user has left the usage area set in the profile; the data usage amount set in the profile has been reached; and the profile has not been used for a predetermined period of time. If the terminal device determines that the termination condition is met, it queries the user via the user interface regarding the deletion of the profile. If the terminal device receives a response from the user requesting the deletion of the profile, it deletes the profile.

[0023] This makes it easier to manage profiles, improving the convenience of the terminal device.

[0024] For example, by providing users with an opportunity to delete profiles that are no longer valid or are not being used effectively, it is possible to encourage them to transfer profiles to other eSIM-compatible devices or cancel profiles that are no longer needed. Deleting unused profiles is also desirable from the perspective of making effective use of the limited number of ICCIDs.

[0025] Furthermore, by giving the user an opportunity to delete profiles that are not valid or not being used effectively, it is possible to increase the free memory capacity within the eUICC.

[0026] The outline of this embodiment has been described above, and the communication system 1 according to this embodiment will now be described in detail.

[0027] <<2. Communication System Configuration>> First, the configuration of the communication system 1 will be described.

[0028] FIG. 2 is a diagram illustrating a configuration example of a communication system 1 according to an embodiment of the present disclosure. The communication system 1 includes a server 10 and a terminal device 20. The communication system 1 may include a plurality of servers 10 and a plurality of terminal devices 20. In the example of FIG. 2, the communication system 1 includes servers 101, 102, etc. as the servers 10, and includes terminal devices 201, 202, 203, etc. as the terminal devices 20. The terminal device 20 may be configured to be connectable to a plurality of networks. In the example of FIG. 2, the terminal device 20 is configured to be connectable to a network N1 and a network N2. The terminal device 20 connects to the server 10 via the network N1 or the network N2.

[0029] The networks N1 and N2 are communication networks such as, for example, a local area network (LAN), a wide area network (WAN), a cellular network, a fixed telephone network, a regional Internet Protocol (IP) network, or the Internet. The networks N1 and N2 may include a wired network or a wireless network. The networks N1 and N2 may also include a core network. The core network is, for example, an Evolved Packet Core (EPC) or a 5G Core network (5GC). Of course, the network N may also be a data network connected to the core network. The data network may be a service network of a telecommunications carrier, for example, an IP Multimedia Subsystem (IMS) network. The data network may also be a private network such as an in-house network.

[0030] 2, only two networks are shown, but the number of networks is not limited to two. For example, the networks to which the terminal device 20 can connect may be a plurality of cellular networks operated by different telecommunications carriers and a wireless LAN network (for example, Wi-Fi (registered trademark)).

[0031] The terminal device 20 may be able to connect to the network using multiple communication paths. In this case, at least one of the multiple communication paths may be a wireless communication path. For example, the communication path may be a wireless communication path (wireless access network) between the terminal device 20 and a base station. Also, the communication path may be a wireless communication path between the terminal device 20 and an access point. Of course, the multiple communication paths may include a wired communication path (for example, a wired LAN). Note that the communication path may be the network itself.

[0032] When the multiple communication paths include a wireless communication path, the terminal device 20 may be configured to connect to a network using a radio access technology (RAT) such as LTE (Long Term Evolution), NR (New Radio), Wi-Fi, or Bluetooth (registered trademark). In this case, the terminal device 20 may be configured to be able to use different radio access technologies (wireless communication methods). For example, the terminal device 20 may be configured to be able to use NR and Wi-Fi. Furthermore, the terminal device 20 may be configured to be able to use different cellular communication technologies (for example, LTE and NR). LTE and NR are types of cellular communication technologies that enable mobile communication of terminal devices by arranging multiple areas covered by base stations in the form of cells.

[0033] In the following description, "LTE" includes LTE-Advanced (LTE-A), LTE-A Pro (LTE-Advanced Pro), and EUTRA (Evolved Universal Terrestrial Radio Access). NR includes NRAT (New Radio Access Technology) and FEUTRA (Further EUTRA). A single base station may manage multiple cells. In the following description, a cell compatible with LTE is referred to as an LTE cell, and a cell compatible with NR is referred to as an NR cell.

[0034] NR is the next generation (5th generation) radio access technology after LTE (4th generation communications including LTE-Advanced and LTE-Advanced Pro). NR is a radio access technology that can support various use cases, including eMBB (Enhanced Mobile Broadband), mMTC (Massive Machine Type Communications), and URLLC (Ultra-Reliable and Low Latency Communications). NR is being studied with the aim of creating a technical framework that can support the usage scenarios, requirements, and deployment scenarios of these use cases.

[0035] The terminal device 20 may be able to connect to a network using a wireless access technology (wireless communication method) other than LTE, NR, Wi-Fi, or Bluetooth. For example, the terminal device 20 may be able to connect to a network using LPWA (Low Power Wide Area) communication. Furthermore, the terminal device 20 may be able to connect to a network using proprietary wireless communication.

[0036] Here, LPWA communication refers to wireless communication that enables low-power wide-range communication. For example, LPWA wireless refers to IoT (Internet of Things) wireless communication that uses specified low-power wireless (e.g., 920 MHz band) or ISM (Industry-Science-Medical) band. Note that the LPWA communication used by the terminal device 20 may be compliant with the LPWA standard. Examples of LPWA standards include ELTRES, ZETA, SIGFOX, LoRaWAN, and NB-IoT. Of course, the LPWA standard is not limited to these, and other LPWA standards may also be used.

[0037] The multiple communication paths may include a virtual network. For example, the multiple communication paths to which the terminal device 20 can connect may include a virtual network such as a VLAN (Virtual Local Area Network) and a physical network such as an IP communication path. In this case, the terminal device 20 may perform route control based on a route control protocol such as OSPF (Open Shortest Path First) or BGP (Border Gateway Protocol).

[0038] Additionally, the multiple communication paths may include one or more overlay networks, or may include one or more network slicings.

[0039] The devices in the diagram may be considered devices in a logical sense, i.e., some or all of the devices in the diagram may be realized by virtual machines (VMs), containers, Dockers, etc., and may be physically implemented on the same hardware.

[0040] In this embodiment, a communication device is a device having a communication function, and in the example of Fig. 2, at least the terminal device 20 is a communication device. The server 10 may also be considered as a communication device.

[0041] The following describes in detail the configuration of each device that makes up the communication system 1. Note that the configuration of each device shown below is merely an example. The configuration of each device may be different from the configuration shown below.

[0042] <2-1. Server configuration> First, the configuration of the server 10 will be described.

[0043] The server 10 is an information processing device (computer) that provides various services to the terminal device 20 via a network (for example, networks N1 and N2). For example, the server 10 may be a server called SM-DP+ (Subscription Manager - Data Preparation +) or a server called SM-DS (Subscription Manager - Discovery Server). The SM-DP+ is a server that serves to transmit profiles to the terminal device 20. The SM-DS is a server that serves to provide the addresses of one or more SM-DP+ to the terminal device 20.

[0044] The server 10 is not limited to the above-mentioned servers (SM-DP+, SM-DS). For example, the server 10 may be an application server or a web server. The server 10 may be a PC server, a mid-range server, or a mainframe server. The server 10 may also be an information processing device that performs data processing (edge ​​processing) near a user or a terminal. For example, the server 10 may be an information processing device (computer) attached to or built into a base station. Of course, the server 10 may also be an information processing device that performs cloud computing.

[0045] FIG. 3 is a diagram illustrating an example configuration of a server 10 according to an embodiment of the present disclosure. The server 10 includes a storage unit 11, a communication unit 12, and a control unit 13. Note that the configuration illustrated in FIG. 3 is a functional configuration, and the hardware configuration may be different from this. Furthermore, the functions of the server 10 may be distributed and implemented in multiple physically separated configurations. For example, the server 10 may be configured by multiple information processing devices.

[0046] The storage unit 11 is a data readable / writable storage device such as a dynamic random access memory (DRAM), a static random access memory (SRAM), a flash memory, or a hard disk. The storage unit 11 functions as a storage means of the server 10. The storage unit 11 stores prediction models (learning models) to be distributed to the terminal device 20, such as a quality prediction model and an intention prediction model. This information will be described later.

[0047] The communication unit 12 is a communication interface for communicating with other devices. For example, the communication unit 12 is a network interface. For example, the communication unit 12 is a LAN (Local Area Network) interface such as a NIC (Network Interface Card). The communication unit 12 may be a wired interface or a wireless interface. The communication unit 12 functions as a communication means of the server 10. The communication unit 12 communicates with the terminal devices 20 and 30 under the control of the control unit 13.

[0048] The control unit 13 is a controller that controls each unit of the server 10. The control unit 13 is realized by a processor such as a CPU (Central Processing Unit) or an MPU (Micro Processing Unit). For example, the control unit 13 is realized by the processor executing various programs stored in a storage device inside the server 10 using a RAM (Random Access Memory) or the like as a working area. The control unit 13 may also be realized by an integrated circuit such as an ASIC (Application Specific Integrated Circuit) or an FPGA (Field Programmable Gate Array). The CPU, MPU, ASIC, and FPGA can all be considered as controllers.

[0049] <2-2. Terminal Device Configuration> Next, the configuration of the terminal device 20 will be described.

[0050] The terminal device 20 is a communication device that communicates with other communication devices such as base stations and access points. The terminal device 20 is configured to be connectable to a plurality of communication paths. For example, the terminal device 20 may be configured to be connectable to two communication paths, Wi-Fi (registered trademark) and a cellular network.

[0051] The terminal device 20 may be any type of computer. For example, the terminal device 20 may be a mobile terminal such as a mobile phone, a smart device (smartphone or tablet), a personal digital assistant (PDA), or a notebook PC. The terminal device 20 may also be a wearable device such as a smart watch. The terminal device 20 may also be an xR device such as an augmented reality (AR) device, a virtual reality (VR) device, or a mixed reality (MR) device. The terminal device 20 may also be an imaging device (e.g., a camcorder) equipped with a communication function, or a motorcycle or mobile broadcast van equipped with a communication device such as a field pickup unit (FPU). The terminal device 20 may also be an M2M (machine to machine) device or an IoT (Internet of Things) device. The terminal device 20 may also be a router having multiple communication paths.

[0052] Furthermore, the terminal device 20 may be capable of LPWA communication with other communication devices (for example, base stations, access points, and other terminal devices 20). The wireless communication used by the terminal device 20 may be wireless communication using millimeter waves. Note that the wireless communication used by the terminal device 20 may be wireless communication using radio waves, or wireless communication using infrared rays or visible light (optical wireless).

[0053] Furthermore, the terminal device 20 may be a mobile device. The mobile device is a wireless communication device that can move. In this case, the terminal device 20 may be a wireless communication device installed in the mobile device, or may be the mobile device itself. For example, the terminal device 20 may be a vehicle that moves on a road, such as an automobile, a bus, a truck, or a motorcycle, or a wireless communication device mounted on the vehicle. The mobile device may be a mobile terminal, or may be a mobile device that moves on land, underground, on water, or underwater. The mobile device may be a mobile device that moves within the atmosphere, such as a drone or a helicopter, or may be a mobile device that moves outside the atmosphere, such as an artificial satellite.

[0054] The terminal device 20 may simultaneously connect to and communicate with multiple base stations or multiple cells. For example, when one base station supports a communication area through multiple cells (e.g., pCell, sCell), the multiple cells can be bundled together using carrier aggregation (CA), dual connectivity (DC), or multi-connectivity (MC) technology to enable communication between the base station and the terminal device 20. Alternatively, the terminal device 20 can communicate with the multiple base stations via cells of different base stations using coordinated multi-point transmission and reception (CoMP).

[0055] Fig. 4 is a diagram illustrating an example configuration of a terminal device 20 according to an embodiment of the present disclosure. The terminal device 20 includes a storage unit 21, a communication unit 22, a control unit 23, an input unit 24, and an output unit 25. Note that the configuration illustrated in Fig. 4 is a functional configuration, and the hardware configuration may be different from this. Furthermore, the functions of the terminal device 20 may be distributed and implemented in multiple physically separated configurations.

[0056] The storage unit 21 is a storage device capable of reading and writing data, such as a DRAM, an SRAM, a flash memory, or a hard disk. The storage unit 21 may be a memory within the eUICC. The storage unit 21 functions as a storage means of the terminal device 20. The storage unit 21 stores, for example, downloaded profiles. The storage unit 21 can record multiple profiles.

[0057] The communication unit 22 is a communication interface for connecting to a network. The communication unit 22 may be a wireless interface or a wired interface. When the communication unit 22 is a wireless interface, the communication unit 22 may support a plurality of wireless access technologies (wireless communication methods). For example, the communication unit 22 may support LTE, NR, Wi-Fi, etc. Alternatively, the communication unit 22 may support wireless access technologies such as Bluetooth and LPWA. When the communication unit 22 is a wired interface, the communication unit 22 may be a LAN interface such as a NIC.

[0058] The control unit 23 is a controller that controls each unit of the terminal device 20. The control unit 23 is realized by a processor such as a CPU or an MPU. For example, the control unit 23 is realized by a processor executing various programs stored in a storage device inside the terminal device 20 using RAM or the like as a work area. The control unit 23 may also be realized by an integrated circuit such as an ASIC or an FPGA. The CPU, MPU, ASIC, and FPGA can all be considered as controllers. The control unit 23 may also be realized by a GPU in addition to or instead of a CPU.

[0059] The control unit 23 includes an acquisition unit 231, a setting unit 232, an output control unit 233, a recording control unit 234, and a determination unit 235. Each block (acquisition unit 231 to determination unit 235) constituting the control unit 23 is a functional block indicating a function of the control unit 23. These functional blocks may be software blocks or hardware blocks. For example, each of the above-mentioned functional blocks may be a software module realized by software (including a microprogram), or may be a circuit block on a semiconductor chip (die). Of course, each functional block may be a processor or an integrated circuit. The control unit 23 may be configured by functional units different from the above-mentioned functional blocks. The method of configuring the functional blocks is arbitrary.

[0060] The control unit 23 may be an eUICC (Embedded UICC). In this case, the eUICC may be mounted on a board within the terminal device 20, or may be mounted on a card inserted into the terminal device 20. Furthermore, each block (acquisition unit 231 to determination unit 235) constituting the control unit 23 may be a functional element provided in an LPA (Local Profile Assistant).

[0061] The input unit 24 is an input device that accepts various inputs from the outside. For example, the input unit 24 is an operation device such as a keyboard, a mouse, or operation keys that allows the user to perform various operations. If a touch panel is employed in the terminal device 20, the touch panel is also included in the input unit 24. In this case, the user performs various operations by touching the screen with a finger or a stylus.

[0062] The output unit 25 is a device that outputs various types of information to the outside, such as sound, light, vibration, and image. The output unit 25 outputs various types of information to the user under the control of the control unit 23. The output unit 25 includes a display device that displays various types of information. The display device is, for example, a liquid crystal display or an organic electroluminescence display (OLED). The output unit 25 may be a touch panel display device. In this case, the input unit 24 and the output unit 25 may be considered to be an integrated configuration.

[0063] <2-3.RSP Architecture> Next, we will explain the RSP (Remote SIM Provisioning) architecture.

[0064] 5 is a diagram showing an example of an RSP architecture configuration applied to the communication system 1 of this embodiment. The RSP architecture shown in FIG. 5 includes a server 101 (SM-DP+), a server 102 (SM-SM), and a terminal device 20.

[0065] The server 101 is a server called SM-DP+ (Subscription Manager - Data Preparation +). The SM-DP+ transmits a profile to the LPA of the eUICC of the terminal device 20.

[0066] The server 102 is a server called a Subscription Manager - Discovery Server (SM-DS). The SM-DS provides the addresses of one or more SM-DP+s to the Local Discovery Service (LDS) of the terminal device 20.

[0067] The terminal device 20 is a user device used in combination with an eUICC. The terminal device 20 includes an LPA and an eUICC.

[0068] The LPA (Local Profile Assistant) is a functional element (software) that provides the LPD function, the LDS function, and the LUI function. The LPA may be a functional element within the terminal device 20 or may be a functional element within the eUICC.

[0069] An eUICC (Embedded UICC) is a UICC (Universal Integrated Circuit Card) that enables local management of profiles in a secure manner. The eUICC may be implemented on a board within the terminal device 20, or may be implemented on a card inserted into the terminal device 20. The eUICC includes an LPA service and an LPA.

[0070] An LPA service is a functional element (software) that provides the services and access to data required for LPA functions. For example, the Local Profile Assistant (LPA) is a functional element (software) that provides the LPD function, LDS function, and LUI function. The LPA has the function of storing multiple profiles in the eUICC memory.

[0071] <<3. Operation of the communication system>> Having described the configuration of the communication system 1, we next explain the operation of the communication system 1 having such a configuration. The operation of the communication system 1 can be divided into an end condition setting process and a profile management process.

[0072] <3-1. Termination condition setting process> First, the termination condition setting process will be described. The termination condition setting process is a process for setting a termination condition for a profile when a usage termination condition is not set for the profile. FIG. 6 is an example of a flowchart showing the termination condition setting process. The following process is executed by, for example, the control unit 23 of the terminal device 20. The termination condition setting process will be described below with reference to the flowchart in FIG. 6.

[0073] First, the acquisition unit 231 of the terminal device 20 downloads a profile from the server 10 (step S101). Then, the terminal device 20 stores the downloaded profile in the storage unit 21 (for example, a memory in the eUICC).

[0074] Note that, before downloading a new profile to the eUICC, the terminal device 20 may check the amount of memory usage at that time. If the amount of memory usage exceeds a predetermined amount, the terminal device 20 may direct the user to a list screen of installed profiles via a user interface. FIG. 7 is a diagram showing an example of a user interface for directing the user to the list screen of installed profiles. In the example of FIG. 7, a pop-up window (hereinafter simply referred to as a window) is shown as the user interface, but the user interface is not limited to a pop-up window. In the example of FIG. 7, the terminal device 20 displays a window P11 on the output unit 25 for directing the user to the list screen of installed profiles. In the figure, XX displays a number indicating the current memory usage percentage. Also, in the figure, eSIM indicates an eSIM profile.

[0075] Returning to FIG. 6, the setting unit 232 of the terminal device 20 determines whether or not a usage termination condition is set for the downloaded profile (step S102). If no termination condition is set (step S102: Yes), the terminal device 20 inquires of the user via the user interface whether or not to set a profile termination condition. FIG. 8 is a diagram showing an example of a user interface for inquiring whether or not to set a termination condition. In the example of FIG. 8, the terminal device 20 displays a window P12 on the output unit 25 for inquiring the user whether or not to set a usage termination condition for the profile. In the figure, XXX displays a character string for identifying the downloaded profile.

[0076] 6, if the user's response indicates that they do not want to set an end condition (step S103: No), the terminal device 20 ends the end condition setting process. If the user's response indicates that they want to set an end condition (step S103: Yes), the terminal device 20 sets a usage end condition in the profile.

[0077] Fig. 9 is a diagram showing an example of a user interface for setting a termination condition. Fig. 9 shows only a window displayed on the output unit 25 of the terminal device 20, and the terminal device 20 is not shown. In the example of Fig. 9, the terminal device 20 is configured to set the following three termination conditions (A1) to (A3).

[0078] (A1) Data traffic volume (A2) Deadline (A3) Usable area (e.g., country or region)

[0079] First, the output control unit 233 of the terminal device 20 inquires of the user via the user interface which of (A1) to (A3) to set. For example, the terminal device 20 displays a window P13 on the output unit 25 to inquire of the user which of (A1) to (A3) to set. Then, the terminal device 20 displays a user interface for setting the end condition in accordance with the user's selection.

[0080] For example, if the user desires to set the data communication amount (A1), the terminal device 20 displays a window P14 for setting the data communication amount that is the termination condition on the output unit 25. The data communication amount (data usage amount) set here is the upper limit usage amount for communication based on the profile.

[0081] Furthermore, if the user desires to set a deadline (A2), the terminal device 20 displays a window P15 for setting a deadline as a termination condition on the output unit 25. The deadline set here is the usage period (expiration date) for communication based on the profile.

[0082] Furthermore, if the user wishes to set an available area (e.g., a country or region) of (A3), the terminal device 20 displays a window P15 on the output unit 25 for setting an available area (e.g., a country or region in the example of FIG. 6) that is to be the termination condition. The available area set here is an area in which communication based on the profile is possible. The available area is not limited to a country or region, and may be a predetermined range, such as an event venue. Furthermore, examples of setting the available area are not limited to the example shown in FIG. 9. For example, the terminal device 20 may be configured to set an area (prohibited area) in which communication based on the profile is not possible for the profile. Setting a prohibited area can also be considered a type of setting of an available area, since communication is possible outside the prohibited area.

[0083] The termination conditions that can be set in a profile are not limited to the above three (A1) to (A3). For example, the terminal device 20 may be configured to also set the following (A4) to (A5) as termination conditions.

[0084] (A4) Duration of invalid state (A5) Duration of out-of-service state

[0085] The duration of the invalid state in (A4) is the duration since the state in which the profile is not being used (for example, since the last time the use of the profile was completed), and the duration of the out-of-service state in (A5) is the duration since the terminal device 20 entered the out-of-service state.

[0086] The terminal device 20 may be configured to be able to set only one termination condition in the profile, or may be configured to be able to set multiple termination conditions. For example, the terminal device 20 may be configured to be able to set one or multiple termination conditions selected from the termination conditions (A1) to (A5) above in the profile. Of course, the terminal device 20 may be configured to be able to set termination conditions other than the above (A1) to (A5) in the profile.

[0087] When the setting of the end condition is completed, the terminal device 20 ends the end condition setting process.

[0088] Returning to FIG. 6, if an end condition is set in the downloaded profile (step S102: No), the output control unit 233 of the terminal device 20 notifies the user of the end condition set in the profile.

[0089] Fig. 10 is a diagram showing an example of a user interface for notifying the user of the termination conditions. In the example of Fig. 10, the terminal device 20 notifies the user of the above three termination conditions (A1) to (A3). In the figure, XXX displays a character string for identifying the downloaded profile.

[0090] For example, if a data communication amount (A1) is set as the termination condition in the profile, the terminal device 20 displays a window P21 for notifying the user of the data communication amount (data usage amount) that is the termination condition on the output unit 25. In the figure, Y displays a value indicating the data communication amount that is the termination condition.

[0091] Furthermore, if the expiration date (A2) is set in the profile as the termination condition, the terminal device 20 displays a window P22 for notifying the user of the expiration date on the output unit 25. In the figure, MMDD displays a value indicating the expiration date (for example, a date).

[0092] Furthermore, if the available area (A3) is set as the termination condition in the profile, the terminal device 20 displays a window P23 for notifying the user of the available area on the output unit 25. In the figure, a character string indicating the available area (for example, a character string indicating a country or region) is displayed in the "predetermined area" position.

[0093] The termination conditions notified to the user are not limited to the above three (A1) to (A3). For example, the terminal device 20 may be configured to set the above (A4) to (A5). When multiple termination conditions are set in the profile, the terminal device 20 may be configured to display all of the multiple set termination conditions.

[0094] When the notification of the end condition is completed, the terminal device 20 ends the end condition setting process.

[0095] <3-2. Profile management process> Next, the profile management process will be described. The profile management process is a process for managing profiles. In the profile management process, when a condition for ending the use of a profile is met, the terminal device 20 queries the user via the user interface regarding the deletion of the profile. FIG. 11 is an example of a flowchart showing the profile management process. The following process is executed, for example, by the control unit 23 of the terminal device 20. The profile management process will be described below with reference to the flowchart in FIG. 11.

[0096] The acquisition unit 231 of the terminal device 20 selects one profile recorded in the storage unit 21 (for example, the memory of the eUICC) (step S201). Then, the determination unit 235 of the terminal device 20 determines whether the selected profile satisfies a termination condition for use. The termination conditions may include the following (B1) to (B5). The following (B1) to (B5) respectively correspond to (A1) to (A5) shown in the termination condition setting process.

[0097] (B1) The data usage limit set in the profile has been reached. (B2) The expiration date set in the profile has been reached. (B3) You have left the available area set in your profile. (B4) The profile has been in an invalid state (unused state) for a specified period of time. (B5) The terminal device 20 has been out of service for a predetermined period of time.

[0098] Note that only one termination condition may be set in the profile, or multiple termination conditions may be set. For example, one or multiple termination conditions selected from the above termination conditions (B1) to (B5) may be set in the profile. Of course, termination conditions other than the above (B1) to (B5) may also be set in the profile.

[0099] When one or more end conditions selected from the end conditions (B1) to (B5) above are set in the profile, the terminal device 20 may operate as follows.

[0100] For example, the determination unit 235 of the terminal device 20 determines whether the amount of communication based on the profile has reached the data usage amount (upper limit usage amount) set in the profile (step S202). If the upper limit usage amount has been reached (step S202: Yes), the terminal device 20 proceeds to step S207.

[0101] If the upper limit of usage has not been reached (step S202: No), the determination unit 235 of the terminal device 20 determines whether the usage period set in the profile has been reached (step S203). If the usage period has been reached (step S203: Yes), the terminal device 20 proceeds to step S207.

[0102] If the usage period has not yet expired (step S203: No), the determination unit 235 of the terminal device 20 determines whether the terminal device 20 is outside the available area set in the profile (step S204). If the terminal device 20 is outside the available area (step S204: Yes), the terminal device 20 proceeds to step S207.

[0103] If the terminal device 20 has not left the available area (step S204: No), the determination unit 235 of the terminal device 20 determines whether the profile has been in an invalid state (a state in which the profile is not being used) for a predetermined period of time (step S205). If the invalid state has continued for the predetermined period of time (step S205: Yes), the terminal device 20 proceeds to step S207.

[0104] If the invalid state has not continued for the predetermined period (step S205: No), the determination unit 235 of the terminal device 20 determines whether the out-of-service state of the terminal device 20 has continued for the predetermined period (step S205). At this time, even if the profile is valid, the determination unit 235 determines that the termination condition has been satisfied if the out-of-service state of the terminal device 20 has continued for the predetermined period. If the out-of-service state has continued for the predetermined period (step S206: Yes), the terminal device 20 proceeds to the process of step S207.

[0105] If the out-of-service state has not continued for the predetermined period (step S206: No), the terminal device 20 returns the process to step S201, changes the profile to another profile, and repeats the processes from step S201 onwards.

[0106] If the selected profile satisfies the conditions for ending use (steps S202 to S206: Yes), the output control unit 233 of the terminal device 20 inquires of the user about deleting the profile via the user interface. Fig. 12 is a diagram showing an example of a user interface for inquiring of the user about deleting the profile. Specifically, Fig. 12 is a diagram showing how, when the profile has reached its expiration date, the user is inquired about whether or not to delete the profile. In the example of Fig. 12, the terminal device 20 displays a window P31 on the output unit 25 for checking the profile and inquiring about whether or not to delete it.

[0107] It should be noted that the user interface does not necessarily have to confirm the profile and ask whether to delete it, for example, the user interface may simply ask whether to delete the profile.

[0108] 13 to 17 are diagrams showing other examples of user interfaces for inquiring of a user regarding profile deletion. More specifically, FIG. 13 is a diagram showing an example of a user interface (window P32) for inquiring of a user regarding whether to delete a profile when the traffic volume of communication based on the profile has reached the upper limit usage volume. FIG. 14 is a diagram showing an example of a user interface (window P33) for inquiring of a user regarding whether to delete a profile when the profile has reached its expiration date. FIG. 15 is a diagram showing an example of a user interface (window P34) for inquiring of a user regarding whether to delete a profile when the terminal device 20 is outside the available area (country or region). FIG. 16 is a diagram showing an example of a user interface (window P35) for inquiring of a user regarding whether to delete a profile when the invalid state of the profile has continued for a predetermined period. FIG. 17 is a diagram showing an example of a user interface (window P36) for inquiring of a user regarding whether to delete a profile (or whether to switch to another profile) when the terminal device 20 has not been out of service area for a predetermined period.

[0109] 11, the determination unit 235 of the terminal device 20 determines whether or not the user desires to delete the profile (step S208). If the user does not desire deletion (step S208: No), the terminal device 20 returns the process to step S201, replaces the profile with another profile, and repeats the processes from step S201 onwards.

[0110] On the other hand, if the user desires deletion (step S208: Yes), the recording control unit 234 of the terminal device 20 deletes the profile selected in step S201 from the storage unit 21 (for example, the memory of the eUICC) (step S209).

[0111] When the deletion of the profile is completed, the terminal device 20 returns the process to step S201, replaces the profile with another profile, and repeats the processes from step S201 onwards.

[0112] <3-3. Supplementary Information> <3-3-1. Profile Metadata> A profile is associated with profile metadata. Profile metadata is information about the profile that is used for the purpose of local profile management. Table 21 of Non-Patent Document 1 (SGP.21 V2.4) describes the profile metadata requirements.

[0113] As described above, in this embodiment, the end condition of usage is set in the profile. In order to have the end condition information in the profile, the requirements shown in METAx1 in FIG. 18 may be added as requirements for the profile metadata. FIG. 18 is a diagram showing additional requirements for the profile metadata. The x1 in METAx1 is replaced with an appropriate number. The requirements described in METAx1 are as follows:

[0114] (METAx1) The profile metadata may include optional fields for storing the following terms of use: 1. Data usage limit (xxGB) 2. Expiration Date 3. Available Space

[0115] <3-3-2.About LPA> As described above, the terminal device 20 includes an LPA (Local Profile Assistant) as a functional element (software) for managing local profiles. Table 21 of Non-Patent Document 1 (SGP.21 V2.4) describes the LPA requirements.

[0116] To realize the terminal device 20 of this embodiment, the requirements shown in LPAx1 to LPAx3 in FIG. 19 may be added as LPA requirements. FIG. 19 is a diagram showing additional LPA requirements. x1 to x3 in LPAx1 to LPAx3 are replaced with appropriate numbers, respectively. At least one of LPAx1 to LPAx3 may be applied to the operation of the terminal device 20 of this embodiment. The requirements described in LPAx1 to LPAx3 are as follows:

[0117] (LPA x 1) The LPA should check the terms of use of downloaded profiles and prompt the user to delete any unwanted profiles. If the profile metadata does not include an optional field for storing terms of use and the user wishes to do so, the LPA can ask the user to set it and maintain it as its own data.

[0118] (LPA x 2) LPA may also have its own conditions that determine whether to recommend the user to remove unwanted profiles. Such conditions are outside the scope of this document and are left to the implementation.

[0119] (LPA x 3) The LPA MUST recommend to the user to delete unnecessary profiles if the size of the free memory on the eUICC may not be sufficient to download another profile. The threshold is outside the scope of this document and is left to the implementation.

[0120] <<4. Modifications>> The above-described embodiment is merely an example, and various modifications and applications are possible.

[0121] <4-1. Variations regarding conditions for terminating use> In the above <3-2. Profile Management Process>, the following five conditions (B1) to (B5) are given as examples of conditions for terminating the use of a profile.

[0122] (B1) The data usage limit set in the profile has been reached. (B2) The expiration date set in the profile has been reached. (B3) You have left the available area set in your profile. (B4) The profile has been in an invalid state (unused state) for a specified period of time. (B5) The terminal device 20 has been out of service for a predetermined period of time.

[0123] However, the termination conditions are not limited to these, and may include, for example, the condition shown in (B6) below.

[0124] (B6) The amount of memory used to store the profile has exceeded a certain amount (certain percentage).

[0125] The termination condition may also be a combination of multiple conditions. For example, the termination condition may be a combination of multiple conditions selected from the above (B1) to (B6). For example, the determination unit 235 of the terminal device 20 may determine that the termination condition is met when (B6) the memory usage exceeds a predetermined amount and (B4) the profile has not been used for a predetermined period of time. When the remaining memory becomes low, the user can be prompted to manage the profile.

[0126] <4-2. Modifications regarding profile deletion> In the above-described <3-2. Profile Management Process>, when the termination condition set in a profile is satisfied, the terminal device 20 inquires of the user via the user interface whether or not to delete the profile (for example, FIGS. 12 to 17). However, the terminal device 20 may be configured to automatically delete the profile when the termination condition set in the profile is satisfied.

[0127] In this case, the terminal device 20 may obtain in advance consent from the user that the profile will be automatically deleted if certain conditions are met when the profile is downloaded. For example, when the output control unit 233 of the terminal device 20 downloads a profile, it inquires the user via a user interface as to whether or not to automatically delete the profile when an end condition set in the profile is met. If the user selects to automatically delete the profile and the end condition set in the profile is met, the recording control unit 234 of the terminal device 20 automatically deletes the profile without inquiring of the user.

[0128] This makes it easier to manage profiles.

[0129] <4-3. Other variations> The server 10 and the control device that controls the terminal device 20 of this embodiment may be realized by a dedicated computer system or a general-purpose computer system.

[0130] For example, a communication program for executing the above-described operations is stored in a computer-readable recording medium such as an optical disk, a semiconductor memory, a magnetic tape, or a flexible disk and distributed. Then, for example, the program is installed in a computer and the above-described processing is executed to configure a control device. In this case, the control device may be a device external to the server 10 or the terminal device 20 (for example, a personal computer). Alternatively, the control device may be a device internal to the server 10 or the terminal device 20 (for example, the control unit 13 or the control unit 23).

[0131] The communication program may also be stored in a disk device provided in a server on a network such as the Internet, and may be downloaded to a computer. The above functions may also be realized by cooperation between an OS (Operating System) and application software. In this case, the parts other than the OS may be stored on a medium and distributed, or may be stored on a server and downloaded to a computer.

[0132] Furthermore, among the processes described in the above embodiments, all or part of the processes described as being performed automatically can be performed manually, or all or part of the processes described as being performed manually can be performed automatically using a known method. In addition, the information including the processing procedures, specific names, various data, and parameters shown in the above documents and drawings can be changed as desired unless otherwise specified. For example, the various information shown in each drawing is not limited to the information shown in the drawings.

[0133] Furthermore, the components of each device shown in the figure are conceptual functional units and do not necessarily have to be physically configured as shown. In other words, the specific form of distribution and integration of each device is not limited to that shown in the figure, and all or part of them can be functionally or physically distributed and integrated in any unit depending on various loads and usage conditions. This distribution and integration configuration may also be performed dynamically.

[0134] The above-described embodiments can be combined as appropriate within the scope of the present invention without causing any inconsistency in the processing content. The order of the steps shown in the flowcharts of the above-described embodiments can be changed as appropriate.

[0135] Furthermore, for example, this embodiment can also be implemented as any configuration that constitutes an apparatus or system, such as a processor as a system LSI (Large Scale Integration), a module using multiple processors, a unit using multiple modules, a set in which other functions are added to a unit, etc. (i.e., a configuration of a part of an apparatus).

[0136] In this embodiment, a system refers to a collection of multiple components (devices, modules (components), etc.), regardless of whether all the components are in the same housing. Therefore, multiple devices housed in separate housings and connected via a network, and a single device in which multiple modules are housed in a single housing, are both systems.

[0137] Furthermore, for example, this embodiment can be configured as a cloud computing system in which one function is shared and processed jointly by a plurality of devices via a network.

[0138] <<5. Conclusion>> As described above, according to one embodiment of the present disclosure, the terminal device 20 has a function for saving and deleting profiles related to wireless communication. For example, the terminal device 20 has an LPA (Local Profile Assistant) for managing eSIM profiles. The terminal device 20 is capable of storing multiple profiles. The terminal device 20 is configured to determine whether a condition for terminating the use of a profile is met. If the terminal device 20 determines that the condition for terminating the use of the profile is met, the terminal device 20 queries the user via a user interface regarding the deletion of the profile. If the terminal device 20 receives a response from the user requesting the deletion of the profile, the terminal device 20 deletes the profile.

[0139] This facilitates profile management, improving the convenience of the terminal device 20. For example, by providing a user with an opportunity to delete a profile that is not valid or not being used effectively, it is possible to encourage the user to move the profile to another eSIM-compatible device or cancel a profile that is no longer needed. Furthermore, by providing a user with an opportunity to delete a profile that is not valid or not being used effectively, it is possible to increase the free memory capacity in the eUICC.

[0140] Although the embodiments of the present disclosure have been described above, the technical scope of the present disclosure is not limited to the above-described embodiments, and various modifications are possible within the scope of the gist of the present disclosure. Furthermore, components of different embodiments and modifications may be combined as appropriate.

[0141] Furthermore, the effects of each embodiment described in this specification are merely examples and are not limiting, and other effects may also be obtained.

[0142] The present technology can also be configured as follows. (1) A communication device having a function for saving and deleting a profile related to wireless communication, a determination unit that determines whether a condition for ending use of the profile is satisfied; an output control unit that, when the termination condition is satisfied, executes an inquiry regarding deletion of the profile via a user interface; A communication device comprising: (2) The communication device has a function of recording a plurality of profiles in a memory. The communication device according to (1) above. (3) The termination condition includes reaching a data usage amount set in the profile. The communication device according to (1) or (2). (4) The termination condition includes reaching a usage period set in the profile. The communication device according to any one of (1) to (3). (5) The termination condition includes leaving an available area set in the profile. The communication device according to any one of (1) to (4). (6) The termination condition includes that the profile has remained invalid for a predetermined period of time. The communication device according to any one of (1) to (5). (7) the communication device has a function of recording a plurality of profiles in a memory; the termination condition includes that the profile has not been used for a predetermined period of time; the determining unit determines that the termination condition is satisfied when the memory usage exceeds a predetermined amount and when the profile has not been used for a predetermined period of time. The communication device according to any one of (1) to (6). (8) the termination condition includes that the communication device has been out of service for a predetermined period of time; the determination unit determines that the termination condition is satisfied when the communication device is out of service area for a predetermined period of time even if the profile is valid. The communication device according to any one of (1) to (7). (9) further comprising a setting unit that sets the termination condition in the profile when the termination condition is not set in the profile; The communication device according to any one of (1) to (8). (10) the output control unit, when the end condition is not set in the profile, executes an inquiry regarding the setting of the end condition in the profile via a user interface; the setting unit sets the termination condition in the profile based on a user's response to an inquiry regarding the setting of the termination condition. The communication device according to (9) above. (11) a recording control unit that deletes the profile based on a user's response to an inquiry regarding the deletion of the profile; The communication device according to any one of (1) to (10). (12) the output control unit inquires of a user via a user interface whether or not to automatically delete the profile when a termination condition set in the profile is satisfied; When a selection is made to automatically delete the profile and an end condition set in the profile is satisfied, the recording control unit automatically deletes the profile without querying the user. The communication device according to (11) above. (13) the profile is an eSIM profile; The communication device according to any one of (1) to (12). (14) The communication device is a smartphone. The communication device according to any one of (1) to (13). (15) A communication method executed by a communication device having a function for recording and deleting a profile related to wireless communication, determining whether a condition for ending use of the profile is satisfied; if the termination condition is met, executing a query regarding deletion of the profile via a user interface; Communication method. [Explanation of symbols]

[0143] 1. Communication Systems 10 Servers 20 Terminal equipment 11, 21 Storage section 12, 22 Communications Department 13, 23 Control section 24 Input section 25 Output section 231 Acquisition Department 232 Settings 233 Output control section 234 Recording control section 235 Discrimination part N1 and N2 networks

Claims

1. A communication device having a function for saving and deleting a profile related to wireless communication, a determination unit that determines whether a condition for ending use of the profile is satisfied; an output control unit that, when the termination condition is satisfied, executes an inquiry regarding deletion of the profile via a user interface; A communication device comprising:

2. The communication device has a function of recording a plurality of profiles in a memory. The communication device according to claim 1 .

3. The termination condition includes reaching a data usage amount set in the profile. The communication device according to claim 1 .

4. The termination condition includes reaching a usage period set in the profile. The communication device according to claim 1 .

5. The termination condition includes leaving an available area set in the profile. The communication device according to claim 1 .

6. The termination condition includes that the profile has remained invalid for a predetermined period of time. The communication device according to claim 1 .

7. the communication device has a function of recording a plurality of profiles in a memory; the termination condition includes that the profile has not been used for a predetermined period of time; the determining unit determines that the termination condition is satisfied when the memory usage exceeds a predetermined amount and when the profile has not been used for a predetermined period of time. The communication device according to claim 1 .

8. the termination condition includes that the communication device has been out of service for a predetermined period of time; the determination unit determines that the termination condition is satisfied when the communication device is out of service area for a predetermined period of time even if the profile is valid. The communication device according to claim 1 .

9. further comprising a setting unit that sets the termination condition in the profile when the termination condition is not set in the profile; The communication device according to claim 1 .

10. the output control unit, when the end condition is not set in the profile, executes an inquiry regarding the setting of the end condition in the profile via a user interface; the setting unit sets the termination condition in the profile based on a user's response to an inquiry regarding the setting of the termination condition. The communication device according to claim 9.

11. a recording control unit that deletes the profile based on a user's response to an inquiry regarding the deletion of the profile; The communication device according to claim 1 .

12. the output control unit inquires of a user via a user interface whether or not to automatically delete the profile when a termination condition set in the profile is satisfied; When a selection is made to automatically delete the profile and an end condition set in the profile is satisfied, the recording control unit automatically deletes the profile without querying the user. The communication device according to claim 11.

13. the profile is an eSIM profile; The communication device according to claim 1 .

14. The communication device is a smartphone. The communication device according to claim 1 .

15. A communication method executed by a communication device having a function for recording and deleting a profile related to wireless communication, determining whether a condition for ending use of the profile is satisfied; if the termination condition is met, executing a query regarding deletion of the profile via a user interface; Communication method.

Images