Roadside device, vehicle-mounted device, communication system and communication method

Abstract

The roadside device comprises: a communication unit that receives data sent from the vehicle-mounted device and forwards it to the server; and a control unit that, when receiving a request to resume uploading data from the vehicle-mounted device during the forwarding of data to the server, reserves the forwarding of the request to resume uploading to the server.

Description

Technical Field

[0001] The present disclosure relates to a roadside device, a vehicle-mounted device, a communication system and a communication method. Background Art

[0002] In recent years, the practical application of advanced road traffic systems (ITS: Intelligent Transport Systems) that transmit and receive information between devices such as on-board devices mounted on vehicles, roadside devices installed on roads, and servers has been advancing.

[0003] Patent Document 1 discloses a method of eliminating the need to retransmit data that has been transmitted once from a mobile phone when a circuit is disconnected during upload from the mobile phone to a Web server.

[0004] Prior art literature

[0005] Patent Literature

[0006] Patent Document 1: Japanese Patent Application Publication No. 2008-271097 Summary of the invention

[0007] When the communication between the vehicle-mounted device and the roadside device is disconnected and then restored, and the vehicle-mounted device re-uploads data, the amount of data sent by the vehicle-mounted device to the roadside device before the communication is disconnected may differ from the amount of data transferred by the roadside device to the server. Therefore, there is a concern that the data of the vehicle-mounted device may not be properly uploaded to the server.

[0008] A non-limiting embodiment of the present disclosure is to provide a roadside device capable of appropriately uploading data of a vehicle-mounted device.

[0009] An embodiment of the present disclosure involves a roadside machine comprising: a communication circuit that receives data sent from a vehicle-mounted device and forwards it to a server; and a control circuit that reserves the forwarding of the upload restart request to the server when the communication circuit receives a request to resume uploading the data from the vehicle-mounted device during the forwarding of the data to the server.

[0010] An embodiment of the present disclosure involves a vehicle-mounted device comprising: a communication circuit that communicates with a roadside device having a forwarding circuit and a control circuit, the forwarding circuit receiving data and forwarding it to a server, the communication circuit retaining the forwarding of the upload restart request to the server when receiving an upload restart request for the data from the vehicle-mounted device during the forwarding of the data to the server; and a control circuit that sets the sending interval of the upload restart request to be longer than that before the communication with the roadside device is cut off after the communication with the roadside device is cut off.

[0011] An embodiment of the present disclosure involves a communication system having a vehicle-mounted device and a roadside machine, the vehicle-mounted device having: a vehicle-mounted device communication circuit for sending data; and a vehicle-mounted device control circuit for sending a request to resume uploading the data, the roadside machine having: a roadside machine communication circuit for receiving the data and transmitting it to a server; and a roadside machine control circuit for retaining the forwarding of the upload resume request to the server when receiving the upload resume request for the data during the forwarding of the data to the server.

[0012] In a communication method involved in an embodiment of the present disclosure, data sent from a vehicle-mounted device is received, the data is forwarded to a server, and during the forwarding of the data to the server, when a request for resuming uploading the data is received from the vehicle-mounted device, the forwarding of the request for resuming uploading to the server is retained.

[0013] In addition, these general or specific methods may be implemented by a system, an apparatus, a method, an integrated circuit, a computer program or a recording medium, or by any combination of systems, apparatuses, methods, integrated circuits, computer programs and recording media.

[0014] According to an embodiment of the present disclosure, data of a vehicle-mounted device can be appropriately uploaded.

[0015] The advantages and effects of one embodiment of the present disclosure are clear from the description and drawings. Such advantages and / or effects are provided by several embodiments and the features described in the description and drawings, but in order to obtain one or more of the same features, it is not necessary to provide all of them. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] Figure 1 It is a diagram showing a configuration example of a communication system according to an embodiment of the present disclosure.

[0017] Figure 2 This is a diagram showing an example of a block structure of a vehicle-mounted device.

[0018] Figure 3 This is a diagram showing an example of a block structure of a roadside device.

[0019] Figure 4 This is a diagram showing an example of a block structure of a server.

[0020] Figure 5 It is a sequence diagram showing an operation example of the communication system.

[0021] Figure 6 This is a flowchart showing an example of the operation of the roadside device.

[0022] Fig. 7A Yes means Figure 1 A timing diagram of an operation example of a communication system.

[0023] Figure 7B Yes means Figure 1 A timing diagram of an operation example of a communication system.

[0024] Fig. 8A Yes means Figure 1 A timing diagram of an operation example of a communication system.

[0025] Figure 8B Yes means Figure 1 A timing diagram of an operation example of a communication system.

[0026] Fig. 9A Yes means Figure 1 A timing diagram of an operation example of a communication system.

[0027] Fig. 9B Yes means Figure 1 A timing diagram of an operation example of a communication system.

[0028] Fig. 10A Yes means Figure 1 A timing diagram of an operation example of a communication system.

[0029] Fig. 10B Yes means Figure 1 A timing diagram of an operation example of a communication system.

[0030] Fig.11 Yes means Figure 1 A timing diagram of an operation example of a communication system.

[0031] Fig.12 Yes means Figure 1 A timing diagram of an operation example of a communication system.

[0032] Fig.13A Yes means Figure 1 A timing diagram of an operation example of a communication system.

[0033] Fig. 13B Yes means Figure 1 A timing diagram of an operation example of a communication system. DETAILED DESCRIPTION

[0034] Hereinafter, the embodiments of the present disclosure will be described in detail with appropriate reference to the accompanying drawings. However, unnecessary detailed descriptions may be omitted. For example, detailed descriptions of well-known matters and repeated descriptions of substantially the same structures may be omitted. This is to avoid the following description from being unnecessarily lengthy and to make it easy for those skilled in the art to understand.

[0035] In addition, the drawings and the following description are provided for those skilled in the art to fully understand the present disclosure, and are not intended to limit the subject matter described in the claims by these contents.

[0036] Figure 1 1 is a diagram showing an example of a configuration of a communication system according to an embodiment of the present disclosure. Figure 1 As shown, the communication system includes a vehicle-mounted device 1 , a roadside device 2 , and a server 3 .

[0037] The vehicle-mounted device 1 is mounted on a vehicle such as an automobile or an electric motorcycle, and performs wireless communication with a roadside device 2 .

[0038] The vehicle-mounted device 1 includes various sensors. The vehicle-mounted device 1 transmits data collected by the various sensors to the roadside device 2. For example, the vehicle-mounted device 1 transmits image data from a camera, position data acquired using a GPS (Global Positioning System), and radar data to the roadside device 2.

[0039] The roadside device 2 is installed on a structure such as a signal, a street lamp, or a power pole. The roadside device 2 forms a communication area on a road or an intersection where vehicles pass, for example. The roadside device 2 wirelessly communicates with the vehicle-mounted device 1 in the communication area, and forwards the data sent from the vehicle-mounted device 1 to the server 3. In addition, the roadside device 2 forwards the data received from the server 3 to the roadside device 2. Forwarding can also be called sending.

[0040] The roadside device 2 is connected to the server 3 via a network 4. The network 4 may be, for example, the Internet. The network 4 may also include a wireless network.

[0041] The server 3 communicates with the roadside device 2. In addition, the server 3 communicates with the vehicle-mounted device 1 via the roadside device 2. The server 3 collects various data uploaded from the vehicle-mounted device 1 and stores them in the storage device. The server 3 processes various data stored in the storage device and sends the processing results to the vehicle-mounted device 1. Uploading can also be called sending.

[0042] In addition, the number of the vehicle-mounted device 1, the roadside device 2, and the server 3 is not limited to Figure 1 Example.

[0043] In addition, for example, a plurality of roadside devices 2 may be installed at one intersection. In addition, one roadside device 2 may form a communication area for a plurality of intersections.

[0044] Figure 2 1 is a diagram showing an example of a block structure of the vehicle-mounted device 1. Figure 2As shown, the vehicle-mounted device 1 includes a communication device 11 , a CPU (Central Processing Unit) 12 , a storage device 13 , and a sensor device 14 .

[0045] The communication device 11 performs wireless communication with the roadside machine 2. The communication device 11 performs wireless communication with the roadside machine 2 based on WiGig (Wireless Gigabit), for example. In addition, the communication device 11 can perform wireless communication with the roadside machine 2 based on DSRC (Dedicated Short Range Communication), C-V2X (Cellular-V2X), wireless LAN (Local Area Network), WiMAX (Worldwide Interoperability for Microwave Access), 4G (4th Generation), or 5G (5th Generation). The communication device 11 can also be called a communication unit.

[0046] The CPU 12 controls the entire vehicle-mounted device 1 . The CPU 12 may also be referred to as a control unit. The CPU 12 transmits data output from the sensor device 14 to the roadside device 2 via the communication device 11 .

