WO2020122262A1

WO2020122262A1 - Non-tcp-based communication system and method for ship

Info

Publication number: WO2020122262A1
Application number: PCT/KR2018/015597
Authority: WO
Inventors: 고태훈; 이정호; 김용훈
Original assignee: (주)썬컴
Priority date: 2018-12-10
Filing date: 2018-12-10
Publication date: 2020-06-18

Abstract

The present invention relates to a system for performing a ship-to-shore communication on the basis of a Non-TCP. The present invention exhibits the following effect. That is, the present invention enables transmission or reception by VDES equipment, without a MAC header, a TCP header, and an IP header, in a ship-to-shore communication, and thus enables reducing not only the number of communications but also a data capacity.

Description

NON-TCP based ship communication system and method

The present invention relates to a system for non-TCP based communication between a ship and land.

In order to use the HTTP protocol, all headers of TCP/IP should be included as shown in FIG. 3. However, such a protocol configuration has difficulties in communication in the currently configured VDES resource, and since it is necessary to transmit a large amount of data, the speed is remarkably lowered and communication is virtually impossible.

The present invention seeks to solve the following problems.

That is, as shown in FIG. 4, a scheme for omitting some headers from communication between a ship and land is proposed by excluding the MAC header, TCP header, and IP header when transmitting/receiving from VDES equipment.

The present invention to solve the above problems,

A client 400 transmitting an HTTP request message to the ship gateway 300 and receiving an HTTP response message from the ship gateway 300; The HTTP request message received from the client 400 is processed into an MRN request message and transmitted to the land gateway 200, and the MRN response message received from the land gateway 200 is processed into an HTTP response message to be transmitted to the client 400 Said ship gateway 300; The MRN request message received from the ship gateway 300 is processed as an HTTP request message and transmitted to the server 100, and the HTTP response message received from the server 100 is processed as an MRN response message and transmitted to the ship gateway 300. An on-shore gateway 200; The server 100 includes an HTTP request message transmitted from the land gateway 200 and generates an HTTP response message to the land gateway 200 and transmits the HTTP request message to the land gateway 200. The HTTP request message includes HTTP headers and headers. Consisting of a body, the header further includes a destination MRN (dstMRN) and a sender MRN (srcMRN) in the MAC header, the TCP header, and the IP header, and the body includes a request message (req_msg), and the HTTP response message is HTTP-based. As data of, it is composed of a header and a body, the header further includes a destination MRN (dstMRN) in the MAC header, the TCP header, and the IP header, and the body includes a response message (res_msg), and the MRN request message is the destination MRN. It consists of (dstMRN), sender MRN (srcMRN), and request message (req_msg), wherein the MRN response message is composed of a destination MRN (dstMRN) and a response message (res_msg),

The ship gateway 300 deletes information other than the destination MRN (dstMRN) and the sender MRN (srcMRN) from the header of the HTTP request message to generate an MRN request message, and includes an MAC header, a TCP header, and an IP header in the MRN response message. It characterized in that it comprises a ship transfer server 310 to generate an HTTP response message by adding the header,

The ship gateway 300 divides the MRN request message received from the ship transfer server 310 into a destination MRN (dstMRN), a sender MRN (srcMRN), and a request message (req_msg). The VDES module of the land gateway 200 is divided into three times. A VDES module consisting of a ship transmitter 321 that transmits to 220 and a ship receiver 322 that transmits an MRN response message received from the VDES module 220 of the land gateway 200 to the ship transfer server 310. 320) further comprising,

The land gateway 200 deletes information other than the destination MRN (dstMRN) from the header of the HTTP response message to generate an MRN response message, and adds a header including a MAC header, a TCP header, and an IP header to the MRN request message to HTTP. It characterized in that it comprises an HTTP land transfer client 210 for generating a request message,

The land gateway 200 divides the MRN response message received from the land transfer client 210 into the destination MRN (dstMRN) and the response message (res_msg) and transmits the MRN response message to the VDES module 320 of the ship gateway 300 twice. Further comprising a VDES module 220 consisting of a land receiving unit 221 that transmits the MRN request message received from the land transmitting unit 222 and the VDES module 320 of the ship gateway 300 to the land transfer client 210 Non-TCP based marine communication system, or

