Wireless devices and programs
IoT devices with embedded eSIMs can locally activate profiles using stored keys, addressing simultaneous activation limitations and ensuring continuous network access by bypassing remote control dependencies.
Patent Information
- Application Number
- JP2024067686
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2024-04-18
- Publication Date
- 2024-12-05
- Estimated Expiration
- 2044-04-18
AI Technical Summary
Existing IoT devices with embedded subscriber identity modules (eSIMs) cannot activate multiple profiles simultaneously due to remote control limitations, leading to communication disruptions when the primary network fails and the secondary network activation command cannot be sent.
The IoT device is configured to store multiple profiles and public keys, allowing local activation of a profile to a valid state using locally generated signature information based on a private key, independent of remote control signals.
Enables profile activation without external communication, ensuring continuous network access even when the primary network fails, enhancing resilience and reducing reliance on remote control systems.
Smart Images

Figure 0007595210000001_ABST
Abstract
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 the Internet of Things (IoT). [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 such as smartphones that are intended to be operated by humans, wireless devices for IoT (hereinafter referred to as IoT devices) are not usually provided with a user interface such as a touch panel. For this reason, Non-Patent Document 1 discloses that a device called 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, multiple profiles are stored in an eSIM, but two or more profiles cannot be in a valid state, i.e., enabled state, at the same time. A profile includes information necessary for an IoT device to access a mobile communication network also called a public land mobile network (PLMN), such as information indicating an accessible mobile communication network.
[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 written as PLMN #1) and a profile #2 for wirelessly accessing a mobile communication network 202 (also written as PLMN #2), and the profile #1 is enabled and the profile #2 is disabled. Therefore, the IoT device 100 wirelessly accesses the mobile communication network 201. The mobile communication network 201 and the mobile communication network 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 PUB#1, and the private key that forms a pair with PUB#1 is SEC#1.
[0008] In the state of Fig. 1, when the profile #2 stored in the eSIM of the IoT device 100 is to be activated, 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 1 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 sets the 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. According to Non-Patent Document 1, two or more profiles cannot be activated at the same time, so when profile #2 is activated, profile #1 is deactivated.
[0010] For example, assume that a failure occurs in mobile communication network 201 in the state of FIG. 1, and as a result, IoT device 100 is 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 eIM 300 cannot communicate with IoT device 100 due to the failure of mobile communication network 201, eIM 300 cannot send an activation command to IoT device 100, and therefore cannot activate profile #2.
[0011] In this way, the profile stored in the eSIM of the IoT device 100 can be controlled only 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 are 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 including information for accessing a mobile communication network without communicating with other devices. [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 including information for accessing a mobile communication network and one or more public keys including a first public key, and when a command is received to change the state of the plurality of profiles between the valid state and the invalid state, 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 verifiable by one of the one or more public keys; a communication means for accessing and communicating on the mobile communication network in accordance with information included in the profile set to the valid state; and a storage means for storing a first private key corresponding to the first public key; and when a predetermined condition is satisfied, generating first signature information using the first private key, and a first command for changing a first profile in the plurality of profiles that is in the disabled state to the enabled state; Do and and control means for transmitting both to said integrated circuit. Effect of the Invention
[0014] According to the present disclosure, a profile including information for accessing a mobile communication network can be activated without communicating with other devices. [Brief description of the drawings]
[0015] [Figure 1] FIG. 1 is a system configuration diagram for explaining an embodiment. [Diagram 2] A diagram showing an example of the configuration of an IoT device before initialization processing. [Diagram 3] FIG. 11 is a diagram showing an example of a sequence of an initialization process. [Figure 4] A diagram showing an example of the configuration of an IoT device after initialization processing. [Diagram 5] FIG. 4 is a diagram showing an example of a sequence of processes executed by a control unit. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0016] Hereinafter, the embodiments will be described in detail with reference to the accompanying drawings. Note that the following embodiments do not limit the invention according to the claims, and not all combinations of features described in the embodiments are essential to the invention. Two or more features among the multiple features described in the embodiments may be arbitrarily combined. In addition, the same reference numbers are used for the same or similar configurations, and duplicated descriptions are omitted.
[0017] FIG. 1 is a system configuration diagram for explaining an embodiment. As shown in FIG. 1, the eSIM of the 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 network 201 and the mobile communication network 202 are networks managed and operated by, for example, different communication operators (communication carriers) and are connected to the Internet 200. The eIM 300 connected to the Internet 200 stores a private key SEC#1 used to control the activation and deactivation of a 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 a configuration of the IoT device 100 before initialization processing. In this embodiment, the initialization processing means a process of storing a public key for controlling activation and deactivation of a profile stored in the eSIM 14 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 to be set to an active state to a maximum of one of the multiple profiles stored in the eSIM 14. The eSIM 14 is also configured to, when receiving a command to change the state of the multiple profiles stored in the eSIM 14 between an active state and an inactive state, receive, together with the command, signature information that can be verified by one of the one or more public keys stored in the eSIM 14 as one of the conditions for executing a process according to the command.
[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 control 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 composed of one or more non-volatile memory devices. The memory device 11 stores in advance information indicating 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 an initialization process has been performed. In the following description, as an example, flag information of a value 0 indicates that the initialization process has not been performed, and flag information of a value different from 0 indicates that the initialization process has been performed. Note that the eSIM_ID is information stored in the eSIM 14 as well, so 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 necessary.
[0022] In addition, 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 included 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 an initialization process when the power is turned on while the value of the flag information stored in the memory device 11 is 0. Fig. 3 shows a sequence when the IoT device 100 is turned on.
[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 execute 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 to execute initialization processing in S11. If the flag information has a value other than 0, the control unit 13 determines that execution of initialization processing is not necessary, and ends the processing in FIG.
[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 by any method. Here, it is assumed that a pair of a private key SECE#2 and a public key PUB#2 is generated. The control unit 13 assigns a key identifier ID#2 of 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 an 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] In addition, 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, which are stored in the memory device 11. 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 to store the information. The process of S15 corresponds to, for example, a process 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 an affirmative 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] Fig. 4 shows the configuration of the IoT device 100 after the initialization process. Compared to 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 is 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. For this reason, 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 that a failure has occurred in the mobile communication network when a wireless link with the mobile communication network cannot be established. Also, the communication unit 10 may detect that a failure has occurred in the mobile communication network when a wireless link with the mobile communication network is established but the Internet 200 cannot be accessed through the mobile communication network, that is, when a connection such as a protocol data unit (PDU) session or a bearer that connects the communication unit 10 and the Internet 200 is not established. Furthermore, the communication unit 10 may detect that a failure has occurred in the mobile communication network when it is continuously unable to transmit and receive packets to and from a server device on the Internet 200 through the accessed mobile communication network for a predetermined period of time or more. When a failure occurs in communication through the mobile communication network 201 accessed according to the profile #1 in the valid state, the control unit 13 starts a change process of changing the profile #2 in the invalid state to the valid state.
[0033] Upon starting the change process, the control unit 13 reads out information indicating the eSIM_ID, the private key SEC#2, the key identifier ID#2, and the counter value #2 from the memory device 11 in S21. Then, the control unit 13 generates processing information including information indicating the eSIM_ID, the key identifier ID#2, and the 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 the 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. The verification includes verifying whether the signature information was generated by 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, the 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 profile #2 to a valid state in S26, and changes the profile #1 to a invalid state instead. The eSIM 14 then 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. The control unit 13 updates the counter value #2 stored in the memory device 11 by incrementing it by 1 in S29.
[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 eSIM 14 of the IoT device 100 is stored with a public key (PUB#1) for remote control by the eIM 300 and a public key (PUB#2) for independent control that does not require the eIM 300 by the initialization process. In addition, the memory device 11 of the IoT device 100 is stored with a private key (SEC#2) corresponding to the public key for independent control by the initialization process. Then, when the control unit 13 of the IoT device 100 detects a trigger for changing a profile that is in an invalid state to an active state, the control unit 13 transmits information indicating the profile to be in an active state, processing information required for changing the profile to an active state, and signature information of the processing information based on the stored private key to the eSIM 14. With this configuration, the profile can be enabled in the IoT device 100 without the involvement of the eIM 300.
[0038] <Other embodiments> In the following, a modified embodiment of the above embodiment will be described. In the above embodiment, in the initialization process, the key generation unit 12 generates a pair of a private key SEC#2 and a public key PUB#2. However, the pair of the private key SEC#2 and the public key PUB#2 and 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. In addition, in S14, the control unit 13 reads out a set of the public key PUB#1, the key identifier ID#1, and the counter value #1 from the memory device 11, 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, the set of the public key PUB#1, the key identifier ID#1, and the counter value #1 is stored in the memory device 11, and in S15, the set of the public key PUB#1, the key identifier ID#1, and the counter value #1 is notified to the eSIM 14 together with the set of the public key PUB#2, the key identifier ID#2, and the counter value #2. This is because, when the set of the public key, the key identifier, and the counter value is stored in the eSIM 14, another set of the public key, the key identifier, and the counter value cannot be added later. However, when a new command for adding another set of the public key, the key identifier, and the counter value to the eSIM 14 is defined, the set of the public key PUB#1, the key identifier ID#1, and the counter value #1 is stored in the eSIM 14 in advance, so that it is not necessary 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 the public key PUB#2, the key identifier ID#2, and the 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, 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 turning on the power of the IoT device 100 when the flag information indicates that the initialization process is not being performed. Therefore, once the initialization process is performed, the initialization process is not performed when the IoT device 100 is subsequently powered on. However, in consideration of the need to perform the initialization process at a later timing, the flag information can be configured to be changeable to 0. For example, the flag information can 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 can be configured to be provided with a simple input interface using a button or the like, and the flag information can be set to 0 by a button operation (user operation). By setting the flag information to 0, the initialization process is performed 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 the IoT device 100 is shipped, or may be performed between the shipment and installation of the IoT device 100, or may be performed when the IoT device 100 is installed.
[0043] Furthermore, in the above embodiment, the eSIM 14 stores two profiles, profile #1 and profile #2, but the present invention can also be applied to an eSIM 14 that can store three or more profiles. In this case, when a failure occurs in the mobile communication network accessed according to the profile in the valid state, the control unit 13 selects a profile to be made valid by any method from other profiles in the invalid state. If communication cannot be performed even with the selected profile, the control unit 13 repeatedly makes one profile selected from the multiple profiles in the invalid state valid until communication becomes possible. As an example, a priority order is set for the multiple profiles, and the control unit 13 selects a profile to be made valid from the multiple profiles in the invalid state according to the priority order.
[0044] Furthermore, the control unit 13 may be configured to, when a failure occurs in a mobile communication network accessed according to a profile in an enabled state, select only a profile that accesses a mobile communication network different from the mobile communication network in question as a profile to be enabled. In other words, when communication via the accessed mobile communication network cannot be performed, the control unit 13 may be configured to select, from among a plurality of 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 becomes possible.
[0045] In the above embodiment, the predetermined condition for the control unit 13 to trigger the profile change process is that a failure occurs in the mobile communication network accessed according to the profile in the valid state. However, the predetermined condition for triggering the profile change process is not limited to that a failure occurs in the mobile communication network accessed according to the profile in the valid state. For example, consider a configuration in which a profile to be used in a 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 that a request to perform the specific communication occurs when a profile different from the profile used in the specific communication is in the valid state. In this case, when the predetermined condition is satisfied, the control unit 13 triggers the change process to change the profile used in the specific communication to the valid 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 a button, and if the specified profile is disabled, a predetermined condition for triggering a profile change process can be satisfied.
[0047] In the above embodiment, based on the current specifications of the eSIM of the IoT device, the eSIM 14 can set only one profile to the active state at most. However, in the future, an eSIM 14 capable of simultaneously setting two or more predetermined profiles to the active state may be used. Here, even in the case of an eSIM 14 capable of simultaneously setting multiple profiles to the active state, there are situations in which it is preferable to control the profile state quickly within the IoT device 100 as illustrated below, rather than controlling the profile state 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 the 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 to group communication for vehicle data and emergency communication into one communication group #1, and personal communication for passengers into one communication group #2, with profile #1 and profile #3 used for communication group #1 and profile #2 used for communication group #2. The purpose of using different profiles depending on the communication group is to avoid the communication groups competing for communication bands. In this case, the IoT device 100 can be configured to communicate in the communication groups #1 and #2 by setting profile #1 and profile #2 to an enabled state. Since the maximum number of profiles that can be set to an enabled state is two, profile #3 is set to an disabled state.
[0049] Here, when a failure occurs in the mobile communication network accessed according to the profile #1, the IoT device 100 needs to change the profile #3 to an active state to continue the communication of the 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 the profile #2, but the interruption time of the communication of the communication group #1 may be long with remote control from the eIM 300. Therefore, it is desirable to change the profile #3 to an active 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 the profile #3 to an active state when a failure occurs in the mobile communication network accessed according to the profile #1. Since the maximum number of profiles that can be set to an active state is 2, the profile #1 in which the mobile communication network to be accessed has a failure is changed to an inactive state by changing the profile #3 to an active state.
[0050] (Example 2) In this example, the IoT device 100 is configured to use profile #1 for vehicle data communication of the automobile, profile #2 for personal communication of passengers, and profile #3 for emergency communication. During non-emergency situations, profile #1 and profile #2 are set to the enabled state to perform vehicle data communication and personal communication. When performing emergency communication due to detection of an automobile accident, for example, profile #2 needs to be set to the disabled state and profile #3 needs to be set to the enabled state instead. Even in such a case, it is desirable to quickly change profile #3 to the enabled state 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 change profile #3 to the enabled state when emergency communication is required. Since the maximum number of profiles that can be set to the enabled state is 2, profile #2 is changed to the disabled state by setting profile #3 to the enabled state. In this example, the profile to be disabled is determined in advance and stored in the control unit 13, and may be profile #1 instead of profile #2.
[0051] The above examples 1 and 2 are for cases where the eSIM 14 is configured such that all profiles that can be stored in the eSIM 14 or that are stored in the eSIM 14 cannot be set to an active state at the same time. If the eSIM 4 has such a restriction, it may be necessary to set at least one profile to an inactive state, but depending on a change in the situation, it may be necessary to change this inactive profile to an active state. Therefore, when a predetermined condition for using an inactive profile is satisfied, the control unit 13 starts a change process to change the profile to an active state, so that the state of the profile can be quickly changed without remote control from the eIM 300. In other words, the above embodiment is applicable even when the eSIM 14 is configured such that multiple profiles can be set to an active state at the same time, but all profiles that can be stored or that are stored cannot be set to an active state at the same time.
[0052] Furthermore, the above embodiment is applicable even in the case where the eSIM 14 is configured so that all profiles can be set to a valid state.
[0053] For example, even if profiles #1 to #3 in the above example can be set to the active state at the same time, it is conceivable to operate the IoT device 100 by setting only one or two profiles to the active state in order to reduce power consumption. As an example, in the case where profiles and communication types are associated with each other as in the above example 2, it may be desirable to normally set a profile associated with a communication type that is used less frequently to the inactive state and quickly set the profile to the active state as necessary. In such a case, the control unit 13 may be configured to trigger a change process to change the profile to the active state when communication using a profile set to the inactive state is requested, and to trigger a change process to change the profile to the inactive state when the communication is terminated.
[0054] Even if the profile and the communication type are not associated with each other, the IoT device 100 may be configured to dynamically control the number of profiles to be set to the enabled state according to the 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 with the profiles set to the enabled state, the control unit 13 may trigger a change process to change the profiles set to the disabled state to the enabled state. When the control unit 13 determines that the traffic volume has decreased and some of the profiles set to the enabled state can be set to the disabled state, the control unit 13 may trigger a change process to change some of the profiles set to the enabled state to the 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 Fig. 3 and Fig. 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] With the above configuration, it is possible to activate the profile stored in the eSIM without communicating with other devices, which will contribute to Goal 9 of the United Nations Sustainable Development Goals (SDGs) "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 is received to change a state of the plurality of profiles between a valid state and an invalid state, one of the conditions for executing a process according to 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 a valid state; a storage means for storing a first private key corresponding to the first public key; a control means for generating first signature information using the first private key when a predetermined condition is satisfied, and transmitting the first signature information to the integrated circuit together with a first command for changing a first profile, which is in the invalid state among the plurality of profiles, to the valid state; A wireless device comprising:
2. the integrated circuit further stores a key identifier for the one or more public keys; 2. The wireless device of claim 1, wherein the control means generates the first signature information using the first private key from processing information including a key identifier of the first public 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 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 a change to the first profile being enabled is performed.
7. The storage means further stores the first public key; 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 for storage in response to an initialization process being triggered.
9. The storage means further stores a second public key; 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 for storage therein.
10. The wireless device of claim 9 , wherein the wireless device does not have a second private key that corresponds to the second public key.
11. The storage means further stores flag information indicating whether the initialization process has been executed or not; The wireless device according to claim 7 , wherein the initialization process is triggered by the wireless device being powered on 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 storable in the integrated circuit cannot be set to the valid state simultaneously.
14. 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, the integrated circuit being configured to, when receiving a command to change a state of the plurality of profiles between a valid state and an invalid state, receive, together with the command, signature information that can be verified by one of the one or more public keys, as one of conditions for executing a process according to the command; a communication means for accessing a mobile communication network and performing communication in accordance with information included in the profile set to a 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 an 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 including information for accessing a mobile communication network, and one or more public keys, the integrated circuit being configured to, when receiving a command to change a state of the plurality of profiles between a valid state and an invalid state, receive, together with the command, signature information that can be verified by one of the one or more public keys, as one of conditions for executing a process according to the command; a communication means for accessing a mobile communication network and performing communication in accordance with information included in the profile set to a 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 an 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 including information for accessing a mobile communication network, and one or more public keys, the integrated circuit being configured to, when receiving a command to change a state of the plurality of profiles between a valid state and an invalid state, receive, together with the command, signature information that can be verified by one of the one or more public keys, as one of conditions for executing a process according to the command; 16. A program which, when executed by the one or more processors of an apparatus having the wireless device, causes the apparatus to function as a wireless device according to any one of claims 1 to 15.
Citation Information
Patent Citations
Biometric smart card for mobile devices
JP2011515724A
Artificial satellite, satellite communication system, broadcast method, and program
JP2019121886A
Method and apparatus for installing and managing multiple eSIM profiles
JP2023539038A
JPP7284881B
Storage device authentication
US20100293383A1
