Vehicle-mounted communication device and push server

Abstract

When a push server (3) receives a push data transmission request from an application server (2) and receives push data from the push server, an in-vehicle communication device (4) transmits the received push data to an in-vehicle ECU (5). A vehicle-mounted communication device is provided with: an executable reset determination unit (4a) that determines whether or not a reset can be executed; and an in-reset information notification unit (4b) that, if it is determined that the reset can be executed, associates in-reset information indicating the subject of the reset with device identification information capable of identifying the local device before the execution of the reset is started, and notifies the push server.

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims the benefit of Japanese Application No. 2022-079541, filed on May 13, 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] The on-board communication machine that sends the push data received from the push server to the on-board ECU needs to be reset, for example, for software updates, status recovery, memory clearing, etc. The on-board communication machine cannot communicate data with the push server during the reset, and the state of being unable to communicate data continues until the startup is completed and the connection of the communication line with the push server is completed. At this time, it can only be identified from the outside of the vehicle that the on-board communication machine and the push server are offline and data communication is not possible. In other words, the push server cannot identify whether the on-board communication machine is temporarily unable to communicate data due to being reset or is unable to communicate data due to some abnormality. Therefore, if the application server sends a request to send push data to the push server during the reset of the on-board communication machine, the push server fails to send push data and continues to retry sending push data until the on-board communication machine is started and the connection of the communication line is completed. Summary of the invention

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

[0008] According to one embodiment of the present disclosure, 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 transmits the received push data to the vehicle-mounted electronic control device. The executable reset determination unit determines whether the reset can be executed. If it is determined that the reset can be executed, the reset information notification unit establishes a correspondence between the reset information indicating the subject of the reset and the device identification information that can identify the device before starting the reset execution, and notifies the push server.

[0009] If it is determined that the reset can be performed, before the reset is started, the reset information indicating that the reset is in progress is associated with the device identification information and notified to the push server. By establishing a correspondence between the reset information and the device identification information and notifying the push server, the push server can determine that the vehicle-mounted communication device determined based on the device identification information is in the process of being reset, and can stop sending push data until the vehicle-mounted communication device is started up and the communication line is reconnected. That is, the push server can avoid continuous failure in sending push data and can avoid continuous retry of sending push data. As a result, push data can be appropriately received from the push server without the push server continuously retrying to send push data.

[0010] According to one aspect of the present disclosure, if a push server receives a request to send push data from an application server, the push data is sent to an on-board communication device, and the communication line with the on-board communication device is cut off as the on-board communication device performs a reset. The resetting information setting unit sets the resetting information corresponding to the on-board communication device that is the notification source of the resetting information indicating that the on-board communication device is being reset. If a resetting information determination unit receives a request to send push data from an application server, it determines whether the resetting information is set corresponding to the on-board communication device that is the destination of the push data. If it is determined that the resetting information is set, the sending reservation unit reserves the sending of the push data and waits for the reconnection of the communication line that was cut off as the on-board communication device performs a reset. If the communication line is reconnected, the information sending unit releases the push data sending reservation and sends the push data that was reserved to be sent to the on-board communication device.

[0011] When a request for sending push data is received from an application server, if reset information is set corresponding to the on-board communication device as the destination of the push data, the sending of the push data is held, and the reconnection of the communication line that was cut off when the on-board communication device was reset is completed. If the communication line is reconnected, the push data sending hold is released, and the push data whose sending is held is sent to the on-board communication device. By holding the sending of push data while the on-board communication device is being reset, it is possible to avoid continuous failure in sending push data by the push server and to avoid continuous retries of sending push data by the push server before the on-board communication device is started and the communication line is reconnected. As a result, push data can be appropriately sent to the on-board 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 chart showing the second embodiment,

[0017] Figure 5 is a timing chart showing the second embodiment,

[0018] Figure 6 is a timing chart showing the second embodiment,

[0019] Figure 7 FIG. 2 shows a third embodiment, 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 chart showing the fourth embodiment,

[0022] Fig.10 is a timing chart showing the fifth embodiment,

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

[0024] Fig.12 is a timing chart showing the sixth embodiment,

[0025] Fig.13 It is a timing chart showing the seventh embodiment. DETAILED DESCRIPTION

[0026] 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.

[0027] (First Embodiment)

