Vehicle-mounted communication device and push server

Abstract

When the push server (3) receives the push data transmission request from the application server (2) and the push data is received from the push server (3), the in-vehicle communication device (4) transmits the received push data to the in-vehicle electronic control device. A vehicle-mounted communication device is provided with: a notification monitoring unit (4a) that monitors notification of a start-up request from a push server by a first method in which standby power is smaller than that of a second method; and a reception control unit (4b) that receives the push data from the push server in a second scheme in which the data length of the push data that can be received from the push server is longer than the data length of the first scheme.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of Japanese Application No. 2022-082281 filed on May 19, 2022, the entire contents of which are incorporated herein by reference. Technical Field

[0003] The present disclosure relates to a vehicle-mounted communication device and a push server. Background Art

[0004] As one of the remote request services for accessing the application of the vehicle-mounted system from outside the vehicle, a push system for sending push data is provided. The push system sets up an application server and a push server on the cloud side, and sets up an on-board communication machine and an on-board electronic control unit (hereinafter referred to as an on-board ECU (Electronic Control Unit)) on the vehicle side. The push server starts the application on the cloud side through, for example, a smartphone terminal, and if a request for sending push data is received from the application server, the push data is sent to the on-board communication machine. The on-board communication machine sends the push data sent from the push server to the on-board ECU, and passes the push data to the application on the on-board system side mounted on the on-board ECU (for example, refer to Patent Document 1).

[0005] Patent Document 1: Japanese Patent Application Publication No. 2019-192953

[0006] In a vehicle-mounted communication device, it is preferred that the standby power be small when monitoring the reception of push data sent from a push server. In particular, when the vehicle is parked for a long time and the remaining capacity of the vehicle battery needs to be ensured, it is preferred that the standby power be extremely small. However, in a method in which the standby power is relatively small, there is a problem that the data length of the push data that can be received from the push server is short. Summary of the invention

[0007] An object of the present disclosure is to appropriately receive push data transmitted from a push server and appropriately transmit the push data to an in-vehicle communication device.

[0008] According to one aspect of the present disclosure, when the push server receives a push data transmission request from the application server and thus receives push data from the push server, the vehicle-mounted communication device transmits the received push data to the vehicle-mounted electronic control device. The notification monitoring unit monitors the notification of the start request from the push server in a first manner in which the standby power is smaller than the second manner. The reception control unit receives the push data from the push server in a second manner in which the data length of the push data that can be received from the push server is longer than the first manner.

[0009] The notification monitoring of the start request from the push server is performed in a first manner, and the push data from the push server is received in a second manner. By performing the notification monitoring of the start request in the first manner in which the standby power is smaller than that in the second manner, the standby power can be appropriately suppressed. By receiving the push data from the push server in the second manner in which the data length of the push data that can be received from the push server is longer than that in the first manner, the push data sent from the push server can be appropriately received. Thus, the push data sent from the push server can be appropriately received while the standby power is appropriately suppressed.

[0010] According to one aspect of the present disclosure, when a push server receives a push data transmission request from an application server, the push data is transmitted to the vehicle-mounted communication device. The notification control unit notifies the vehicle-mounted communication device of the start request in a first manner in which the standby power in the vehicle-mounted communication device is smaller than in a second manner. The push data transmission control unit transmits the push data to the vehicle-mounted communication device in a second manner in which the data length of the push data that can be transmitted to the vehicle-mounted communication device is longer than in the first manner.

[0011] The notification of the start request to the vehicle-mounted communication device is performed by the first method, and the push data is sent to the vehicle-mounted communication device by the second method. By sending the push data to the vehicle-mounted communication device by the second method in which the data length of the push data that can be sent to the vehicle-mounted communication device is longer than that of the first method, the push data can be appropriately sent to the vehicle-mounted communication device. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] The above-mentioned object and other objects, features and advantages of the present disclosure will become more apparent through the following detailed description with reference to the accompanying drawings.

[0013] Figure 1 The first embodiment is shown, which is a diagram showing the overall structure of the push system.

[0014] Figure 2 This is the functional block diagram of the vehicle-mounted communication device and the push server.

[0015] Figure 3 is a timing diagram,

[0016] Figure 4 is a timing diagram,

[0017] Figure 5 is a timing diagram,

[0018] Figure 6 is a timing diagram,

[0019] Figure 7 The second embodiment is shown, which is a functional block diagram of an in-vehicle communication device and a push server.

[0020] Figure 8 is a timing diagram,

[0021] Fig. 9 is a timing diagram,

[0022] Fig.10 is a timing diagram,

