KR102199594B1 - IoT device controlling method regardless of communication - Google Patents

Abstract

According to an aspect of the present invention, the IoT device and the user terminal exchange data through short-range wireless communication, and the user terminal and the IoT server control an IoT device that is not affected by a communication state applied to a network transmitting and receiving data through high-speed data communication. A method is provided. An IoT device control method that is not affected by a communication state includes the steps of, when receiving an IoT device registration request, generating a server public key and a server security key by an IoT server and transmitting the server public key to a user terminal, the server public key. Upon receiving, the user terminal divides and transmits the server public key to the IoT device, upon receiving the dividedly transmitted server public key, the IoT device generates a device public key and a device security key, and the server public key And generating and storing an IoT device symmetric key using the device security key, and transmitting the device public key to the user terminal. When receiving the dividedly transmitted device public key, the user terminal sends the device public key to the IoT Transmitting to a server, and upon receiving the device public key, the IoT server generating an IoT server symmetric key using the device public key and the server security key, wherein divided transmission between the IoT device and the user terminal May be divided and transmitted in units of a data size that can be transmitted once through the short-range wireless communication.

Description

IoT device controlling method regardless of communication

The present invention relates to a method for controlling an IoT device that is not affected by a communication state.

IoT devices are devices that can be connected to a network and transmit and receive data through the connected network. IoT devices can transmit and receive data through various communication methods, for example, high-speed data communication such as mobile communication, wired/wireless Internet, and Ethernet, as well as short-range wireless communication such as NFC, Bluetooth, Zigbee, and RFID. On the other hand, between IoT servers that manage IoT devices, two or more networks that follow different communication protocols may exist. For example, the IoT device and the user terminal may transmit and receive data through NFC, and the user terminal and the IoT server may transmit and receive data through the wireless Internet. In order to instruct an IoT device to perform a specific operation or processing, data transmission/reception between the IoT device, the user terminal and the IoT server must be possible. However, when communication between the user terminal and the IoT server is disconnected, the IoT server cannot approve commands to control the IoT device. Meanwhile, only data transmission or reception may be possible depending on the communication performance of the IoT device and/or the user terminal.

An object of the present invention is to provide a method for controlling an IoT device that is not affected by a communication state.

According to an aspect of the present invention, the IoT device and the user terminal exchange data through short-range wireless communication, and the user terminal and the IoT server control an IoT device that is not affected by a communication state applied to a network transmitting and receiving data through high-speed data communication. A method is provided. An IoT device control method that is not affected by a communication state includes the steps of, when receiving an IoT device registration request, generating a server public key and a server security key by an IoT server and transmitting the server public key to a user terminal, the server public key. Upon receiving, the user terminal divides and transmits the server public key to the IoT device, upon receiving the dividedly transmitted server public key, the IoT device generates a device public key and a device security key, and the server public key And generating and storing an IoT device symmetric key using the device security key, and transmitting the device public key to the user terminal. When receiving the dividedly transmitted device public key, the user terminal sends the device public key to the IoT Transmitting to a server, and upon receiving the device public key, the IoT server generating an IoT server symmetric key using the device public key and the server security key, wherein divided transmission between the IoT device and the user terminal May be divided and transmitted in units of a data size that can be transmitted once through the short-range wireless communication.

The IoT device symmetric key and the IoT server symmetric key are the same, and communication between the IoT device and the IoT server may be encrypted by the IoT device symmetric key and the IoT server symmetric key.

In the IoT device control method that is not affected by a communication state, when receiving an identification information request message, the IoT device encrypts a first identifier with the IoT device symmetric key and transmits the encrypted first identifier to the user terminal-Here, the first The identifier is an identifier assigned to the IoT device, and upon receiving the dividedly transmitted first identifier, the user terminal sends an authorization request message including a request code, an encrypted first identifier, and a second identifier to the IoT server. Transmitting step-Here, the request code represents an operation or processing to be requested from the IoT device, and the second identifier is information for identifying a user or the user terminal. Upon receiving the authorization request message, the IoT server Decrypting the encrypted first identifier with the IoT server symmetric key and approving the request code based on the second identifier, the IoT server generating a command code corresponding to the approved request code, and symmetric the IoT server Encrypting with a key and transmitting to the IoT device through the user terminal, and upon receiving the encrypted command code, the IoT device decrypts with the IoT device symmetric key to execute an operation or processing according to the command code can do.