[0028] Reference Figure 1 to Figure 3 A first embodiment will be described. Figure 1 The push system 1 shown 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 on-vehicle system-side application 6 for realizing a remote request service is mounted on the on-vehicle ECU 5. The push system 1 is a system that can transmit push data from the application server 2 to the on-vehicle system-side application 6 when the cloud-side application is started by a smartphone terminal or the like.

[0029] For example, if a user uses a smartphone terminal to start an application based on remote control such as starting the air conditioner before getting on the vehicle or locking the doors after 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 vehicle ECU 5 via the vehicle communication device 4 and is passed to the application 6 on the vehicle system side that enables the start of the air conditioner, locking of the doors, etc.

[0030] exist Figure 1 In 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.

[0031] 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.

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

[0033] (1) Cloud-side system

[0034] 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.

[0035] The push server 3 is a transmission source of push data, and includes a configuration of the ACP cloud 8 that implements the cloud-side functions of the automotive wireless communication platform 7. The push server 3 has a microcontroller having a processor 10, a RAM 11, and a storage medium 12 as a main body. The push server 3 performs various actions 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.

[0036] 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.

[0037] 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.

[0038] The push server 3 can retry the sending of 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 push data fails, the push server 3 retries the sending of 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 push data remains in a state of failure, the push server 3 determines that the sending of push data has failed, and ends the retry of sending push data.

[0039] (2) Vehicle-side onboard system

[0040] 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. It is the destination of push data and includes the ACP engine 9 that implements 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 the 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.

[0041] 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.

[0042] The vehicle-mounted communication device 4 is connected to the push server 3 through 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.

[0043] 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.

[0044] 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.

[0045] 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 corresponding to 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 notifies the push server 3 that is the transmission source of the failure of the push data transmission and the reason information corresponding to the failure.

[0046] 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 with low power consumption, but on the other hand, it cannot perform data communication. When the power of the on-board ECU 5 determined as the destination based on the status information is in the off state, the on-board communication device 4 performs a start-up process to start the on-board ECU 5 and turn the power on (start-up state).

[0047] 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 delivery destination of the push data from the multiple application programs 6, and delivers the push data to the application 6 determined as the delivery destination.

[0048] 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.

[0049] In the above configuration, as described above, the vehicle-mounted communication device 4 needs to be reset periodically for software update, state recovery, memory clearing, etc., but if the application server 2 sends a push data transmission request to the push server 3 during the resetting of the vehicle-mounted communication device 4, the push data transmission of the push server 3 continues to fail, and the push data transmission is continuously retried until the vehicle-mounted communication device 4 is started up and the communication line is connected. In this regard, in the present embodiment, the vehicle-mounted communication device 4 and the push server 3 each have the following functions.

[0050] like Figure 2 As shown, the vehicle-mounted communication device 4 includes an executable reset determination unit 4a and a reset-in-progress flag notification unit 4b. The reset-in-progress flag notification unit 4b corresponds to a reset-in-progress information notification unit.

[0051] If a request event such as software update, state recovery, memory clearing, etc. occurs, the executable reset determination unit 4a determines the operation state at that time and determines whether the reset can be performed. For example, if the executable reset determination unit 4a is not communicating data with the vehicle-mounted ECU 5 and determines that no adverse conditions will occur even if the reset is performed, it determines that the reset can be performed. On the other hand, if the executable reset determination unit 4a is communicating data with the vehicle-mounted ECU 5 and determines that there is a possibility of adverse conditions such as data loss or data loss if the reset is performed, it determines that the reset cannot be performed.

[0052] If the reset executable determination unit 4a determines that the reset is executable, the reset flag notification unit 4b associates the reset flag indicating that the reset is in progress with the device ID that can identify the vehicle-mounted communication device 4 and notifies the push server 3 before starting the reset. The device ID is equivalent to the device identification information.

[0053] The push server 3 includes a resetting flag setting unit 3a, a resetting flag determination unit 3b, a transmission holding unit 3c, and an information transmission unit 3d. The resetting flag setting unit 3a corresponds to a resetting information setting unit, and the resetting flag determination unit 3b corresponds to a resetting information determination unit.

[0054] When the resetting flag setting unit 3a is notified of the resetting flag from the vehicle-mounted communication device 4, it determines the vehicle-mounted communication device 4 that is the notification source of the resetting flag based on the device ID that establishes a correspondence relationship with the resetting flag, and sets the resetting flag corresponding to the vehicle-mounted communication device 4 that is the notification source of the resetting flag.