The ship communication method using the ship communication system includes the steps of transmitting an HTTP request message from the client 400 to the ship gateway 300; When the HTTP request message is transmitted to the ship gateway 300, the ship transfer server 310 receives it and removes the MAC header, TCP header, and IP header, and only the destination MRN (dstMRN), sender MRN (srcMRN), and request message (req_msg) Generating a left MRN request message and transmitting it to the ship transmitter 321 of the VDES module 320; Dividing the MRN request message into the destination MRN (dstMRN), the sender MRN (srcMRN), and the request message (req_msg) in the ship transmitting unit 321 to the VDES module 220 of the land gateway 200 over three times; The VDES module land receiving unit 221 of the land gateway 200 receiving the MRN request message transmits it to the land transfer client 210; Generating an HTTP request message by adding a header including a MAC header, a TCP header, and an IP header to the MRN request message in the land transfer client 210 and transmitting it to the server 100; Transmitting an HTTP response message from the server 100 to the land gateway 200 in response to the HTTP request message; When the HTTP response message is transmitted to the land gateway 200, the land transfer client 210 receives it and removes the MAC header, the TCP header, and the IP header. After doing this, transmitting it to the land transmitter 222 of the VDES module 220; Dividing the MRN response message into the destination MRN (dstMRN) and the response message (res_msg) in the land transmitter 222 and transmitting the MRN response message to the VDES module 320 of the ship gateway 300 twice; The VDES module ship receiving unit 322 of the ship gateway 300 receiving the MRN response message transmits it to the ship transfer server 310; Generating a HTTP response message by adding a header including a MAC header, a TCP header, and an IP header to the MRN response message in the ship transfer server 310 and transmitting it to the client 400; We propose a non-TCP based ship communication method.

The present invention exerts the following effects.

That is, in the communication between the ship and the land, the transmission and reception by the VDES equipment excludes the MAC header, TCP header, and IP header to reduce the number of communication and reduce the data capacity.

1 is a view showing the overall configuration of the present invention.

2 is a view showing the configuration of each type of data (message) transmitted by the present invention.

3 is a table for MRN rules.

The best mode for carrying out the present invention is as follows.

That is, the client 400 transmits an HTTP request message to the ship gateway 300 and receives an HTTP response message from the ship gateway 300; The HTTP request message received from the client 400 is processed into an MRN request message and transmitted to the land gateway 200, and the MRN response message received from the land gateway 200 is processed into an HTTP response message to be transmitted to the client 400 Said ship gateway 300; The MRN request message received from the ship gateway 300 is processed as an HTTP request message and transmitted to the server 100, and the HTTP response message received from the server 100 is processed as an MRN response message and transmitted to the ship gateway 300. An on-shore gateway 200; The server 100 includes an HTTP request message transmitted from the land gateway 200 and generates an HTTP response message to the land gateway 200 and transmits the HTTP request message to the land gateway 200. The HTTP request message includes HTTP headers and headers. Consisting of a body, the header further includes a destination MRN (dstMRN) and a sender MRN (srcMRN) in the MAC header, the TCP header, and the IP header, and the body includes a request message (req_msg), and the HTTP response message is HTTP-based. As data of, it is composed of a header and a body, the header further includes a destination MRN (dstMRN) in the MAC header, the TCP header, and the IP header, and the body includes a response message (res_msg), and the MRN request message is the destination MRN. It consists of (dstMRN), sender MRN (srcMRN), and request message (req_msg), wherein the MRN response message is composed of a destination MRN (dstMRN) and a response message (res_msg),

The land gateway 200 divides the MRN response message received from the land transfer client 210 into the destination MRN (dstMRN) and the response message (res_msg) and transmits the MRN response message to the VDES module 320 of the ship gateway 300 twice. Further comprising a VDES module 220 consisting of a land receiving unit 221 that transmits the MRN request message received from the land transmitting unit 222 and the VDES module 320 of the ship gateway 300 to the land transfer client 210 It is characterized by.

Hereinafter, preferred embodiments of the present invention will be described with reference to the accompanying drawings. However, the scope of the present invention should be grasped by describing the claims. Also, descriptions of well-known technologies that obscure the subject matter of the present invention will be omitted.

