Vehicle-mounted communication device and push server

Abstract

The invention relates to an in-vehicle communication device and a push server. When a push server (3) receives a push data transmission request from an application server (2) and an in-vehicle communication device (4) receives push data from the push server, the in-vehicle communication device (4) transmits the received push data to an in-vehicle ECU (5). The in-vehicle communication device is provided with a startup control unit (4a) which, when a startup start instruction is notified from an application server to a push server immediately after a cloud-side application program is started up and the startup start instruction is notified from the push server. The start-up control unit causes the vehicle-mounted electronic control device, which is a transmission destination of the push data, to start a start-up process.

Description

[0001] Cross-reference to related applications

[0002] This application incorporates the contents of Japanese Patent Application No. 2023-53434, filed on March 29, 2023. Technical Field

[0003] This disclosure relates to in-vehicle communication devices and push servers. Background Technology

[0004] As one of the remote request services for accessing in-vehicle system applications from outside the vehicle, a push system provides the ability to send push data. The push system sets up an application server and a push server on the cloud side, and an in-vehicle communication unit and an in-vehicle electronic control unit (hereinafter referred to as an in-vehicle ECU) on the vehicle side. For example, when an application on the cloud side is launched via a smartphone terminal, and the push server receives a push data sending request from the application server, the push server sends the push data to the in-vehicle communication unit. The in-vehicle communication unit then sends the push data from the push server to the in-vehicle ECU and transmits the push data to the in-vehicle system application mounted on the in-vehicle ECU (see, for example, Patent Document 1).

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

[0006] The transmission of push data to the application on the vehicle system side requires the vehicle ECU to have completed its startup process and be running. However, depending on the ECU's structure and functional configuration, there are concerns that the startup time required for the vehicle ECU to complete its startup process may be lengthy. Therefore, in a structure where the vehicle communication unit initiates the vehicle ECU's startup process by receiving push data sent from the push server, it is possible that the vehicle ECU has not yet started when the vehicle communication unit sends the push data to the vehicle ECU. This makes it difficult to provide immediate remote request services, resulting in poor serviceability and marketability. Summary of the Invention

[0007] The purpose of this disclosure is to enable the vehicle electronic control unit, which is the destination of the push data, to start immediately.

[0008] According to one aspect of this disclosure, when a push server receives a push data sending request from an application server and thus receives push data from that push server, it sends the received push data to the vehicle electronic control unit. When the application on the cloud side immediately notifies the push server of a startup start instruction after startup, and the push server then notifies the application server of the startup start instruction, the startup control unit causes the vehicle electronic control unit, which is the destination of the push data, to begin startup processing.

[0009] When a startup instruction is received from the push server, the in-vehicle electronic control unit (EV unit) begins startup processing. When the cloud-side application starts, the EV unit, as the destination of the push data, immediately begins startup processing, ensuring its immediate completion. This reduces the likelihood that the EV unit has not started by the time the in-vehicle communicator sends push data to it, enabling immediate startup of applications on the in-vehicle system side integrated with the EV unit, thus improving serviceability and marketability.

[0010] According to one method of this disclosure, when a push data sending request is received from the application server, the push data is sent to the vehicle communication unit. When the application on the cloud side is notified of a startup start indication immediately after startup from the application server, the startup start indication notification unit notifies the vehicle communication unit, which is the destination of the push data, of the startup start indication.

[0011] When the application on the cloud side is launched and immediately receives a launch start instruction from the application server, the launch start instruction is sent to the in-vehicle communication unit, which is the destination of the push data. When the cloud-side application launches, the in-vehicle electronic control unit (IVR), the destination of the push data, immediately begins its startup process, ensuring that the IVR completes startup immediately. This reduces the possibility that the IVR has not yet started when the in-vehicle communication unit sends push data to the IVR, enabling the application on the in-vehicle system side, which is integrated with the IVR, to launch immediately, thus improving serviceability and marketability. Attached Figure Description

