Wireless device and program

Abstract

To activate a profile containing information for accessing a mobile communication network without communicating with other apparatuses.SOLUTION: A wireless device includes an integrated circuit configured to store a plurality of profiles and one or more public keys, including a first public key, in which when a command to change the state of the profiles is received, one of conditions for executing a process following the command is receiving signature information verifiable with one among the one or more public keys. The wireless device also includes storage means for storing a first private key corresponding to the first public key, and control means for transmitting, to the integrated circuit, a first command to change a first profile from an invalid state to a valid state when predetermined conditions are met, along with first signature information generated with the first private key.SELECTED DRAWING: Figure 4

Description

[Technical Field]

[0001] The present disclosure relates to a control technology for an embedded subscriber identity module (eSIM) implemented in a wireless device for IoT (Internet of Things). [Background technology]

[0002] Non-Patent Document 1 discloses an IoT architecture for eSIM. In this specification, the terms "eSIM" and "embedded universal integrated circuit card (eUICC)" are used interchangeably. Unlike wireless devices that are intended to be operated by humans, such as smartphones, wireless devices for IoT (hereinafter referred to as IoT devices) are usually not provided with a user interface such as a touch panel. For this reason, Non-Patent Document 1 discloses that a device called an eIM (eSIM IoT remote manager) remotely controls the eSIM of an IoT device via a mobile communication network.

[0003] According to Non-Patent Document 1, an eSIM stores multiple profiles, but two or more profiles cannot be enabled at the same time. A profile includes information necessary for an IoT device to access a mobile communication network also known as a public land mobile network (PLMN), such as information indicating accessible mobile communication networks.

[0004] For example, if Profile #1 for accessing PLMN #1 and Profile #2 for accessing PLMN #2 are stored in the eSIM of an IoT device, the IoT device can access PLMN #1 by enabling Profile #1, and can access PLMN #2 by enabling Profile #2. However, since Profile #1 and Profile #2 cannot be enabled at the same time, the IoT device cannot access PLMN #1 and PLMN #2 at the same time. [Prior art documents] [Non-patent literature]

[0005] [Non-Patent Document 1] eSIM IoT Technical Specification GSMA SGP.32 v1.0.1, July 4, 2023 Summary of the Invention [Problem to be solved by the invention]

[0006] 1 is a more detailed explanatory diagram of the remote control configuration of the eSIM of the IoT device 100 according to the above-mentioned Non-Patent Document 1. The eSIM of the IoT device 100 stores a profile #1 for wirelessly accessing a mobile communication network 201 (also referred to as PLMN #1) and a profile #2 for wirelessly accessing a mobile communication network 202 (also referred to as PLMN #2), with profile #1 being enabled and profile #2 being disabled. Therefore, the IoT device 100 wirelessly accesses the mobile communication network 201. The mobile communication networks 201 and 202 are connected to the Internet 200, and the eIM 300 is connected to the Internet 200.

[0007] The eSIM of the IoT device 100 stores an identifier of the eSIM, a public key, a key identifier of the public key, etc., and the eIM 300 stores a private key that is paired with the public key stored in the eSIM of the IoT device 100. In FIG. 1, the public key stored in the eSIM of the IoT device 100 is designated as PUB#1, and the private key that forms a pair with PUB#1 is designated as SEC#1.

[0008] 1, when activating profile #2 stored in the eSIM of the IoT device 100, the eIM 300 transmits an activation command to the IoT device 100. The activation command includes processing information including a key identifier of the public key PUB#1 stored in the eSIM of the IoT device 100, a counter value, and the like, and signature information indicating a digital signature by SEC#1 of the processing information. Note that the counter value is a value associated with SEC#1 / PUB#1 and managed by the eIM 300 and the eSIM of the IoT device 100, and is incremented by one each time a process using SEC#1 / PUB#1 is performed between the eIM 300 and the eSIM of the IoT device 100.

