KR20200069520A - Electronic device and control method thereof - Google Patents

Abstract

An electronic device is disclosed. According to the present invention, the electronic device comprises: a communication unit; and a processor configured to access a first multicast address through the communication unit, receive data transmitted from an external server through the first multicast address, generate a second multicast address different from the first multicast address if it is identified that an error has occurred in the data reception based on the received data, transmit the generated second multicast address and information on the data in which the error has occurred to the external server and an external device through the first multicast address, access the second multicast address through the communication unit, and receive the data in which the error has occurred through the second multicast address from at least one of the external server and the external device.

Description

Electronic device and control method thereof

The present disclosure relates to an electronic device for receiving or retransmitting data and a control method thereof, and more particularly, to an electronic device for receiving or retransmitting data through a multicast method and a control method thereof.

A large number of machinery and equipment exist in a factory, and an edge device is introduced to control/monitor the machinery and equipment for each process. To deliver the same data to a large number of machines, the central server can send data to the edge devices and the edge devices can send the data to each machine. For example, the central server may transmit an application or process control message to the edge device, and the edge device may transmit the transmitted application or process control message to each machine.

However, when a data transmission problem occurs in one edge device, a number of mechanical processes connected to the edge device may be stopped, so a solution is needed to solve the data transmission problem of the edge device where the problem occurs.

The present disclosure is in accordance with the above-described need, and an object of the present disclosure is to recover an apparatus in which a data transmission error occurs by re-receiving data or recovering the data by transmitting data to a device in which a data transmission error occurs. And to provide a control method therefor.

An electronic device according to an embodiment of the present disclosure for achieving the above object, accesses a first multicast address through a communication unit and the communication unit, and receives data transmitted from an external server through the first multicast address Then, based on the received data, when it is identified that an error has occurred in data reception, a second multicast address different from the first multicast address is generated, and the generated second multicast address and the error are generated. The information on the data is transmitted to the external server and the external device through the first multicast address, and the second multicast address is accessed through the communication unit to access the second multicast address from the external server or at least one of the external devices. 2 It may include a processor for receiving the error-generated data through a multicast address.

The processor receives data transmitted in chunk units from the external server and, based on the received data, identifies information about the chunk data identified as having an error through the first multicast address. It can be transmitted to the external server and the external device.

The processor may identify chunk data that has failed to receive based on a checksum included in each chunk data.

The processor identifies the number of retransmission requests through the second multicast address based on the total number of chunk data and the number of chunk data in which the error occurred, and the chunk data in which an error occurred during the identified number of retransmission requests If reception is unsuccessful, a transmission control protocol (TCP) connection may be requested from at least one of the external server or the external device, and the chunk data having the error may be re-received through the TCP connection.

Here, the number of retransmission requests may be a value obtained by dividing the total number of chunk data by the number of chunk data in which the error occurred.

The processor may multicast, to the external server and the external device, identification information of data in which an error has not occurred among data transmitted from the external server through the first multicast address.

The processor, when the identification information of the data in which the error has not occurred through the first multicast address from the external device, a transmission request for the data, and a third multicast address are received, the data in which the error has not occurred Can be multicast to the external device and the external server through the third multicast address.

An electronic system according to an embodiment of the present disclosure receives a server that multicasts data to a first device and a second device through a first multicast address, and receives data transmitted from the server through a first multicast address. When a data reception is identified as an error based on the received data, a second multicast address different from the first multicast address is generated, and the generated second multicast address and the error-generated data are generated. It may include a first device for transmitting information about the first multicast address to the server and the second device through the first multicast address and a second device to receive data transmitted from the server.

Here, the server or the second device may multicast the error-generated data to the first device through the second multicast address.

The second device receives data transmitted in units of chunks from the server and, based on the received data, identification information for chunk data identified as having an error occurs through the first multicast address. And to the first device.

The second device may identify chunk data that has failed to receive based on a checksum included in each chunk data.

The electronic system accesses the second multicast address when it is identified that an error has occurred in the reception of the same data as the data in which the error occurred in the first device, and from the server or at least one of the second devices The third device may further include a third device that receives the error-generated data through a second multicast address.

A control method of an electronic device according to an embodiment of the present disclosure includes accessing a first multicast address and receiving data transmitted from an external server through the first multicast address, based on the received data When it is identified that an error has occurred in receiving data, a second multicast address different from the first multicast address is generated, and the generated second multicast address and information on the data in which the error occurs are generated in the first multicast. Transmitting the data to the external server and the external device through a cast address, and accessing the second multicast address, and generating the error data through the second multicast address from at least one of the external server or the external device It may include the step of receiving.

In the transmitting step, data transmitted in chunk units from the external server is received, and identification information for chunk data identified as having an error based on the received data is transmitted to the first multicast address. Through the can be transmitted to the external server and the external device.

The transmitting may identify chunk data that has failed to receive based on a checksum included in each chunk-unit data.

The control method identifies the number of retransmission requests through the second multicast address based on the total number of chunk data and the number of chunk data in which the error occurred, and the chunk in which an error occurs during the identified number of retransmission requests If data reception is unsuccessful, requesting a Transmission Control Protocol (TCP) connection to at least one of the external server or the external device, and re-receiving the chunk data in which the error occurred through the TCP connection in a unicast manner. It may further include.

Here, the number of retransmission requests may be a value obtained by dividing the total number of chunk data by the number of chunk data in which the error occurred.

The control method may further include multicasting the identification information of the data in which no error occurs among the data transmitted from the external server to the external server and the external device through the first multicast address.

In the multicasting step, when the identification information of the data for which the error has not occurred, the request for transmission of the data, and the third multicast address are received from the external device through the first multicast address, the error occurs. The method may further include multicasting the unused data to the external device and the external server through the third multicast address.

As described above, according to various embodiments of the present disclosure, the data transmission time may be reduced and the load generated in the server may be reduced by re-receiving or re-transmitting the error-generated data through the multicast method.

