KR100919216B1 - Method and apparatus for transmitting and receiving data - Google Patents

Abstract

The present invention relates to a packet structure and a transmission method in which headers and data are changed. According to an aspect of the present invention, a data transmitting method separates data in packet units, generates a packet in which a header is added to the rear end of the separated data, and transmits the packet to the receiving end. The receiving end receives the packet transmitted from the transmitting end by the data receiving method, directly connects the received packet to the data of the previous packet, and separates the header of the received packet. According to this, there is an advantage that the data recombination can be continuously performed by utilizing the packet structure in which the header located at the front end of the data is arranged at the rear end.

Description

Data transmission method, reception method and apparatus therefor {Method and apparatus for transmitting and receiving data}

The present invention relates to a packet structure, and more particularly, to a packet structure and a transmission method in which headers and data are changed.

Transmission Control Protocol / Internet Protocol (TCP / IP) is the basic communication protocol of the Internet. When a user configures his computer to access the Internet, a TCP / IP program is installed, which allows him or her to exchange messages or obtain information with other computer users who also use the same TCP / IP protocol.

TCP / IP consists of two layers. TCP, the upper layer (transport layer), is responsible for dividing messages or files into smaller packets for transmission over the Internet, and for reassembling the received packets into original messages. Divide the data into packets (segments) and add a header to each. The header contains information that the segment uses to recombine it in its original form, confirming that the data has not been changed while in transit.

IP, the lower layer (internet layer) processes the address portion of each packet, allowing packets to reach their destination accurately. Each gateway on the network checks the address of the message to know where to forward the message.

In addition to TCP as a transport layer, there is also a user data protocol (UDP). When a user sends and receives information on the Internet, it refers to a communication protocol of a method of unilaterally sending from one side to another.

In the transport layer, the header attached to the front end of the received packet identifies the data at the rear end and recombines the original form. In this case, there is a problem in that data recombination is possible after the process of checking the header and separating the header for each packet in the case of continuously transmitted data, thereby causing a time delay.

Accordingly, the present invention provides a data transmission method capable of continuous data recombination using a packet structure in which a header located at a data front end is arranged at a rear end.

In addition, the present invention provides a data transmission method with improved efficiency in recombining data.

According to an aspect of the present invention, a method for transmitting data through a network, the method comprising: separating the data into packet units; Generating a packet including a header after the separated data; And transmitting the packet to a receiving end.

In the transmitting of the packet to the receiving end, the packet may be sequentially transmitted such that the separated data is sequentially received at the receiving end.

The data may be part of a multimedia data stream.

In addition, the header may include information for recombining the separated data.

The separating of the data and generating the packet may be performed in a transport layer.

According to another aspect of the present invention, in a recording medium on which a program of instructions that can be executed by a computer is tangibly implemented so that a method of transmitting data through a network is implemented, the program being readable by a computer, Separating, by the transmitter, data in packet units; Generating a packet including a header after the separated data; And a recording medium recording a program for implementing a data transmission method comprising the step of transmitting the packet to a receiving end.

In the transmitting of the packet to the receiving end, the packet may be sequentially transmitted such that the separated data is sequentially received at the receiving end.

The data may be part of a multimedia data stream.

In addition, the header may include information for recombining the separated data.

The separating of the data and generating the packet may be performed in a transport layer.

According to another aspect of the present invention, there is provided a method of receiving data over a network, the method comprising: a receiving end receiving a packet transmitted from a transmitting end, wherein the packet is located at a front end and a header at a rear end; Directly connecting the received packet to data of a previous packet; And separating a header of the received packet.

Here, the packet may be sequentially transmitted at the transmitting end so that data in the packet is sequentially recombined.

The data may be part of a multimedia data stream.

In addition, the header may include information for recombining the separated data.

The connection of the data and the separation of the header may be performed at the transport layer.

According to another aspect of the present invention, there is provided a recording medium in which a program of instructions that can be executed by a computer is tangibly implemented so that a method of receiving data through a network is embodied and records a program that can be read by a computer. Receiving, by the receiving end, a packet transmitted from the transmitting end, wherein the packet has data located at the front end and a header at the rear end; Directly connecting the received packet to data of a previous packet; And separating a header of the received packet. There is provided a recording medium recording a program for implementing a data receiving method.

Here, the packet may be sequentially transmitted at the transmitting end so that data in the packet is sequentially recombined.

The data may be part of a multimedia data stream.

In addition, the header may include information for recombining the separated data.

The connection of the data and the separation of the header may be performed at the transport layer.

Other aspects, features, and advantages other than those described above will become apparent from the following drawings, claims, and detailed description of the invention.