[0047] The storage device 13 stores programs for the CPU 12 to run. In addition, the storage device 13 stores data for the CPU 12 to perform calculations or data for the CPU 12 to control various parts. The storage device 13 may be composed of a storage device such as a RAM (Random Access Memory), a ROM (Read Only Memory), a flash memory, and a HDD (Hard Disk Drive).

[0048] The sensor device 14 is, for example, a sensor device such as a camera, a radar, a LiDAR (Light Detection and Ranging), a sonar, or an ultrasonic sensor. The sensor device 14 may include an ECU (Electronic Control Unit).

[0049] In addition, the vehicle-mounted device 1 may not include the sensor device 14. The sensor device 14 may be provided in the vehicle.

[0050] Figure 3 2 is a diagram showing an example of a block structure of the roadside machine 2. Figure 3As shown, the roadside device 2 includes communication devices 21 a and 21 b , a CPU 22 , and a storage device 23 .

[0051] The communication device 21a performs wireless communication with the vehicle-mounted device 1. The communication device 21a performs wireless communication with the vehicle-mounted device 1 based on, for example, DSRC. The communication device 21a may also be referred to as a communication unit.

[0052] The communication device 21b communicates with the server 3 via wire. The communication device 21b may communicate with the server 3 wirelessly. The communication device 21b may also be referred to as a communication unit.

[0053] The CPU 22 controls the entire roadside device 2. The CPU 22 may also be called a control unit. The CPU 22 transmits data of the vehicle-mounted device 1 received by the communication device 21a to the server 3 via the communication device 21b. The CPU 22 transmits data of the server 3 received by the communication device 21b to the vehicle-mounted device 1 via the communication device 21a.

[0054] The storage device 23 stores programs for the CPU 22 to operate. In addition, the storage device 23 stores data for the CPU 22 to perform calculations or data for the CPU 22 to control various parts. The storage device 23 may be composed of a storage device such as a RAM, a ROM, a flash memory, and a HDD. In addition, the storage device 23 may also store data from the vehicle-mounted device 1 received by the communication device 21a and data from the server 3 received by the communication device 21b.

[0055] Figure 4 is a diagram showing an example of a block structure of the server 3. Figure 4 As shown, the server 3 includes a communication device 31 , a CPU 32 , and a storage device 33 .

[0056] The communication device 31 communicates with the roadside device 2 via a wire. In addition, the communication device 31 may communicate with the roadside device 2 via a wireless network using, for example, a wireless LAN, WiMAX, 4G, or 5G. In addition, the communication device 31 may also be referred to as a communication unit.

[0057] The CPU 32 controls the entire server 3. The CPU 32 may also be called a control unit. The CPU 32 stores the data of the roadside device 2 (vehicle-mounted device 1) received by the communication device 31 in the storage device 33. The CPU 32 transmits the processing result obtained by processing using the data stored in the storage device 33 to the roadside device 2 via the communication device 31.

[0058] The storage device 33 stores programs for the CPU 32 to operate. In addition, the storage device 33 stores data for the CPU 32 to perform calculations, data for the CPU 32 to control various components, and the like. In addition, the storage device 33 stores data sent from the vehicle-mounted device 1. The storage device 33 storing the data of the vehicle-mounted device 1 may also be called a database. The storage device 33 may also be composed of a storage device such as a RAM, a ROM, a flash memory, and a HDD.

[0059] Figure 5 1 is a sequence diagram showing an example of the operation of the communication system. The vehicle-mounted device sends an upload request to the roadside device (S1).

[0060] The roadside device transmits the upload request of S1 to the server (S2).

[0061] Upon receipt of the upload request in S2, the server sends an upload approval to the roadside device (S3). The upload approval may also include identification information assigned by the server. The identification information is information for identifying the data uploaded from the vehicle-mounted device.

[0062] The roadside device receives the upload approval sent in S3. The roadside device registers (stores in a storage device) the identification information included in the received upload approval, and transfers the upload approval including the identification information to the vehicle-mounted device (S4).

[0063] In addition, the roadside machine manages the amount of data received from the vehicle-mounted device for each identification information. That is, the roadside machine distinguishes the data received from the vehicle-mounted device for each communication session and manages the amount of data for each communication session. In addition, a communication session refers to a unit that manages from the start to the end of communication. For example, in this embodiment, the roadside machine sends an upload approval with identification information to the vehicle-mounted device ( Figure 5 7) until the upload completion response (S44 of FIG. 7) indicating that the upload of the data managed by the roadside device using the same identification information to the vehicle-mounted device is completed. Figure 7B Units up to S58).

[0064] The vehicle-mounted device transfers (uploads) the data to the roadside device (S5) based on the reception of the upload approval in S4.

[0065] The roadside device receives the data uploaded by the roadside device and transfers it to the server (starts transfer) (S6).

[0066] The vehicle-mounted device completes the data transfer (S7).

[0067] Furthermore, when the vehicle-mounted device completes data transmission, the data transmission between the roadside device and the server is not completed. Figure 5As shown, when the communication speed between the roadside unit and the server is slower than the communication speed between the on-vehicle unit and the roadside unit, the upload of the on-vehicle unit is completed, but the upload (transfer) of the roadside unit is not completed.

[0068] Here, in a state where the on-vehicle unit does not receive a response indicating the end of data transfer for S7 (data transfer end response), the wireless communication between the on-vehicle unit and the roadside unit is cut off. The on-vehicle unit times out the data transfer process during the cut-off of the wireless communication. In the case of timeout data transfer processing, the on-vehicle unit sends a request to restart the upload to the roadside unit, but since the wireless communication is in a cut-off state, the request to restart the upload is not sent.

[0069] After the wireless communication between the on-vehicle unit and the roadside unit is restored, the on-vehicle unit sends a request to restart the upload to the roadside unit (S8). The request to restart the upload includes the identification information sent in S4.

[0070] The roadside unit receives the request to restart the upload sent in S8. The roadside unit obtains the amount of data that has been received from the data transferred from the on-vehicle unit corresponding to the identification information included in the received request to restart the upload from the storage device 23.

[0071] For example, assume that the data transfer for S7 is completed and the on-vehicle unit sends N bytes of data to the roadside unit. In this case, the roadside unit obtains N bytes of information as the information on the amount of data received.

[0072] Based on the reception of the request to restart the upload in S8, the roadside unit sends re-upload information to the on-vehicle unit (S9). The re-upload information includes the amount of data received. For example, in the above example, the re-upload information includes N bytes of information.

[0073] After the start of data transfer in S6, a failure occurs in the network between the roadside unit and the server (S10). The roadside unit has not completed the data transfer of the on-vehicle unit at the moment when the network failure occurs. For example, at the moment when the network failure occurs, the roadside unit transfers M bytes (M < N) of the data received from the on-vehicle unit to the server.

[0074] In Figure 5 In the shown time sequence, when the roadside unit receives the request to restart the upload in S8, it sends re-upload information including information on the amount of N bytes of data received to the on-vehicle unit (S9). After receiving the re-upload information in S9, the on-vehicle unit may also start uploading again from the (N + 1)-th byte of data (not shown).

[0075] On the other hand, the roadside unit transfers M bytes of data to the server, but there is also data that has not been transferred to the server. For example, in Figure 5In the sequence shown, there are "NM" bytes of data that are not transferred to the server. For example, if the communication speed between the roadside device and the server is slower than the communication speed between the vehicle-mounted device and the roadside device, data that is not transferred to the server may be generated.

[0076] like Figure 1 The communication system shown performs the following operations in order to appropriately upload the data of the vehicle-mounted device 1 to the server 3 .

[0077] Figure 6 2 is a flowchart showing an example of the operation of the roadside device 2. The operation is started when a vehicle equipped with the vehicle-mounted device 1 enters the communication area of ​​the roadside device 2. The vehicle-mounted device 1 has data to be uploaded to the server 3.

[0078] The roadside device 2 establishes wireless communication connection with the vehicle-mounted device 1 and receives an upload request from the vehicle-mounted device 1 ( S21 ).

[0079] In addition, the roadside device 2 forwards the upload request received from the vehicle-mounted device 1 to the server 3. When receiving the upload request from the roadside device 2, the server 3 sends identification information to the roadside device 2. The identification information includes the data size of the data uploaded from the vehicle-mounted device 1 to the server 3. The roadside device 2 registers (stores in the storage device 23) the identification information sent from the server 3 and sends it to the vehicle-mounted device 1.

[0080] The roadside device 2 determines whether the communication request received from the vehicle-mounted device 1 is a request to upload data or a request to resume uploading ( S22 ).