[0012] The above-mentioned objects, as well as other objects, features, and advantages of this disclosure, will become more apparent from the following detailed description with reference to the accompanying drawings. The accompanying drawings are:

[0013] Figure 1 The first embodiment is shown in a diagram illustrating the overall structure of the push system.

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

[0015] Figure 3 It is a timing diagram.

[0016] Figure 4 This is a timing diagram representing the second embodiment.

[0017] Figure 5 This is a timing diagram representing the third implementation method.

[0018] Figure 6 The fourth embodiment is shown as a functional block diagram of the vehicle-mounted communication unit and the push server.

[0019] Figure 7 It is a timing diagram.

[0020] Figure 8 It is a timing diagram. Detailed Implementation

[0021] Hereinafter, several embodiments will be described with reference to the accompanying drawings. Descriptions of common parts in the various embodiments may be omitted.

[0022] (First Implementation)

[0023] Reference Figures 1 to 3 The first embodiment will be described. Figure 1 The push system 1 shown includes an application server 2 and a push server 3 located on the cloud side, and an in-vehicle communication unit 4 and an in-vehicle ECU 5 located on the vehicle side. The in-vehicle ECU 5 carries an application 6 for remotely requesting services. The push system 1 is a system capable of sending push data from the application server 2 to the in-vehicle application 6 when, for example, the cloud-side application is launched via a smartphone terminal.

[0024] For example, when a user performs a specified operation by remotely activating an application such as starting the air conditioning before boarding the vehicle or locking the doors after boarding the vehicle via a smartphone terminal, the application server 2 sends a push data request to the push server 3 to command the air conditioning to start and the doors to lock. The push data is then sent to the vehicle ECU 5 via the vehicle communication unit 4 and transmitted to the application 6 on the vehicle system side that enables the air conditioning to start and the doors to lock.

[0025] exist Figure 1 The example illustrates a structure where a push server 3 is set up for multiple application servers 2 on the cloud side, but it could also be a structure where multiple push servers 3 are set up for multiple application servers 2. Similarly, the example illustrates a structure where a vehicle communication unit 4 is set up for multiple vehicle ECUs 5 on the vehicle side, but it could also be a structure where multiple vehicle communication units 4 are set up for multiple vehicle ECUs 5.

[0026] The push system 1 employs an automotive wireless communication platform 7. The automotive wireless communication platform 7 functions through the cloud-side ACP cloud 8 and the vehicle-side ACP engine 9, enabling secure connections between the application server 2 and the application program 6 anytime, anywhere. To elaborate, the power supply to the on-board ECU 5 is disconnected, for example, when the vehicle is parked, and the power states differ between vehicles. Furthermore, the system architecture containing the on-board ECU 5 varies from vehicle to vehicle. The automotive wireless communication platform 7 hides these differences in the power states of the on-board ECU 5 and the differences in the system architecture of each vehicle from the application server 2. As a result, a pseudo-always-connected connection can be achieved on a vehicle-by-vehicle basis, as if all on-board ECU 5 are always connected to the external network.

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

[0028] (1) Cloud-side system

[0029] First, the vehicle-side in-vehicle system will be described. Application server 2 functions as the source of push data sending requests. Application server 2 manages at least one of the application ID and token used to identify application application 6. When sending a push data sending request to push server 3, application server 2 provides either the application ID or the token as request information along with the message body sent to application application 6. If the token is used as the request information, application server 2 reads the token corresponding to the destination of the push data. The token becomes the key information used by push server 3 and the in-vehicle system to determine the destination of the push data.

[0030] Push server 3 is the source of push data and includes the structure of ACP cloud 8, which implements the cloud-side functions of automotive wireless communication platform 7. Push server 3 has a microcontroller as its main body, which includes processor 10, RAM 11, and storage medium 12. Push server 3 uses processor 10 to execute control programs stored in storage medium 12 to perform various actions, thereby realizing the cloud-side functions of automotive wireless communication platform 7.

