KR20150054643A - Method and apparatus for recovering error in RDM protocol - Google Patents

Method and apparatus for recovering error in RDM protocol Download PDF

Info

Publication number
KR20150054643A
KR20150054643A KR1020140101737A KR20140101737A KR20150054643A KR 20150054643 A KR20150054643 A KR 20150054643A KR 1020140101737 A KR1020140101737 A KR 1020140101737A KR 20140101737 A KR20140101737 A KR 20140101737A KR 20150054643 A KR20150054643 A KR 20150054643A
Authority
KR
South Korea
Prior art keywords
rdm
packet
response packet
transaction number
buffer
Prior art date
Application number
KR1020140101737A
Other languages
Korean (ko)
Inventor
임상규
김인수
강태규
장일순
Original Assignee
한국전자통신연구원
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 한국전자통신연구원 filed Critical 한국전자통신연구원
Priority to US14/530,976 priority Critical patent/US20150131428A1/en
Publication of KR20150054643A publication Critical patent/KR20150054643A/en

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1809—Selective-repeat protocols
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L1/00—Arrangements for detecting or preventing errors in the information received
    • H04L1/12—Arrangements for detecting or preventing errors in the information received by using return channel
    • H04L1/16—Arrangements for detecting or preventing errors in the information received by using return channel in which the return channel carries supervisory signals, e.g. repetition request signals
    • H04L1/18—Automatic repetition systems, e.g. Van Duuren systems
    • H04L1/1867—Arrangements specially adapted for the transmitter end
    • H04L1/1874—Buffer management

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Communication Control (AREA)

Abstract

Provided are a method and an apparatus for re-transmitting remote device management (RDM) packets lost in a RDM protocol for controlling various devices connected to a DMX512 network. The method is a method for recovering from an error in a remote controller for remotely controlling devices connected to a DMX512 network via a RDM protocol based on the DMX512 network. The method for recovering from an error in a RDM protocol comprises the steps of: storing RDM packets to be transmitted to a device in a buffer and transmitting the same to the device; waiting for a preset span of time to receive a response packet from the device; if the response packet is received within a preset span of time, checking the transaction number of the response packet to check the same against the sequence of a response packet that arrived previously; and re-transmitting a corresponding RDM packet according to the checking result against the sequence of the response packet that arrived previously.

Description

[0001] The present invention relates to a method and apparatus for recovering an error in an RDM protocol,

The present invention relates to an error recovery method and apparatus in an RDM protocol, and more particularly, to a method and apparatus for recovering an error or a loss of a control message transmitted from an RDM (Remote Device Management) protocol focused on transmission of a device control message transmitted through a DMX512 network To a method and apparatus capable of defining a retransmission mechanism for a mobile station.

In the prior art, the RDM (Remote Device Management) protocol transmits a control message (RDM packet) for controlling various devices including a lighting device connected to the DMX512 network or a dimmer controlling the brightness of illumination from the controller to each device do.

The controller generates an RDM packet to change the state of a specific or a plurality of devices and delivers the controller's command by transmitting the packet to the device.

After receiving the RDM packet, the devices determine whether the status change is possible. If possible, they send a related response message. If not, the devices respond with a NACK message. Reason codes Code.

However, in the conventional RDM protocol, there is no definition of a retransmission mechanism for coping with a loss or an error of the RDM packet transmitted. Therefore, an RDM packet that can not be processed due to an error occurs or is lost, is not recovered, and the status change or status information request of the device included in the RDM packet is not made.

Related prior arts are disclosed in Korean Patent Laid-Open Publication No. 2011-0061069 (LED lighting apparatus supporting DMX512 communication protocol) in which the entire lighting control system is simplified so as to facilitate installation and construction and contribute to cost reduction .

The invention disclosed in Korean Patent Laid-Open Publication No. 2011-0061069 is applied to illumination control in the DMX512 (ANSI E1.11) protocol environment and is applied to each LED connected to the DMX512 (ANSI E1.11) communication protocol master device LED) Each lighting apparatus extracts only the data corresponding to its own channel among the DMX512 data generated by the master device, and performs illumination control, so that DMX512 communication Protocol.

Other related prior art techniques are disclosed in U. S. Patent Application No. < RTI ID = 0.0 > 2012-0161642 < / RTI > (LIGHTING CONTROL METHOD AND DEVICE).

The invention described in the above-mentioned U.S. Patent Application Publication No. 2012-0161642 is merely a matter of verifying the illumination control data and displaying an error state corresponding thereto if there is an error. In the RDM protocol focused on the device control message transmission on the DMX512 network, There is no indication of a retransmission mechanism for an error or loss of a control message.

