KR102302765B1 - Wireless-communication terminal and method to control client device - Google Patents

Abstract

A wireless communication terminal comprises: a communicator configured to perform short-range wireless communication, a first storage, a second storage separated from the first storage, and a processor. The processor is configured to establish short-range wireless communication with a first external terminal through the communicator, interact with the first external terminal through short-range wireless communication to detect existence of a first data unit associated with a client device among data units stored in the first external terminal, selectively acquire the first data unit from the first external terminal and store it in the first storage, acquire second data units among the data units from the first external terminal and store them in the second storage, and update the client device using the first data unit stored in the first storage.

Description

WIRELESS-COMMUNICATION TERMINAL AND METHOD TO CONTROL CLIENT DEVICE

The present invention relates to devices for performing wireless communication, and more particularly, to a wireless communication terminal and method for controlling a client device.

Wireless communication refers to a communication technology that transmits information to a remote location using radio waves without a line connecting devices. In general, a wireless network includes terminals and a plurality of base stations performing wireless communication with the terminals, wherein the terminals communicate data with each other through the plurality of base stations.

Recently, various types of short-range wireless communication have been proposed. Terminals may establish short-range wireless communication and communicate data through short-range wireless communication without going through a base station. Here, short-range wireless communication may include various types of techniques for transmitting information at a relatively short distance without contacting each other.

The above description is only for helping the understanding of the background of the technical spirit of the present invention, and therefore it cannot be understood as the content corresponding to the prior art known to those skilled in the art of the present invention.

SUMMARY Embodiments of the present invention provide a wireless communication terminal and method that provide improved convenience in distributing and/or providing data units. For example, data may be automatically distributed and/or provided via wireless communication terminals without each of the wireless communication terminals having to access a specific server and/or device to download the data.

A wireless communication terminal for controlling a client device according to an embodiment of the present invention includes a communicator configured to perform short-range wireless communication; first storage; a second storage separate from the first storage; and a processor configured to control the first and second storages and the communicator, wherein the processor establishes the short-range wireless communication with a first external terminal through the communicator; interact with the first external terminal through the short-range wireless communication to detect the presence of a first data unit associated with the client device among data units stored in the first external terminal; selectively acquiring the first data unit from the first external terminal and storing it in the first storage; obtaining second data units among the data units from the first external terminal and storing them in the second storage; and update the client device using the first data unit stored in the first storage.

The processor establishes the short-range wireless communication with a second external terminal through the communicator; and provide at least one list representing the first data unit of the first storage and the second data unit of the second storage to the second external terminal.

The processor may be configured to transmit, to the second external terminal, at least one of the first data unit and the second data unit corresponding to a request from the second external terminal.

The processor is configured to receive the list of data units from the first external terminal through the short-range wireless communication; and detect the presence of the first data unit among the data units according to the list.

The first storage may be configured to store an identifier, and the processor may be configured to detect the presence of the first one of the data units by comparing the identifier to the list.

The first storage may be configured to store first meta data indicating a version associated with the client device, and wherein the processor is configured to: receive second metadata; compare the second metadata with the first metadata; and obtain the first data unit from the first external terminal based on a result of the comparison.

The first storage may be configured to further store a verification key associated with the client device, wherein the processor further receives authentication data corresponding to the first data unit from the first external terminal through the short-range wireless communication do; verify the authentication data using the verification key; and obtain the first data unit from the first external terminal, further based on whether the verification has passed.

the processor establishes the short-range wireless communication with the client device through the communicator; and provide the first data unit to the client device via the short-range wireless communication to update the client device.

Another aspect of the present invention relates to a method for controlling a client device. The method includes: establishing short-range wireless communication with a first external terminal; detecting the presence of a first data unit associated with the client device among data units stored in the first external terminal by interacting with the first external terminal through the short-range wireless communication; selectively acquiring the first data unit from the first external terminal and storing the first data unit in a first storage; obtaining second data units among the data units from the first external terminal and storing them in a second storage separate from the first storage; and updating the client device using the first data unit stored in the first storage.

The method includes establishing the short-range wireless communication with a second external terminal; and providing at least one list indicating the first data unit of the first storage and the second data unit of the second storage to the second external terminal.

The method may further include transmitting at least one of the first data unit and the second data unit corresponding to the request from the second external terminal to the second external terminal.

The detecting of the existence of the first data unit may include: receiving a list of the data units from the first external terminal through the short-range wireless communication; and detecting the presence of the first data unit among the data units according to the list.

The method may further include receiving first metadata indicating a version of the first data unit from the first external terminal via the short-range wireless communication, wherein the first storage is a version associated with the client device. may be configured to store second metadata representing and obtaining the first data unit from the first external terminal based on a result of the comparison.

The method may further include receiving authentication data corresponding to the first data unit from the first external terminal through the short-range wireless communication, wherein the first storage further stores a verification key associated with the client device. may be configured to store, wherein obtaining the first data unit includes: verifying the authentication data using the verification key; and obtaining the first data unit from the first external terminal further based on whether the verification has passed.

According to embodiments of the present invention, a wireless communication terminal and method for providing improved convenience in distributing and/or providing data units are provided.