[0031] The push server 3 connects to the vehicle-mounted communication unit 4 via a wireless communication line through a mobile communication network. With the communication line connected, it can send push data to the vehicle-mounted communication unit 4. Mobile communication networks include, for example, mobile phone networks, Wi-Fi (registered trademark), and V2X (Vehicle-to-Anything). When the push server 3 receives a push data sending request from the application server 2, it selects the vehicle-mounted communication unit 4 as the destination and sends the push data to that selected destination.

[0032] Push server 3 provides functions such as authentication of communication objects, encryption of communication content, and tamper detection through TLS (Transport Layer Security) processing, and provides data communication functions using TCP / IP, UDP / IP and other protocols, thereby realizing secure data communication with application server 2 and vehicle communication unit 4.

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

[0034] (2) Vehicle-side onboard system

[0035] Next, the vehicle-side in-vehicle system will be described. The in-vehicle communication unit 4, referred to as a TCU (Telematics Control Unit) or DCM (Data Communication Module), is the destination for data transmission and contains the ACP engine 9, which implements the vehicle-side functions of the automotive wireless communication platform 7. The in-vehicle communication unit 4 has a microcontroller as its main component, which includes a processor 13, RAM 14, and a storage medium 15. The in-vehicle communication unit 4 uses the processor 13 to execute control programs stored in the storage medium 15 to perform various actions, thereby realizing the vehicle-side functions of the automotive wireless communication platform 7.

[0036] The vehicle communication unit 4 connects to multiple vehicle ECUs 5 via the in-vehicle network. In-vehicle networks include, for example, Ethernet (registered trademark), CAN (Controller Area Network) (registered trademark), FLEXRAY (registered trademark), CXPI (Clock Extension Peripheral Interface) (registered trademark), and LIN (Local Interconnect Network). In-vehicle networks are configured for each system, including the powertrain, chassis, body, multimedia, and safety systems.

[0037] The vehicle-mounted communication unit 4 is connected to the push server 3 via a wireless communication line through a mobile communication network. When the communication line is connected, the vehicle-mounted communication unit 4 can receive push data. When the vehicle-mounted communication unit 4 receives push data from the push server 3, it selects a vehicle-mounted ECU 5 as the destination and sends the push data to that selected ECU 5.

[0038] The vehicle-mounted communication unit 4 provides functions such as authentication of communication objects, encryption of communication content, and tamper detection through TLS processing, and also provides data communication capabilities using TCP / IP, UDP / IP, and other protocols. Secure data communication can occur between the vehicle-mounted communication unit 4 and the push server 3, and between the vehicle-mounted communication unit 4 and the vehicle-mounted ECU 5.

[0039] The vehicle communication unit 4 can maintain its online connection to the communication network even when the vehicle's main power is disconnected, specifically when the ignition switch is off, such as when the vehicle is parked. The vehicle communication unit 4 monitors the wireless communication connection status between itself and the push server 3, as well as the progress of push data transmission within the vehicle network. The vehicle communication unit 4 and the push server 3 cooperate to confirm the connection between themselves. There is also a connection confirmation mechanism between the vehicle communication unit 4 and the push server 3, referred to as heartbeat monitoring.

[0040] If the push data fails to reach its destination, the vehicle-mounted communication unit 4 notifies the sending source of the push data transmission failure along with a reason message corresponding to the failure. For example, if the application 6 or the vehicle-mounted ECU 5, which serves as the destination for the push data, does not exist in the in-vehicle network, the vehicle-mounted communication unit 4 notifies the push server 3, which is the sending source, of the push data transmission failure along with such a reason message.

[0041] The vehicle communication unit 4 determines the destination information and status information, which are ECU information related to the vehicle ECU 5 that is the destination for the pushed data. The destination information may also be referred to as target address information. The destination information is the information that allows the vehicle ECU 5 to be identified as the destination for the pushed data from among multiple vehicle ECUs 5. The vehicle communication unit 4 obtains the destination information by referring to the application ID or token. The status information is the information that determines the power status (on / off state) of the vehicle ECU 5 that has been identified as the destination. In detail, the power-off state here refers to a state where the vehicle ECU 5 has moved from the start state to the stop state due to the ignition switch being turned off, etc. At this time, the vehicle ECU 5 is in a state where it can receive start requests with low power but cannot perform data communication. If, based on the status information, the power of the vehicle ECU 5 that is identified as the destination is in the off state, the vehicle communication unit 4 performs a start process to start the vehicle ECU 5 and turn its power on (start state).