The method of controlling an IoT device that is not affected by a communication state includes the steps of generating a temporary approval request message by the user terminal according to a preset condition and transmitting it to the IoT server, determining whether the IoT server meets the preset condition Generating a command code and transmitting a temporary approval message including a command code encrypted with the IoT server symmetric key to the user terminal, and when a state in which communication with the IoT server is impossible is detected, the user terminal sends the temporary approval message It may further include the step of transmitting the encrypted command code included in the divided to the IoT device.

The method of controlling an IoT device that is not affected by a communication state may further include setting a current time to the IoT device before the step of transmitting the encrypted command code in division.

The encrypted command code included in the temporary approval message may be time dependent.

The method for controlling an IoT device that is not affected by a communication state includes the steps of, by the user terminal, transmitting an authorization request message including a first identifier, a second identifier, and a request code encrypted with the IoT device symmetric key to the IoT server, the Upon receiving the authorization request message, the IoT server decrypting the encrypted first identifier with the IoT server symmetric key and approving the request code based on the second identifier, the IoT server generating a server-generated OTP. Transmitting to a user terminal, the user terminal displaying the server-generated OTP, and when the server-generated OTP is input, one or more devices previously generated based on a time point when the IoT device starts to input the OTP It may further include comparing the OTP and the server-generated OTP.

The method for controlling an IoT device that is not affected by a communication state disclosed in an embodiment according to the present invention may enable service provision even when communication between the IoT device, a user terminal, and an IoT server is not smooth.

In the following, the present invention is explained with reference to the embodiments shown in the accompanying drawings. For ease of understanding, throughout the accompanying drawings, like reference numerals are assigned to like elements. The configurations shown in the accompanying drawings are merely exemplary embodiments to describe the present invention, and are not intended to limit the scope of the present invention.
1 is a diagram for illustratively illustrating a communication failure situation that may occur in an IoT network.
2 is a flowchart illustrating a process of registering an IoT device when a communication state is normal.
3 is a diagram illustrating a process of controlling an IoT device to perform a specific operation when a communication state is normal.
4 is a diagram illustrating a process of controlling an IoT device to perform a specific operation in a communication failure state between a user terminal and an IoT server.
5 is a diagram illustrating a process of controlling an IoT device to perform a specific operation when bidirectional data communication between an IoT device and a user terminal is not supported.
6 is a diagram illustrating a network configuration to which the IoT device control method illustrated in FIGS. 2 to 5 is applied.
FIG. 7 is a diagram illustrating an exemplary point accumulation and use system to which the network configuration illustrated in FIG. 6 is applied.

In the present invention, various modifications may be made and various embodiments may be provided. Specific embodiments are illustrated in the drawings and will be described in detail through detailed description. However, this is not intended to limit the present invention to a specific embodiment, it is to be understood to include all changes, equivalents, and substitutes included in the spirit and scope of the present invention.

Hereinafter, embodiments of the present invention will be described in detail with reference to the related drawings.

1 is a diagram for illustratively illustrating a communication failure situation that may occur in an IoT network.

One or more IoT devices are registered on the IoT server. The IoT device can be controlled directly or indirectly by the IoT server. The IoT device may perform a specific operation or processing (eg, temperature sensing) independently or by an IoT server. In communication over a network, information security is very important, and this is also the case for communication between IoT devices and IoT servers. The IoT server manages the IoT device, and the IoT device must be controlled only by the IoT server to which it is registered. Therefore, the registration 100 of the IoT device should be performed only when communication between the IoT device and the IoT server is normal. The IoT device registration 100 is a process of exchanging a symmetric key used to encrypt all communication between the IoT device and the server after registration, and will be described in detail with reference to FIG. 2. Some IoT devices may communicate with an IoT server through a user terminal, for example, a smart phone, due to constraints such as power and size. For example, an IoT device and a smart phone can be connected via NFC or Bluetooth, and a smart phone and an IoT server can be connected via wireless Internet.

The IoT device registration 100 and the IoT device control 110 can be performed only when the communication state is normal. A process of controlling the IoT device when the communication state is normal will be described in detail with reference to FIG. 3. However, as described above, even in a situation where there is a failure 120 in communication between the IoT device and the user terminal, or in a situation where there is a failure 130 in communication between the user terminal in charge of communication relay and the IoT server, it is necessary to control the IoT device. There may be.