[0055] When receiving a push data transmission request from the application server 2, the resetting flag determination unit 3b determines whether a resetting flag is set corresponding to the in-vehicle communication device 4 that is the transmission destination of the push data.

[0056] When the resetting flag determination unit 3b determines that the resetting flag is set corresponding to the on-vehicle communication device 4 as the transmission destination of the push data, the transmission holding unit 3c holds the transmission of the push data and waits for the communication line disconnected by the resetting of the on-vehicle communication device 4 to be reconnected.

[0057] When the communication line is reconnected, the information transmission unit 3 d releases the transmission hold of the push data by the transmission hold unit 3 c , and transmits the push data whose transmission is held to the in-vehicle communication device 4 .

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

[0059] If a request event such as software update, status recovery, memory clearing, etc. occurs, the vehicle-mounted communication device 4 determines the operation state at that time and determines whether the reset can be performed. If the vehicle-mounted communication device 4 determines that the reset can be performed (A1), it notifies the push server 3 of the reset flag (S1). If the push server 3 is notified of the reset flag from the vehicle-mounted communication device 4, the reset flag is set corresponding to the vehicle-mounted communication device 4 as the source of the reset flag (B1). After notifying the push server 3 of the reset flag, the vehicle-mounted communication device 4 disconnects the communication line connected to the push server 3 (A2) and performs the reset (A3).

[0060] Here, when the push server 3 receives a push data transmission request (S2) transmitted from the application server 2, it determines whether a reset flag is set corresponding to the vehicle-mounted communication device 4 as the transmission destination of the push data. When the push server 3 determines that the reset flag is set corresponding to the vehicle-mounted communication device 4 as the transmission destination of the push data (B2), the transmission of the push data is suspended (S3). The push server 3 waits for the reconnection of the communication line that was disconnected as the vehicle-mounted communication device 4 as the transmission destination of the push data is reset (B3). That is, the push server 3 does not process the transmission of the push data as a failure even if the communication line is not connected between the vehicle-mounted communication device 4 as the transmission destination of the push data, by suspending the transmission of the push data.

[0061] If the on-board communication device 4 completes the reset and the startup is completed (A4), it reconnects the disconnected communication line with the push server 3 (A5). If the push server 3 determines that the reconnection of the communication line is completed, it releases the push data sending reservation (B4) and sends the push data whose sending is reserved to the on-board communication device 4 (S3). If the on-board communication device 4 receives the push data sent from the push server 3, it sends the received push data to the on-board ECU 5 (S4). If the push server 3 determines that the sending of the push data to the on-board communication device 4 is completed (B5), it notifies the application server 2 of the sending completion notification (S5). If the on-board ECU 5 receives the push data sent from the on-board 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.

[0062] As described above, according to the first embodiment, the following effects can be obtained. In the vehicle-mounted communication device 4, if it is determined that the reset can be performed, before the reset is started, a corresponding relationship is established between the resetting flag and the device ID and the push server 3 is notified. By establishing a corresponding relationship between the resetting flag and the device ID and notifying the push server 3, the push server 3 can determine that the vehicle-mounted communication device 4 determined by the device ID is in the process of resetting, and can stop sending push data until the vehicle-mounted communication device 4 is started and the communication line is reconnected. That is, the push server 3 can avoid continuous failure in sending push data and can avoid continuous retry of sending push data. As a result, push data can be properly received from the push server 3 without the push server 3 continuously retrying to send push data.

[0063] In the push server 3, when receiving a request to send push data from the application server 2, if a reset flag is set corresponding to the vehicle-mounted communication device 4 as the destination of the push data, the sending of the push data is held, and the reconnection of the communication line that was disconnected when the vehicle-mounted communication device 4 was reset is completed. If the reconnection of the communication line is completed, the push data sending hold is released, and the push data whose sending is held is sent to the vehicle-mounted communication device 4. By holding the sending of push data while the vehicle-mounted communication device 4 is being reset, the push server 3 can avoid continuous failure in sending push data and continuous retries of sending push data before the vehicle-mounted communication device 4 is started and the connection of the communication line is completed. As a result, the push data can be appropriately sent to the vehicle-mounted communication device 4.

[0064] (Second Embodiment)

[0065] Reference Figures 4 to 6 The second embodiment is described. In the vehicle-mounted communication device 4, the reset information notification unit 4b, before starting the execution of the reset, not only notifies the push server 3 of a reset-in-progress flag indicating that the reset is in progress, but also notifies the push server 3 of time information indicating a scheduled time until the reconnection of the communication line is completed or time information indicating the scheduled time when the reconnection is completed.