[0042] The vehicle-mounted ECU 5 carries one or more application programs 6, capable of executing these applications. The vehicle-mounted ECU 5 has a microcontroller as its main component, which includes a processor (not shown), RAM (not shown), and a storage medium (not shown). The vehicle-mounted ECU 5 executes control programs stored in the storage medium through the processor to perform various actions, acting as a terminal ECU that serves as the final destination for push data sent from the push server 3. When the vehicle-mounted ECU 5 receives push data sent from the vehicle-mounted communication unit 4, it determines the registration information that matches the application ID or token corresponding to the push data, identifies the application 6 from among the multiple applications 6 as the destination for the push data, and then transmits the push data to the identified destination application 6.

[0043] The vehicle ECU 5 provides encryption capabilities, enabling secure data communication between the vehicle communication unit 4 and the application program 6. Unlike the vehicle communication unit 4, the vehicle ECU 5 is, in principle, disconnected when the vehicle's power is off to suppress power consumption. In this state, the vehicle ECU 5's connection to the communication network is also severed. Alternatively, some vehicle ECU 5s may not carry the application program 6. Furthermore, the vehicle communication unit 4 can also be integrated into the vehicle system as a secondary device, serving as the vehicle ECU 5, and can carry the application program 6.

[0044] In the above structure, as described above, in the configuration where the vehicle communication unit 4 initiates the vehicle ECU 5's startup process by receiving push data sent from the push server 3, it is possible that the vehicle ECU 5 may not start when the vehicle communication unit 4 sends push data to the vehicle ECU 5. Regarding this, in this embodiment, the vehicle communication unit 4 and the push server 3 each possess the functions described below.

[0045] like Figure 2 As shown, the vehicle communication unit 4 includes a startup control unit 4a and a first startup completion notification unit 4b. When a startup start instruction is received from the push server 3, the startup control unit 4a causes the vehicle ECU 5, which is the destination of the push data, to start startup processing in a low-power state. At this time, the startup control unit 4a does not cause the vehicle ECU 5, which is not the destination of the push data, to start startup processing. When a startup completion notification indicating that the vehicle ECU 5 has completed startup is received, the first startup completion notification unit 4b sends the startup completion notification to the push server 3.

[0046] The push server 3 includes a startup start indication notification unit 3a and a startup completion notification unit 3b. When a startup start indication is notified from the application server 2 immediately after the application on the cloud side starts, the startup start indication notification unit 3a notifies the vehicle communication unit 4, which is the destination for sending push data, of the startup start indication. When a startup completion notification is notified from the vehicle communication unit 4, the second startup completion notification unit 3b notifies the application server 2 of the startup completion notification.

[0047] Reference Figure 3 The function of the above-mentioned structures will be explained.

[0048] Application server 2, for example, when it determines that a user has launched a smartphone application on a smartphone terminal (A1), sends a launch start indication to push server 3 (S1). Push server 3, upon receiving the launch start indication from application server 2, sends the launch start indication to vehicle communication unit 4 (S2). Vehicle communication unit 4, upon receiving the launch start indication from push server 3, sends the launch start indication to vehicle ECU 5, which is the destination for the push data (S3). That is, vehicle communication unit 4, in response to the launch start indication, determines the vehicle ECU 5 as the destination for the push data, and thus only sends the launch start indication to vehicle ECU 5 that is the destination for the push data, while not sending the launch start indication to vehicle ECU 5 that is not the destination for the push data.

