JP5132252B2 - Mobile communication device and mobile communication method - Google Patents

Description

  The present invention relates to a mobile communication device and a mobile communication method for transmitting and receiving data between a mobile object and a communication target via a center connected to the Internet, and in particular, a transfer terminal between the mobile object and the center. The present invention relates to a mobile communication device and a mobile communication method via the network.

  Communication such as the Internet or music download in a mobile body is determined by using roaming technology that enables continuous communication, technology using a plurality of terminals such as mobile phones and wireless LAN terminals, and movement information and travel information. Therefore, techniques for performing stable communication, such as techniques for performing stable switching, have been developed.

In the case of the prior art, it is possible to cope with a train that moves at a high speed but has a constant destination, or a person who moves unpredictably but has a low speed. However, since the vehicle moves at a high speed and does not always designate the destination, the destination may not be predicted. For this reason, there is no guarantee that sufficient communication can be performed in the vehicle. This is due to the narrow effective range of currently used communication terminals.
Further, as a method for vehicle communication, a TCP (Transmission Control Protocol) protocol method or a UDP (User Datagram Protocol) protocol method is known (for example, Patent Document 1).

Japanese Patent Laid-Open No. 2002-32276

  A communication method using the TCP protocol method will be briefly described with reference to FIG. Next, the connected side (for example, the communication target) sends a SYN-ACK packet 102 in which an ACK packet indicating connection permission and a SYN packet of a connection request are combined. Finally, the ACK packet 103 is also sent from the vehicle side, and the connection is established. Thereafter, data 104 is transmitted and received. The procedure for establishing the connection in this way is generally called negotiation, but in the TCP protocol method, since a packet is transmitted and received three times, it is called a three-way handshake.

  Next, problems when a vehicle as a mobile body communicates via an access point (AP) will be described with reference to FIG. Here, it is assumed that all communication between the vehicle and the AP, between the AP and the center, and between the center and the communication target is performed by the TCP protocol method, and focuses on the communication between the vehicle and the AP. Consider narrowing down.

  First, a vehicle in the AP network area 100 transmits a SYN packet to AP2. Next, the AP that has received the SYN packet transmits a SYN-ACK packet to the moving vehicle 1. Even if the vehicle 1 is moving, if it is within the AP network range 100, this SYN-ACK packet can be received. However, if the vehicle 1 moves further and goes out of the range of the AP2, even if the vehicle 1 transmits an ACK packet, the AP2 cannot receive and cannot establish a connection by the TCP protocol method. There was a problem.

  Next, problems when communication is performed using the UDP protocol instead of the TCP protocol will be described. FIG. 3 shows an overview of the UDP protocol method. Here, a case is considered in which all communication between the vehicle and the communication GW, between the communication GW and the center, and between the center and the communication target is performed by the UDP protocol method. Unlike the TCP protocol method, the UDP protocol method performs communication without establishing a connection (no negotiation). Therefore, when the vehicle requests data transmission to the communication target, even if the server connected to the communication target is down, the vehicle cannot confirm it and cannot know where the communication is interrupted.