[0023] Fig.11 is a timing chart showing the third embodiment,

[0024] Fig.12 is a timing diagram,

[0025] Fig.13 is a timing diagram,

[0026] Fig.14 is a timing chart showing the fourth embodiment,

[0027] Fig.15 is a timing diagram,

[0028] Fig.16 is a timing diagram,

[0029] Fig.17 It is a timing diagram. DETAILED DESCRIPTION

[0030] Hereinafter, a plurality of embodiments will be described with reference to the drawings. The description of the same parts among the plurality of embodiments may be omitted.

[0031] (First Embodiment)

[0032] Reference Figure 1 to Figure 6 A first embodiment will be described. Figure 1 The push system 1 shown in the figure includes an application server 2 and a push server 3 provided on the cloud side, an on-vehicle communication device 4 provided on the vehicle side, and an on-vehicle ECU 5. An application 6 for realizing a remote request service is mounted on the on-vehicle ECU 5. The push system 1 is a system capable of sending push data from the application server 2 to the application 6.

[0033] For example, if a user uses a terminal such as a smartphone to start an application based on remote control such as starting the air conditioner or locking the doors before getting on the vehicle and performs specified operations, a request for sending push data commanding the start of the air conditioner and the locking of the doors is sent from the application server 2 to the push server 3. The push data is sent to the on-board ECU 5 via the on-board communication device 4 and is passed to the application 6 that enables the start of the air conditioner, locking of the doors, etc.

[0034] exist Figure 1In the example, a configuration in which one push server 3 is provided for multiple application servers 2 on the cloud side is illustrated, but a configuration in which multiple push servers 3 are provided for multiple application servers 2 is also possible. In addition, a configuration in which one vehicle-mounted communication device 4 is provided for multiple vehicle-mounted ECUs 5 on the vehicle side is illustrated, but a configuration in which multiple vehicle-mounted communication devices 4 are provided for multiple vehicle-mounted ECUs 5 is also possible.

[0035] The push system 1 adopts the automobile wireless communication platform 7. The automobile wireless communication platform 7 realizes functions through the ACP cloud 8 on the cloud side and the ACP engine 9 on the vehicle side, and can make a secure connection between the application server 2 and the application 6 anytime and anywhere. To be detailed, the vehicle-mounted ECU 5 is disconnected when the vehicle is parked, and the power states are different from each other. In addition, the system configuration of the vehicle-mounted ECU 5 in each vehicle is different from each other. The automobile wireless communication platform 7 hides such differences in the power state of the vehicle-mounted ECU 5 and the differences in the system configuration of each vehicle from the application server 2 side. As a result, it is possible to achieve a simulated always-on connection for each vehicle unit, such as all the vehicle-mounted ECUs 5 are always connected to the network outside the vehicle.

[0036] The following describes a cloud-side system and a vehicle-side in-vehicle system that are equipped with the automotive wireless communication platform 7 .

[0037] (1) Cloud-side system

[0038] First, the vehicle-mounted system on the vehicle side is explained. The application server 2 is a server that functions as a source of a request to send push data. The application server 2 manages at least one of an application ID and a token that identifies the application 6. When the application server 2 sends a request to send push data to the push server 3, the application server 2 provides the application ID or the token as request information together with the message body sent to the application 6. When the application server 2 uses the token as request information, it reads out the token that has established a corresponding relationship with the destination of the push data. The token becomes the key information that determines the destination of the push data in the push server 3 and the vehicle-mounted system.

[0039] The push server 3 is a transmission source of push data, and includes a configuration that functions as an ACP cloud 8 that implements the cloud-side functions of the automotive wireless communication platform 7. The push server 3 includes a microcontroller having a processor 10, a RAM 11, and a storage medium 12 as a main body. The push server 3 performs various operations by executing a control program stored in the storage medium 12 through the processor 10, thereby implementing the cloud-side functions of the automotive wireless communication platform 7.

[0040] The push server 3 is connected to the vehicle-mounted communication device 4 via a communication line based on wireless communication via a mobile communication network, and can send push data to the vehicle-mounted communication device 4 while the communication line is connected. The mobile communication network includes, for example, a mobile phone network, Wi-Fi (registered trademark), and V2X (Vehicle-to-Anything). When the push server 3 receives a request to send push data from the application server 2, it selects the vehicle-mounted communication device 4 as the destination of the push data, and sends the push data to the vehicle-mounted communication device 4 selected as the destination.

[0041] The push server 3 provides functions such as authentication of communication objects, encryption of communication contents, and detection of tampering through TLS (Transport Layer Security) processing, and provides data communication functions using TCP / IP, UDP / IP and protocols other than these, enabling secure data communication with the application server 2 and the on-board communication device 4.