[0081] When the roadside device 2 determines in S22 that the communication request received from the vehicle-mounted device 1 is for data upload ("data" in S22), it determines whether reception of the uploaded data from the vehicle-mounted device 1 has been completed (S23).

[0082] The end of receiving data from the vehicle-mounted device 1 may include the end of receiving all data from the vehicle-mounted device 1. The end of receiving data from the vehicle-mounted device 1 may include, for example, interrupting the reception of data from the vehicle-mounted device 1 by disconnecting wireless communication.

[0083] When the roadside device 2 determines in S23 that the reception of data from the vehicle-mounted device 1 has not been completed (No in S23), the process of S23 is repeated.

[0084] When the roadside device 2 determines in S23 that the data reception from the vehicle-mounted device 1 has been completed (YES in S23 ), it determines whether an upload restart request has been received from the vehicle-mounted device 1 ( S24 ).

[0085] When the roadside device 2 determines in S24 that the upload restart request has been received from the vehicle-mounted device 1 (Yes in S24 ), the transfer of the upload restart request to the server 3 is suspended ( S25 ).

[0086] When the roadside machine 2 determines in S24 that no upload restart request has been received from the vehicle-mounted device 1 ("No" in S24), or when the forwarding of the upload restart request to the server 3 is retained in S25, it determines whether the forwarding of the uploaded data to the server 3 is completed (S26).

[0087] In addition, the end of data transfer to the server 3 may include the end of transfer of all data by the roadside device 2. In addition, the end of data transfer to the server 3 may include, for example, the interruption of data transfer by the roadside device 2 due to communication disconnection of the network 4.

[0088] When the roadside device 2 determines in S26 that the data transfer to the server 3 has not been completed (No in S26 ), the process proceeds to S24 .

[0089] When the roadside device 2 determines in S26 that the data transfer to the server 3 is completed (Yes in S26 ), the data transfer to the server 3 is completed ( S27 ).

[0090] When the server 3 completes receiving (uploading) data from the vehicle-mounted device 1, it may send a response to the vehicle-mounted device 1 via the roadside device 2. The response may be based on, for example, the status code 200 of HTTP (HyperText Transfer Protocol).

[0091] The roadside device 2 determines whether the transfer of the upload restart request is on hold ( S28 ).

[0092] When the roadside device 2 determines in S28 that the forwarding of the upload restart request is reserved ("Yes" in S28), the upload restart request is forwarded to the server 3, and a response to the upload restart request is received from the server 3 (S29). In addition, when the roadside device 2 determines in S22 that the communication request received from the vehicle-mounted device 1 is an upload restart request ("Upload restart request" in S22), the upload restart request is forwarded to the server 3, and a response to the upload restart request is received from the server 3 (S29).

[0093] In addition, the response from the server 3 may also comply with, for example, the HTTP status code 200 or 100.

[0094] In addition, when the roadside device 2 does not receive a response from the server 3 due to, for example, a disconnection of the network 4 , it may transmit an error notification based on the HTTP status code 500 to the vehicle-mounted device 1 .

[0095] When the roadside device 2 determines in S28 that the forwarding of the upload restart request is not reserved (No in S28), it determines whether all the data corresponding to the identification information has been forwarded to the server 3 (S30). In addition, when the roadside device 2 receives a response to the upload restart request from the server 3 in S29 (S29), it determines whether all the data corresponding to the identification information has been forwarded to the server 3 (S30).

[0096] When the roadside device 2 determines in S30 that all the data corresponding to the identification information has not been transmitted to the server 3 (No in S30 ), the process proceeds to S22 .

[0097] When the roadside device 2 determines in S30 that all the data corresponding to the identification information has been transmitted to the server 3 (YES in S30 ), the process of this flowchart ends.

[0098] Fig. 7A and Figure 7B Yes means Figure 1 The timing diagram of the operation example of the communication system in FIG. Fig. 7A The timing shown follows Figure 7B The timing of Fig. 7A and Figure 7B The symbols in the dashed box are the same as those in Figure 6 The actions of the symbols shown correspond to each other. For example, Fig. 7A and Figure 7B The dashed box S21 shown is Figure 6 The operation of S21 shown corresponds to this.