As described above, there is a problem in both cases where the communication between the vehicle and the communication target is all performed by the TCP protocol method and all the communication is performed by the UDP protocol method.
An object of the present invention is to realize a mobile communication method that solves these problems.

  The mobile communication method of the present invention is a mobile communication method for performing communication between a mobile body and a communication gateway, and performing communication between the communication gateway and a center connected to a communication target of the mobile body. The mobile transmits a request data to a specific communication gateway in a manner that does not establish a connection; and the communication gateway receives the request data, and connects the received request data to the request data. Transmitting to the center in an established manner; transmitting the request data received by the center to the communication target; transmitting the response data to the center by the communication target; Transmitting the received response data to the communication gateway; and the communication gateway receiving the received response data. Transmitting to the mobile at not establish system connection, said moving body, characterized in that a step of receiving the response data.

  Further, the mobile communication device of the present invention is a mobile communication device that communicates with a communication gateway, wherein data transmission means for transmitting request data in a manner that does not establish a connection, and response data in response to the transmitted request data Response data receiving means for receiving the message in a method that does not establish a connection, and completion notification data transmitting means for transmitting completion notification data for the response data in a method that does not establish a connection.

  According to the mobile communication method of the present invention, the mobile body communicates with the UDP protocol system that does not establish a connection between the mobile body and the communication gateway, and communicates with the TCP protocol system that establishes the other connection. Even when moving at high speed, reliable communication is possible, and as a result, more efficient communication can be performed.

  Further, by using a unique packet, communication in different network networks can be performed.

  Furthermore, since a communication line is formed in advance between the communication gateway and the center, a request from the vehicle can be transferred more quickly.

  Hereinafter, a mobile communication device and a mobile communication method according to the present invention will be described with reference to the drawings. However, it should be noted that the technical scope of the present invention is not limited to these embodiments, but extends to the invention described in the claims and equivalents thereof.

  In the mobile communication method of the present invention, as shown in FIG. 4, first, a server 4 is connected via a center 3 in which a vehicle 1 is connected to a communication gateway (hereinafter referred to as “communication GW”) 2 and an Internet network 20. Data is transmitted to the communication target at Here, it is assumed that the vehicle 1 exists in the communication area of one communication GW. The vehicle 1 transmits data to a specific communication GW using UDP packet data (hereinafter referred to as “UDP packet”) by the UDP protocol method. The communication GW 2 transmits data to the center 3, and the center transmits data to a communication target that is a transmission destination that the vehicle originally wants to transmit. A series of processes for transmitting data requesting transmission to a communication target (request data) from the vehicle 1 to the communication target in this way is referred to as “request transmission processing”.

  Response data for notifying that the communication target has received data or for returning a response to the vehicle 1 to which the communication target has transmitted data is first transmitted to the center 3 via the server 4, and then The signal is transmitted from the center 3 to the communication GW 2 and transmitted from the communication GW 2 to the vehicle 1. This series of processing is called “response reception processing”.

  Furthermore, it is necessary to notify the communication GW 2 that the vehicle 1 has received the response data. This is because the communication between the vehicle and the communication GW uses the UDP protocol method and does not negotiate. In order to notify that the vehicle 1 has received the response data, data for reception completion notification is transmitted. This series of procedures is called “reception completion notification”.

  First, a configuration of a vehicle as an example of a mobile body that transmits and receives data and a mobile communication method according to the present invention will be described with reference to FIG. The vehicle 1 includes a communication device 11 and a navigation device 12 that can perform wireless communication. The communication device 11 includes a control unit 13 connected to the navigation device 12, a storage unit 14 that stores data (for example, a vehicle unique ID 18), and a wireless communication terminal 17 connected to the antenna 10 for performing wireless communication. Have. Furthermore, the communication device 11 includes an input unit 15 for inputting data. The control unit 13 includes request packet data generation means 19 for generating request packet data, which will be described later, and completion notification packet data generation means 20 for generating completion notification packet data. The navigation device 12 includes an output device (for example, a display) 16 for outputting display data and the like. The output device 16 displays image data, audio data, and the like based on output data from the control unit 13 of the communication device 11. I do. The output device 16 may be integrated with the navigation device 12 as shown in FIG. 6, or may be separated from the navigation device. Furthermore, in the present embodiment, the configuration in which the communication device 11 and the navigation device 12 are separated is illustrated, but the communication device 11 and the navigation device 12 may be integrated. Further, a car stereo or the like capable of communication can be used instead of the navigation device. Furthermore, the mobile communication system for realizing the mobile communication method according to the present invention is installed in the communication network GW2 functioning as a vehicle-specific access point having a function of relaying and connecting the vehicle 1 and the Internet network 200, and the Internet network 200. The center facility 3 is configured to enable communication specialized for vehicles.