[0042] The push server 3 can retry sending the push data within a specified time. When sending push data, there are scenarios where a response from the vehicle system is required immediately, and scenarios where the push data only needs to reach the notification destination. A retry period is set corresponding to the response to the request. If the sending of the push data fails, the push server 3 retries the sending of the push data within a specified time before the retry period expires based on the retry period set according to the content of the push data. If the retry period expires while the sending of the push data remains in a state of failure, the push server 3 determines that the sending of the push data has failed and ends the sending of the push data.

[0043] (2) Vehicle-side onboard system

[0044] Next, the vehicle-mounted system on the vehicle side is explained. The vehicle-mounted communication device 4 is called TCU (Telematics Control Unit) or DCM (Data Communication Module), etc., and is the destination of push data. It includes a structure that functions as an ACP engine 9 that realizes the vehicle-side functions of the automobile wireless communication platform 7. The vehicle-mounted communication device 4 has a microcontroller having a processor 13, RAM 14, and a storage medium 15 as a main body. The vehicle-mounted communication device 4 performs various actions by executing a control program stored in the storage medium 15 through the processor 13, thereby realizing the vehicle-side functions of the automobile wireless communication platform 7.

[0045] The vehicle-mounted communication device 4 is connected to a plurality of vehicle-mounted ECUs 5 via an in-vehicle network. Examples of the in-vehicle network include Ethernet (registered trademark), CAN (Controller Area Network) (registered trademark), FLEXRAY (registered trademark), CXPI (Clock Extension Peripheral Interface) (registered trademark), and LIN (Local Interconnect Network). The in-vehicle network is provided for each system such as a powertrain system, a chassis system, a body system, a multimedia system, and a safety system.

[0046] The vehicle-mounted communication device 4 is connected to the push server 3 via a communication line based on wireless communication via a mobile communication network, and can receive push data from the vehicle-mounted communication device 4 while the communication line is connected. When the vehicle-mounted communication device 4 receives push data from the push server 3, it selects the vehicle-mounted ECU 5 as the sending destination, and sends the push data to the vehicle-mounted ECU 5 selected as the sending destination.

[0047] The vehicle-mounted communication device 4 provides functions such as authentication of the communication object, encryption of the communication content, and detection of tampering through TLS processing, and provides a data communication function using TCP / IP, UDP / IP, and protocols other than these. There are cases where secure data communication can be performed between the vehicle-mounted communication device 4 and the push server 3, and between the vehicle-mounted communication device 4 and the vehicle-mounted ECU 5.

[0048] The vehicle-mounted communication device 4 can maintain an online state connected to the communication network even when the main power source of the vehicle is turned off, specifically, when the ignition switch is turned off, for example, while the vehicle is parked. The vehicle-mounted communication device 4 monitors the connection state with the push server 3 via wireless communication and the progress state of the push data transmission on the in-vehicle network. The vehicle-mounted communication device 4 cooperates with the push server 3 and can confirm the mutual connection between the vehicle-mounted communication device 4 and the push server 3. The mutual connection confirmation between the vehicle-mounted communication device 4 and the push server 3 is sometimes called life and death monitoring.

[0049] When the push data does not reach the destination, the vehicle-mounted communication device 4 notifies the transmission source of the failure of the push data transmission together with the reason information associated with the failure. As an example, when the application 6 or the vehicle-mounted ECU 5 that is the destination of the push data does not exist in the in-vehicle network, the vehicle-mounted communication device 4 associates the failure of the push data transmission with such reason information and notifies the push server 3 that is the transmission source. In addition, when the push data transmission to the application 6 fails, the vehicle-mounted communication device 4 associates the failure of the push data transmission with such reason information and notifies the push server 3 that is the transmission source.

[0050] The on-board communication device 4 determines the destination information and the status information as ECU information related to the on-board ECU 5 that is the destination of the push data. The destination information is sometimes also referred to as the destination information. The destination information is information that can determine the on-board ECU 5 that is the destination of the push data from a plurality of on-board ECUs 5. The on-board communication device 4 obtains the destination information with reference to the application ID or the token. The status information is information that can determine the power state (on / off state) of the on-board ECU 5 that is determined as the destination. In detail, the power-off state here refers to a state in which the on-board ECU 5 moves from the start state to the stop state due to the disconnection of the ignition switch, etc. At this time, the on-board ECU 5 becomes a state in which it can receive the start request in a power-saving manner, but on the other hand, it cannot perform data communication. When the power of the on-board ECU 5 that is determined as the destination based on the status information is in the off state, the on-board communication device 4 performs a startup process to start the on-board ECU 5 and turn the power on (start-up state).