1 is a block diagram showing a data sharing system according to an embodiment of the present invention.
FIG. 2 is a block diagram showing an embodiment of any one of the first to third IOT terminals 110 to 130 of FIG. 1 .
3 is a diagram conceptually illustrating an embodiment of data stored in the main storage and the sub storage of FIG. 2 .
4 is a diagram exemplarily showing data stored in each of two IOT terminals.
5 is a diagram exemplarily showing data stored in each of the IOT terminals after the IOT terminals of FIG. 4 share a data unit through short-range wireless communication.
6 is a flowchart illustrating a method of receiving data units from an external IOT terminal and storing them in main and sub storages according to an embodiment of the present invention.
7 is a flowchart illustrating a method of providing data units to an external IOT terminal.
8 is a flowchart illustrating an embodiment of a method of receiving data units from an external IOT terminal and storing the data units in main and sub storages.
9 is a diagram conceptually illustrating another embodiment of data stored in the main storage and the sub storage of FIG. 2 .
10 is a flowchart illustrating an embodiment of step S340 of FIG. 8 .

Hereinafter, preferred embodiments according to the present invention will be described in detail with reference to the accompanying drawings. It should be noted that in the following description, only parts necessary for understanding the operation according to the present invention are described, and descriptions of other parts will be omitted so as not to obscure the gist of the present invention. Also, the present invention is not limited to the embodiments described herein and may be embodied in other forms. However, the embodiments described herein are provided to explain in detail enough to easily implement the technical spirit of the present invention to those of ordinary skill in the art to which the present invention pertains.

Throughout the specification, when a part is "connected" with another part, this includes not only the case of being "directly connected" but also the case of being "indirectly connected" with another element interposed therebetween. . The terminology used herein is for the purpose of describing particular embodiments and not for limiting the present invention. Throughout the specification, when a part "includes" a certain element, it means that other elements may be further included, rather than excluding other elements, unless otherwise stated. “At least any one of X, Y, and Z” and “at least any one selected from the group consisting of X, Y, and Z” means one X, one Y, one Z, or two of X, Y, and Z or It can be interpreted as any combination of more (eg, XYZ, XYY, YZ, ZZ). Herein, "and/or" includes any combination of one or more of the elements.

1 is a block diagram showing a data sharing system according to an embodiment of the present invention.

Referring to FIG. 1 , the data sharing system 100 may include a beacon terminal 105 and first to third Internet of Things (IOT) terminals 110 to 130 .

The beacon terminal 105 and the first to third IOT terminals 110 to 130 may communicate with each other through short-range wireless communication. The wireless communication terminals exemplified by the IOT terminals 110 to 130 may be installed and/or loaded to the first to third moving means VH1 to VH3, respectively. In this case, the first to third IOT terminals 110 to 130 move together with the first to third moving means VH1 to VH3, respectively. When the beacon terminal 105 and the first to third IOT terminals 110 to 130 are adjacent to each other, they may establish short-range wireless communication such as Bluetooth communication and share data units through the established short-range wireless communication. For example, the data unit may be transmitted to the third IOT terminal 130 through the beacon terminal 105 , the first IOT terminal 110 , and the second IOT terminal 120 in sequence. In this way, each IOT terminal can receive a new data unit from the other IOT terminal while providing an arbitrary data unit to the other IOT terminal through short-range wireless communication with the other IOT terminal. Similarly, the beacon terminal 105 may provide an arbitrary data unit to the IOT terminal and receive a new data unit from the IOT terminal through short-range wireless communication with the IOT terminal. In embodiments, the beacon terminal 105 may be configured similarly to each of the first to third IOT terminals 110 to 130 , except that the first to third IOT terminals 110 to 130 have a different fixed structure. can be installed on

Short-range wireless communication includes Bluetooth communication, Wi-Fi communication, LTE D2D (Device-to-Device) communication, RFID (Radio Frequency IDentification) communication, Magnetic Secure Transmission communication, Zigbee communication, infrared ( It may include various types of technologies that transmit information without contacting each other at a relatively short distance, such as IrDA (infrared Data Association) communication.

First to third client terminals 115 to 135 may be provided. The first to third client devices 115 to 135 may be loaded and/or installed in the first to third moving means VH1 to VH3, respectively. Therefore, the first to third client devices 115 to 135 may be adjacent to the first to third IOT terminals 110 to 130, respectively, and may communicate with them through short-range wireless communication. In embodiments, the first to third client devices 115 to 135 may be components integrated into the first to third IOT terminals 110 to 130, respectively.

Each of the first to third client devices 115 to 135 may be a computer device provided for various purposes. For example, each of the first to third client devices 115 to 135 is an ECU (e.g., a navigation device providing a route guidance function, an engine, and an ECU (Anti-lock Brake System)) that controls various functions of the corresponding moving means, such as an anti-lock brake system (ABS). Electronic Control Unit), a transmission control unit (TCU) that performs control on a transmission that controls an engine gear ratio, and the like. Firmware and/or software included in each of the first to third client devices 115 to 135 needs to be updated. To this end, the manager may store a data unit in the beacon terminal 105, and the data unit of the beacon terminal 105 may be transmitted to the first to third IOT terminals 110 to 130 as described above. . In this case, at least one of the first to third IOT terminals 110 to 130 may update the firmware and/or software of the corresponding client device using the transmitted data unit. Accordingly, without the administrator's terminal accessing the IOT terminal and providing data, the corresponding IOT terminal can acquire the data unit through other IOT terminals and update the client device using the acquired data unit. Additionally, by storing the data unit only in the beacon terminal 105 without the hassle of the administrator identifying and accessing the IOT terminal, the data unit is automatically distributed and distributed to the corresponding IOT terminal by the plurality of IOT terminals 110 to 130 / or may be provided. Accordingly, it may provide improved convenience in distributing and/or providing data units.