Here, when the vehicle communicates with a specific target (communication target) of the Internet network, the vehicle 1 transmits data to the communication GW2, the communication GW2 transfers the data to the center 3, and the center 3 transmits data from the communication target. Obtaining and returning a response to the communication GW 2, the communication GW 2 performs communication by returning the response to the vehicle 1.
In the present invention, as shown in FIG. 6, communication is performed between the vehicle 1 and the communication GW 2 using a UDP packet according to the UDP protocol method, between the communication GW 2 and the center 3, and between the center 3 and the communication object 4. Is characterized in that communication is performed using TCP packets by the TCP protocol method.

<Request transmission process>
Next, the request transmission process will be described with reference to the drawings. FIGS. 7A to 7C illustrate an outline of a series of data communication embodiments in which data is transferred from the vehicle to the communication GW to the center to the communication target, and FIG. 7A illustrates transmission of request data from the vehicle 1 to the communication GW2. 7B shows an outline of request data transmission from the communication GW 2 to the center 3, and FIG. 7C shows an outline of request data transmission from the center 3 to the communication target 4. Table 1 shows the communication path, transmission destination, transmission source, header, and data part of the request data in the request transmission process.

(Vehicle communication processing flow)
First, the communication processing flow of the vehicle will be described using the flowchart of FIG. The communication processing flow is started in S101 of FIG. 8, and the vehicle communication device 11 (see FIG. 5) is activated in S102. Next, in step S103, request packet data is generated in the request packet data generation unit 19 (see FIG. 5) of the vehicle. As shown in FIG. 7A, the request packet data 31 uses a UDP packet according to the UDP protocol method, and includes a transmission destination IP, a transmission source IP, a UDP header, and a data part. Here, the transmission source IP is a mobile IP, that is, a vehicle IP, and the transmission destination IP is a specific communication GWIP. Further, the data part includes a mobile unit unique ID, that is, a vehicle unique ID, a transmission destination IP (IP to be communicated) to be originally transmitted, and request data. Here, as shown in FIG. 5, the vehicle unique ID 18 is stored in the storage unit 14.

  Next, in S104, it is determined whether or not the vehicle is within the communication GW range. If the vehicle is within the communication range, the wireless communication terminal 17 (see FIG. 5) mounted on the communication device 11 of the vehicle 1 is used in S105. UDP packet data including request data is transmitted, and request packet UDP transmission is performed. Since the vehicle receives response data for confirming that the communication target has received data from the wireless communication terminal 17 (see FIG. 5), the vehicle enters a response waiting state in S106.