[0051] The vehicle-mounted ECU 5 is equipped with one or more application programs 6 and can execute the application programs. The vehicle-mounted ECU 5 has a microcontroller having a processor (not shown), a RAM (not shown), and a storage medium (not shown) as a main body. The vehicle-mounted ECU 5 performs various actions by executing a control program stored in the storage medium through the processor, and acts as a terminal ECU that becomes the final destination of the push data sent from the push server 3. If the vehicle-mounted ECU 5 receives the push data sent from the vehicle-mounted communication device 4, it determines the registration information that is consistent with the application ID or token that establishes a corresponding relationship with the push data, determines the application 6 that becomes the destination of the push data from multiple applications 6, and sends the push data to the application 6 determined as the destination.

[0052] The vehicle-mounted ECU 5 provides an encryption processing function to enable secure data communication between the vehicle-mounted communication device 4 and the application 6. Unlike the vehicle-mounted communication device 4, the vehicle-mounted ECU 5 is in principle in a closed state in order to suppress power consumption when the power supply of the vehicle is disconnected. At this time, the vehicle-mounted ECU 5 is also disconnected from the communication network. In addition, the application 6 may not be installed in a part of the vehicle-mounted ECU 5. In addition, the vehicle-mounted communication device 4 may be provided in the vehicle-mounted system as a structure that also serves as the vehicle-mounted ECU 5, and can be equipped with the application 6.

[0053] In the above configuration, as described above, it is preferred that the standby power is small when monitoring the notification of the push data sent from the push server 3. In particular, when the parking period is long and the remaining capacity of the vehicle battery needs to be ensured, it is preferred that the standby power is extremely small. However, in the method of relatively small standby power, there are problems such as the data length of the push data that can be received from the push server 3 is short or the restriction of safety measures is large. In this regard, in this embodiment, the vehicle-mounted communication device 4 and the push server 3 each have the following functions.

[0054] In the present embodiment, the first method is a short message service (hereinafter referred to as an SMS (Short Message Service) method), and the second method is an MQTT (Message Queuing Telemetry Transport) method. Although the SMS method has a smaller standby power than the MQTT method, the data length of the push data that can be communicated is shorter than that of the MQTT method, and the restrictions on security measures are greater than those of the MQTT method. Although the data length of the push data that can be communicated by the MQTT method is longer than that of the SMS method, and the restrictions on security measures are less than those of the SMS method, the standby power is greater than that of the SMS method. That is, if the SMS method and the MQTT method are compared, the SMS method has an advantage in standby power, and the MQTT method has an advantage in the data length of the push data that can be communicated and the restrictions on security measures.

[0055] like Figure 2 As shown, the vehicle-mounted communication device 4 includes a notification monitoring unit 4a and a reception control unit 4b. The notification monitoring unit 4a performs notification monitoring of the start request from the push server 3 by either SMS or MQTT. The notification monitoring unit 4a establishes a correspondence relationship between notification monitoring information and a device ID that can identify the vehicle-mounted communication device 4 and notifies the push server 3. The notification monitoring information indicates whether the notification monitoring of the start request from the push server 3 is performed by SMS or MQTT. The device ID is equivalent to the device identification information.

[0056] When the notification monitoring unit 4a performs notification monitoring of the start request from the push server 3 by the MQTT method, it monitors whether the suppression condition of the standby power is satisfied. The suppression condition of the standby power is, for example, that a certain period has passed since the vehicle was parked, that the power consumption has reached a threshold since the vehicle was parked, etc. If the notification monitoring unit 4a determines that the suppression condition of the standby power is satisfied, it establishes a connection with the push server 3 by the SMS method, disconnects the connection with the push server 3 by the MQTT method, and performs notification monitoring of the start request from the push server 3 by the SMS method. That is, if the notification monitoring unit 4a determines that the suppression condition of the standby power is satisfied, it switches the method of performing the notification monitoring of the start request from the push server 3 from the MQTT method to the SMS method.

[0057] The receiving control unit 4b receives the push data from the push server 3 by the MQTT method. The receiving control unit 4b receives the push data from the push server 3 by the MQTT method, thereby ensuring a longer data length of the push data that can be received from the push server 3 than when the push data is received by the SMS method, and reducing the restrictions of the security measures compared to when the push data is received by the SMS method.