The communication failure 120 between the IoT device and the user terminal may occur when communication between the IoT device and/or the user terminal cannot be made in both directions. One-way communication may occur due to communication capability constraints of either or both of the IoT device and the user terminal. The IoT device can transmit data to the outside, but cannot receive it (for example, if the IoT device does not have a wireless communication function), or the user terminal can read data from the IoT device, but send the data to the IoT device. It may not be possible to write (for example, when the NFC module of the user terminal operates in reader mode only). The process of transmitting the command code to the IoT device when the communication failure 120 between the IoT device and the user terminal occurs will be described in detail with reference to FIG. 5.

A failure 130 in communication between the user terminal and the IoT server may be caused by various causes, and thus, the IoT server cannot transmit a command code to the IoT device. A process of transmitting the command code to the IoT device when a communication failure 130 between the user terminal and the IoT server occurs will be described in detail with reference to FIG. 4.

FIG. 2 is a flowchart for explaining a process of registering an IoT device when the communication state is normal, and may be divided into a process of registering an IoT device 200 to 240 and a process of setting a password 245 to 265. Here, the password setting process is an optional process.

The registration process 200 to 240 of the IoT device is a process of distributing a symmetric key using asymmetric encryption. Asymmetric encryption is completed by the IoT server generating the server public key and server security key, passing the server public key to the IoT device, the IoT device generating the device public key and device security key, and passing the device public key to the IoT server. Can be. The symmetric key is generated in each of the IoT device and the IoT server by an asymmetric encryption process, and the IoT device symmetric key and the IoT server symmetric key are the same.

In 200, the user terminal sends a registration request message including the location identifier to the IoT server. Here, the location identifier is information for identifying the location where the IoT device is installed. For example, when the IoT device is a door lock, it may be the number of a room in which the door lock is installed.

At 205, the IoT server generates a server public key and a server security key for an asymmetric encryption process. Additionally, the IoT server may generate a random server random value in order to detect that a message is forged or altered by hacking or the like during a transmission process. Meanwhile, the IoT server stores the location identifier in the database for symmetric key exchange to be performed later. The server public key and server security key are associated with the location identifier and stored in the database. Additionally, the server random value may be associated with the location identifier and stored in the database.

At 210, the IoT server generates a server message and transmits it to the user terminal. The server message includes the server public key, and may further include a server random value. Meanwhile, if the IoT device and the IoT server know the same initial symmetric key, the server public key and/or the server random value may be encrypted using the initial symmetric key. Here, the initial symmetric key is a symmetric key stored in the IoT device upon factory initialization, and may no longer be used after the symmetric key is distributed by asymmetric encryption.

At 215, the user terminal divides and transmits the server message to the IoT device. Compared with the communication line between the user terminal and the IoT server, the data transmission capability of the communication line between the IoT device and the user terminal is relatively low. Data communication between the IoT device and the user terminal is initiated by an action of the user, for example, an operation of bringing the user terminal to the IoT device, and is preferably completed within a few seconds. Communication methods capable of satisfying such requirements are, for example, RFID or NFC. In such short-range wireless communication, the size of data that can be transmitted at one time is limited. The user terminal checks the maximum transferable data size of short-range wireless communication upon initial connection with the IoT device, and sets the data size that can be transferred once. If the encrypted server message is larger than the data size that can be transmitted once, the user terminal divides the server message into units of the data size that can be transmitted once and transmits it to the IoT device. For example, a data size unit that can be transmitted once may be 64 bits. The divided transmitted message may include a header, the number of divided messages, and divided server messages.

In 220, an IoT device symmetric key is generated using a server message completed from the dividedly transmitted message. The IoT device generates a device public key and a device security key. The IoT device symmetric key is generated by the server public key included in the server message and the device security key generated by the IoT device. The generated IoT device symmetric key is stored in the IoT device.

In 225, the IoT device generates a device message and transmits it to the user terminal. The device message may be generated by encrypting the device public key and the first identifier using the server public key. Here, the first identifier is an identifier assigned to the IoT device, and may be, for example, a unique serial number. In the same manner as in step 215, the IoT device divides the device message into units of a data size that can be transmitted once and transmits it to the user terminal.

At 230, the user terminal generates a registration message and transmits it to the IoT server. The user terminal may transmit the device message completed from the dividedly transmitted message to the IoT server as it is. Additionally, the user terminal may include a second identifier capable of identifying the user or the user terminal in the registration message.