[0009] The eSIM of the IoT device 100 verifies the signature information included in the received activation command using the public key PUB#1 indicated by the key identifier of the processing information included in the received activation command. The eSIM of the IoT device 100 then sets successful verification of the signature information as one of the conditions for activating Profile #2. In other words, if the verification of the signature information is unsuccessful, the eSIM of the IoT device 100 does not activate Profile #2. Note that, according to Non-Patent Document 1, two or more profiles cannot be activated at the same time, so activating Profile #2 disables Profile #1.

[0010] For example, assume that a failure occurs in mobile communication network 201 in the state shown in Figure 1, causing IoT device 100 to be unable to communicate via mobile communication network 201. In this case, by activating profile #2, IoT device 100 can communicate with a server device on Internet 200 via mobile communication network 202. However, because the failure in mobile communication network 201 prevents eIM 300 from communicating with IoT device 100, eIM 300 cannot send an activation command to IoT device 100, and therefore profile #2 cannot be activated.

[0011] In this way, the profile stored in the eSIM of the IoT device 100 can only be controlled by the eIM300 having the private key SEC#1 corresponding to the public key PUB#1 stored in the eSIM of the IoT device 100. However, there may be cases where it is desired to activate the profile stored in the eSIM of the IoT device 100 without communicating with the eIM300, such as during a failure in the mobile communication network described above.

[0012] The present disclosure provides a technique for validating a profile containing information for accessing a mobile communication network without communicating with another device. [Means for solving the problem]

[0013] According to one aspect of the present disclosure, a wireless device includes an integrated circuit configured to store a plurality of profiles, each containing information for accessing a mobile communication network, and one or more public keys including a first public key, wherein, when a command to change the state of the plurality of profiles between the valid state and the invalid state is received, one of the conditions for executing a process in accordance with the command is to receive signature information verifiable by one of the one or more public keys along with the command; communication means for accessing and communicating with the mobile communication network in accordance with information contained in the profile set to the valid state; storage means for storing a first private key corresponding to the first public key; and control means for, when a predetermined condition is met, transmitting to the integrated circuit a first command to change a first profile of the plurality of profiles that is in the invalid state to the valid state, together with first signature information generated by the first private key. [Effects of the Invention]

[0014] According to the present disclosure, a profile containing information for accessing a mobile communication network can be activated without communicating with other devices. [Brief explanation of the drawings]

[0015] [Figure 1] FIG. 1 is a system configuration diagram for explaining an embodiment. [Figure 2] FIG. 1 is a diagram showing an example of the configuration of an IoT device before initialization processing. [Figure 3] FIG. 10 is a diagram showing an example of a sequence of an initialization process. [Figure 4] FIG. 10 is a diagram showing an example of the configuration of an IoT device after initialization processing. [Figure 5] FIG. 4 is a diagram showing an example of a sequence of processes executed by a control unit. DETAILED DESCRIPTION OF THE INVENTION

[0016] Hereinafter, the embodiments will be described in detail with reference to the accompanying drawings. Note that the following embodiments do not limit the scope of the invention as claimed, and not all combinations of features described in the embodiments are necessarily essential to the invention. Two or more of the features described in the embodiments may be arbitrarily combined. Furthermore, the same reference numerals are used for the same or similar components, and redundant explanations will be omitted.

[0017] Fig. 1 is a system configuration diagram for explaining an embodiment. As shown in Fig. 1, the eSIM of an IoT device 100 stores a profile #1 for accessing a mobile communication network 201 and a profile #2 for accessing a mobile communication network 202. The mobile communication networks 201 and 202 are networks managed and operated by, for example, different telecommunications operators (communications carriers) and are connected to the Internet 200. An eIM 300 connected to the Internet 200 stores a private key SEC#1 used to control the activation and deactivation of the profile stored in the eSIM of the IoT device 100. The IoT device 100 stores a public key PUB#1 corresponding to the private key SEC#1 held by the eIM 300.

[0018] 2 shows the configuration of the IoT device 100 before initialization processing. In this embodiment, initialization processing refers to processing for storing a public key in the eSIM 14 for controlling the activation and deactivation of profiles stored in the eSIM 14. The IoT device 100 includes a communication unit 10, a memory device 11, a control unit 13, and the eSIM 14.

