WO2021107389A1 - Système de réseaux et son procédé de sécurité de messages - Google Patents

Système de réseaux et son procédé de sécurité de messages Download PDF

Info

Publication number
WO2021107389A1
WO2021107389A1 PCT/KR2020/013707 KR2020013707W WO2021107389A1 WO 2021107389 A1 WO2021107389 A1 WO 2021107389A1 KR 2020013707 W KR2020013707 W KR 2020013707W WO 2021107389 A1 WO2021107389 A1 WO 2021107389A1
Authority
WO
WIPO (PCT)
Prior art keywords
terminal
encryption key
payload
topic
producer
Prior art date
Application number
PCT/KR2020/013707
Other languages
English (en)
Korean (ko)
Inventor
권태경
곽명철
이현우
이현민
임정환
신유정
Original Assignee
서울대학교 산학협력단
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 서울대학교 산학협력단 filed Critical 서울대학교 산학협력단
Publication of WO2021107389A1 publication Critical patent/WO2021107389A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/04—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks
    • H04L63/0428—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload
    • H04L63/0471—Network architectures or network communication protocols for network security for providing a confidential data exchange among entities communicating through data packet networks wherein the data content is protected, e.g. by encrypting or encapsulating the payload applying encryption by an intermediary, e.g. receiving clear information at the intermediary and encrypting the received information at the intermediary before forwarding
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/06—Network architectures or network communication protocols for network security for supporting key management in a packet data network
    • H04L63/061—Network architectures or network communication protocols for network security for supporting key management in a packet data network for key exchange, e.g. in peer-to-peer networks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/06—Network architectures or network communication protocols for network security for supporting key management in a packet data network
    • H04L63/065—Network architectures or network communication protocols for network security for supporting key management in a packet data network for group communications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/06—Network architectures or network communication protocols for network security for supporting key management in a packet data network
    • H04L63/067—Network architectures or network communication protocols for network security for supporting key management in a packet data network using one-time keys
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/06—Network architectures or network communication protocols for network security for supporting key management in a packet data network
    • H04L63/068—Network architectures or network communication protocols for network security for supporting key management in a packet data network using time-dependent keys, e.g. periodically changing keys
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
    • H04L65/40—Support for services or applications
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/14—Session management
    • H04L67/141—Setup of application sessions
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/50—Network services
    • H04L67/56—Provisioning of proxy services
    • H04L67/562—Brokering proxy services