[0049] When the vehicle ECU 5 receives a startup start instruction from the vehicle communication unit 4, it transitions from sleep mode to low-power mode and begins startup processing (B1). When the vehicle ECU 5 completes startup processing (B2: "Yes"), it sends a startup completion notification to the vehicle communication unit 4, indicating that the startup process is complete (S4). When the vehicle communication unit 4 receives the startup completion notification from the vehicle ECU 5, it sends the startup completion notification to the push server 3 (S5). When the push server 3 receives the startup completion notification from the vehicle communication unit 4, it sends the startup completion notification to the application server 2 (S6).

[0050] Application server 2, for example, when it determines that a user has performed a specified operation to request a remote service (A2), sends a push data sending request to push server 3 (S7). Push server 3, upon receiving the push data sending request from application server 2, sends the push data to vehicle communication unit 4 (S8). Vehicle communication unit 4, upon receiving the push data from push server 3, sends the push data to vehicle ECU 5 (S9). Vehicle ECU 5, upon receiving the push data from vehicle communication unit 4, transmits the push data to the application program 6 corresponding to the push data, causing application program 6 to start and control the remote service request corresponding to the push data (B3).

[0051] As explained above, the following effects can be achieved according to the first embodiment. In the vehicle communication unit 4, when a start-up instruction is received from the push server 3, the vehicle ECU 5 begins startup processing. When the cloud-side application starts, the vehicle ECU 5, as the destination for push data transmission, immediately begins startup processing, thereby enabling the vehicle ECU 5, as the destination for push data transmission, to complete startup immediately. This reduces the possibility that the vehicle ECU 5 has not started when the vehicle communication unit 4 sends push data to it, and enables the application on the vehicle system side mounted on the vehicle ECU 5 to start immediately, improving serviceability and marketability.

[0052] In push server 3, when the application on the cloud side is immediately notified of a startup start instruction from application server 2 after its launch, the startup start instruction is sent to the vehicle communication unit 4, which is the destination of the push data. When the application on the cloud side starts, the vehicle ECU 5, which is the destination of the push data, immediately begins startup processing, thereby enabling the vehicle ECU 5 to start up immediately. This reduces the possibility that the vehicle ECU 5 has not started when the vehicle communication unit 4 sends push data to the vehicle ECU 5, and enables the application on the vehicle system side equipped with the vehicle ECU 5 to start immediately, thereby improving serviceability and marketability.

[0053] (Second Implementation)

[0054] Reference Figure 4 The second embodiment will be described. In the vehicle communication unit 4, the start control unit 4a maintains start target information of the vehicle ECU 5 that is the start target for determining the start target to start the start process, and determines the vehicle ECU 5 that is the start target for starting the start process based on the start target information. The push server 3 sends push data to the vehicle ECU 5 determined based on the start target information.

[0055] Refer to and explain the function of the above structures.

[0056] The vehicle communication unit 4, for example, maintains startup target information (C1) pre-set by the vehicle manufacturer. When the vehicle communication unit 4 is notified of a startup start instruction from the push server 3, it refers to the startup target information and determines the vehicle ECU 5 (C2) of the startup target that will initiate the startup process. The vehicle communication unit 4 determines the vehicle ECU 5 determined based on the startup target information as the destination for push data transmission and notifies the vehicle ECU 5, the destination for push data transmission, of the startup start instruction (S3). After this, the same processing as in the first embodiment is performed.

[0057] As explained above, according to the second embodiment, the vehicle ECU 5 that initiates the startup process is determined based on the startup target information. The vehicle ECU 5 determined based on the startup target information is then designated as the destination for the push data, and a startup start instruction is sent to the vehicle ECU 5 designated as the push data destination. This approach achieves a balance between improving serviceability and marketability, and reducing vehicle power consumption.

[0058] For example, in vehicles with relatively high risk of insufficient charging, such as inexpensive compact cars and light vehicles with small battery capacity, there is a greater need to suppress unnecessary vehicle power consumption. For instance, by registering only applications requiring immediate action, such as door locking, as startup objects in the startup object information, and excluding applications that do not require immediate action, such as air conditioning activation, vehicle power consumption can be suppressed, and applications requiring immediate action can be prioritized for startup.