In FIG. 1 , three IOT terminals 110 to 130 and three client devices 115 to 135 are shown, but this is for convenience of description and more IOT terminals and client devices may be provided. .

FIG. 2 is a block diagram showing an embodiment of any one of the first to third IOT terminals 110 to 130 of FIG. 1 . A client device 1m5 loaded on the mobile means together with the IOT terminal 200 is further illustrated in FIG. 2 .

Referring to FIG. 2 , the ITO terminal 200 may include a communicator 210 , a data sharer 220 , a main storage 230 , and a sub-storage 240 .

The communicator 210 is connected to the data sharer 220 . The communicator 210 may perform short-range wireless communication in response to the control of the data sharer 220 . The communicator 210 establishes short-range wireless communication with the external IOT terminal in response to the control of the data sharer 220 , and provides communication between the data sharer 220 and the external IOT terminal. In addition, the communicator 210 establishes short-range wireless communication with the client device 1m5 in response to the control of the data sharer 220 , and provides communication between the data sharer 220 and the client device 1m5 .

The data sharer 220 is configured to control the communicator 210 , the main storage 230 , and the sub storage 240 . The data sharer 220 may include a communication interface (I/F) 221 , a sharing control unit 222 , a storage access unit 223 , and a client update unit 224 .

The communication interface 221 may interface between the data sharer 220 and the communicator 210 . The communication interface 221 may receive data from the external IOT terminal and/or the client device 1m5 and transmit the received data to a suitable component of the data sharer 220 . Further, the communication interface 221 is configured to transmit data from the components of the data sharer 220 to the external IOT terminal and/or the client device 1m5.

The sharing control unit 222 may control overall operations of the data sharer 220 . The sharing control unit 222 may interact with the external IOT terminal through the communication interface 221 to detect the presence of a data unit associated with the client device 1m5 in the external IOT terminal.

The storage access unit 223 may access the main storage 230 and the sub storage 240 to read and write data. The sharing control unit 222 may selectively acquire the sensed data unit from the external IOT terminal, and store the acquired data unit in the main storage 230 through the storage access unit 223 . In addition, the sharing control unit 222 acquires data units not associated with the client device 1m5 among the data units stored in the external IOT terminal, and transfers the obtained data units to the sub storage 240 through the storage access unit 223 . can be stored in

In addition, the sharing control unit 222 reads data units from the main storage 230 and the sub storage 240 through the storage access unit 223 in response to a request from the external IOT terminal, and reads the read data units from the external IOT. It can be provided to the terminal.

Operations of the sharing control unit 222 will be described in detail with reference to FIGS. 4 and 5 .

The client update unit 224 may update the function module FM of the client device 1m5 by using the data unit stored in the main storage 230 in response to the control of the sharing control unit 222 . In this case, the function module FM is software and/or firmware installed in the client device 1m5. The client update unit 224 obtains the data unit stored in the main storage 230 through the storage access unit 223 , provides the obtained data unit to the client device 1m5 , and provides the data unit to the client device 1m5 . You can command the update using .

The main storage 230 and the sub storage 240 are connected to the data sharer 220 . The main storage 230 and the sub storage 240 may write and read data in response to the control of the data sharer 220 . The main storage 230 and the sub storage 240 may include a hard disk drive (HDD) that retains data even when power is cut off, a solid state drive (SSD), such as a flash memory, etc. They may be non-volatile storage media.

The sub storage 240 is physically and/or logically separated from the main storage 230 . Accordingly, data and/or information may not be mixed and stored in the main storage 230 and the sub storage 240 . For example, a data unit that is not associated with the client device 1m5 is received from an external IOT terminal for delivery to another IOT terminal and stored in the IOT terminal 200 , but is particularly stored in the sub storage 240 and stored in the main storage Data stored in the 230, for example, may be stored in a space separated from the data unit associated with the client device 1m5. Accordingly, each of the main storage 230 and the sub storage 240 may provide an improved security level and reliability for data stored therein.

3 is a diagram conceptually illustrating an embodiment of data stored in the main storage and the sub storage of FIG. 2 .

2 and 3 , the main storage 230 may store first and second data units DU1 and DU2. In FIG. 2 , the main storage 230 is illustrated as storing two data units DU1 and DU2 , but this is only for convenience of description and the number of data units stored in the main storage 230 is not limited thereto. does not

The first and second data units DU1 and DU2 stored in the main storage 230 may correspond to software and/or firmwares of the client device 1m5 such as the function module FM shown in FIG. 2 . . For example, the first and second data units DU1 and DU2 may be installation and/or update files for at least one function module FM of the client device 1m5 . The data units DU1 and DU2 stored in the main storage 230 may be defined as main data units MDU.

The main storage 230 may further store first and second data unit identifiers DUID1 and DUID2 respectively corresponding to the first and second data units DU1 and DU2 . The first and second data units DU1 and DU2 stored in the main storage 230 may be identified through the first and second data unit identifiers DUID1 and DUID2 . In other words, at least one function module FM included in the client device 1m5 may be identified through the first and second data unit identifiers DUID1 and DUID2 . The data unit identifiers DUID1 and DUID2 stored in the main storage 230 may be defined as a main data list MDL. The main data list MDL may be stored in advance in the main storage 230 when the IOT terminal 200 is manufactured, for example.