At 235, upon receiving the registration message, the IoT server registers the IoT device. The IoT server generates an IoT server symmetric key and a first identifier using a server random value, a server security key, and a registration message. The IoT server obtains a device public key by decrypting the device message included in the registration message using the server security key. The IoT server symmetric key is generated using the device public key and the server security key, and is the same as the IoT device symmetric key. The server random value extracted from the registration message is compared with the server random value stored in the database. If the random values of both servers match, the IoT server stores the IoT server symmetric key, the first identifier, and the second identifier in the database in association with the location identifier.

At 240, the IoT server generates a registration confirmation message and transmits it to the user terminal. When the registration of the IoT device is successfully completed, the user terminal and/or the IoT device receiving the registration confirmation message may perform a subsequent process, for example, a password setting process. Through steps 200 to 240, the IoT device holds the IoT device symmetric key, and the IoT server holds the IoT server symmetric key, respectively, and then communication between the IoT device and the IoT server may be encrypted using each symmetric key.

At 245, the user terminal generates a user authentication key setting message and transmits the divided transmission to the IoT device. The user authentication key setting message includes a command for setting the IoT device with the authentication key input through the user terminal. Here, the user authentication key is information necessary to confirm whether the user is a legitimate user when a user requests a specific operation or processing from the IoT device, and may be, for example, a personal identification number (PIN) or a password. In the same manner as in step 215, the user terminal divides the user authentication key setting message into units of a data size that can be transmitted once and transmits it to the IoT device.

At 250, the IoT device stores the user authentication key by using the user authentication key setting message completed from the dividedly transmitted message. The IoT device generates a device public key and a device security key. The IoT device symmetric key is generated by the server public key included in the server message and the device security key generated by the IoT device. The generated IoT device symmetric key is stored in the IoT device. The stored user authentication key is compared with a user authentication key provided at the time of a specific operation or processing request from the user or the user terminal, and is used to approve the request.

At 255, the IoT device generates a configuration confirmation message and transmits the divided transmission to the user terminal. At 260, the user terminal extracts the user authentication key setting result from the setting confirmation message, generates a setting completion message, and transmits the setting completion message to the IoT server. At 265, the IoT server verifies that a user authentication key has been set in the IoT device.

FIG. 3 is a diagram for illustratively illustrating a process of controlling an IoT device to perform a specific operation when a communication state is normal, and illustrates a case in which communication between an IoT device and a user terminal and an IoT server can be performed normally.

In 300, the user terminal requests an identification information request message from the IoT device. When a user approaches a user terminal in a state in which short-range wireless communication, for example, NFC communication is activated, to the IoT device, the user terminal generates an identification information request message and transmits it to the IoT device. The identification information request message includes a command for instructing transmission of the first identifier of the IoT device. The identification information request message may be dividedly transmitted to the IoT device.

At 305, upon receiving the identification information request message, the IoT device generates an encrypted first identifier. The first identifier is encrypted with the IoT device symmetric key. Additionally, the IoT device may generate a device random value. The generated device random value may then be used to verify whether communication with the IoT server has been forged or altered.

In 310, the IoT device divides and transmits the identification information message to the user terminal. The identification information message includes an encrypted first identifier, and may further include a device random value.

In 315, the user terminal transmits an authorization request message to the IoT server. The authorization request message includes a request code indicating an operation or processing requested by the user to the IoT device, an encrypted first identifier, and a second identifier.

At 320, the IoT server approves execution of the request code requested by the user terminal according to the approval request message. The IoT server extracts the encrypted first identifier, the device random value, and the second identifier from the authorization request message, and decrypts the encrypted first identifier using the IoT device symmetric key. When the first identifier has already been registered and it is confirmed by the second identifier that it is an authorization request message from a legitimate user, the IoT server approves the request code requested by the user terminal.

At 325, the IoT server generates an approval message and transmits it to the user terminal. The authorization message includes a command code for causing the IoT device to execute a specific operation or processing according to the approved request code, and a device random value, and the command code and the device random value are encrypted with an IoT server symmetric key.

At 330, the user terminal generates a control message and transmits it dividedly to the IoT device. The control message includes an encrypted command code and a device random value.

At 335, the IoT device checks the approval result and executes a specific operation or process according to the command code. In one embodiment, the IoT device obtains the command code and the received device random value by decrypting the encrypted command code using the IoT device symmetric key. The IoT device executes an operation or processing according to an instruction code. In another embodiment, the IoT device may obtain a command code and a received device random value using the IoT device symmetric key and the stored device random value. When the received device random value and the stored device random value match, the IoT device may perform an operation or processing according to the command code.