[0066] When the on-vehicle communication device 4 determines that the reset can be performed (A1), it notifies the push server 3 of the reset flag (S1), and notifies the push server 3 of the time information or the moment information (S11). When the push server 3 is notified of the reset flag from the on-vehicle communication device 4, it sets the reset flag corresponding to the on-vehicle communication device 4 that is the source of the reset flag (B1), and when the push server 3 is notified of the time information or the moment information from the on-vehicle communication device 4, it stores the notified time information or the moment information (B11).

[0067] In this case, when the push server 3 receives a push data transmission request from the application server 2 during the setting of the reset flag, and determines that the reset flag is set corresponding to the vehicle-mounted communication device 4 as the transmission destination of the push data (B2), the push server 3 determines whether the scheduled time or the scheduled moment has arrived based on the stored time information or moment information (B12). If the push server 3 determines that the scheduled time or the scheduled moment has not arrived (B12: No), it notifies the application server 2 of a transmission holding response (S12), and holds the transmission of the push data (B3).

[0068] On the other hand, if the push server 3 determines that the predetermined time or the predetermined moment has arrived, it notifies the application server 2 of a transmission failure response (S13), releases the transmission hold of the push data (B4), and stops waiting for the reconnection of the communication line that was disconnected when the on-vehicle communication device 4, which is the transmission destination of the push data, is reset. That is, the push server 3 processes the failure of the transmission of the push data as a result of the unconnected communication line between the on-vehicle communication device 4, which is the transmission destination of the push data, by releasing the transmission hold of the push data.

[0069] As described above, according to the second embodiment, the push server 3 can correctly determine that the offline state is temporary by notifying the time information or time information from the vehicle-mounted communication device 4. In addition, it is possible to appropriately cope with the situation where the required time required for resetting differs for each vehicle-mounted communication device 4.

[0070] (Third Embodiment)

[0071] Reference Figure 7-Figure 8 The third embodiment is described. Figure 7 As shown, the in-vehicle communication device 4 includes a reset execution holding portion 4c and a reset execution holding release portion 4d in addition to the reset executable determination portion 4a and the reset-in-progress flag notification portion 4b.

[0072] The reset execution holding unit 4c holds the reset execution when notified of the reset execution holding request from the push server 3. The reset execution holding release unit 4d releases the reset execution holding when a certain time has passed since the reset execution was held or when notified of the reset execution holding release request from the push server 3.

[0073] The push server 3 includes a reservation determination unit 3e, a reset execution hold request notification unit 3f, and a reset execution hold release request notification unit 3g in addition to a reset-in-progress flag setting unit 3a, a reset-in-progress flag determination unit 3b, a transmission hold unit 3c, and an information transmission unit 3d.

[0074] The schedule existence determination unit 3e determines whether there is a schedule to send push data within a specified time. If the schedule existence determination unit 3e determines that there is a schedule to send push data within a specified time, the reset execution hold request notification unit 3f notifies the on-vehicle communication device 4 of the reset execution hold request. The reset execution hold release request notification unit 3g notifies the on-vehicle communication device 4 of the reset execution hold release request.

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

[0076] When the push server 3 is notified of the reset flag from the on-board communication device 4, the reset flag is set corresponding to the on-board communication device 4 that is the source of the reset flag (B1), and determines whether there is a schedule to send push data within a specified time (B21). When the push server 3 determines that there is a schedule to send push data within the specified time (B21: Yes), it notifies the on-board communication device 4 of a reset execution hold request (S21).

[0077] When notified of the reset execution suspension request from the push server 3, the vehicle-mounted communication device 4 suspends the execution of the reset (A21), monitors the elapsed time from the suspension of the execution of the reset, and determines whether the elapsed time from the suspension of the execution of the reset has reached a certain time (A22).

[0078] If the push server 3 receives a push data transmission request from the application server 2 before the elapsed time from the execution of the reset being held in the vehicle-mounted communication device 4 reaches a certain time (S22), the push data is transmitted to the vehicle-mounted communication device 4 because the vehicle-mounted communication device 4 holds the execution of the reset (S23). If the vehicle-mounted communication device 4 receives the push data transmitted from the push server 3, it transmits the received push data to the vehicle-mounted ECU 5 (S24).