Also, data may be transmitted to a plurality of electronic devices without error by re-receiving or re-transmitting data using a second multicast address different from the first multicast address.

1 is a diagram illustrating an electronic system according to an embodiment of the present disclosure.
2 is a block diagram illustrating an operation of an electronic device according to an embodiment of the present disclosure.
3 is a block diagram illustrating a detailed configuration of an electronic device.
4 is a view for explaining data re-reception and re-transmission through a first multicast address and a second multicast address according to an embodiment of the present disclosure.
5 is a sequence diagram illustrating a data transmission and retransmission request process according to an embodiment of the present disclosure.
6 is a diagram for describing an operation of retransmitting data by generating a retransmission list according to an embodiment of the present disclosure.
7 is a diagram for describing an operation of identifying chunk data that has failed to receive based on a checksum according to an embodiment of the present disclosure.
8 is a flowchart illustrating a method of controlling an electronic device according to an embodiment of the present disclosure.

Hereinafter, the present disclosure will be described in detail with reference to the accompanying drawings.

Terms used in this specification will be briefly described, and the present disclosure will be described in detail.

Terms used in the embodiments of the present disclosure, while considering the functions in the present disclosure, general terms that are currently widely used are selected, but this may vary depending on the intention or precedent of a person skilled in the art or the appearance of new technologies. . In addition, in certain cases, some terms are arbitrarily selected by the applicant, and in this case, the meaning will be described in detail in the description of the corresponding disclosure. Therefore, the terms used in the present disclosure should be defined based on the meaning of the terms and the contents of the present disclosure, not simply the names of the terms.

Embodiments of the present disclosure may apply various transformations and may have various embodiments, and specific embodiments are illustrated in the drawings and described in detail in the detailed description. However, this is not intended to limit the scope of the specific embodiments, it should be understood to include all transformations, equivalents, or substitutes included in the disclosed spirit and scope of technology. In the description of the embodiments, when it is determined that the detailed description of the related known technology may obscure the subject matter, the detailed description is omitted.

Singular expressions include plural expressions unless the context clearly indicates otherwise. In this application, terms such as “comprises” or “consist of” are intended to indicate that a feature, number, step, operation, component, part, or combination thereof described in the specification exists, one or more other It should be understood that features or numbers, steps, operations, components, parts or combinations thereof are not excluded in advance.

It should be understood that the expression “at least one of A and/or B” refers to either “A” or “B” or “A and B”.

As used herein, expressions such as "first," "second," "first," or "second," may modify various components, regardless of order and/or importance, and denote one component. It is used to distinguish from other components, but does not limit the components.

Some component (eg, first component) is "(functionally or communicatively) coupled with/to" another component (eg, second component), or " When referred to as "connected to", it should be understood that a component may be directly connected to another component, or may be connected through another component (eg, a third component).

In the present disclosure, "module" or "unit" performs at least one function or operation, and may be implemented in hardware or software, or a combination of hardware and software. In addition, a plurality of "modules" or a plurality of "parts" are integrated into at least one module except for "modules" or "parts" that need to be implemented with specific hardware to be implemented with at least one processor (not shown). Can be. In this specification, the term user may refer to a person using an electronic device or a device using an electronic device (eg, an artificial intelligence electronic device).

Hereinafter, exemplary embodiments of the present disclosure will be described in detail with reference to the accompanying drawings so that those skilled in the art to which the present disclosure pertains can easily implement them. However, the present disclosure may be implemented in various different forms and is not limited to the embodiments described herein. In addition, in order to clearly describe the present disclosure in the drawings, parts irrelevant to the description are omitted, and like reference numerals are assigned to similar parts throughout the specification.

Hereinafter, an embodiment of the present disclosure will be described in detail with reference to the accompanying drawings.

1 is a diagram illustrating an electronic system according to an embodiment of the present disclosure.

The electronic system 1000 includes an electronic device 100, another electronic device 200, and a server 300.

According to an embodiment of the present disclosure, the electronic device 100 is a device capable of transmitting and receiving data to and from the server 300, and may be implemented as an edge device. The other electronic device 200 may be another electronic device on the network to which the electronic device 100 is connected, that is, another edge device. The other electronic device 200 may be one, but may be a plurality (200-1, 200-2) as shown in FIG. 1. The server 300 is a component that transmits and receives data to and from the electronic device 100 and other electronic devices 200 on a network, and may transmit data through a router. The server 300 may be implemented as a central server in edge computing described later.

Here, the edge device refers to an apparatus for transmitting data transmitted from a central server on a network to a terminal device, and may also be referred to as a small server. A technique in which distributed edge devices transmit data to a terminal device is called edge computing. Edge computing is a system that contrasts with cloud computing, where a central server sends data directly to all terminal devices. For example, suppose that there are a large number of mechanical devices (terminal devices) performing the same function in a factory, and a control command is sent to all of these mechanical devices to perform a specific operation or the same application is installed. Sending commands or data to all machine units through an edge device is faster than the central server sending commands to all machine units directly or data containing application installation files. Or data can be transmitted.

Meanwhile, when an error occurs in data transmitted from the server 300 to the electronic device 100, the electronic device 100 must receive the corresponding data again. In addition, when a request for retransmission of data is received from another electronic device 200, the electronic device 100 may retransmit the corresponding data. Hereinafter, various embodiments of the present disclosure will be described in detail with reference to the drawings.

2 is a block diagram illustrating an operation of an electronic device according to an embodiment of the present disclosure.

According to FIG. 2, the electronic device 100 includes a communication unit 110 and a processor 120.

The communication unit 110 is a component capable of transmitting and receiving data with at least one external device 200 and the external server 300. Here, the external device 200 may be another electronic device on the network to which the electronic device 100 is connected, that is, another edge device.

For example, the communication unit 110 may transmit data to the external device 200 and the external server 300 according to a wireless communication method. In particular, a wireless fidelity (WI-FI) or Ethernet communication method may be used. . In addition, the communication unit 110 communicates with Zigbee, IR (Infrared), Serial Interface, USB (Universal Serial Bus), NFC (Near Field Communication), V2X (Vehicle to Everything), mobile communication (Cellular), BT (BlueTooth), etc. You can also use the method.

