JP5966697B2 - Information processing device - Google Patents

Description

  The present invention relates to an information processing apparatus.

  Conventionally, for example, in the field of automobile technology, a communication protocol called CAN (Controller Area Network) (registered trademark) has been adopted. Using this CAN, a diagnostic tool is connected to an ECU (Electric Control Unit) that controls the operation of the vehicle via the CAN bus, and a request message for diagnosis is transmitted from the diagnostic tool to check the operation state of the ECU. Systems for performing diagnosis are known.

  In this type of system, when a plurality of diagnostic tools are connected, there is a possibility that one ECU receives each request message from each diagnostic tool at the same time. For this reason, the protocol of the diagnostic service communication specification ISO14230 currently used requires that request messages from a plurality of diagnostic tools be processed in parallel.

  On the other hand, in the protocol of ISO 14229, which is the next communication specification, in order to simplify processing, only request messages from a diagnostic tool having a high priority (priority) among a plurality of diagnostic tools are accepted, and after processing of the request message is completed. A request message is received from a low-priority diagnostic tool.

  As what diagnoses the operation state of ECU according to priority, the multitask system disclosed by patent document 1 is known. The one described in Patent Document 1 executes an application with the highest priority among applications in an executable state, and an application with a lower priority is executed after the application with a higher priority ends.

JP 2009-251663 A

  However, in the one described in Patent Document 1, it is necessary to check whether the application is terminated regularly or every time a new request message is received, and thus there is a problem that a large amount of CPU resources may be consumed. was there.

  Specifically, when diagnosing the operation state of the ECU, for example, there are cases where a large number of actuators are operated to obtain the operation results. In such a case, the confirmation destination of the operation state is diverse, A process for notifying the operation state for each confirmation destination is required. Therefore, in such a situation, the one described in Patent Document 1 has a problem of consuming a large amount of CPU resources.

  The present invention has been made to solve the above-described conventional problems, and an object thereof is to provide an information processing apparatus capable of suppressing consumption of CPU resources.

In order to achieve the above object, the information processing apparatus according to the present invention includes (1) a request message mounted on a vehicle , connected to a plurality of clients, and including identification information of a transmission source and requesting execution of a predetermined application. An information processing apparatus that receives from a client, the priority determining unit that determines the priority of the client that has transmitted the request message based on the identification information, and the vehicle ignition is turned off and then turned off. Means for recording a reception history on the condition that a request message from a client having a predetermined priority among the clients is received during the period until it is turned on again, and whether or not the reception history is recorded Arbitration means for arbitrating which client's request is permitted based on the request, and the arbitration means permits Includes an application executing unit for executing the application according to determined, wherein the arbitration means, during the period, on the condition that the reception history is not recorded, a low priority client lower than the predetermined priority The request from the low priority client is rejected on the condition that the request from the client is permitted and the reception history is recorded .

  With this configuration, the information processing apparatus according to the present invention receives a request message from a client having a predetermined priority during a predetermined period, and then receives a request from a client having a priority lower than the predetermined priority. Since there is no need to execute the application related to the request message, even when an application for obtaining diagnostic data by driving various actuators or the like is executed, a process of notifying the client of the operation state for each actuator becomes unnecessary. Therefore, the information processing apparatus according to the present invention can suppress consumption of CPU resources.