SUMMARY OF THE INVENTION It is an object of the present invention to provide a method and apparatus for retransmitting an RDM packet lost in an RDM (Remote Device Management) protocol based on a DMX512 network.

In order to achieve the above object, an error recovery method in an RDM protocol according to a preferred embodiment of the present invention is an error recovery method in a remote controller that remotely controls a device connected to a DMX512 network through an RDM protocol,

Storing an RDM packet to be transmitted to the device in a buffer and transmitting the RDM packet to the device; Waiting for a predetermined time to receive a response packet from the device; Receiving a response packet within the predetermined time period, checking a transaction number of the response packet and confirming a sequence with a previously arrived response packet; And retransmitting the corresponding RDM packet according to a result of the sequential check with the previously received response packet.

Preferably, the step of retransmitting the corresponding RDM packet is a step of retransmitting the RDM packet having the transaction number corresponding to the intermediate empty number in the buffer when it is determined that the sequence number is out of order and a sequential error occurs, can do.

Preferably, the RDM packet having the same transaction number as the transaction number of the response packet can be deleted if the sequential error does not occur as a result of the sequential check.

Meanwhile, an error recovery apparatus in the RDM protocol according to a preferred embodiment of the present invention includes: a buffer for storing an RDM packet to be transmitted; A transmitter for transmitting the RDM packet stored in the buffer to a device connected to the DMX512 network through an RDM protocol based on the DMX512 network; A timepiece that reveals time; A response packet receiving unit for receiving a response packet from the device; And storing the RDM packet to be transmitted in the buffer and transmitting the RDM packet to the device. When the response packet of the device is received within a predetermined time based on the timekeeping data of the timepiece, the transaction number of the response packet is checked And a control unit for confirming the sequence with the received response packet and retransmitting the RDM packet according to the result of the sequence check.

Preferably, the controller is able to retransmit the RDM packet having the transaction number corresponding to the empty number in the buffer when it is determined that the sequence number is out of order and the intermediate empty number occurs.

The controller may delete the RDM packet having the same transaction number as the transaction number of the response packet if the sequential error does not occur as a result of the sequential check.

According to the present invention, when the RDM packet transmitted by the RDM protocol is lost for controlling various devices connected to the DMX512 network, the reliability of the packet transmission is increased through the retransmission mechanism to provide efficient device control.

1 is a diagram illustrating a DMX512 network system to which the present invention is applied.
2 is an example of the internal configuration of the remote controller shown in Fig.
3 is a flowchart illustrating an error recovery method in the RDM protocol according to an embodiment of the present invention.

While the invention is susceptible to various modifications and alternative forms, specific embodiments thereof are shown by way of example in the drawings and will herein be described in detail.

It should be understood, however, that the invention is not intended to be limited to the particular embodiments, but includes all modifications, equivalents, and alternatives falling within the spirit and scope of the invention.

The terminology used in this application is used only to describe a specific embodiment and is not intended to limit the invention. The singular expressions include plural expressions unless the context clearly dictates otherwise. In the present application, the terms "comprises" or "having" and the like are used to specify that there is a feature, a number, a step, an operation, an element, a component or a combination thereof described in the specification, But do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, or combinations thereof.

Unless defined otherwise, all terms used herein, including technical or scientific terms, have the same meaning as commonly understood by one of ordinary skill in the art to which this invention belongs. Terms such as those defined in commonly used dictionaries should be interpreted as having a meaning consistent with the meaning in the context of the relevant art and are to be interpreted in an ideal or overly formal sense unless explicitly defined in the present application Do not.

Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. In order to facilitate the understanding of the present invention, the same reference numerals are used for the same constituent elements in the drawings and redundant explanations for the same constituent elements are omitted.

1 is a diagram illustrating a DMX512 network system to which the present invention is applied

The DMX512 network system includes a plurality of devices 30a through 30n, a remote controller 10, and a DMX512 network 40 connecting them.

Each of the devices 30a to 30n may have an identifier (ID) for distinguishing from other devices.