Also, the communication unit 110 may use a multicast method when data is transmitted to the external server 300 and at least one external device 200 under the control of the processor 120. However, the present invention is not limited thereto, and the communication unit 110 may unicast data to a specific device or broadcast to all devices under the control of the processor 120.

The processor 120 controls the overall operation of the electronic device 100.

According to an embodiment of the present disclosure, the processor 120 may be implemented as a digital signal processor (DSP), a microprocessor, or a time controller (TCON) that processes digital signals. It is not limited, and a central processing unit (CPU), a micro controller unit (MCU), a micro processing unit (MPU), a controller, an application processor (AP), or a communication processor ( communication processor (CP), one or more of the ARM processors, or may be defined in terms of the processor 120. In addition, the processor 120 is a SoC (System on Chip) with a built-in processing algorithm, large scale integration (LSI) ) Or in the form of a field programmable gate array (FPGA).The processor 120 performs various functions by executing computer executable instructions stored in a storage unit (not shown). can do.

According to an embodiment of the present disclosure, the processor 120 may access the first multicast address through the communication unit 110 and receive data transmitted from the external server 300 through the first multicast address. . Here, the electronic device 100, the external server 300 and the at least one external device 200 are connected to a specific multicast address as a group, so that the electronic device 100, the external server 300, and the external device ( If one of the 200) transmits specific data to the corresponding multicast address, the other device can receive the corresponding data. That is, according to an embodiment, the electronic device 100, the server 300, and the at least one external device 200 may transmit and receive data to each other through a multicast method. Since the processor 120 can transmit data to a plurality of devices in one transmission by using a multicast method as a data transmission method, the load of the processor 120 can be reduced. However, the present disclosure is not limited thereto, and the electronic device 100, the server 300, and the at least one external device 200 may transmit and receive data to and from each other through various communication methods such as unicast and broadcast.

Here, the multicast address may be an IP address used in the multicast method. A plurality of devices grouped in a corresponding multicast address, such as the electronic device 100, the external device 200, and the server 300, may be connected to the multicast address.

The processor 120 may generate a second multicast address different from the first multicast address when it is identified that an error occurs in data reception based on the received data. Here, the error of data reception may include a case in which the electronic device 100 has failed to receive data or has received data but has received data including an error.

The processor 120 receives data transmitted in chunk units from the external server 300, and receives a first multicast address for identifying information about the chunk data identified as having an error based on the received data. Through this, it can be transmitted to the external server 300 and the external device 200. That is, the processor 120 may identify an error of data reception in chunk units. Here, a chunk means a unit for classifying data. For example, 100 MB byte data may be divided into 100 chunks in 1 MB increments.

Further, the identification information may be number information for distinguishing a specific chunk data from other chunk data. For example, it is assumed that the data in which the error has occurred is the second chunk data. The processor 120 may identify that the error-generated data is the second chunk data based on the identification information of the error chunk data is “Chunk #2”. That is, the processor 120 can easily identify which chunk data an error has occurred through the identification information of the chunk data.

The identification information value of the chunk data may be set in the order of transmission. For example, the identification information of the first chunk data transmitted may be “Chunk #1”, and the identification information of the chunk data transmitted later may be “Chunk #2”. Accordingly, all chunk data may have different identification information.

The processor 120 may obtain the entire data by combining a plurality of chunk data based on the identification information of the received chunk data.

According to an embodiment, the processor 120 may identify chunk data that has failed to receive based on a checksum included in each chunk data. That is, the processor 120 may identify the chunk data in which an error occurs based on the chunk-based checksum. Here, the checksum is a sum used for the purpose of checking the accuracy of data, and is one of error detection methods, and a result value in which bytes of each chunk data are output through a hash function can be used as a checksum. Specifically, the processor 120 may receive specific chunk data, and compare a checksum included in the chunk data with bytes of the received chunk data to identify whether an error has occurred in the chunk data. The processor 120 may identify whether an error occurs in data reception based on the checksum, and may also identify identification information of the chunk data in which the error occurred. This will be described in detail in FIG. 7.

Since the processor 120 receives data classified in chunk units and requests retransmission of data in chunk units, the size of the retransmitted data may be relatively small. Accordingly, the load of the electronic device 100, the external device 200, and the server 300 may be relatively reduced compared to when the entire data is transmitted and received again.

Meanwhile, the processor 120 may make a retransmission request including retransmission time information to the external server 300 and at least one external device 200. Specifically, the processor 120 may request a retransmission by specifying a time point at which it is easy to receive the retransmitted data in consideration of the computation amount. Alternatively, if it is identified that an error has occurred in data reception, the processor 120 may request a retransmission at a time when it is easy to receive the retransmitted data without immediately requesting retransmission of the error data. If it is identified that an error has occurred in data reception, the 120 may generate a second multicast address. Here, the second multicast address is an address different from the first multicast address and is an address for re-receiving or re-transmitting the data in which an error has occurred. For example, if an error occurs in data reception while the first multicast address is 239.0.0.10, the processor 120 may generate a second multicast address different from the first multicast address as 239.0.0.20. . Here, it goes without saying that the specific multicast address is only an example.

Thereafter, the processor 120 may transmit information on the generated second multicast address and the error-generated data to the external server 300 and the external device 200 through the first multicast address. That is, the processor 120 may request the external server 300 and the at least one external device 200 to retransmit the error-generated data. The processor 120 may perform a request for retransmission of the data in which an error has occurred through a broadcast method as well as a multicast method or a unicast method. Here, the information about the data in which the error occurred may include identification information of the data in which the error occurred.

The processor 120 does not request the retransmission of the error-generated data after the entire data is transmitted from the external server 300, but identifies the error of the data in chunk units and requests the retransmission, so the error is relatively quickly. Can receive the generated data again. However, the present invention is not limited thereto, and the processor 120 may request retransmission of the chunk data in which an error occurs after the entire data is transmitted from the external server 300.