[0019] The eSIM 14 is an integrated circuit configured to store multiple profiles and one or more public keys, and is also referred to as an eUICC. The eSIM 14 is configured to limit the number of profiles that are set to an active state to a maximum of one of the multiple profiles stored therein. The eSIM 14 is also configured to, when receiving a command to change the state of the multiple profiles stored therein between an active state and an inactive state, include, as one of the conditions for executing a process in accordance with the command, receiving, together with the command, signature information that can be verified by one of the one or more public keys stored therein.

[0020] The control unit 13 includes, for example, one or more processors and one or more volatile memory devices. The one or more processors load the control program stored in the memory device 11 into the one or more volatile memory devices and execute the program, thereby controlling the entire IoT device 100. In this case, the one or more processors also function as the key generation unit 12.

[0021] The memory device 11 is configured with one or more non-volatile memory devices. The memory device 11 pre-stores information indicating an eSIM_ID, which is an identifier of the eSIM 14, flag information, a public key PUB#1 corresponding to a private key SEC#1 held by the eIM 300, a key identifier ID#1 of the public key PUB#1, and a counter value #1 associated with the public key PUB#1. The counter value #1 is a variable, and an initial value of the counter value #1, for example, 0, is stored in the memory device 11. The flag information is information indicating whether or not initialization processing has been performed. In the following description, as an example, flag information with a value of 0 indicates that initialization processing has not been performed, and flag information with a value different from 0 indicates that initialization processing has been performed. Note that the eSIM_ID is information also stored in the eSIM 14. Therefore, instead of storing the eSIM_ID in the memory device 11, the control unit 13 may acquire the eSIM_ID from the eSIM 14 as needed.

[0022] In Non-Patent Document 1, the eSIM_ID is referred to as an EID (Embedded Identity Document), the counter value is referred to as a counterValue, and the key identifier is referred to as an eimID.

[0023] The communication unit 10 wirelessly connects to the mobile communication network 201 or 202 in accordance with information contained in the valid profile of the two profiles of the eSIM 14. Furthermore, the communication unit 10 performs communication processing via the mobile communication network to which it is wirelessly connected.

[0024] In this embodiment, the control unit 13 executes initialization processing when power is turned on while the value of the flag information stored in the memory device 11 is 0. Figure 3 shows the sequence when power is turned on for the IoT device 100.

[0025] When the power is turned on, the control unit 13 reads flag information from the memory device 11 in S10, and determines whether or not to perform initialization processing based on the value in S11. In this example, the value of the flag information is 0, so the control unit 13 determines in S11 that initialization processing should be performed. If the flag information has a value other than 0, the control unit 13 determines that initialization processing does not need to be performed, and ends the processing in FIG. 3.

[0026] When executing the initialization process, the control unit 13 causes the key generation unit 12 to perform the key generation process. The key generation unit 12 generates a pair of a private key and a public key using an arbitrary method. Here, it is assumed that a pair of a private key SECE#2 and a public key PUB#2 has been generated. The control unit 13 assigns a key identifier ID#2 to the public key PUB#2 generated by the key generation unit 12. In S13, the control unit 13 stores information indicating the private key SEC#2, the key identifier ID#2, and the initial value of a counter value #2 associated with the public key PUB#2 in the memory device 11. The counter value #2 is a variable, and its initial value is, for example, 0.

[0027] Furthermore, in S14, the control unit 13 reads out the public key PUB#1, the key identifier ID#1 of the public key PUB#1, and the initial value of the counter value #1 associated with the public key PUB#1, all stored in the memory device 11. Then, in S15, the control unit 13 transmits information indicating a set of the public key PUB#1, the key identifier ID#1, and the initial value of the counter value #1, and a set of the public key PUB#2, the key identifier ID#2, and the initial value of the counter value #2, to the eSIM 14, which stores the information. The processing of S15 corresponds to, for example, the processing performed by the function "ES10b.AddInitialEim" defined in Non-Patent Document 1. After storing the information received in S15, the eSIM 14 transmits an affirmative response to the control unit 13 in S16. Note that if any error occurs, the eSIM 14 notifies the control unit 13 of the error in S16.