(Communication GW processing flow)
Next, the processing flow of the communication GW that has received data from the vehicle as described above will be described. In the communication GW, processing for receiving data from the vehicle and processing for transmitting the received data to the center are performed. A flowchart of the processing flow of the communication GW is shown in FIGS. 9A and 9B. First, the communication GW is activated in S201, and a negotiation process (3-way handshake) to the center is performed in S202.

  Here, the negotiation process to the center in the communication GW will be described in detail. FIG. 10 explains the outline of the negotiation process (3-way handshake) between the communication GW and the center. The communication GW 2 receives a UDP packet from a vehicle that is a moving body, but when it is transferred to the center 3, the communication GW 2 converts it into a TCP packet and transmits it by the TCP protocol method. Therefore, the communication GW 2 always performs a negotiation process with the center 3. Specifically, as shown in FIG. 10, a SYN packet 71 indicating a connection request is first sent from the communication GW 2 to the center. Next, the center sends a SYN-ACK packet 72, which is a combination of an ACK packet indicating connection permission and a SYN packet for connection request, to the communication GW. Finally, the ACK packet 73 is also sent from the communication GW side, and the connection is established. Thereafter, request data 74 is transmitted. In the present invention, the communication GW always establishes a communication connection state by transmitting / receiving a SYN / SYN-ACK / ACK packet 75 between the communication GW 2 and the center 3, so that the mobile GW 2 The request data 76 can be transferred faster.

  Next, as shown in FIG. 9A, it is determined whether or not data is received from the vehicle in S203, and when data is received from the vehicle, in S204, “vehicle unique ID” and “sender” IP ”is acquired. Here, the source IP is a vehicle IP as shown in FIG. 7A. The vehicle unique ID and the vehicle IP that is the transmission source IP are used in response data transmission processing to be described later.

  Next, as shown in FIG. 9A, in S205, it is determined whether or not the same unique ID exists in the retained data. Here, assuming that data transmitted by the same vehicle having a specific unique ID is received a plurality of times, it is determined whether the data is received first or after the second time. If it is received for the first time, since there is no same unique ID in the retained data, the process proceeds to S208. In S208, the “counter” is set to 1 and is held together with “unique ID” and “source IP”. As will be described later, the counter is used to check whether or not the number of request data matches the number of completion notification data.

  If the same vehicle receives data transmitted after the second time, the same unique ID is present in the retained data in S205, and the process proceeds to S206. In S206, the same unique ID and source IP are held, and 1 is added to the held “counter”. Thereby, even when a plurality of request data is received from the same vehicle, the number of request data to be answered can be grasped.

  Next, as shown in FIG. 9A, in S207, the received "data" (unique ID, communication target IP, request data) is transferred to the center. As the data to be transferred, a TCP packet 32 is used as shown in FIG. 9B. The TCP packet 32 includes a transmission destination IP, a transmission source IP, a TCP header, and a data part. Here, the transmission destination is fixed at the center IP. The source IP is a communication GW. The data part is the same as the UDP packet received from the vehicle 1 by the communication GW 2 and includes a vehicle unique ID, a destination IP to be originally transmitted, and request data, as shown in FIG. 7B.

(Center processing flow)
Next, the processing flow of the center that receives data from the communication GW will be described. The center performs a process of receiving request data from the communication GW and a process of transmitting the request data received to the communication target to the communication target.

FIG. 11 shows a flowchart of the center processing flow. First, in S301, the center is activated, and in S302, it is determined whether data is received from the communication GW. Here, since data is received from the communication GW, the process proceeds to S303. In S303, “vehicle unique ID” and “source IP” are acquired from the received data and stored. The source IP is the IP of the communication GW and is used when responding.
Next, in S304, the “communication target” IP in the received data is set as the transmission destination IP, and the request data is transmitted. The data is TCP packet data 33 as shown in FIG. 7C, and is composed of a transmission destination (communication target) IP to be originally transmitted, a transmission source IP (center IP), a TCP header, and request data. As a result, the data requested by the vehicle for data transmission is transmitted to a desired communication target.

  Table 1 shows request data transmitted and received between the terminals in the above request transmission processing.

表１において、＊を付した車両ＩＰと車両固有ＩＤは通信ＧＷにて保有し、＊＊を付した通信ＧＷＩＰと車両固有ＩＤはセンタにて保有し、それぞれ後述する応答データ送信時に利用される。

In Table 1, the vehicle IP marked with * and the vehicle unique ID are held in the communication GW, and the communication GWIP marked with ** and the vehicle unique ID are held in the center, and are respectively used when sending response data to be described later. .

<Response reception process>
Next, data processing when response reception processing is performed will be described. 12A to 12C show a series of processes in which the communication target receiving the data transmits response data from the communication target → center → communication GW → vehicle. FIG. 12A shows response data transmission from the communication target 4 to the center 3. FIG. 12B shows an outline of response data transmission from the center 3 to the communication GW 2, and FIG. 12C shows an outline of transmission / reception of response data and completion notification data between the vehicle 1 and the communication GW 2. Table 2 shows the communication path, transmission destination, transmission source, header, and data part of the response data in the response reception process. The data processing procedure in the center and communication GW will be described using a flowchart.

(Response processing at the center)
FIG. 11 shows a flowchart of the processing flow in the center. In S305, it is determined whether or not response data is received from the communication target. If response data is received, the process proceeds to S306. In S306, the transmission source IP (IP of the communication GW) that is held is set as the transmission destination, and the “vehicle unique ID” and “response data” are added and transmitted.

  The procedure for searching for the destination IP will be described with reference to Table 2.