Also, since the processor 120 identifies an error of data in chunk units and requests retransmission, data may be received from different devices for each chunk data in which an error occurs. For example, the first chunk data with an error may be received from the external server 300, and the second chunk data with an error may be received from the external device 200. An error from the electronic device 100 The external device 200 and the external server 300 that have received the request for retransmission of the generated data may identify whether retransmission of the corresponding data is possible.

Specifically, the external device 200 identifies whether or not the data having an error in the electronic device 100 is normally received by the external device 200, checks the amount of computation of the external device 200, and retransmits the corresponding data It is possible to identify whether it is possible. Here, the calculation amount may include CPU, RAM usage, and the like. In addition, the external server 300 may identify whether or not retransmission of the corresponding data is possible by checking the calculation amount. Here, since the external server 300 corresponds to the electronic device 100 and the source device that has transmitted data to the external device 200, is the external server 300 equipped with the data in which the error occurred in the electronic device 100? It is not necessary to identify whether it is separate.

At least one of the external device 200 or the external server 300 identified as retransmittable may access the second multicast address and retransmit the corresponding data through the second multicast address.

The processor 120 accesses the second multicast address through the communication unit 110 to receive the error-generated data through the second multicast address from at least one of the external server 300 or the external device 200. Can be.

According to an embodiment, when a plurality of devices are identified as being capable of retransmission, the processor 120 may select one of the devices identified as being capable of retransmission and retransmit the data having an error from the selected device. have. For example, it is assumed that an error occurs in the reception of the first chunk data and both the external device 200 and the external server 300 are identified as being capable of retransmission. In this case, the processor 120 may select one device based on a preset condition and retransmit the first chunk data from the selected device. Here, the preset condition may include at least one of an intensity (RSSI) of a communication signal with the electronic device 100, a calculation amount, or whether the electronic device 100 satisfies a request time for retransmission. For example, the electronic device 100 satisfies a retransmission time of the device having a relatively large signal strength (RSSI) with the electronic device 100, a device having a relatively large amount of computation, or the electronic device 100 It is possible to select at least one of the devices capable of retransmission and retransmit the data having an error from the selected device.

According to another embodiment, the processor 120 may equally retransmit the error-generated data from a device identified as being capable of retransmission. For example, it is assumed that an error occurs in the reception of the first chunk data and both the external device 200 and the external server 300 are identified as being capable of retransmission. In this case, the processor 120 may retransmit half of the first chunk data from the external device 200 and retransmit the other half from the external server 300.

Meanwhile, the external server 300 may transmit identification information of each external device 200 that is successfully received for each chunk data through the first multicast address. Accordingly, the processor 120 may identify identification information of the external device 200 having normal data of the data in which the error occurred.

Meanwhile, a device having an error in receiving the same chunk data as the electronic device 100 may access the second multicast address and re-receive data transmitted from at least one of the external server 300 or the external device 200. have. This will be described in detail in FIG. 4.

Meanwhile, the processor 120 may delete the second multicast address when the re-receiving of the chunk data in which an error occurs through the second multicast address is successful.

Meanwhile, according to an embodiment of the present disclosure, the processor 120 may identify the number of retransmission requests through the second multicast address based on the total number of chunk data and the number of chunk data in which an error occurs. The processor 120 may identify the total number of chunk data based on the data header received from the external server 300. For example, if the electronic device 100 does not normally receive data even though it has repeatedly requested the retransmission of the errored chunk data several times, in order to prevent unnecessary delay, the errored chunk data is transmitted through another method. You need to receive it again. Therefore, the processor 120 may limit the number of retransmission requests through the multicast method.

Specifically, the number of retransmission requests may be a value obtained by dividing the total number of chunk data by the number of chunk data in which an error occurs. For example, it is assumed that an error occurs in 5 chunk data out of a total of 100 chunk data. The total number of chunk data (100) divided by the number of errored chunk data (5) is 20. That is, the processor 120 may transmit a request for retransmission of chunk data having an error for 20 times to the external device 200 and the external server 300 through a multicast method.

The processor 120 requests transmission of a Transmission Control Protocol (TCP) connection to at least one of the external server 300 or the external device 200 when the reception of the chunk data in which an error occurs during the identified number of retransmission requests fails, and the TCP Through the connection, the chunk data in which an error has occurred can be received again in a unicast manner.

For example, assuming that an error occurs in 5 chunk data out of 100 chunk data in total, as described above, the number of retransmission requests is 20 times. That is, the processor 120 transmits a request for re-transmitting the chunk data having an error for 20 times to the external device 200 and the external server 300 through a multicast method based on a User Datagram Protocol (UDP) connection, Nevertheless, if the reception of the errored chunk data fails, it is possible to receive the errored chunk data through the TCP connection with the external server 300 without performing the 21st retransmission request through the multicast method.

The method of receiving data through the TCP connection has a higher probability of receiving data than the method of receiving data through the multicast method based on the UDP connection, but since the load may be generated on the external server 300, the processor 120 retransmits During the number of requests, it is possible to request a retransmission of an errored chunk data through a multicast method, and nevertheless, if data reception fails, a TCP connection may be attempted to prevent unnecessary delay.

Meanwhile, an embodiment in which the electronic device 100 requests retransmission of the data in which an error occurs and re-receives the data has been described above. Hereinafter, the electronic device 100 retransmits data to the external device 200. The embodiments will be described.

According to an embodiment of the present disclosure, the processor 120 may transmit a response of successful reception of data to the external server 300 and the external device 200. The processor 120 may transmit a response of successful reception of data in chunk units.