[0099] like Fig. 7A as well as Figure 7B The timing shown in the figure shows an operation example in which the wireless communication is disconnected on the wireless communication path between the vehicle-mounted device 1 and the roadside device 2 when uploading the second block of data D1 after uploading the data D1 from the vehicle-mounted device 1 to the roadside device 2 (see Figure 7B In addition, if Fig. 7A as well as Figure 7B The sequence shown in the figure shows an example of the operation when the roadside device 2 transfers data to the server 3 when the roadside device 2 receives the upload restart request from the vehicle-mounted device 1 (see Figure 7B S53).

[0100] The vehicle equipped with the vehicle-mounted device 1 starts operating by entering the communication area of ​​the roadside device 2. The vehicle-mounted device 1 has data to be uploaded to the server 3.

[0101] The vehicle-mounted device 1 establishes a wireless communication connection with the roadside device 2 and transmits a request to upload the first block of data D1 to the roadside device 2 ( S41 ).

[0102] The roadside device 2 transfers the upload request of S41 to the server 3 ( S42 ).

[0103] Upon receipt of the upload request in S42 , the server 3 transmits an upload approval to the roadside device 2 ( S43 ).

[0104] The roadside device 2 transfers the upload approval of S43 to the vehicle-mounted device 1 ( S44 ).

[0105] The upload approval includes identification information given by the server 30. The identification information is information for identifying data uploaded from the vehicle-mounted device 1. The identification information includes information on the data size of the entire uploaded data (hereinafter, sometimes referred to as UL data size).

[0106] In addition, the vehicle-mounted device 1 may divide the data (data D1) to be uploaded to the server 3 into a plurality of blocks and upload them to the server 3, or may upload them all at once to the server 3. When the vehicle-mounted device 1 divides the data D1 into a plurality of blocks and uploads them to the server 3, the data of the divided blocks may have common identification information or may include identification information of each divided block (data size of the divided block). Fig. 7A and Figure 7B The sequence shown shows an example in which data D1 is divided into a plurality of blocks and uploaded.

[0107] The vehicle-mounted device 1 transfers (uploads) the first block of data to the roadside device 2 (S45) based on the reception of the upload approval sent in S44. The vehicle-mounted device 1 uploads the first block of data using, for example, HTTP communication.

[0108] In addition, S45 to S48 show an example of uploading the first block when there is no disconnection of communication on the wireless communication path between the vehicle-mounted device 1 and the roadside device 2. In addition, S45 to S48 show an example of uploading the first block when there is no disconnection of communication on the communication circuit between the roadside device 2 and the server 3.

[0109] The roadside device 2 transfers the first block of data transferred in S45 to the server 3 ( S46 ).

[0110] The vehicle-mounted device 1 completes the data transfer to the roadside device 2 (S47).

[0111] When the data size of the first block of the received data matches the data size (data size of the first block) recorded in the HTTP header, the server 3 sends a data transfer completion response to the roadside device 2 (S48). The data transfer completion response may be based on, for example, HTTP status code 200.

[0112] The roadside device 2 transfers the data transfer completion response of S48 to the vehicle-mounted device 1 (S49).

[0113] In addition, the communication speed of the communication circuit is slower than that of the wireless communication path. Therefore, the time until the data transfer in the communication circuit is completed is longer than the time until the data transfer in the wireless communication path is completed (refer to the time from S45 to S47 and the time from S46 to S48).

[0114] The vehicle-mounted device 1 transfers (uploads) the second block of data as the next block (S50). The vehicle-mounted device 1 transfers the second block of data using, for example, HTTP communication.

[0115] The roadside device 2 transfers the second block of data uploaded in S50 to the server 3 ( S51 ).

[0116] The vehicle-mounted device 1 completes the data transfer to the roadside device 2 (S52).

[0117] Here, the wireless communication in the wireless communication path is disconnected. For example, when the vehicle-mounted device 1 moves out of the communication area of ​​the roadside device 2, the wireless communication is disconnected. Alternatively, the wireless communication is disconnected due to the influence of interference.

[0118] When the vehicle-mounted device 1 reconnects the wireless communication with the roadside device 2 after the wireless communication is disconnected, the vehicle-mounted device 1 transmits an upload restart request to the roadside device 2 (S53). The upload restart request includes the identification information assigned by the server 30.

[0119] When receiving the upload restart request in S53, the roadside device 2 determines the transfer status of the corresponding data to the server 3 based on the identification information included in the upload restart request. Here, the data corresponding to the identification information is in the middle of the transfer of the second block, and the roadside device 2 determines that the data is being transferred.

[0120] When the roadside device 2 receives the upload restart request of S53, if the data transmission to the server 3 is in progress, the upload restart request of S53 is held to be transmitted to the server 3. Figure 7B As shown by the two dotted arrows shown in the dotted frame S25, the roadside device 2 holds the transmission of the upload restart request to the server 3 for a predetermined period of time.

[0121] Furthermore, when the roadside device 2 receives the upload restart request again from the vehicle-mounted device 1 while the upload restart request is being forwarded to the server 3 , it may send a message with a status code 102 in accordance with HTTP to the vehicle-mounted device 1 .

[0122] Alternatively, the vehicle-mounted device 1 may set the timeout time for sending the upload restart request to be longer than a certain time. For example, the vehicle-mounted device 1 may set the timeout time to be longer than the standard setting time.

[0123] When the data transfer of the second block based on the roadside machine 2 is completed, the server 3 sends a data transfer completion response to the roadside machine 2 (S54). For example, when the data size of the second block of data received from the roadside machine 2 is consistent with the data size recorded in the HTTP header of the data transfer, the server 3 sends a data transfer completion response to the roadside machine 2. The data transfer completion response may also be based on, for example, HTTP status code 200.

[0124] The roadside device 2 transfers the data transfer completion response of S54 to the vehicle-mounted device 1 (S55).

[0125] After all the data (first block, second block) received from the vehicle-mounted device 1 are transferred (transfer completed), the roadside device 2 transfers the held upload restart request to the server 3 (S56). The upload restart request includes the identification information of the data D1 given by the server 30.

[0126] When receiving the upload restart request in S56 , the server 3 acquires the total received data size of the data D1 corresponding to the identification information. The total received data size is the total received size of the data received from the roadside device 2 and managed by the server 30 for each identification information.

[0127] The server 3 compares the received total data size of the acquired data D1 with the UL data size of the data D1. When the received total data size of the data D1 is consistent with the UL data size of the data D1, the server 3 sends an upload completion response of the data D1 to the roadside device 2 (S57). The upload completion response may also be based on, for example, the HTTP status code 200.

[0128] The roadside device 2 transfers the upload completion response of S57 to the vehicle-mounted device 1 ( S58 ).

[0129] Through the above-mentioned processing, the uploading from the vehicle-mounted device 1 to the server 3 (uploading of the data D1) is completed.

[0130] Next, the vehicle-mounted device 1 has data (next data D2) to upload to the server 3.

[0131] The vehicle-mounted device 1 transmits a request to upload the data D2 to the roadside device 2 (S59).

[0132] The roadside device 2 transfers the upload request of the data D2 in S59 to the server 3 ( S60 ).

[0133] In response to receiving the upload request of the data D2 in S60 , the server 3 transmits an approval for uploading the data D2 to the roadside device 2 ( S61 ).

[0134] The roadside device 2 transfers the approval of uploading the data D2 in S61 to the vehicle-mounted device 1 (S62).

[0135] The vehicle-mounted device 1 transfers the data D2 to the roadside device 2 based on the reception of the upload approval of the data D2 transmitted in S62 (S63).

[0136] Furthermore, the vehicle-mounted device 1 may divide the data (data D2) to be uploaded to the server 3 into a plurality of blocks and upload the data to the server 3, or may upload the data to the server 3 all at once.

[0137] The roadside device 2 transfers the data D2 transferred in S63 to the server 3 ( S64 ).

[0138] As described above, the communication device 21a of the roadside device 2 receives the data transmitted from the vehicle-mounted device 1, and the communication device 21b transfers the data to the server 3. When the CPU 22 of the roadside device 2 receives a data upload restart request from the vehicle-mounted device 1 during the data transfer to the server 3, the transfer of the upload restart request to the server 3 is suspended. As a result, the vehicle-mounted device 1 can properly upload data.

[0139] Fig. 8A and Figure 8B Yes means Figure 1 The timing diagram of the operation example of the communication system. Fig. 8A The timing shown follows Figure 8B The timing of Fig. 8A as well as Figure 8B The dashed box symbol is shown with Figure 6 The actions of the symbols shown correspond to the following. Fig. 8A as well as Figure 8B The dashed box S21 shown is Figure 6 The operation of S21 shown corresponds to this.

[0140] like Fig. 8A as well as Figure 8B The sequence shown in the figure shows an operation example in which the wireless communication between the vehicle-mounted device 1 and the roadside device 2 is disconnected before the data upload from the vehicle-mounted device 1 to the roadside device 2 is completed (data is being transferred) (see Figure 8B In addition, if Fig. 8A as well as Figure 8B The sequence shown in the figure shows an example of the operation when the roadside device 2 transfers data to the server 3 when the roadside device 2 receives the upload restart request from the vehicle-mounted device 1 (see Figure 8B S73).

[0141] like Fig. 8A The processing of S41 to S49 shown is the same as the processing of S41 to S49 shown in FIG. 7 , and the description thereof is omitted.

[0142] like Figure 8B As shown, the vehicle-mounted device 1 transfers the second block of the data D1 as the next block (S71). The vehicle-mounted device 1 transfers the data using HTTP communication, for example.

[0143] The roadside device 2 transfers the second block of the data D1 transferred in S71 to the server 3 ( S72 ).

[0144] Here, before the vehicle-mounted device 1 completes uploading the second block (during data transfer), the wireless communication of the wireless communication path between the vehicle-mounted device 1 and the roadside device 2 is disconnected. For example, when the vehicle-mounted device 1 moves out of the communication area of ​​the roadside device 2, the wireless communication is disconnected. Alternatively, the wireless communication is disconnected due to the influence of interference. Due to the disconnection of the wireless communication, the uploading of the second block of data D1 is interrupted.

[0145] When wireless communication is established again with the roadside device 2 after wireless communication is disconnected, the vehicle-mounted device 1 transmits a request to resume uploading the second block to the roadside device 2 (S73). The upload resumption request includes identification information given by the server 30.

[0146] When receiving the upload restart request in S73, the roadside device 2 determines the transfer status of the second block of the corresponding data D1 to the server 3 based on the identification information. Here, the second block of the data D1 corresponding to the identification information is being transferred, and the roadside device 2 determines that the data is being transferred.

[0147] When the vehicle-mounted device 1 interrupts the uploading of the second block of data D1 and receives the uploading restart request from the vehicle-mounted device 1, the roadside device 2 holds the uploading restart request of S73 to the server 3 while the second block of data D1 is being transferred to the server 3. For example, Figure 8B As shown by the two dotted arrows shown in the dotted frame S25, the upload is retained and the request is restarted to be transferred to the server 3.

[0148] After the roadside device 2 transfers all the second block of data D1 received from the vehicle-mounted device 1 (data received from the vehicle-mounted device 1 before the wireless communication is disconnected) to the server 3, it sends an upload restart request to the server 3 (S74). The upload restart request includes identification information related to the second block of data D1 assigned by the server 30.

[0149] Furthermore, when the roadside device 2 receives the upload restart request again from the vehicle-mounted device 1 while the upload restart request is being forwarded to the server 3 , the roadside device 2 may transmit a message 102 in accordance with the HTTP status code to the vehicle-mounted device 1 .

[0150] Alternatively, the vehicle-mounted device 1 may set the timeout time for sending the upload restart request to be longer than a certain time. For example, the vehicle-mounted device 1 may set the timeout time to be longer than the standard setting time.

[0151] When receiving the upload restart request in S74 , the server 3 acquires the received total data size of the second block of the data D1 corresponding to the identification information.

[0152] The server 3 compares the received total data size of the second block of data D1 and the UL data size of the second block of data D1. Since the vehicle-mounted device 1 interrupts the upload of the second block of data D1, the server 3 determines that the received total data size of the second block of data D1 is smaller than the UL data size of the second block of data D1, and sends the re-upload information to the roadside device 2 (S75). The re-upload information includes the information of the received total data size of the second block of data D1. Figure 8B The "Number of bytes sent: N" shown in S75 indicates the total received data size of the second block of data D1 included in the re-upload information. The re-upload information may be based on, for example, HTTP status code No. 100.

[0153] The roadside device 2 transfers the re-upload information of S75 to the vehicle-mounted device 1 (S76).

[0154] The vehicle-mounted device 1 restarts data transfer in response to reception of the re-upload information in S76 (S77). The vehicle-mounted device 1 restarts data transfer of the second block of data D1 starting from the N+1th byte of data based on the information of the received total data size included in the re-upload information.

[0155] The roadside device 2 transfers the data transferred in S77 to the server 3 ( S78 ).

[0156] When the uploading of the data by the roadside device 2 is completed, the server 3 transmits a data transfer completion response to the roadside device 2 ( S79 ).

[0157] The roadside device 2 transfers the data transfer completion response of S79 to the vehicle-mounted device 1 (S80). Figure 8B In the above process, the upload completion responses S57 and S58 may be omitted.

[0158] As described above, the CPU 22 of the roadside device 2 receives re-upload information including information indicating the amount of uploaded data from the server 3 and transfers it to the vehicle-mounted device 1. Thus, the vehicle-mounted device 1 can restart uploading data not uploaded to the server 3 and can upload data appropriately.

[0159] Fig. 9A and Fig. 9B Yes means Figure 1 The timing diagram of the operation example of the communication system in FIG. Fig. 9A The timing shown follows Fig. 9B The timing of Fig. 9A as well as Fig. 9B The dashed box symbol is shown with Figure 6 The actions of the symbols shown correspond to each other. For example, Fig. 9A as well as Fig. 9B The dashed box S21 shown is Figure 6 The operation of S21 shown corresponds to this.

[0160] Fig. 9A as well as Fig. 9B The timing shown in the figure shows an operation example in which the wireless communication between the vehicle-mounted device 1 and the roadside device 2 is disconnected after the data transfer from the vehicle-mounted device 1 to the roadside device 2 is completed (see Fig. 9B ). Furthermore, if Fig. 9A as well as Fig. 9B The sequence shown in the figure shows an operation example in which the communication circuit between the roadside device 2 and the server 3 is disconnected in the middle of data transfer from the roadside device 2 to the server 3 after the roadside device 2 receives the upload restart request from the vehicle-mounted device 1 (see Fig. 9B The shadow portion S26 on the lower side).

[0161] like Fig. 9A The processing of S41 to S49 shown in FIG. Fig. 7A The processes of S41 to S49 shown are the same, and the description thereof is omitted.

[0162] like Fig. 9B As shown, the vehicle-mounted device 1 transfers (uploads) the second block of data D1 as the next block (S101). The vehicle-mounted device 1 transfers data using, for example, HTTP communication.

[0163] The roadside device 2 transfers the second block of the data D1 uploaded in S101 to the server 3 ( S102 ).

[0164] The vehicle-mounted device 1 completes the data transfer to the roadside device 2 ( S103 ).

[0165] Here, the wireless communication is disconnected in the wireless communication path between the vehicle-mounted device 1 and the roadside device 2. For example, the wireless communication is disconnected when the vehicle-mounted device 1 moves out of the communication area of ​​the roadside device 2. Alternatively, the wireless communication between the vehicle-mounted device 1 and the roadside device 2 is disconnected due to the influence of interference.

[0166] When the vehicle-mounted device 1 reconnects the wireless communication with the roadside device 2 after the wireless communication is disconnected, the vehicle-mounted device 1 transmits an upload restart request to the roadside device 2 (S104). The upload restart request includes the identification information assigned by the server 30.

[0167] When receiving the upload restart request in S104, the roadside device 2 determines the transfer status of the corresponding data to the server 3 based on the identification information. Here, the data corresponding to the identification information is being transferred, and the roadside device 2 determines that the data is being transferred.

[0168] After the data transfer of S103 of the vehicle-mounted device 1 is completed, if the data transfer to the server 3 is in progress, the roadside device 2 reserves the upload of S103 and restarts the request to transfer to the server 3. Fig. 9B As shown by the two dotted arrows shown in the dotted frame S25 , the roadside device 2 holds the upload and resumes forwarding the request to the server 3 .

[0169] Here, while the roadside device 2 holds forwarding the upload restart request to the server 3 and before the roadside device 2 completes uploading the data of the vehicle-mounted device 1, the communication circuit between the roadside device 2 and the server 3 is disconnected (S26).

[0170] During the period when the communication circuit between the roadside device 2 and the server 3 is disconnected, the forwarding holding process of the upload restart request times out and stops the forwarding holding process of the upload restart request. By stopping the forwarding holding process, the roadside device 2 forwards the upload restart request to the server 3 (see Fig. 9B The roadside device 2 may repeatedly forward the upload restart request at a certain interval when the upload restart request fails to be sent.

[0171] When the communication circuit is restored, the roadside device 2 transfers an upload restart request to the server 3 (S105). The upload restart request includes identification information given by the server 30.

[0172] When receiving the upload restart request in S105 , the server 3 acquires the received total data size of the data D1 corresponding to the identification information.

[0173] The server 3 compares the received total data size of the data D1 and the UL data size. Since the communication circuit is disconnected, the upload of the data D1 from the roadside device 2 is interrupted in the middle, so the server 3 determines that the received total data size of the data D1 is smaller than the UL data size, and sends the re-upload information to the roadside device 2 (S106). The re-upload information includes the information of the received total data size of the data D1. Fig. 9B The "Number of bytes sent: N" shown in S106 indicates the total received data size of the data D1 included in the re-upload information. The re-upload information may be based on, for example, HTTP status code No. 100.

[0174] The roadside device 2 transfers the re-upload information of S106 to the vehicle-mounted device 1 (S107).

[0175] The vehicle-mounted device 1 restarts data transfer in response to reception of the re-upload information in S107 (S108). The vehicle-mounted device 1 restarts data transfer from data of N+1 bytes based on information on the received total data size included in the re-upload information.

[0176] The roadside device 2 transfers the data transferred in S108 to the server 3 ( S109 ).

[0177] When the uploading of the data by the roadside device 2 is completed, the server 3 transmits a data transfer completion response to the roadside device 2 ( S110 ).

[0178] The roadside device 2 transfers the data transfer completion response of S110 to the vehicle-mounted device 1 (S111). Fig. 9B In the above process, the upload completion responses S57 and S58 may be omitted.

[0179] As described above, when the communication with the server 3 is disconnected and the forwarding holding process of the upload restart request of the vehicle-mounted device 1 times out, the CPU 22 of the roadside device 2 forwards the upload restart request of the vehicle-mounted device 1 to the server 3. As a result, the server 3 can send the re-upload information to the vehicle-mounted device 1, and the vehicle-mounted device 1 can upload data appropriately.

[0180] Fig. 10A and Fig. 10B Yes means Figure 1 The timing diagram of the operation example of the communication system. Fig. 10A The timing sequence shown Fig. 10B The timing of Fig. 10A as well as Fig. 10B The dashed box symbol is shown with Figure 6 The actions of the symbols shown correspond to the following. Fig. 10A and Fig. 10B The dashed box S21 and Figure 6 The operation of S21 shown corresponds to this.

[0181] like Fig. 10A as well as Fig. 10B The timing diagram shows that for Fig. 9A as well as Fig. 9B The sequence shown in FIG. 1 is an example of an operation when the communication circuit between the roadside device 2 and the server 3 is disconnected and the communication circuit is not restored even if the roadside device 2 sends an upload restart request a predetermined number of times (see FIG. 11 ). Fig. 10B The lower shadow part of the ).

[0182] like Fig. 10A The processing of S41 to S49 shown in FIG. Fig. 7A The processes of S41 to S49 are the same as those shown in FIG. 1 , and their description is omitted. Fig. 10B The processing of S101 to S104 shown in FIG. Fig. 9B The processes of S101 to S104 shown are the same, and the description thereof is omitted.

[0183] Here, while the roadside device 2 holds forwarding the upload restart request to the server 3 and before the roadside device 2 completes uploading the data from the vehicle-mounted device 1 , the communication circuit between the roadside device 2 and the server 3 is disconnected.

[0184] During the period when the communication circuit between the roadside device 2 and the server 3 is disconnected, the forwarding holding process of the upload restart request times out and stops the forwarding holding process of the upload restart request. By stopping the forwarding holding process, the roadside device 2 forwards the upload restart request to the server 3 (see Fig. 10B When the transmission of the upload restart request fails, the roadside device 2 repeatedly transmits the upload restart request at a certain interval.

[0185] The roadside device 2 forwards the upload restart request to (at Fig. 10B In the example, the server 3 is contacted 3 times, and no response is received from the server 3, an error notification is sent to the vehicle-mounted device 1 (S121). The error notification can be based on, for example, the HTTP status code 500.

[0186] The vehicle-mounted device 1 transmits an upload restart request to the roadside device 2 in response to receipt of the error notification in S121 (S122). The upload restart request includes identification information of the data D1 assigned by the server 30.

[0187] In response to receiving the upload restart request in S122 , the roadside device 2 transfers the upload restart request for the data D1 to the server 3 .

[0188] Here, the disconnection of the communication circuit between the roadside device 2 and the server 3 continues. The forwarding of the upload restart request by the roadside device 2 fails, and the roadside device 2 repeatedly forwards the upload restart request at a certain interval.

[0189] The roadside device 2 forwards the upload restart request to (at Fig. 10B In the example, 3 times) server 3, if no response is received from server 3, an error notification is sent to the vehicle-mounted device 1 (S123).

[0190] The vehicle-mounted device 1 transmits an upload restart request to the roadside device 2 in response to receipt of the error notification in S123 (S124).

[0191] Here, the communication circuit between the roadside device 2 and the server 3 is restored. The roadside device 2 transfers the upload restart request of S124 to the server 3 (S125). The transfer of the upload restart request by the roadside device 2 is successful.

[0192] When receiving the upload restart request in S125 , the server 3 acquires the received total data size of the data corresponding to the identification information.

[0193] The server 3 compares the received total data size of the data D1 and the UL data size. Since the communication circuit is disconnected, the upload of the data D1 from the roadside device 2 is interrupted in the middle, so the server 3 determines that the received total data size of the data D1 is smaller than the UL data size, and sends the re-upload information to the roadside device 2 (S126). The re-upload information includes the information of the received total data size of the data D1. Fig. 10B The "Number of bytes sent: N" shown in S126 indicates the total received data size of the data D1 included in the re-upload information. The re-upload information may be based on, for example, HTTP status code No. 100.

[0194] The roadside device 2 transfers the re-upload information of S126 to the vehicle-mounted device 1 (S127).

[0195] In addition, the vehicle-mounted device 1 restarts data transfer based on the reception of the re-upload information in S127. The vehicle-mounted device 1 restarts data transfer from the N+1 byte data based on the information of the received total data size included in the re-upload information. Fig. 10B In the above process, the upload completion responses S57 and S58 may be omitted.

[0196] As described above, after holding the forwarding of the upload restart request, the CPU 22 of the roadside device 2 sends an error notification to the vehicle-mounted device 1 when the forwarding of the upload restart request is started, that is, when the upload restart request is not received by the server 3. As a result, the vehicle-mounted device 1 can resend the upload restart request to the roadside device 2 and upload data appropriately.

[0197] Fig.11 Yes means Figure 1 The timing diagram of the operation example of the communication system. Fig.11 The dashed box symbol is shown with Figure 6 The actions of the symbols shown correspond to the following. Fig.11 The dashed box S21 and Figure 6 The operation of S21 shown corresponds to this.

[0198] like Fig.11 The sequence shown in the figure shows an operation example when the wireless communication is disconnected in the wireless communication path between the vehicle-mounted device 1 and the roadside device 2 after the data upload of the second block of data D1 from the vehicle-mounted device 1 to the roadside device 2 is completed (see Fig.11 In addition, if Fig.11 The sequence shown in the figure shows an example of operation when the wireless communication is disconnected in the wireless communication path between the vehicle-mounted device 1 and the roadside device 2 when the roadside device 2 receives the data transfer completion response of the second block of data D1 from the server 3 (see Fig.11 ).

[0199] like Fig.11 The processing of S41 to S49 shown is the same as the processing of S41 to S49 shown in FIG. 7 , and the description thereof is omitted.

[0200] like Fig.11 As shown, the vehicle-mounted device 1 transfers the second block of the data D1 as the next block (S141). The vehicle-mounted device 1 transfers the data using HTTP communication, for example.

[0201] The roadside device 2 transfers the second block of the data D1 transferred in S141 to the server 3 ( S142 ).

[0202] The vehicle-mounted device 1 ends the data transfer to the roadside device 2 (S143).

[0203] Here, the wireless communication between the vehicle-mounted device 1 and the roadside device 2 is disconnected. For example, when the vehicle-mounted device 1 moves out of the communication area of ​​the roadside device 2, the wireless communication is disconnected. Or, due to the influence of interference, the wireless communication between the vehicle-mounted device 1 and the roadside device 2 is disconnected. In addition, the roadside device 2 continues to forward the data D1 received from the vehicle-mounted device 1 to the server 3 of the second block.

[0204] When the data transfer of the roadside machine 2 is completed, the server 3 sends a data transfer completion response (S144) to the roadside machine 2. For example, when the data size of the data D1 received from the roadside machine 2 is consistent with the data size recorded in the HTTP header of the data transfer, the server 3 sends a data transfer completion response to the roadside machine 2. The data transfer completion response can be based on, for example, the HTTP status code 200.

[0205] Here, since the wireless communication between the vehicle-mounted device 1 and the roadside device 2 is disconnected, the roadside device 2 transfers the data transfer completion response of S144 to the vehicle-mounted device 1 , but the transfer fails due to the disconnection of the wireless communication.

[0206] When the wireless communication between the vehicle-mounted device 1 and the roadside device 2 is restored and the data transfer end response is not received from the server 3 , the vehicle-mounted device 1 transmits an upload restart request to the roadside device 2 ( S145 ).

[0207] The roadside device 2 transfers the upload restart request of S145 to the server 3 (S146). Since the roadside device 2 has completed the data transfer of the second block of data D1, it transfers the upload restart request to the server 3 without holding it.

[0208] When receiving the upload restart request in S146 , the server 3 acquires the received total data size of the data D1 corresponding to the identification information.

[0209] The server 3 compares the received total data size of the acquired data D1 with the UL data size. When the received total data size of the data D1 is consistent with the UL data size, the server 3 sends an upload completion response to the roadside device 2 (S147). The upload completion response may also be based on, for example, HTTP status code 200.

[0210] The roadside device 2 transmits an upload completion response to the vehicle-mounted device 1 in response to reception of the upload completion response in S147 ( S148 ).

[0211] As described above, after the data transfer is completed, if the wireless communication with the roadside device 2 is disconnected and no data transfer completion response is received from the server 3, the CPU 11 of the vehicle-mounted device 1 sends an upload restart request to the server 3 after the wireless communication with the roadside device 2 is restored. As a result, the vehicle-mounted device 1 can properly upload the data D1.

[0212] Fig.12 Yes means Figure 1 The timing diagram of the operation example of the communication system. Fig.12 The dashed box symbol is shown with Figure 6 The actions of the symbols shown correspond to the following. Fig.12The dashed box S21 and Figure 6 The operation of S21 shown corresponds to this.

[0213] like Fig.12 The sequence shown in the figure shows an operation example when the wireless communication is disconnected on the wireless communication path between the vehicle-mounted device 1 and the roadside device 2 before the data transfer from the vehicle-mounted device 1 to the roadside device 2 is completed (during data transfer) (see Fig.12 In addition, if Fig.12 The sequence shown in the figure shows an operation example in which the wireless communication is disconnected on the wireless communication path between the vehicle-mounted device 1 and the roadside device 2 before the data transfer from the vehicle-mounted device 1 to the roadside device 2 is completed, so the data transfer from the vehicle-mounted device 1 to the server 3 is interrupted (see Fig.12 ).

[0214] like Fig.12 The processing of S41 to S49 shown is the same as the processing of S41 to S49 shown in FIG. 7 , and the description thereof is omitted.

[0215] like Fig.12 As shown, the vehicle-mounted device 1 transfers the next block of data (S151). The vehicle-mounted device 1 transfers the data using HTTP communication, for example.

[0216] The roadside device 2 transfers the data transferred in S151 to the server 3 ( S152 ).

[0217] Here, before the next block of data transfer is completed (during data transfer), the wireless communication between the vehicle-mounted device 1 and the roadside device 2 is disconnected. For example, when the vehicle-mounted device 1 moves out of the communication area of ​​the roadside device 2, the wireless communication between the vehicle-mounted device 1 and the roadside device 2 is disconnected. Alternatively, the wireless communication between the vehicle-mounted device 1 and the roadside device 2 is disconnected due to the influence of interference.

[0218] The disconnection of wireless communication interrupts the upload (data transfer) of the second block of data D1 in the vehicle-mounted device 1. The roadside device 2 transfers the data received from the vehicle-mounted device 1 to the server 3 until wireless communication between the vehicle-mounted device 1 and the roadside device 2 is restored.

[0219] When the vehicle-mounted device 1 reconnects the wireless communication with the roadside device 2 after the wireless communication is disconnected, the vehicle-mounted device 1 transmits an upload restart request to the roadside device 2 (S153). The upload restart request includes the identification information assigned by the server 30.

[0220] The roadside device 2 transfers the upload restart request of S153 to the server 3 (S154). The upload restart request includes the identification information of the data D1 given by the server 3.

[0221] In addition, when the roadside machine 2 receives a request to resume uploading from the vehicle-mounted device 1, if all the data received from the vehicle-mounted device 1 (the second block of data D1 received before the wireless communication of the wireless communication path is disconnected) is forwarded to the server 3, the forwarding of the request to resume uploading to the server 3 is not retained.

[0222] When receiving the upload restart request in S154 , the server 3 acquires the received total data size of the data D1 corresponding to the identification information.

[0223] The server 3 compares the received total data size of the acquired data D1 with the UL data size. Since the vehicle-mounted device 1 interrupts the upload of the second block of data D1 by cutting off the wireless communication of the wireless communication path, the server 3 determines that the received total data size of data D1 is smaller than the UL data size, and sends the re-upload information to the roadside device 2 (S155). The re-upload information includes the information of the received total data size of data D1. Fig.12 The "Number of bytes sent: N" shown in S155 indicates the total received data size of the data D1 included in the re-upload information. The re-upload information may be based on, for example, HTTP status code No. 100.

[0224] The roadside device 2 transfers the re-upload information of S155 to the vehicle-mounted device 1 (S156).

[0225] The vehicle-mounted device 1 restarts data transfer in response to reception of the re-upload information in S156 (S157). The vehicle-mounted device 1 restarts data transfer from data of N+1 bytes based on the information of the received total data size included in the re-upload information.

[0226] The roadside device 2 transfers the data transferred in S157 to the server 3 ( S158 ).

[0227] When the uploading of the data to the roadside device 2 is completed, the server 3 transmits a data transfer completion response to the roadside device 2 ( S159 ).

[0228] The roadside device 2 transfers the data transfer completion response of S159 to the vehicle-mounted device 1 (S160). Fig.12 In the above process, the upload completion responses S57 and S58 may be omitted.

[0229] As described above, the CPU 11 of the vehicle-mounted device 1 is disconnected from the wireless communication with the roadside device 2 before the data transfer is completed. If the re-upload information is not received from the server 3, the CPU 11 sends the upload restart request to the server 3 after the wireless communication with the roadside device 2 is restored. The CPU 32 of the server 3 sends the re-upload information to the vehicle-mounted device 1 in accordance with the upload restart request from the vehicle-mounted device 1. As a result, the vehicle-mounted device 1 can properly upload data.

[0230] Figure 13 and Fig. 13B Yes means Figure 1 A timing diagram of an operation example of a communication system. Fig.13A The timing shown follows Fig. 13B As shown in Figure 13 and Fig. 13B The dashed box symbol is shown with Figure 6 The actions of the symbols shown correspond to the following. Fig.13A and Fig. 13B The dashed box S21 shown is Figure 6 The operation of S21 shown corresponds to this.

[0231] like Fig.13A as well as Fig. 13B The sequence shown in the figure shows an operation example in which the wireless communication between the vehicle-mounted device 1 and the roadside device 2 is disconnected after the data transfer from the vehicle-mounted device 1 to the roadside device 2 is completed (see Fig. 13B In addition, if Fig.13A and Fig. 13B The sequence shown shows an example of operation when the communication circuit between the roadside device 2 and the server 3 is disconnected before the data transfer from the roadside device 2 to the server 3 is completed (see the hatched portion S26 on the right side of FIG. 13 ). Fig.13A as well as Fig. 13B The sequence diagram shows an operation example in which the vehicle-mounted device 1 transmits an upload restart request after the wireless communication between the vehicle-mounted device 1 and the roadside device 2 and the communication between the roadside device 2 and the server 3 are restored.

[0232] like Fig.13A The processing of S41 to S49 shown in FIG. Fig. 7A The processes of S41 to S49 shown are the same, and the description thereof is omitted.

[0233] like Fig. 13B As shown, the vehicle-mounted device 1 transfers the second block of the data D1 as the next block (S171). The vehicle-mounted device 1 transfers the data using HTTP communication, for example.

[0234] The roadside device 2 transfers the second block of data D1 transferred in S171 to the server 3 ( S172 ).

[0235] The vehicle-mounted device 1 ends the data transfer to the roadside device 2 (S173).

[0236] Here, the wireless communication in the wireless communication path between the vehicle-mounted device 1 and the roadside device 2 is disconnected. For example, the wireless communication is disconnected when the vehicle-mounted device 1 moves out of the communication area of ​​the roadside device 2. Alternatively, the wireless communication between the vehicle-mounted device 1 and the roadside device 2 is disconnected due to the influence of interference.

[0237] In addition, while the roadside device 2 was transferring data from the vehicle-mounted device 1 to the server 3, the communication circuit between the roadside device 2 and the server 3 was disconnected. The roadside device 2 timed out before completing the data transfer from the vehicle-mounted device 1. In other words, the roadside device 2 interrupted the data transfer from the vehicle-mounted device 1 midway.

[0238] When the vehicle-mounted device 1 reconnects the wireless communication with the roadside device 2 after the wireless communication is disconnected, the vehicle-mounted device 1 transmits an upload restart request to the roadside device 2 (S174). The upload restart request includes the identification information of the data D1 given by the server 30.

[0239] The roadside device 2 transmits an upload restart request to the server 3 in response to reception of the upload restart request in S174 (S175). The upload restart request includes identification information of the data D1 assigned by the server 30.

[0240] Furthermore, when the upload restart request of S175 is sent, the roadside device 2 ends the data transfer process of the vehicle-mounted device 1 to the server 3 (timeout), and therefore the transfer of the upload restart request to the server 3 may not be held.

[0241] When receiving the upload restart request in S175 , the server 3 acquires the received total data size of the data D1 corresponding to the identification information.

[0242] The server 30 compares the received total data size of the data D1 and the UL data size. Since the roadside device 2 interrupts the upload of the data D1 in the middle by cutting off the communication between the roadside device 2 and the server 3, the server 3 determines that the received total data size of the data D1 is smaller than the UL data size, and sends the re-upload information to the roadside device 2 (S176). The re-upload information includes the information of the received total data size of the data D1. Fig. 13B The "Number of bytes sent: N" shown in S176 indicates the total size of received data included in the re-upload information. The re-upload information may be based on, for example, HTTP status code 100.

[0243] The roadside device 2 transfers the re-upload information of S176 to the vehicle-mounted device 1 (S177).

[0244] The vehicle-mounted device 1 restarts data transfer in response to reception of the re-upload information in S177 (S178). The vehicle-mounted device 1 receives information on the total data size based on the data D1 included in the re-upload information, and restarts data transfer from data of N+1 bytes.

[0245] The roadside device 2 transfers the second block of data D1 transferred in S178 to the server 3 ( S179 ).

[0246] When the uploading of the roadside device 2 is completed, the server 3 transmits a data transfer completion response to the roadside device 2 ( S180 ).

[0247] The roadside device 2 transfers the data transfer completion response of S180 to the vehicle-mounted device 1 (S181). Fig. 13B In the above process, the upload completion responses S57 and S58 may be omitted.

[0248] As described above, after the data transfer is completed, if the wireless communication with the roadside device 2 is disconnected and no data transfer completion response is received from the server 3, the CPU 11 of the vehicle-mounted device 1 sends an upload restart request to the server 3 after the wireless communication with the roadside device 2 is restored. If the upload of the vehicle-mounted device 1 is not completed, the CPU 32 of the server 3 sends the re-upload information including the information of the received total data size to the vehicle-mounted device 1. As a result, the vehicle-mounted device 1 can properly upload data.

[0249] (Variant 1)

[0250] The CPU 22 of the roadside device 2 may transmit information for controlling the transmission interval of the upload restart request transmitted by the vehicle-mounted device 1 to the vehicle-mounted device 1 while the forwarding of the upload restart request is on hold. For example, the CPU 22 may make the transmission interval of the upload restart request of the vehicle-mounted device 1 after the forwarding of the upload restart request is on hold longer than the transmission interval before the forwarding is on hold. Thus, during the period when the roadside device 2 is on hold to forward the upload restart request, it is possible to suppress the vehicle-mounted device 1 from frequently transmitting the upload restart request to the roadside device 2.

[0251] (Variant 2)

[0252] The CPU 12 of the vehicle-mounted device 1 may also set the transmission interval of the upload restart request to be longer than that before the communication with the roadside device 2 is disconnected after the communication with the roadside device 2 is disconnected. Thus, while the roadside device 2 holds the forwarding of the upload restart request, it is possible to suppress the vehicle-mounted device 1 from frequently sending the upload restart request to the roadside device 2. In addition, the CPU 21 may also restore the transmission interval of the upload restart request when the communication with the roadside device 2 is restored.

[0253] In the above-mentioned embodiments, the expression “…part” used in each structural element may be replaced by other expressions such as “…circuitry”, “…device”, “…component”, “…unit” or “…module”.

[0254] The above embodiments are described with reference to the accompanying drawings, but the present invention is not limited to the above examples. Those skilled in the art understand that various variations or modifications can be thought of within the scope of the claims. Such variations or modifications are also understood to belong to the technical scope of the present disclosure. In addition, the various structural elements in the embodiments can be combined arbitrarily without departing from the scope of the present disclosure.

[0255] The present disclosure can be implemented by software, hardware or software in cooperation with hardware. Each functional block used in the description of the above-mentioned embodiments is partially or entirely implemented as an LSI of an integrated circuit, and each process described in the above-mentioned embodiments can also be partially or entirely controlled by an LSI or a combination of LSIs. LSI can be composed of individual chips or a chip in a manner that includes part or all of the functional blocks. LSI can also have data input and output. LSI is sometimes also referred to as IC, system LSI, super LSI, and ultra LSI, depending on the degree of integration.

[0256] The method of integrated circuitization is not limited to LSI, and can also be implemented by a dedicated circuit, a general-purpose processor or a dedicated processor. In addition, an FPGA (Field Programmable Gate Array) that can be programmed after LSI manufacturing, and a reconfigurable processor that can reconfigure the connection and setting of the circuit unit inside the LSI can also be used. The present disclosure can also be implemented as digital processing or analog processing.

[0257] Furthermore, if integrated circuit technology that replaces LSI emerges due to advances in semiconductor technology or other derived technologies, it is of course possible to use this technology to integrate functional blocks. Biotechnology, etc. may be applied.

[0258] The present disclosure can be implemented in all types of devices, equipment and systems (collectively referred to as communication devices) with communication functions. The communication device may also include a wireless transceiver (transceiver) and a processing / control circuit. The wireless transceiver may also include a receiving part and a transmitting part, or they may function as a function. The wireless transceiver (transmitting unit and receiving unit) may include an RF (Radio Frequency: Radio Frequency) module and one or more antennas. The RF module may include an amplifier, an RF modulator / demodulator or a module similar to them. As non-limiting examples of communication devices, telephones (portable phones, smart phones, etc.), tablet computers, personal computers (PCs) (laptops, desktops, notebooks, etc.), cameras (digital still cameras / camcorders, etc.), digital players (digital audio / video / players, etc.), wearable devices (wearable cameras, smart watches, tracking devices, etc.), game consoles, digital book readers, stereoscopic phantom devices (remote health care workers / caregiver prescriptions) devices, vehicles with communication functions or transporters (cars, airplanes, ships) and combinations of the above-mentioned various devices can be cited.

[0259] Communication devices are not limited to portable or movable communication devices, but also include all types of devices, equipment, and systems that cannot be carried or fixed, such as smart home devices (home appliances, lighting equipment, smart meters or measuring equipment, control panels, etc.), vending machines, and all other "things" that may exist on the IoT (Internet of Things) network.

[0260] The communication includes data communication based on a cellular system, a wireless LAN system, a communication satellite system, etc. as well as data communication based on a combination of these.

[0261] In addition, the communication device also includes devices such as a controller and a sensor connected or linked to the communication device that performs the communication function described in the present disclosure. For example, it includes a controller and a sensor that generate control signals and data signals used by the communication device that performs the communication function of the communication device.

[0262] In addition, the communication device includes infrastructure equipment that communicates with the above-mentioned non-limited various devices or controls these various devices, such as base stations, access points, and all other devices, equipment, and systems.

[0263] (Summary of this disclosure)

[0264] The roadside machine involved in the present disclosure comprises: a communication circuit that receives data sent from a vehicle-mounted device and forwards it to a server; and a control circuit that reserves the forwarding of the upload restart request to the server when the communication circuit receives a request to resume uploading the data from the vehicle-mounted device during the forwarding of the data to the server.

[0265] In the roadside device according to the present disclosure, the control circuit transfers the upload restart request to the server after receiving a data transfer completion response of the data from the server via the communication circuit.

[0266] In the roadside device according to the present disclosure, the control circuit receives re-upload information including information indicating an amount of data already uploaded of the data from the server via the communication circuit, and transfers the re-upload information to the vehicle-mounted device.

[0267] In the roadside device according to the present disclosure, when communication with the server is disconnected and times out, the control circuit transfers the upload resumption request to the server via the communication circuit.

[0268] In the roadside device involved in the present disclosure, the control circuit starts forwarding the upload restart request after retaining the forwarding of the upload restart request, but sends an error notification to the vehicle-mounted device via the communication circuit when the server does not receive the upload restart request.

[0269] In the roadside device according to the present disclosure, the control circuit transmits information for controlling a transmission interval of the upload restart request transmitted by the vehicle-mounted device to the vehicle-mounted device via the communication circuit while withholding the forwarding of the upload restart request.

[0270] The vehicle-mounted device involved in the present disclosure comprises: a communication circuit that communicates with a roadside device having a forwarding circuit and a control circuit, the forwarding circuit receiving data and forwarding it to a server, the communication circuit retaining the forwarding of the upload restart request to the server when receiving a request for resuming upload of the data from the vehicle-mounted device during the forwarding of the data to the server; and a control circuit that sets the sending interval of the upload restart request to be longer than that before the communication with the roadside device is cut off after the communication with the roadside device is cut off.

[0271] The communication system involved in the present disclosure has a vehicle-mounted device and a roadside machine, the vehicle-mounted device has: a vehicle-mounted device communication circuit for sending data; and a vehicle-mounted device control circuit for sending a request to resume uploading the data, and the roadside machine has: a roadside machine communication circuit for receiving the data and transmitting it to a server; and a roadside machine control circuit for retaining the forwarding of the upload resume request to the server when receiving the upload resume request for the data during the forwarding of the data to the server.

[0272] The communication method disclosed herein receives data sent from a vehicle-mounted device, forwards the data to a server, and when receiving a request to resume uploading the data from the vehicle-mounted device during the forwarding of the data to the server, retains the forwarding of the request to resume uploading to the server.

[0273] The disclosures of the specification, drawings, and abstract of Japanese Patent Application No. 2020-042246 filed on March 11, 2020 are incorporated herein by reference in their entirety.

[0274] Industrial Applicability

[0275] The present disclosure is useful for a communication system that uploads data from a vehicle-mounted device to a server.

[0276] Description of Reference Numerals

[0277] 1. Vehicle-mounted device

[0278] Dual side machine

[0279] 3 Servers

[0280] 4. Network

[0281] 11, 21a, 21b, 31 communication device

[0282] 12, 22, 32 CPU

[0283] 13, 23, 33 storage device.

Claims

1. A roadside machine, comprising: a communication circuit that receives data sent from the vehicle-mounted device and forwards it to the server; and a control circuit for holding forwarding the upload restart request to the server when the communication circuit receives a request for restarting upload of the data from the vehicle-mounted device during the transfer of the data to the server, The control circuit transfers the upload restart request to the server after receiving a data transfer completion response of the data from the server through the communication circuit.

2. The roadside machine according to claim 1, wherein: The control circuit receives re-upload information including information indicating an amount of data already uploaded from the server via the communication circuit, and transfers the re-upload information to the vehicle-mounted device.

3. The roadside machine according to claim 1, wherein: The control circuit transfers the upload resumption request to the server via the communication circuit when communication with the server is disconnected and times out.

4. The roadside machine according to claim 1, wherein: The control circuit starts transferring the upload restart request after holding the transfer of the upload restart request, but transmits an error notification to the vehicle-mounted device via the communication circuit if the server does not receive the upload restart request.

5. The roadside machine according to claim 1, wherein: The control circuit transmits information for controlling a transmission interval of the upload restart request transmitted by the vehicle-mounted device to the vehicle-mounted device via the communication circuit, when the transfer of the upload restart request is withheld.

6. A vehicle-mounted device, comprising: a communication circuit that communicates with a roadside device having a forwarding circuit and a control circuit, the forwarding circuit receiving data and forwarding the data to a server, the communication circuit, when receiving a request to resume uploading the data from a vehicle-mounted device during the forwarding of the data to the server, withholding the forwarding of the request to resume uploading to the server; and The control circuit sets the transmission interval of the upload restart request to be longer than that before the communication with the roadside device is disconnected after the communication with the roadside device is disconnected, After receiving a data transfer completion response of the data from the server, the upload restart request is transferred to the server.

7. A communication system comprising a vehicle-mounted device and a roadside device, The vehicle-mounted device has: A vehicle-mounted device communication circuit for transmitting data; and The vehicle-mounted device control circuit sends a request to resume uploading the data. The roadside machine has: A roadside machine communication circuit receives the data and transmits it to the server; and The roadside device control circuit, when receiving the upload restart request of the data during the transfer of the data to the server, withholds the transfer of the upload restart request to the server, The roadside device control circuit transfers the upload restart request to the server after receiving a data transfer completion response of the data from the server via the roadside device communication circuit.

8. A communication method, Receive data sent from the vehicle-mounted device, forwarding said data to a server, When a request for resuming uploading the data is received from the vehicle-mounted device during the transfer of the data to the server, the transfer of the request for resuming uploading to the server is suspended; After receiving a data transfer completion response of the data from the server, the upload restart request is transferred to the server.

Images