[0079] When the vehicle-mounted communication device 4 determines that the time elapsed from the execution of the hold reset has reached a certain time (A22: Yes), it cancels the hold of the execution of the reset (A23), disconnects the communication line connected to the push server 3 (A2), and executes the reset (A3). Thereafter, the same processing as the first embodiment is performed.

[0080] As described above, according to the third embodiment, in the push server 3, the reset flag is set, but if it is determined that there is a schedule to send push data within a specified time, by notifying the on-board communication device 4 of a reset execution hold request, the push data can be sent to the on-board communication device 4 before the on-board communication device 4 executes the reset. In addition, if the elapsed time from the execution of the hold reset reaches a certain time, the on-board communication device 4 can execute the reset.

[0081] (Fourth Embodiment)

[0082] Reference Fig. 9 A fourth embodiment will be described.

[0083] If the push server 3 determines that there is a schedule to send push data within the specified time (B21: Yes), it notifies the on-board communication device 4 of the reset execution hold request (S21). If a certain time has passed since the reset execution hold request was notified to the on-board communication device 4, it notifies the on-board communication device 4 of the reset execution hold release request (S25).

[0084] If the push server 3 receives a request to send push data from the application server 2 before notifying the on-board communication device 4 of the reset execution hold release request (S22), the on-board communication device 4 holds the reset execution, so the push data is sent to the on-board communication device 4 (S23). If the on-board communication device 4 receives the push data sent from the push server 3, it sends the received push data to the on-board ECU 5 (S24).

[0085] When the on-vehicle communication device 4 receives the reset execution hold release request from the push server 3, it releases the reset execution hold (A23), disconnects the communication line connected to the push server 3 (A2), and executes the reset (A3). Thereafter, the same processing as the first embodiment is performed.

[0086] As described above, according to the fourth embodiment, similar to the third embodiment, the resetting flag is set in the push server 3, but if it is determined that there is a schedule to send push data within a prescribed time, the push data can be sent to the vehicle-mounted communication device 4 before the vehicle-mounted communication device 4 performs the reset by notifying the vehicle-mounted communication device 4 of the reset execution hold request. In addition, by notifying the vehicle-mounted communication device 4 of the reset execution hold request from the push server 3, the vehicle-mounted communication device 4 can perform the reset.

[0087] (Fifth Embodiment)

[0088] Reference Figure 10-11 A fifth embodiment will be described.

[0089] When the on-vehicle communication device 4 is notified of the reset execution hold release request from the push server 3, the reset execution hold is released (A23), and when it is determined that the reset can be executed (A1), the push server 3 is notified of the reset in progress flag (S1). When the push server 3 is notified of the reset in progress flag from the on-vehicle communication device 4, the reset in progress flag is set corresponding to the on-vehicle communication device 4 that is the source of the reset in progress flag (B1). After notifying the push server 3 of the reset in progress flag, the on-vehicle communication device 4 disconnects the communication line connected to the push server 3 (A2) and executes the reset (A3).

[0090] As described above, according to the fifth embodiment, the on-vehicle communication device 4 can notify the push server 3 of the resetting-in-progress flag if it is determined that the resetting is executable after the execution hold of the resetting is released.

[0091] (Sixth Embodiment)

[0092] Reference Fig.12 A sixth embodiment will be described.

[0093] The push server 3 determines whether there is a schedule to send push data within the specified time (B31). If the push server 3 determines that there is no schedule to send push data within the specified time (B31: No), it sets the reset flag (B1) and notifies the vehicle-mounted communication device 4 of a reset execution request (S31).

[0094] When the vehicle-mounted communication device 4 is notified of the reset execution request from the push server 3, it determines whether the reset can be executed. If it is determined that the reset can be executed (A1), it cuts off the communication line connected to the push server 3 (A2) and executes the reset (A3). Thereafter, the same processing as the first embodiment is performed.

[0095] As described above, according to the sixth embodiment, the in-vehicle communication device 4 can execute the reset when the push server 3 notifies the in-vehicle communication device 4 of the reset execution request.

[0096] (Seventh Embodiment)

[0097] Reference Fig.13 The seventh embodiment will be described. The push server 3 determines whether push data is scheduled to be sent within a predetermined time (B31). If the push server 3 determines that push data is not scheduled to be sent within the predetermined time (B31: No), it notifies the vehicle-mounted communication device 4 of a reset execution request (S31).