In the data transmission method according to the present invention, data recombination can be continuously performed by using a packet structure in which a header located at a data front end is arranged at a rear end.

In addition, since the process of separating the header is not preceded, serial data recombination is possible, which is useful for real time reproduction of a multimedia data stream.

In addition, the efficiency is improved in recombining the data.

1 is a packet structure in a general transport layer.

2 is a packet structure in a transport layer according to an embodiment of the present invention.

3 is information included in a header in a TCP protocol according to an embodiment of the present invention.

4 is information included in a header in the UDP protocol according to an embodiment of the present invention.

5 is a flowchart of a data transmission method using a packet structure according to an embodiment of the present invention.

6 is a flowchart of a data receiving method using a packet structure according to an embodiment of the present invention.

7 is a diagram illustrating time lapse upon reception of a general packet structure.

8 is a diagram showing time lapse upon reception of a packet structure according to an embodiment of the present invention.

<Description of the symbols for the main parts of the drawings>

100, 200: packet

110, 210: header

120, 220: data

As the invention allows for various changes and numerous embodiments, particular embodiments will be illustrated in the drawings and described in detail in the written description. However, this is not intended to limit the present invention to specific embodiments, it should be understood to include all transformations, equivalents, and substitutes included in the spirit and scope of the present invention. In the following description of the present invention, if it is determined that the detailed description of the related known technology may obscure the gist of the present invention, the detailed description thereof will be omitted.

Terms such as first and second may be used to describe various components, but the components should not be limited by the terms. The terms are used only for the purpose of distinguishing one component from another.

The terminology used herein is for the purpose of describing particular example embodiments only and is not intended to be limiting of the present invention. Singular expressions include plural expressions unless the context clearly indicates otherwise. In this application, the terms "comprise" or "have" are intended to indicate that there is a feature, number, step, operation, component, part, or combination thereof described in the specification, and one or more other features. It is to be understood that the present invention does not exclude the possibility of the presence or the addition of numbers, steps, operations, components, components, or a combination thereof.

Hereinafter, exemplary embodiments of the present invention will be described in detail with reference to the accompanying drawings.

1 is a packet structure in a general transport layer, Figure 2 is a packet structure in a transport layer according to an embodiment of the present invention.

Referring to FIG. 1, in the transport layer, a header 110 is attached to a front end of data 120 transferred from an application layer to form a packet 100. The header 110 includes information that ensures that the data 120 at the end of the packet 100 has not been changed while being transmitted, and can be recombined in its original form.

Since the header 110 is located in front of the data 120, the process of separating the header 110 must be preceded in connecting the data 120.

Referring to FIG. 2, in the embodiment of the present invention, the header 210 is attached to the rear end of the data 220 transmitted from the application layer in the transport layer to form the packet 200. The header 210 includes information to ensure that data 220 at the front end of the packet 200 has not been changed while being transmitted, and can be recombined in its original form.

Since the header 210 is located at a tail of the packet 200, the data 220 may be directly connected to other data without the process of separating the header 210 in connecting the data 220.

Information included in the header 210 will be described in detail with reference to FIGS. 3 and 4.

3 is information included in a header in the TCP protocol according to an embodiment of the present invention. The field names are shown, and the number and contents of each field are as follows.

SCR PORT is 16 bits and represents the port number of the sender.

DEST PORT is 16 bits and represents the destination port number.

A SEQ (Sequence Number) is 32 bits and is a sequence number indicating a unit of a data stream to be sent by the sender.

The acknowledgment number (ACK) is 32 bits and has a transmission sequence number that the other party should send the next time it receives it.

HLEN (Header Length) is 4 bits and represents the length of the TCP header.

Reserved is 6 bits and is a field reserved for later expansion.

Code Bit is 6 bits and it is called Contrl flag or control bit and it has 6 control values. If '1' is specified, it means the following. Looking at the field value from the left side, Urgent Flag (URG) means that data that needs to be urgently processed, and Acknowledgment Flag (ACK) uses response confirmation number. PSH (Push Flag) sends the data received by TCP to the upper layer application. RST (Reset Flag) means that if the communication is not recovered even if retransmission for some cause unilaterally disconnects the TCP virtual line. SYN (Synchronize Flag) is used to establish a virtual circuit. Initialize the sequence number to the send sequence number as it appears in this TCP header. And the FIN (Fin Flag) indicates that the data sent by the sender has ended. However, reception is still possible. In the case of normal termination, the requesting disconnection first informs the termination request to the TCP that specified the FIN. The receiving end terminates all processing by returning the TCP header that specifies the FIN.