[0059] On the other hand, in vehicles such as electric vehicles equipped with charging facilities, the need to suppress unnecessary vehicle power consumption is not high. For example, by registering not only applications requiring immediate action, such as door locking, but also applications that do not require immediate action, such as air conditioning activation, as launch objects in the launch object information, multiple applications can be launched simultaneously regardless of whether immediate action is required.

[0060] (Third Implementation)

[0061] Reference Figure 5The third embodiment will be described. In the vehicle-mounted communication unit 4, the start control unit 4a synchronizes the start target information with the push server 3.

[0062] Refer to and explain the function of the above structures.

[0063] The push server 3 maintains startup object information (D1). When the startup object information is updated (D2), it sends the startup object information to the vehicle communication unit 4 (S10). When the vehicle communication unit 4 receives the startup object information sent from the push server 3, it updates the maintained startup object information (C3) to synchronize the startup object information with the push server 3. After this, the same processing as in the second embodiment is performed.

[0064] As explained above, according to the third embodiment, the launch object information is synchronized between the vehicle communication unit 4 and the push server 3. This allows for flexible adjustments to the trade-offs between improving serviceability and marketability, and reducing vehicle power consumption, based on the needs of the vehicle and the user, thereby enhancing convenience.

[0065] For example, in the case of long-distance driving where the need to suppress vehicle power consumption is not high under normal use, the need to suppress vehicle power consumption arises in order to ensure driving range. By updating the startup object information maintained on the push server 3 and synchronizing the startup object information between the vehicle communication unit 4 and the push server 3, it is possible to flexibly respond to changes in the usage environment.

[0066] (Fourth Implementation)

[0067] Reference Figures 6 to 8 The fourth embodiment will be described. In addition to the start-up notification unit 3a and the start-up completion notification unit 3b, the push server 3 also includes a session establishment unit 3c and a destination determination unit 3d.

[0068] When the session establishment unit 3c receives a start-up completion notification from the vehicle communication unit 4, it establishes a session with the application 6. The destination determination unit 3d determines the destination of the push data.

[0069] Reference Figures 7 to 8 The function of the above-mentioned structures will be explained.

[0070] When push server 3 receives a startup completion notification from in-vehicle communication unit 4, it establishes a session with application 6. Push server 3 manages the session establishment with application 6 and determines whether the session establishment was successful. Figure 7As shown, push server 3 determines that the session with application 6 has been successfully established (D3). When it receives a push data sending request from application server 2, it determines the destination of the push data (D4) and directly transmits the push data to application 6, which has successfully established the session (S11).

[0071] On the other hand, such as Figure 8 As shown, push server 3 determines that the session establishment with application 6 has failed (D5). When it receives a push data sending request from application server 2, it sends the push data to vehicle communication unit 4 (S12). When vehicle communication unit 4 receives push data from push server 3, it sends the push data to vehicle ECU 5 (S13). When vehicle ECU 5 receives push data from vehicle communication unit 4, it transmits the push data to application 6 corresponding to the push data, causing application 6 to start and control the remote request service corresponding to the push data (B3).

[0072] As explained above, according to the fourth embodiment, a session is established between the application that serves as the destination of the push data and the push server 3. By sending the push data directly from the push server 3 to the vehicle ECU 5, the processing of the vehicle communication unit 4 is eliminated, thereby shortening the transmission time required to send the push data from the push server 3 to the vehicle ECU 5 and improving real-time performance.

[0073] (Other implementation methods)

[0074] This disclosure is based on embodiments, but it should be understood that it is not limited to these embodiments or structures. This disclosure also includes various modifications and variations within the same scope. In addition, various combinations and methods, and even other combinations and methods containing only one element, more or fewer elements, are included within the scope and spirit of this disclosure.

[0075] In implementations, the functions provided by the push server 3 and the vehicle communication unit 4 can be provided through software and the hardware executing that software, through software alone, through hardware alone, or through a combination thereof. Furthermore, while such functions are provided through electronic circuits as hardware, they can also be provided through digital or analog circuits containing numerous logic circuits.