The non-TCP based ship communication system of the present invention is composed of a server 100, a land gateway 200, a ship gateway 300, and a client 400 as shown in FIG. At this time, the server 100 and the land gateway 200 are components installed on the land, and the ship gateway 300 and the client 400 are components installed on the ship.

The land gateway 200 and the ship gateway 300 are connected by VDES (VHF Data Exchange System) communication, and the server 100 and the land gateway 200, the ship gateway 300 and the client 400 are based on TCP/IP. It is assumed that communication is performed by HTTP protocol.

Normal communication uses layer 7 to layer 4, and the data used here is large, and in the case of TCP/IP, it is difficult to accommodate at a rate of 28 Kbps to 56 bps, such as VHF, by sending and receiving multiple communication due to the nature of communication.

In order to solve this, the present invention proposes a configuration capable of reducing the number of times of communication and simultaneously reducing the data capacity. (For TCP/IP, at least three times for communication once based on 3 wayhandshaking) Sending and receiving is required, but in the present invention, communication is performed with one sending and receiving).

When each message type mentioned in the present invention is first described with reference to FIG. 2, the HTTP request message (①, ⑤) is HTTP-based data and is composed of a header and a body, and the header is a MAC header, a TCP header, and an IP header. It further includes a destination MRN (dstMRN) and a sender MRN (srcMRN), and the body includes a request message (req_msg).

The HTTP response message (⑥, ⑩) is HTTP-based data and is composed of a header and a body, and the header further includes a destination MRN (dstMRN) in the MAC header, TCP header, and IP header, and the body includes a response message (res_msg). Includes.

The MRN request message is composed of a destination MRN (dstMRN), a sender MRN (srcMRN), and a request message (req_msg). The MRN response message is composed of a destination MRN (dstMRN) and a response message (res_msg).

Maritime Resource Name (MRN) is a maritime resource identification number, a number system for managing marine facilities (ships, equipment, objects, etc.) or sailors (captains, etc.), and is used in a similar concept to the resident registration number. You can check the MRN rules.

The client 400 serves to transmit the HTTP request message to the ship gateway 300 and to receive the HTTP response message from the ship gateway 300, and the server 100 receives the HTTP request message from the land gateway 200. It creates an HTTP response message for this and transmits it to the land gateway 200.

The ship gateway 300 processes the HTTP request message received from the client 400 into an MRN request message and transmits it to the land gateway 200, and processes the MRN response message received from the land gateway 200 into an HTTP response message. It serves to transmit to the client 400, and is composed of a ship transfer server 310 and a VDES module 320.

The ship transfer server 310 deletes information other than the destination MRN (dstMRN) and the sender MRN (srcMRN) from the header of the HTTP request message, generates an MRN request message, transmits it to the VDES module 320, and sends the MAC to the MRN response message. An HTTP response message is generated by adding a header including a header, a TCP header, and an IP header, and transmitted to the client 400. At this time, the MAC header and the TCP header are determined according to the standard, and the IP header is retrieved from the lookup table previously stored in the ship transfer server 310 and the land transfer client 210.

The look-up table is given an ID matching a specific IP, and when the IP header is deleted from the MRN request message in the ship transfer server 310, the ID matching the corresponding IP is called from the look-up table and the MRN response message When adding the ID information to the MRN and adding the IP header to the MRN response message, the ID information is retrieved from the MRN response message, the matching IP is retrieved from the lookup table, and then added to the MRN response message.

When the IP header is added to the MRN request message in the land transfer client 210, which will be described later, the ID information is retrieved from the corresponding MRN request message, the matching IP is retrieved from the lookup table, and then added to the MRN request message. When deleting an IP header from a message, the ID matching the corresponding IP is retrieved from the lookup table and ID information is added to the MRN request message.

The VDES module 320 is composed of a ship transmitter 321 and a ship receiver 322, and the ship transmitter 321 receives an MRN request message received from the ship transfer server 310 as a destination MRN (dstMRN) and a sender MRN (srcMRN). ), divided into a request message (req_msg) and transmitted to the VDES module 220 of the land gateway 200 three times, and the ship receiving unit 322 receives the MRN response message received from the VDES module 220 of the land gateway 200 Is transmitted to the ship transfer server 310.