[0098] When the on-vehicle communication device 4 is notified of the reset execution request from the push server 3, it determines whether the reset can be executed. If it is determined that the reset can be executed (A1), it notifies the push server 3 of the reset flag (S1). When the push server 3 is notified of the reset flag from the on-vehicle communication device 4, it sets the reset flag corresponding to the on-vehicle communication device 4 that is the source of the reset flag (B1). After notifying the push server 3 of the reset flag, the on-vehicle communication device 4 disconnects the communication line connected to the push server 3 (A2) and executes the reset (A3). Thereafter, the same processing as the first embodiment is performed.

[0099] As described above, according to the seventh embodiment, similarly to the sixth embodiment, the in-vehicle communication device 4 can execute the reset when the push server 3 notifies the in-vehicle communication device 4 of the reset execution request.

[0100] (Other Embodiments)

[0101] 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.

[0102] 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 electronic circuits as hardware, each function can also be provided by a digital circuit including a large number of logic circuits, or an analog circuit.

[0103] 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).

[0104] 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 nonvolatile 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 the configuration provided on the circuit substrate, and can also be provided in the form of a memory card or the like, and electrically connected to the processing circuit of the push server 3 and the vehicle-mounted communication device 4 by being inserted into the 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.

[0105] 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. An in-vehicle 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 in-vehicle communication device (4) transmits the received push data to an in-vehicle electronic control device, wherein: have: An executable reset determination unit (4a) for determining whether the reset can be performed; and When determining that the reset can be performed, the reset information notification unit (4b) establishes a correspondence between reset information indicating that the reset is in progress and device identification information that can identify the device and notifies the push server before starting the reset.

2. The vehicle-mounted communication device according to claim 1, wherein: The resetting information notification unit not only notifies the push server of the resetting information, but also notifies the push server of time information indicating a scheduled time until the reconnection of the communication line is completed or time information indicating a scheduled time when the reconnection is completed.

3. The vehicle-mounted communication device according to claim 1 or 2, wherein: have: A reset execution holding unit (4c) holds execution of the reset when a reset execution holding request is notified from the push server.

4. The vehicle-mounted communication device according to claim 3, wherein: have: A reset execution hold releasing unit (4d) releases the reset execution hold when a certain time has passed since the execution of the hold reset has been executed.

5. The vehicle-mounted communication device according to claim 3, wherein: have: The reset execution hold release unit (4d) releases the reset execution hold when a reset execution hold release request is notified from the push server.

6. A push server, which, upon receiving a push data transmission request from an application server, transmits the push data to an on-board communication device, and disconnects the communication line with the on-board communication device when the on-board communication device is reset (3), wherein: have: A resetting information setting unit (3a) sets resetting information indicating that the vehicle-mounted communication device is being reset, in correspondence with the vehicle-mounted communication device that is a notification source of the resetting information; A resetting information determination unit (3b) determines whether resetting information is set corresponding to the vehicle-mounted communication device as the destination of the push data, upon receiving a request for sending push data from the application server; A transmission holding section (3c) holds the transmission of the push data if it is determined that the reset information is set, and waits for the reconnection of the communication line that was cut off when the vehicle-mounted communication device is reset; as well as The information sending unit (3d) releases the push data transmission reservation when the reconnection of the communication line is completed, and sends the push data whose transmission is reserved to the vehicle-mounted communication device.

7. The push server according to claim 6, wherein: When the resetting information is notified from the on-vehicle communication device, the resetting information setting unit sets the resetting information in correspondence with the on-vehicle communication device that is the notification source of the resetting information.

8. The push server according to claim 6 or 7, wherein: The vehicle-mounted communication means is configured to suspend the execution of the reset upon receipt of a reset execution suspension request from the push server. The method comprises: a schedule existence determination unit (3e) for determining whether there is a schedule to send push data within a specified time; as well as The reset execution hold request notification unit (3f) notifies the above-mentioned on-vehicle communication device of the above-mentioned reset execution hold request when it is determined that there is a schedule to send push data within a predetermined time.

9. The push server according to claim 8, wherein: The vehicle-mounted communication means is configured to release the reset execution hold upon receiving a request to release the reset execution hold from the push server. The invention comprises: a reset execution hold release request notification unit (3g) for notifying the on-vehicle communication device of the reset execution hold release request after the reset execution hold request notification unit notifies the on-vehicle communication device of the reset execution hold release request.

Images