Specifically, the processor 120 may multicast the identification information of the data in which no error occurs among the data transmitted from the external server 300 to the external server 300 and the external device 200 through the first multicast address. Can be. Meanwhile, the external device 200 that has successfully received the same data may not transmit a separate data reception success response. For example, it is assumed that the first device and the second device have successfully received the first chunk data. After a certain time, when the first device transmits the first chunk data reception success response through the first multicast address, the second device may not separately transmit the first chunk data reception success response. If one device succeeds in receiving the first chunk data, the corresponding device can then transmit the first chunk data to the device that has failed to receive the first chunk data, so when the first data reception success response is transmitted, the other devices send a success response. There is no need. However, the present invention is not limited thereto, and all devices that successfully receive data may transmit a success response.

Thereafter, when the processor 120 receives identification information of data for which no error has occurred, a request for transmission of the corresponding data, and a third multicast address from the external device 200 through the first multicast address, an error is not generated. Unused data may be multicast to the external device 200 and the external server 300 through the third multicast address. Here, the data in which an error has not occurred is data in which the processor 120 has successfully received data, but an error has occurred in at least one external device 200 and may be chunk data. The third multicast address is an address generated by the external device 200 and is an address different from the first multicast address. The third multicast address may be the same as or different from the second multicast address.

For example, it is assumed that the processor 120 receives a specific data transmission request through the first multicast address from the external device 200. First, the processor 120 may identify whether the corresponding data is normally received by the electronic device 100. When the corresponding data is normally received, the processor 120 may identify whether data transmission is possible based on the calculation amount of the electronic device 100. For example, the processor 120 may identify a state in which data transmission is possible when the current computation amount is equal to or less than a preset threshold. Accordingly, the processor 120 may access the third multicast address and transmit the corresponding data to the external device 200 and the external server 300 through the third multicast address. However, when the external server 300 transmits the corresponding data to the external device 200 through the third multicast address before the electronic device 100, the processor 120 may not transmit the corresponding data.

Meanwhile, the above-described data may be Docker Image data, but is not limited thereto.

On the other hand, the electronic device 100 has been described above assuming a case of being implemented as an edge device, but of course, the electronic device 100 may be implemented as a terminal device.

The above-described embodiments of the present disclosure can be applied to a scenario in which a central server transmits control commands or data to an edge device. In addition, embodiments of the present disclosure are required to reliably transmit the same data to a plurality of devices, such as a scenario in which the same educational content is distributed to a plurality of electronic devices such as a tablet and a scenario in which firmware of a plurality of devices is updated. It can be applied to various scenarios.

3 is a block diagram illustrating a detailed configuration of an electronic device.

According to FIG. 3, the electronic device 100 includes a communication unit 110, a processor 120, and a storage unit 130. Part of the configuration shown in FIG. 3 that overlaps with the configuration shown in FIG. 2 will be omitted.

The communication unit 110 is a configuration capable of transmitting and receiving data to and from the external server 300 and the external device 200. The communication unit 110 may include a Wi-Fi module (not shown), an Ethernet module (not shown), a local area network (LAN) module, and a wireless communication module (not shown). Here, each communication module may be implemented in the form of at least one hardware chip. The wireless communication module includes Zigbee, 3G (3rd Generation), 3GPP (3rd Generation Partnership Project), LTE (Long Term Evolution), LTE-A (LTE Advanced), 4G (4th Generation), 5G in addition to the above-described communication methods It may include at least one communication chip that performs communication according to various wireless communication standards such as (5th Generation). However, this is only an example, and the communication unit 110 may use at least one communication module among various communication modules when communicating with the external device 200 or the external server 300.

The processor 120 controls overall operations of the electronic device 100 using various programs stored in the storage 130.

Specifically, the processor 120 includes a RAM 121, a ROM 122, a main CPU 123, first to n interfaces 124-1 to 124-n, and a bus 125.

The RAM 121, the ROM 122, the main CPU 123, and the first to n interfaces 124-1 to 124-n may be connected to each other through the bus 125.

The ROM 122 stores a set of instructions for booting the system. When the turn-on command is input and power is supplied, the main CPU 123 copies the O/S stored in the storage unit 130 to the RAM 121 according to the command stored in the ROM 122, and executes the O/S. Boot the system. When the booting is completed, the main CPU 123 copies various application programs stored in the storage unit 130 to the RAM 121 and executes the application programs copied to the RAM 121 to perform various operations.

The main CPU 123 accesses the storage unit 130 to boot using the O/S stored in the storage unit 130. Then, various operations are performed using various programs and content data stored in the storage unit 130.

The first to n interfaces 124-1 to 124-n are connected to various components described above. One of the interfaces may be a network interface connected to an external device through a network.

The storage unit 130 may store chunk data transmitted from at least one of the external server 300 or the external device 200.

The storage unit 130 is implemented as an internal memory such as a ROM (eg, electrically erasable programmable read-only memory (EEPROM)) or RAM included in the processor 120, or the processor 120 And a separate memory. In this case, the storage unit 130 may be implemented in the form of a memory embedded in the electronic device 100 according to a data storage purpose, or may be implemented in a form of a memory that is detachable to the electronic device 100. For example, data for driving the electronic device 100 is stored in a memory embedded in the electronic device 100, and data for an extension function of the electronic device 100 is detachable from the electronic device 100. Can be stored in memory as much as possible. Meanwhile, in the case of a memory embedded in the electronic device 100, volatile memory (for example, dynamic RAM (DRAM), static RAM (SRAM), or synchronous dynamic RAM (SDRAM)), non-volatile memory ( Examples: one time programmable ROM (OTPROM), programmable ROM (PROM), erasable and programmable ROM (EPROM), electrically erasable and programmable ROM (EEPROM), mask ROM, flash ROM, flash memory (e.g. NAND flash or NOR flash, etc.) ), a hard drive, or at least one of a solid state drive (SSD), and a memory card (for example, CF (compact flash), SD (SD), for removable memory in the electronic device 100) Secure digital (micro-SD), micro secure digital (Mini-SD), mini secure digital (SD), extreme digital (xD), multi-media card (MMC), etc., external memory that can be connected to a USB port (for example, USB memory).