In 340, the IoT device generates an execution result message and transmits it to the user terminal. The execution result message includes an execution result indicating whether the operation or processing has been normally executed according to the received instruction code.

At 345, the user terminal provides the execution result to the IoT server, and at 350, the IoT server verifies whether the command code has been correctly executed.

4 is a diagram illustrating a process of controlling an IoT device to perform a specific operation in a communication failure state between a user terminal and an IoT server.

In 400, the user terminal transmits a temporary approval request message to the IoT server. The user terminal generates a temporary approval request message according to a preset condition and transmits it to the IoT server. In an embodiment, when the pre-action requested by the user is successfully completed, the user terminal may generate a temporary approval request message and transmit it to the IoT server, or the IoT server may generate a temporary approval message and provide it to the user terminal. For example, the pre-action requested from the user may be a reservation, a reservation and payment, a product purchase, a product purchase at the same store, a new purchase within a predetermined period after product purchase, and the like. In another embodiment, at a certain period or when an event occurs, the user terminal may generate a temporary approval request message and transmit it to the IoT server, or the IoT server may generate a temporary approval message and provide it to the user terminal. For example, the event is when the user terminal is in a state where communication with the IoT server is possible, when the user terminal enters a predetermined location, when communication between the user terminal and the IoT server is not possible beyond a set time limit, the user terminal This may be a case where communication between the IoT server and the IoT server is frequently impossible beyond a set period.

In 405, the IoT server determines whether the temporary approval request message satisfies a preset condition.

In 410, if the preset condition is met, the IoT server generates a temporary approval message and transmits it to the user terminal. The temporary acknowledgment message includes a command code for causing the IoT device to perform a specific operation or processing, and a device random value, and the command code and the device random value are encrypted with an IoT server symmetric key. Additionally, the temporary approval message may further include a time setting command for setting the time of the IoT device.

The command code included in the temporary approval message may be given a valid condition. In an embodiment, the command code may be time dependent. For example, the command code may be valid only within a certain period of time or may be valid only at a specific time. In another embodiment, the instruction code may be position dependent. For example, the command code may be valid only at a set position.

At 415, the user terminal stores the encrypted command code.

The user terminal checks whether communication with the IoT server is possible. The check point may be determined in various ways, but it is assumed here that when NFC is activated, the user terminal checks whether communication is possible. If communication with the IoT server is possible, the user terminal controls the IoT device in the manner described with reference to FIG. 3. That is, the encrypted command code stored in the user terminal through steps 400 to 415 is not used. Meanwhile, if communication with the IoT server is not possible, the user terminal may control the IoT device in a manner according to steps 420 to 445.

At 420, when the user approaches the user terminal in a state in which short-range wireless communication is activated to the IoT device, the user terminal may divide and transmit a time synchronization command to the IoT device. When initiating communication with the IoT device, the user terminal checks whether the IoT device knows the current time. When the current time cannot be known because the IoT device does not use a real-time clock, the user terminal provides the current time to the IoT device. The time synchronization command is a command code that causes an IoT device that does not use a real time clock to set the current time. At 425, the IoT device is set to the current time. When the IoT device uses a real time clock, steps 420 and 425 may be omitted.

At 430, the user terminal generates a control message and transmits it dividedly to the IoT device. The control message includes an encrypted command code.

At 435, the IoT device executes a specific operation or process according to the encrypted command code. In one embodiment, the IoT device obtains the command code by decrypting the encrypted command code using the IoT device symmetric key. The IoT device executes an operation or processing according to the command code. In another embodiment, the IoT device may further determine the validity of the command code according to a valid condition associated with the command code. Since the command code was generated without the intervention of the IoT device, there is no device random value associated with the command code. If there is no device random value, the IoT device may further determine whether the command code satisfies the valid condition. When the valid condition is satisfied, the IoT device executes an operation or processing according to the command code.

At 440, the IoT device generates an execution result message and transmits it to the user terminal. The execution result message includes an execution result indicating whether the operation or processing has been normally executed according to the received instruction code.

Meanwhile, in order for the IoT device to perform a specific operation or process, communication between the user terminal and the IoT device may be added after step 445. For example, when the user wants to change the user authentication key already set in the IoT device, the IoT device switches to a mode in which the user authentication key can be changed, and then receives and stores the new user authentication key input to the user terminal. You can run more steps.

5 is a diagram illustrating a process of controlling an IoT device to perform a specific operation when bidirectional data communication between an IoT device and a user terminal is not supported. In FIG. 5, the IoT device includes an input means, for example, a numeric keypad for receiving a user authentication key from a user. The process illustrated in FIG. 5 may be applied when bidirectional wireless communication is not possible by any one of an IoT device and a user terminal.