The main storage 230 may further store the first and second version information VI1 and VI2 respectively mapped to the first and second data unit identifiers DUID1 and DUID2 . Versions of the first and second data units DU1 and DU2 may be identified through the first and second version information VI1 and VI2 . The version information VI1 and VI2 stored in the main storage 230 may be defined as main metadata MMT.

When any one of the main data units (MDU) is updated according to communication with the external IOT terminal, the client update unit 224 uses the updated main data unit to update the function module FM of the client device 1m5. can be updated. Version information corresponding to the updated main data unit may also be received from the external IOT terminal and updated in the main metadata MMT.

The sub storage 240 is separated from the main storage 230 . The sub storage 240 is configured with third and fourth data unit identifiers DUID3 and DUID4 corresponding to the third and fourth data units DU3 and DU4 and the third and fourth data units DU3 and DU4, respectively. ), and third and fourth version information VI3 and VI4 mapped to the third and fourth data unit identifiers DUID3 and DUID4, respectively. In FIG. 2 , the sub storage 240 is shown to store two data units DU3 and DU4 , but this is only for convenience of description and the number of data units stored in the sub storage 240 is not limited thereto. does not

The third and fourth data units DU3 and DU4 stored in the sub storage 240 may be those that are not associated with the function block FM of the client device 1m5 . The data units DU3 and DU4 stored in the sub storage 240 may be defined as sub data units SDU. Data units DU3 and DU4 stored in the sub storage 240 may be identified through the data unit identifiers DUID3 and DUID4 stored in the sub storage 240 . The data unit identifiers DUID3 and DUID4 stored in the sub storage 240 may be defined as a sub data list SDL. Versions of the data units DU3 and DU4 stored in the sub storage 240 may be identified through the version information VI3 and VI4 stored in the sub storage 240 . The version information VI3 and VI4 stored in the sub storage 240 may be defined as sub metadata SMT.

Each of the IOT terminals that have established short-range wireless communication refer to each other's main data list (MDL) and main metadata (MMT), and the sub data list (SDL) and sub metadata (SMT) of the other party's respective data units. It can be determined whether to obtain

4 is a diagram exemplarily showing data stored in each of two IOT terminals. 5 is a diagram exemplarily showing data stored in each of the IOT terminals after the IOT terminals of FIG. 4 share a data unit through short-range wireless communication. For convenience of description, the data shown in FIGS. 4 and 5 is exemplified as being stored in the first IOT terminal 110 and the second IOT terminal 120 .

1, 2 and 4 , the main storage 230 of the first IOT terminal 110 includes first main data units MDU1, a first main data list MDL1, and a first main meta The data MMT1 is stored, and the sub storage 240 of the first IOT terminal 110 includes the first sub data units SDU1, the first sub data list SDL1, and the first sub metadata SMT1. save the The first main data units MDU1 include first and second data units DU1 and DU2, and the first main data list MDL1 includes first and second data unit identifiers DUID1 and DUID2. , and the first main metadata MMT1 is exemplified as including the first and second version information VI1 and VI2. The first sub data units SDU1 include third and fourth data units DU3 and DU4, and the first sub data list SDL1 includes third and fourth data unit identifiers DUID3 and DUID4. , and the first sub-meta data SMT1 is exemplified as including the third and fourth version information VI3 and VI4.

The main storage 230 of the second IOT terminal 120 stores the second main data units MDU2, the second main data list MDL2, and the second main metadata MMT2, and the second IOT terminal The sub storage 240 of 120 stores the second sub data units SDU2 , the second sub data list SDL2 , and the second sub metadata SMT2 . The second main data units MDU2 include fifth and sixth data units DU5 and DU6, and the second main data list MDL2 includes fifth and sixth data unit identifiers DUID5 and DUID6. , and the second main metadata MMT2 is exemplified as including fifth and sixth version information VI5 and VI6. The second sub data units SDU2 include first and second data units DU1' and DU2', and the second sub data list SDL2 includes first and second data unit identifiers DUID1, DUID2), and the second sub-meta data SMT2 is exemplified as including first and second version information VI1' and VI2'.

The first and second IOT terminals 110 and 120 may establish short-range wireless communication when they are adjacent to each other. The sharing control unit 222 of each of the first and second IOT terminals 110 and 120 may provide its own main data list (MDL) and sub data list (SDL) to the other party through short-range wireless communication. In addition, the sharing control unit 222 of each of the first and second IOT terminals 110 and 120 may provide its own main metadata (MMT) and sub metadata (SMT) to the other party through short-range wireless communication. .

The sharing control unit 222 of the first IOT terminal 110 refers to the second main data list MDL2 and the second sub data list SDL2 received from the second IOT terminal 120, and the first client device ( It may be detected whether a data unit associated with 115 exists in the second IOT terminal 120 . This may be determined by comparing the received lists MDL2 and SDL2 with the first main data list MDL1. In FIG. 4 , the first and second data unit identifiers DUID1 and DUID2 included in the second sub data list SDL2 are the first and second data unit identifiers DUID1 of the first main data list MDL1 . , DUID2).