[0058] The push server 3 includes a notification control unit 3a and a transmission control unit 3b. The notification control unit 3a notifies the vehicle-mounted communication device 4 of the start request by either the SMS method or the MQTT method. The notification control unit 3a determines whether the method of monitoring the notification of the start request in the vehicle-mounted communication device 4 is the SMS method or the MQTT method based on the notification monitoring information notified from the vehicle-mounted communication device 4. If the notification control unit 3a determines that the method of monitoring the notification of the start request in the vehicle-mounted communication device 4 is the SMS method, the notification control unit 3a notifies the vehicle-mounted communication device 4 of the start request by the SMS method. If the notification control unit 3a determines that the method of monitoring the notification of the start request in the vehicle-mounted communication device 4 is the MQTT method, the notification control unit 3a notifies the vehicle-mounted communication device 4 of the start request by the MQTT method.

[0059] Reference Figure 3 to Figure 6 The operation of the above-mentioned configuration will be described.

[0060] The push server 3 notifies the vehicle-mounted communication device 4, which is the destination of the push data, of a start request, and sends the push data to the vehicle-mounted communication device 4 via the MQTT method (S1). When the vehicle-mounted communication device 4 monitors the notification of the start request from the push server 3 via the MQTT method, it starts if the start request is notified from the push server 3 (A1), and sends the received push data to the vehicle-mounted ECU 5 if the push data sent from the push server 3 is received (S2). The push server 3 determines that the sending of the push data to the vehicle-mounted communication device 4 is completed (B1), and notifies the application server 2 of the sending completion notification (S3).

[0061] The vehicle-mounted communication device 4 monitors the establishment of the suppression condition of the standby power. If it is determined that the suppression condition of the standby power is established (A2), an SMS connection with the push server 3 is established (A3), the MQTT connection with the push server 3 is disconnected (A4), and the notification monitoring information is notified to the push server 3 (S4). Thereafter, the vehicle-mounted communication device 4 performs notification monitoring of the start request from the push server 3 via SMS.

[0062] When the push server 3 is notified of the notification monitoring information from the vehicle-mounted communication device 4, the notification monitoring information is stored in correspondence with the vehicle-mounted communication device 4 as the transmission source of the notification monitoring information (B2), and the vehicle-mounted communication device 4 performs notification monitoring of the start request from the push server 3 via SMS.

[0063] Here, when the push server 3 is notified of the push data transmission request from the application server 2 (S5), the push server 3 refers to the notification monitoring information (B3) stored corresponding to the vehicle-mounted communication device 4 as the transmission destination of the push data. When the push server 3 determines that the vehicle-mounted communication device 4 as the transmission destination of the push data performs notification monitoring of the start request from the push server 3 via SMS (B4), the push server 3 notifies the start request via SMS (S6).

[0064] The vehicle-mounted communication device 4 starts up when the push server 3 notifies the start request via SMS (A5), and establishes an MQTT connection with the push server 3 (A6). When the push server 3 determines that the MQTT connection with the vehicle-mounted communication device 4 is established, it identifies the MQTT connection (B5), and sends the push data to the vehicle-mounted communication device 4 as the destination of the push data via MQTT (S7). When the vehicle-mounted communication device 4 receives the push data sent from the push server 3, it sends the received push data to the vehicle-mounted ECU 5 (S8).

[0065] When the vehicle-mounted ECU 5 receives the push data sent from the vehicle-mounted communication device 4, it passes the push data to the application 6 corresponding to the push data, starts the application 6, and controls the remote request service corresponding to the push data. When the vehicle-mounted ECU 5 receives the push data sent from the vehicle-mounted communication device 4, it notifies the vehicle-mounted communication device 4 of the push data reception response (S9). When the vehicle-mounted communication device 4 is notified of the push data reception response from the vehicle-mounted ECU 5, it confirms the arrival of the push data (A7), and notifies the push data reception response to the push server 3 (S10).

[0066] When the push data reception response from the in-vehicle communication device 4 is notified, the push server 3 determines that the transmission of the push data to the in-vehicle communication device 4 is completed (B6), and notifies the application server 2 of the transmission completion notification (S11).

[0067] The vehicle-mounted communication device 4 establishes an SMS connection with the push server 3 (A8), disconnects the MQTT connection with the push server 3 (A9), and notifies the push server 3 of the notification monitoring information (S12). Thereafter, the vehicle-mounted communication device 4 monitors the notification of the start request from the push server 3 via SMS.

