Vehicle control system, access control device, and access control method
By introducing multiple electronic control devices and collaboration control units into the vehicle control system, using the collaboration and policy storage units between functional modules to set the recognition policy, the problem that the API cannot eliminate inappropriate access requests is solved, and the vehicle control system is realized Improved safety and reliability.
Patent Information
- Application Number
- CN202380032487.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-04-07
- Filing Date
- 2023-04-04
- Publication Date
- 2024-11-22
AI Technical Summary
In vehicle control systems, the API cannot effectively exclude inappropriate access requests from recognized applications, especially in the case of third-party applications, inappropriate access requests due to insufficient knowledge may increase, resulting in unanticipated behavior of vehicle control .
A number of electronic control devices and a collaboration control unit are introduced into the vehicle control system. Through the collaboration and policy storage unit between functional modules, an approval policy is set to determine the legality of the access request, and only functional modules that meet a specific safety level are allowed to be safe. The relevant APIs are accessed to ensure that only functional modules that provide appropriate security levels can use the API.
Effectively suppress inappropriate API access requests, prevent unanticipated vehicle control behavior, simplify processing flow, and improve system security and reliability.
Smart Images

Figure CN119013668A_ABST
Abstract
Description
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] The present international application claims priority based on Japanese Patent Application No. 2022-064078 filed with the Japan Patent Office on April 7, 2022, the entire contents of which are incorporated herein by reference. Technical Field
[0003] The present disclosure relates to a technology for protecting vehicle functions. Background Art
[0004] Patent Document 1 listed below describes a technique that, in an open platform for mobile terminals, when access to a user resource from an application is detected, determines whether the access is permitted by referring to an access policy.
[0005] Patent document 1: Japanese Patent No. 6124627.
[0006] However, in the vehicle control system, a platform using an API is used. The API is an interface prepared to provide vehicle functions, and applications installed in the platform use the API to implement various functions.
[0007] The platform used in the vehicle control system needs to realize functions with limited resources while ensuring real-time performance. Therefore, the access policy for determining whether access rights are granted to each API is set, for example, for each application unit.
[0008] In this case, even if the access request dynamically generated during the execution of the application contains inappropriate control content, as long as it is an access request from an approved application, the API will accept the access request and execute the processing. In other words, the API cannot exclude inappropriate access requests from approved applications. An inappropriate access request refers to, for example, a request to control the vehicle with an acceleration exceeding the permitted range for an API that provides a function of controlling the acceleration of the vehicle.
[0009] Furthermore, when third-party applications are introduced in the future, unexpected and inappropriate access requests due to lack of knowledge of application creators may increase. Summary of the invention
[0010] In one technical solution of the present disclosure, a technology is provided to limit inappropriate access requests to an API in a vehicle control system.
[0011] A vehicle control system according to one technical aspect of the present disclosure includes a plurality of electronic control devices mounted on a vehicle and connected to an in-vehicle network. The plurality of electronic control devices includes a plurality of functional modules and a cooperative control unit.
[0012] The functional modules are configured to execute respective predetermined processes, and at least a part of the functional modules are configured to provide a function of controlling the motion of the vehicle. The cooperation control unit realizes cooperation among the plurality of functional modules.
[0013] At least some of the plurality of functional modules include a functional interface. The functional interface is an interface configured to provide its own functions to other functional modules.
[0014] The cooperation control unit includes a policy storage unit and an access control unit.
[0015] The policy storage unit is configured to store an authorization policy indicating a rule for authorizing access to an access request from an arbitrary functional module to an arbitrary functional interface.
[0016] When the access control unit receives an access request from any of the multiple functional modules, it determines whether to approve the access from the request source module to the request destination interface based on the approval policy. The request source module is a functional module that becomes the request source of the access request. The request destination interface is a functional interface that becomes the request destination of the access. The access control unit is configured to pass the access request to the request destination interface when the access is approved. The approval policy is set using the provision level and the request level, wherein the provision level is a security level indicating the security of the function guaranteed by the request source module, and the request level is a security level requested by the request destination interface to the request source module.
[0017] According to such a structure, only the access request from the function module that meets the request level of the function interface can be passed to the function interface of the access destination. Therefore, the function interface that provides the function related to security is freely used by the function module with low reliability, etc., thereby suppressing the execution of unexpected control. In addition, the functions provided by the function interface do not need to include the processing of the request from the function module that does not meet the request level, so the processing can be simplified.
[0018] An access control device in one technical solution of the present disclosure includes the above-mentioned multiple functional modules and a cooperation control unit.
[0019] According to the access control device, the same effects as those of the vehicle control system can be obtained.
[0020] In an access control method in a technical solution of the present disclosure, for an access request to a functional interface from any one of a plurality of functional modules, it is determined whether to approve access from a request source module to a request destination interface according to an approval policy. In the case of approving access, the access request is passed to the request destination interface. The approval policy is set using a provided level and a requested level, wherein the provided level is a security level indicating the security of the function provided by the request source module, and the requested level is a security level requested by the request destination interface to the request source module.
[0021] The plurality of functional modules are configured to execute the determined processing respectively. The functional interface is an interface provided by at least a part of the plurality of functional modules and used to provide the functions possessed by the module to other functional modules. The authorization policy indicates the rules for authorizing access to the access request to the functional interface. The request source module is the functional module that becomes the request source of the access request. The request destination interface is the functional interface that becomes the request destination of the access request.
[0022] According to the access control system, the same effects as those of the access control device can be obtained. BRIEF DESCRIPTION OF THE DRAWINGS
[0023] Figure 1 is a block diagram showing a vehicle control system.
[0024] Figure 2 It is a block diagram showing the structure of the ECU.
[0025] Figure 3 is a block diagram showing the structure of an API gateway.
[0026] Figure 4 This is a table illustrating the contents of the authorization policy.
[0027] Figure 5 This is an explanatory diagram illustrating API access control based on an API gateway.
[0028] Figure 6 It means in Figure 5 In the example shown, the result of determining whether or not the API can be accessed from the SW-C is a table of approval policy images.
[0029] Figure 7 This is an explanatory diagram illustrating API access control based on an API gateway.
[0030] Figure 8 This is an explanatory diagram showing a method of functionally dividing a service application composed of a plurality of microservices into applications that operate independently and allocating the functions to a plurality of SW-Cs, and a flow of processing in this case.
[0031] Fig. 9This is an explanatory diagram showing a method of functionally dividing a service application composed of a plurality of microservices for each security level and allocating the functions to a plurality of SW-Cs, and a flow of processing in this case.
[0032] Fig.10 This is an explanatory diagram showing a method of functionally dividing a service application composed of a plurality of microservices for each microservice and allocating the functions to a plurality of SW-Cs, and a flow of processing in this case.
[0033] Fig.11 This is a flowchart of the process executed by the access control unit.
[0034] Fig.12 This is a table illustrating the contents of the correspondence table. DETAILED DESCRIPTION
[0035] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings.
[0036] [1.Structure]
[0037] The following and attached Figure 1 The first embodiment of the present disclosure will be described.
[0038] The vehicle control system 1 of this embodiment is mounted on a vehicle. In addition to the manual driving function, the vehicle may also have an automatic driving function. The vehicle may also be a hybrid vehicle having an engine and an electric motor as driving sources. The vehicle is not limited to a vehicle having an automatic driving function and a hybrid vehicle, and may also be a vehicle having only a manual driving function, or a vehicle having only an engine or only an electric motor as a driving source. Hereinafter, a vehicle equipped with the vehicle control system 1 is referred to as a vehicle.
[0039] like Figure 1 As shown, the vehicle control system 1 includes one ECU 2, a plurality of ECUs 3, a plurality of ECUs 4, an external vehicle communication device 5, and an internal vehicle communication network 6. ECU is an abbreviation of Electronic Control Unit.
[0040] The ECU 2 integrates the plurality of ECUs 3 to achieve coordinated control of the entire vehicle.
[0041] ECU3 is set in each domain divided according to the function in the vehicle, and mainly performs the control of multiple ECU4 existing in the domain. Each ECU3 is connected to the subordinate ECU4 via a lower layer network (for example, CAN) that is separately set up. CAN is the abbreviation of Controller Area Network, which is a registered trademark. ECU3 has the function of uniformly managing the access rights for the subordinate ECU4 and authenticating the user. Domains are, for example, powertrain, body, chassis, and cockpit.
[0042] The ECU 4 connected to the ECU 3 belonging to the domain of the powertrain system includes, for example, an ECU 4 for controlling an engine, an ECU 4 for controlling a motor, and an ECU 4 for controlling a battery.
[0043] The ECU 4 connected to the ECU 3 belonging to the domain of the vehicle body includes, for example, an ECU 4 for controlling an air conditioner and an ECU 4 for controlling vehicle doors.
[0044] The ECU 4 connected to the ECU 3 belonging to the chassis domain includes, for example, an ECU 4 for controlling brakes and an ECU 4 for controlling a steering wheel.
[0045] The ECU 4 connected to the ECU 3 belonging to the cockpit domain includes, for example, an ECU 4 that controls the display of meters and navigation, and an ECU 4 that controls input devices operated by a vehicle occupant.
[0046] The external vehicle communication device 5 performs data communication with a communication device (eg, a cloud server) outside the vehicle via a wide area wireless communication network.
[0047] The in-vehicle communication network 6 includes CAN FD and Ethernet. Ethernet is a registered trademark. CAN FD is the abbreviation of CAN with Flexible Data Rate. CAN FD connects ECU2 with each ECU3 and the in-vehicle communication device 5 by bus. Ethernet connects ECU2 with each ECU3 and the in-vehicle communication device 5 individually. Figure 2 As shown, the ECU 2 includes an Ethernet switch 7 for switching the Ethernet to be used.
[0048] ECU2 is an electronic control device centered on a microcomputer having CPU2a, ROM2b, and RAM2c. The various functions of the microcomputer are realized by CPU2a executing a program stored in a non-migrating physical recording medium. In this example, ROM2b is equivalent to a non-migrating physical recording medium storing the program. In addition, by executing the program, a method corresponding to the program is executed. In addition, a part or all of the functions executed by CPU2a may be constituted in hardware by one or more ICs. In addition, the number of microcomputers constituting ECU2 may be one or more.
[0049] ECU3, ECU4 and the vehicle external communication device 5 are all electronic control devices, similar to ECU2, which are mainly composed of a microcomputer having a CPU, ROM, RAM, etc. In addition, the number of microcomputers constituting ECU3, ECU4 and the vehicle external communication device 5 may be one or more. ECU3 is an ECU that integrates more than one ECU4, and ECU2 is an ECU that integrates more than one ECU3, or integrates ECU3 and 4 of the entire vehicle including the vehicle external communication device 5.
[0050] Hereinafter, when the ECU 2 , ECU 3 , ECU 4 , and the vehicle external communication device 5 are not particularly distinguished, they are referred to as vehicle-mounted devices 2 to 5 .
[0051] The ECU 2 includes a real-time processing unit 10 and an application processing unit 20. When the ECU 2 includes a plurality of CPUs 2a, the real-time processing unit 10 and the application processing unit 20 may be implemented by processes executed by the same CPU or by processes executed by different CPUs.
[0052] The real-time processing unit 10 cooperates with the vehicle-mounted devices 3 to 5 connected via CAN FD to execute real-time vehicle control, etc. The application processing unit 20 cooperates with the vehicle-mounted devices 3 to 5 connected via Ethernet to execute various applications (e.g., entertainment system applications, etc.) that require high processing capabilities.
[0053] The application processing unit 20 has a function of transmitting instructions for processing based on various applications to the real-time processing unit 10. The real-time processing unit 10 has a function of transmitting information collected from the ECU and the like via CAN FD to the application processing unit 20. The real-time processing unit 10 and the application processing unit 20 cooperate with each other to realize various functions.
[0054] [2. Functional structure]
[0055] The software of the vehicle control system 1 is built along AUTOSAR. AUTOSAR is an architecture for autonomous driving and is the abbreviation of AUTomotive Open System Architecture. AUTOSAR not only provides communication between software components (hereinafter, SW-C) installed to realize various applications, but also provides functions related to cloud connection, security, etc. SW-C is software that is componentized to realize a certain function. An application contains more than one SW-C. In addition, the software of the vehicle control system 1 does not necessarily need to be built along AUTOSAR.
[0056] Each device belonging to the vehicle control system 1, namely, the ECU 2, ECU 3, ECU 4, and the vehicle external communication device 5, includes a platform. The platform provides an environment for executing SW-C written in a format that does not depend on hardware.
[0057] The platform has a runtime environment (hereinafter, RTE) and basic software (hereinafter, BSW). RTE is an interface that connects SW-Cs to each other and between SW-C and BSW. BSW is a layer that connects hardware to SW-C, including OS, drivers, middleware, etc. The functions of BSW are divided into small modules, and the functions of each module are provided to SW-C via API. API is the abbreviation of Application Programming Interface.
[0058] Hereinafter, the platform included in the real-time processing unit 10 is referred to as a first platform (hereinafter, first PF) 11 , and the platform included in the application processing unit 20 is referred to as a second platform (hereinafter, second PF) 21 .
[0059] like Figure 2 As shown, the real-time processing unit 10 includes a control system functional module group 12 as a collection of service applications (hereinafter referred to as service applications) operating on the first PF 11. The service application is an application that receives a request from a client, processes it, and returns a result.
[0060] The control system functional module group 12 has an API for accepting commands related to the movement of the vehicle, and is an application group for integrating the commands accepted by the API to achieve integrated vehicle control. The control system functional module group 12 outputs various commands to the vehicle-mounted devices 3 to 5 that are entities that execute control based on the commands via the in-vehicle communication network 6.
[0061] The first PF 11 includes a conversion gateway 111. The conversion gateway 111 has a function of converting a communication frame received by the real-time processing unit 10 via CAN FD into an Ethernet format and providing it to the application processing unit 20. In addition, the conversion gateway 111 has a function of converting a communication frame in the Ethernet format provided from the application processing unit 20 into a CAN FD format.
[0062] The application processing unit 20 includes a hypervisor 22 and executes software on a plurality of virtual machines. The hypervisor 22 may be omitted.
[0063] The application processing unit 20 includes a service system function module group 23 as a collection of service applications that operate on the second PF 21 .
[0064] The service system functional module group 23 is a collection of service applications. Each service application has one or more SW-Cs. Service applications are provided not only by vehicle manufacturers that manufacture vehicles, but also by third parties. As third parties that provide service applications, for example, data flexible application providers that provide services by collecting data from vehicles are listed.
[0065] The second PF 21 includes a control system function module group 25 , a data system function module group 26 , and an API gateway 30 .
[0066] The control system function module group 25 is a collection of programs having an API for accepting requests related to vehicle control from the service system function module group 23. The control system function module group 25 converts the API access request from the service system function module group 23, which is expressed in a form independent of the vehicle, into an API access request expressed in a form dependent on the vehicle, and provides it to the real-time processing unit 10. The APIs possessed by the control system function module group 25 include a motion system API for controlling the motion of the vehicle and a non-motion system API other than the motion system API. The API access request accepted by the motion system API is forwarded to the control system function module group 12, and is forwarded from the control system function module group 12 to the vehicle-mounted devices 3 to 5 that execute control based on the request via the in-vehicle communication network 6. The API access request accepted by the non-motion system API is forwarded to the vehicle-mounted devices 3 to 5 that execute control based on the request via the in-vehicle communication network 6.
[0067] The data system function module group 26 is a set of programs having an API for processing vehicle data acquired and accumulated via the real-time processing unit 10. The data system function module group 26 has the following function: abstracting and accumulating the vehicle data expressed in a vehicle-dependent form supplied from the real-time processing unit 10 in a vehicle-independent form. The data system function module group 26 may also have an API that provides a function of sending the specified vehicle data to the ECU or the like via Ethernet. In particular, when the destination is the external vehicle communication device 5, the external vehicle communication device 5 may also upload the sent vehicle data to the cloud.
[0068] In addition, the communication with other onboard devices 3 to 5 via the control system functional module group 25 is not limited to CAN FD, and Ethernet or other communication means may be used. In addition, the communication with other onboard devices 3 to 5 via the data system functional module group 26 is not limited to Ethernet, and CAN FD or other communication means may be used.
[0069] The API gateway 30 is configured to utilize the functions of a virtual function bus (hereinafter, VFB). VFB is a middleware that can realize communication between SW-Cs and communication between SW-Cs and BSWs regardless of hardware, communication protocols, etc., and is also called a software bus. Communication between SW-Cs refers to access from SW-Cs to APIs provided by other SW-Cs, and communication between SW-Cs and BSWs refers to access from SW-Cs to APIs provided by the control system function module group 25 and the data system function module group 26.
[0070] That is, the SW-C accesses various APIs via the API gateway 30 and implements desired functions by utilizing the functions provided by the accessed APIs.
[0071] When using an API, SW-C transmits an API access request. The API access request includes at least the process ID of the SW-C that is the request source and API-ID that is information indicating the API that is the request destination.
[0072] [3. Access restriction mechanism]
[0073] The access restriction mechanism for restricting access to the API from the SW-C in the API gateway 30 is described below. From the perspective of ensuring safety, the access restriction mechanism is set so that the execution of a service application with a low security level among the service applications belonging to the service system function module group 23 does not cause danger to the occupants of the vehicle.
[0074] The API gateway 30 is not only provided by the second PF 21 operating on the application processing unit 20 , but is also provided by a platform of all vehicle-mounted devices 2 to 5 that may be equipped with any one of the service system function module group 23 , the control system function module group 25 , and the data system function module group 26 .
[0075] like Figure 3 As shown, the API gateway 30 includes an information storage unit 31 and an access control unit 32 .
[0076] The information storage unit 31 stores a correspondence table 311, API information 312, application information 313, and an authorization policy 314. The correspondence table 311 is stored in the RAM 2c, and the API information 312, application information 313, and authorization policy 314 are stored in the ROM 2b. The API information 312, application information 313, and authorization policy 314 may also be stored in the non-volatile RAM 2c.
[0077] The correspondence table 311 is information that establishes a correspondence between a process ID dynamically allocated to a process, which is an execution unit of a program in an operating system (hereinafter, OS), and an application ID unique to a SW-C executed in the process. In addition, the correspondence table 311 is information that establishes a correspondence between an API-ID unique to each API and a process ID of a process of a SW-C that is a physical entity that executes the API. The correspondence table 311 is generated by the OS when a process of each SW-C is generated at the start of the system. The correspondence table 311 is stored in the RAM 2c.
[0078] The API information 312 indicates information related to the API identified by the API-ID. In particular, the API information 312 about the API that provides a function related to safety (hereinafter, the safety system API) includes the safety level (hereinafter, the request level) requested for the SW-C that is the source of the API access request. The safety system API includes, for example, an API that provides a function of controlling an actuator related to the movement of the vehicle (for example, front and rear acceleration, steering wheel), an API that provides a function of controlling the lighting of a lamp, and the like.
[0079] The application information 313 indicates information related to the SW-C identified by the application ID. The application information 313 about the SW-C that executes processing related to security in particular (hereinafter, the security system SW-C) includes a security level (hereinafter, the provision level) indicating the reliability of the security of the processing executed by the SW-C. When the SW-C has an additional API, the application information 313 includes the request level of the additional API. The additional API is an API prepared by the SW-C to provide its own functions to other SW-Cs.
[0080] The safety level uses, for example, the automotive safety level (hereinafter, ASIL). ASIL is a risk classification system defined in the ISO26262 standard regarding the functional safety of cars traveling on the road. ASIL is determined by three parameters: probability of exposure, controllability, and severity, and is represented by four stages: A to D. A is the lowest level, and D corresponds to the highest level. The request level of the non-safety system API is represented by QM. In other words, the safety level is essentially represented by five stages: QM, A to D, with QM being the lowest level. The safety level does not necessarily need to use ASIL, as long as it is defined as a safety level with multiple levels. Therefore, the safety level does not need to be the four stages of AD, and can also be less than three stages or more than five stages.
[0081] like Figure 4 As shown, the authorization policy 314 expresses whether the API is accessible from SW-C by means of a matrix representing all combinations of the provision level of SW-C and the request level of API. The provision level of SW-C indicates the security level of the call source. The request level of API indicates the security level of the call destination. In the figure, the ○ mark indicates accessible, and the × mark indicates inaccessible. Here, it is set to accessible when the provision level is above the request level, and it is set to inaccessible when the provision level is lower than the request level. For example, access requests to an API with a request level of QM are all accessible regardless of the provision level of the request source SW-C. In addition, access requests to an API with a request level of C are accessible when the provision level of the request source SW-C is C or D, and are inaccessible when the provision level of the request source SW-C is QM, A, or B.
[0082] Figure 4 The approval policy 314 shown is a table showing a common policy applied to all SW-Cs and all APIs. Alternatively, a table showing a policy adapted to each vehicle (hereinafter referred to as a correspondence table) created by combining the approval policy 314 and the information in the correspondence table 311 may be used.
[0083] like Fig.12 As shown, in the correspondence table, instead of the provision level that the SW-C can adopt, the provision level of each SW-C actually working on the second PF 21 is listed. It is also possible to establish a correspondence between the process ID corresponding to the SW-C and the provision level of each SW-C. In addition, in the adaptive authorization policy, instead of the request level that the API can adopt, the request level of each API actually prepared in the second PF 21 is listed. It is also possible to establish a correspondence between the process ID corresponding to the API and the request level of each API.
[0084] That is, in the correspondence table, whether each SW-C can access each API is expressed by a matrix representing all combinations of one or more SW-Cs each having a certain provision level and one or more APIs each having a certain request level. According to the content of the authorization policy 314, when the provision level is higher than the request level, access is set to accessible, and when the provision level is lower than the request level, access is set to inaccessible.
[0085] The above correspondence table is pre-incorporated with the result of the determination of access permission based on the permission policy 341, but the correspondence table may only indicate the correspondence between each SW-C and the provision level, and the correspondence between each API and the request level. In this case, based on the SW-C of the request source and the API of the request destination extracted from the access request, the provision level of the SW-C and the request level of the API are extracted with reference to the correspondence table. Then, based on the extracted provision level and request level, it is determined whether the SW-C of the request source can access the API of the request destination according to the permission policy 341. That is, it is also possible to determine whether access is permitted each time an access request is generated, using the permission policy 314.
[0086] In addition, the number of SW-Cs operating on the second PF 21 and the number of APIs provided by the second PF may increase or decrease, and the definition of the provision level and the request level may also change. Therefore, the authorization policy 314 and the correspondence table may be updated every time the software is updated.
[0087] The SW-C to which the provision level is assigned is designed to satisfy the assigned provision level. The provision level of the SW-C may be the same as or different from the request level of the API possessed by the SW-C.
[0088] The access control unit 32 receives an API access request from a SW-C, and the API access request indicates a process ID indicating a request source and an API-ID indicating an access destination. The access control unit 32 receives API access requests not only from SW-Cs belonging to the service system function module group 23, but also from all SW-Cs operating on a platform having an API gateway 30.
[0089] use Fig.11 The flowchart of FIG. 1 illustrates the processing executed by the access control unit 32.
[0090] In S110 , the access control unit 32 determines whether an API access request has been accepted from the SW-C. If the API access request has been accepted, the process moves to S120 . If the API access request has not been accepted, the process waits by repeating this step.
[0091] In S120, the access control unit 32 uses the authorization policy 314 based on the information indicated in the API access request to determine whether the access according to the API access request is allowed. Specifically, the access control unit 32 uses the correspondence table 311 to determine the application ID based on the process ID indicated in the received API access request. The access control unit 32 determines the provision level of the access request source, that is, SW-C (hereinafter, the request source SW-C), based on the application information 313 corresponding to the determined application ID. The access control unit 32 determines the request level of the API specified by the API-ID based on the API information corresponding to the API-ID indicated in the received API access request. Moreover, the access control unit 32 uses the authorization policy 314 to determine whether the access destination API is accessible from the request source SW-C based on the provision level determined by the process ID and the request level determined by the API-ID. In addition, the authorization policy does not necessarily need to be specified for all APIs. In the case where the API access request has an API that is not specified in the authorization policy as the request destination, S140 may be performed instead of S120 and S130.
[0092] In the next S130 , the access control unit 32 determines whether the result of the determination in S120 is that the access is allowed, and if so, the process shifts to S140 , and if not, the process shifts to S150 .
[0093] In S140 , the access control unit 32 transmits the API access request received in S110 to the access destination API and terminates the process. For example, the API access request is transmitted to the ECU 4 that performs engine control and brake control via the control system function module group 25 through CAN-FD or Ethernet communication.
[0094] In S150, the access control unit 32 abandons the API access request accepted in S110 and ends the process. At this time, the request source SW-C may be notified of the access denial.
[0095] [4.Use example]
[0096] [4-1. First example]]
[0097] like Figure 5 As shown, the case where the function module F1 and the function module F2 are installed is described. Function module F1 is a service system function module that implements the collision safety function. Function module F2 is a service system function module that implements the collision damage reduction function when driving at a low speed. It is assumed that the function module F1 and the function module F2 are each implemented by one SW-C.
[0098] For example, the function module F1 performs a deceleration process when an obstacle is detected ahead while the vehicle is traveling at a speed of 80 km / h or less. When the function module F1 decelerates due to a faulty operation at a speed of 80 km / h, the life of the occupants is in danger, so the provision level is set to the highest level D.
[0099] Function module F2 decelerates when an obstacle is detected in the front or rear when the vehicle is traveling at a speed of 15 km / h or less. Function module F2 decelerates when a faulty operation causes deceleration at 15 km / h, which causes a slight / moderate obstacle to the occupants, so the provision level is set to B.
[0100] The control system function module group 25 provides an API for controlling the accelerator and the brake according to the acceleration and deceleration requests from the function modules F1 and F2. The request level of the deceleration API used in the high speed area (hereinafter, the high speed area API) is set to D. The request level of the deceleration API used in the low speed area (hereinafter, the low speed area API) is set to B. The high speed area is set to 15 km / h<V≤80 km, for example, and the low speed area is set to V≥15 km / h, for example.
[0101] In this case, an image showing the result of determining whether each function module F1, F2 can access each API (i.e., high-speed area API, low-speed area API) provided by the control system function module group 25 according to the authorization policy 314 is as follows: Figure 6 shown.
[0102] That is, the access to the high-speed area API with a request level of D is permitted from the function module F1 providing the D level. The access to the high-speed area API with a request level of D is denied from the function module F2 providing the B level. The access request to the low-speed area API with a request level of B is permitted from the function module F2 providing the B level.
[0103] For example, when a service system function module with no set security level (i.e., provision level QM) is installed, all access requests from the service system function module to the API of the control system function module group 25 with set security level (i.e., request level A to D) are rejected.
[0104] [4-2. Second example]
[0105] like Figure 7As shown, the installation of function module F3 and function module F4 is described. Function module F3 is a service system function module that uses AI to implement adaptive cruise control (hereinafter, ACC). Function module F4 is a service system function module that implements the acceleration and deceleration mediation function and collision safety function in the advanced driver assistance system (hereinafter, ADAS). Among them, function module F3 and function module F4 are respectively implemented by one SW-C.
[0106] Function module F3 determines the vehicle condition through AI and executes the process of realizing acceleration and deceleration control close to the human operation feeling. Function module F3 is designed so that the upper limit of the requested acceleration and deceleration is less than the first threshold value. In function module F3, in the case of insufficient deceleration / malfunction due to a fault, slight / moderate damage will affect the occupants, so the provision level is set to B.
[0107] Function module F4 mediates the acceleration and deceleration requested by the ADAS function, and requests the mediated acceleration and deceleration to the control system function module group 12. In addition, when the deceleration request of the ADAS function is insufficient or there is no deceleration request, and when there is a risk of collision with the vehicle ahead, function module F4 performs processing to reduce the impact of the collision through function module F4. Function module F4 is designed so that the upper limit of the requested acceleration and deceleration is above the second threshold. The second threshold is set to a value greater than the first threshold. In function module F4, in the event of insufficient deceleration caused by a fault or non-operation of function module F4, the life of the occupants is in danger, so the provision level is set to D.
[0108] The function module F4 includes a mediation API for accepting the acceleration / deceleration request requested by the function module F3. The request level of the mediation API is set to B.
[0109] The control system functional module group 25 provides an acceleration / deceleration API for controlling the accelerator and the brake according to the acceleration / deceleration request from the service system functional module group 23 .
[0110] The acceleration / deceleration API is used in all speed ranges from a low vehicle speed range to a high vehicle speed range, and therefore the request level is set to D.
[0111] In this case, the function module F3 requests the API gateway 30 to access the mediation API of the function module F4. The API gateway 30 determines whether the access is allowed based on the authorization policy. Here, the provision level and the request level are both B, so the API gateway 30 determines that the access is allowed and passes the API access request from the function module F3 to the mediation API of the function module F4.
[0112] After the function module F4 mediates the acceleration / deceleration request received by the mediation API, it requests the API gateway 30 to access the acceleration / deceleration API provided by the control system function module group 25. The API gateway 30 determines whether access is allowed based on the approval policy. Here, the provision level and the request level are both D, so the API gateway 30 determines that it is accessible and passes the API access request from the function module F4 to the acceleration / deceleration API of the control system function module group 25.
[0113] [5. Installation method]
[0114] A software architecture representing a method of functionally dividing a service application composed of a plurality of microservices and allocating the functions to a plurality of SW-Cs (ie, service system functional modules) is described.
[0115] The service application is implemented by four microservices: "ACC", "Collision Safety", "Acceleration and Deceleration Mediation", and "Acceleration and Deceleration API".
[0116] "ACC" determines the vehicle condition through AI and performs the process of realizing automatic cruise control by accelerating and decelerating the vehicle in a manner close to the human operating feeling. The provision level is set to B. "Collision safety" performs the process of decelerating the vehicle when an obstacle with a possible collision is detected. "Acceleration and deceleration mediation" performs the process of mediating the acceleration and deceleration requests respectively requested from "ACC" and "Collision safety". "Acceleration and deceleration API" performs the process of generating an API access request for accessing the acceleration and deceleration API provided by the control system functional module group 12.
[0117] The provision level of "ACC" is set to B, and the provision level of "Collision Safety" and "Acceleration / Deceleration Mediation" is set to D. "Acceleration / Deceleration API" is not a process related to safety.
[0118] [5-1. Functional division by application unit]
[0119] A description will be given of a case where the service application is divided into processes and functions so that the ACC function and the collision safety function operate independently.
[0120] like Figure 8 As shown, a SW-C such as the ACC application (hereinafter referred to as the ACC process) implements multiple software "ACC", "Acceleration and deceleration mediation", and "Acceleration and deceleration API". In addition, a SW-C such as another collision safety application (hereinafter referred to as the collision safety process) implements multiple software "Collision safety", "Acceleration and deceleration mediation", and "Acceleration and deceleration API". The ACC process and the collision safety process both set the process provision level to D so that it is consistent with the highest provision level among the microservices included in this process.
[0121] In this case, if Figure 8 As shown in the processing flow of the thin line with an arrow in FIG. 2 , the ACC process and the collision safety process can both operate independently. In addition, the ACC process and the collision safety process can each access the acceleration / deceleration API provided by the control system functional module group 25 via the API gateway 30 .
[0122] However, when the ACC process and the collision safety process are running at the same time, the function for obtaining cooperation between the microservices in either process, namely the "acceleration and deceleration mediation", needs to be separated from the API gateway 30 for obtaining cooperation between the processes. In addition, the API access request to the control system function module group 25 based on the mediation result needs to be structured to be made from any process (for example, the collision safety process). The processing flow in this case is as follows Figure 8 Indicated by the thick line with arrows.
[0123] In this split method, it becomes difficult to guarantee the provision level of the ACC process as a whole in an ACC process where microservices with different provision levels coexist. In addition, in this split method, a separate mechanism is required to achieve cooperation between "acceleration and deceleration mediation", which complicates the structure.
[0124] [5-2. Functional division by provision level]
[0125] The following describes the case where a service application is functionally divided (i.e., process divided) with an eye on the level of provision of microservices.
[0126] like Fig. 9 As shown, one SW-C (hereinafter referred to as ACC process) is used to implement the software "ACC" with a provision level of B, and another SW-C (hereinafter referred to as collision safety process) is used to implement the software "collision safety" and "acceleration and deceleration mediation" with a provision level of D. The "acceleration and deceleration API" is processed at the later stage of "acceleration and deceleration mediation" and is therefore included in the collision safety process. By dividing the functions and processes in this way, the provision level of the ACC process can be set to B, and the provision level of the collision safety process can be set to D.
[0127] The collision safety process needs to have an API (ie, mediation API) for providing the "acceleration / deceleration mediation" function to other processes. The request level of the mediation API is set to B to match the provision level of "ACC".
[0128] In this case, if Fig. 9 As shown in the bold arrowed line in FIG. 1 , the access request from the ACC process to the mediation API provided by the collision safety process is executed via the API gateway 30 . Also, the access request from the collision safety process to the acceleration / deceleration API provided by the control system functional module group 25 is executed via the API gateway 30 .
[0129] In this segmentation method, each process is functionally segmented so that microservices with the same provision level are included in the same process, and microservices with different provision levels are not mixed in one process. Therefore, it is easy to ensure the provision level of each process. In addition, the collision safety process including "acceleration and deceleration mediation" needs to have a mediation API, so the structure of the collision safety process is complicated.
[0130] In addition, this segmentation method is Figure 7 The usage example shown corresponds to the following.
[0131] [5-3. Functional division by microservice]
[0132] The following describes how to divide the functions of a service application into microservices.
[0133] like Fig.10 As shown, one SW-C (hereinafter referred to as ACC process) is assigned to the software "ACC". Another SW-C (hereinafter referred to as collision safety process) is assigned to the software "collision safety". Another SW-C (hereinafter referred to as mediation process) is assigned to the software "acceleration and deceleration mediation". Another SW-C (hereinafter referred to as mediation process) is assigned to the software "acceleration and deceleration API".
[0134] By dividing the functions and processes in this way, the provision level of the ACC process can be set to B, and the provision level of the collision safety process and the mediation process can be set to D. In addition, the provision level of the API process is set to D in accordance with the request level of the acceleration / deceleration API provided by the control system functional module group 25 .
[0135] The mediation process has an API (i.e., mediation API) for providing the function of "acceleration and deceleration mediation" to the ACC process and the collision safety process. The API process has an API (hereinafter, request generation API) for providing the function of "acceleration and deceleration API" to the mediation process. The request level of the mediation API that accepts requests from the ACC process is set to B to match the provision level of the ACC process, and the request level of the mediation API that accepts requests from the collision safety process is set to D. The request level of the request generation API is conveniently set to D to match the provision level of the mediation process.
[0136] In this case, if Fig.10 As shown by the bold arrowed line in , access requests from the ACC process and the collision safety process to the mediation process are implemented via the API gateway 30. In addition, access requests from the mediation process to the API process are implemented via the API gateway 30. Furthermore, access requests from the API process to the control system functional module group 25 are implemented via the API gateway 30.
[0137] In this segmentation method, each process is functionally segmented so that each microservice is included in a different process. Microservices with different provision levels will not be mixed in one process, so it is easy to ensure the provision level of each process. In addition, the structure of each process is simple, but the communication volume between processes through the API gateway 30 increases.
[0138] [6. Correspondence of terms]
[0139] The API gateway 30 in the above-mentioned embodiment is equivalent to the access control device and the collaborative control unit in the present disclosure. The in-vehicle communication network 6 is equivalent to the in-vehicle network in the present disclosure. The service system functional module group 23, the control system functional module group 25, and the SW-C constituting the data system functional module group 26 are equivalent to the functional modules in the present disclosure. The API is equivalent to the functional interface in the present disclosure. The information storage unit 31 storing the approval policy 314 is equivalent to the policy storage unit in the present disclosure. The microservice is equivalent to the microfunctional module in the present disclosure.
[0140] [7. Effect]
[0141] According to the above detailed embodiments, the following effects are achieved.
[0142] (1) The API gateway 30 allows access to the API that is the access destination from the SW-C that is the request source of the API access request, when the security level guaranteed by the SW-C, i.e., the provision level, satisfies the security level requested by the API, i.e., the request level. That is, only the API access request from the SW-C that satisfies the API request level is passed to the API that is the access destination. Therefore, the API that provides safety-related functions can be freely used by the service system function modules that are not assigned a security level, thereby suppressing unexpected driving control. In addition, the functions provided by the API do not need to include processing for requests from SW-Cs that do not meet the request level, so the processing can be simplified.
[0143] (2) When implementing a service application that includes multiple microservices through multiple SW-Cs, focus on the provision level of the microservices and perform functional division so that microservices with the same provision level are included in the same SW-C (i.e., process). When performing such functional division, it is possible to achieve both a reduction in processing load and an improvement in development efficiency.
[0144] [8. Other embodiments]
[0145] As mentioned above, although embodiment of this disclosure was described, this disclosure is not limited to the said embodiment, It can implement with various deformation|transformation.
[0146] (a) In the present disclosure, access restrictions are imposed on the security system API. However, for an API that is determined by the SW-C that is the source of the API access request and other SW-Cs have no possibility of being the source of the request, even if it is a security system API, it can be excluded from the objects of access restrictions in the API gateway 30.
[0147] (b) In the present disclosure, the authorization policy is represented by a matrix showing all combinations of the offer level and the request level, but it can also be represented by Figure 6 As shown in the authorization policy image, it is expressed by a matrix indicating the combination of application ID and API. In this case, it is possible to more easily determine whether access is allowed based on the information indicated in the API access request.
[0148] (c) In the present disclosure, the ECU 2 includes both the real-time processing unit 10 and the application processing unit 20 , but may include either one of them.
[0149] (d) In the present disclosure, the ECU 2 includes the service system functional module group 23, the control system functional module group 25, and the data system functional module group 26, but other vehicle-mounted devices 3 to 5 may also include at least a part of the functional module groups 23 to 26. In addition, the functional module groups 23 to 26 may be centrally arranged in any one of the vehicle-mounted devices 2 to 5, or may be dispersedly arranged in a plurality of vehicle-mounted devices 2 to 5.
[0150] (e) The vehicle-mounted devices 2 to 5 and methods thereof described in the present disclosure may also be implemented by a dedicated computer, which is provided by a processor and a memory programmed to execute one or more functions embodied by a computer program. Alternatively, the vehicle-mounted devices 2 to 5 and methods thereof described in the present disclosure may also be implemented by a dedicated computer, which is provided by a processor composed of one or more dedicated hardware logic circuits. Alternatively, the ECU, etc. and methods thereof described in the present disclosure may also be implemented by one or more dedicated computers, which are 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.
[0151] (f) It is also possible to realize multiple functions of one component in the above-mentioned embodiment by multiple components, or to realize one function of one component by multiple components. In addition, it is also possible to realize multiple functions of multiple components by one component, or to realize one function realized by multiple components by one component. In addition, it is also possible to omit a part of the structure of the above-mentioned embodiment. In addition, it is also possible to add or replace at least a part of the structure of the above-mentioned embodiment with respect to the structure of other above-mentioned embodiments.
[0152] (g) In addition to the above-mentioned vehicle control system and access control device, the present disclosure may be implemented in various forms such as a program for causing a computer to function as the access control device, a non-migrating physical recording medium such as a semiconductor memory recording the program, and an access control method.
[0153] [10. Technical ideas disclosed in this specification]
[0154] [Project 1]
[0155] A vehicle control system, wherein:
[0156] A plurality of electronic control devices are provided, the plurality of electronic control devices are mounted on a vehicle and connected to an in-vehicle network,
[0157] The above-mentioned multiple electronic control devices include:
[0158] a plurality of functional modules, each configured to execute a determined process and configured to at least partially provide a function of controlling the movement of the vehicle; and
[0159] A collaboration control unit is configured to realize collaboration among the above-mentioned multiple functional modules.
[0160] At least a part of the plurality of functional modules has a functional interface, which is an interface configured to provide its own functions to other functional modules.
[0161] The above-mentioned cooperative control unit has:
[0162] a policy storage unit configured to store an authorization policy indicating a rule for authorizing access to an access request from any of the functional modules to any of the functional interfaces; and
[0163] The access control unit is configured to, if the access request is accepted from any one of the plurality of functional modules, determine whether to approve access from the request source module to the request destination interface based on the approval policy, and if the access is approved, pass the access request to the request destination interface, wherein the request source module is the functional module that is the request source of the access request, and the request destination interface is the functional interface that is the request destination of the access request.
[0164] The authorization policy is set using a provision level, which is a security level indicating the security of a function guaranteed by the request source module, and a request level, which is the security level requested by the request destination interface to the request source module.
[0165] [Project 2]
[0166] According to the vehicle control system described in item 1, wherein:
[0167] The authorization policy is set to authorize access when the provision level is higher than the request level, and to deny access when the provision level is lower than the request level.
[0168] [Item 3]
[0169] The vehicle control system according to item 1 or item 2, wherein:
[0170] The automobile safety level is used as the above safety level.
[0171] [Item 4]
[0172] A vehicle control system according to any one of items 1 to 3, wherein:
[0173] The above functional modules have more than one micro-functional module.
[0174] The provision level of the functional module is configured to achieve the highest level of the security levels requested of each of the micro-functional modules.
[0175] [Item 5]
[0176] A vehicle control system according to any one of items 1 to 4, wherein:
[0177] A correspondence table indicating the provision level of the request source module and the request level of the request destination interface is provided,
[0178] The access control unit is configured to extract the provision level of the request source module and the request destination interface based on the request source module and the request destination interface extracted from the access request and referring to the correspondence table, and determine whether to approve access from the request source module to the request destination interface based on the extracted provision level and request level using the approval policy.
[0179] [Item 6]
[0180] A vehicle control system according to any one of items 1 to 4, wherein:
[0181] A correspondence table is provided, the correspondence table indicating the provision level of the request source module and the request level of the request destination interface, and indicating whether access is permitted according to the authorization policy for all combination patterns of the request source module and the request destination interface,
[0182] The access control unit is configured to determine whether access from the request source module to the request destination interface is authorized by referring to the correspondence table based on the request source module and the request destination interface extracted from the access request.
[0183] [Item 7]
[0184] The vehicle control system according to item 5 or item 6, wherein:
[0185] The functional modules and the functional interfaces are identified by a process ID assigned by the operating system when the vehicle control system is started.
[0186] The correspondence table is configured to be generated by the operating system after the process ID is assigned, and to identify the request source module and the request destination interface by the process ID.
[0187] [Item 8]
[0188] An access control device, comprising:
[0189] A plurality of functional modules configured to execute the determined processing; and
[0190] A collaboration control unit is configured to realize collaboration among the above-mentioned multiple functional modules.
[0191] At least a part of the plurality of functional modules has a functional interface, which is an interface configured to provide its own functions to other functional modules.
[0192] The above-mentioned cooperative control unit has:
[0193] a policy storage unit configured to store an authorization policy indicating a rule for authorizing access to an access request from any of the functional modules to any of the functional interfaces; and
[0194] The access control unit is configured to, if the access request is received from any of the plurality of functional modules, determine, based on the approval policy, whether to approve access from the functional module that is the request source of the access request, i.e., the request source module, to the functional interface that is the request destination of the access request, i.e., the request destination interface, and, if the access is approved, pass the access request to the request destination interface.
[0195] The authorization policy is set using a provision level and a request level, wherein the provision level is a security level indicating the security of a function provided by the request source module, and the request level is the security level requested by the request destination interface to the request source module.
[0196] [Item 9]
[0197] An access control method, wherein:
[0198] For an access request to a functional interface from any one of a plurality of functional modules configured to respectively execute a determined process, it is determined whether to approve access from a request source module to a request destination interface based on an approval policy showing a rule for approving access, wherein the functional interface is provided by at least a part of the plurality of functional modules and is used to provide an interface of the functions possessed by the module to the other functional modules, the request source module being the functional module that is the request source of the access request, and the request destination interface being the functional interface that is the request destination of the access request,
[0199] If the access is approved, the access request is passed to the request destination interface.
[0200] The authorization policy is set using a provision level and a request level, wherein the provision level is a security level indicating the security of a function provided by the request source module, and the request level is the security level requested by the request destination interface to the request source module.
Claims
1. A vehicle control system, in, A plurality of electronic control devices (2 to 5) are provided, wherein the plurality of electronic control devices (2 to 5) are mounted on a vehicle and connected to an in-vehicle network. The plurality of electronic control devices include: a plurality of functional modules (23-26), each configured to execute a determined process and configured to at least partially provide a function of controlling the movement of the vehicle; and A collaboration control unit (30) configured to realize collaboration among the plurality of functional modules. At least a part of the plurality of functional modules has a functional interface configured to provide its own functions to other functional modules. The cooperation control unit comprises: a policy storage unit (31) configured to store an authorization policy indicating a rule for authorizing access to an access request from any of the functional modules to any of the functional interfaces; and The access control unit (32) is configured to, if the access request is received from any one of the plurality of functional modules, determine whether to approve access from the request source module to the request destination interface based on the approval policy, and if the access is approved, pass the access request to the request destination interface, wherein the request source module is the functional module that is the request source of the access request, and the request destination interface is the functional interface that is the request destination of the access request, The authorization policy is set using a provision level, which is a security level indicating the security of a function guaranteed by the request source module, and a request level, which is the security level requested by the request destination interface to the request source module.
2. The vehicle control system according to claim 1, in, The authorization policy is set to authorize access when the provision level is equal to or higher than the request level, and to deny access when the provision level is lower than the request level.
3. The vehicle control system according to claim 1 or 2, in, As the safety level, an automobile safety level is used.
4. The vehicle control system according to claim 1 or 2, in, The functional module has more than one micro-functional module. The provision level of the functional module is configured to achieve the highest level of the security levels requested of each of the micro-functional modules.
5. The vehicle control system according to claim 1, in, A correspondence table indicating the provision level of the request source module and the request level of the request destination interface is provided, The access control unit is configured to extract the provision level of the request source module and the request destination interface based on the request source module and the request destination interface extracted from the access request and referring to the correspondence table, and to determine whether to approve access from the request source module to the request destination interface based on the extracted provision level and request level using the approval policy.
6. The vehicle control system according to claim 1, in, A correspondence table is provided, the correspondence table indicating the provision level of the request source module and the request level of the request destination interface, and indicating access permission according to the authorization policy for all combination patterns of the request source module and the request destination interface, The access control unit is configured to determine whether access from the request source module to the request destination interface is authorized by referring to the correspondence table based on the request source module and the request destination interface extracted from the access request.
7. The vehicle control system according to claim 5 or 6, in, The functional module and the functional interface are identified by a process ID assigned by the operating system when the vehicle control system is started. The correspondence table is configured to be generated by the operating system after the process ID is assigned, and to identify the request source module and the request destination interface by the process ID.
8. An access control device, in, have: A plurality of functional modules (23 to 26) configured to execute the determined processing; and A collaboration control unit (30) configured to realize collaboration among the plurality of functional modules. At least a part of the plurality of functional modules has a functional interface configured to provide its own functions to other functional modules. The cooperation control unit comprises: a policy storage unit (31) configured to store an authorization policy indicating a rule for authorizing access to an access request from any of the functional modules to any of the functional interfaces; and The access control unit (32) is configured to, if the access request is received from any one of the plurality of functional modules, determine whether to approve access from the request source module to the request destination interface based on the approval policy, and if the access is approved, pass the access request to the request destination interface, so that the request source module becomes the functional module of the request source of the access request, and the request destination interface becomes the functional interface of the request destination of the access request, The authorization policy is set using a provided level, which is a security level indicating the security of a function provided by the request source module, and a requested level, which is the security level requested by the request destination interface to the request source module.
9. An access control method, in, In response to an access request to a functional interface from any one of a plurality of functional modules configured to respectively execute a determined process, it is determined whether access to a request destination interface from a request source module is approved based on an approval policy showing a rule for approving access, wherein the functional interface is provided by at least a part of the plurality of functional modules and is used to provide the interface of the function possessed by the other functional modules, the request source module is the functional module that is the request source of the access request, and the request destination interface is the functional interface that is the request destination of the access request, If the access is approved, the access request is passed to the request destination interface. The authorization policy is set using a provided level, which is a security level indicating the security of a function provided by the request source module, and a requested level, which is the security level requested by the request destination interface to the request source module.