Subsequently, the sharing control unit 222 of the first IOT terminal 110 may selectively acquire the corresponding data unit from the second IOT terminal 120 . In embodiments, the version information VI1 ′, VI2 ′ of the second IOT terminal 120 corresponding to the first and second data unit identifiers DUID1 and DUID2 is the corresponding version of the first IOT terminal 110 . It may be compared with the information VI1 and VI2. The first and second version information VI1 ′ and VI2 ′ stored in the second IOT terminal 120 may be higher than the first and second version information VI1 , VI2 stored in the first IOT terminal 110 . have. In this case, the sharing control unit 222 of the first IOT terminal 110 may acquire the first and second data units DU1 ′ and DU2 ′ from the second IOT terminal 120 . In embodiments, the sharing control unit 222 of the first IOT terminal 110 may transmit a request corresponding to the first and second data unit identifiers DUID1 and DUID2 to the second IOT terminal 120 , The second IOT terminal 120 may transmit the first and second data units DU1' and DU2' corresponding to the request to the first IOT terminal 110 . The second IOT terminal 120 may further transmit the first and second version information VI1' and VI2' to the first IOT terminal 110 in response to the request. In addition, the sharing control unit 222 of the first IOT terminal 110 may update the first and second data units DU1 ′ and DU2 ′ to the main storage 230 through the storage access unit 223 . . For example, the first and second data units DU1 and DU2 stored in the main storage 230 are updated to the first and second data units DU1' and DU2' as shown in FIG. 5 . and/or may be substituted. In addition, the first and second version information VI1 and VI2 stored in the main storage 230 are updated and/or updated to the first and second version information VI1' and VI2' as shown in FIG. 5 . or may be substituted.

In embodiments, the sharing control unit 222 of the first IOT terminal 110 may control the first and second data units DU1' and DU2' in various ways, for example, according to the method described with reference to FIG. 10 . , and when the verification is passed, the first and second data units DU1 ′ and DU2 ′ and the first and second version information VI1 ′ and VI2 ′ are stored in the main storage 230 . can be updated. When a verification fails, that data may be dropped and/or discarded.

In addition, the sharing control unit 222 of the first IOT terminal 110 refers to the second main data list (MDL2) and the second sub data list (SDL2), but is not associated with the first client device 115, but the first It may be detected whether a new data unit that does not exist in the IOT terminal 110 exists in the second IOT terminal 120 . In this case, identifiers other than the identifiers of the first main data list MDL1 among the second main and sub data lists MDL2 and SDL2 and their version information are included in the first sub data list SDL1 and the first sub metadata. (SMT1) can be performed by comparing. In FIG. 4 , the fifth and sixth data unit identifiers DUID5 and UDID6 are not included in the first sub data list SDL1 . This means that the fifth and sixth data units DU5 and DU6 corresponding to the fifth and sixth data unit identifiers DUID5 and UDID6 are new data units that do not exist in the first IOT terminal 110 . can do.