[0068] When the push server 3 is notified of the notification monitoring information from the vehicle-mounted communication device 4, the notification monitoring information is stored in correspondence with the vehicle-mounted communication device 4 as the transmission source of the notification monitoring information (B7), and the vehicle-mounted communication device 4 performs the notification monitoring of the start request from the push server 3 via the SMS method. Thereafter, the push server 3 waits for the notification of the transmission request of the push data from the application server 2, and repeats the above-mentioned process.

[0069] In addition, if Figure 5 as well as Figure 6 As shown, if the vehicle-mounted communication device 4 determines that the standby power suppression condition is established (A2), it may determine whether SMS reception is possible (A11), and if it is determined that SMS reception is possible (A11: Yes), the notification monitoring information is notified to the push server 3 (S4). In addition, if the vehicle-mounted communication device 4 determines that SMS reception is not possible and cannot be received (A11: No), it notifies the push server 3 of the push reception end notification.

[0070] As described above, according to the first embodiment, the following effects can be obtained. In the vehicle-mounted communication device 4, notification monitoring of the start request from the push server 3 is performed by SMS, and push data from the push server 3 is received by MQTT. By performing notification monitoring of the start request by SMS, which has a smaller standby power than the MQTT method, the standby power can be appropriately suppressed. By receiving push data from the push server 3 by MQTT, which has a longer data length than the SMS method, the push data sent from the push server 3 can be appropriately received. As a result, the push data sent from the push server 3 can be appropriately received while the standby power is appropriately suppressed. The constraints on security measures when receiving push data sent from the push server 3 can be reduced.

[0071] In addition, if it is determined that the standby power suppression condition is satisfied, the MQTT connection with the push server 3 is disconnected, and an SMS connection with the push server 3 is established. By pre-registering the standby power suppression condition, for example, the standby power can be appropriately suppressed according to the vehicle usage plan. By appropriately suppressing the standby power, for example, theft monitoring can be appropriately implemented while the vehicle is parked, and if it is an electric vehicle, the cruising range can be ensured to be longer when the vehicle is next ridden.

[0072] In the push server 3, the notification of the start request is performed to the vehicle-mounted communication device 4 by the SMS method, and the push data is sent to the vehicle-mounted communication device 4 by the MQTT method. By sending the push data to the vehicle-mounted communication device 4 by the MQTT method, in which the data length of the push data that can be sent to the vehicle-mounted communication device 4 is longer than that of the SMS method, the push data can be appropriately sent to the vehicle-mounted communication device 4.

[0073] (Second Embodiment)

[0074] Reference Figure 7 to Figure 10 The second embodiment is described below. The second embodiment is a configuration in which notification of the start request from the push server 3 is retried in consideration of the fact that the communication guarantee of the SMS method is not sufficiently high.

[0075] The push server 3 includes a retry count determination unit 3c, an elapsed time determination unit 3d, and a transmission failure notification unit 3e in addition to a notification control unit 3a and a transmission control unit 3b. The retry count determination unit 3c determines the number of retries of the notification of the start request to the on-board communication device 4. The elapsed time determination unit 3d determines the elapsed time from the notification of the start request to the on-board communication device 4. If the retry count determination unit 3c determines that the number of retries of the notification of the start request to the on-board communication device 4 has not reached a certain number of times, and the elapsed time determination unit 3d determines that the elapsed time from the notification of the start request to the on-board communication device 4 has reached a certain time, the notification control unit 3a retries the notification of the start request to the on-board communication device 4 by SMS. If the retry count determination unit 3c determines that the number of retries of the notification of the start request to the on-board communication device 4 has reached a certain number of times, the notification control unit 3a stops the retry of the notification of the start request to the on-board communication device 4. When the retry count determining unit 3c determines that the number of retries for notifying the vehicle-mounted communication device 4 of the start request has reached a certain number, the transmission failure notifying unit 3e notifies the application server 2 of a transmission failure indicating that the transmission of push data has failed.

[0076] Reference Figure 8 to Figure 10 The operation of the above-mentioned configuration will be described.

[0077] If the activation request is notified by SMS (S6), the push server 3 determines the number of retries of the notification of the activation request to the vehicle-mounted communication device 4 (B11). If the push server 3 determines that the number of retries has not reached the certain number (B11: No), it determines the elapsed time from the notification of the activation request to the vehicle-mounted communication device 4 (B12). If the push server 3 determines that the elapsed time has reached the certain time (B12: Yes), it retries the notification of the activation request to the vehicle-mounted communication device 4 by SMS (S21), and counts up the number of retries. If the activation request is notified from the push server 3 by SMS, the vehicle-mounted communication device 4 is activated, and thereafter, the same processing as the first embodiment is performed.