In order to achieve the above object, the information processing apparatus according to the present invention includes (2) a request message mounted on a vehicle, connected to a plurality of clients, and including identification information of a transmission source and requesting execution of a predetermined application. An information processing apparatus that receives from a client, the priority determining unit that determines the priority of the client that has transmitted the request message based on the identification information, and the vehicle ignition is turned off and then turned off. Means for recording a reception history on the condition that a request message from a client having a predetermined priority among the clients is received during the period until it is turned on again, and whether or not the reception history is recorded Arbitration means for arbitrating which client's request is permitted based on the request, and the arbitration means permits And application executing means for executing an application according to the determined, that previous request message received before one of the most recent latest request message received is a specific request message which is determined in advance from the predetermined priority of the client Execution confirmation means for confirming whether or not the application execution means has completed execution of the immediately preceding execution application related to the specific request message, or the arbitration means, during the period, On the condition that the previous request message is not the specific request message and the reception history is not recorded, a request from a low priority client lower than the predetermined priority is permitted, and the previous request message is the specific request message. on condition that the reception history not request message is recorded, Serial rejects the request from the low priority client, to condition said previous request message has the a specific request message execution of the immediately preceding execution application is complete, allow the request from the low priority client The request from the low priority client is rejected on condition that the immediately preceding request message is the specific request message and the immediately preceding execution application is being executed.

  With this configuration, the information processing apparatus according to the present invention executes the application related to the latest request message from the low priority client only when the immediately preceding request message is a predetermined specific request message. It is possible to suppress the consumption of CPU resources rather than confirming the completion of application processing for a message.

  In the information processing apparatus according to (1) or (2) above, (3) the arbitration unit is configured to execute the low priority on a condition that an application related to a request message from the low priority client is being executed. A request from a high priority client having a higher priority than the client is permitted, and the application execution means executes the application related to the request from the high priority client in parallel with the application being executed. It has the structure which is.

  With this configuration, the information processing apparatus according to the present invention can update the latest request message from the high-priority client without confirming the completion of execution of the application even when the application related to the request message from the low-priority client is being executed. Since such an application is executed in parallel, it is possible to suppress the consumption of CPU resources rather than checking the completion of processing of the application.

  ADVANTAGE OF THE INVENTION According to this invention, the information processing apparatus which can suppress consumption of CPU resource can be provided.

It is a block block diagram of the vehicle in the 1st Embodiment of this invention. It is a software block diagram of 1st ECU in the 1st Embodiment of this invention. It is a structure explanatory drawing of the frame according to the CAN protocol in the 1st Embodiment of this invention. It is a timing chart which shows the outline | summary of operation | movement of 1st ECU in the 1st Embodiment of this invention. It is a flowchart which shows operation | movement of 1st ECU in the 1st Embodiment of this invention. It is a software block diagram of 1st ECU in the 2nd Embodiment of this invention. It is a timing chart explaining the function of the request determination part and the execution confirmation part in the 2nd Embodiment of this invention. It is a timing chart explaining the function of the request determination part and the execution confirmation part in the 2nd Embodiment of this invention. It is a flowchart which shows operation | movement of 1st ECU in the 2nd Embodiment of this invention. It is explanatory drawing of the parallel processing which the application execution part in the 2nd Embodiment of this invention performs.

  Embodiments of the present invention will be described below with reference to the drawings. In addition, the example which applied the information processing apparatus which concerns on this invention to ECU of the vehicle to which a some diagnostic tool is connected is given.