The sharing control unit 222 of the first IOT terminal 110 may acquire the corresponding data units from the second IOT terminal 120 . The sharing control unit 222 of the first IOT terminal 110 may transmit a request corresponding to the fifth and sixth data unit identifiers DUID5 and UDID6 to the second IOT terminal 120, and the second IOT terminal ( 120 may transmit the fifth and sixth data units DU5 and DU6 to the first IOT terminal 110 in response to the request. The second IOT terminal 120 may further transmit the fifth and sixth version information VI5 and VI6 in response to the request. As shown in FIG. 5 , the sharing control unit 222 of the first IOT terminal 110 includes the fifth and sixth data units DU5 and DU6, the fifth and sixth data unit identifiers DUID5 and DUID6, In addition, the fifth and sixth version information VI5 and VI6 may be stored in the sub storage 240 .

Similarly, the sharing control unit 222 of the second IOT terminal 120 refers to the first main data list MDL1 and the first sub data list SDL1 received from the first IOT terminal 110, and the second client It may be detected whether a data unit associated with the device 125 exists in the first IOT terminal 110 , and the sensed data unit may be selectively obtained from the first IOT terminal 110 . In FIG. 5 , identifiers DUID5 and DUID6 of the second main data list MDL2 do not exist in the first main and sub data lists MDL1 and SDL1 . Accordingly, the main storage 230 of the second IOT terminal 120 may not be updated.

The sharing control unit 222 of the second IOT terminal 120 refers to the first main and sub data lists MDL1 and SDL1 , but is not associated with the second client device 125 , but in the second IOT terminal 120 . It may be detected whether a new data unit that does not exist exists in the first IOT terminal 110 , and the detected data units may be acquired from the first IOT terminal 110 . In FIG. 5 , the third and fourth data unit identifiers DUID3 and DUID4 are not included in the second sub data list SDL2 . Accordingly, the third and fourth data units DU3 and DU4, the third and fourth data unit identifiers DUID3 and DUID4, and the third and fourth version information VI3 and VI4 are the second IOT It may be stored in the sub storage 240 of the terminal 120 . In FIG. 5 , the first and second data unit identifiers DUID1 and DUID2 of the first main data list MDL1 are included in the second sub data list SDL2 . In this case, the corresponding version information may be additionally referenced. When the first and second version information VI1 ′ and VI2 ′ of the second IOT terminal 120 are higher than the first and second version information VI1 , VI2 of the first IOT terminal 110 , the first 2 Corresponding data units DU1' and DU2' of the IOT terminal 120 may not be updated as shown in FIG. 5 . If the first and second version information VI1' and VI2' of the second IOT terminal 120 are lower than the first and second version information VI1, VI2 of the first IOT terminal 110, The corresponding data units DU1 ′ and DU2 ′ of the second IOT terminal 120 may be updated with data units obtained from the first IOT terminal 110 .

6 is a flowchart illustrating a method of receiving data units from an external IOT terminal and storing them in main and sub storages according to an embodiment of the present invention. For convenience of description, it is assumed that the first IOT terminal 110 of FIG. 1 is adjacent to the second IOT terminal 120 and performs the steps of FIG. 6 . At this time, although not described with reference to FIG. 6 , the second IOT terminal 120 may also perform the steps of FIG. 6 similarly.

1 and 6 , in step S110 , the first IOT terminal 110 establishes short-range wireless communication with the adjacent second IOT terminal 120 .

In step S120 , the first IOT terminal 110 interacts with the second IOT terminal 120 to determine whether a data unit associated with the first client device 115 exists in the second IOT terminal 120 . The first IOT terminal 110 receives the list of data units from the second IOT terminal 120 , and the data unit associated with the first client device 115 in the second IOT terminal 120 based on the received list existence can be determined.

In step S130 , the first IOT terminal 110 selectively acquires the determined data unit from the second IOT terminal 120 and stores or updates it in the main storage 230 (refer to FIG. 2 ). In embodiments, the first IOT terminal 110 receives the data unit from the second IOT terminal 120 when the version of the data unit of the second IOT terminal 120 is higher than that of the first IOT terminal 110 . can be obtained

In step S140 , the first IOT terminal 110 acquires another part of the data units stored in the second IOT terminal 120 and stores it in the sub storage 240 separated from the main storage 230 . The first IOT terminal 110 determines whether a new data unit that is not associated with the first client device 115 but does not exist in the first IOT terminal 110 exists in the second IOT terminal 120 , and returns the determined data unit. It may be obtained from the second IOT terminal 120 and stored in the sub storage 240 . The first IOT terminal 110, based on the list of data units received from the second IOT terminal 120, a new data unit not associated with the first client device 115 but not in the first IOT terminal 110 It may be determined whether it exists in the second IOT terminal 120 .

In step S150 , the first IOT terminal 110 updates the first client device 115 using the data unit updated in the main storage 230 . The first IOT terminal 110 may provide the data unit to the first client device 115 and use it to command the first client device 115 to update the function module (FM, see FIG. 2 ).

7 is a flowchart illustrating a method of providing data units to an external IOT terminal. For convenience of description, it is assumed that the first IOT terminal 110 performs the steps of FIG. 7 adjacent to the second IOT terminal 120 . At this time, although not described with reference to FIG. 7 , the second IOT terminal 120 may also perform the steps of FIG. 7 similarly.

1 and 7, in step S210, after short-range wireless communication is established between the first IOT terminal 110 and the second IOT terminal 120 as described with reference to step S110 of FIG. 6, The first IOT terminal 110 provides a list of data units stored in the main and sub storages 230 and 240 (see FIG. 2 ) to the second IOT terminal 120 .

In step S220 , the first IOT terminal 110 may receive a request for at least one of the data units of the provided list from the second IOT terminal 120 . The second IOT terminal 120 selects at least one of the data units from the provided list, similar to the operations of the first IOT terminal 110 in steps S120 to S140 of FIG. 6 , and sets the selected data unit to the first IOT A request may be made to the terminal 110 .

In step S230 , the first IOT terminal 110 transmits the requested data unit to the second IOT terminal 120 .

In this way, both IOT terminals that have established short-range wireless communication adjacent to each other can exchange data units with each other.

8 is a flowchart illustrating an embodiment of a method of receiving data units from an external IOT terminal and storing the data units in main and sub storages. FIG. 8 shows steps included in steps S120 to S140 of FIG. 6 in more detail.

1 and 8 , in step S310 , the first IOT terminal 110 transmits its main data list to the second IOT terminal 120 (hereinafter, the first main data list; see MDL1 in FIG. 4 ) and It is possible to provide its own sub data list (hereinafter, a first sub data list; see SDL1 of FIG. 4 ). In addition, in step S320, the first IOT terminal 110 from the second IOT terminal 120 to the main data list of the second IOT terminal 120 (hereinafter, the second main data list; see MDL2 in FIG. 4) and the sub A data list (hereinafter, a second sub data list; see SDL2 of FIG. 4 ) may be received.

In step S330, the first IOT terminal 110 determines whether the identifier of the first main data list is searched in the received second main and sub data lists. If so, this means that there is a data unit associated with the first client device 115 in the second IOT terminal 120 . In this case, step S340 is performed. If not, step S360 is performed.

Steps S310 to S330 may be included in step S120 of FIG. 6 .

In step S340 , the first IOT terminal 110 determines whether the second IOT terminal 120 has a higher version than itself in association with the searched identifier. If so, step S350 is performed. If not, step S360 is performed.

In step S350 , the first IOT terminal 110 acquires the data unit corresponding to the searched identifier from the external IOT terminal and updates it in the main storage 230 (refer to FIG. 2 ).

Steps S340 and S350 may be included in step S130 of FIG. 6 .

In FIG. 4 , each of the identifiers DUID1 and DUID2 of the first main data list MDL1 exists in the second sub data list SDL2 . When the first and second version information VI1 ′ and VI2 ′ of the second IOT terminal 120 are higher than the first and second version information VI1 , VI2 of the first IOT terminal 110 , the first 1 IOT terminal 110 receives the first and second data units DU1' and DU2' from the second IOT terminal 110, and updates them to the main storage 230 as shown in FIG. can do. In embodiments, the first and second data units DU1 ′ and DU2 ′ from the second IOT terminal 110 are the first and second data units DU1 and DU2 stored in the main storage 230 . ) can be substituted. Version information VI1' and VI2' of the first and second data units DU1' and DU2' are further received from the second IOT terminal 120, and as shown in FIG. The two data units DU1 ′ and DU2 ′ may be updated in the main storage 230 .