The land gateway 200 processes the MRN request message received from the ship gateway 300 into an HTTP request message, transmits it to the server 100, and processes the HTTP response message received from the server 100 into an MRN response message to ship. It serves to transmit to the gateway 300, and is composed of a land transfer client 210 and a VDES module 220.

The land transfer client 210 deletes information other than the destination MRN (dstMRN) from the header of the HTTP response message, generates an MRN response message, transmits it to the VDES module 220, and sends the MAC header, TCP header, IP to the MRN request message. Adds a header including a header to generate an HTTP request message and transmits it to the server 100. When sending a message from the server 100 to the client 400, the sender MRN is not necessary, and only the destination MRN needs to be known, so the sender MRN is also deleted to minimize the amount of data. In addition, it is possible to increase the transmission speed by minimizing the number of times when data is transmitted from the land transmission unit 222.

The VDES module 220 is composed of a terrestrial receiver 221 and a terrestrial transmitter 222, and the terrestrial transmitter 222 receives an MRN response message received from the terrestrial transfer client 210 as a destination MRN (dstMRN) and a response message (res_msg). ) To transmit to the VDES module 320 of the ship gateway 300 twice, and the land receiver 221 receives the MRN request message received from the VDES module 320 of the ship gateway 300. ).

The process of communication between the client 400 of the ship and the server 100 of the land by the present invention based on the above configuration will be described as follows.

First, the client 400 transmits an HTTP request message to the ship gateway 300. At this time, the HTTP request message includes a header including a destination MRN (dstMRN) and a sender MRN (srcMRN) in the MAC header, the TCP header, and the IP header. And a body including a request message (req_msg).

When the HTTP request message is transmitted to the ship gateway 300, the ship transfer server 310 receives it and removes the MAC header, TCP header, and IP header, and only the destination MRN (dstMRN), sender MRN (srcMRN), and request message (req_msg) After creating the left MRN request message, it is transmitted to the ship transmitter 321 of the VDES module 320.

The ship transmission unit 321 divides the MRN request message into a destination MRN (dstMRN), a sender MRN (srcMRN), and a request message (req_msg) and transmits it to the VDES module 220 of the land gateway 200 over three times.

The VDES module land receiving unit 221 of the land gateway 200 that received the MRN request message transmits it to the land transfer client 210, and the land transfer client 210 sends the MAC header, the TCP header, and the IP header to the MRN request message. An HTTP request message is generated by adding a header including a message, and transmitted to the server 100.

In response to this, the server 100 transmits an HTTP response message to the land gateway 200, wherein the HTTP response message includes a header including a destination MRN (dstMRN) in the MAC header, TCP header, and IP header, and the response. It consists of a body containing a message (res_msg).

When the HTTP response message is transmitted to the land gateway 200, the land transfer client 210 receives it and removes the MAC header, the TCP header, and the IP header, leaving only the destination MRN (dstMRN) and response message (res_msg) to generate the MRN response message. After that, it is transmitted to the land transmitter 222 of the VDES module 220.

The land transmitter 222 divides the MRN response message into the destination MRN (dstMRN) and the response message (res_msg) and transmits the MRN response message to the VDES module 320 of the ship gateway 300 twice.

The VDES module ship receiving unit 322 of the ship gateway 300 that received the MRN response message transmits it to the ship transfer server 310, and the MAC header, TCP header, IP header to the MRN response message from the ship transfer server 310 An HTTP response message is generated by adding a header including a and transmits it to the client 400.

The present invention described above is not limited by the above-described embodiments and the accompanying drawings, and various substitutions, modifications and changes can be made without departing from the technical spirit of the present invention. It will be clear to those who have knowledge.

Claims

A client 400 transmitting an HTTP request message to the ship gateway 300 and receiving an HTTP response message from the ship gateway 300;

The HTTP request message received from the client 400 is processed into an MRN request message and transmitted to the land gateway 200, and the MRN response message received from the land gateway 200 is processed into an HTTP response message to be transmitted to the client 400 Said ship gateway 300;

The MRN request message received from the ship gateway 300 is processed as an HTTP request message and transmitted to the server 100, and the HTTP response message received from the server 100 is processed as an MRN response message and transmitted to the ship gateway 300. An on-shore gateway 200;