[0028] When the control unit 13 receives the positive response from the eSIM 14, in S17, the control unit 13 updates the flag information stored in the memory device 11 to a value different from 0, for example, to a value of 1.

[0029] 4 shows the configuration of the IoT device 100 after the initialization process. Compared to the state before the initialization process shown in FIG. 2, information indicating a private key SEC#2, a key identifier ID#2, and a counter value #2 is additionally stored in the memory device 11. Furthermore, the flag information stored in the memory device 11 is updated from a value of 0 to a value of 1. Furthermore, information indicating a set of a public key PUB#1, a key identifier ID#1, and a counter value #1, and a set of a public key PUB#2, a key identifier ID#2, and a counter value #2 is additionally stored in the eSIM 14.

[0030] Fig. 5 is a sequence diagram of the process executed by the control unit 13. It is assumed that at the start of the process in Fig. 5, profile #1 is valid and therefore profile #2 is invalid.

[0031] In S20, the control unit 13 detects that a predetermined condition that triggers a process of changing an invalid profile to an valid profile has been satisfied. As an example, the predetermined condition is satisfied when a failure occurs in the mobile communication network 201 accessed according to the valid profile #1. Therefore, the communication unit 10 is configured to notify the control unit 13 of the occurrence of the failure when a failure occurs in the mobile communication network accessed according to the valid profile.

[0032] For example, the communication unit 10 may detect a failure in the mobile communication network when a wireless link with the mobile communication network cannot be established. Furthermore, the communication unit 10 may detect a failure in the mobile communication network when a wireless link with the mobile communication network is established but the Internet 200 cannot be accessed via the mobile communication network, i.e., when a connection such as a protocol data unit (PDU) session or a bearer connecting the communication unit 10 and the Internet 200 is not established. Furthermore, the communication unit 10 may detect a failure in the mobile communication network when it is unable to transmit or receive packets to or from a server device on the Internet 200 via the accessed mobile communication network for a predetermined period of time or longer. When a failure occurs in communication via the mobile communication network 201 accessed according to the valid profile #1, the control unit 13 starts a change process to change the invalid profile #2 to the valid profile.

[0033] Upon start of the change process, the control unit 13 reads information indicating the eSIM_ID, private key SEC#2, key identifier ID#2, and counter value #2 from the memory device 11 in S21. Then, the control unit 13 generates processing information including information indicating the eSIM_ID, key identifier ID#2, and counter value #2 in S22, and generates signature information for the processing information using the private key SEC#2 in S23. The control unit 13 transmits a profile activation command to the eSIM 14 in S24. The activation command includes information indicating profile #2 to be changed to an active state, the processing information, and the signature information. The process of S24 corresponds to the process performed by the function “ES10b:LoadEuiccPackage” defined in Non-Patent Document 1, for example.

[0034] In S25, the eSIM 14 verifies the processing information. This verification includes verifying whether the signature information was generated using the private key SEC#2 based on the public key PUB#2 indicated by the key identifier ID#2 included in the processing information. Furthermore, this verification includes verifying that the counter value #2 included in the processing information matches the counter value #2 stored in the eSIM 14.

[0035] If the verification is successful, the eSIM 14 changes the state of profile #2 to valid in S26 and changes the state of profile #1 to invalid instead. Then, the eSIM 14 updates the counter value #2 by incrementing it by 1 in S27, and notifies the control unit 13 of the processing result in S28. If the verification is unsuccessful, the eSIM 14 notifies the control unit 13 of an error. In S29, the control unit 13 updates the counter value #2 stored in the memory device 11 by incrementing it by 1.

[0036] The eSIM 14 of the IoT device 100 also stores a public key PUB#1 corresponding to the private key SEC#1 held by the eIM 300. Therefore, the eIM 300 can also control the profile of the IoT device 100.