(First embodiment)
First, the configuration will be described.

  As shown in FIG. 1, a vehicle 50 according to an embodiment of the present invention is communicably connected to clients 1 and 2, and includes a first ECU 10, a second ECU 20 and a third ECU 30 as servers, a diagnostic connector 51, a wireless communication device 52, A CAN bus 53 is provided. Here, each of the first ECU 10, the second ECU 20, and the third ECU 30 constitutes an information processing apparatus according to the present invention.

  The client 1 is a service tool used by, for example, an automobile dealer, and is connected to the diagnostic connector 51. The client 2 is a remote tool provided in a service center of a telematics service such as the well-known G-Book (registered trademark), and is connected to the wireless communication device 52 via a wireless communication line. The clients 1 and 2 are configured to transmit request messages for diagnosing the operation states of the first ECU 10, the second ECU 20, and the third ECU 30 via the CAN bus 53.

  The first ECU 10, the second ECU 20, and the third ECU 30 operate as, for example, an engine ECU, a transmission ECU, a battery ECU, and the like. These ECUs are connected to each other via a CAN bus 53. A diagnostic connector 51 and a wireless communication device 52 are connected to the CAN bus 53.

  Next, the hardware configuration of the first ECU 10 will be described. Note that the second ECU 20 and the third ECU 30 have the same configuration as that of the first ECU 10, and a description thereof will be omitted.

  The first ECU 10 includes a central processing unit (CPU) 11 as a central processing unit, a read only memory (ROM) 12 in which programs and the like are stored, and a random access memory (RAM) 13 in which data and the like are temporarily stored. And.

  Further, the first ECU 10 includes an input unit 14 to which various sensors are connected, an output unit 15 that outputs control signals based on calculation results of the CPU 11 to various actuators, a communication unit 17 connected to the CAN bus 53, and various types. And a bus 18 for transmitting signals. When the first ECU 10 is an engine ECU, for example, the various sensors are an engine speed sensor, a throttle opening sensor, and the like, and the various actuators are a throttle valve, a fuel injection valve, and the like.

  Next, the software configuration of the first ECU 10 will be described with reference to FIG.

  As shown in FIG. 2, the first ECU 10 includes a communication processing unit 101, a network layer processing unit 102, a session layer processing unit 103, a service reception instruction unit 104, and an application execution unit 105.

  Here, the network layer processing unit 102 and the session layer processing unit 103 are signals corresponding to the third layer (network layer) and the fifth layer (session layer) defined by the OSI (Open Systems Interconnection) basic reference model, respectively. Processing is to be executed.

  The communication processing unit 101 communicates with the client 1 via the diagnostic connector 51 via the CAN bus 53 and communicates with the client 2 via the wireless communication device 52.

  The network layer processing unit 102 assembles a message for diagnosis received from the clients 1 and 2 as a request message and outputs the request message to the session layer processing unit 103.

  The frame according to the CAN protocol output from the network layer processing unit 102 has a format as shown in FIG. 3A, and an arbitration field for storing a CAN-ID for identifying the frame; It contains a data field that stores the data to be transferred.

  Here, the CAN-ID stored in the arbitration field in the frame is set for each type of frame, is used to identify the contents of the data and the client, and is used to determine the priority in arbitration in communication. It also represents a number.

  The data field includes areas of N_PCI (Network Protocol Control Information) and N_Data (Network Data). A diagnosis message for diagnosing the operation state of a predetermined ECU is stored in the N_Data area.

  As shown in FIG. 3B, the diagnostic message includes a request message and a response message in response to the request message.

  The request message includes areas of required service ID (SID), optional sub function, data ID (Data ID), and data (Data). The service ID indicates the outline of the requested diagnostic service and is represented by a 1-byte identification number. In the sub-function area, a 1-byte identification number indicating details of the requested diagnostic service is described. In the data ID area, an ID number of 1 to 2 bytes indicating the target of the requested diagnostic service is described. In the data area, data necessary for implementing the diagnostic service is described.

  The response message has the same configuration as the request message, but the contents described in each area are different from the request message. In the response message, a value obtained by adding “0x40” to the service ID of the request message is described in the service ID area as an identification number for confirming the requested diagnostic service. In the subfunction area, the value of the requested subfunction is described as it is. In the data ID area, the value of the requested data ID is described as it is. In the data area, data obtained by executing the diagnostic service is described.

  By specifying the service ID in the request message, the clients 1 and 2 request, for example, battery voltage measurement data from the battery ECU, or forcibly drive the actuator or perform routines dedicated to diagnosis to a predetermined ECU. It is possible to request data of operation results when used.

  Returning to FIG. 2, the session layer processing unit 103 includes a priority determination unit 103a that determines the priority of the client that transmitted the request message, and an arbitration unit 103b that arbitrates execution of the application according to the priority.

  The priority determination unit 103a determines the priority of the client based on the CAN-ID included in the request message. Here, the priority determination unit 103a constitutes a priority determination unit according to the present invention. In the present embodiment, it is assumed that the client 1 has a higher priority than the client 2.

  The arbitration unit 103b accepts a request message from the low-priority client 2 before accepting a request message from the high-priority client 1, and after accepting a request message from the high-priority client 1, the arbitration unit 103b The arbitration is performed such that the request message from the client 2 is not accepted. Here, the arbitrating unit 103b constitutes an arbitrating unit according to the present invention.

  The service reception instructing unit 104 refers to the service ID included in the request message, receives processing such as output and deletion of diagnostic service result information, forced driving of various actuators, execution of routine processing dedicated to diagnosis, and the like. The execution unit 105 is instructed.

  Based on an instruction from the service reception instruction unit 104, the application execution unit 105 executes diagnostic service information acquisition, forced driving of each actuator, routine processing dedicated to diagnosis, and the like, and outputs the result data. . Here, the application execution unit 105 constitutes an application execution unit according to the present invention.

  Next, the operation will be described.

  First, an outline of the operation will be described with reference to a timing chart shown in FIG. Note that the operation cycle shown in FIG. 4 corresponds to a predetermined period according to the present invention and corresponds to “operation cycles” described in the specification of ISO14229. In the present embodiment, a period from when the ignition is turned on to when it is turned off and then turned on again is defined as an operation cycle.

  As shown in FIG. 4, when the client 1 transmits a request message 1 to the first ECU 10 in the operation cycle A, the request message 1 is sent to the session layer processing unit 103 via the communication processing unit 101 and the network layer processing unit 102. Sent. The session layer processing unit 103 records a reception history indicating that a request message from the client 1 having a higher priority among the clients 1 and 2 has been received. For example, data indicating that a request message has been received from the client 1 and data such as a service ID and a data ID included in the request message are recorded in the reception history.

  The session layer processing unit 103 transmits the request message 1 to the service reception instruction unit 104, and the service reception instruction unit 104 causes the application execution unit 105 to execute the application based on the service ID included in the request message 1.

  The application execution unit 105 receives a response message indicating that it has received processing of an application for implementing a diagnostic service specified by the service ID included in the request message 1 (hereinafter referred to as “application related to the request message 1”). 1 is transmitted to the service reception instruction unit 104, and the application related to the request message 1 is executed. The response message 1 is finally received by the client 1.

  After that, in the operation cycle A, a case where the client 2 having a lower priority than the client 1 transmits a request message will be described.

  When the client 2 transmits the request message 2 during a period when the execution processing of the application execution unit 105 is not completed, the session layer processing unit 103 has already recorded the reception history of the high priority client 1 Therefore, arbitration is performed so that the request message 2 is not accepted. That is, the application related to the request message 2 is not executed by the application execution unit 105.

  Even if the client 2 transmits the request message 3 after the execution processing of the application execution unit 105 is completed, the request message 3 is not accepted because the reception history of the high priority client 1 is already recorded. Mediation.

  Note that after the reception history of the client 1 is recorded, the session layer processing unit 103 includes a service ID and a data ID different from the data ID recorded in the reception history in the request message from the client 2. Even if the request message is received, the request message from the client 2 is not accepted.

  When the operation cycle A ends and the client 2 transmits the request message 4 in the subsequent operation cycle B, the session layer processing unit 103 has not recorded the reception history of the high priority client 1. Arbitration processing is not performed. Therefore, for example, the application execution unit 105 transmits the response message 4 indicating that the process related to the request message 4 has been received to the service reception instruction unit 104, and executes the application related to the request message 4. The response message 4 is finally received by the client 2.

  Next, the operation will be described with reference to the flowchart shown in FIG.

  The CPU 11 determines whether an operation cycle has been started (step S11). If the CPU 11 does not determine that the operation cycle has started, it repeats step S11.

  On the other hand, when determining that the operation cycle has started, the CPU 11 determines whether a request message has been received from the client 1 or 2 (step S12).

  In step S12, when the CPU 11 determines that the request message has been received, the CPU 11 records the transmission source data indicating the transmission source client that transmitted the request message in the RAM 13 based on the CAN-ID included in the request message ( Step S13). This transmission source data is represented, for example, by turning on or off a specific bit, and is updated every time a request message is received.

  The CPU 11 determines the priority of the transmission source client that has transmitted the request message based on the CAN-ID included in the request message (step S14).

  In step S14, when the transmission source of the request message is the high priority client 1, the CPU 11 records the reception history data in the RAM 13 (step S15).

  On the other hand, when the transmission source of the request message is the low priority client 2 in step S14, the CPU 11 determines whether or not the reception history of the high priority client 1 is recorded (step S16).

  In step S16, if the CPU 11 determines that the reception history of the high priority client 1 is recorded, the CPU 11 performs arbitration (step S17) and returns to step S12. That is, the CPU 11 does not accept a request message from the client 2 when the acceptance history of the client 1 is recorded.

  After recording the reception history at step S15 and when determining that the reception history is not recorded at step S16, the CPU 11 executes processing of the application related to the request message (step S18) and transmits a response message. (Step S19).

  The CPU 11 determines whether or not the operation cycle has ended (step S20). If it is determined that the operation cycle has ended, the process ends. If it has not been determined that the operation cycle has ended, the process returns to step S12. .

  As described above, the first ECU 10 in the present embodiment records a reception history when receiving a request message from the high priority client 1 in one operation cycle, and from the low priority client 2 received thereafter. For example, even when various actuators are driven to obtain diagnostic data, processing for notifying the client 1 or 2 of the operation state for each actuator is not required.

  Therefore, the first ECU 10 in the present invention can suppress consumption of CPU resources.

  In the embodiment described above, the number of clients is two, but the present invention is not limited to this. For example, when there are three or more clients and each has a different priority, the reception history is kept and request messages from clients with a priority lower than a predetermined priority are not accepted. Thus, the same effect as described above can be obtained.