It includes; a server 100 that receives an HTTP request message from the land gateway 200 and generates an HTTP response message to the land gateway 200 and transmits it to the land gateway 200.

The HTTP request message is HTTP-based data,

It consists of a header and body,

The header further includes a destination MRN (dstMRN) and a sender MRN (srcMRN) in the MAC header, TCP header, and IP header.

The body contains a request message (req_msg),

The HTTP response message is HTTP-based data,

It consists of a header and body,

The header further includes a destination MRN (dstMRN) in the MAC header, TCP header, and IP header,

The body includes a response message (res_msg),

The MRN request message

It consists of destination MRN (dstMRN), sender MRN (srcMRN), and request message (req_msg).

The MRN response message

It consists of destination MRN (dstMRN) and response message (res_msg).

Non-TCP based ship communication system.
According to claim 1,

The ship gateway 300 is

In the header of the HTTP request message, information other than the destination MRN (dstMRN) and sender MRN (srcMRN) is deleted to generate an MRN request message, and an HTTP response is added to the MRN response message by adding a header including a MAC header, a TCP header, and an IP header. Characterized in that it comprises a ship transfer server 310 for generating a message

Non-TCP based ship communication system.
According to claim 2,

The ship gateway 300 is

The ship sends the MRN request message received from the ship transfer server 310 to the destination MRN (dstMRN), the sender MRN (srcMRN), and the request message (req_msg) to the VDES module 220 of the land gateway 200 over three times. Further comprising a VDES module 320 consisting of a transmitter 321 and a ship receiving unit 322 that transmits the MRN response message received from the VDES module 220 of the land gateway 200 to the ship transfer server 310. Characterized by

Non-TCP based ship communication system.
The method according to claim 2 or 3,

The land gateway 200 is

Creates an MRN response message by deleting information other than the destination MRN (dstMRN) from the header of the HTTP response message, and adds a header including a MAC header, a TCP header, and an IP header to the MRN request message to generate an HTTP request message. Characterized in that it comprises a transfer client 210

Non-TCP based ship communication system.
The method of claim 4,

The land gateway 200 is

The MRN response message received from the land transfer client 210 is divided into the destination MRN (dstMRN) and the response message (res_msg), and the land transmitter 222 and the ship are transmitted twice to the VDES module 320 of the ship gateway 300. Characterized in that it further comprises a VDES module (220) consisting of a land receiving unit (221) for transmitting the MRN request message received from the VDES module (320) of the gateway (300) to the land transfer client (210).

Non-TCP based ship communication system.
The ship communication method using the ship communication system of claim 5 is

Transmitting an HTTP request message from the client 400 to the ship gateway 300;

When the HTTP request message is transmitted to the ship gateway 300, the ship transfer server 310 receives it and removes the MAC header, TCP header, and IP header, and only the destination MRN (dstMRN), sender MRN (srcMRN), and request message (req_msg) Generating a left MRN request message and transmitting it to the ship transmitter 321 of the VDES module 320;

Dividing the MRN request message into the destination MRN (dstMRN), the sender MRN (srcMRN), and the request message (req_msg) in the ship transmitting unit 321 to the VDES module 220 of the land gateway 200 over three times;

The VDES module land receiving unit 221 of the land gateway 200 receiving the MRN request message transmits it to the land transfer client 210;

Generating an HTTP request message by adding a header including a MAC header, a TCP header, and an IP header to the MRN request message in the land transfer client 210 and transmitting it to the server 100;

Transmitting an HTTP response message from the server 100 to the land gateway 200 in response to the HTTP request message;

When the HTTP response message is transmitted to the land gateway 200, the land transfer client 210 receives it and removes the MAC header, the TCP header, and the IP header. After doing this, transmitting it to the land transmitter 222 of the VDES module 220;

Dividing the MRN response message into the destination MRN (dstMRN) and the response message (res_msg) in the land transmitter 222 and transmitting the MRN response message to the VDES module 320 of the ship gateway 300 twice;

The VDES module ship receiving unit 322 of the ship gateway 300 receiving the MRN response message transmits it to the ship transfer server 310;

Generating a HTTP response message by adding a header including a MAC header, a TCP header, and an IP header to the MRN response message in the ship transfer server 310 and transmitting it to the client 400;

Non-TCP based ship communication method.