Mobility service providing system, in-vehicle system, management server, access control method, and program

By using multiple strategies distinguished by viewpoints in the on-board system to generate static viewpoint policies, the problem of access control complexity in the on-board system is solved, simplified access authority determination and flexible access restrictions are achieved, and the efficiency and security of the system are improved. sex.

CN119096243APending Publication Date: 2024-12-06DENSO CORP
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202380036227.9
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2022-04-28
Filing Date
2023-04-06
Publication Date
2024-12-06

AI Technical Summary

Technical Problem

In the on-board system, with the increase in the number of service applications, access control becomes complicated, making it difficult to effectively utilize limited resources and ensure real-time. At the same time, it is necessary to restrict access to vehicle functions and information by third-party service applications.

Method used

Use multiple strategies distinguished by viewpoint to generate static viewpoint policies, and provide them to the on-board system by integrating multiple policies as authorization policies, which are used to determine access rights between functional blocks, reduce the load on access rights determination, and through the collaboration control department and policy The storage unit realizes collaboration and access control between functional blocks.

Benefits of technology

It simplifies the use of access authorization policies, improves the efficiency of access authority determination, reduces the load on the on-board system, and flexibly responds to access restrictions needs from different viewpoints, such as security, property and privacy-related access controls.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119096243A_ABST
    Figure CN119096243A_ABST
Patent Text Reader

Abstract

The invention provides a mobility service providing system, an in-vehicle system, a management server, an access control method, and a program. An authorization policy provision unit provides, as an authorization policy, a static viewpoint policy generated by integrating a plurality of viewpoint-specific policies to an in-vehicle system. If the access request is accepted, the access control unit determines whether or not the use source block has access to the use destination block by using the authorization policy provided from the authorization policy providing unit and stored in the policy storage unit. When it is determined that the access right is present, the access control unit transmits the access request to the use destination plot.
Need to check novelty before this filing date? Find Prior Art

Description

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This international application claims the benefit of priority based on Japanese Patent Application No. 2022-074970 filed with the Japan Patent Office on April 28, 2022, the entire contents of which are incorporated herein by reference. Technical Field

[0003] The present disclosure relates to techniques for controlling access. Background Art

[0004] Patent Document 1 below describes a technology for limiting access using access authorization policies when detecting access to resources or information in a system via a service application in an open platform for mobile terminals. The access authorization policy specifies who is allowed or prohibited to do what.

[0005] Patent Document 1: Japanese Patent No. 6124627

[0006] In the future, it is assumed that a plurality of non-specific third-party service applications are installed in the electronic control system (hereinafter referred to as the vehicle-mounted system) installed in the vehicle. The third-party service applications are required to restrict access as needed when accessing the functions and information possessed by the vehicle. In addition, as the vehicle-mounted system is equipped with various service applications due to its high functionality, access control is also complicated. It is necessary to perform access control in a real-time state while effectively utilizing the limited resources of the vehicle-mounted system. Summary of the invention

[0007] One aspect of the present disclosure provides a technique for simplifying access control using access authorization policies.

[0008] A mobility service providing system according to one aspect of the present disclosure includes an in-vehicle system and an authorization policy providing unit. The in-vehicle system is mounted on a vehicle and includes a plurality of electronic control devices connected to an in-vehicle network. The authorization policy providing unit is provided outside the vehicle.

[0009] The vehicle-mounted system includes a plurality of functional blocks and a cooperation control unit. The plurality of functional blocks are respectively mounted on any one of a plurality of electronic control devices and are configured to respectively execute a determined process. The cooperation control unit is configured to realize cooperation between the plurality of functional blocks.

[0010] The collaboration control unit includes a policy storage unit and an access control unit. The policy storage unit is configured to obtain and store the authorization policy that specifies the access rights between the functional blocks from the authorization policy providing unit. The access control unit receives an access request to the destination block from the source block, wherein the source block is one of the multiple functional blocks and the destination block is another of the multiple functional blocks. If the access control unit receives the access request, it uses the authorization policy stored in the policy storage unit to determine whether the source block has access rights to the destination block. The access control unit is configured to pass the access request to the destination block if it is determined that the source block has access rights.

[0011] The authorization policy providing unit is configured to provide the in-vehicle system with a static viewpoint policy generated by integrating a plurality of viewpoint policies as the authorization policy. The plurality of viewpoint policies define access rights for each of a plurality of viewpoints focusing on static attributes of a functional block.

[0012] According to such a structure, the vehicle-mounted system uses an authorization policy including a static viewpoint policy that integrates a plurality of viewpoint-based policies to determine whether there is access permission from the source block to the destination block. Therefore, in the vehicle-mounted system, it is possible to simply determine whether there is access permission all at once, rather than independently determining whether there is access permission according to each of the plurality of viewpoint-based policies. In addition, the authorization policy is obtained from outside the vehicle. As a result, in the vehicle-mounted system, the load required for determining access permission can be reduced.

[0013] The in-vehicle system of one aspect of the present disclosure includes a plurality of functional blocks and a cooperation control unit. The plurality of functional blocks are respectively mounted on any one of a plurality of electronic control devices connected to an in-vehicle network and are configured to respectively execute a determined process. The cooperation control unit is configured to realize cooperation between the plurality of functional blocks.

[0014] The collaboration control unit includes a policy storage unit and an access control unit. The policy storage unit is configured to store an authorization policy, and the authorization policy specifies access rights between functional blocks. The access control unit receives an access request to a destination block from a source block, wherein the source block is one of a plurality of functional blocks, and the destination block is another of the plurality of functional blocks. If the access control unit receives the access request, it uses the authorization policy stored in the policy storage unit to determine whether the source block has access rights to the destination block. The access control unit is configured to pass the access request to the destination block if it is determined that the source block has access rights.

[0015] The authorization policy is configured to include a static viewpoint policy generated by integrating a plurality of viewpoint policies that define access rights for each of a plurality of viewpoints focusing on static attributes of a function block.

[0016] A management server in one aspect of the present disclosure is communicatively connected to a vehicle, wherein the vehicle includes an in-vehicle system having a plurality of electronic control devices connected to an in-vehicle network. The management server includes an authorization policy storage unit, an authorization policy generation unit, and an authorization policy providing unit.

[0017] The authorization policy storage unit is mounted on any one of the plurality of electronic control devices and is configured to store an authorization policy referred to in order to control access rights from a utilization source block to a utilization destination block. The utilization source block is one of the plurality of functional blocks configured to respectively execute a determined process. The utilization destination block is another functional block of the plurality of functional blocks.

