System with Data Exchange and Monitoring Techniques for Real-Time Event Delivery
A communication protocol with a dedicated UDP header ensures reliable and real-time data exchange between systems by using redundancy and monitoring, addressing the limitations of existing methods for joint operations.
Patent Information
- Application Number
- KR1020230186922
- Authority / Receiving Office
- KR · KR
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2023-12-20
- Publication Date
- 2026-11-10
- Estimated Expiration
- 2043-12-20
AI Technical Summary
Existing communication methods like TCP and UDP lack unified reliability and real-time capabilities for data exchange between systems performing different tasks, making them unsuitable for joint operations.
A communication protocol that inserts a dedicated header into UDP packets for real-time event transmission, including features like packet type, sequence number, retransmission count, and checksums, with redundancy and monitoring packets to ensure reliable and real-time data exchange.
Enables high-reliability, real-time data exchange between systems, ensuring time-sensitive data processing without loss or damage, and providing fault detection and recovery mechanisms.
Smart Images

Figure 112023143122765-PAT00003_ABST
Abstract
Description
Technology Field
[0001] The present invention relates to a system to which data exchange and monitoring techniques for real-time event delivery are applied. Background Technology
[0002] Systems performing different tasks are highly likely to exchange data within their respective systems using individual communication methods developed by multiple vendors. Therefore, to perform common missions while closely interoperating with each other, a unified communication method that guarantees high reliability and real-time performance is required.
[0003] Although TCP (Transmission Control Protocol) is highly reliable, it includes flow and congestion control methods, making it susceptible to interference from other traffic and lacking real-time capabilities. Therefore, it has limitations in providing unified communication with guaranteed real-time performance while systems performing different tasks interoperate and carry out common missions.
[0004] User Datagram Protocol (UDP) places low overhead on data transmission but makes it difficult to expect reliable data delivery. A method has been proposed to address this issue to some extent by defining separate fields based on UDP for communication. A representative such method is Real-Time Protocol (RTP, defined in RFC 3350), which utilizes dedicated headers and payloads to specialize in the transmission of multimedia, such as audio and video, for real-time streaming services. However, it is not a suitable communication method for performing joint tasks while closely interoperating between systems. The problem to be solved
[0005] The technical problem that the present invention aims to solve is to provide a system that communicates using a communication method in which data exchange and monitoring techniques for real-time event transmission are applied. means of solving the problem
[0006] In the system according to the present invention for solving the above-mentioned technical problem, the packet exchanged between the first computing device and the second computing device has a structure in which a dedicated header is inserted after the UDP L4 header of the UDP (User Datagram Protocol) packet.
[0007] When the first computing device and the second computing device receive a sending packet sent by the other party, they send a Reply packet corresponding to the sending packet to the other party; when the Reply packet sent by the other party is successfully received, they send a sending packet corresponding to the next procedure of the sending packet corresponding to the successfully received Reply packet to the other party; and if the Reply packet corresponding to the sending packet is not successfully received from the other party within a predetermined time, they resend the sending packet for which the Reply packet was not successfully received to the other party.
[0008] The above dedicated header may include a packet type, a sequence number by type, the number of retransmissions, an event size, a standard transmission time, a data checksum, and a header checksum.
[0009] Packet type is a value identifying one of a connection control packet, a payload packet, and a monitoring packet, type-specific sequence number is a value managing the packet order by packet type and by sender / receiver, retransmission count is a value that increases by 1 when the same sent packet is retransmitted, event size is a value indicating the size of the payload portion attached after the dedicated header, the sending standard time is the current standard time of the sender when the packet is sent from the sender, and data checksum and header checksum may be checksum values for detecting errors in the payload and dedicated header.
[0010] The Reply packet includes a dedicated header of the corresponding sending packet, wherein the sending standard time included in the dedicated header of the sending packet can be changed to the sending standard time of the Reply packet.
[0011] The above connection control packet is a packet in which the packet type is set to connection control packet in the dedicated header, and the above connection control packet can be classified into a communication connection start request packet, a communication connection start request acceptance packet, a communication termination request packet, and a communication termination request acceptance packet based on a specific value of the data checksum of the dedicated header.
[0012] When the first computing device transmits a communication connection start request packet to the second computing device and receives a Reply packet corresponding to the communication connection start request packet, and when the second computing device transmits a communication connection start request acceptance packet to the first computing device and receives a Reply packet corresponding to the communication connection start request acceptance packet, a communication connection can be established between the first computing device and the second computing device.
[0013] The above payload packet is a packet in which the packet type is set to payload packet in the dedicated header, and the above payload packet may include one or more payloads corresponding to event data to be exchanged between the first computing device and the second computing device after the dedicated header.
[0014] The above one or more payloads include fields for a payload start identifier, a payload type, an event ID, and an ID-specific indicator value. The payload start identifier is an indicator value indicating the start of each payload included in the payload packet. The payload type is an identifier distinguishing whether the event data of the payload is data transmitted periodically or non-periodically. The event ID is an identifier assigned to each event type. The ID-specific indicator value may be a value representing detailed information about the event corresponding to the event ID.
[0015] If the standard time of dispatch for a dispatch packet sent from the first computing device to the second computing device is 'T1', the current standard time of the second computing device is 'T2' when the second computing device receives the dispatch packet, the standard time of dispatch for a Reply packet sent from the second computing device in response to the dispatch packet is 'T3', and the current standard time of the first computing device is 'T4' when the first computing device receives the Reply packet, then the second computing device is △T 21 (=T2-T1) and △T 32 Obtain at least one of (=T3-T2) to monitor the packet transmission status between the first computing device and the second computing device, and the first computing device is △T 43 (=T4-T3) and △T 41 By obtaining at least one of (=T4-T1), the packet transmission status between the first computing device and the second computing device can be monitored.
[0016] When the communication channel between the first computing device and the second computing device is configured with redundancy using an Active channel and a Standby channel, the first computing device and the second computing device exchange monitoring packets at predetermined intervals through the Standby channel to verify the validity of the Standby channel, and can immediately switch to the Standby channel if an abnormal condition occurs in the Active channel.
[0017] When the communication channel between the first computing device and the second computing device is triple-redundantly configured with three channels, the first computing device and the second computing device can determine that the payload packet is normal when the payload data of the payload packet received from two or more of the three channels matches.
[0018] The first computing device and the second computing device may generate an alarm on the operator screen in at least one of the following cases: when a payload corresponding to a data type determined to be transmitted periodically is received a number of times exceeding the allowable error range relative to a predetermined period; when the payload contains a value other than a predetermined value; when a payload packet is received before or after the start or end of a communication connection between the first computing device and the second computing device; when a retransmission of the payload packet occurs; and when a Reply packet is not received while the payload packet is retransmitted a predetermined number of times. Effects of the invention
[0019] According to the present invention, a unified communication method with high reliability and real-time capability can be provided between systems performing different tasks. Accordingly, the present invention enables the exchange and processing of time-sensitive data between systems performing different tasks without loss or damage. Brief explanation of the drawing
[0020] FIG. 1 is a configuration diagram of data exchange and monitoring for real-time event transmission according to one embodiment of the present invention. FIG. 2 is a diagram provided to illustrate a dedicated header inserted into a UDP packet according to the present invention. FIG. 3 is a flowchart illustrating a communication connection procedure according to one embodiment of the present invention. FIG. 4 is a flowchart illustrating a communication connection termination procedure according to an embodiment of the present invention. FIG. 5 is a drawing provided to illustrate a payload packet according to an embodiment of the present invention. FIG. 6 is a flowchart illustrating a transmission status monitoring method using packet transmission and reception time according to an embodiment of the present invention. Specific details for implementing the invention
[0021] Then, with reference to the attached drawings, embodiments of the present invention will be described in detail so that those skilled in the art can easily implement the present invention.
[0022] The terms used in this specification are for describing embodiments and are not intended to limit the invention. In this specification, the singular form includes the plural form unless specifically stated otherwise in the text. The terms "comprises" and / or "comprising" used in this specification do not exclude the presence or addition of one or more other components in addition to the components mentioned. Throughout the specification, the same reference numerals refer to the same components, and "and / or" includes each of the mentioned components and all combinations of one or more. Although terms such as "first," "second," etc., are used to describe various components, these components are not limited by these terms. These terms are used merely to distinguish one component from another. Therefore, the first component mentioned below may be the second component within the technical scope of the invention.
[0023] In this specification, the term "computing device" includes all various devices capable of performing computational processing and providing results to a user. For example, a computing device may include desktop PCs, notebook computers, and server computers, as well as smartphones, tablet PCs, cellular phones, PCS phones (Personal Communication Service phones), synchronous / asynchronous IMT-2000 (International Mobile Telecommunication-2000) mobile terminals, Palm PCs (Personal Computers), and Personal Digital Assistants (PDAs).
[0024] FIG. 1 is a configuration diagram of data exchange and monitoring for real-time event transmission according to one embodiment of the present invention.
[0025] Referring to FIG. 1, the first system (100) and the second system (200) are systems that perform different tasks and may each include a plurality of computing devices.
[0026] The first system (100) and the second system (200) can exchange data through different individual communication methods within their respective systems.
[0027] The first system (100) and the second system (200) can exchange packets according to the communication protocol newly proposed in the present invention. Here, the packet exchange between the first system (100) and the second system (200) can be understood as packet exchange through a communication network between a first computing device and a second computing device belonging to the first system (100) and the second system (200), respectively.
[0028] First, a packet used in the communication protocol according to the present invention will be described. The packet according to the present invention has a structure in which a dedicated header is inserted into the payload portion of a UDP (User Datagram Protocol) packet.
[0029] According to the protocol according to the present invention, the first system (100) and the second system (200) exchange packets such as connection control packets, payload packets, and monitoring packets, and corresponding reply packets.
[0030] A connection control packet is a packet used in the communication connection and termination procedure between the first system (100) and the second system (200). A payload packet is a packet used for data transmission, such as event delivery, after establishing a communication connection between the first system (100) and the second system (200). A monitoring packet is a packet used to verify the health of the communication channel established between the first system (100) and the second system (200).
[0031] For all packets sent by the sender, such as connection control packets, payload packets, and monitoring packets, the receiver sends a Reply packet to the sender containing a dedicated header for the corresponding packet. The sender proceeds to the next procedure only if there are no issues with the Reply packet. The Reply packet can be used to acknowledge receipt of the packet sent by the sender and to monitor the network status.
[0032] All packets sent from the sending side are retransmitted if a Reply packet is not received within a predetermined time (e.g., 500ms), and the communication connection of the session can be terminated if a Reply packet is not received within a predetermined number of times (e.g., 2 times).
[0033] Meanwhile, it is desirable to implement the protocol according to the present invention in a redundant or triple redundant environment to improve availability and reliability.
[0035] FIG. 2 is a diagram provided to illustrate a dedicated header inserted into a UDP packet according to the present invention.
[0036] Referring to FIG. 2, the packet according to the present invention has a structure in which a dedicated header (20) is inserted after the UDP L4 header (10) of the UDP packet.
[0037] The UDP L4 header (10) has fields such as Source / Destination Port Number, UDP length, and UDP CheckSum arranged in order.
[0038] The dedicated header (20) has fields such as "packet type (21)", "sequence number by type (22)", "retransmission count (23)", "event size (24)", "transmission standard time (25)", "data checksum (26)", and "header checksum (27)" arranged in a predetermined order. Depending on the embodiment, the order of the fields of the dedicated header (20) may be changed.
[0039] "Packet type (21)" contains a value that identifies the packet type, such as the previously described "connection control packet," "payload packet," and "monitoring packet."
[0040] The "sequence number by type (22)" is managed by packet type and by the transmitting and receiving side. When the transmitting side successfully receives a Reply packet corresponding to the transmitted packet, the "sequence number by type (22)" increases by one each time the next packet is transmitted. Here, the Reply is a packet transmitted to the sending side in response to the received packet when the receiving side successfully receives the packet. Through the "sequence number by type (22)," it is possible to check whether a packet is missing, or to identify the target for retransmission.
[0041] "The number of retransmissions (23)" increases by 1 each time the same packet is retransmitted.
[0042] "Event size (24)" indicates the size of the entire payload, i.e., the data portion attached after the dedicated header (20).
[0043] "The standard time of transmission (25)" is the standard time of the sending side inserted during packet transmission. The standard time of the sending side may be a standard time with a time precision of ms or more.
[0044] "Data checksum (26)" and "header checksum (27)" each include a checksum capable of detecting errors in the payload (event data) and dedicated header (20).
[0045] In cases where data fields are not used, such as in "connection control packets" (i.e., cases where no payload is included other than a dedicated header), the "data checksum (26)" field can be used as a field in which an identifier is entered to identify "communication connection start request," "communication connection start request acceptance," "communication termination request," and "communication termination request acceptance" during communication connection and termination procedures.
[0047] Hereinafter, connection control packets, payload packets, and monitoring packets exchanged between the first system (100) and the second system (200) according to the protocol according to the present invention will be described in detail in order.
[0049] - Connection control packet
[0050] It is used to indicate "start communication connection" and "end communication connection" between the first system (100) and the second system (200).
[0051] FIG. 3 is a flowchart illustrating a communication connection procedure according to one embodiment of the present invention, and FIG. 4 is a flowchart illustrating a communication connection termination procedure according to one embodiment of the present invention.
[0052] Referring to FIG. 3, a communication connection is established between the first system (100) and the second system (200) through the exchange of four packets: a "communication connection start request" packet, a "communication connection start request acceptance" packet, and a Reply packet corresponding to each.
[0053] Referring to FIG. 4, the communication connection between the first system (100) and the second system (200) is terminated by the exchange of four packets: a "communication connection termination request" packet, a "communication connection termination request acceptance" packet, and a Reply packet corresponding to each.
[0054] As explained above, among the "connection control packets," the "communication connection start request," "communication connection start request acceptance," "communication connection termination request," and "communication connection termination request acceptance" packets are identified using the "data checksum (26)" field.
[0055] A communication connection request can be initiated from either side of the communication between the first system (100) and the second system (200).
[0056] After the communication connection between the first system (100) and the second system (200) is established, the status of each channel can be displayed on the operator screen of a display device (not shown) used by the operator of each of the first system (100) and the second system (200).
[0058] - Payload packet
[0059] The payload packet includes a payload containing event data to be exchanged between the first system (100) and the second system (200).
[0060] FIG. 5 is a drawing provided to illustrate a payload packet according to an embodiment of the present invention.
[0061] Referring to FIG. 5, the payload packet according to the present invention includes a payload (30) after a dedicated header (20).
[0062] The payload packet may include one or more payloads (30a, 30b, …) consecutively after a dedicated header (20). This allows multiple events to be transmitted simultaneously by a single payload packet.
[0063] The payload (30a, 30b, …) consists of fields such as "payload start identifier (31)", "payload type (32)", "event ID (33)", and "ID-specific indicator (34)" arranged in order.
[0064] "Payload start identifier (31)" is an indicator value that indicates that each payload (30a, 30b, …) is started.
[0065] "Payload type (32)" is an identifier that distinguishes the type of data in which event data to be exchanged between the first system (100) and the second system (200) is transmitted periodically or non-periodically. Depending on the "Payload type (32)," it is possible to distinguish whether the data is transmitted periodically or non-periodically. Meanwhile, the transmission period of the payload packet can be varied in advance or during operation at the operator's request (for example, the transmission period of the payload packet can be varied within the range of 50ms to 2s. Of course, the transmission period range may also be determined differently depending on the embodiment).
[0066] "Event ID (33)" is an identifier assigned to each type of event to identify a specific event. By assigning event IDs according to number ranges systematically classified by participating systems and event types, operators between missions can intuitively identify specific events (for example, with '2' predefined to represent ambient oxygen supply equipment, '5' to represent building 5, and '34' to represent valve 34, event ID '2534' indicates that the corresponding event data is for valve 34 of building 5 of the ambient oxygen supply equipment).
[0067] "ID-specific indicator value (34)" is a value used to identify detailed information about an event corresponding to an event ID, such as a command, command execution result, or measurement value for the corresponding event type. By assigning a systematic number range to each event type, "ID-specific indicator value (34)" can also be intuitively recognized by operators during each mission (for example, the ID-specific indicator value '1010' can be assigned such that the first '10' indicates supply and the second '10' indicates start).
[0068] Meanwhile, the receiving side that has received the payload packet transmitted from the transmitting side may perform a task according to the payload packet and then transmit a payload packet corresponding to the result value to the transmitting side. For example, the receiving side that has received "Event ID (33)" '2534' and "ID-specific instruction value (34)" '1010' from the transmitting side may perform the corresponding task and then transmit a payload packet containing "Event ID (33)" '2534' and "ID-specific instruction value (34)" '1020" corresponding to the result of the task to the transmitting side. Here, the last '20' in "ID-specific instruction value (34)" '1020' indicates completion of supply.
[0070] - Monitoring packets
[0071] Monitoring packets can be transmitted periodically (e.g., every 500ms) to check the communication health of each channel established in the first system (100) and the second system (200).
[0072] Monitoring packets can be transmitted by both parties after a communication connection is established. The transmission period of monitoring packets may vary in advance or during operation depending on the operating status or monitoring purpose (e.g., 50ms to 2s).
[0074] Meanwhile, the first system (100) and the second system (200), which perform different tasks, can synchronize their internal time through standard time. And since precise time synchronization is essential for the sequential execution of complex events and accident analysis between the first system (100) and the second system (200), the time synchronization between the first system (100) and the second system (200) and the system status can be monitored in real time to display an alarm when a problem occurs, using the method described below.
[0076] FIG. 6 is a flowchart illustrating a transmission status monitoring method using packet transmission and reception time according to an embodiment of the present invention.
[0077] Referring to FIG. 6, transmission status monitoring according to the present invention can be performed through all packets (connection control packet, payload packet, monitoring packet, etc.).
[0078] First, the sending side may include the creation time 'T1' of a payload packet, connection control packet, or monitoring packet (hereinafter referred to as 'sending packet') as the 'sending standard time' in a dedicated header and transmit it to the receiving side.
[0079] At the receiving end, the difference between the current standard time 'T2' of the receiving end that received the sent packet and the sending standard time 'T1' of the sent packet (△T 21 Calculate (=T2-T1) and △T 21 If this predetermined allowable range is exceeded, it can be determined that a problem has occurred with time synchronization between the transmitting and receiving systems or with the systems themselves. Specifically, △T 21If this predetermined allowable range is exceeded, it is determined that problems have occurred, such as 1) the soundness of the time synchronization system including the GPS receiver and signal splitter, 2) the soundness of the time synchronization processing logic of both the transmitting and receiving systems, 3) whether network delays have occurred along the path, 4) the soundness of the data processing logic of both the transmitting and receiving systems, and 5) CPU overload or memory shortage in both the transmitting and receiving systems, and a procedure to inspect both the transmitting and receiving systems can be performed. In this way, since the total processing time is monitored very precisely through time synchronization monitoring, it can play an important role in detecting and repairing problems (load or processing logic).
[0080] The receiving side can generate a Reply packet for the dispatch packet sent by the transmitting side, include the time 'T3' at which the Reply packet was generated as the standard dispatch time of the Reply packet in a dedicated header, and send it to the transmitting side.
[0081] At the receiving end, the difference between the standard sending time of the Reply packet 'T3' and the time of receiving the packet 'T2' (△T 32 Calculate (=T3-T2) and △T 32 If it exceeds the predetermined allowable range, it can be determined that a problem has occurred in the receiving side's internal system.
[0082] On the sending side, the difference between the sending side's current standard time 'T4' at which the Reply packet was received and the sending standard time 'T3' of the Reply packet (△T 43 Calculate (=T4-T3) and △T 43 If this predetermined allowable range is exceeded, it can be determined that a time synchronization issue has occurred between the sending and receiving systems, a system problem has arisen, or the delay time has increased. Previously, the difference (△T) between the receiving side's current standard time 'T2' and the sending packet's standard time 'T1'. 21Similar to when =T2-T1) exceeds a predetermined allowable range, it is determined that a problem has occurred, and inspection procedures can be performed on both the transmitting and receiving systems.
[0083] In addition, on the sending side, the difference (△T) between the sending side's current time 'T4' when the Reply packet was received and the standard sending time 'T1' of the sent packet 41 Calculate (=T4-T1) and △T 41 If this predetermined allowable range is exceeded, it can be determined that a problem has occurred with time synchronization between the transmitting and receiving systems.
[0084] And on the transmitting side, △T 43 and △T 41 By comparing, the following points can be verified.
[0085] △T 43 △T 41 : Can determine time synchronization with the receiving end or whether there is a lot of data on the receiving path
[0086] 2×△T 43 << △T 41 : Determine transmission time synchronization or data delivery delay along the transmission path
[0087] Meanwhile, according to an embodiment, it is also possible to implement transmission status monitoring using only monitoring packets and reply packets thereto. Furthermore, since monitoring packets and reply packets are periodically exchanged between both sides of the communication, transmission status monitoring according to the present invention is possible at both sides of the communication.
[0089] Communication connections between the first system (100) and the second system (200) according to the communication protocol according to the present invention can be multiplexed into multiple channels. In this case, the validity of each channel can be determined as follows.
[0090] When the communication channel between the first system (100) and the second system (200) is configured with redundancy, it is possible to implement a system where a session is established in advance for both the Active channel and the Standby channel, and the validity of the Standby channel is also verified through "monitoring packets." The validity status of the Active channel and the Standby channel can be displayed on the operator screen. For example, the validity of the Standby channel can be verified by exchanging monitoring packets at predetermined intervals through the Standby channel, and if an abnormal state occurs in the Active channel—for example, if a normal Reply packet is not received within a predetermined number of times—it can be implemented to immediately switch to the Standby channel in a normal state.
[0092] When the communication channel between the first system (100) and the second system (200) is configured as a triple redundancy, three separate sessions are established between the first system (100) and the second system (200). After the sessions are established, it is determined to be normal when the payload data of the payload packets received from two or more of the three channels matches. The determination of whether the payloads match is performed within a "payload comparison allowance time" predetermined by the operator. The payload comparison allowance time can be implemented to count from the time when a payload packet is received from one of the three channels.
[0093] If the payload packets received from two of the three channels match, it is determined to be normal, but abnormal channels that do not match may be displayed on the operator screen. Additionally, if the payload data between each channel does not match, it is determined to be abnormal and an alarm may be generated.
[0094] Meanwhile, even if the payload data for each channel is compared and determined to be normal, the system can be implemented to identify the situation as abnormal in the following cases and trigger an alarm on the operator screen. Of course, it is also possible to exclude some of the situations exemplified here from being identified as abnormal, or to add other situations to be identified as abnormal.
[0095] Meanwhile, the first system (100) and the second system (200) can determine that an abnormality has occurred in the following cases and generate an alarm on the operator screen.
[0096] 1. In the case of a periodic payload configured to be transmitted periodically, if the payload is received a number of times exceeding the tolerance range relative to the pre-agreed period
[0097] 2. If a value other than the promised value is received in the payload("payload start identifier", "payload type", "event ID", "ID-specific indicator")
[0098] 3. When a payload packet is received before the start or after the termination of the inter-system communication connection
[0099] 4. When payload packet retransmission occurs
[0100] 5. If a Reply packet is not received while the payload packet is retransmitted a predetermined number of times (e.g., 2 times)
[0102] The embodiments described above may be implemented as hardware components, software components, and / or combinations of hardware and software components. For example, the devices, methods, and components described in the embodiments may be implemented using one or more general-purpose or special-purpose computers, such as, for example, a processor, a controller, an arithmetic logic unit (ALU), a digital signal processor, a microcomputer, a field programmable gate array (FPGA), a programmable logic unit (PLU), a microprocessor, or any other device capable of executing and responding to instructions. The processing unit may execute an operating system (OS) and one or more software applications executed on said operating system. Additionally, the processing unit may access, store, manipulate, process, and generate data in response to the execution of the software. For ease of understanding, the processing unit may be described as being used as a single unit, but those skilled in the art will understand that the processing unit may include multiple processing elements and / or multiple types of processing elements. For example, the processing unit may include multiple processors or one processor and one controller. Additionally, other processing configurations, such as parallel processors, are also possible.
[0103] Software may include computer programs, code, instructions, or a combination of one or more of these, and may configure a processing unit to operate as desired or instruct the processing unit independently or collectively. Software and / or data may be permanently or temporarily embodied in any type of machine, component, physical device, virtual equipment, computer storage medium, or device so as to be interpreted by the processing unit or to provide instructions or data to the processing unit. Software may be distributed over networked computer systems and stored or executed in a distributed manner. Software and data may be stored on one or more computer-readable recording media.
[0104] The method according to the embodiment may be implemented in the form of program instructions that can be executed through various computer means and recorded on a computer-readable medium. The computer-readable medium may include program instructions, data files, data structures, etc., either alone or in combination. The program instructions recorded on the medium may be those specifically designed and configured for the embodiment, or they may be those known and available to those skilled in the art of computer software. Examples of computer-readable recording media include magnetic media such as hard disks, floppy disks, and magnetic tapes; optical recording media such as CD-ROMs and DVDs; magneto-optical media such as floptical disks; and hardware devices specifically configured to store and execute program instructions, such as ROM, RAM, and flash memory. Examples of program instructions include machine code, such as that generated by a compiler, as well as high-level language code that can be executed by a computer using an interpreter, etc. The hardware devices described above may be configured to operate as one or more software modules to perform the operation of the embodiment, and vice versa.
[0105] Although the embodiments have been described above with reference to the limited drawings, those skilled in the art can apply various technical modifications and variations based on the above. For example, suitable results may be achieved even if the described techniques are performed in a different order than described, and / or if the components of the described system, structure, device, circuit, etc. are combined or assembled in a form different from described, or replaced or substituted by other components or equivalents.
Claims
Claim 1 In a system comprising a first computing device and a second computing device, the packets exchanged between the first computing device and the second computing device have a structure in which a dedicated header is inserted after the UDP L4 header of a UDP (User Datagram Protocol) packet; the first computing device and the second computing device, upon receiving a sending packet sent by the other party, send a Reply packet corresponding to the sending packet to the other party; upon successfully receiving the Reply packet sent by the other party, send a sending packet corresponding to the next procedure of the sending packet corresponding to the successfully received Reply packet to the other party; and if the Reply packet corresponding to the sending packet is not successfully received from the other party within a predetermined time, resend the sending packet for which the Reply packet was not successfully received to the other party; the dedicated header includes a packet type, a type-specific sequence number, a number of retransmissions, an event size, a standard sending time, a data checksum, and a header checksum; the packet type is a value identifying one of a connection control packet, a payload packet, and a monitoring packet; the type-specific sequence number is a value managing the packet order by packet type and by sender / receiver; and the number of retransmissions is the same sending A system in which a value that increases by 1 when a packet is retransmitted, an event size is a value representing the size of the payload portion attached after the dedicated header, the transmission standard time is the current standard time of the sender corresponding when the packet is sent from the sender, the data checksum and header checksum are checksum values for detecting errors in the payload and dedicated header, and the Reply packet includes the dedicated header of the corresponding sending packet, wherein the transmission standard time included in the dedicated header of the sending packet is changed to the transmission standard time of the Reply packet. Claim 2 delete Claim 3 delete Claim 4 A system in which, in claim 1, the connection control packet is a packet in which the packet type is set to a connection control packet in the dedicated header, and the connection control packet is classified into a communication connection start request packet, a communication connection start request acceptance packet, a communication termination request packet, and a communication termination request acceptance packet by the value of the data checksum of the dedicated header, and when the first computing device transmits a communication connection start request packet to the second computing device and receives a Reply packet corresponding to the communication connection start request packet, and when the second computing device transmits a communication connection start request acceptance packet to the first computing device and receives a Reply packet corresponding to the communication connection start request acceptance packet, a communication connection is established between the first computing device and the second computing device. Claim 5 A system according to claim 1, wherein the payload packet is a packet in which the packet type is set to payload packet in the dedicated header, and the payload packet includes one or more payloads corresponding to event data to be exchanged between the first computing device and the second computing device following the dedicated header. Claim 6 In claim 5, the one or more payloads include fields for a payload start identifier, a payload type, an event ID, and an ID-specific indicator value, wherein the payload start identifier is an indicator value indicating the start of each payload included in the payload packet, the payload type is an identifier distinguishing whether the event data of the payload is data transmitted periodically or non-periodically, the event ID is an identifier assigned to each event type, and the ID-specific indicator value is a value representing detailed information about the event corresponding to the event ID. Claim 7 In claim 1, if the standard time of dispatch of a dispatch packet sent from the first computing device to the second computing device is 'T1', the current standard time of the second computing device is 'T2' when the second computing device receives the dispatch packet, the standard time of dispatch of a Reply packet sent from the second computing device in response to the dispatch packet is 'T3', and the current standard time of the first computing device is 'T4' when the first computing device receives the Reply packet, then the second computing device is △T 21 (=T2-T1) and △T 32 Obtaining at least one of (=T3-T2) to monitor the packet transmission status between the first computing device and the second computing device, and the first computing device △T 43 (=T4-T3) and △T 41 A system for monitoring packet transmission status between the first computing device and the second computing device by obtaining at least one of (=T4-T1). Claim 8 In claim 1, when a communication channel between the first computing device and the second computing device is configured with redundancy in the form of an Active channel and a Standby channel, the first computing device and the second computing device exchange monitoring packets at predetermined intervals through the Standby channel to verify the validity of the Standby channel, and if an abnormal condition occurs in the Active channel, the system switches immediately to the Standby channel. Claim 9 In claim 1, when the communication channel between the first computing device and the second computing device is triple-redundantly configured with three channels, the first computing device and the second computing device determine a payload packet as normal when the payload data of a payload packet received from two or more of the three channels matches. Claim 10 A system for generating an alarm on an operator screen in at least one of the following cases: when the first computing device and the second computing device receive a payload corresponding to a data type determined to be transmitted periodically a number of times exceeding an allowable error range relative to a predetermined period; when the payload contains a value other than a predetermined value; when a payload packet is received before or after the start or end of a communication connection between the first computing device and the second computing device; when a retransmission of the payload packet occurs; and when a Reply packet is not received while the payload packet is retransmitted a predetermined number of times.
Citation Information
Patent Citations
Compression device and associated decompression device
EP1916819A1
Four layer architecture for network device drivers
US20050213603A1
Compression device wherein compression is adapted as a function of the transport medium, and associated decompression device, for communication equipments
US20080098129A1
Packet transmission method and user equipment
US20200195390A1