In particular, the storage unit 130 may include multicast address information, identification information for chunk data identified as having an error, a checksum, and the like.

4 is a diagram illustrating data re-reception and re-transmission through a first multicast address and a second multicast address according to an embodiment of the present disclosure.

The server 300 transmits the first chunk data and the second chunk data to the first device 400-1, the second device 400-2, and the third device 400-3 through the first multicast address. It can be (S410). Here, since the server 300, the first device 400-1, the second device 400-2, and the third device 400-3 are connected to the first multicast address as a group, the server ( When the 300) multicasts the first chunk data and the second chunk data to the first multicast address as destination information, the first chunk data and the second chunk data include the first device 400-1 and the second device ( 400-2) and the third device 400-3.

Thereafter, the first device 400-1 normally receives the first chunk data and the second chunk data, and the second device 400-2 and the third device 400-3 normally receive the first chunk data. However, it is assumed that an error occurs in the reception of the second chunk data.

The second device 400-2 and the third device 400-3 identify that the data in which the error occurred is the second chunk data, and the second device 400-2 or the third device 400-3 is A second multicast address different from the first multicast address may be generated. In FIG. 4, it is assumed that the second device 400-2 has generated a second multicast address.

The second device 400-2 generates the second multicast address information and the Chunk #2 corresponding to the identification information of the second chunk data in which the error occurred through the first multicast address of the server 300 and the first. It may be transmitted to the device 400-1 and the third device 400-3 (S420).

Thereafter, the third device 400-3 may access the second multicast address generated and transmitted from the second device 400-2 in order to receive the second chunk data again (S430 ). The third device 400-3 does not generate a separate multicast address, and may access the multicast address generated by the second device 400-2 to receive the second chunk data again, thereby reducing the computation amount. have. In addition, the server 300 or the first device 400-1 does not need to separately transmit second chunk data to the third device 400-3.

In addition, the first device 400-2 and the server 300 may identify whether or not the second chunk data can be transmitted by checking their computation amount (S440 ). In FIG. 4, since the server 300 is transmitting the remaining chunk data other than the first and second chunk data, it is assumed that the second chunk data cannot be retransmitted in excess of a preset threshold calculation amount. Accordingly, the first device 400-1 may access the second multicast address and transmit the second chunk data through the second multicast address (S450 ).

Here, although the first device 400-1 is described as accessing the second multicast address after the third device 400-3 accesses the second multicast address, the first device 400-1 is After accessing the second multicast address, the third device 400-3 accesses the second multicast address, or the first device 400-1 and the third device 400-3 simultaneously access the second multicast address. Of course, you can also connect to.

Meanwhile, the server 300 may access all multicast addresses generated by a device connected to the server 300 as a central server.

5 is a sequence diagram illustrating a data transmission and retransmission request process according to an embodiment of the present disclosure.

The server 300 may transmit the first chunk data through the first multicast address 505-1 (S510). The first multicast address 505-1 may be, for example, an IP address of 239.0.0.10. Here, the server 300, the first device 500-1, the second device 500-2, and the third device 500-3 are connected to the IP address of 239.0.0.10 as one multicast group. Can be. Therefore, the server 300 sets the destination information to the first multicast address 505-1 to transmit the first chunk data, the first device 500-1, the second device 500-2 and the The first chunk data may be transmitted to the 3 devices 500-3.

The first device 500-1 which has successfully received the first chunk data may transmit the first chunk data transmission success notification through the first multicast address 505-1 (S520 ). Specifically, the first device 500-1 receives the normally received first chunk data identification information through the first multicast address 505-1 server 300, the second device 500-2, and It can multicast to 3 devices 500-3.

The second device 500-2 having an error in receiving the first chunk data and the third device 500-3 acquire identification information of the first chunk data in which the error has occurred, and the second device 500-2. ) Or the third device 500-3 may generate a second multicast address 505-2 different from the first multicast address 505-1.

5, the second device 500-2 may generate a second multicast address 505-2 (S530). Subsequently, the second device 500-2 stores the identification information of the second multicast address 505-2 generated through the first multicast address 505-1 and the first chunk data in which an error occurs ( 300), the first device 500-1 and the third device 500-3 may be transmitted (S540).

Thereafter, the third device 500-3 may access the second multicast address 505-2 to receive the first chunk data in which the error occurred (S550 ). Also, the first device 500-1 may access the second multicast address 505-2 to transmit the first chunk data (S560 ).

Thereafter, the first device 500-1 transmits the first chunk data to the server 300, the second device 500-2, and the third device 500-3 through the second multicast address 505-2. It may be transmitted (S570).

6 is a diagram for describing an operation of retransmitting data by generating a retransmission list according to an embodiment of the present disclosure.

The server 300 may generate information about the error-generated data from each of a plurality of electronic devices connected to the server 300 and generate a retransmission list 620.

Specifically, as shown in FIG. 6A, each of the electronic devices may generate a list 610 regarding the chunk data in which an error has occurred. In FIG. 6A, Chunk ID indicates identification information of chunk data, and the list 610 regarding chunk data may include Chunk ID information and error information corresponding to each Chunk ID. The chunk data list 610 of FIG. 6A is a list generated by the first device, and each of the plurality of electronic devices may generate a list of chunk data.

Thereafter, each of the plurality of electronic devices may transmit the list generated to the server 300 through the first multicast address.

The server 300 may generate a list 620 of retransmitted chunk data from a list of chunk data transmitted from a plurality of electronic devices. The retransmission chunk data list 620 may include device identification information (Device ID) and error data information generated in each device, that is, chunk information for which retransmission is required.

For example, the server 300 through the list 620 regarding the retransmission chunk data, the error chunk data generated in the first device is the second chunk data, and the error chunk data generated in the second device is the third and It can be identified that the 10th chunk data, no error is generated in the third device, and the error chunk data generated in the nth device are the fifth and ninth chunk data.

Thereafter, the server 300 may transmit the chunk data corresponding to the union of the error chunk data generated in the first to nth devices through a second multicast address different from the first multicast address.