[0018] The authorization policy generation unit is configured to generate a static viewpoint policy by integrating a plurality of static viewpoint-differentiated policies based on a plurality of static viewpoint-differentiated policies that define access rights for each of a plurality of viewpoints focusing on static attributes of a functional block. In addition, the authorization policy generation unit is configured to store the generated static viewpoint policy as an authorization policy in an authorization policy storage unit.

[0019] The authorization policy providing unit is configured to provide the authorization policy stored in the authorization policy storage unit to the vehicle.

[0020] In one aspect of the present disclosure, an access control method is provided in which at least one of a plurality of electronic control devices connected to a vehicle network uses an authorization policy that specifies access rights between the functional blocks to control access between the functional blocks. The plurality of functional blocks are respectively mounted on any one of the plurality of electronic control devices and are configured to respectively execute a determined process.

[0021] In the access control method, a static viewpoint policy is used as an authorization policy, and the static viewpoint policy is generated by integrating a plurality of viewpoint-specific policies that define access rights for each of a plurality of viewpoints focusing on static attributes of a functional block. Furthermore, if an access request to a utilization destination block is received from a utilization source block, it is determined based on the authorization policy whether the utilization source block has access rights to the utilization destination block, and if it is determined that the utilization source block has access rights, the access request is transmitted to the utilization destination block, wherein the utilization source block is one of the plurality of functional blocks, and the utilization destination block is another of the plurality of functional blocks.

[0022] A program implementation of one aspect of the present disclosure uses an authorization policy that specifies access rights between functional blocks to control access between multiple functional blocks, wherein the multiple functional blocks are respectively installed in any one of multiple electronic control devices connected to a vehicle network and are configured to respectively execute determined processing.

[0023] In the program, a static viewpoint policy is used as an authorization policy, and the static viewpoint policy is generated by integrating a plurality of viewpoint-specific policies that define the access rights for each of a plurality of viewpoints focusing on static attributes of a functional block. In addition, the program causes a computer to realize: if an access request to a utilization destination block is received from a utilization source block, it is determined based on the authorization policy whether the utilization source block has access rights to the utilization destination block, and if it is determined that the access rights are available, the access request is transmitted to the utilization destination block, wherein the utilization source block is one of the plurality of functional blocks, and the utilization destination block is another of the plurality of functional blocks. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] Figure 1 This is a block diagram showing the structure of a mobility service providing system.

[0025] Figure 2 It is a block diagram showing the structure of the ECU.

[0026] Figure 3 is a block diagram showing the structure of an API gateway.

[0027] Figure 4 This is an explanatory diagram showing the contents of user information.

[0028] Figure 5 This is an explanatory diagram showing an overview of the authorization policy.

[0029] Figure 6 This diagram explains API access rights and security levels.

[0030] Figure 7 This is an explanatory diagram illustrating the policies classified from a static viewpoint based on security.

[0031] Figure 8 This is an explanatory diagram illustrating strategies classified from a static viewpoint with corporate assets as the viewpoint.

[0032] Fig. 9 This is an explanatory diagram illustrating a policy based on dynamic viewpoints based on personal property, a dynamic viewpoint policy based on privacy, and a dynamic policy that integrates the policies based on dynamic viewpoints.

[0033] Fig.10This is an explanatory diagram illustrating a static policy that integrates policies classified according to static viewpoints.

[0034] Fig.11 This is a flowchart of the access restriction process executed by the access control unit.

[0035] Fig.12 It is a block diagram showing the structure of a cloud server.

[0036] Fig.13 is a flow chart of a policy generation provisioning process performed by a cloud server. DETAILED DESCRIPTION

[0037] Below, while referring to the attached Figure 1 Embodiments of the present disclosure will be described.

[0038] [1.Structure]

[0039] The mobility service providing system 1 of this embodiment includes an in-vehicle system 100 and a cloud server 200 mounted on a vehicle. The vehicle may have an automatic driving function in addition to a manual driving function. The vehicle may also be a hybrid vehicle having an engine and an electric motor as a driving source. 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 in-vehicle system 100 is simply referred to as a vehicle.

[0040] like Figure 1 As shown, the vehicle-mounted system 100 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.

[0041] The ECU 2 realizes coordinated control of the entire vehicle by taking charge of the plurality of ECUs 3 .

[0042] ECU3 is set up in each domain divided according to the functions 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 independently set up. CAN is the abbreviation of Controller Area Network, which is a registered trademark. ECU3 has the function of centrally managing the access rights to the subordinate ECU4 and authenticating the user. Domains are, for example, powertrain, body, chassis, and cockpit.

[0043] The ECU 4 connected to the ECU 3 belonging to the powertrain domain 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.

[0044] The ECU 4 connected to the ECU 3 belonging to the vehicle body domain includes, for example, an ECU 4 for controlling an air conditioner and an ECU 4 for controlling vehicle doors.

[0045] The ECU 4 connected to the ECU 3 belonging to the chassis domain includes, for example, an ECU for controlling brakes and an ECU for controlling a steering wheel.

[0046] The ECU 4 connected to the ECU 3 belonging to the cockpit domain includes, for example, an ECU 4 for controlling a display of an instrument or navigation, an ECU 4 for controlling an input device operated by a vehicle occupant, and the like.

[0047] The vehicle external communication device 5 performs data communication with the vehicle external device such as the cloud server 200 via the wide area wireless communication network.

[0048] 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 independently. Figure 2 As shown, the ECU 2 includes an Ethernet switch 7 for switching the Ethernet to be used.

[0049] ECU2 is an electronic control device centered on a microcomputer having CPU2a, ROM2b, RAM2c, etc. Various functions of the microcomputer are realized by CPU2a executing a program stored in a non-transitional physical recording medium. In this example, ROM2b is equivalent to a non-transitional physical recording medium storing a 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, etc. In addition, the number of microcomputers constituting ECU2 may be one or more.

[0050] ECU3, ECU4 and the vehicle external communication device 5 are all electronic control devices, similar to ECU2, mainly composed of a microcomputer including a CPU, ROM, RAM, etc. The number of microcomputers constituting ECU3, ECU4 and the vehicle external communication device 5 may be one or more.

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

[0052] 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 processing executed by the same CPU or by processing executed by different CPUs.

[0053] The real-time processing unit 10 cooperates with the vehicle-mounted devices 3 to 5 connected via CAN FD to execute vehicle control requiring real-time performance, etc. The application processing unit 20 cooperates with the vehicle-mounted devices 3 to 5 connected via Ethernet to execute various application programs (e.g., entertainment applications, etc.) that require high processing capabilities.

[0054] The application processing unit 20 has a function of transmitting instructions for processing based on various application programs to the real-time processing unit 10. The real-time processing unit 10 has a function of transmitting information collected from the vehicle-mounted devices 3 to 5 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.