In step S360, the first IOT terminal 110 may select at least some of the identifiers that do not match the identifier of the first main data list among the second main and sub data lists.

In step S370 , the first IOT terminal 110 may receive the data unit of the selected identifier from the second IOT terminal 120 and store it in the sub storage 240 (refer to FIG. 2 ).

Steps S360 and S370 may be included in step S140 of FIG. 6 .

In FIG. 4 , the fifth and sixth data unit identifiers DUID5 and DUID6 among the identifiers DUID1 , DUID2 , DUID5 , and DUID6 of the second main and sub data lists MDL2 and SDL2 are the first main data list Does not match any identifier in (MDL1). In addition, the fifth and sixth data unit identifiers DUID5 and DUID6 do not exist in the first sub data list MDL2. In this case, the first IOT terminal 110 obtains the fifth and sixth data units DU5 and DU6 and the fifth and sixth version information VI5 and VI6 from the second IOT terminal 120 and , may store them in the sub storage 240 as shown in FIG. 5 .

9 is a diagram conceptually illustrating another embodiment of data stored in the main storage and the sub storage of FIG. 2 .

2 and 9 , the main storage 230 and the sub storage 240 may further store an authenticator corresponding to each data unit. In FIG. 9 , the main storage 230 further stores first and second authenticators ATN1 and ATN2 corresponding to the first and second data units DU1 and DU2, respectively, and the sub storage 240 . may further store third and fourth authenticators ATN3 and ATN4 corresponding to the third and fourth data units DU3 and DU4, respectively. In this case, each authenticator may be data generated using an encryption code such as a private key.

Furthermore, the main storage 230 may additionally store a verification key corresponding to each data unit. 9 , the main storage 230 may store first and second verification keys VK1 and VK2 corresponding to the first and second data units DU1 and DU2, respectively. In this case, each verification key may be data generated using an arbitrary code such as a public key corresponding to a private key, and may be used to verify a corresponding authenticator.

10 is a flowchart illustrating an embodiment of step S340 of FIG. 8 .

1 and 10, in step S410, the first IOT terminal 110 is associated with the searched identifier as described with reference to step S340 of FIG. 8, and the second IOT terminal 120 is more Determine if you have a higher version. If so, step S420 is performed. If not, step S360 of FIG. 8 is performed.

In step S420 , the first IOT terminal 110 may verify the authenticator of the second IOT terminal 120 corresponding to the searched identifier using the corresponding verification key. In step S430, the first IOT terminal 110 performs step S350 or step S360 of FIG. 8 according to whether the verification using the verification key is passed.

In embodiments, the authenticator may be received together with the second main and sub data lists in step S320 of FIG. 8 . In other embodiments, the first IOT terminal 110 may additionally request an authenticator from the second IOT terminal 120 .

For example, when the authenticator ATN (refer to FIG. 9) corresponding to the first data unit DU1' of FIG. 4 is received, the first IOT terminal 110 transmits the first verification key VK1, see FIG. 9 ) can be used to verify the authenticator (ATN). In embodiments, the verification may be passed when the received authenticator ATN matches the first verification key VK1. In other embodiments, an operation such as, for example, a hash function is performed using the first verification key (VK1) or the authenticator (ATN), and the result of the operation is returned to the authenticator (ATN) or the first verification key ( By comparing with VK1), it can be determined whether the verification passes or not.

11 is a block diagram illustrating a computer device capable of implementing the IOT terminal of FIG. 2 .

Referring to FIG. 11 , the computer device 500 may include a communicator 510 , a first nonvolatile memory 520 , a second nonvolatile memory 530 , a processor 540 , and a system memory 550 . have.

The computer device 500 is configured to establish short-range wireless communication with an adjacent external IOT terminal through the communicator 510 , and transmit and receive wireless signals through short-range wireless communication in response to the control of the processor 540 . In embodiments, the communicator 510 may perform at least one of various types of short-range wireless communication such as Bluetooth communication, Wi-Fi communication, LTE D2D communication, RFID communication, magnetic secure transmission communication, Zigbee communication, and infrared communication. The communicator 510 may be provided as the communicator 210 of FIG. 2 .

Each of the first and second nonvolatile memories 520 and 530 may be at least one of various types of storage media capable of retaining data even when power is cut off, such as a hard disk drive, a solid state drive, and a flash memory. The first and second nonvolatile memories 520 and 530 may be provided as the main storage 230 and the sub storage 240 of FIG. 2 , respectively.

The processor 500 may include either a general purpose or a dedicated processor, and controls operations of the communicator 510 , the first and second nonvolatile memories 520 and 530 , and the system memory 550 .