For example, in FIG. 6B, the server 300 may retransmit the second, 3, 5, 9, and 10 chunk data to the first, second, and nth device in which an error occurs through the second multicast address. have. The first, second, and nth devices in which an error has occurred are connected to the second multicast address and thus can receive such retransmission data.

In FIG. 6, it is described that the server 300 re-transmits the chunk data at one time by summing up information on the chunk data in which an error occurs in each electronic device, but the server 300 re-creates the chunk data from each electronic device. If there is a transmission request, the chunk data may be retransmitted in real time without summing all the chunk data information.

In addition, it is needless to say that an electronic device other than the server 300 may transmit chunk data to another electronic device.

7 is a view for explaining an operation of identifying chunk data that has failed to receive based on a checksum according to an embodiment of the present disclosure.

Here, the checksum is a sum used for checking the accuracy of data, and is one of error detection methods.

The electronic device 100 may receive a specific chunk data and compare the checksum included in the chunk data with bytes of the received chunk data to identify whether an error has occurred in the chunk data. The electronic device 100 may identify whether an error occurs in data reception based on the checksum, or may identify identification information of the chunk data in which the error occurred.

According to FIG. 7, it is assumed that 100 MB of data is divided into 100 chunk data in 1 MB increments. The electronic device 100 may compare the sum of bytes up to the last chunk data and the checksum of the last chunk data to identify whether an error occurs in data reception. For example, when the sum of bytes in the state of receiving the 99th chunk data is less than 99000, the electronic device 100 may identify that an error has occurred in receiving at least one chunk data.

Also, the electronic device 100 may identify identification information of the chunk data in which an error occurs based on the checksum of each chunk data. Specifically, it is possible to identify the identification information of the chunk data in which an error occurs by comparing the sum of bytes in the state of receiving each chunk data and the checksum of the chunk data. For example, when a state in which an error occurs in data reception in a state in which the first chunk data is received is not identified, when the sum of bytes in the state in which the second chunk data is received is less than 2000, the electronic device 100 may display the second It can be identified that an error has occurred in receiving chunk data.

8 is a flowchart illustrating a method of controlling an electronic device according to an embodiment of the present disclosure.

The electronic device 100 may access the first multicast address and receive data transmitted from the external server 300 through the first multicast address (S810).

When it is identified that an error has occurred in data reception based on the received data, the electronic device 100 generates a second multicast address different from the first multicast address, and the generated second multicast address and error occurs Information about the data may be transmitted to the external server 300 and the external device 200 through the first multicast address (S820).

Specifically, the electronic device 100 receives data transmitted in chunk units from the external server 300, and first identifies identification information for the chunk data identified as having an error based on the received data. It can be transmitted to the external server 300 and the external device 200 through the multicast address.

The electronic device 100 may identify chunk data that has failed to be received based on a checksum included in each chunk data.

The electronic device 100 may access the second multicast address and receive data having an error through the second multicast address from at least one of the external server 300 or the external device 200 (S830). .

Meanwhile, the electronic device 100 identifies the number of retransmission requests through the second multicast address based on the total number of chunk data and the number of chunk data in which an error occurs, and the chunk in which an error occurs during the identified number of retransmission requests If the data reception fails, a request is made to a Transmission Control Protocol (TCP) connection to at least one of the external server 300 or the external device 200, and the chunk data having an error through the TCP connection is re-received in a unicast manner. Can be.

Here, the number of retransmission requests may be a value obtained by dividing the total number of chunk data by the number of chunk data in which an error occurs.

Meanwhile, the electronic device 100 multicasts the identification information of the data in which no error occurs among the data transmitted from the external server 300 to the external server 300 and the external device 200 through the first multicast address. Can be.

Thereafter, when the electronic device 100 receives identification information of data for which no error has occurred through the first multicast address from the external device 200, a transmission request for the corresponding data, and a third multicast address, an error occurs. Uncast data may be multicast to the external device 200 and the external server 300 through the third multicast address.

The detailed operation of each step has been described above, so a detailed description thereof will be omitted.

Meanwhile, the methods according to various embodiments of the present disclosure described above may be implemented in an application form that can be installed in an existing electronic device.

Further, the methods according to various embodiments of the present disclosure described above may be implemented only by software upgrade or hardware upgrade of an existing electronic device.

In addition, various embodiments of the present disclosure described above may be performed through an embedded server provided in an electronic device or an external server of at least one of an electronic device and a display device.

Meanwhile, according to a date and time example of the present disclosure, various embodiments described above may be implemented by software including instructions stored in a machine-readable storage media (machine). The device may include an electronic device according to the disclosed embodiments as a device capable of invoking a stored command from a storage medium and operable according to the called command. When the command is executed by the processor, the processor may directly Or, under the control of the processor, other components may be used to perform functions corresponding to the instructions, which may include code generated or executed by a compiler or interpreter. It may be provided in the form of a non-transitory storage medium, where'non-transitory' means that the storage medium does not contain a signal and is tangible, but the data is semi-permanent or Does not distinguish between temporary storage.

Further, according to an embodiment of the present disclosure, a method according to various embodiments described above may be provided as being included in a computer program product. Computer program products are commodities that can be traded between sellers and buyers. The computer program product may be distributed online in the form of a device-readable storage medium (eg compact disc read only memory (CD-ROM)) or through an application store (eg Play StoreTM). In the case of online distribution, at least a portion of the computer program product may be stored at least temporarily on a storage medium such as a memory of a manufacturer's server, an application store's server, or a relay server, or may be temporarily generated.

In addition, according to an embodiment of the present disclosure, various embodiments described above may be used in a recording medium readable by a computer or a similar device using software, hardware, or a combination thereof. Can be implemented in In some cases, the embodiments described herein may be implemented by the processor itself. According to the software implementation, embodiments such as procedures and functions described herein may be implemented as separate software modules. Each of the software modules can perform one or more functions and operations described herein.