[0055] like Fig.12 As shown, the cloud server 200 includes a control unit 201 , a storage unit 202 , and a communication unit 203 .

[0056] The control unit 201 is an electronic control device composed of a microcomputer including a CPU 201a, a ROM 201b, and a RAM 201c. The various functions of the microcomputer are realized by executing a program stored in a non-transitional physical recording medium by the CPU 201a. In this example, the ROM 201b is equivalent to a non-transitional physical recording medium storing the program. In addition, by executing the program, a method corresponding to the program is executed. The control unit 201 at least performs a policy generation and providing process.

[0057] The storage unit 202 stores a plurality of authorization policies. The authorization policies stored in the storage unit 202 include static viewpoint policies and dynamic viewpoint policies generated by the policy generation and provision processing executed by the control unit 201. In addition, the authorization policies may also include a plurality of policies for each viewpoint used when generating the static viewpoint policy and the dynamic viewpoint policy.

[0058] The communication unit 203 performs data communication with the vehicle-mounted system 100 mounted in each of a plurality of vehicles via the wide area wireless communication network.

[0059] [2. Functional structure]

[0060] The software installed in the vehicle-mounted devices 2 to 5 belonging to the vehicle-mounted system 100 is constructed 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 referred to as SW-C) installed to implement various applications, but also provides functions related to connection with the cloud and security. SW-C is componentized software to achieve a certain function. An application contains one or more SW-C. In addition, the software of the mobility service providing system 1 does not necessarily need to be built along AUTSAR.

[0061] The in-vehicle devices 2 to 5 are each provided with a platform. The platform provides an environment for executing SW-Cs described in a format that does not depend on hardware.