The remote controller 10 sends a device control message (RDM packet) to the devices 30a to 30n via the DMX512 network 40. [ Each of the devices 30a to 30n may be a dimmer that adjusts the brightness of a lighting device or a lighting device.

The DMX512 network 40 forwards the RDM packets from the remote controller 10 to the devices 30a-30n for control of the various devices connected to the DMX512 network.

2 is an example of the internal configuration of the remote controller shown in Fig. The remote controller 10 in FIG. 2 utilizes a transaction number in a packet existing for mapping a request message and a response message in an existing device control message (RDM packet).

2 includes a control message generator 12, a buffer 14, a transmitter 16, a clock 18, a response packet receiver 20, and a controller 22.

The control message generating unit 12 generates a device control message (i.e., an RDM packet) to be transmitted to each of the devices 30a to 30n.

The buffer 14 stores the device control message (RDM packet) generated by the control message generating unit 12 for each packet.

The transmitting unit 16 transmits a device control message (RDM packet) to be transmitted stored in the buffer 14 to the devices 30a to 30n via the DMX512 network 40. [ That is, the transmitting unit 16 may transmit the RDM packets stored in the buffer 14 to the corresponding devices 30a to 30n through the RDM protocol based on the DMX512 network.

Timepiece unit 18 reveals time. The timepiece unit 18 transmits the timing data to the control unit 22.

The response packet receiving unit 20 receives response packets from the devices 30a to 30n via the DMX512 network 40. [

The control unit 22 stores the RDM packets to be transmitted to the devices 30a to 30n in the buffer 14 and then transmits them to the devices 30a to 30n. If the response packet of one of the devices 30a to 30n is received within a predetermined time based on the timekeeping data of the timepiece 18, the control unit 22 checks the transaction number of the response packet, And confirms the sequence with the response packet arrived at. The control unit 22 retransmits the RDM packet according to the sequential check result.

Preferably, the controller 22 determines that the RDM packet having the transaction number corresponding to the intermediate empty number is retrieved from the buffer 14 and retransmitted when it is determined that the sequence number is out of sequence and the intermediate empty number is generated.

On the other hand, if there is no sequential error as a result of the sequential check, the control unit 22 deletes the RDM packet having the same transaction number as the transaction number of the response packet from the buffer 14. That is, since the RDM packet having the same transaction number as the transaction number of the response packet in which the sequential error does not occur is data that does not need to be retransmitted, it is desirable to delete the RDM packet in order to optimize the buffer capacity in terms of resource management efficiency.

3 is a flowchart illustrating an error recovery method in the RDM protocol according to an embodiment of the present invention. The error recovery method of FIG. 3 can be understood as an operation in the remote controller 10 shown in FIG.

When the remote controller 10 sends a device control message (RDM packet) to the devices 30a to 30n ("Yes" in S10), the control unit 22 stores the RDM packet to be transmitted in the buffer 14 S12). Here, the RDM packet to be transmitted may be one packet or a plurality of packets arranged in a serial manner.

Next, the control unit 22 controls the transmitting unit 16 to transmit the corresponding RDM packet to the devices 30a to 30n (S14).

Thereafter, the control unit 22 waits for a predetermined period of time to receive a response packet from the corresponding device. At this time, it is possible to confirm whether or not the predetermined time has arrived, based on the time data from the time unit 18.

If a response packet has arrived within a predetermined period of time ("Yes" in S16), the control unit 22 confirms the transaction number TN of the response packet and confirms the sequence with the previously received response packet .

As a result of the sequential check, if there is an empty number in the middle of the sequential check, the control unit 22 determines that the transaction number is a sequential error of the transaction number ("Yes" in S18) 14 to be retransmitted through the transmission unit 16 (S20). Then, the process returns to the above-described step S16 and waits for a response again.

On the other hand, if the response packet does not arrive ("No" in S16), the control unit 22 of the remote controller 10 judges whether there is an RDM packet to be further transmitted in this state (S22). As a result of the determination, if there is an additional RDM packet to be transmitted, the process returns to step S12 to perform packet storage and subsequent operations.

On the other hand, if it is determined in step S18 that the sequential error of the transaction number TN has not occurred, the controller 22 deletes the RDM packet having the same transaction number as the transaction number of the response packet from the buffer 14 (S24), and returns to the above-described step S22 to perform additional RDM packet transmission. Since the RDM packet having the same transaction number as the transaction number of the response packet in which no sequential error occurs does not need to be retransmitted, it is preferable to delete the RDM packet from the buffer 14 in terms of resource management efficiency.

As described above, an optimal embodiment has been disclosed in the drawings and specification. Although specific terms have been employed herein, they are used for purposes of illustration only and are not intended to limit the scope of the invention as defined in the claims or the claims. Therefore, those skilled in the art will appreciate that various modifications and equivalent embodiments are possible without departing from the scope of the present invention. Accordingly, the true scope of the present invention should be determined by the technical idea of the appended claims.

10: remote controller
12: Control message generation unit
14: buffer
16:
18: Timepiece
20: response packet receiver
22:
30a to 30n: Device
40: DMX512 network

Claims (6)

A method for remotely controlling a device connected to a DMX512 network via an RDM protocol based on a DMX512 network,
Storing an RDM packet to be transmitted to the device in a buffer and transmitting the RDM packet to the device;
Waiting for a predetermined time to receive a response packet from the device;
Receiving a response packet within the predetermined time period, checking a transaction number of the response packet and confirming a sequence with a previously arrived response packet; And
And retransmitting the RDM packet according to a result of the sequential check with the previously received response packet. The method according to claim 1,
Wherein the retransmitting the RDM packet comprises:
Wherein the RDM packet having the transaction number corresponding to the intermediate empty number is retransmitted and retransmitted in the buffer when it is determined that the intermediate error number is a sequential error in which the sequence is out of order. The method of claim 2,
Wherein the RDM packet having the same transaction number as the transaction number of the response packet is deleted if the sequential error does not occur as a result of the sequential check. A buffer for storing an RDM packet to be transmitted;
A transmitter for transmitting the RDM packet stored in the buffer to a device connected to the DMX512 network through an RDM protocol based on the DMX512 network;
A timepiece that reveals time;
A response packet receiving unit for receiving a response packet from the device; And
Storing the RDM packet to be transmitted in the buffer and transmitting the RDM packet to the device; receiving a response packet of the device on the basis of the timekeeping data of the timekeeping unit, checking the transaction number of the response packet, And a controller for confirming the sequence with the response packet and for retransmitting the RDM packet according to the result of the sequence check. The method of claim 4,
Wherein,
Wherein the RDM packet having the transaction number corresponding to the intermediate empty number is retransmitted and retransmitted in the buffer when it is determined that the intermediate error number is a sequential error due to the out of order. The method of claim 5,
Wherein the controller deletes the RDM packet having the same transaction number as the transaction number of the response packet if the sequential error does not occur as a result of the sequential check.
KR1020140101737A 2013-11-12 2014-08-07 Method and apparatus for recovering error in RDM protocol KR20150054643A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US14/530,976 US20150131428A1 (en) 2013-11-12 2014-11-03 Method and apparatus for recovering error in rdm protocol

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
KR20130136787 2013-11-12
KR1020130136787 2013-11-12

Publications (1)

Publication Number Publication Date
KR20150054643A true KR20150054643A (en) 2015-05-20

Family

ID=53390733

Family Applications (1)

Application Number Title Priority Date Filing Date
KR1020140101737A KR20150054643A (en) 2013-11-12 2014-08-07 Method and apparatus for recovering error in RDM protocol

Country Status (1)

Country Link
KR (1) KR20150054643A (en)

Similar Documents

Publication Publication Date Title
CN102368700B (en) Transmission method of massages in distributed system
US7746786B2 (en) Retransmission control method and device
RU2421918C2 (en) Protocol of automatic repeat request having multiple mechanisms of additional feedback
CN106559739B (en) Lightweight data transmission method suitable for Bluetooth low-power wireless communication system
CN101848490B (en) According to the method for operation of data duplicate retransmission and device in mobile communication system
US7609698B2 (en) Apparatus and method for retransmitting data in mobile communication system
RU2011108113A (en) DEVICE AND METHOD FOR FORMING MAS DATA PROTOCOL MODULE IN WIRELESS COMMUNICATION SYSTEM
KR102147679B1 (en) Hybrid arq method and apparatus in a relay wireless communication system using compress and forward scheme
JP6374945B2 (en) Method and apparatus for using more transmission opportunities in a distributed network topology with limited HARQ processes
CN104780028A (en) Method and equipment for retransmitting TCP (transmission control protocol) data messages
US20060039698A1 (en) System and method of communications with traffic signals
JPWO2007052719A1 (en) Retransmission control method and receiving apparatus
CN104993916A (en) method and apparatus for processing date by terminal in mobile communication system
CN103973414B (en) A kind of data transmission method and device
ATE500670T1 (en) BUILDING A LOSSLESS RADIO LINK CONTROL ENTITY (RLC) WHILE AVOIDING DUPLICATION OF THE SERVICE DATA UNIT (SDU)
KR101769133B1 (en) Electronic device adaptively selecting tcp/r-udp and packet transmitting/receiving method thereof
CN101601219A (en) The method and apparatus that is used for improved re-transmission
CN102377544A (en) Retransmission method in communication system
US20150131428A1 (en) Method and apparatus for recovering error in rdm protocol
JP4708982B2 (en) Retransmission control method and receiving apparatus
KR20150054643A (en) Method and apparatus for recovering error in RDM protocol
KR100683417B1 (en) Apparatus and method of packet relay in wireless network, MAC layer data structure therein
KR101019055B1 (en) Method for reliability of transferring data in a network
JP4936469B2 (en) Communications system
KR100855347B1 (en) Message transmitting system based on udp control and method for the same

Legal Events

Date Code Title Description
WITN Withdrawal due to no request for examination