SIM and information processing device
The SIM with an applet area and stored program simplifies IoT device communication by eliminating the need for LwM2M module modifications and interoperability testing, facilitating seamless communication with IoT platforms using low-power protocols.
Patent Information
- Application Number
- JP2024186950
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2024-10-23
- Publication Date
- 2025-12-11
- Estimated Expiration
- 2044-10-23
AI Technical Summary
Existing IoT devices require costly implementation of LwM2M communication functions in the communication module or application layer, and interoperability testing is necessary each time a new model or communication module is introduced, leading to time-consuming operations.
A SIM with an applet area and a memory unit storing a first program that executes communication processing according to a predetermined protocol, allowing IoT devices to communicate without modifying the application or communication modules, and eliminating the need for interoperability testing.
Simplifies IoT device communication operations by enabling direct communication with IoT platforms using low-power protocols like LwM2M, reducing the need for interoperability testing and initial setup complexity.
Smart Images

Figure 0007784504000001_ABST
Abstract
Description
[Technical Field]
[0001] The present invention relates to a SIM and an information processing device, and more particularly to a SIM and an information processing device that provide technology that enables dramatic simplification of operations related to communication of IoT devices. [Background technology]
[0002] To save power, IoT (Internet of Things) devices often use low-power communication protocols such as LwM2M (Lightweight M2M), an IoT protocol developed by OMA (Open Mobile Alliance), and MQTT (Message Queue Telemetry Transport), developed by OASIS (Organization for the Advancement of Structured Information Standards).
[0003] In addition, a technology has been proposed for communication between an IoT device and a cloud service, in which if the IoT device is capable of transmitting multiple types of data, the data is transmitted to a cloud service application that is appropriate for the type of data (see, for example, Patent Document 1). [Prior art documents] [Patent documents]
[0004] [Patent Document 1] Japanese Patent Publication No. 2023-141501 Summary of the Invention [Problem to be solved by the invention]
[0005] However, there are few communication modules that implement communication functions based on low-power communication protocols for IoT devices. For this reason, when introducing IoT devices, it was previously necessary to implement LwM2M communication functions in the communication module or application layer, which was costly.
[0006] Furthermore, interoperability testing (IOT) is required to use IoT devices and communication modules on the communication networks of mobile communication carriers. In other words, interoperability testing must be completed each time a new model or a communication module with no proven track record is introduced.
[0007] For example, even if an IoT device is widely used, if the device's communication module or application layer is modified to include LwM2M functionality, it may not be able to be used with some mobile carriers' IoT platforms unless interoperability testing is completed again. As such, conventional operations related to IoT device communications have been time-consuming.
[0008] An object of one aspect of the present invention is to provide a technology that enables dramatic simplification of operations related to communication between IoT devices. [Means for solving the problem]
[0009] A SIM according to one embodiment of the present invention is a Subscriber Identity Module (SIM) for use in an IoT device, and has an applet area, which is a storage area used as an applet, and is equipped with a memory unit in which a first program that causes the IoT device to execute communication processing in accordance with a predetermined communication protocol is stored in the applet area, and a processing execution unit that is a program implemented in the IoT device and executes communication processing by the first program based on instructions from a second program belonging to an application layer.
[0010] A data processing method according to one embodiment of the present invention is a data processing method for a SIM used in an IoT device, wherein the SIM has an applet area which is a memory area used as an applet, a first program which causes the IoT device to execute communication processing in accordance with a predetermined communication protocol is stored in the applet area, and the SIM includes a step of executing communication processing by the first program based on instructions from a second program which is a program implemented in the IoT device and belongs to an application layer. [Effects of the Invention]
[0011] According to one aspect of the present invention, it is possible to provide a technology that enables dramatic simplification of operations related to communication of IoT devices. [Brief explanation of the drawings]
[0012] [Figure 1] FIG. 1 is a diagram showing an example of the configuration of a communication system according to an embodiment of the present invention. [Figure 2] FIG. 2 is a diagram illustrating an example of the functional configuration of a first IoT device. [Figure 3] FIG. 2 is a diagram illustrating an example of the functional configuration of a second IoT device. [Figure 4] FIG. 2 is a block diagram showing an example of the functional configuration of a USIM. [Figure 5] FIG. 10 is a diagram illustrating an example of a communication protocol stack when communication is controlled by an applet in accordance with the LwM2M communication protocol. [Figure 6] FIG. 1 is a diagram illustrating a connection between an applet of a USIM of an IoT device and an IoT platform. [Figure 7] FIG. 10 is a diagram illustrating data exchange between an applet and an application. [Figure 8] FIG. 10 is a diagram illustrating another example of data exchange between an applet and an application. [Figure 9] 10 is a flowchart illustrating an example of the flow of a data transmission process. [Figure 10] 10 is a flowchart illustrating an example of the flow of a data reception process. [Figure 11] 10 is a flowchart illustrating another example of the flow of a data reception process. [Figure 12] FIG. 1 is a block diagram illustrating an example of the hardware configuration of a computer that realizes an IoT device. DETAILED DESCRIPTION OF THE INVENTION
[0013] Hereinafter, an embodiment of the present invention will be described with reference to the drawings.
[0014] (Communication System Configuration) 1 is a diagram showing an example of the configuration of a communication system according to an embodiment of the present invention. In the communication system 10 shown in the figure, multiple IoT (Internet of Things) devices are connected to an IoT platform 90 of a mobile communication carrier.
[0015] In this example, IoT device 30 and IoT device 60 are shown as IoT devices, but in reality many more IoT devices are connected to IoT platform 90. IoT platform 90 includes, for example, an access point, a core network, a server that analyzes data collected from IoT device 30, and a server that distributes software to IoT devices.
[0016] IoT device 30 and IoT device 60 may conform to any of the following communication methods: 3G (3rd Generation) communication method, LTE (Long Term Evolution) communication method, 5G (5th Generation) communication method, and 6G (6th Generation) communication method or later.
[0017] In the communication system 10, a low-power consumption communication protocol is used for communication between IoT devices. As an example, the communication system 10 employs LwM2M (Lightweight M2M), a protocol for IoT established by the Open Mobile Alliance (OMA) for the purpose of power saving in IoT devices. Here, the IoT device 30 and the IoT device 60 have different implementation methods for the LwM2M communication function. As will be described in detail later, in the IoT device 30, for example, the LwM2M communication function is implemented in an application, while in the IoT device 60, for example, the LwM2M communication function is stored in a USIM.
[0018] (Functional configuration of the first IoT device) 2 is a diagram illustrating an example of the functional configuration of the IoT device 30. In this example, the IoT device 30 includes an application 31, a communication module 32, and a USIM (Universal Subscriber Identity Module) 33.
[0019] The application 31 is, for example, software that belongs to the application layer of the IoT device 30, and is configured to include device information 41 and an LwM2M communication function 42. The device information 41 describes, for example, information related to the model and installation location of the IoT device 30. The LwM2M communication function 42 is configured, for example, by a program for causing the IoT device 30 to communicate with the IoT platform 90 in accordance with the LwM2M communication protocol.
[0020] The communication module 32 transmits data supplied from the application 31 via a bearer corresponding to a wireless communication method such as 3G, LTE, 5G, or 6G. The communication module 32 also receives data transmitted from the IoT platform 90 via a bearer corresponding to a wireless communication method such as 3G, LTE, 5G, or 6G, and supplies the data to the application 31. The communication module 32 may be configured as, for example, a modem.
[0021] The USIM 33 is mounted as a subscriber identity module in the IoT device 30 and is configured as, for example, a removable card. The USIM 33 has a storage area with a predetermined storage capacity, and in this example, authentication information 51 is stored in the storage area.
[0022] In the case of the IoT device 30, the device vendor implements an LwM2M communication function in the application 31. This enables the IoT device 30 to communicate with the IoT platform 90 according to the LwM2M communication protocol. In other words, it becomes possible for the IoT device 30 to communicate with the IoT platform 90 using a low-power consumption communication protocol.
[0023] Although the example in which the LwM2M communication function is implemented in the application 31 by the device vendor has been described here, the LwM2M communication function may also be implemented in the middleware of the communication module 32. Even in this case, it is still possible to allow the IoT device 30 to communicate with the IoT platform 90 using a low-power communication protocol.
[0024] That is, in the case of FIG. 2, the device vendor modifies the IoT device 30 or the communication module 32 to implement the LwM2M communication function.
[0025] (Functional configuration of the second IoT device) 3 is a diagram illustrating an example of the functional configuration of an IoT device 60. In this example, the IoT device 60 includes an application 61, a communication module 62, and a USIM 63.
[0026] The application 61 is, for example, software that belongs to the application layer of the IoT device 60, and is configured to include device information 71. The device information 71 describes information related to, for example, the model and installation location of the IoT device 30.
[0027] In the example of FIG. 3, unlike the case of FIG. 2, the application 61 does not include an LwM2M communication function.
[0028] The communication module 62 transmits data supplied from the USIM 63 via a bearer corresponding to a wireless communication method such as 3G, LTE, 5G, or 6G. Data exchange between the USIM 63 and the communication module 62 may be performed via middleware or the like implemented in the IoT device 60, for example.
[0029] Furthermore, the communication module 62 receives data transmitted from the IoT platform 90 via a bearer corresponding to a wireless communication method such as 3G, LTE, 5G, or 6G, and supplies the data to the USIM 63. The communication module 62 may be configured as, for example, a modem.
[0030] The USIM 63 is installed in the IoT device 60 as a subscriber identity module, and is configured as, for example, a removable card.
[0031] The USIM 63 has a storage area with a predetermined storage capacity, and in this example, authentication information 81 and an LwM2M communication function 82 are stored in the storage area. The LwM2M communication function 82 is configured by, for example, a program for causing the IoT device 60 to communicate with the IoT platform 90 in accordance with the LwM2M communication protocol.
[0032] In the case of the IoT device 60, the LwM2M communication function 82 is stored in the USIM 63. This enables the IoT device 60 to communicate with the IoT platform 90 according to the LwM2M communication protocol. That is, it becomes possible for the IoT device 60 to communicate with the IoT platform 90 using a low-power consumption communication protocol.
[0033] In the case of FIG. 3, the device vendor does not need to modify the IoT device 60 or the communication module 62 to implement the LwM2M communication function.
[0034] (Interoperability Test) Inter-Operability Testing (IOT) may be required to use IoT devices and communication modules on the communication networks of mobile communication carriers. For example, in IoT platforms that use the communication networks of some mobile communication carriers, it may be required to complete interoperability testing each time a new model or a communication module with no proven track record is introduced.
[0035] For example, even if an IoT device 30 is in widespread use, if it is modified to implement an LwM2M communication function or the like in the application layer as shown in Figure 2, it may not be usable on the communication networks of some mobile communication operators unless an interoperability test is completed again.
[0036] On the other hand, in the example of Fig. 3, an IoT device equipped with a USIM 63 and a communication module 62 does not require interoperability testing, even for new models. For example, if the communication module 62 is used in a variety of IoT devices, using the USIM 63 makes it possible for most IoT devices to be used on IoT platforms related to the communication networks of mobile communication carriers as described above, without conducting interoperability testing.
[0037] (USIM functional configuration) 4 is a block diagram showing an example of the functional configuration of the USIM 63. In this example, the storage unit 100 of the USIM 63 is divided into an area 101 and an area 102. The area 101 stores, for example, information required for connecting to the communication network of a mobile communication carrier. In this example, the area 101 stores authentication information 81.
[0038] Area 102 stores, for example, information corresponding to the above-mentioned LwM2M communication function 82, and in this example, stores basic setting information 131 and a protocol execution control program 132. Area 102 is also called an applet area. Area 102 is a highly tamper-resistant area, and can store, for example, information other than information necessary for connecting to the communication network of a mobile communication carrier.
[0039] A program stored in the USIM and running on the USIM may also be called an applet. The information stored in area 102 may be automatically updated by, for example, a distribution OTA server.
[0040] As such, the USIM 63 of this embodiment has an applet area, which is a memory area used as an applet, and the applet area has a memory unit that stores a first program (e.g., protocol execution control program 132) that causes an IoT device to execute communication processing in accordance with a predetermined communication protocol (e.g., LwM2M).
[0041] The basic setting information may be, for example, a connection destination URL of the IoT device 60. The basic setting information may also be, for example, LwM2M operation parameters. The LwM2M operation parameters may be, for example, Lifetime, Binding, Mode, etc.
[0042] The protocol execution control program 132 may be a program that runs on the USIM and controls the execution of communication processing in accordance with the LwM2M communication program. The USIM 63 has a CPU, an interface, etc., and the program stored in the area 102 is executed by the CPU, and data is exchanged between the application 61 or the communication module 62 via the interface.
[0043] The protocol execution control program 132, for example, acquires data to be transmitted based on a command output from the application 61, and notifies the communication module 62 via the interface of an instruction to transmit packets in accordance with the LwM2M communication protocol. The protocol execution control program 132 also supplies data obtained by receiving packets transmitted from the IoT platform 90 in accordance with the LwM2M communication protocol to the application 61 via the interface based on a command output from the application 61. That is, the program stored in the area 102 is executed by the CPU, thereby executing communication processing in accordance with the LwM2M communication protocol.
[0044] As such, the USIM 63 of this embodiment is a program implemented in an IoT device, and has a processing execution unit that executes communication processing by a first program based on instructions from a second program (e.g., application 61) belonging to the application layer.
[0045] Hereinafter, the program stored in the area 102 will be referred to as the applet 102 where appropriate. When the applet 102 runs on the USIM 63, the IoT device 60 communicates with the IoT platform 90 in accordance with the LwM2M communication protocol.
[0046] 5 is a diagram showing an example of a communication protocol stack when communication according to the LwM2M communication protocol is controlled by applet 102. As shown in the diagram, the communication protocol stack used for sending or receiving transmitted / received data includes LwM2M, CoAP (Constrained Application Protocol), DTLS (Datagram Transport Layer Security), and UDP.
[0047] (Connection between applet and IoT platform) FIG. 6 is a diagram illustrating a connection between the applet 102 of the USIM 63 of the IoT device 60 and the IoT platform 90. As shown in FIG.
[0048] 3, an IoT client application 151 is running on an IoT device 60. The IoT client application 151 acquires information detected by a sensor or the like included in the IoT device 60 and provides the information to an IoT server 172 of the IoT platform 90. The IoT client application 151 may be, for example, a part of the application 61 in FIG.
[0049] The IoT client application 151 sends, for example, data relating to information detected by a sensor or the like included in the IoT device 60 (hereinafter referred to as detected data) to the applet 102 of the USIM 63.
[0050] The applet 102 transmits the sensing data acquired from the IoT client application 151 to the communication module 62. At this time, the applet 102 packetizes the sensing data according to, for example, the LwM2M communication protocol and transmits the packetized data to the communication module 62.
[0051] The communication module 62 transmits, for example, packets acquired from the applet 102 via a bearer corresponding to a wireless communication method such as 3G, LTE, 5G, 6G, etc. The transmitted packets are received by the IoT server 172 of the IoT platform 90.
[0052] Furthermore, the IoT server 172 transmits a request for transmitting detection data to the IoT device 60 as needed. As an example, the IoT server 172 may transmit data indicating a request for changing the threshold value of the sensor of the IoT device 60 as needed. Data related to such a request will be referred to as request data.
[0053] Furthermore, the applet 102 acquires packets based on signals received by the communication module 62 according to, for example, the LwM2M communication protocol, and supplies the application 61 with requested data obtained from the acquired packets.
[0054] In this way, the IoT device transmits and receives data to and from other devices (e.g., IoT server 172), and the first program (e.g., protocol execution control program 132) supplies first data (e.g., detection data) supplied from the second program (e.g., application 61) to the communication module of the IoT device according to a predetermined communication protocol (e.g., LwM2M), causing the communication module to generate a wireless signal to be transmitted to the other device, and acquires second data (e.g., request data) transmitted from the other device, which is data obtained based on the wireless signal received by the communication module of the IoT device.
[0055] That is, the IoT device 60 and the IoT server 172 transmit and receive data according to, for example, the LwM2M communication protocol.
[0056] The distribution OTA server 171 transmits data for updating the applet 102 as a wireless signal via a bearer corresponding to a wireless communication method such as 3G, LTE, 5G, or 6G, and the data is received by the communication module 62 of the IoT device 60. The communication module 62 supplies data obtained from the received wireless signal to the applet 102 of the USIM 63. As a result, the applet 102 is updated.
[0057] The data updated by the delivery OTA server 171 may be, for example, the basic setting information 131 or the protocol execution control program 132.
[0058] That is, the IoT device 60 may be connected to an IoT platform 90 including a distribution OTA server 171, and basic setting information 131 stored in the area 102, the basic setting information including information indicating a connection destination address of the IoT device 60 or information indicating operation parameters related to a predetermined communication protocol, may be distributed by the distribution OTA server 171. Also, update data for the first program (protocol execution control program 132) stored in the applet area may be further distributed by the distribution OTA server 171.
[0059] The protocol used when the delivery OTA server 171 and the applet 102 communicate with each other may be HTTPS over BIP (Bearer Independent Protocol).
[0060] (Transferring information between applets and applications) Next, we will explain the exchange of data between the IoT client application 151 and the applet 102. For example, when the IoT client application 151 supplies data to be provided to the IoT platform 90 to the applet 102, the applet 102 can read the data by issuing an AT+CSIM command, for example.
[0061] On the other hand, for example, when a request for the IoT device 60 is received from the IoT platform 90, request data related to the received request is supplied from the communication module 62 to the applet 102. An example of a request from the IoT platform 90 to the IoT device 60 is a request to change a threshold value set for detection by a sensor. In this case, the applet 102 needs to notify the IoT client application 151 of the request data.
[0062] FIG. 7 is a diagram for explaining the exchange of data between the applet 102 and the application 61. In FIG.
[0063] For example, when the detection data detected by a sensor of the IoT device 60 is to be transmitted to the IoT platform 90, the detection data is supplied from the application 61 to the applet 102. In this case, the application 61 supplies the detection data to be transmitted to the IoT platform 90 to the applet 102 by causing the applet 102 to read the detection data using, for example, an AT+CSIM command.
[0064] For example, when the IoT server 172 requests a change in the threshold value of a sensor of the IoT device 60, the applet 102 supplies the application 61 with request data relating to the request.
[0065] 7, the application 61 periodically polls the applet 102 using the AT+CSIM command. The applet 102 supplies the application 61 with requested data from the IoT platform 90 in response to the polling using the AT+CSIM command.
[0066] In this way, for example, it becomes possible to change the threshold value of the sensor in response to a request from the IoT platform 90.
[0067] 8 is a diagram illustrating another example of data exchange between applet 102 and application 61. Note that although the AT+CSIM command is issued in the above description, it is also possible to implement a unique command equivalent to the AT+CSIM command to read data.
[0068] For example, when the detection data detected by a sensor of the IoT device 60 is to be transmitted to the IoT platform 90, the detection data is supplied from the application 61 to the applet 102. In this case, the application 61 supplies the detection data to be transmitted to the IoT platform 90 to the applet 102 by causing the applet 102 to read the detection data using an AT+CSIM command, as in the case of FIG.
[0069] For example, when the IoT server 172 requests a change in the threshold value of a sensor of the IoT device 60, the applet 102 supplies the application 61 with request data relating to the request.
[0070] 8, when the applet 102 receives request data for the IoT device 60 from the IoT platform 90, it outputs a proactive command to the application 61. A proactive command is used when an applet actively outputs a command to a device. In this case, for example, the applet 102 outputs a proactive command that causes the application 61 to output an AT+CIM command.
[0071] When the application 61 receives the proactive command, it instructs the applet 102 to supply the requested data by an AT+CSIM command. The applet 102 supplies the requested data from the IoT platform 90 to the application 61 in response to the AT+CSIM command.
[0072] Alternatively, when the applet 102 receives request data for the IoT device 60 from the IoT platform 90, it may output a proactive command to the application 61 to instruct the application 61 to change the threshold value of the sensor, etc. In this case, when the application 61 receives the proactive command, it will change the threshold value of the sensor in response to the instruction of the proactive command.
[0073] Furthermore, when the applet 102 receives request data for the IoT device 60 from the IoT platform 90, it may transmit a message to the application 61 by SMS (Short Message Service). In this case, when the application 61 receives the message, it issues an AT+C SIM command in response to the message. Then, the applet 102 supplies the request data from the IoT platform 90 to the application 61 as a response to the AT+C SIM command.
[0074] In this way, for example, it becomes possible to change the threshold value of the sensor in response to a request from the IoT platform 90. Unlike the method in Fig. 7, the method in Fig. 8 does not require polling, so it is expected that the system will operate with reduced power consumption.
[0075] (An example of data transmission processing) Next, an example of data transmission processing by the applet 102 will be described. This processing is executed, for example, when detecting data detected by a sensor of the IoT device 60 is transmitted to the IoT platform 90. Fig. 9 is a flowchart illustrating an example of the flow of the data transmission processing.
[0076] In step S101, the applet 102 determines whether or not an AT+C SIM command has been received from the application 61, and waits until it is determined that the AT+C SIM command has been received. If it is determined in step S101 that the AT+C SIM command has been received, the process of step S102 is executed.
[0077] In step S102, the applet 102 reads the detected data in accordance with the AT+C SIM command determined to have been received in the process of step S101. As a result, the detected data is supplied from the application 61 to the applet 102.
[0078] In step S103, the applet 102 outputs the detection data read in the process of step S102 in accordance with the LwM2M communication protocol to the communication module 62. As a result, the communication module 62 transmits a wireless signal corresponding to the detection data.
[0079] In this way, the data transmission process is carried out.
[0080] (An example of data reception processing) Next, we will explain an example of data reception processing by the applet 102. This processing is executed, for example, when a request is made from the IoT server 172 to change the threshold value of the sensor of the IoT device 60. Fig. 10 is a flowchart explaining an example of the flow of data reception processing.
[0081] In step S121, applet 102 determines whether or not it has received a polling signal from application 61, and waits until it is determined that it has received a polling signal. Here, it is assumed that polling signals are periodically output to applet 102 by the AT+CSIM command.
[0082] If it is determined in step S121 that a polling signal has been received, the process proceeds to step S122.
[0083] In step S122, the applet 102 supplies the request data as a response to the polling to the application 61. As a result, for example, the application 61 changes the threshold value of the sensor in response to a request from the IoT platform 90.
[0084] If the IoT device 60 has not yet received the request data from the IoT server 172, the applet 102 may supply null data to the application 61 in step S122, or may return an error in response to the polling.
[0085] In this way, the data reception process is executed.
[0086] (Another example of data reception processing) Next, we will explain another example of data reception processing by the applet 102. This processing is executed, for example, when a request is made from the IoT server 172 to change the threshold value of the sensor of the IoT device 60. Fig. 11 is a flowchart explaining another example of the flow of data reception processing.
[0087] In step S141, the applet 102 determines whether or not the request data has been acquired from the IoT server 172, and waits until it is determined that the request data has been acquired. If it is determined in step S141 that the request data has been acquired, the process proceeds to step S142.
[0088] In step S142, the applet 102 issues a proactive command to the application 61 to output an AT+CIM command.
[0089] In step S143, applet 102 determines whether or not it has received the AT+C SIM command output by application 61 in response to the proactive command output in step S142. Then, applet 102 waits until it is determined that it has received the AT+C SIM command output by application 61. If it is determined in step S143 that it has received the AT+C SIM command, it executes the processing of step S144.
[0090] In step S144, the applet 102 supplies the request data from the IoT platform 90 to the application 61 as a response to the AT+CSIM command determined to have been received in step S143.
[0091] In step S142, the applet 102 may output a proactive command to the application 61 to instruct the application 61 to change the threshold value of the sensor, etc. In this case, the application 61 will change the threshold value of the sensor in response to the instruction of the proactive command.
[0092] Also, in step S142, applet 102 may send a message by SMS to application 61. Then, in step S143, it may be determined whether or not an AT+C SIM command output by application 61 in response to the message output in step S142 has been received.
[0093] In this way, the data reception process may be performed.
[0094] (Example of IoT device configuration) IoT devices such as the IoT device 30 and the IoT device 60 can be realized, for example, by causing one or more computers to execute programs. Fig. 12 is a block diagram showing an example of the hardware configuration of the computer in this embodiment.
[0095] As shown in FIG. 12, a computer 500 can be configured by a computer including a bus 510, a processor 501, a main memory 502, an auxiliary memory 503, a communication interface 504, and an input / output interface 505.
[0096] The processor 501, main memory 502, auxiliary memory 503, communication interface 504, and input / output interface 505 are connected to one another via a bus 510. A drive 506 and a sensor 507 are connected to the input / output interface 505.
[0097] The processor 501 may be, for example, a CPU (Central Processing Unit), a microprocessor, a digital signal processor, a microcontroller, or a combination of these.
[0098] The main memory 502 may be, for example, a semiconductor RAM (random access memory).
[0099] For example, a flash memory, a hard disk drive (HDD), a solid state drive (SSD), or a combination of these may be used as the auxiliary memory 503. A program for causing the processor 501 to execute predetermined processing is stored in the auxiliary memory 503. The processor 501 loads the program stored in the auxiliary memory 503 onto the main memory 502 and executes each instruction included in the loaded program.
[0100] The program may be stored non-transitoryly on one or more recording media that can be read by the computer 500. The recording media may or may not be included in the computer 500. In the latter case, the program may be supplied to the computer 500 via any wired or wireless transmission medium.
[0101] The communication interface 504 is an interface for connecting to a network, and may be an interface compatible with wireless communication methods such as WLAN, 3G, LTE, 5G, and 6G.
[0102] The input / output interface 505 may be, for example, an interface conforming to a predetermined standard. The input / output interface 505 may also include a USB interface, a short-range communication interface such as infrared or Bluetooth (registered trademark), or a combination thereof.
[0103] A drive 506 into which the USIM 63 is inserted is connected to the input / output interface 505. The USIM 63 may be directly connected to the input / output interface 505. In this case, the drive 506 may not be provided. In addition, for example, a sensor 507 included in the IoT device is connected to the input / output interface 505.
[0104] Furthermore, input devices and output devices may be connected to the input / output interface 505 as needed. Examples of input devices that may be used include a keyboard, a mouse, a touchpad, a microphone, or a combination of these. Examples of output devices that may be used include a display, a printer, a speaker, or a combination of these.
[0105] (Effects of the embodiment) According to this embodiment, simply inserting the USIM 63 into the IoT device 60 enables the IoT device 60 and the IoT platform 90 to communicate with each other according to, for example, the LwM2M communication protocol.
[0106] That is, according to this embodiment, there is no need to modify the applications and communication modules of the IoT device to implement a communication function using a predetermined communication protocol (e.g., LwM2M). Furthermore, if the communication module of the IoT device has a proven track record, the IoT device can be connected to and used with the communication network of a mobile communications carrier without conducting an interoperability test. For example, even when using an IoT platform related to the communication network of a mobile communications carrier that requires interoperability testing to be completed each time a new model or an unproven communication module is introduced, the burden on the user related to the interoperability test can be reduced.
[0107] Furthermore, basic setting information including the connection destination address of the IoT device 60 and LwM2M operation parameters is distributed from the distribution OTA server 171, so it is possible to automate initial settings for the IoT device 60. In other words, the user can acquire desired data and analyze it on the IoT platform simply by inserting the USIM 63 into the IoT device 60.
[0108] As described above, according to this embodiment, it is possible to dramatically simplify the operation of communication between IoT devices.
[0109] (Other embodiments) In the above-described embodiment, an example has been described in which communication according to the LwM2M communication protocol is performed between the IoT device 60 and the IoT platform 90 by inserting the USIM 63 into the IoT device 60. However, for example, other low-power communication protocols such as MQTT (Message Queue Telemetry Transport) and HTTP (Hyper Text Transfer Protocol) may be used instead of LwM2M.
[0110] Also, an eSIM (Embedded SIM) may be used instead of the USIM 63. The USIM and eSIM will be collectively referred to as SIM.
[0111] According to each aspect of the present invention described above, the above-mentioned effects can be achieved, thereby contributing to the achievement of Goal 9 of the Sustainable Development Goals (SDGs), "Build resilient infrastructure, promote inclusive and sustainable industrialization, and build resilient infrastructure."
[0112] The present invention is not limited to the above-described embodiments, and various modifications are possible within the scope of the claims. Embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of the present invention.
[0113] 〔summary〕 The SIM according to aspect 1 of the present invention is a SIM (Subscriber Identity Module) used in an IoT device, and has an applet area, which is a memory area used as an applet, and is equipped with a memory unit in which a first program that causes the IoT device to execute communication processing in accordance with a predetermined communication protocol is stored in the applet area, and a processing execution unit that is a program implemented in the IoT device and executes communication processing by the first program based on instructions from a second program belonging to an application layer.
[0114] In a second aspect of the present invention, in the SIM of the first aspect, the communication protocol is LwM2M (Lightweight M2M), MQTT (Message Queue Telemetry Transport), or HTTP (Hyper Text Transfer Protocol).
[0115] A SIM according to aspect 3 of the present invention is the same as that according to aspect 1 above, in which the IoT device transmits and receives data to and from other devices, and the first program supplies first data supplied from the second program to a communication module of the IoT device according to a predetermined communication protocol, causing the communication module to generate a wireless signal to be transmitted to the other device, and acquires second data transmitted from the other device, which is data obtained based on the wireless signal received by the communication module of the IoT device.
[0116] In a SIM according to aspect 4 of the present invention, in aspect 3 above, the second program periodically outputs polling using an AT+CSIM command, and the first program supplies the second data to the second program in response to the polling.
[0117] In a SIM according to aspect 5 of the present invention, in aspect 3 above, when the first program acquires the second data, it outputs a proactive command or a message via SMS that causes the second program to execute instructions related to the second data.
[0118] A SIM according to aspect 6 of the present invention is configured such that, in aspect 3 above, the first program, upon acquiring the second data, outputs a proactive command to cause the second program to output an AT+CSIM command, and the second program, upon receiving the proactive command, outputs an AT+CSIM command to cause the first program to output data, and the first program supplies the second data to the second program in response to the AT+CSIM command.
[0119] In a SIM according to aspect 7 of the present invention, in any of aspects 1 to 6 above, the IoT device is connected to an IoT platform including a distribution OTA server, and basic setting information stored in the applet area, the basic setting information including information indicating the connection address of the IoT device or information indicating operating parameters related to the specified communication protocol, is distributed by the distribution OTA server.
[0120] In a SIM according to an eighth aspect of the present invention, in the seventh aspect, update data for the first program stored in the applet area is further distributed by the distribution OTA server.
[0121] A data processing method according to aspect 9 of the present invention is a data processing method for a SIM used in an IoT device, wherein the SIM has an applet area which is a memory area used as an applet, a first program which causes the IoT device to execute communication processing in accordance with a predetermined communication protocol is stored in the applet area, and the SIM includes a step of executing communication processing by the first program based on instructions from a second program which is a program implemented in the IoT device and belongs to an application layer.
[0122] An information processing device according to a tenth aspect of the present invention is an information processing device used as an IoT device, and includes the SIM according to the first aspect above. [Explanation of symbols]
[0123] 10. Communication Systems 30 IoT devices 31 Applications 32 Communication Module 33 USIM 60 IoT devices 61 Applications 62 Communication Module 63 USIM 90 IoT Platforms 100 Storage section 102 Applets 131 Basic setting information 132 Protocol Execution Control Program 151 IoT client applications 171 OTA server for distribution 172 IoT servers
Claims
1. A SIM (Subscriber Identity Module) used in an IoT device, a storage unit having an applet area that is a storage area used as an applet, in which a first program that causes the IoT device to execute communication processing in accordance with an LwM2M (Lightweight M2M) communication protocol is stored in the applet area; a processing execution unit that is a program implemented in the IoT device and that executes communication processing by the first program based on a command from a second program belonging to an application layer; A SIM equipped with:
2. The IoT device transmits and receives data to and from other devices, The first program supplying the first data supplied from the second program to a communication module of the IoT device in accordance with an LwM2M communication protocol, thereby causing the communication module to generate a wireless signal to be transmitted to the other device; Acquire second data transmitted from the other device, the second data being data obtained based on a wireless signal received by a communication module of the IoT device.
2. The SIM of claim 1.
3. the second program periodically outputs polling using an AT+CSIM command; The first program provides the second data to the second program in response to the polling.
3. The SIM of claim 2.
4. The first program When the second data is acquired, a proactive command or a message by SMS (Short Message Service) is output to cause the second program to execute a command related to the second data.
3. The SIM of claim 2.
5. The first program When the second data is acquired, outputting a proactive command to cause the second program to output an AT+CSIM command; The second program Upon receiving the proactive command, outputting an AT+CSIM command that causes the first program to output data; The first program provides the second data to the second program in response to the AT+CSIM command.
3. The SIM of claim 2.
6. The IoT device is connected to an IoT platform including an OTA server for distribution; The basic setting information stored in the applet area includes information indicating a destination address of the IoT device or information indicating operation parameters related to the LwM2M communication protocol, and is distributed by the distribution OTA server.
2. The SIM of claim 1.
7. Update data for the first program stored in the applet area is further distributed by the distribution OTA server.
7. The SIM of claim 6.
8. A data processing method for a SIM used in an IoT device, comprising: The SIM has an applet area, which is a storage area used as an applet, In the applet area, a communication process according to a communication protocol of LwM2M (Lightweight M2M) is executed in the IoT device. A first program for The SIM is a program installed in the IoT device, and a second program belonging to the ear, based on a command from the first program. Includes a step of performing a process Data processing methods.
9. An information processing device used as an IoT device, comprising the SIM according to claim 1. Information processing device.
Citation Information
Patent Citations
Mobile phone communication devices and data management methods
JP2005535195A
Electronic apparatus, portable terminal device, portable communication system and data migration program
JP2009038598A
WiFi communication method, user equipment, and wireless router
JP2013537749A
Communication terminal and service provision device
JP2015211379A
Interworking lightweight machine-to-machine protocol with device management protocol
JP2017525293A