Meanwhile, computer instructions for performing a processing operation of a device according to various embodiments described above may be stored in a non-transitory computer-readable medium. The computer instructions stored in the non-transitory computer readable medium allow a specific device to perform a processing operation in the device according to various embodiments described above when executed by a processor of the specific device.

The non-transitory computer-readable medium refers to a medium that stores data semi-permanently and that can be read by a device, rather than a medium that stores data for a short time, such as registers, caches, and memory. Specific examples of non-transitory computer-readable media may include CDs, DVDs, hard disks, Blu-ray disks, USBs, memory cards, and ROMs.

In addition, each of the components (for example, a module or a program) according to various embodiments described above may be composed of a singular or a plurality of entities, and some of the aforementioned sub-components may be omitted, or other sub-components may be omitted. Components may be further included in various embodiments. Alternatively or additionally, some components (eg, modules or programs) may be integrated into one entity, performing the same or similar functions performed by each corresponding component prior to integration. According to various embodiments, operations performed by a module, program, or other component may be sequentially, parallelly, repeatedly, or heuristically executed, at least some operations may be executed in a different order, omitted, or other operations may be added. Can be.

Although the preferred embodiments of the present disclosure have been illustrated and described above, the present disclosure is not limited to the specific embodiments described above, and it is usually in the technical field belonging to the present disclosure without departing from the gist of the present disclosure claimed in the claims. Of course, various modifications can be implemented by a person who has knowledge of, and these modifications should not be individually understood from the technical idea or prospect of the present disclosure.

100: electronic device 110: communication unit
120: processor 130: storage unit
200: external device 300: server
1000: electronic system

Claims (18)

Communication department; And
Access to a first multicast address through the communication unit, receive data transmitted from an external server through the first multicast address,
When it is identified that an error has occurred in data reception based on the received data, a second multicast address different from the first multicast address is generated, and the generated second multicast address and the error data are generated. Information to the external server and the external device through the first multicast address,
And a processor configured to access the second multicast address through the communication unit and receive the error-generated data from the external server or at least one of the external devices through the second multicast address. According to claim 1,
The processor,
Receiving data transmitted in chunk units from the external server, and based on the received data, identification information for the chunk data identified as having an error is generated through the first multicast address and the external server and An electronic device that transmits to an external device. According to claim 2,
The processor,
An electronic device that identifies chunk data that has failed to be received based on a checksum included in each chunk data. According to claim 2,
The processor,
If the number of re-transmission requests through the second multicast address is identified based on the total number of chunk data and the number of chunk data in which the error occurs, and the reception of the chunk data in which an error occurs during the identified number of re-transmission requests fails , Requesting a Transmission Control Protocol (TCP) connection to at least one of the external server or the external device, and re-receiving the chunk data in which the error occurred through the TCP connection in a unicast manner. The method of claim 4,
The number of retransmission requests,
An electronic device that is a value obtained by dividing the total number of chunk data by the number of chunk data in which the error occurs. According to claim 1,
The processor,
An electronic device for multicasting identification information of data for which no error has occurred among data transmitted from the external server to the external server and the external device through the first multicast address. The method of claim 6,
The processor,
When the identification information of the data in which the error has not occurred, the transmission request for the data, and the third multicast address are received from the external device through the first multicast address, the data in which the error has not occurred is transmitted to the third An electronic device that multicasts to the external device and the external server through a multicast address. A server that multicasts data to the first device and the second device through the first multicast address;
When receiving data transmitted from the server through a first multicast address, and when it is identified that an error occurs in data reception based on the received data, a second multicast address different from the first multicast address is generated and , A first device that transmits information about the generated second multicast address and the error-generated data to the server and the second device through the first multicast address; And
It includes; a second device for receiving the data transmitted from the server;
The server or the second device,
And multicast the data in which the error occurred through the second multicast address to the first device. The method of claim 8,
The second device,
Receiving data transmitted in chunk units from the server, and based on the received data, identification information for chunk data identified as having an error is transmitted to the server and the first device through the first multicast address. Transmitting, electronic system. The method of claim 9,
The second device,
An electronic system for identifying chunk data that has failed to receive based on a checksum included in each chunk data. The method of claim 8,
If it is identified that an error has occurred in the reception of the same data as the error-generated data in the first device, the second multicast address is accessed from at least one of the server or the second device by accessing the second multicast address. And a third device that receives the data through which the error has occurred. Accessing a first multicast address and receiving data transmitted from an external server through the first multicast address;
If it is identified that an error has occurred in data reception based on the received data, a second multicast address different from the first multicast address is generated, and the generated second multicast address and the error data are generated. Transmitting information on the external server and the external device through the first multicast address; And
And accessing the second multicast address to receive the error-generated data through the second multicast address from at least one of the external server or the external device. The method of claim 12,
The transmitting step,
Receiving data transmitted in chunk units from the external server, and based on the received data, identification information for the chunk data identified as having an error is generated through the first multicast address and the external server and Control method to transmit to an external device. The method of claim 13,
The transmitting step,
A control method for identifying chunk data that has failed to receive based on a checksum included in each chunk data. The method of claim 13,
If the number of re-transmission requests through the second multicast address is identified based on the total number of chunk data and the number of chunk data in which the error occurs, and the reception of the chunk data in which an error occurs during the identified number of re-transmission requests fails , Requesting a Transmission Control Protocol (TCP) connection to at least one of the external server or the external device, and re-receiving the chunk data in which the error occurred through the TCP connection in a unicast manner. Way. The method of claim 15,
The number of retransmission requests,
The control method is a value obtained by dividing the total number of chunk data by the number of chunk data in which the error occurred. The method of claim 12,
And multicasting the identification information of the data having no error among the data transmitted from the external server to the external server and the external device through the first multicast address. The method of claim 17,
The multicasting step,
When the identification information of the data in which the error has not occurred, the transmission request for the data, and the third multicast address are received from the external device through the first multicast address, the data in which the error has not occurred is transmitted to the third And multicasting to the external device and the external server through a multicast address.

Images