[0037] As described above, in this embodiment, the initialization process stores a public key (PUB#1) for remote control by the eIM300 and a public key (PUB#2) for independent control that does not require the eIM300 in the eSIM14 of the IoT device 100. Furthermore, the initialization process stores a private key (SEC#2) corresponding to the public key for independent control in the memory device 11 of the IoT device 100. When the control unit 13 of the IoT device 100 detects a trigger for changing a disabled profile to an enabled profile, the control unit 13 transmits to the eSIM14 information indicating the profile to be enabled, processing information required to change the profile to the enabled state, and signature information for the processing information based on the stored private key. This configuration allows a profile to be enabled in the IoT device 100 without the involvement of the eIM300.

[0038] <Other embodiments> A variation of the above embodiment will be described below. In the above embodiment, the key generation unit 12 generates a pair of a private key SEC#2 and a public key PUB#2 in the initialization process. However, the pair of the private key SEC#2 and the public key PUB#2, along with the initial values ​​of the key identifier ID#2 and the counter value #2, may be pre-stored in the memory device 11. In this case, in the initialization process, the control unit 13 notifies the eSIM 14 of the initial values ​​of the public key PUB#2, the key identifier ID#2, and the counter value #2 stored in the memory device 11. That is, S12 and S13 in FIG. 3 are omitted. Furthermore, in S14, the control unit 13 reads from the memory device 11 a set of the public key PUB#1, the key identifier ID#1, and the counter value #1, and a set of the public key PUB#2, the key identifier ID#2, and the counter value #2, and notifies the eSIM 14 of them in S15.

[0039] In the above embodiment, a set of public key PUB#1, key identifier ID#1, and counter value #1 is stored in the memory device 11, and in S15, the set of public key PUB#1, key identifier ID#1, and counter value #1 is notified to the eSIM 14 together with the set of public key PUB#2, key identifier ID#2, and counter value #2. This is because, when a set of public key, key identifier, and counter value is stored in the eSIM 14, another set of public key, key identifier, and counter value cannot be added later. However, when a new command is defined for adding another set of public key, key identifier, and counter value to the eSIM 14, the set of public key PUB#1, key identifier ID#1, and counter value #1 is stored in the eSIM 14 in advance, eliminating the need to store the set in the memory device 11. In this case, S14 in FIG. 3 is omitted, and in S15, the control unit 13 adds the set of public key PUB#2, key identifier ID#2, and counter value #2 to the eSIM 14.

[0040] Furthermore, if control of eSIM 14 by eIM 300 is not required, there is no need to store the set of public key PUB#1, key identifier ID#1, and counter value #1 in eSIM 14. In this case, there is no need to store the set of public key PUB#1, key identifier ID#1, and counter value #1 in IoT device 100, so S14 in FIG. 3 is omitted, and in S15, control unit 13 adds the set of public key PUB#2, key identifier ID#2, and counter value #2 to eSIM 14.

[0041] In the above embodiment, the initialization process is triggered by powering on the IoT device 100 when the flag information indicates that the initialization process has not been executed. Therefore, once the initialization process is executed, the initialization process is not executed when the IoT device 100 is subsequently powered on. However, in consideration of the need to execute the initialization process at a later timing, the flag information may be configured to be changeable to 0. For example, the flag information may be changed by the eIM 300 connected to the Internet 200 or another server device (not shown) via a mobile communication network to which the Internet 200 and the IoT device 100 are connected. Alternatively, the IoT device 100 may be provided with a simple input interface such as a button, and the flag information may be set to 0 by operating the button (user operation). By setting the flag information to 0, the initialization process is executed when the IoT device 100 is subsequently powered on.

[0042] Furthermore, the IoT device 100 may be provided with an input interface using buttons or the like, and the initialization process may be forcibly executed by operating the button (user operation) regardless of the value of the flag information. Note that the initialization process may be performed before shipping the IoT device 100, between shipping and installation of the IoT device 100, or when installing the IoT device 100.

[0043] Furthermore, in the above embodiment, two profiles, profile #1 and profile #2, are stored in the eSIM 14. However, the present invention can also be applied to an eSIM 14 that can store three or more profiles. In this case, if a failure occurs in the mobile communication network accessed according to an enabled profile, the control unit 13 selects a profile to be enabled from other disabled profiles by any method. If communication is not possible with the selected profile, the control unit 13 repeatedly enables one profile selected from the multiple disabled profiles until communication is possible. As an example, a priority order is assigned to the multiple profiles, and the control unit 13 selects a profile to be enabled from the multiple disabled profiles according to the priority order.

[0044] Furthermore, the control unit 13 can be configured to, when a failure occurs in a mobile communication network being accessed according to an enabled profile, select only a profile that accesses a mobile communication network different from the mobile communication network being accessed as a profile to be enabled. In other words, when communication via the accessed mobile communication network is not possible, the control unit 13 can be configured to select, from among multiple disabled profiles, one or more profiles that access a mobile communication network different from the accessed mobile communication network, and to repeatedly enable the selected one or more profiles in order until communication is possible.

[0045] In the above embodiment, the predetermined condition for triggering the profile change process by the control unit 13 is the occurrence of a failure in the mobile communication network accessed according to the active profile. However, the predetermined condition for triggering the profile change process is not limited to the occurrence of a failure in the mobile communication network accessed according to the active profile. For example, consider a configuration in which a profile to be used for specific communication, such as an emergency communication, is determined in advance. In this case, the predetermined condition for triggering the profile change process can be the occurrence of a request to perform the specific communication when a profile different from the profile used for the specific communication is active. In this case, when the predetermined condition is satisfied, the control unit 13 triggers the change process to change the profile used for the specific communication to the active state.

[0046] Furthermore, if the IoT device 100 is provided with a simple input interface using buttons or the like, the user can specify a profile to be enabled by operating the button, and if the specified profile is disabled, it can be considered that a predetermined condition is met to trigger a profile change process.

[0047] Furthermore, in the above embodiment, based on the current eSIM specifications for IoT devices, the eSIM 14 is assumed to be capable of setting a maximum of one profile to an active state. However, in the future, eSIMs 14 capable of simultaneously setting two or more predetermined profiles to an active state may also be used. Even in the case of an eSIM 14 capable of simultaneously setting multiple profiles to an active state, there may be situations in which it is preferable to quickly control the profile states within the IoT device 100, as exemplified below, rather than controlling the profile states by remote control from the eIM 300. In the following example, it is assumed that an eSIM 14 capable of storing three profiles, Profile #1 to Profile #3, and capable of simultaneously setting a maximum of two profiles to an active state is used in an IoT device 100 mounted on a vehicle.

[0048] (Example 1) In Example 1, the IoT device 100 is configured so that communication for vehicle data and emergency communication are grouped as one communication group #1, and personal communication for passengers is grouped as one communication group #2, with Profile #1 and Profile #3 being used for communication group #1 and Profile #2 being used for communication group #2. The purpose of using different profiles depending on the communication group is to prevent communication groups from competing for communication bandwidth. In this case, the IoT device 100 can be configured to communicate with communication group #1 and communication group #2 by enabling Profile #1 and Profile #2. Since the maximum number of profiles that can be enabled is two, Profile #3 is set to disabled.

[0049] Here, if a failure occurs in the mobile communication network accessed according to Profile #1, the IoT device 100 needs to change Profile #3 to an enabled state to continue communication in Communication Group #1. In this example, the eIM 300 can access the IoT device 100 via the mobile communication network accessed by the IoT device 100 according to Profile #2, but remote control from the eIM 300 may result in a long interruption of communication in Communication Group #1. Therefore, it is desirable to change Profile #3 to an enabled state in the IoT device 100 without remote control from the eIM 300. In this example, the control unit 13 is configured to trigger a change process to change Profile #3 to an enabled state when a failure occurs in the mobile communication network accessed according to Profile #1. Since the maximum number of profiles that can be set to an enabled state is two, by setting Profile #3 to an enabled state, Profile #1, which has experienced a failure in the accessed mobile communication network, is changed to an disabled state.

[0050] (Example 2) In this example, the IoT device 100 is configured to use Profile #1 for vehicle data communication, Profile #2 for personal communication with passengers, and Profile #3 for emergency communication. During non-emergency situations, Profile #1 and Profile #2 are enabled for vehicle data communication and personal communication. When emergency communication is required due to a vehicle accident, for example, Profile #2 must be disabled and Profile #3 must be enabled instead. Even in such a case, it is desirable to quickly enable Profile #3 in the IoT device 100 without remote control from the eIM 300. Therefore, in this example, the control unit 13 is configured to trigger a change process to enable Profile #3 when emergency communication is required. Since the maximum number of profiles that can be enabled is two, enabling Profile #3 disables Profile #2. In this example, the profile to be disabled is predetermined and stored in the control unit 13, and may be Profile #1 instead of Profile #2.

[0051] The above examples 1 and 2 are examples in which the eSIM 14 is configured so that all profiles that can be stored in the eSIM 14 or all profiles stored in the eSIM 14 cannot be simultaneously enabled. If the eSIM 4 has such limitations, it may be necessary to disable at least one profile. However, depending on the situation, it may become necessary to change this disabled profile to an enabled state. Therefore, when a predetermined condition for using an disabled profile is met, the control unit 13 initiates a change process to enable the profile, thereby enabling a quick change of the profile state without remote control from the eIM 300. In other words, the above embodiments are applicable even when the eSIM 14 is configured so that multiple profiles can be simultaneously enabled but not all profiles that can be stored in the eSIM 14 or all profiles stored in the eSIM 14 can be simultaneously enabled.

[0052] Furthermore, the above embodiment is applicable even when the eSIM 14 is configured so that all profiles can be set to the valid state.

[0053] For example, even if Profiles #1 to #3 in the above example can be set to the enabled state simultaneously, it is conceivable to operate the IoT device 100 by setting only one or two profiles to the enabled state in order to reduce power consumption. As an example, when profiles and communication types are associated with each other as in Example 2 above, it may be desirable to normally set a profile associated with a less frequently used communication type to the disabled state and quickly set the profile to the enabled state as needed. In such a case, the control unit 13 may be configured to trigger a change process to change the profile to the enabled state when communication using a profile set to the disabled state is requested, and to trigger a change process to change the profile to the disabled state when the communication is terminated.

[0054] Even if profiles are not associated with communication types, the IoT device 100 may be configured to dynamically control the number of profiles to be set to an enabled state depending on communication traffic in order to reduce power consumption. In this case, when the control unit 13 determines that the traffic volume has increased and communication cannot be performed using profiles set to an enabled state, it may trigger a change process to change disabled profiles to an enabled state. When the control unit 13 determines that the traffic volume has decreased and some of the enabled profiles can be set to an disabled state, it may trigger a change process to change some of the enabled profiles to an disabled state.

[0055] Furthermore, the present invention provides a program executed by the control unit 13 and a computer-readable storage medium storing the program. Furthermore, the present invention provides a method for controlling a profile shown in the sequences described in Figures 3 and 5, a program for causing a device having one or more processors to execute the control method, and a computer-readable storage medium storing the program.

[0056] This configuration makes it possible to activate profiles stored in the eSIM without communicating with other devices, thereby contributing to Goal 9 of the United Nations' Sustainable Development Goals (SDGs), which is to "Build resilient infrastructure, promote sustainable industrialization and foster innovation."

[0057] The invention is not limited to the above-described embodiment, and various modifications and variations are possible within the scope of the gist of the invention. [Explanation of symbols]

[0058] 10: Communication unit, 11: Memory device, 13: Control unit, 14: eSIM

Claims

1. an integrated circuit configured to store a plurality of profiles, each including information for accessing a mobile communication network, and one or more public keys including a first public key, wherein, when a command to change the state of the plurality of profiles between a valid state and an invalid state is received, one of the conditions for executing a process in accordance with the command is to receive, together with the command, signature information that can be verified by one of the one or more public keys; a communication means for accessing a mobile communication network and performing communication in accordance with information included in the profile set to the valid state; a storage means for storing a first private key corresponding to the first public key; a control means for transmitting, when a predetermined condition is satisfied, a first command for changing a first profile of the plurality of profiles that is in the invalid state to the valid state, together with first signature information generated by the first private key, to the integrated circuit; A wireless device comprising:

2. the integrated circuit further stores key identifiers for the one or more public keys; 2. The wireless device according to claim 1, wherein the control means generates the first signature information from processing information including a key identifier of the first public key using the first private key, and transmits the first command including the processing information and the first signature information to the integrated circuit.

3. 2. The wireless device of claim 1, wherein the predetermined condition is satisfied when the communication means detects a failure of the first mobile communication network while the communication means is connected to the first mobile communication network according to information contained in a second profile that is in the valid state among the plurality of profiles.

4. The wireless device of claim 3 , wherein the first profile includes information for connecting to a second mobile communication network that is different from the first mobile communication network.

5. 2. The wireless device of claim 1, wherein the predetermined condition is satisfied when a communication is requested via a second mobile communication network to which the communication means is connected in accordance with information contained in the first profile.

6. The wireless device according to claim 1 , wherein the predetermined condition is satisfied when a user operation indicating that the first profile is to be changed to an enabled state is performed.

7. the storage means further stores the first public key; 2. The wireless device according to claim 1, wherein the control means transmits the first public key stored in the storage means to the integrated circuit to store it therein in response to an initialization process being triggered.

8. 2. The wireless device of claim 1, wherein the control means generates the first private key and the first public key, stores the first private key in the storage means, and transmits the first public key to the integrated circuit to store it in response to an initialization process being triggered.

9. the storage means further stores a second public key; 9. The wireless device according to claim 8, wherein the control means, in response to the initialization process being triggered, transmits the second public key stored in the storage means to the integrated circuit to store it therein.

10. The wireless device of claim 9 , wherein the wireless device does not have a second private key corresponding to the second public key.

11. the storage means further stores flag information indicating whether the initialization process has been executed; The wireless device according to claim 7 , wherein the initialization process is triggered by powering on the wireless device when the flag information indicates that the initialization process has not been performed.

12. The wireless device of claim 7 , wherein the initialization process is triggered by a user operation.

13. 2. The wireless device of claim 1, wherein the integrated circuit is configured such that all profiles that can be stored in the integrated circuit cannot be set to the valid state simultaneously.

14. an integrated circuit configured to store a plurality of profiles, each containing information for accessing a mobile communication network, and one or more public keys, wherein, when a command to change the state of the plurality of profiles between a valid state and an invalid state is received, one of the conditions for executing a process in accordance with the command is to receive, together with the command, signature information that can be verified by one of the one or more public keys; a communication means for accessing a mobile communication network and performing communication in accordance with information included in the profile set to the valid state; a storage means; a control means for generating a first private key and a first public key corresponding to the first private key in response to the initialization process being triggered, transmitting the first public key to the integrated circuit to be stored therein, and storing the first private key in the storage means; A wireless device comprising:

15. an integrated circuit configured to store a plurality of profiles, each containing information for accessing a mobile communication network, and one or more public keys, wherein, when a command to change the state of the plurality of profiles between a valid state and an invalid state is received, one of the conditions for executing a process in accordance with the command is to receive, together with the command, signature information that can be verified by one of the one or more public keys; a communication means for accessing a mobile communication network and performing communication in accordance with information included in the profile set to the valid state; a storage means for storing a first private key and a first public key corresponding to the first private key; a control means for transmitting the first public key to the integrated circuit and storing the first public key in response to the initialization process being triggered; A wireless device comprising:

16. one or more processors; one or more memory devices; an integrated circuit configured to store a plurality of profiles, each containing information for accessing a mobile communication network, and one or more public keys, wherein, when a command to change the state of the plurality of profiles between a valid state and an invalid state is received, one of the conditions for executing a process in accordance with the command is to receive, together with the command, signature information that can be verified by one of the one or more public keys; 16. A program which, when executed by the one or more processors of a device having the program, causes the device to function as a wireless device according to any one of claims 1 to 15.

Images