At 500, the user terminal acquires an identification information message including a first identifier encrypted with an IoT device symmetric key. In an embodiment, the identification information message may be read from the IoT device. In another embodiment, the IoT device broadcasts the identification information message at a predetermined period, and the user terminal may receive it.

On the other hand, the IoT device and the IoT server generate OTP at regular intervals, and the device-generated OTP and the server-generated OTP are the same. OTP consists of one or more digits, and the validity period of the OTP generated at a specific time can be arbitrarily specified. The IoT device may generate an OTP, for example, when an identification information message is transmitted, when a user starts to input a user authentication key, or the like.

In 505, the user terminal transmits an authorization request message to the IoT server. The authorization request message includes a request code, an encrypted first identifier, and a second identifier.

At 510, the IoT server approves the request code according to the approval request message. The IoT server extracts the encrypted first identifier and the second identifier from the authorization request message, and decrypts the encrypted first identifier using the IoT device symmetric key. When the first identifier has already been registered and it is confirmed by the second identifier that it is an authorization request message from a legitimate user, the IoT server approves the request code transmitted by the user terminal.

At 515, the IoT server generates an approval message and transmits it to the user terminal. The acknowledgment message includes a server-generated OTP. At 520, upon receiving the approval message, the user terminal displays a server-generated OTP. The displayed server-generated OTP is used as a user authentication key, and the user inputs the server-generated OTP through the keypad of the IoT device.

At 525, the IoT device checks the approval result and executes a specific operation or process according to the command code. The approval result may be confirmed by whether the server-generated OTP input by the user and the device-generated OTP match. Here, it may take at least several seconds for the user terminal to display the server-generated OTP and then for the user to input the server-generated OTP. The IoT device may compare one or more device-generated OTPs previously generated based on a time when the user starts to input the server-generated OTP with the server-generated OTP input by the user. For example, assuming that the OTP generation cycle is 2 seconds, and the average time it takes from the time when the user receives the server-generated OTP to the time the input starts is 5 seconds, the IoT device allows the user to input the server-generated OTP. The four device-generated OTPs generated at the start time T, T-2, T-4, and T-6 seconds are compared with the server-generated OTP entered by the user. When any one of the four device-generated OTPs and the server-generated OTP input by the user match, the IoT device may execute an operation or processing according to the command code.

In 530, the IoT device generates an execution result message and transmits it to the user terminal. The execution result message includes an execution result indicating whether the operation or processing has been normally executed according to the received instruction code.

At 535, the user terminal provides the execution result to the IoT server, and at 540, the IoT server checks whether the command code has been correctly executed.

6 is a diagram illustrating a network configuration to which the IoT device control method illustrated in FIGS. 2 to 5 is applied.

A network including the IoT devices 600, 610, 625, and 640 and the IoT server 630 may be configured in various ways according to a communication method between them. 6A shows a user terminal, for example, a smartphone 620 capable of transmitting and receiving data through short-range wireless communication and high-speed data communication, relaying communication between the IoT devices 600 and 610 and the IoT server 630 In (b), a kiosk 605 capable of transmitting and receiving data through short-range wireless communication and high-speed data communication is a user terminal that relays communication between the IoT devices 625 and 640 and the IoT server 630. In (a), the IoT device is, for example, a kiosk 600, a door lock 620, and the like, and in (b), the IoT device may be a smart phone 625, a smart card, or an electronic wallet 640.

The IoT device control method that is not affected by the communication state illustrated in FIGS. 1 to 5 can be applied to various application fields. In the network shown in (a), in one embodiment, the process of purchasing products or accumulating mileage through the kiosk 600 is protected by symmetric key encryption, in particular, the kiosk 600-the user terminal 620 -It is not affected by the communication state between IoT servers 630. The IoT server 630 may be a payment server that processes a payment process according to a purchase or an application server that manages mileage. When applied to payment or mileage accumulation, the command code may be, for example, transmission or update of information requiring security. In another embodiment, a method of controlling an IoT device that is not affected by a communication state may be applied to opening the door lock 610 using the user terminal 620. When applied to the door lock opening, the command code may be a password setting/change, door lock opening, or the like. Similarly, the IoT device control method that is not affected by the communication state can be applied to the network shown in (b) to securely protect a product purchase or mileage accrual process.