[0076] The processor 10 of the push server 3 and the processor 13 of the vehicle-mounted communication unit 4 are both structures that include at least one CPU (Central Processing Unit) or other computing core. The processing circuits containing each processor 10 and 13 can also be structures based on FPGA (Field-Programmable Gate Array) and ASIC (Application-Specific Integrated Circuit).

[0077] The storage medium 12 of the push server 3 and the storage medium 15 of the vehicle communication unit 4 are both structures containing non-volatile storage media. The form of each storage medium 12 and 15 can also be appropriately changed. For example, each storage medium 12 and 15 is not limited to a structure mounted on a circuit board; it can be provided in the form of a memory card, etc., and electrically connected to the processing circuitry of the push server 3 and the vehicle communication unit 4 by being inserted into a slot. Furthermore, each storage medium 12 and 15 can also be an optical disc, hard disk drive, etc., which serve as the basis for program copying.

[0078] The control unit and methods described in this disclosure can also be implemented by a special-purpose computer consisting of a processor and memory programmed to perform one or more functions embodied in a computer program. Alternatively, the control unit and methods described in this disclosure can also be implemented by a special-purpose computer consisting of a processor composed of one or more special-purpose hardware logic circuits. Alternatively, the control unit and methods described in this disclosure can also be implemented by one or more special-purpose computers consisting of a processor and memory programmed to perform one or more functions and a processor composed of one or more hardware logic circuits. Furthermore, the computer program can also be stored as instructions executable by a computer on a non-transferable tangible recording medium readable by a computer.

[0079] In addition to the claims, this disclosure includes the following disclosure.

[0080] [1]

[0081] A vehicle-mounted communication unit (4) is used when a push server receives a push data sending request from an application server and thus receives push data from the push server, and then sends the received push data to the vehicle-mounted electronic control device.

[0082] The system includes a startup control unit (4a). When the application server sends a startup start instruction to the push server immediately after the application on the cloud side is launched, the startup control unit causes the vehicle electronic control device, which is the destination of the push data, to start the startup process.

[0083] [2]

[0084] According to the vehicle-mounted communication device described in [1], wherein,

[0085] The aforementioned start control unit initiates the start-up process of the vehicle electronic control device that is the destination of the push data, but does not initiate the start-up process of vehicle electronic control devices that are not the destination of the push data.

[0086] [3]

[0087] According to the vehicle-mounted communication device described in [1] or [2], wherein,

[0088] The aforementioned vehicle electronic control device, which determines the starting object to initiate the starting process based on the starting object information, is a starting control unit.

[0089] [4]

[0090] According to the vehicle-mounted communication device described in [3], wherein,

[0091] The aforementioned startup control unit synchronizes the startup object information with the aforementioned push server.

[0092] [5]

[0093] The vehicle-mounted communication device according to any one of [1] to [4], wherein,

[0094] The aforementioned startup control unit causes the aforementioned vehicle electronic control device, which serves as the destination for the push data, to begin startup processing in a low-power state.

[0095] [6]

[0096] The vehicle-mounted communication device according to any one of [1] to [5], wherein,

[0097] The device is equipped with a first startup completion notification unit (4b). When the vehicle electronic control device completes the startup process, the first startup completion notification unit sends a startup completion notification to the push server indicating that the vehicle electronic control device has completed the startup process.

[0098] [7]

[0099] One type of push server is a push server (3) that sends push data to the vehicle communication unit when it receives a push data sending request from the application server.

[0100] The device is equipped with a startup start indication notification unit (3a). When a startup start indication is notified from the application server immediately after the application on the cloud side is launched, the startup start indication notification unit notifies the vehicle communication unit, which is the destination of the push data, of the startup start indication notification.

[0101] [8]

[0102] According to the push server described in [7], wherein,

[0103] When the aforementioned vehicle communication mechanism completes the startup process of the aforementioned vehicle electronic control device, it will send a startup completion notification to the aforementioned push server, indicating that the aforementioned vehicle electronic control device has completed the startup process.