即ち、表１に示すように、センタは上述したように通信ＧＷから要求データを受信した際に、車両固有ＩＤと通信ＧＷＩＰとを保有しており、表２の１行目に示すように、センタが通信対象から受信した車両固有ＩＤから通信ＧＷＩＰを検索し、これを送信先ＩＰとする。
なお、応答データは、図１２Ａに示すように、ＴＣＰパケットデータ４１であり、送信先ＩＰ（センタＩＰ）、送信元ＩＰ、ＴＣＰヘッダ、応答データからなる。

That is, as shown in Table 1, when the center receives the request data from the communication GW as described above, it holds the vehicle unique ID and the communication GWIP. As shown in the first row of Table 2, The center searches the communication GWIP from the vehicle unique ID received from the communication target, and sets this as the transmission destination IP.
As shown in FIG. 12A, the response data is TCP packet data 41, and includes a transmission destination IP (center IP), a transmission source IP, a TCP header, and response data.

(Response reception processing in communication GW)
Since the communication GW receives the response data from the center, the processing flow starts from S209 in FIG. 9A. When the communication GW receives the response data from the center, the process proceeds to S210, where the “vehicle unique ID” is acquired from the data and compared with the stored data. Next, as shown in FIG. 9B, in S211, it is determined whether or not the received unique ID is the same as the received unique ID. If it is held, in S212, the corresponding transmission source IP (vehicle IP) is set as the transmission destination, and the response data in the reception data is transmitted to the vehicle. If not, the received data is discarded in S213.

That is, as shown in FIG. 12C, the communication GW 2 searches the correspondence table between the vehicle unique ID and the transmission source IP already held by the communication GW from the received vehicle unique ID, and retrieves the response destination vehicle from the unique ID. To do.
That is, as shown in Table 1, when the communication GW receives the request data from the vehicle as described above, it holds the vehicle unique ID and the vehicle IP, and as shown in the second row of Table 2, The communication GW searches the communication GWIP from the vehicle unique ID received from the center, and sets this as the transmission destination IP.
As shown in FIG. 12C, the vehicle IP found in the search is set as the destination IP, the source IP, the UDP header, and the response data are added to form the UDP packet data 43, and the communication GW transmits the data to the vehicle. If the received unique ID is not held, it is determined that the vehicle has already moved out of the range of the communication GW, and thus the received data is discarded in S213 as described above.

(Response reception processing flow in the vehicle)
Next, response data reception processing in the vehicle will be described. FIG. 13 is a flowchart showing a communication processing flow in the vehicle. The vehicle is normally waiting for a response in S401, and whether or not the vehicle has received a response is determined in S402, and the response is made by the wireless communication terminal 17 (see FIG. 5) installed in the communication device 11 of the vehicle 1. In step S407, the completion notification packet data created by the completion notification packet data generation unit 20 (see FIG. 5) is transmitted, and the reception of the response data is completed.

  However, when no response is received, the process proceeds to S405, and it is determined whether or not a predetermined time has elapsed. If a response has not been received even after a predetermined time has elapsed, the process proceeds to S406, and the request packet is retransmitted. This is because the response data is not received even after a certain period of time, and it is considered that the communication target has not received the request data transmitted by the vehicle to the communication target. After retransmitting the request packet, the process again waits for a response in S407.

<Completion notification process>
When the vehicle receives the response data, it is necessary to notify the communication GW of the result and notify that the response processing is completed. This is because the connection between the vehicle and the communication GW is not established because the communication is performed by the UDP protocol method. Therefore, when the response data is received, the vehicle transmits a completion notification to the communication GW. Here, the completion notification process will be described. Table 3 shows the communication path, transmission destination, transmission source, header, and data portion of completion notification data in completion notification communication.