FIG. 7 is a diagram illustrating an exemplary point accumulation and use system to which the network configuration illustrated in FIG. 6 is applied.

Referring to FIG. 7, a point accumulation and use system to which a method for controlling an IoT device that is not affected by a communication state is applied may pay an electronic coin to a user as a reward for the user's product purchase/service use. The electronic coin may be an electronic coin that can be transacted universally, for example, Bitcoin and Ethereum, as well as an electronic coin that can be used only for a specific server or service for which transactions are permitted. The point accumulation and use system may include an electronic coin management server 700, a kiosk/POS 710, a user terminal 720, and an electronic coin use server 730.

The electronic coin management server 700 manages electronic coin accounts for each user. For example, the electronic coin management server 700 may transfer electronic coins between accounts or mediate the trading of electronic coins. The kiosk/POS 720 may request an electronic coin transfer to the user terminal 720. The kiosk or POS is installed in an individual-owned store or franchise store, and directly transmits and receives data through high-speed data communication with the electronic coin management server 700, or is connected to the user terminal 720 through short-range wireless communication to provide an electronic coin. Data can be transmitted and received with the management server 700. The user terminal 720 includes an app that holds or manages electronic coins. The app can store electronic coins in the user's electronic coin account by interlocking with the kiosk/POS 710, and the electronic coin use server 730 from the user's electronic coin account by interlocking with the electronic coin use server 730 Electronic coins can be transferred to an electronic coin account. The electronic coin use server 730 provides a service that allows a user to use an electronic coin. The electronic coin use server 730 is, for example, a content server that downloads music or video, a donation service server that pays an electronic coin donated by a user to a third party, and invests in a third party or company designated by the user. It may be an investment service server or the like.

The method of accumulating and using points executed in the above-described system is as follows.

In S1, the electronic coin management server 700 transfers the electronic coin to the electronic coin account associated with the kiosk/POS 710. When a store owner or a franchise company purchases an electronic coin, the electronic coin management server 700 may transfer the purchased electronic coin by creating an electronic coin account for each kiosk/POS.

In S2, when the user purchases a product, in S3/S3', the kiosk/POS 710 transfers the electronic coin to the user's electronic coin account. Before transferring electronic coins between accounts, a user authentication process is required. To this end, information (eg, a second identifier) capable of identifying a user or a user terminal must be exchanged between the electronic coin management server 700-kiosk/POS 710-user terminal 720. In the user authentication process, the IoT device control method that is not affected by the communication state described with reference to FIGS. 2 to 5 is applied.

In S4, the user can use the electronic coin in the electronic coin use server 730. When the user transfers the electronic coin through the user terminal 720, the electronic coin use server 730 provides the service desired by the user, for example, content provision, electronic coin donation, investment, etc., and in S5, the result Is notified to the user terminal 720.

In S6, the electronic coin use server 730 may perform a settlement process with the electronic coin management server 700. Settlement is a process of selling electronic coins and converting them into real money or authorizing electronic coin transfer between accounts.

The above description of the present invention is for illustrative purposes only, and those of ordinary skill in the art to which the present invention pertains will be able to understand that it can be easily modified into other specific forms without changing the technical spirit or essential features of the present invention. will be. Therefore, it should be understood that the embodiments described above are illustrative and non-limiting in all respects.

The scope of the present invention is indicated by the claims to be described later rather than the detailed description, and all changes or modified forms derived from the meaning and scope of the claims and their equivalent concepts should be construed as being included in the scope of the present invention. .

Claims (7)