Definitions

  • Embodiments disclosed herein relate to a network system and its message security method. More particularly, it relates to a network system capable of increasing message security so as to prevent leakage or manipulation of a message by a broker relaying between a producer and a subscriber, and a message security method thereof.
  • the Message Queuing Telemetry Transport (MQTT) protocol is used as a lightweight subscription/production (Pub(Publish)/Sub(Subsribe)) message protocol.
  • the MQTT protocol was created for use in Machine to Machine (M2M) and Internet of Things (IoT) environments.
  • MQTT protocol is a protocol designed to be used in a low-power, low-bandwidth environment.
  • This MQTT protocol operates as a basic principle of publishing messages and subscribing to topics of interest.
  • the producer terminal may generate a message related to the topic and deliver it to the subscriber terminal.
  • a wearable information service including a wearable device that generates wearable data, a wearable broker that receives and distributes wearable data over a network, and a user terminal that receives wearable data Describe the system.
  • Embodiments disclosed herein have an object to provide a network system capable of preventing message leakage or manipulation by a broker relaying between producers and subscribers and a message security method thereof.
  • the embodiments disclosed in the present specification when receiving an encrypted topic and a payload from a producer terminal that generates a topic, decrypts the topic using an encryption key shared with the producer terminal. Checks the subscriber terminal subscribing to , encrypts the topic using an encryption key shared with the subscriber terminal, and then transmits it to the subscriber terminal together with the encrypted payload.
  • FIG. 1 is a diagram illustrating a network system according to an embodiment.
  • FIG. 2 is a flowchart illustrating an operation of a network system according to an embodiment.
  • FIG. 3 is a flowchart illustrating an operation of a subscriber terminal according to an embodiment.
  • FIG. 4 is a flowchart illustrating an operation of a broker terminal according to an embodiment.
  • 5 to 6 are flowcharts illustrating an operation of a producer terminal according to an embodiment.
  • the network system communicates with a producer terminal generating a topic, a subscriber terminal subscribing to the topic, and the subscriber terminal and the producer terminal,
  • a message including an encrypted topic and an encrypted payload is received from the producer terminal
  • the encrypted topic is decrypted using a second topic encryption key shared with the producer terminal to check the subscriber terminal subscribing to the decrypted topic and a broker terminal for encrypting the topic using a first topic encryption key shared with the subscriber terminal and transmitting the encrypted payload to the subscriber terminal.
  • a message security method performed in a network system includes, by a broker terminal, establishing a session with a subscriber terminal subscribing to a topic, the broker terminal establishing a session with a producer terminal generating the topic Step, when the broker terminal receives a message including an encrypted topic and an encrypted payload from the producer terminal, decrypting the encrypted topic using a second topic encryption key shared with the producer terminal; and the broker terminal identifies a subscriber terminal subscribing to the decrypted topic, encrypts the topic using a first topic encryption key shared with the subscriber terminal, and transmits it to the subscriber terminal together with the encrypted payload including the steps of
  • the network system refers to a system that communicates using a producer terminal and a subscriber terminal, that is, a producer and subscriber model.
  • a network system can operate based on a publish subscription-based message protocol, for example, a lightweight subscription/production (Pub(Publish)/Sub(Subsribe)) message protocol with message queuing telemetry transport (MQTT). : Message Queuing Telemetry Transport) protocol can be applied.
  • a network system may include all systems capable of utilizing a proxy, such as a smart factory or a smart home.
  • FIG. 1 is a diagram illustrating a network system according to an embodiment.
  • the network system 100 may include a subscriber terminal 110 , a broker terminal 120 , a producer terminal 130 , and a master terminal 140 .
  • the subscriber terminal 110 may be connected to the broker terminal in order to subscribe to the topic generated by the producer terminal 130, and the message generated by the producer terminal 130 may be received through the broker terminal 120 relaying the message.
  • the message may include a topic and a payload corresponding to the topic, and each is encrypted.
  • the broker terminal 120 may communicate with the subscriber terminal 110 and the producer terminal 130 .
  • the broker terminal 120 may establish a session with each of the subscriber terminal 110 and the producer terminal 130 for communication. Through this, when the broker terminal 120 receives the payload related to the topic subscribed to by the subscriber terminal 110 from the producer terminal 130, the broker terminal 120 may provide the payload related to the topic to the subscriber terminal.
  • the broker terminal 120 may generate a first topic encryption key 20 when establishing a session with the subscriber terminal 110, and may generate a second topic encryption key 30 when establishing a session with the producer terminal 130 have. At this time, the subscriber terminal 110 may also generate the first topic encryption key 20 when the session is established, and the producer terminal 130 may also generate the second topic encryption key 30 when the session is established.
  • the producer terminal 130 may generate a payload encryption key 40 for encrypting the payload.
  • the producer terminal 130 may receive the group key from the master terminal 140 .
  • the producer terminal 130 may set the group key as the payload encryption key 40 or generate the payload encryption key 40 using the group key.
  • the producer terminal 130 may encrypt the payload using the payload encryption key, and may encrypt the topic using the second topic encryption key 30 . Through this, the producer terminal 130 may generate a message including an encrypted topic and an encrypted payload.
  • the producer terminal 130 may transmit a message to the broker terminal.
  • the master terminal 140 may manage the group key when the group key of the same layer is unified and managed.
  • the master terminal 140 may not be included in the network system 10 when the group key is not unified and managed, and individual payload encryption keys are generated in each of the producer terminals.
  • the master terminal 140 may provide the group key to the producer terminal 130 by establishing a session with the broker terminal 120, and if direct communication with the producer terminal 130 is possible, do not go through the broker terminal 120 It is also possible to directly provide the group key to the producer terminal 130 without the need to.
  • the broker terminal 120 may receive a message from the producer terminal 130 .
  • the broker terminal 120 may classify the encrypted topic and the encrypted payload in the message, and may decrypt the encrypted topic with the second topic encryption key 30 .
  • the broker terminal 120 may check the decrypted topic and the subscriber terminal subscribing to the corresponding topic.
  • the broker terminal 120 may encrypt the decrypted topic with the first topic encryption key 20 and deliver the topic together with the encrypted payload to the subscriber terminal 110 subscribing to the topic.
  • the subscriber terminal 110 may decrypt the received message using the encryption key, decrypt the encrypted topic using the first topic encryption key 20, and use the encrypted payload as the payload encryption key ( 40) can be used for decryption.
  • the subscriber terminal 110 receives the payload encryption key 40 encrypted with the one-time encryption key generated by exchanging the public key with the producer terminal 130, and decrypts it with the one-time encryption key to obtain it.
  • the broker terminal 120 checks the encrypted topic among the encrypted topic and the encrypted payload in the message transmitted between the subscriber terminal 110 and the producer terminal 130, the message is transmitted without checking the message content. Because it can be delivered, the message transmitted between the subscriber terminal 110 and the producer terminal 130 can be encrypted and delivered so that the broker cannot see the message content.
  • the topic can be confirmed and transmitted in the broker terminal 120 in which the session is established, so that message security is possible. Moreover, since the payload transmitted between the subscriber terminal 110 and the producer terminal 130 cannot be checked by the broker terminal 120, the payload cannot be leaked or manipulated by the broker terminal 120, so message security can increase
  • FIG. 2 is a flowchart illustrating an operation of a network system according to an embodiment.
  • the network system includes a subscriber terminal 110 , a broker terminal 120 , and a producer terminal 130 .
  • the subscriber terminal 110 may request session establishment from the broker terminal 120 (S211).
  • the subscriber terminal may generate a public key, for example, a Diffe-Hellman (DH) public key.
  • the subscriber terminal 110 may transmit a public key (DH public key), a signature, and a certificate together when requesting session establishment.
  • DH Diffe-Hellman
  • the broker terminal 120 may respond to the request for session establishment to the subscriber terminal 110 (S213).
  • the broker terminal 120 may store the public key (DH public key), signature, and certificate of the subscriber terminal 110 received according to the session establishment request.
  • the broker terminal 120 may provide its own certificate to the subscriber terminal.
  • the subscriber terminal 110 may perform a handshake with the broker terminal 120 to subscribe to a specific topic.
  • the subscriber terminal 110 and the broker terminal 120 may establish a session (S215).
  • the subscriber terminal 110 and the broker terminal 120 may establish, for example, a Transport Layer Security (TLS) session.
  • TLS Transport Layer Security
  • the subscriber terminal 110 and the broker terminal 120 may generate a session key when establishing a session.
  • the generated session key may be used as the first topic encryption key 20 for encrypting or decrypting a topic in each of the broker terminal 120 and the subscriber terminal 110 .
  • the subscriber terminal 110 may make a connection request for subscription to a specific topic to the broker terminal 120 (S217).
  • the broker terminal 120 may make a connection response to the connection request of the subscriber terminal 110 (S219).
  • the subscriber terminal 110 may request a subscription to a specific topic desired to be subscribed to to the broker terminal 120 (S221).
  • the broker terminal 120 may make a subscription response to the subscription request to the subscriber terminal 110 (S223).
  • the subscriber terminal 110 makes a subscription request for a specific topic between the broker terminals 120 , and when receiving a subscription response corresponding to the subscription request, the subscriber terminal 110 sends a message message for the specific topic desired by the subscriber terminal 110 . Ready to receive.
  • the producer terminal 130 may request the broker terminal 120 to establish a session (S225).
  • the producer terminal 130 may generate the payload encryption key 40 while generating the topic, and may initialize the payload sequence number to 0.
  • the payload sequence number is information counted when a message is transmitted, and may be used to verify the payload in the subscriber terminal 110 and to check whether the message is manipulated or the order is changed.
  • the broker terminal 120 may respond to the request for session establishment to the producer terminal 130 (S227).
  • the broker terminal 120 may transmit the public key (DH public key), the signature, and the certificate received from the subscriber terminal to the producer terminal 130 .
  • the producer terminal 130 may perform a handshake with the broker terminal 120 in order to transmit a message related to the topic.
  • the producer terminal 130 and the broker terminal 120 may establish a session (S229).
  • the producer terminal 130 and the broker terminal 120 may establish, for example, a Transport Layer Security (TLS) session.
  • TLS Transport Layer Security
  • the producer terminal 130 and the broker terminal 120 may generate a session key when establishing a session.
  • the generated session key may be used as the second topic encryption key 30 for encrypting or decrypting the topic in each of the producer terminal 130 and the broker terminal 120 .
  • the producer terminal 130 may verify the signature and determine whether to participate in the topic generated by the producer terminal 130 .
  • the producer terminal 130 may transmit a subscriber authentication message to the broker terminal 120 to complete the subscriber authentication (S231).
  • the broker terminal 120 may transmit the received subscriber authentication message to the subscriber terminal 110 to complete subscriber authentication (S233).
  • the producer terminal 130 may generate the one-time encryption key 50 with the public key (DH public key) transmitted from the subscriber terminal 110 based on the key exchange algorithm with the subscriber terminal 110 .
  • the one-time encryption key 50 is used as an encryption key for encrypting the payload encryption key 40 and delivering it to the subscriber terminal 110, and may also be used for encryption of the payload sequence number. This, one-time encryption key 50 may be used only once for delivery of the payload encryption key 40 .
  • the producer terminal 130 may generate a message and transmit the generated message to the broker terminal 120 (S235).
  • the producer terminal 130 may generate a message by encrypting the topic with the second encryption key 30 and encrypting the payload related to the topic with the payload encryption key 40 .
  • the producer terminal 130 may transmit the payload encryption key and the payload sequence number encrypted with the one-time encryption key together using the message.
  • the producer terminal 130 may transmit the DH public key, signature, and certificate of the producer terminal 130 to the broker terminal 120 together with the message.
  • the producer terminal 130 may give a current payload sequence number to the payload when transmitting the message, encrypt the payload and the payload sequence number with the payload encryption key, and transmit it to the broker terminal 120 .
  • the broker terminal 120 may transmit the message of the producer terminal 130 to the subscriber terminal 110 (S237).
  • the broker terminal 120 may classify the encrypted topic and the encrypted payload in the message of the producer terminal 130 , and decrypt it with the second topic encryption key 30 .
  • the broker terminal 120 may use the decrypted topic to check the subscriber terminal 110 subscribing to the corresponding topic.
  • the broker terminal 120 may encrypt the topic with the first topic encryption key 20 and transmit it to the confirmed subscriber terminal 110 together with the encrypted payload.
  • the subscriber terminal 110 When the subscriber terminal 110 receives a message including the payload encryption key from the broker terminal 120, it generates a one-time encryption key 50 with the public key transmitted from the producer terminal 130 based on the key exchange algorithm, and generates The one-time encryption key 50 can decrypt the encrypted payload encryption key 40 and the encrypted payload sequence number.
  • the subscriber terminal 110 may decrypt the encrypted payload included in the message with the decrypted payload encryption key 40 .
  • the subscriber terminal 110 may decrypt the topic included in the message using the first topic encryption key 20 generated when the session with the broker terminal 120 is established.
  • the subscriber terminal 110 may decrypt the payload sequence number with the payload encryption key 40 .
  • Such a payload sequence number may be used for data verification for confirming manipulation or order change of messages in the subscriber terminal 110 .
  • the subscriber terminal 110 may receive a message corresponding to the subscription-requested topic.
  • the producer terminal 130 may update, ie, change, the payload encryption key 40 at predetermined intervals to enhance message security.
  • the producer terminal 130 may generate a new payload encryption key 60 for changing the payload encryption key 40 .
  • the producer terminal 130 activates the key update flag information in the message in order to deliver the new payload encryption key 60 to the subscriber terminal 110 (eg, change the bit value 0 -> 1, etc.),
  • the new payload encryption key 60 may be encrypted with the existing payload encryption key 40 .
  • the producer terminal 130 may encrypt the payload with the new payload encryption key 60 and transmit it to the broker terminal 120 (S239).
  • the broker terminal 120 may transmit the message of the producer terminal 130 to the subscriber terminal 110 (S241). At this time, the broker terminal 120 may extract the encrypted topic from the message of the producer terminal 130 and decrypt it with the second topic encryption key 30, and encrypt the topic with the first topic encryption key 20 It can be transmitted to the subscriber terminal 110 together with the payload.
  • the subscriber terminal 110 may check that the key is updated by checking the key update flag in the message.
  • the subscriber terminal 110 may decrypt the new payload encryption key 60 using the existing payload encryption key 40 , and decrypt the encrypted payload included in the message with the new payload encryption key 60 . can do. Also, the subscriber terminal 110 may decrypt the encrypted topic included in the encrypted message using the first topic encryption key 20 .
  • the producer terminal 130 and the subscriber terminal 120 may encrypt and decrypt the payload by changing the payload encryption key at predetermined intervals.
  • FIG. 3 is a flowchart illustrating an operation of a subscriber terminal according to an embodiment.
  • the subscriber terminal 110 may establish a session by performing a handshake with the broker terminal 120 ( S310 ).
  • the subscriber terminal 110 may use the session key generated during session establishment as the first topic encryption key for decrypting the topic of the received message.
  • the subscriber terminal 110 may transmit a subscription request for a topic for which message reception is desired to the broker terminal 120 (S320).
  • the subscriber terminal 110 may determine whether a message has been received from the broker terminal 120 (S330).
  • step S330 if the message is not received, the subscriber terminal 110 may proceed to step S340 and wait for a predetermined time to receive the message.
  • step S330 upon receiving the message, the subscriber terminal 110 may proceed to step S340.
  • the subscriber terminal 110 may check the message by decrypting the message. In this case, the subscriber terminal may decrypt the encrypted topic in the message with the first topic encryption key. Also, the subscriber terminal 110 may decrypt the encrypted payload in the message with the payload encryption key.
  • the subscriber terminal 110 when the subscriber terminal 110 receives the payload encryption key, it generates a one-time encryption key using the public key (DH public key) transmitted from the producer terminal 130 using a key exchange algorithm, and the encrypted pay It can be obtained by decrypting the load encryption key with a one-time encryption key.
  • the public key DH public key
  • the new payload encryption key encrypted with the existing payload encryption key may be decrypted to obtain a new payload encryption key.
  • the subscriber terminal 110 may decrypt the encrypted payload.
  • the subscriber terminal 110 may determine whether to end the operation (S350).
  • step S350 if the operation is not terminated, the subscriber terminal 110 may proceed to step S330 and wait for reception of the next message. However, the subscriber terminal 110 may proceed to another step as needed.
  • the subscriber terminal 110 may end the operation.
  • FIG. 4 is a flowchart illustrating an operation of a broker terminal according to an embodiment.
  • the broker terminal 120 may establish a session with the subscriber terminal 110 ( S410 ).
  • the broker terminal 120 may use the session key generated during session establishment as a second topic encryption key for encrypting the topic of a message to be transmitted to the subscriber terminal 110 .
  • the broker terminal 120 may set up a subscription with the subscriber terminal 110 for a specific topic to be subscribed to in the subscriber terminal 110 (S420).
  • the broker terminal 120 may check whether a session establishment request exists from the producer terminal 130 (S430).
  • step S430 if there is no session establishment request from the producer terminal 130 , the broker terminal 120 waits for a predetermined time and then proceeds to step S430 to check whether the session establishment request exists.
  • step S430 if there is a session establishment request from the producer terminal 130 , the broker terminal 120 may proceed to step S440 .
  • the broker terminal 120 may establish a session with the producer terminal 130 (S440).
  • the broker terminal 120 may use the session key generated during session establishment as the second topic encryption key for decrypting the topic of the message received from the producer terminal 130 .
  • the broker terminal 120 may determine whether a message has been received from the producer terminal 130 (S450).
  • step S450 if a message is not received from the producer terminal 130 , the broker terminal 120 waits for a predetermined time and then proceeds to step S450 to determine reception of the message from the producer terminal 130 .
  • step S450 when a message is received from the producer terminal 130, the broker terminal 120 may proceed to step S460.
  • the broker terminal 120 may decrypt the encrypted topic in the message with the second topic encryption key, and encrypt the decrypted topic with the first topic encryption key (S460).
  • the broker terminal 120 may transmit a message including the topic encrypted with the first topic encryption key and the encrypted payload in the message to the subscriber terminal 110 (S470).
  • the broker terminal 120 may determine whether to end the operation (S480).
  • step S480 if the operation is not terminated, the broker terminal 120 may proceed to step S450 and wait for reception of the next message. However, the broker terminal 120 may proceed to another step as needed.
  • the broker terminal 120 may end the operation.
  • 5 to 6 are flowcharts illustrating an operation of a producer terminal according to an embodiment.
  • the producer terminal 130 may establish a session ( S511 ).
  • the producer terminal 130 may establish a session when there is a message to be transmitted for the topic.
  • the producer terminal 130 may check whether to use the group key (S513). These group keys may be unified and managed as one in the same layer for payload transmission. At this time, the producer terminal 130 must receive the group key from the master terminal that manages the group key, that is, the master node. For this reason, when the producer terminal 130 newly enters the network system, it can determine whether to use the group key or its own payload encryption key while generating the topic.
  • step S5 As a result of checking in step S513, if the group key is not used, the producer terminal 130 may proceed to step S525.
  • step S513 if the group key is used, the producer terminal 130 proceeds to step S515.
  • the producer terminal 130 to register the topic of '/building/5thfloor/temperature' may use the /building/5thfloor key.
  • the producer terminal 130 may search for the group key to receive the group key from the master terminal (S515).
  • the producer terminal 130 may determine whether the group key has been received within a preset time according to the group key search (S517).
  • step S517 if the group key is received within a preset time, the producer terminal 130 may proceed to step S519.
  • the producer terminal 130 may generate a payload encryption key using the group key and proceed to step S525.
  • the producer terminal 130 may directly use the group key as the payload encryption key, but may also generate the payload encryption key using the group key.
  • step S517 if the group key is not received within a preset time, the producer terminal 130 may proceed to step S521.
  • the producer terminal 130 must receive the group key from the master terminal.
  • a temporary payload key may be generated and used in a situation in which it is difficult to receive the group key.
  • the producer terminal 130 may generate a temporary payload key (S521).
  • the producer terminal 130 may generate a payload encryption key using the temporary payload key, and proceed to step S521 (S523). After receiving the group key, the producer terminal 130 performs the payload encryption key update operation described in steps S239 to S241 of FIG. 2 to generate the payload encryption key generated as a temporary payload key using the group key. It can be used by converting the payload encryption key.
  • the producer terminal 130 may check whether a subscriber authentication request has been received from the broker terminal 120 (S525).
  • step S525 if the subscriber is not authenticated, the producer terminal 130 may proceed to step S535.
  • step S525 if the subscriber is authenticated, the producer terminal 130 may proceed to step S527.
  • the producer terminal 130 may generate a message by encrypting the topic and the payload.
  • the producer terminal 130 may generate a payload encryption key while generating a topic when not using the group key. In this case, the producer terminal 130 may also initialize the payload sequence number to 0.
  • the producer terminal 130 may encrypt the topic with the topic encryption key generated when establishing a session with the broker terminal, and the payload may be encrypted with the payload encryption key.
  • the producer terminal 130 may generate a one-time encryption key using the public key received from the subscriber terminal 110 .
  • the producer terminal 130 may encrypt the payload encryption key with a one-time encryption key.
  • the producer terminal 130 may transmit a message to the broker terminal (S529).
  • the producer terminal 130 transmits the payload encryption key to the producer terminal, there is no need to transmit the payload encryption key when transmitting the next message.
  • the producer terminal 130 may check whether to update the payload encryption key when a predetermined period or the like arrives (S531).
  • step S531 if the payload encryption key is not updated, the producer terminal 130 may generate a message by proceeding to step S527.
  • step S531 when updating the payload encryption key, the producer terminal 130 may proceed to step S533.
  • the producer terminal 130 may generate a new payload encryption key and encrypt the new payload encryption key with the existing payload encryption key (S533).
  • the producer terminal 130 may encrypt the payload to be transmitted with the new payload encryption key if there is a payload to be transmitted.
  • the producer terminal 130 may transmit a message in which the payload encryption key is updated including the new encrypted payload encryption key to the subscriber terminal 110 through the broker terminal 120 .
  • the producer terminal 130 may determine whether to end the operation (S537).
  • step S537 if the operation is not terminated, the producer terminal 130 may proceed to step S527 to generate a message. However, the producer terminal 130 may proceed to another step as needed.
  • the broker terminal 120 may end the operation.
  • ' ⁇ unit' used in this embodiment means software or hardware components such as field programmable gate array (FPGA) or ASIC, and ' ⁇ unit' performs certain roles.
  • ' ⁇ part' is not limited to software or hardware.
  • the ' ⁇ unit' may be configured to reside on an addressable storage medium or may be configured to refresh one or more processors.
  • ' ⁇ ' refers to components such as software components, object-oriented software components, class components, and task components, and processes, functions, properties, and procedures. , subroutines, segments of program patent code, drivers, firmware, microcode, circuitry, data, databases, data structures, tables, arrays, and variables.
  • components and ' ⁇ units' may be implemented to play one or more CPUs in a device or secure multimedia card.
  • the message security method may be implemented as a computer program (or computer program product) including instructions executable by a computer.
  • the computer program includes programmable machine instructions processed by a processor, and may be implemented in a high-level programming language, an object-oriented programming language, an assembly language, or a machine language.
  • the computer program may be recorded in a tangible computer-readable recording medium (eg, a memory, a hard disk, a magnetic/optical medium, or a solid-state drive (SSD), etc.).
  • the message security method may be implemented by executing the computer program as described above by a computing device.
  • the computing device may include at least a portion of a processor, a memory, a storage device, a high-speed interface connected to the memory and the high-speed expansion port, and a low-speed interface connected to the low-speed bus and the storage device.
  • a processor may include at least a portion of a processor, a memory, a storage device, a high-speed interface connected to the memory and the high-speed expansion port, and a low-speed interface connected to the low-speed bus and the storage device.
  • Each of these components is connected to each other using various buses, and may be mounted on a common motherboard or in any other suitable manner.
  • the processor may process a command within the computing device, such as for displaying graphic information for providing a Graphical User Interface (GUI) on an external input or output device, such as a display connected to a high-speed interface.
  • GUI Graphical User Interface
  • Examples are instructions stored in memory or a storage device.
  • multiple processors and/or multiple buses may be used with multiple memories and types of memory as appropriate.
  • the processor may be implemented as a chipset formed by chips including a plurality of independent analog and/or digital processors.
  • Memory also stores information within the computing device.
  • the memory may be configured as a volatile memory unit or a set thereof.
  • the memory may be configured as a non-volatile memory unit or a set thereof.
  • the memory may also be another form of computer readable medium such as, for example, a magnetic or optical disk.
  • a storage device may provide a large-capacity storage space to the computing device.
  • a storage device may be a computer-readable medium or a component comprising such a medium, and may include, for example, devices or other components within a storage area network (SAN), a floppy disk device, a hard disk device, an optical disk device, or a tape device, a flash memory, or other semiconductor memory device or device array similar thereto.
  • SAN storage area network
  • floppy disk device a hard disk device
  • an optical disk device or a tape device
  • flash memory or other semiconductor memory device or device array similar thereto.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Hardware Design (AREA)
  • Computing Systems (AREA)
  • General Engineering & Computer Science (AREA)
  • Multimedia (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Un mode de réalisation de la présente invention concerne un système de réseaux qui comprend : un terminal producteur destiné à générer un sujet ; un terminal abonné destiné à s'abonner au sujet ; et un terminal courtier qui communique avec le terminal abonné et le terminal producteur, qui déchiffre un sujet chiffré au moyen d'une deuxième clé de chiffrement de sujet partagée avec le terminal producteur afin d'identifier un terminal abonné qui s'abonne au sujet déchiffré lorsqu'un message incluant le sujet chiffré et une charge utile chiffrée est reçu du terminal producteur, et qui chiffre le sujet au moyen d'une première clé de chiffrement de sujet partagée avec le terminal abonné afin de transmettre le sujet chiffré en même temps que la charge utile chiffrée au terminal abonné.
PCT/KR2020/013707 2019-11-29 2020-10-08 Système de réseaux et son procédé de sécurité de messages WO2021107389A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
KR1020190156578A KR102265611B1 (ko) 2019-11-29 2019-11-29 네트워크 시스템 및 그것의 메시지 보안 방법
KR10-2019-0156578 2019-11-29

Publications (1)

Publication Number Publication Date
WO2021107389A1 true WO2021107389A1 (fr) 2021-06-03

Family

ID=76129353

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2020/013707 WO2021107389A1 (fr) 2019-11-29 2020-10-08 Système de réseaux et son procédé de sécurité de messages

Country Status (2)

Country Link
KR (1) KR102265611B1 (fr)
WO (1) WO2021107389A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11936773B2 (en) 2021-11-09 2024-03-19 Penta Security Inc. Encryption key management method in data subscription system

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20120087550A (ko) * 2011-01-28 2012-08-07 오픈스택 주식회사 암호 통신 방법 및 이를 이용한 암호 통신 시스템
KR20160050766A (ko) * 2014-10-31 2016-05-11 삼성에스디에스 주식회사 메시지 통신 장치 및 방법
KR101760376B1 (ko) * 2015-11-26 2017-07-24 고려대학교 산학협력단 안전한 메신저 서비스를 제공하는 단말 및 방법
KR20190007336A (ko) * 2017-07-12 2019-01-22 주식회사 코스콤 보안채널 생성 방법 및 그 장치와 이를 이용한 보안정보의 송수신 방법 및 그 장치
KR102028151B1 (ko) * 2017-04-07 2019-10-02 주식회사트러스트홀딩스 장치 인증키를 이용한 데이터 암호화 방법 및 시스템

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20120087550A (ko) * 2011-01-28 2012-08-07 오픈스택 주식회사 암호 통신 방법 및 이를 이용한 암호 통신 시스템
KR20160050766A (ko) * 2014-10-31 2016-05-11 삼성에스디에스 주식회사 메시지 통신 장치 및 방법
KR101760376B1 (ko) * 2015-11-26 2017-07-24 고려대학교 산학협력단 안전한 메신저 서비스를 제공하는 단말 및 방법
KR102028151B1 (ko) * 2017-04-07 2019-10-02 주식회사트러스트홀딩스 장치 인증키를 이용한 데이터 암호화 방법 및 시스템
KR20190007336A (ko) * 2017-07-12 2019-01-22 주식회사 코스콤 보안채널 생성 방법 및 그 장치와 이를 이용한 보안정보의 송수신 방법 및 그 장치

Non-Patent Citations (1)

* Cited by examiner, † Cited by third party
Title
LEE HYUNWOO, LIM JUNGHWAN, KWON TED LTAEKYOUNGR: "MQTLS: Toward Secure MQTT Communication with an Untrusted Broker", 2019 INTERNATIONAL CONFERENCE ON INFORMATION AND COMMUNICATION TECHNOLOGY CONVERGENCE (ICTC), IEEE, 1 October 2019 (2019-10-01) - 18 October 2019 (2019-10-18), pages 53 - 58, XP055815920, ISBN: 978-1-7281-0893-3, DOI: 10.1109/ICTC46691.2019.8940001 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11936773B2 (en) 2021-11-09 2024-03-19 Penta Security Inc. Encryption key management method in data subscription system

Also Published As

Publication number Publication date
KR20210067208A (ko) 2021-06-08
KR102265611B1 (ko) 2021-06-15

Similar Documents

Publication Publication Date Title
WO2016137304A1 (fr) Sécurité de bout en bout sur la base de zone de confiance
US7978858B2 (en) Terminal device, group management server, network communication system, and method for generating encryption key
WO2020029585A1 (fr) Procédé et dispositif de modélisation de fédération de réseau neuronal faisant intervenir un apprentissage par transfert et support d'informations
WO2015147547A1 (fr) Procédé et appareil permettant la prise en charge de l'ouverture de session au moyen d'un terminal d'utilisateur
WO2016190476A1 (fr) Procédé destiné à la gestion de clé de chiffrement pour service en nuage et appareil correspondant
WO2014063455A1 (fr) Procédé et système de messagerie instantanée
WO2009145495A2 (fr) Procédé et appareil pour fournir un service de diffusion à l'aide d'une clé de cryptage dans un système de communication
WO2019132272A1 (fr) Identifiant en tant que service basé sur une chaîne de blocs
WO2019074326A1 (fr) Procédé et appareil de paiement hors ligne sécurisé
WO2018151390A1 (fr) Dispositif de l'internet des objets
WO2020101087A1 (fr) Système et procédé de chiffrement pour traitement d'informations personnelles
WO2009151277A2 (fr) Procédé de distribution de clés de chiffrement dans un système de diffusion mobile et système correspondant
WO2019182377A1 (fr) Procédé, dispositif électronique et support d'enregistrement lisible par ordinateur permettant de générer des informations d'adresse utilisées pour une transaction de cryptomonnaie à base de chaîne de blocs
WO2011122912A2 (fr) Procédé et système de gestion d'une clé de chiffrement pour un service de diffusion
WO2015199271A1 (fr) Procédé et système de partage de fichiers sur p2p
WO2021162341A1 (fr) Procédé de fonctionnement d'un système de service de transfert de fonds par chaîne de blocs et portefeuille électronique pour transfert de fonds
WO2021107389A1 (fr) Système de réseaux et son procédé de sécurité de messages
WO2017206602A1 (fr) Procédé et appareil de traitement de données
WO2022177204A1 (fr) Système décentralisé basé sur un did pour stocker et partager des données d'utilisateur
WO2020111403A1 (fr) Procédé de sécurité d'image basé sur un flux chiffré à l'aide d'un tatouage numérique nul, serveur et support d'enregistrement lisible par ordinateur
WO2022080784A1 (fr) Procédé et dispositif de distribution de clés quantiques
WO2016111407A1 (fr) Procédé de communication en réseau avec fonction de récupération de session de terminal
WO2023149660A1 (fr) Procédé et système d'apprentissage fédéré basé sur une signature de groupe, et support d'enregistrement pour la mise en œuvre de ceux-ci
WO2018004114A2 (fr) Système d'authentification de proxy, et procédé d'authentification pour fournir un service de proxy
WO2018128264A1 (fr) Procédé de gestion de clé dans un système de sécurité d'un environnement de multidiffusion

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20894165

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20894165

Country of ref document: EP

Kind code of ref document: A1