Windows is 16 bits and tells you how much data can be received from the SEQ number shown in the ACK.

CheckSum is 16 bits, and the sender creates a TCP fake head, calculates a checksum, and puts it in this field. The receiver creates a fake head of the same type, calculates a checksum, and checks whether the data has been properly received.

Urgent Pointer is 16 bits and is treated as a pointer to data containing urgent data. The number of bytes that appear in this emergency pointer from the beginning of the data is processed as data that needs to be urgently processed.

Options are flexible and are used to adjust the details of the communication. It is rarely used and should be specified so that the total length is a multiple of 32 bits.

4 is information included in a header in the UDP protocol according to an embodiment of the present invention. The field names are shown, and the number and contents of each field are as follows.

SCR PORT is 16 bits and represents the port number of the sender.

DEST PORT is 16 bits and represents the destination port number.

LENGTH is 16 bits and is set in byte units plus the length of the UDP header and the length of the user data.

CheckSum is 16 bits, and the sender creates a UDP fake head, calculates a checksum and puts it in this field, and the receiver creates a fake head of the same type, calculates a checksum, and checks whether data has been properly received.

Hereinafter, a data transmission method and a reception method using the above-described packet structure will be described with reference to the drawings. The transmitting end is called a transmitting end and the receiving end is called a receiving end.

5 is a flowchart illustrating a data transmission method using a packet structure according to an embodiment of the present invention.

In step S300, the transmitting end divides data to be transmitted in packet units.

According to an embodiment, when the above-described packet structure is used in the transport layer, data to be transmitted is received from the application layer. Data received from the application layer is divided into packet units and later recombined at the receiving end.

In step S310, a packet is generated by adding a header to the rear end of the data divided into packet units. In other words, a packet having a structure as shown in FIG. 2 is generated.

In step S320, the generated packet is transmitted to the receiving end to which data is to be transmitted.

Here, each packet may be sequentially transmitted according to the classification order of the data so that the divided data are sequentially received at the receiver.

6 is a flowchart illustrating a data receiving method using a packet structure according to an embodiment of the present invention.

In step S400, the receiving end receives a packet. In the received packet, as shown in FIG. 2, data is located at the front end and the header is located at the rear end.

In step S410, the data of the currently received packet is recombined consecutively with the data of the previously received packet. In the packet structure as shown in FIG. 1, the header is positioned at the front of the packet, and a process of separating the header is required. However, in the exemplary embodiment of the present invention, the header is not located at the front of the packet and the data is located at the header. You can recombine data right away without separating it.

In step S420, while reading the recombined data, the header located at the rear of the packet is separated to check the header contents, and information about the data currently being read is obtained.

The receiving end regards consecutively received packets as valid packets and preferentially recombines the data in the packets without header confirmation. Then recombine the data and separate the headers to see the header contents.

Through this process, serial data recombination is possible because the header content is not checked and the header is not separated from the packet, and the time delay in recombining a plurality of separated data is reduced. have.

According to another embodiment of the present invention, the data to be transmitted from the transmitting end to the receiving end may be a multimedia data stream. In this case, the transmitting end divides and transmits the multimedia data stream in packet units, and the receiving end recombines data in the transmitted packets to reproduce the multimedia data stream.

Here, the header may include a header length field, a video / audio packet duration field, a video format information field, a video version field, an FPS field, a video bit rate field, an audio format information field, a sampling frequency field, and an audio bit rate field.

The header length field is a field indicating the total length of the header, and the multimedia packet duration field is a value determined according to a user's request or a characteristic of a network protocol and is used as a value for determining the size of a multimedia packet constituting a multimedia data part. . For example, if the user who creates a file determines that the multimedia packet unit is one second, video / audio data to be processed in one second is included. If there is no request from the user, the size of data to be transmitted in the network 1 packet is determined through the characteristics of the network protocol, and the size is converted into time to determine the multimedia packet duration field.

The video format information field is information about a video format of a multimedia data portion and is description information about a video format. The video version field contains the video processing player version. The FPS field indicates the number of video frames to be processed per second in Frame per second. The video bitrate field indicates the bit rate that occurs per second of the actual video stream.

The audio format information field is information about an audio format of a multimedia data portion and is description information about an audio format. The audio version field contains the audio processing player version. The sampling frequency field indicates the number of samples of audio frames to be processed per second. The audio bit rate field indicates the bit rate that occurs per second of the actual audio stream.

The multimedia packet may include a sequence number indicating the order of video / audio frames, a time stamp indicating the actual time at which the video / audio frame should be actually expressed, and information on the actual length of the video / audio data.