In the IoT device control method that is not affected by a communication state applied to a network in which an IoT device and a user terminal exchange data through short-range wireless communication, and a user terminal and an IoT server transmit and receive data through high-speed data communication,
Upon receiving an IoT device registration request, the IoT server generating a server public key and a server security key and transmitting the server public key to a user terminal;
Upon receiving the server public key, the user terminal divides and transmits the server public key to an IoT device;
Upon receiving the dividedly transmitted server public key, the IoT device generates a device public key and a device security key, generates and stores an IoT device symmetric key using the server public key and the device security key, and stores the device public key. Splitting and transmitting to a user terminal;
Upon receiving the dividedly transmitted device public key, transmitting, by the user terminal, the device public key to the IoT server;
Upon receiving the device public key, generating, by the IoT server, an IoT server symmetric key using the device public key and the server security key;
Upon receiving the identification information request message, the IoT device encrypting a first identifier with the IoT device symmetric key and transmitting the encrypted first identifier to the user terminal, wherein the first identifier is an identifier assigned to the IoT device;
Upon receiving the dividedly transmitted first identifier, transmitting, by the user terminal, an authorization request message including a request code, an encrypted first identifier, and a second identifier to the IoT server-wherein the request code is the IoT Indicates an operation or processing to be requested from the device, and the second identifier is information for identifying a user or the user terminal;
Upon receiving the authorization request message, the IoT server decrypting the encrypted first identifier with the IoT device symmetric key and approving the request code based on the second identifier;
Generating, by the IoT server, a command code corresponding to the approved request code, encrypting it with the IoT server symmetric key, and transmitting it to the IoT device through the user terminal; And
Upon receiving the encrypted command code, the IoT device decrypts it with the IoT device symmetric key to execute an operation or processing according to the command code,
The divided transmission between the IoT device and the user terminal is divided and transmitted in units of a data size that can be transmitted once by the short-range wireless communication, and is not affected by a communication state. The method according to claim 1, wherein the IoT device symmetric key and the IoT server symmetric key are the same, and the communication between the IoT device and the IoT server is encrypted by the IoT device symmetric key and the IoT server symmetric key. How to control IoT devices that do not receive. delete In the IoT device control method that is not affected by a communication state applied to a network in which an IoT device and a user terminal exchange data through short-range wireless communication, and a user terminal and an IoT server transmit and receive data through high-speed data communication,
Upon receiving an IoT device registration request, the IoT server generating a server public key and a server security key and transmitting the server public key to a user terminal;
Upon receiving the server public key, the user terminal divides and transmits the server public key to an IoT device;
Upon receiving the dividedly transmitted server public key, the IoT device generates a device public key and a device security key, generates and stores an IoT device symmetric key using the server public key and the device security key, and stores the device public key. Splitting and transmitting to a user terminal;
Upon receiving the dividedly transmitted device public key, transmitting, by the user terminal, the device public key to the IoT server;
Upon receiving the device public key, generating, by the IoT server, an IoT server symmetric key using the device public key and the server security key;
Generating, by the user terminal, a temporary approval request message according to a preset condition and transmitting it to the IoT server;
Determining whether the IoT server meets the preset condition, generating a command code, and transmitting a temporary approval message including a command code encrypted with the IoT server symmetric key to the user terminal; And
When a state in which communication with the IoT server is impossible is detected, the user terminal further comprises the step of transmitting the encrypted command code included in the temporary approval message to the IoT device,
The divided transmission between the IoT device and the user terminal is divided and transmitted in units of a data size that can be transmitted once by the short-range wireless communication, and is not affected by a communication state. The method of claim 4,
The method of controlling an IoT device that is not affected by a communication state, further comprising setting a current time to the IoT device prior to the divided transmission of the encrypted command code. The method of claim 4, wherein the encrypted command code included in the temporary approval message is time dependent and is not affected by a communication state. In the IoT device control method that is not affected by a communication state applied to a network in which an IoT device and a user terminal exchange data through short-range wireless communication, and a user terminal and an IoT server transmit and receive data through high-speed data communication,
Upon receiving an IoT device registration request, the IoT server generating a server public key and a server security key and transmitting the server public key to a user terminal;
Upon receiving the server public key, the user terminal divides and transmits the server public key to an IoT device;
Upon receiving the dividedly transmitted server public key, the IoT device generates a device public key and a device security key, generates and stores an IoT device symmetric key using the server public key and the device security key, and stores the device public key. Splitting and transmitting to a user terminal;
Upon receiving the dividedly transmitted device public key, transmitting, by the user terminal, the device public key to the IoT server;
Upon receiving the device public key, generating, by the IoT server, an IoT server symmetric key using the device public key and the server security key;
Transmitting, by the user terminal, an authorization request message including a first identifier, a second identifier, and a request code encrypted with the IoT device symmetric key to the IoT server;
Upon receiving the authorization request message, the IoT server decrypting the encrypted first identifier with the IoT server symmetric key and approving the request code based on the second identifier;
Transmitting, by the IoT server, a server-generated OTP to the user terminal;
Displaying the server generated OTP by the user terminal; And
When the server-generated OTP is input, comparing the server-generated OTP with one or more device-generated OTPs previously generated based on a point in time when the IoT device starts to input the OTP,
The divided transmission between the IoT device and the user terminal is divided and transmitted in units of a data size that can be transmitted once by the short-range wireless communication, and is not affected by a communication state.

Images