(Second Embodiment)
First, the configuration will be described.

  Since the hardware configuration of the first ECU 40 in the present embodiment is the same as that of the first ECU 10 in the first embodiment (FIG. 1), the illustration is omitted, and the software configuration will be described with reference to FIG. In addition, the same number is attached | subjected to the structure similar to 1st Embodiment, and the description is abbreviate | omitted.

  As shown in FIG. 6, the first ECU 40 in the present embodiment includes a session layer processing unit 106. The session layer processing unit 106 includes a request determination unit 106a and an execution confirmation unit 106b in addition to the priority determination unit 103a and the arbitration unit 103b.

  The request determination unit 106a determines whether the received request message is a predetermined specific request message based on the service ID included in the received request message. This specific request message includes a predetermined specific service ID. The specific service ID is, for example, a service ID for requesting a diagnostic service (hereinafter, referred to as “ID-driven diagnostic service”) using a routine dedicated to forced driving of the actuator or a diagnosis.

  When the request determination unit 106a determines that the request message is a specific request message and then receives the request message next time, the execution confirmation unit 106b determines whether the application execution unit 105 has received the application related to the specific request message received immediately before. It is designed to check whether or not the execution of is completed. Here, the execution confirmation unit 106b constitutes an execution confirmation unit according to the present invention.

  Functions of the request determination unit 106a and the execution confirmation unit 106b will be described with reference to FIGS. 7 and 8, only the session layer processing unit 106 and the application execution unit 105 are shown in the software configuration of the first ECU 40, and other illustrations are omitted.

  FIG. 7 shows a state in which the client 1 transmits the request message 11 and the application execution unit 105 returns the response message 11 by executing the processing related to the request message 11. As illustrated, even if the client 2 transmits the request message 12 before the session layer processing unit 106 receives the request message 11 and transmits the response message 11, the arbitration unit 103b of the session layer processing unit 106 Since the priority of the client 2 is lower than that of the client 1, arbitration is performed so that the application related to the request message 12 is not executed.

  In an actual vehicle, in most cases, the request message from the low priority client 2 is not accepted in the state shown in FIG. Here, if the service ID simply requests a diagnostic service for reading data, for example, it can be determined that the processing is completed when the application execution unit 105 returns a response message. However, if the service ID is for requesting an ID-driven diagnostic service, the application execution unit 105 is defined in the standard to send a response message when the process is accepted, not when the process is completed. Therefore, when the response message is returned, it is not possible to know when the processing is finished.

  Therefore, the request determination unit 106a determines whether or not the request message is a request message (specific request message) for requesting an ID-driven diagnosis service, based on the service ID included in the received request message. If the request determination unit 106a determines that the request message is a specific request message, when the request message is received after the specific request message, the execution confirmation unit 106b completes execution of the application related to the specific request message. It is to check whether or not.

  Specifically, in FIG. 8, the request message 13 is transmitted from the client 1, and the request message 13 requests an ID-driven diagnostic service as a result of the request determination unit 106a of the session layer processing unit 106 referring to the service ID. It is assumed that it is a specific request message. In this case, when the next request message is received, the execution confirmation unit 106b of the session layer processing unit 106 confirms whether or not the application execution process related to the immediately preceding specific request message has been completed.

  For example, when the client 2 transmits the request message 14 following the request message 13 that is a specific request message, the execution confirmation unit 106b determines that the application execution process related to the specific request message has not been completed. The arbitration unit 103b of the session layer processing unit 106 performs arbitration such that the request message 14 is not accepted.

  On the other hand, when the client 2 transmits the request message 15 following the request message 13 that is the specific request message, the execution confirmation unit 106b determines that the execution processing of the application related to the immediately preceding specific request message has been completed. Therefore, the arbitration unit 103b does not perform arbitration, and the application related to the request message 15 is executed.

  Next, the operation will be described with reference to the flowchart shown in FIG. In addition, the same number is attached | subjected to the step similar to 1st Embodiment, and the description is abbreviate | omitted.

  In step S14, when the CPU 11 determines that the transmission source of the request message is the high priority client 1, after recording the reception history in step S15, the CPU 11 stores the service ID (SID) data included in the request message. It records in RAM13 (step S21).

  On the other hand, if the CPU 11 determines in step S14 that the request message is transmitted from the low-priority client 2, the CPU 11 reads the service ID data of the request message received immediately before from the RAM 13 (step S22).

  Based on the read service ID, the CPU 11 determines whether or not the request message received immediately before is a specific request message (step S23).

  In step S23, if the CPU 11 determines that the request message received immediately before is a specific request message, the CPU 11 determines whether the processing of the application related to the specific request message has been completed (step S24).

  If the CPU 11 determines in step S24 that the processing of the application related to the specific request message has been completed, the process proceeds to step S21.

  In step S23 described above, when the CPU 11 does not determine that the request message received immediately before is the specific request message, the CPU 11 determines whether or not the reception history of step S16 is recorded.

  In step S16, if the CPU 11 determines that the reception history is recorded, and if it is not determined in step S24 that the processing of the application related to the specific request message has been completed, the process proceeds to step S17, and arbitration is performed. Run.

  In step S16, when the CPU 11 does not determine that the reception history is recorded, the process proceeds to step S21.

  Incidentally, in step S18, during the processing of the application related to the request message of the client 2, the processing of the application related to the request message of the client 1 may be executed. This will be described with reference to FIG.

  FIG. 10 shows a case where the client 2 transmits the request message 16 and the client 1 transmits the request message 17 while the application execution unit 105 executes the application related to the request message 16. In this case, the priority is determined in step S14 shown in FIG. 9, and the client 1 has a higher priority than the client 2. Therefore, in the application execution unit 105, the application related to the request message 17 is the request message 16 It will be executed in parallel with the application concerned. Note that the parallel processing by the application execution unit 105 shown in FIG. 10 can be performed in the first ECU 10 in the first embodiment in the same manner as described above.

  As described above, the first ECU 40 according to the present embodiment receives a request message from the high priority client 1 and receives a request message from the client 1 when the next request message is received from the low priority client 2. Only when a request message is a specific request message, it is configured to confirm the completion of application processing related to the specific request message. Can be suppressed.

  Further, the first ECU 40 in the present embodiment does not confirm the completion of execution of the application even when the application related to the latest request message from the low priority client 2 is being executed, but the latest request from the high priority client 1. Since the application related to the message is executed in parallel, it is possible to suppress the consumption of CPU resources rather than checking the completion of processing of the application.

  As described above, the information processing apparatus according to the present invention has an effect that consumption of CPU resources can be suppressed, and is useful as an ECU of a vehicle to which a plurality of diagnostic tools are connected.