The processor 500 loads program codes and/or instructions that provide various functions when executed from the first nonvolatile memory 520 into the system memory 550 and executes the loaded program codes and/or instructions. is composed For example, the system memory 550 may be provided as a working memory of the processor 500 . The processor 500 may further include an additional working memory.

The processor 500 is a data sharing module 551 that, when executed by the processor 500, performs the operations of the data sharer 220 or IOT terminal described with reference to FIGS. 2, 6 to 8, and 10 in the system. The memory 550 may be loaded and the loaded data sharing module 551 may be executed. The data sharing module 551 may be provided from a computer-readable storage medium, for example, through the communicator 510 , and installed in the computer device 500 . The processor 500 is a data sharing module 551 with components such as the communicator 510 and the first and second nonvolatile memories 520 and 530 of the computer device 500 when executed by the processor 500 . An operating system 552 providing an interface therebetween may be loaded into the system memory 550 and the loaded operating system 552 may be executed. The operating system 552 may control overall operations of the computer device 500 .

In embodiments, the system memory 550 may include at least one of a random access memory (RAM), a read only memory (ROM), and other types of computer-readable media.

Although specific embodiments and application examples have been described herein, these are only provided to help a more general understanding of the present invention, and the present invention is not limited to the above embodiments, and those of ordinary skill in the art to which the present invention pertains Various modifications and variations are possible from this substrate as it grows.

Therefore, the spirit of the present invention should not be limited to the described embodiments, and not only the claims to be described later, but also all those with equivalent or equivalent modifications to the claims will be said to belong to the scope of the spirit of the present invention. .

105: beacon terminal
110 to 130: first to third IOT terminals
115 to 135: first to third client devices
210: communicator
220: data sharer
230: main storage
240: sub storage

Claims (14)

A wireless communication terminal for controlling a client device, comprising:
a communicator configured to perform short-range wireless communication;
first storage;
a second storage separate from the first storage; and
a processor configured to control the first and second storages and the communicator;
The processor is
establishing the short-range wireless communication with a first external terminal through the communicator;
Interact with the first external terminal through the short-range wireless communication to detect the presence of a first data unit associated with the client device and second data units not associated with the client device among data units stored in the first external terminal do;
selectively acquiring the first data unit from the first external terminal and storing it in the first storage;
obtaining the second data units from the first external terminal and storing them in the second storage;
update the client device using the first data unit stored in the first storage;
and provide at least some of the second data units from the second storage to the second external terminal in response to a request from the second external terminal. The method of claim 1,
The processor is
establishing the short-range wireless communication with the second external terminal through the communicator;
and provide at least one list representing the first data unit in the first storage and the second data units in the second storage to the second external terminal. delete The method of claim 1,
The processor is
receive the list of data units from the first external terminal through the short-range wireless communication;
and detect the presence of the first data unit and the second data unit among the data units according to the list. 5. The method of claim 4,
the first storage is configured to store an identifier;
and the processor is configured to detect the presence of the first one of the data units by comparing the identifier to the list. The method of claim 1,
the first storage is configured to store first metadata indicative of a version associated with the client device;
The processor is
receive second metadata indicating a version of the first data unit from the first external terminal through the short-range wireless communication;
compare the second metadata with the first metadata;
and obtain the first data unit from the first external terminal based on a result of the comparison. 7. The method of claim 6,
the first storage is configured to further store a verification key associated with the client device;
The processor is
further receiving authentication data corresponding to the first data unit from the first external terminal through the short-range wireless communication;
verify the authentication data using the verification key;
and obtain the first data unit from the first external terminal, further based on whether the verification passes. The method of claim 1,
The processor is
establish the short-range wireless communication with the client device through the communicator;
and provide the first data unit to the client device via the short-range wireless communication to update the client device. A method for controlling a client device, comprising:
establishing short-range wireless communication with a first external terminal;
Interact with the first external terminal through the short-range wireless communication to detect the presence of a first data unit associated with the client device and second data units not associated with the client device among data units stored in the first external terminal to do;
selectively acquiring the first data unit from the first external terminal and storing the first data unit in a first storage;
obtaining the second data units from the first external terminal and storing them in a second storage separate from the first storage;
updating the client device using the first data unit stored in the first storage; and
and providing at least some of the second data units from the second storage to the second external terminal in response to a request from the second external terminal. 10. The method of claim 9,
establishing the short-range wireless communication with the second external terminal; and
The method further comprising the step of providing at least one list representing the first data unit of the first storage and the second data units of the second storage to the second external terminal. delete 10. The method of claim 9,
Detecting the presence of the first data unit and the second data unit comprises:
receiving the list of data units from the first external terminal through the short-range wireless communication; and
detecting the presence of the first data unit and the second data units among the data units according to the list. 10. The method of claim 9,
Receiving first metadata indicating a version of the first data unit from the first external terminal through the short-range wireless communication,
the first storage is configured to store second metadata indicative of a version associated with the client device;
The step of storing in the first storage comprises:
comparing the first metadata with the second metadata; and
and obtaining the first data unit from the first external terminal based on a result of the comparison. 14. The method of claim 13,
Receiving authentication data corresponding to the first data unit from the first external terminal through the short-range wireless communication,
the first storage is configured to further store a verification key associated with the client device;
Obtaining the first data unit comprises:
verifying the authentication data using the verification key; and
and obtaining the first data unit from the first external terminal further based on whether the verification has passed.

Images