[0078] If the push server 3 determines that the number of retries has reached a certain number (B11: Yes), it stops retrying the notification of the start request to the on-vehicle communication device 4, determines that the sending of the push data has failed (B13), and notifies the application server 2 of a sending failure notification indicating that the sending of the push data has failed (S22).

[0079] As described above, according to the second embodiment, in the push server 3, if it is determined that the number of retries has not reached the certain number of times and it is determined that the elapsed time has reached the certain time, the notification of the start request to the on-board communication device 4 is retried by the SMS method. The communication guarantee of the SMS method is not high enough, and it is possible to deal with it appropriately by retrying the notification of the start request to the on-board communication device 4. In addition, if it is determined that the number of retries has reached the certain number of times, the retry of the notification of the start request to the on-board communication device 4 is stopped, and a transmission failure notification indicating that the transmission of the push data has failed is notified to the application server 2. It is possible to impose restrictions on the retry, and it is possible to avoid unnecessary power consumption.

[0080] (Third Embodiment)

[0081] Reference Figure 11 to Figure 13 The third embodiment is described below. In the third embodiment, the vehicle-mounted communication device 4 determines that the standby power suppression condition is satisfied, and if it is determined that SMS reception is possible, notifies the push server 3 of notification monitoring mode switching confirmation.

[0082] When the vehicle-mounted communication device 4 determines that the condition for suppressing the standby power is satisfied (A2), it determines whether SMS reception is possible (A11), and when it determines that SMS reception is possible (A11: Yes), it notifies the push server 3 of the notification monitoring mode switching confirmation (S31). When the push server 3 is notified of the notification monitoring mode switching confirmation from the vehicle-mounted communication device 4, it notifies the application server 2 of the notification monitoring mode switching confirmation (S32).

[0083] If the application server 2 is notified of the notification monitoring mode switching confirmation from the push server 3, it selects the switching of the notification monitoring mode (C21). The application server 2 selects either suppression permission or suppression condition change, and notifies the push server 3 of the notification monitoring mode switching selection (S33). If the push server 3 is notified of the notification monitoring mode switching selection from the application server 2, it determines whether the switching selection is suppression permission or suppression condition change (B21, B22). If the push server 3 determines that suppression permission (B21: Yes), it notifies the vehicle-mounted communication device 4 of the suppression processing permission (S34). If the vehicle-mounted communication device 4 is notified of the suppression processing permission from the push server 3, it notifies the push server 3 of the notification monitoring information (S4). If the push server 3 is notified of the notification monitoring information from the vehicle-mounted communication device 4, it will perform the same processing as the first embodiment thereafter.

[0084] On the other hand, if the push server 3 determines that the switching selection is a suppression condition change (B22: Yes), it notifies the vehicle-mounted communication device 4 of a suppression condition change request (S35). If the vehicle-mounted communication device 4 is notified of the suppression condition change request from the push server 3, it changes the suppression condition (A31) and returns to step A2.

[0085] As described above, according to the third embodiment, the push server 3 notifies the application server 2 of the notification monitoring mode switching confirmation. The user or the system can select whether to allow suppression or to change the suppression condition.

[0086] (Fourth Embodiment)

[0087] Reference Figure 14 to Figure 17 A fourth embodiment will be described. In the fourth embodiment, the push server 3 is configured to determine whether or not the MQTT connection is in progress.

[0088] When the push server 3 is notified of the push data transmission request from the application server 2 (S5), it refers to the notification monitoring information (B3) stored corresponding to the vehicle-mounted communication device 4 as the transmission destination of the push data, and determines whether it is in the MQTT connection (B31). If the push server 3 determines that it is not in the MQTT connection (B31: No), it determines that the vehicle-mounted communication device 4 as the transmission destination of the push data performs notification monitoring of the start request from the push server 3 by SMS (B4), notifies the start request by SMS (S6), and then performs the same processing as the first embodiment.

[0089] On the other hand, when the push server 3 determines that the MQTT connection is in progress (B31: YES), it transmits the push data to the in-vehicle communication device 4 as the destination of the push data by the MQTT method (S7), and thereafter performs the same processing as the first embodiment.

[0090] As described above, according to the fourth embodiment, in the push server 3, if the push data transmission request from the application server 2 is notified, it is determined whether the MQTT connection is in progress, and if it is determined that the MQTT connection is in progress, the push data is sent to the vehicle-mounted communication device 4, which is the transmission destination of the push data, through the MQTT method. If the MQTT connection is in progress, the push data can be sent to the vehicle-mounted communication device 4 immediately.

[0091] (Other Embodiments)