1, 2 Client 10, 40 First ECU (information processing device)
11 CPU
14 input unit 15 output unit 17 communication unit 20 second ECU (information processing device)
30 3ECU (information processing device)
Reference Signs List 51 diagnostic connector 52 wireless communication device 53 CAN bus 101 communication processing unit 102 network layer processing unit 103, 106 session layer processing unit 103a priority determination unit (priority determination means)
103b Arbitration part (arbitration means)
104 Service reception instruction unit 105 Application execution unit (application execution means)
106a request determination unit 106b execution confirmation unit (execution confirmation unit)

Claims (3)

An information processing apparatus mounted on a vehicle, connected to a plurality of clients, and receiving a request message including identification information of a transmission source and requesting execution of a predetermined application from each of the clients,
Priority determination means for determining the priority of the client that has transmitted the request message based on the identification information;
Records the reception history on the condition that a request message from a client of a predetermined priority among the clients is received during a period from when the vehicle ignition is turned on to when the vehicle is turned off and then turned on again. Means to
Arbitration means for arbitrating which client request is permitted based on whether the reception history is recorded;
Application execution means for executing an application related to the request permitted by the arbitration means;
With
During the period, the mediation means is
Allowing a request from a low priority client lower than the predetermined priority on the condition that the reception history is not recorded,
The request from the low priority client is rejected on the condition that the reception history is recorded.
An information processing apparatus characterized by that. An information processing apparatus mounted on a vehicle, connected to a plurality of clients, and receiving a request message including identification information of a transmission source and requesting execution of a predetermined application from each of the clients,
Priority determination means for determining the priority of the client that has transmitted the request message based on the identification information;
Records the reception history on the condition that a request message from a client of a predetermined priority among the clients is received during a period from when the vehicle ignition is turned on to when the vehicle is turned off and then turned on again. Means to
Arbitration means for arbitrating which client request is permitted based on whether the reception history is recorded;
Application execution means for executing an application related to the request permitted by the arbitration means;
On the condition that the previous request message received immediately before the latest received latest request message is a specific request message determined in advance from the client having the predetermined priority , the application execution means executes the specific request message. Execution confirmation means for confirming whether the execution of the immediately preceding application related to the application has been completed or is being executed;
With
During the period, the mediation means is
Permitting a request from a low priority client lower than the predetermined priority on condition that the immediately preceding request message is not the specific request message and the reception history is not recorded;
Rejecting the request from the low priority client on the condition that the previous request message is not the specific request message but the reception history is recorded ,
Permit the request from the low priority client on the condition that the immediately preceding request message is the specific request message and the execution of the immediately preceding execution application is completed;
The request from the low priority client is rejected on the condition that the immediately preceding request message is the specific request message and the immediately preceding execution application is being executed.
An information processing apparatus characterized by that. The arbitration means permits a request from a high priority client having a higher priority than the low priority client on condition that an application related to the request message from the low priority client is being executed. Yes,
The application execution means executes an application related to the request of the high priority client in parallel with the application being executed.
The information processing apparatus according to claim 1, wherein the information processing apparatus is an information processing apparatus.

Images