[0104] The aforementioned push server has a second startup completion notification unit (3b). When a startup completion notification is received from the aforementioned vehicle communication unit, the aforementioned second startup completion notification unit sends the startup completion notification to the aforementioned application server.

[0105] [9]

[0106] According to the push server described in [7] or [8], wherein,

[0107] The system includes a session establishment unit (3c), which establishes a session with the application when a startup completion notification is received from the vehicle communication unit.

[0108]

[10]

[0109] According to any one of [7] to [9], the push server, wherein,

[0110] When a session based on the above session establishment section is successfully established, push data will be directly delivered to the application where the session was successfully established.

[0111]

[11]

[0112] According to the push server described in

[10] , wherein,

[0113] It has a destination determination unit (3d) that determines the destination of the pushed data.

[0114]

[12]

[0115] According to the push server described in [9] or

[10] , wherein,

[0116] When session establishment based on the above session establishment unit fails, push data will be sent to the above vehicle communication unit.

Claims

1. A vehicle-mounted communication device, wherein when a push server receives a push data sending request from an application server and the vehicle-mounted communication device receives push data from the push server, the vehicle-mounted communication device (4) sends the received push data to a vehicle-mounted electronic control device, wherein, The aforementioned vehicle communication unit includes a startup control unit (4a). When the application on the cloud side is started, the startup control unit immediately notifies the push server of a startup start instruction from the application server and is notified of the startup start instruction from the push server. The startup control unit then causes the vehicle electronic control device, which is the destination of the push data, to start the startup process.

2. The vehicle-mounted communication device according to claim 1, wherein, The aforementioned start control unit initiates the start-up process of the vehicle electronic control device that is the destination of the push data, but does not initiate the start-up process of vehicle electronic control devices that are not the destination of the push data.

3. The vehicle-mounted communication device according to claim 1, wherein, The aforementioned vehicle electronic control device, which determines the starting object to initiate the starting process based on the starting object information, is a starting control unit.

4. The vehicle-mounted communication device according to claim 3, wherein, The aforementioned startup control unit synchronizes the startup object information with the aforementioned push server.

5. The vehicle-mounted communication device according to claim 1, wherein, The aforementioned startup control unit causes the aforementioned vehicle electronic control device, which serves as the destination for the push data, to begin startup processing in a low-power state.

6. The vehicle-mounted communication device according to any one of claims 1 to 5, wherein, The device is equipped with a first startup completion notification unit (4b). When the vehicle electronic control device completes the startup process, the first startup completion notification unit sends a startup completion notification to the push server indicating that the vehicle electronic control device has completed the startup process.

7. A push server, which, upon receiving a push data sending request from an application server, sends the push data to the aforementioned vehicle-mounted communication device, wherein... The aforementioned push server (3) is equipped with a startup start indication notification unit (3a). When the application on the cloud side is started and immediately notified of a startup start indication from the application server, the aforementioned startup start indication notification unit notifies the vehicle communication unit, which is the destination of the push data, of the startup start indication.

8. The push server according to claim 7, wherein, When the aforementioned vehicle communication mechanism completes the startup process of the aforementioned vehicle electronic control device, it will send a startup completion notification to the aforementioned push server, indicating that the aforementioned vehicle electronic control device has completed the startup process. The aforementioned push server has a second startup completion notification unit (3b). When a startup completion notification is received from the aforementioned vehicle communication unit, the aforementioned second startup completion notification unit sends the startup completion notification to the aforementioned application server.

9. The push server according to claim 8, wherein, The system includes a session establishment unit (3c), which establishes a session with the application when the system receives a startup completion notification from the vehicle communication unit.

10. The push server according to claim 9, wherein, When a session is successfully established based on the above session establishment section, the push data will be directly delivered to the application where the session was successfully established.

11. The push server according to claim 10, wherein, It has a destination determination unit (3d) that determines the destination of the pushed data.

12. The push server according to claim 9 or 10, wherein, When session establishment based on the above session establishment unit fails, push data will be sent to the above vehicle communication unit.

Images