(Vehicle completion notification process)
In the flowchart illustrating the communication processing flow in the vehicle illustrated in FIG. 13, when the vehicle receives a response, the vehicle is directed to the communication GW by the completion notification packet data generation unit 20 in the communication device 11 of the vehicle 1 in S407. Completion notification data is generated, and a completion notification packet is transmitted by the wireless communication terminal 17 (see FIG. 5). As shown in the lower part of FIG. 12C, the completion notification data is a UDP packet 51, and includes a transmission destination IP, a transmission source IP, a UDP header, and a vehicle unique ID. As shown in FIG. 5, the vehicle unique ID 18 is held in the storage unit 14 in the vehicle communication device 11. By sending the completion notification data by the UDP protocol method, it is not necessary to establish a connection as in the TCP protocol method, so that even when the vehicle is moving, it can be transmitted to the communication GW in a short time.

(Completion notification process in communication GW)
Processing when the communication GW receives completion notification data from the vehicle will be described. Whether or not the communication GW has received the completion notification is determined in S214 in the communication GW processing flow shown in FIG. 9B. When the communication GW receives the completion notification, the process proceeds to S215, and the value of the “counter” held together with the transmitted unique ID is decremented by 1, and if the value is 0, the holding is discarded.
That is, as shown in Table 1, when the communication GW receives the request data from the vehicle as described above, the communication GW has the vehicle unique ID and the vehicle IP. The number of vehicle unique IDs received from is counted.

ここでカウンタは、車両から通信対象に向けて送信された要求データの数を通信ＧＷがカウントするものであり、例えばｎ個の要求データが送信されていれば、カウンタの値はｎとなっている。車両が応答データを受信し、通信ＧＷに対して完了通知がなされた場合、完了通知のたびにカウンタを１ずつ減算することにより、車両が通信対象に対して送信した要求データに対して、完了通知がなされたか否かが確認できる。例えば、上記の例で、ｎ個の完了通知データを受信した場合、カウンタの値は０となり、全ての要求データに対して、完了通知がなされたこととなる。この場合、車両固有ＩＤと送信元ＩＰ（車両ＩＰ）を保有しておく必要が無くなるため、図１２Ｃに示すようにデータを破棄する。

Here, the counter is for the communication GW to count the number of request data transmitted from the vehicle toward the communication target. For example, if n request data are transmitted, the counter value is n. Yes. When the vehicle receives the response data and a completion notification is made to the communication GW, the counter is decremented by 1 for each completion notification, thereby completing the request data transmitted to the communication target by the vehicle. It can be confirmed whether or not notification has been made. For example, in the above example, when n completion notification data are received, the value of the counter is 0, and the completion notification is made for all the request data. In this case, since it is not necessary to have the vehicle unique ID and the transmission source IP (vehicle IP), the data is discarded as shown in FIG. 12C.

  Here, for example, a case where request data or completion notification data is transmitted from two vehicles (vehicle unique IDs: X, Y) will be described with reference to Table 4.

表４に示すように、時刻：ｔ１、ｔ２、ｔ３、・・・に、各車両が要求データまたは完了通知データを送信したとする。時刻ｔ１において、通信ＧＷは車両Ｘから要求データを受信するため、Ｘ用カウンタは１となる。時刻ｔ３において完了通知を受信した場合には、カウンタの数を１だけ減算して、その結果、Ｘ用カウンタは０となる。同様に、車両Ｙから時刻ｔ２とｔ４に要求データを受信したとすると、カウンタの数は２となる。さらに、時刻ｔ６とｔ８において完了通知を受信すると、それぞれ１ずつ減算するため、カウンタの数は０となる。このようにして、カウンタにより、通信ＧＷが受信した要求データの数と、完了通知データの数を一致させることができ、車両と通信ＧＷとの間の通信をＵＤＰプロトコル方式により行なっても確実にデータの送受信を行うことができる。