Here, the header is located at the rear of the multimedia packet, and the receiving end regards the packet as a valid packet for the continuously received multimedia packet and continuously reassembles and reproduces the multimedia data. The header is checked during playback to see if it is a valid packet.

7 is a diagram illustrating a time lapse upon reception of a general packet structure, and FIG. 8 is a diagram showing a time lapse upon reception of a packet structure according to an embodiment of the present invention.

Referring to Fig. 7, the time lapse upon receipt of a general packet structure is shown.

The first packet P1 is received at T0. After checking the first header H1, a predetermined operation (for example, real time playback in the case of multimedia data) is performed through the first data D1. In addition, the second packet P2 is received at the end T1 of performing the operation through the first data D1. The second header H2 is also checked with respect to the second packet P2 and then a predetermined operation is performed through the second data D2. That is, the second data D2 is continuously recombined after the first data D1. Thereafter, the third packet P3 is received at the time T2, and after confirming the third header H3 with respect to the third packet P3, a predetermined operation is performed through the third data D3. That is, the third data D3 is continuously recombined after the second data D2. According to this, there is a problem in that data cannot be continuously recombined as a process of receiving a packet and checking a header is preceded.

Referring to Fig. 8, a time lapse upon receipt of a packet structure in accordance with the present invention is shown.

The first packet P1 is received at T0. In the first packet P1, the first data D1 is positioned at the front end and the first header H1 is positioned at the rear end. That is, while performing a predetermined operation (eg, real time playback in the case of multimedia data) through the first data D1, the first header H1 at the rear end is checked. In addition, the second packet P2 is received at T11 after performing the operation through the first data D1. As the second data P2 is located at the front end of the second packet P2, the received second packet P2 performs an operation through the second data D2 immediately. While performing an operation through the second data D2, the second header H2 is checked to determine whether valid data is present. Then, the third packet P3 is received at T21 where the operation through the second data D2 is completed. The received third packet P3 performs an operation through the third data D3 as soon as the third data D3 is located at the front end. The third header H3 is checked while the third data D3 passes through the operation to determine valid data.

That is, since the header checking process is not preceded separately, the time delay as much as the header checking process is reduced, which is advantageous in terms of time when playing a multimedia data stream.

In addition, since the header verification process is not separately performed, the efficiency of recombining data is improved.

In addition, the above-mentioned data transmission method and reception method can be created by a computer program. Codes and code segments constituting the program can be easily inferred by a computer programmer in the art. In addition, the program is stored in a computer readable media, and read and executed by a computer to implement a method for providing a document search service. The information storage medium includes a magnetic recording medium, an optical recording medium, and a carrier wave medium.

Although the above has been described with reference to a preferred embodiment of the present invention, those skilled in the art to which the present invention pertains without departing from the spirit and scope of the present invention as set forth in the claims below It will be appreciated that modifications and variations can be made.

Claims (12)

In a method for transmitting data over a network, Separating, by the transmitter, data in packet units; Generating a packet including a header after the separated data; And Transmitting the packet to a receiving end. The method of claim 1, The transmitting of the packet to the receiving end may include transmitting the packet sequentially so that the separated data is sequentially received at the receiving end. The method of claim 1, And the data is part of a multimedia data stream. The method of claim 1, And the header includes information for recombining the separated data. The method of claim 1, Separating the data and generating the packet are performed in a transport layer. A recording medium in which a program of instructions that can be executed by a computer is tangibly implemented so that a method of transmitting data over a network is implemented, and which records a program that can be read by a computer, Separating, by the transmitter, data in packet units; Generating a packet including a header after the separated data; And And recording a program for implementing a data transmission method comprising the step of transmitting the packet to a receiving end. In a method for receiving data over a network, Receiving, by the receiving end, a packet transmitted from the transmitting end, wherein the packet includes data at the front end and a header at the rear end; Directly connecting the received packet to data of a previous packet; And And separating a header of the received packet. The method of claim 7, wherein The packet is a data reception method, characterized in that the transmission is sequentially transmitted from the transmitting end so that the data in the packet is sequentially recombined. The method of claim 7, wherein And the data is part of a multimedia data stream. The method of claim 7, wherein And the header includes information for recombining the separated data. The method of claim 7, wherein The step of concatenating the data and detaching the header is performed at a transport layer. A recording medium in which a program of instructions executable by a computer is tangibly implemented so that a method of receiving data via a network is implemented, and which records a program that can be read by a computer, Receiving, by the receiving end, a packet transmitted from the transmitting end, wherein the packet includes data at the front end and a header at the rear end; Directly connecting the received packet to data of a previous packet; And Recording a program for implementing a data receiving method, comprising: separating a header of the received packet.