[0062] The platform has an operating environment (hereinafter referred to as RTE) and basic software (hereinafter referred to as 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 and 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.

[0063] Hereinafter, the platform included in the real-time processing unit 10 is referred to as a first platform (hereinafter referred to as a first PF) 11 , and the platform included in the application processing unit 20 is referred to as a second platform (hereinafter referred to as a second PF) 21 .

[0064] like Figure 2 As shown, the real-time processing unit 10 includes a control system functional block group 12 as a collection of service applications (hereinafter referred to as service applications) running on the first PF 11. A service application is an application that receives requests from a client, processes them, and returns results. Each service application is composed of one or more SW-Cs.

[0065] The control system functional block group 12 has an API for receiving commands related to vehicle motion and is an application for integrating commands received by the API and implementing matching vehicle control. The control system functional block group 12 outputs various commands to the vehicle-mounted devices 3 to 5 where entities that execute control based on the commands are located via CANFD.

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

[0067] The application processing unit 20 includes a hypervisor 22 and executes software on a plurality of virtual machines. The hypervisor 22 may be omitted.

[0068] The application processing unit 20 includes service system function block groups 23 and 24 as a collection of service applications that operate on the second PF 21 .

[0069] The service system functional block group 23 is a collection of service applications (hereinafter referred to as OEM applications) provided by the OEM. Each OEM application has one or more SW-Cs. OEM is a vehicle manufacturer that manufactures vehicles. OEM is the abbreviation of Original Equipment Manufacturer. In addition, the OEM application may also include applications developed by the OEM itself and applications developed by other suppliers.

[0070] The service system functional block group 24 is a collection of service applications (hereinafter referred to as 3rd applications) provided by a third party. Each 3rd application has one or more SW-Cs. The third party is a third party other than the vehicle owner and the OEM. As a third party, for example, a data user who provides services by collecting data from the vehicle can be cited.

[0071] The second PF 21 includes a control system function block group 25 , a data system function block group 26 , and an API gateway 30 .

[0072] The control system function block group 25 is a collection of service applications having an API for receiving requests related to vehicle control from the service system function block groups 23 and 24. The control system function block group 25 converts the API access request from the service system function block groups 23 and 24, 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 block 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 received by the motion system API is forwarded to the control system function block group 12, and is forwarded from the control system function block group 12 to the vehicle-mounted devices 3 to 5, etc., which execute control based on the request, via the in-vehicle communication network 6 such as CAN FD. The API access request received by the non-motion system API is forwarded to the vehicle-mounted devices 3 to 5, etc., which execute control based on the request, via the in-vehicle communication network 6 such as CAN FD.

[0073] The data system functional block group 26 is a collection of service applications having an API for processing vehicle data acquired and accumulated via the real-time processing unit 10. The data system functional block group 26 has a function of abstracting the vehicle data presented in a vehicle-dependent form supplied from the real-time processing unit 10 into a vehicle-independent form and accumulating the data. The data system functional block group 26 may also have an API that provides a function of sending designated vehicle data to an onboard device or the like via an in-vehicle communication network 6 such as Ethernet. In particular, when the destination is an external vehicle communication device 5, the external vehicle communication device 5 may also upload the sent vehicle data to the cloud. In addition, the data system functional block group 26 may also have an API that provides a function of acquiring data from the cloud server 200.

[0074] In addition, the communication with other onboard devices 3 to 5 via the control system functional block group 25 is not limited to CAN FD, and Ethernet or other communication methods may be used. In addition, the communication with other onboard devices 3 to 5 via the data system functional block group 26 is not limited to Ethernet, and CAN FD or other communication methods may be used.

[0075] Hereinafter, the API provided by the service applications belonging to the control system function block group 25 and the data system function block group 26 will be referred to as a vehicle API.

[0076] The API gateway 30 is constructed using the functions of the virtual function bus (hereinafter referred to as VBF). VBF 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 to APIs provided by SW-Cs to other SW-Cs between service applications belonging to the service system function block groups 23 and 24. Communication between SW-Cs and BSWs refers to access to vehicle APIs from SW-Cs between service applications belonging to the service system function block groups 23 and 24 and service applications belonging to the control system function block group 25 and the data system function block group 26. The following description will be given as a one-to-one correspondence between SW-Cs and service applications.

[0077] When the service application utilizes the functions provided by the control system functional block group 25 and the data system functional block group 26, the service application sends an API access request, which is an access request to the vehicle API. The API access request includes at least the process ID of the service application that is the utilization source (hereinafter referred to as the utilization source application) and the information that uniquely identifies the vehicle API that is the utilization destination (hereinafter referred to as the utilization destination API), that is, the API-ID.

[0078] [3. Access restriction mechanism]

[0079] The access restriction mechanism for restricting the access from the service application to the vehicle API of the API gateway 30 is described. The access restriction mechanism is set from the perspective of the attribute defined as the security protection asset, namely SFOP. S is the abbreviation of Safety, which refers to the access restriction on the API access that affects safety. F is the abbreviation of Financial, which refers to the access restriction on the API access that affects the property of a company or an individual. O is the abbreviation of Operational, which refers to the access restriction on the API access that affects the operational performance of the vehicle. P is the abbreviation of Privacy, which refers to the access restriction on the API access that affects privacy information.

[0080] The API gateway 30 does not include only the second PF 21 operating on the application processing unit 20. The API gateway 30 includes a platform for all vehicle-mounted devices 2 to 5 that may be equipped with any of the service system function block groups 23 and 24, the control system function block group 25, and the data system function block group 26.

[0081] like Figure 3 As shown, the API gateway 30 includes an information storage unit 31 , an access control unit 32 , and a status monitoring unit 33 .

[0082] The information storage unit 31 stores an API authorization policy 311, a correspondence table 312, and user information 313. The correspondence table 312 is stored in the RAM 2c, and the API authorization policy 311 and user information 313 are stored in the ROM 2b. However, the API authorization policy 311 and user information 313 may also be stored in the nonvolatile RAM 2c.

[0083] The API authorization policy 311 is a set of information for determining whether a service application has access rights to the vehicle API. The API authorization policy 311 is downloaded from the cloud server 200 using a function of a service application belonging to the data system functional block group 26 and stored in the information storage unit 31 .

[0084] The correspondence table 312 includes information for establishing a correspondence between a process ID and a unique application ID, wherein the process ID is an ID dynamically assigned to a process, which is an execution unit of a program in an operating system (hereinafter referred to as an OS), and the unique application ID is an ID of a service application executed in the process. In addition, the correspondence table 312 includes information for establishing a correspondence between a unique API-ID of each vehicle API and a process ID of a process of a service application, which is an entity that executes the API function. The correspondence table 312 is generated by the OS when the process of each service application is generated at system startup.

[0085] The user information 313 is information that is referenced when determining whether or not there is access permission using the API authorization policy 311, and is information that is arbitrarily set by the vehicle user. Figure 4 As shown, the user information 313 has the content of setting whether to allow the access request from the service application to the private information identified by the private information ID for each vehicle user identified by the user ID. The user information 313 may also include the contact information for the vehicle user.

[0086] When the access control unit 32 receives the API access request, it uses the corresponding table 312 to determine the application ID of the source application based on the process ID indicated in the API access request. The access control unit 32 performs access restriction processing to determine whether there is access authority based on the determined application ID and the API-ID of the destination API indicated in the API access request according to the API authorization policy 311. The details of the access restriction processing will be described later.

[0087] The status monitoring unit 33 monitors the access status of each service application to each vehicle API and generates status information indicating the access status. For example, the status information is generated by summarizing the number of accesses to each vehicle API and the amount of data being processed for each utilization source application.

[0088] [4.API authorization strategy]

[0089] A method for generating the API authorization policy 311 distributed by the cloud server 200 is described.

[0090] like Figure 5 As shown, in the cloud server 200, a plurality of viewpoint-differentiated policies generated from different viewpoints are prepared according to the attributes of each SFOP. The viewpoint-differentiated policies may be generated by the cloud server 200, or the viewpoint-differentiated policies generated outside the cloud server 200 may be collected. It is not necessary to prepare viewpoint-differentiated policies for all attributes of the SFOP. In addition, a plurality of viewpoint-differentiated policies may be prepared for one attribute.

[0091] Among the policies differentiated by viewpoint, there are policies differentiated by static viewpoint generated from the viewpoint of focusing on the static attributes of the service application and policies differentiated by dynamic viewpoint generated from the viewpoint of focusing on the dynamic attributes of the service application. The so-called static attributes of the service application refer to information related to features that do not change depending on the use environment, use status, etc. of the service application, such as information indicating the security of the processing performed by the service application, information indicating the source of the service application, etc. The so-called dynamic attributes of the service application refer to information related to features that change depending on the use environment, use status, etc. of the service application, such as restrictions based on the charging contract of the provider of the service application and information arbitrarily set by the vehicle user, etc.

[0092] [4-1. Authorization policies related to security]

[0093] The “security-related authorization policy” is described as an example of a static viewpoint-based policy classified as an S attribute.

[0094] As a premise, a security level (hereinafter referred to as a guarantee level) indicating the reliability of the security of the processing executed by the safety system application is assigned to a service application (hereinafter referred to as a safety system application) that performs processing related to the safety of the vehicle. In addition, an API (hereinafter referred to as a safety system API) possessed by the safety system application is assigned a security level (hereinafter referred to as a request level) required by the service application that is the source of the utilization requesting access to the safety system API.

[0095] Safety levels use, for example, the Automotive Safety Level (hereinafter referred to as ASIL). ASIL is a risk classification system defined in accordance with the ISO26262 standard regarding the functional safety of vehicles traveling on the road. ASIL is determined based on three parameters: probability of exposure, controllability, and severity, and is represented by four stages from A to D. A is the lowest level, and D corresponds to the highest level. No requirement level is assigned to non-safety system APIs, and QM is used to indicate that no requirement level is assigned. 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 have 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 four stages from A to D, and can also be less than three stages, or more than five stages.

[0096] A matrix showing all combinations of the service application guarantee level and the API requirement level is used to display a list of whether or not the service application has access to the API. Figure 6The ○ mark in the table indicates that the user has access rights, and the × mark indicates that the user does not have access rights. Here, if the security level is higher than the required level, the user has access rights, and if the security level is lower than the required level, the user does not have access rights. Figure 6 As shown in the left figure in , for example, a service application with a guarantee level of A has access rights to APIs with a requirement level of A, but does not have access rights to APIs with a requirement level of D. A service application with a guarantee level of D has access rights to all APIs including those with a requirement level of D.

[0097] like Figure 7 As shown, by combining application information, API information and Figure 6 Create a "security-related authorization policy" based on the list of access rights shown.

[0098] The application information is information that associates an application ID with a guarantee level assigned to a service application identified by the application ID. The API information is information that associates an API ID with a requirement level assigned to a vehicle API identified by the API ID.

[0099] The content of the "security-related authorization policy" is expressed by a list defining whether or not the source application identified by the application ID has access to the destination API identified by the API ID.

[0100] [4-2. Authorization strategy related to corporate assets]

[0101] An “authorization policy related to corporate assets” is described as an example of a policy classified from a static viewpoint and categorized as an F attribute.

[0102] As a premise, the service application is given a group attribute corresponding to the provider. The group attribute is GA for OEM applications developed by the company, GB for OEM applications developed by other suppliers, and GC for 3rd party applications developed by a third party.

[0103] like Figure 8 As shown, an "authorization policy related to corporate assets" is generated by combining access right information differentiated by group attributes with application information.

[0104] The application information is information that establishes a correspondence between an application ID of a service application and a group attribute assigned to the service application identified by the application ID.

[0105] The access right information differentiated by group attributes is information indicating whether a service application with a certain group attribute has access rights to a vehicle API identified by the API ID, by means of a matrix representing all combinations of the vehicle API's API-ID and the group attribute. The reliability of the service application from the group attribute is, for example, GA>GB>GC, and the access rights to each vehicle API are also set based on this reliability.

[0106] The content of "Authorization policy related to corporate assets" is the same as that of "Authorization policy related to security", and is expressed as a list defining whether or not the source application identified by the application ID has access to the destination API identified by the API-ID.

[0107] [4-3. Authorization strategy related to personal property]

[0108] An “authorization policy related to personal property” is described as an example of a policy classified by dynamic viewpoint and categorized as the F attribute.

[0109] In order to determine whether or not access rights exist based on the access status to each vehicle API in accordance with the API fee contract of the service application provider, the "authorization policy related to personal property" is used.

[0110] like Fig. 9 As shown in the upper left section, "Authorization policy related to personal property" is information that establishes a correspondence between the API-ID, the confirmation information set for the vehicle API determined by the API-ID, the permission type information, and the charging contract content information.

[0111] The confirmation information is information indicating whether it is necessary to confirm the dynamic authority related to personal property when determining the access right to the vehicle API. Here, in the case where there is a fee contract related to the access to the vehicle API, it is set to be necessary to confirm the dynamic authority.

[0112] The authority type information is information indicating which attribute of the SFOP the information complies with, and is set to F (ie, Financial) in the "Authorization policy related to personal property."

[0113] The billing contract content information is information indicating the content of the billing contract for the vehicle API, and for example, indicates the upper limit of the number of times the vehicle API is used, restrictions in the volume-based billing, and the like.

[0114] [4-4. Authorization policies related to privacy]

[0115] The following describes an "authorization policy related to privacy" as an example of a policy classified by dynamic viewpoints as attribute P. The privacy information is information related to the privacy of the vehicle user and stored in the vehicle.

[0116] Whether to allow the service application to access the private information of the vehicle user and to what extent the access is allowed depends on the vehicle user's intention. Therefore, the access to the private information requires the consent of the vehicle user according to the content of each private information. The consent content related to the private information of each vehicle user is shown in Figure 4 User information 313 is shown.

[0117] like Fig. 9 As shown in the lower left section of , “Privacy-related authorization policy” is information that establishes a correspondence between the API-ID and the confirmation requirement information, permission type information, and privacy information ID set for the vehicle API determined by the API-ID.

[0118] Whether confirmation information is required is information indicating whether dynamic permissions related to privacy need to be confirmed when determining access rights to the vehicle API. Here, when the function provided by the vehicle API includes access to private information, confirmation of dynamic permissions is required.

[0119] The permission type information is information indicating which attribute of the SFOP the information complies with, and is set to P (ie, Privacy) in the "authorization policy related to privacy".

[0120] The private information ID may be an ID assigned to private information that is to be accessed by the function of the vehicle API.

[0121] [4-5. Generation of API authorization policy]

[0122] like Figure 5 As shown, the API authorization policy 311 includes a static policy and a dynamic policy.

[0123] A static policy is generated by integrating multiple policies distinguished by static viewpoints into one. Figure 7 , 8 As shown in FIG, the policies distinguished by static viewpoints are expressed in a matrix form whether the service application determined by the application ID has access to the vehicle API determined by the API-ID. Fig.10 As shown, each block of the matrix representing the static policy is set to have access permission when all of the plurality of policies classified by viewpoints to be integrated have permission, and is set to have no access permission even if any one of them does not have permission.

[0124] A dynamic strategy is generated by integrating multiple strategies differentiated by dynamic viewpoints into one. Fig. 9 As shown on the left, the policy differentiated by dynamic viewpoint establishes a corresponding relationship between information and each API-ID. Fig. 9 As shown on the right, the dynamic policy sets confirmation necessity information, permission type information, and confirmation information for each API-ID based on a plurality of policies classified by dynamic viewpoints to be integrated.

[0125] The confirmation necessity information is set to be necessary if any one of the confirmation necessity information of the plurality of viewpoint-based policies to be integrated is necessary.

[0126] The rights type information is set as is with respect to the rights type information of the plurality of viewpoint policies to be integrated.

[0127] The confirmation information is set to the content corresponding to the setting of the authority type information. That is, the confirmation information sets the fee contract content when the authority type information is set to Financial, and sets the privacy information ID when the authority type information is set to Privacy.

[0128] Return to Figure 5 The cloud server 200 distributes the API authorization policy generated by integrating a plurality of policies differentiated by viewpoints in this way in response to a request from the in-vehicle system 100. The API authorization policy may also be distributed in response to a request from the cloud server 200.

[0129] In the in-vehicle system 100 , the API authorization policy acquired from the cloud server 200 is stored in the information storage unit 31 of the API gateway 30 , and is used for access restriction processing.

[0130] [5. Processing]

[0131] [5-1. Access restriction processing]

[0132] use Fig.11 The flowchart of FIG. 1 illustrates the access control process executed by the access control unit 32.

[0133] In S110 , the access control unit 32 determines whether an API access request is received from the service application. If an API access request is received, the process proceeds to S120 . If no API access request is received, the process waits by repeating this step.

[0134] In S120, the access control unit 32 uses the static policy in the API authorization policy to determine whether the request source of the API access request, that is, the request source application, has access rights based on the information shown in the API access request. Specifically, the access control unit 32 first uses the corresponding table 312 to determine the application ID based on the process ID shown in the API access request. Next, the access control unit 32 refers to the static policy based on the determined application ID and the API-ID shown in the API access request to determine whether the source application determined by the application ID has access rights to the destination API determined by the AP-ID.

[0135] In the next S130 , if it is determined that the source application has access rights to the destination API, the access control unit 32 moves the process to S140 , and if it is determined that the source application does not have access rights, the access control unit 32 moves the process to S220 .

[0136] In S140, the access control unit 32 determines whether it is necessary to confirm the dynamic permission in accessing the destination API by referring to the confirmation information indicated by the dynamic policy. If it is determined that the dynamic permission needs to be confirmed, the access control unit 32 moves the process to S150. If it is determined that the dynamic permission does not need to be confirmed, the access control unit 32 moves the process to S220.

[0137] In S150 , the access control unit 32 refers to the permission confirmation type indicated by the dynamic policy, and moves the process to S160 if the indicated confirmation type is Financial, and moves the process to S180 if the indicated confirmation type is Privacy.

[0138] In S160 , the access control unit 32 refers to the billing contract content indicated by the confirmation information of the dynamic policy, and acquires the status information indicating the access status related to the billing contract content from the status monitoring unit 33 .

[0139] In the next S170, the access control unit 32 determines whether the value indicated by the access status information is within the range of the billing contract content, and moves the process to S210 if it is within the range of the billing contract content, and moves the process to S220 if it is not.

[0140] In S180, the access control unit 32 determines whether the access source application has access to the private information specified by the private information ID. This determination is performed by using the private information ID indicated by the confirmation information of the dynamic policy and the user ID of the vehicle user specified by the access source application and referring to the user information 313. If the access control unit 32 determines that there is access to the private information, the process moves to S190, and if it determines that there is no access to the private information, the process moves to S220.

[0141] In S190, the access control unit 32 inquires the vehicle user identified by the user ID whether or not the user agrees to access the private information. The inquiry is made to the contact information registered in association with the user ID via email or voice call.

[0142] In the next S200 , the access control unit 32 determines whether the vehicle user has given consent as a result of the inquiry in S190 , and if so, the process proceeds to S210 , and if not, the process proceeds to S220 .

[0143] In S210 , the access control section 32 permits access from the utilization source application to the utilization destination API, that is, passes the API access request to the utilization destination API and ends the processing.

[0144] In S220 , the access control unit 32 denies access from the utilization source application to the utilization destination API, that is, abandons the API access request, and ends the process.

[0145] [5-2. Policy generation and provision processing]

[0146] use Fig.13 The flowchart of FIG. 1 illustrates the policy generation and provision processing executed by the control unit 201 of the cloud server 200 .

[0147] In S310, the control unit 201 acquires the viewpoint-specific policies generated independently for each viewpoint. The viewpoint-specific policies may be stored in the storage unit 202 or may be input from a terminal device or the like connected to the cloud server 200 via a wide area network or the like.

[0148] In the next step S320, the control unit 201 generates an API authorization policy 311 by integrating the multiple policies differentiated by viewpoints acquired in S310. Fig.10 As shown, the static policy in the API authorization policy 311 is generated by integrating multiple policies differentiated by static viewpoints, such as Fig. 9 As shown, a dynamic policy is generated by integrating multiple dynamic viewpoint policies.

[0149] In the next S330 , the control unit 201 stores the API authorization policy 311 generated in S320 in the storage unit 202 .

[0150] In the next step S340, the control unit 201 sends the API authorization policy 311 stored in the storage unit 202 to the vehicle-mounted system 100 to be provided, and ends the process if the predetermined provision conditions are met. The provision conditions may include the existence of a request from the vehicle-mounted system 100 and the storage unit 202 storing a new policy for each viewpoint.

[0151] [6. Effect]

[0152] According to the embodiments described in detail above, the following effects are achieved.

[0153] (1) An API authorization policy 311 generated by the cloud server 200 (i.e., Out-Car) and integrating multiple policies differentiated by viewpoint is distributed to the vehicle-mounted system 100 (i.e., In-Car). In the vehicle-mounted system 100, by using the distributed API authorization policy 311, it is possible to simply determine whether there is access permission from the source application to the destination application API, rather than making independent determinations based on each policy differentiated by viewpoint. As a result, the load on the vehicle-mounted system 100 required for the determination can be reduced.

[0154] (2) The API authorization policy 311 includes a dynamic policy for determining whether access rights are granted based on information that changes dynamically according to the current situation and the user's intention. Therefore, for example, it is possible to flexibly respond to access restrictions that change according to the content of the billing contract, the user's opinion on privacy information, etc.

[0155] [7. Correspondence of terms]

[0156] The API gateway 30 in this embodiment is equivalent to the collaborative control unit in this disclosure. The multiple service applications belonging to the service system function block group 23, 24, the control system function block group 25 and the data system function block group 26 in this disclosure are equivalent to the multiple function blocks in this disclosure. The information storage unit 31 in this embodiment is equivalent to the policy storage unit in this disclosure. The API authorization policy in this embodiment is equivalent to the authorization policy in this disclosure. The cloud server 200 in this embodiment is equivalent to the authorization policy providing unit and the management server in this disclosure. The vehicle-mounted devices 2 to 5 in this embodiment are equivalent to the electronic control device in this disclosure. The storage unit 202 in this embodiment is equivalent to the authorization policy storage unit in this disclosure. The processing S310 to S330 performed by the control unit 201 in this embodiment is equivalent to the authorization policy generation unit in this disclosure. The processing S340 performed by the control unit 201 in this embodiment is equivalent to the authorization policy providing unit in this disclosure.

[0157] [8. Technical ideas disclosed in this specification]

[0158] [Project 1]

[0159] A mobility service providing system comprises: an in-vehicle system, which is mounted on a vehicle and comprises a plurality of electronic control devices connected to an in-vehicle network; and

[0160] The authorization strategy providing unit is arranged outside the vehicle.

[0161] The above-mentioned vehicle-mounted system has:

[0162] a plurality of functional blocks, each mounted on any one of the plurality of electronic control devices, and configured to execute a determined process; and

[0163] A cooperation control unit is configured to realize cooperation among the plurality of functional blocks.

[0164] The above-mentioned cooperative control unit has:

[0165] a policy storage unit configured to obtain and store the authorization policy that specifies the access rights between the functional blocks from the authorization policy providing unit; and

[0166] The access control unit is configured to, upon receiving an access request to a destination block from a source block, use the authorization policy stored in the policy storage unit to determine whether the source block has access rights to the destination block, and, if it is determined that the source block has access rights, transmit the access request to the destination block, wherein the source block is one of the plurality of functional blocks and the destination block is another of the plurality of functional blocks.

[0167] The authorization policy providing unit is configured to provide the vehicle-mounted system with a static viewpoint policy generated by integrating a plurality of viewpoint-based policies that define the access rights for each of a plurality of viewpoints focusing on the static attributes of the functional block as the authorization policy.

[0168] [Project 2]

[0169] The mobility service providing system according to item 1, wherein:

[0170] One of the above-mentioned strategies classified by viewpoints takes the safety of the functions provided by the above-mentioned functional blocks as the above-mentioned viewpoint.

[0171] [Item 3]

[0172] The mobility service providing system according to item 1 or item 2, wherein:

[0173] One of the strategies for differentiation by viewpoint is to use the reliability of the source of supply of the functional block as the viewpoint.

[0174] [Item 4]

[0175] The mobility service providing system according to any one of items 1 to 3, wherein:

[0176] The authorization policy includes one or more dynamic viewpoint policies in addition to the static viewpoint policy, and the one or more dynamic viewpoint policies define the access authority for each of the one or more viewpoints focusing on dynamic attributes of the function block.

[0177] [Item 5]

[0178] The mobility service providing system according to item 4, wherein:

[0179] One of the dynamic viewpoint strategies is to use the presence or absence of the vehicle user's consent as the viewpoint.

[0180] [Item 6]

[0181] The mobility service providing system according to item 4 or item 5, wherein:

[0182] One of the dynamic viewpoint strategies uses the access status between the functional blocks as the viewpoint.

[0183] [Item 7]

[0184] The mobility service providing system according to any one of items 1 to 6, wherein:

[0185] The authorization policy is generated from at least one of the security, finance, operation, and privacy of assets classified as security protection as the viewpoint.

[0186] [Item 8]

[0187] An in-vehicle system comprises: a plurality of function blocks, each of which is mounted on any one of a plurality of electronic control devices connected to an in-vehicle network and is configured to execute a determined process; and

[0188] A cooperation control unit is configured to realize cooperation among the plurality of functional blocks.

[0189] The above-mentioned cooperative control unit has:

[0190] a policy storage unit configured to store an authorization policy, wherein the authorization policy specifies access rights between the functional blocks; and

[0191] The access control unit (32) is configured to, upon receiving an access request from a source block to a destination block, use the authorization policy stored in the policy storage unit to determine whether the source block has access rights to the destination block, and, if it is determined that the source block has access rights, transmit the access request to the destination block, wherein the source block is one of the plurality of functional blocks and the destination block is another of the plurality of functional blocks.

[0192] The authorization policy includes a static viewpoint policy generated by integrating a plurality of viewpoint-specific policies that define the access rights for each of a plurality of viewpoints focusing on static attributes of the functional block.

[0193] [Item 9]

[0194] A management server is a management server connected to a vehicle in a communicable manner, wherein the vehicle is provided with an on-board system, and the on-board system has a plurality of electronic control devices connected to an on-board network.

[0195] The above management server has:

[0196] an authorization policy storage unit configured to store an authorization policy referred to in order to control access rights from a utilization source block to a utilization destination block, wherein the utilization source block is one of a plurality of function blocks mounted in any one of the plurality of electronic control devices and configured to respectively execute a determined process, and the utilization destination block is another function block of the plurality of function blocks;

[0197] an authorization policy generating unit configured to generate a static viewpoint policy by integrating the plurality of static viewpoint-based policies that define the access rights for each of the plurality of viewpoints focusing on the static attributes of the functional block, and store the static viewpoint policy as the authorization policy in the authorization policy storing unit; and

[0198] The authorization policy providing unit is configured to provide the authorization policy stored in the authorization policy storage unit to the vehicle.

[0199] [Item 10]

[0200] The management server according to item 9, wherein:

[0201] The above-mentioned authorization policy generation unit is constructed as follows: based on a plurality of policies differentiated by dynamic viewpoints that define the above-mentioned access rights for each of a plurality of viewpoints focusing on the dynamic attributes of the above-mentioned functional blocks, a dynamic viewpoint policy is generated by integrating the plurality of the above-mentioned policies differentiated by dynamic viewpoints, and the dynamic viewpoint policy is stored as the above-mentioned authorization policy in the above-mentioned authorization policy storage unit.

[0202] [Item 11]

[0203] An access control method is an access control method in which at least one of a plurality of electronic control devices uses an authorization policy that specifies access rights between the functional blocks to control access between the plurality of the functional blocks, wherein the plurality of functional blocks are respectively mounted on any one of the plurality of electronic control devices connected to an in-vehicle network and are configured to respectively execute a determined process, wherein:

[0204] using, as the authorization policy, a static viewpoint policy generated by integrating a plurality of viewpoint-specific policies that define the access rights for each of a plurality of viewpoints focusing on the static attributes of the functional block,

[0205] If an access request to a destination block is received from a source block, it is determined whether the source block has access rights to the destination block based on the authorization policy. If it is determined that the source block has access rights, the access request is passed to the destination block, wherein the source block is one of the multiple functional blocks and the destination block is another of the multiple functional blocks.

[0206] [Item 12]

[0207] A program for causing a computer to implement the following function, for implementing an access control method for controlling access between a plurality of function blocks using an authorization policy that specifies access rights between the function blocks, wherein the plurality of function blocks are respectively mounted on any one of a plurality of electronic control devices connected to an in-vehicle network and are configured to respectively execute a determined process,

[0208] and using, as the authorization policy, a static viewpoint policy generated by integrating a plurality of viewpoint-specific policies that define the access rights for each of a plurality of viewpoints focusing on the static attributes of the functional block; and

[0209] If an access request to a destination block is received from a source block, it is determined whether the source block has access rights to the destination block based on the authorization policy. If it is determined that the source block has access rights, the access request is passed to the destination block, wherein the source block is one of the multiple functional blocks and the destination block is another of the multiple functional blocks.

[0210] In addition, in items 8 to 12, contents corresponding to the descriptions in items 2 to 7 may be added.

[0211] [9. Other embodiments]

[0212] As mentioned above, although embodiment of this disclosure was described, this disclosure is not limited to the said embodiment, Various deformation|transformation can be made and it can be implemented.

[0213] (a) In the above-mentioned embodiment, the O attribute is not illustrated, but a policy for each attribute created with the same idea as the S attribute can be used. For example, in air conditioning control, it is considered that the policy is set so that the state set to AUTO will not be changed to an uncomfortable setting. The S attribute targets phenomena related to life, while the O attribute also targets comfort and convenience.

[0214] (b) In the above-described embodiment, the ECU 2 includes the real-time processing unit 10 and the application processing unit 20 , but may include either one of them.

[0215] (c) In the above-mentioned embodiment, the ECU 2 includes the service system function block groups 23 and 24, the control system function block group 25, and the data system function block group 26, but at least a part of the function block groups 23 to 26 may be included in other vehicle-mounted devices 3 to 5. In addition, the function block 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.

[0216] (d) The vehicle-mounted device, etc. and the method thereof described in the present disclosure may also be implemented by a special-purpose 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 device, etc. and the method thereof described in the present disclosure may also be implemented by a special-purpose computer, which is provided by a processor composed of one or more special-purpose hardware logic circuits. Alternatively, the vehicle-mounted device, etc. and the method thereof described in the present disclosure may also be implemented by one or more special-purpose 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-transitional tangible recording medium readable by a computer. The method for realizing the functions of each part included in the vehicle-mounted device, etc. does not necessarily need to include software, and all its functions may be realized using one or more hardware.

[0217] (e) 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 the structure of other above-mentioned embodiments.

[0218] (f) In addition to the above-mentioned mobility service providing system 1, the vehicle-mounted system 100, and the cloud server 200 serving as an authorization policy providing unit and a management server, the present disclosure may also be implemented in various forms such as a program for enabling a computer to function as the vehicle-mounted system 100 and the authorization policy providing unit, a non-transitional physical recording medium such as a semiconductor memory recording the program, and an access control method.

Claims

1. A mobility service providing system, comprising: An in-vehicle system, mounted on a vehicle, having a plurality of electronic control devices connected to an in-vehicle network; and The authorization strategy providing unit is arranged outside the vehicle. The above-mentioned vehicle-mounted system has: a plurality of functional blocks, each mounted on any one of the plurality of electronic control devices, and configured to execute a determined process; and A cooperation control unit is configured to realize cooperation among the plurality of functional blocks. The above-mentioned cooperative control unit has: a policy storage unit configured to obtain and store the authorization policy that specifies the access rights between the functional blocks from the authorization policy providing unit; and The access control unit is configured to, upon receiving an access request to a destination block from a source block, use the authorization policy stored in the policy storage unit to determine whether the source block has access rights to the destination block, and, if it is determined that the source block has access rights, pass the access request to the destination block, wherein: The utilization source block is one of the plurality of functional blocks, and the utilization destination block is another functional block of the plurality of functional blocks. The authorization policy providing unit is configured to provide the vehicle-mounted system with a static viewpoint policy generated by integrating a plurality of viewpoint-based policies that define the access rights for each of a plurality of viewpoints focusing on the static attributes of the functional block as the authorization policy.

2. The mobility service providing system according to claim 1, wherein: One of the above-mentioned strategies classified by viewpoints takes the safety of the functions provided by the above-mentioned functional blocks as the above-mentioned viewpoint.

3. The mobility service providing system according to claim 1, wherein: One of the strategies for differentiation by viewpoint is to use the reliability of the source of supply of the functional block as the viewpoint.

4. The mobility service providing system according to any one of claims 1 to 3, wherein: The authorization policy includes one or more dynamic viewpoint policies in addition to the static viewpoint policy, and the one or more dynamic viewpoint policies define the access authority for each of the one or more viewpoints focusing on dynamic attributes of the function block.

5. The mobility service providing system according to claim 4, wherein: One of the dynamic viewpoint strategies is to use the presence or absence of the vehicle user's consent as the viewpoint.

6. The mobility service providing system according to claim 4, wherein: One of the dynamic viewpoint strategies uses the access status between the functional blocks as the viewpoint.

7. The mobility service providing system according to claim 1, wherein: The authorization policy is generated from at least one of the security, finance, operation, and privacy of assets classified as security protection as the viewpoint.

8. A vehicle-mounted system comprising: A plurality of functional blocks are respectively mounted on any one of a plurality of electronic control devices connected to the vehicle network and are configured to respectively execute the determined processing; and A cooperation control unit is configured to realize cooperation among the plurality of functional blocks. The above-mentioned cooperative control unit has: a policy storage unit configured to store an authorization policy, wherein the authorization policy specifies access rights between the functional blocks; and The access control unit is configured to, upon receiving an access request to a destination block from a source block, use the authorization policy stored in the policy storage unit to determine whether the source block has access rights to the destination block, and, if it is determined that the source block has access rights, pass the access request to the destination block, wherein: The utilization source block is one of the plurality of functional blocks, and the utilization destination block is another functional block of the plurality of functional blocks. The authorization policy includes a static viewpoint policy generated by integrating a plurality of viewpoint-specific policies that define the access rights for each of a plurality of viewpoints focusing on static attributes of the functional block.

9. A management server is a management server communicably connected to a vehicle, wherein: The vehicle is provided with an on-board system, wherein the on-board system has a plurality of electronic control devices connected to an on-board network. The above management server has: an authorization policy storage unit, mounted on any one of the plurality of electronic control devices, configured to store an authorization policy referred to in order to control access rights from a utilization source block to a utilization destination block, wherein the utilization source block is one of a plurality of function blocks configured to respectively execute determined processing, and the utilization destination block is another function block of the plurality of function blocks; an authorization policy generating unit configured to generate a static viewpoint policy by integrating the plurality of static viewpoint-based policies that define the access rights for each of the plurality of viewpoints focusing on the static attributes of the functional block, and store the static viewpoint policy as the authorization policy in the authorization policy storing unit; and The authorization policy providing unit is configured to provide the authorization policy stored in the authorization policy storage unit to the vehicle.

10. The management server according to claim 9, wherein: The above-mentioned authorization policy generation unit is constructed as follows: based on a plurality of policies differentiated by dynamic viewpoints that define the above-mentioned access rights for each of a plurality of viewpoints focusing on the dynamic attributes of the above-mentioned functional blocks, a dynamic viewpoint policy is generated by integrating the plurality of the above-mentioned policies differentiated by dynamic viewpoints, and the dynamic viewpoint policy is stored as the above-mentioned authorization policy in the above-mentioned authorization policy storage unit.

11. An access control method, wherein at least one of a plurality of electronic control devices uses an authorization policy that specifies access rights between functional blocks to control access between the plurality of functional blocks, wherein: The plurality of functional blocks are respectively mounted on any one of the plurality of electronic control devices connected to the vehicle network and are configured to respectively execute the determined processing, wherein: using, as the authorization policy, a static viewpoint policy generated by integrating a plurality of viewpoint-specific policies that define the access rights for each of a plurality of viewpoints focusing on the static attributes of the functional block, If an access request to a destination block is received from a source block, it is determined whether the source block has access rights to the destination block based on the authorization policy. If it is determined that the source block has access rights, the access request is passed to the destination block, wherein the source block is one of the multiple functional blocks and the destination block is another of the multiple functional blocks.

12. A program for causing a computer to implement the following function: to implement an access control method for controlling access between a plurality of function blocks using an authorization policy that specifies access rights between the function blocks, wherein: The plurality of functional blocks are respectively mounted on any one of a plurality of electronic control devices connected to the vehicle network, and are configured to respectively execute a determined process. A static viewpoint policy is used as the authorization policy. The static viewpoint policy is generated by integrating a plurality of viewpoint-based policies that define the access rights for each of a plurality of viewpoints focusing on the static attributes of the functional block. If an access request to a destination block is received from a source block, it is determined whether the source block has access rights to the destination block based on the authorization policy. If it is determined that the source block has access rights, the access request is passed to the destination block, wherein the source block is one of the multiple functional blocks and the destination block is another of the multiple functional blocks.