As shown in Table 4, each vehicle transmits request data or completion notification data at times t1, t2, t3,. At time t1, since the communication GW receives request data from the vehicle X, the X counter becomes 1. When a completion notification is received at time t3, the number of counters is decremented by 1, and as a result, the X counter becomes 0. Similarly, if request data is received from the vehicle Y at times t2 and t4, the number of counters is two. Further, when completion notifications are received at times t6 and t8, 1 is subtracted from each other, so the number of counters becomes zero. In this way, the counter can match the number of request data received by the communication GW with the number of completion notification data, so that the communication between the vehicle and the communication GW can be reliably performed by the UDP protocol method. Data can be sent and received.

  As described above, even when data is transmitted and received between the mobile vehicle and the communication GW by the UDP protocol method, the completion notification data is transmitted and received, and the request data number and the completion notification data number are counted reliably. Data can be sent and received. Furthermore, since data transmission / reception between the vehicle and the communication GW is performed by the UDP protocol method, data transmission / reception can be performed quickly, and communication can be reliably performed even when the vehicle is moving. This makes it possible to perform more efficient communication.

  In this embodiment, an example of the UDP protocol method is shown as a communication method that does not establish a connection, and an example of a TCP protocol method is shown as a communication method that establishes a connection, but is not limited thereto.

  In the above embodiments, the vehicle has been described as an example of the moving body. However, the present invention is not limited to this, and can be applied to other moving bodies that move at high speed, such as airplanes and helicopters, where the moving destination is not determined. It is. In this embodiment, data processing from one vehicle has been described. However, the present invention can also be applied to a case where a plurality of vehicles transmit and receive data simultaneously.

  Furthermore, in the present embodiment, the communication device 11 is described as being independent of the navigation device 12, but may be incorporated in the navigation device.

An outline of a communication method based on the TCP protocol method is shown. The outline of the problem of the conventional vehicle communication is shown. Problems in the communication method using the UDP protocol method will be described. 1 shows a system configuration of a mobile communication method of the present invention. The vehicle structure carrying the mobile communication apparatus of this invention is shown. The communication system between each terminal of this invention is shown. The outline | summary of the request data transmission to the communication GW from the vehicle in the mobile communication method of this invention is shown. An outline of request data transmission from the communication GW to the center in the mobile communication method of the present invention is shown. An outline of request data transmission from a center to a communication target in the mobile communication method of the present invention is shown. The communication processing flow in the vehicle which concerns on the mobile communication method of this invention is shown. The processing flow in communication GW which concerns on the mobile communication method of this invention is shown. The processing flow in communication GW which concerns on the mobile communication method of this invention is shown. The procedure of the 3-way handshake between the communication GW and the center in the mobile communication method of the present invention will be shown. The processing flow in the center which concerns on the mobile communication method of this invention is shown. The outline | summary of the response data transmission to the center from the communication object in the mobile communication method of this invention is shown. An outline of response data transmission from the center to the communication GW in the mobile communication method of the present invention is shown. The outline | summary of transmission / reception of the response data and completion notification data between the vehicle and communication GW in the mobile communication method of this invention is shown. The communication processing flow in the vehicle which concerns on the mobile communication method of this invention is shown.

Explanation of symbols

1 vehicle 2 communication GW
3 Center 4 Server 10 Antenna 11 Communication Device 12 Navigation Device 13 Control Unit 14 Storage Unit 15 Input Unit 16 Output Device 17 Wireless Communication Terminal 18 Vehicle Unique ID
19 Request packet data generation means 20 Completion notification packet data generation means 200 Internet network 31 UDP packet data including request data transmitted by vehicle to communication GW 32 TCP packet data including request data transmitted by communication GW to center 33 TCP packet data including request data transmitted from the center to the communication target 41 TCP packet data including response data transmitted from the communication target to the center 42 TCP packet data including response data transmitted from the center to the communication GW 43 Communication GW Packet data including response data transmitted from the vehicle to the vehicle 51 UDP packet data including completion notification data transmitted from the vehicle to the communication GW

Claims (10)