[0092] The present disclosure is described based on the embodiments, but it should be understood that it is not limited to the embodiments and structures. The present disclosure also includes various modifications and variations within the same scope. In addition, various combinations and methods, even other combinations and methods that only include one element, more or fewer elements, are included in the scope and thought range of the present disclosure.

[0093] In the embodiment, each function provided by the push server 3 and the vehicle-mounted communication device 4 can be provided by software and hardware that executes the software, only by software, only by hardware, or by a complex combination thereof. Furthermore, when such functions are provided by an electronic circuit as hardware, each function can also be provided by a digital circuit including a large number of logic circuits, or an analog circuit.

[0094] The processor 10 of the push server 3 and the processor 13 of the vehicle-mounted communication device 4 are each composed of a computing core including at least one CPU (Central Processing Unit). The processing circuit including each processor 10, 13 may also be composed mainly of an FPGA (Field-Programmable Gate Array) and an ASIC (Application-Specific Integrated Circuit).

[0095] The storage medium 12 of the push server 3 and the storage medium 15 of the vehicle-mounted communication device 4 are each composed of a non-volatile storage medium. The form of each storage medium 12, 15 can also be appropriately changed. For example, each storage medium 12, 15 is not limited to a configuration provided on a circuit substrate, and can also be configured to be provided in the form of a memory card or the like, and to be electrically connected to the processing circuit of the push server 3 and the vehicle-mounted communication device 4 by being inserted into a socket. In addition, each storage medium 12, 15 can also be an optical disk, a hard disk drive, etc., which is the basis for copying the program.

[0096] The control unit and method described in the present disclosure may also be implemented by a dedicated computer provided by a processor and a memory programmed to execute one or more functions embodied by a computer program. Alternatively, the control unit and method described in the present disclosure may also be implemented by a dedicated computer provided by a processor composed of one or more dedicated hardware logic circuits. Alternatively, the control unit and method described in the present disclosure may also be implemented by one or more dedicated computers composed of a combination of a processor and a memory programmed to execute one or more functions and a processor composed of one or more hardware logic circuits. In addition, the computer program may also be stored as an instruction executed by a computer in a non-migratable tangible recording medium that can be read by a computer.

Claims

1. A vehicle-mounted communication device, when a push server receives a push data transmission request from an application server and thus receives push data from the push server, the vehicle-mounted communication device (4) transmits the received push data to a vehicle-mounted electronic control device, in, have: A notification monitoring unit (4a) monitors notification of a start request from the push server in a first mode in which standby power is smaller than a second mode; and A reception control unit (4b) receives the push data from the push server in the second method in which the data length of the push data receivable from the push server is longer than that in the first method.

2. The vehicle-mounted communication device according to claim 1, in, The notification monitoring unit associates notification monitoring information with device identification information that can identify the device and notifies the push server of the notification monitoring information, wherein the notification monitoring information indicates whether the notification monitoring of the activation request from the push server is performed in the first method or the second method.

3. The vehicle-mounted communication device according to claim 1 or 2, in, The notification monitoring unit monitors notification of the activation request from the push server in the first manner by establishing the connection with the push server in the first manner and disconnecting the connection with the push server in the second manner.

4. The vehicle-mounted communication device according to claim 3, in, When a condition for suppressing standby power is satisfied, the notification monitoring unit establishes the first type of connection with the push server and disconnects the second type of connection with the push server.

5. A push server that sends push data to a vehicle-mounted communication device upon receiving a push data sending request from an application server (3). in, have: a notification control unit (3a) for notifying the on-board communication device of a start-up request in a first mode in which the standby power in the on-board communication device is smaller than that in a second mode; and A transmission control unit (3b) transmits push data to the on-vehicle communication device using the second method in which the data length of the push data that can be transmitted to the on-vehicle communication device is longer than that of the first method.

6. The push server according to claim 5, in, have: a retry count determination unit (3c) for determining the number of retries of the notification of the start request to the above-mentioned on-vehicle communication device; and An elapsed time determination unit (3d) determines the elapsed time from the notification of the start request to the above-mentioned vehicle-mounted communication device, If the notification control unit determines that the number of retries of notifying the on-board communication device of the start request has not reached a certain number, and determines that the time elapsed from notifying the on-board communication device of the start request has reached a certain time, the notification control unit retries the notification of the start request to the on-board communication device using the first method.

7. The push server according to claim 6, in, have: A transmission failure notification unit (3e) notifies the application server of a transmission failure notification indicating that the transmission of the push data has failed, if it is determined that the number of retries of the notification to the on-vehicle communication device of the start request has reached a certain number.

Images