While communicating between the mobile and the communication gateway,
A mobile communication method for performing communication between the communication gateway and a center connected to a communication target of the mobile,
The mobile transmits request data to a specific communication gateway in a manner that does not establish a connection;
The communication gateway receives the request data and transmits the received request data to the center in a manner to establish a connection;
The center transmitting the received request data to the communication target;
The communication target transmits response data to the center;
The center transmitting the received response data to the communication gateway;
The communication gateway transmitting the received response data to the mobile in a manner that does not establish a connection;
Said moving body, have a, a step of receiving the response data,
In the step of transmitting request data in a manner in which the mobile does not establish a connection with a specific communication gateway
The data transmitted by the mobile unit to a specific communication gateway includes a destination Internet protocol (IP) as a communication gateway IP, a source IP as a mobile unit IP, a mobile unit unique ID, a communication target IP, and request data. A mobile communication method characterized by being a data part . The communication gateway receives the request data and transmits the request data received in a manner to establish a connection to the center.
The communication gateway has a mobile unit unique ID in the received data and a mobile unit IP that is a source IP,
The data communication gateway sends to the center, the destination as a center IP, sends the source IP communications gateway IP, claim 1, characterized in that it has the same data portion and a data portion received from the mobile The mobile communication method according to 1. In the step of transmitting the request data received by the center to the communication target,
The center has a mobile unit unique ID and an IP of a communication gateway which is a source IP,
Data to which the center is transmitted to the communication target, the destination IP and the communication target IP in the data unit, sends the source IP as center IP, according to claim 2, characterized in that the requested data and data section Mobile communication method. In the step of the center sending the received response data to the communication gateway,
The data transmitted from the center to the communication gateway is a communication gateway IP having a transmission destination IP, a transmission source IP is a center IP, and a mobile unit unique ID and response data are used as a data part. The mobile communication method according to claim 3 . In the step in which the communication gateway transmits the received response data to the mobile body in a manner that does not establish a connection,
Search the mobile IP based on the mobile unique ID in the received data,
5. The movement according to claim 4 , wherein the data transmitted by the communication gateway to the mobile body includes a destination IP as a mobile IP, a source IP as a communication gateway IP, and response data as a data portion. Body communication method. Following the step in which the mobile receives response data,
The mobile unit further includes a step of transmitting to the communication gateway, as a reception completion notification, data having the transmission destination IP as the communication gateway IP, the transmission source IP as the mobile IP, and only the mobile unit unique ID as a data part. The mobile communication method according to claim 5 . If the data received by the communication gateway is converted into data including response data and transmitted to the mobile unit, a response completion data is not received from the mobile unit even if a predetermined time elapses. The mobile communication method according to claim 6 , wherein data including the message is transmitted again. When the communication gateway has a mobile unit unique ID and a mobile unit IP, the communication counter has an initial value of 1 together,
When the communication gateway receives data from the mobile body, if the mobile body unique ID of the received data is the same as the mobile body unique ID held, the counter is incremented by 1 and when the completion notification is received Subtract 1 from the counter,
8. The mobile communication method according to claim 7 , wherein when the counter reaches 0, the mobile unit unique ID and the mobile unit IP held together with the counter that has reached 0 are discarded. The method of not establishing the connection is a UDP protocol method of transmitting and receiving UDP packets,
The method of establishing a connection, the mobile communication method according to any one of claims 1 to 8 is a TCP protocol scheme for transmitting and receiving TCP packets. A mobile communication device in which a mobile unit communicates with a communication gateway,
Data transmission means for transmitting request data in a method that does not establish a connection;
Response data receiving means for receiving response data in response to the transmitted request data in a manner that does not establish a connection;
The completion notification data to the response data, possess a completion notification data transmitter unit configured to transmit at not establish system connections, and
The data transmitted by the mobile unit to a specific communication gateway includes a destination Internet protocol (IP) as a communication gateway IP, a source IP as a mobile unit IP, a mobile unit unique ID, a communication target IP, and request data. A mobile communication device characterized by being a data part .

Images