Information processing method, information processing device, and program

The information processing method and device in vehicles dynamically manage software by detecting new additions and user contracts, updating software lists, and using a vehicle-stored SBOM for real-time vulnerability assessment, addressing security and efficiency issues in existing systems.

WO2024247379A1PCT designated stage expired Publication Date: 2024-12-05PANASONIC INTELLECTUAL PROPERTY MANAGEMENT CO LTD
View PDF 5 Cites 0 Cited by

Patent Information

Application Number
PCT/JP2024/004348
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-05-30
Filing Date
2024-02-08
Publication Date
2024-12-05

AI Technical Summary

Technical Problem

Existing software management systems in vehicles lack effective methods to dynamically manage software vulnerabilities and user contracts, leading to potential security risks and inefficiencies in enabling or disabling vehicle functions based on user permissions.

Method used

An information processing method and device that detects new software additions, determines user contracts, and updates software information lists to ensure only contracted software is enabled, using a Software Bill of Materials (SBOM) stored on the vehicle for real-time management and vulnerability assessment.

Benefits of technology

This approach enables secure, real-time management of software vulnerabilities and user permissions, ensuring only contracted software is operational, enhancing vehicle security and responsiveness by maintaining accurate software lists even without server connectivity.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure JP2024004348_05122024_PF_FP_ABST
    Figure JP2024004348_05122024_PF_FP_ABST
Patent Text Reader

Abstract

An information processing method performed using a computer in a vehicle 100 that switches between enabling and disabling each of the equipped functions thereof depending on whether or not the user of the vehicle has a contract for the function, said information processing method comprising: a detection step S11 for detecting a new addition of software for operating one or more functions; a determination step 14 for determining whether or not the user has a contract for the function operated by the software, the new addition of which has been detected; an acquisition step for acquiring software information corresponding to the software for which it is determined that the user has a contract; and an update step (step S15, step S16, and step S17) for updating a software information list of functions operable in the vehicle by adding the acquired software information.
Need to check novelty before this filing date? Find Prior Art

Description

Information processing method, information processing device, and program

[0001] The present disclosure relates to an information processing method, an information processing device, and a program.

[0002] Patent Literature 1 describes a technology that, when transmitting software called a container to a device, uses an unmodifiable area provided in the software to ensure that the unmodifiable area has not been modified, thereby appropriately providing information about vulnerabilities in the software contained in the unmodifiable area (hereinafter simply referred to as vulnerability information). There is a demand for information processing technology for appropriately managing software installed in devices, particularly for detecting software vulnerabilities using appropriately transmitted vulnerability information as described in Patent Literature 1.

[0003] International Publication No. 2021 / 260753

[0004] The present disclosure provides an information processing method and the like for more appropriately managing software.

[0005] An information processing method according to one aspect of the present disclosure is an information processing method executed by a computer in a vehicle that switches whether or not each of the equipped functions is operable depending on whether or not the user of the vehicle has a contract for the function, and includes a detection step of detecting new additions of software for operating one or more functions, a determination step of determining whether or not the user has a contract for the function operated by the software for which the new addition has been detected, an acquisition step of acquiring software information corresponding to the software for which it has been determined that the user has a contract, and an update step of updating a software information list of functions that are operable in the vehicle by adding the acquired software information.

[0006] Another aspect of the present disclosure is an information processing device mounted on a vehicle that switches whether or not each of the equipped functions is operable depending on whether or not the user of the vehicle has a contract, and includes a detection unit that detects new additions of software for operating one or more functions, a determination unit that determines whether or not the user has a contract for the function operated by the software for which new additions have been detected, an acquisition unit that acquires software information corresponding to the software for which it has been determined that the user has a contract, a memory unit that stores a software information list of functions that are operable in the vehicle, and an update unit that updates the stored software information list by adding the acquired software information.

[0007] A program according to one aspect of the present disclosure is a program for causing a computer to execute the information processing method described above.

[0008] These general or specific aspects may be realized by a device, an integrated circuit, a computer program, or a non-transitory recording medium such as a computer-readable CD-ROM, or by any combination of a device, an integrated circuit, a computer program, and a non-transitory recording medium.

[0009] According to the information processing method and the like of the present disclosure, it becomes possible to manage software more appropriately.

[0010] FIG. 1 is a block diagram illustrating an example of a functional configuration of an information processing system according to an embodiment. FIG. 2 is a flowchart illustrating an example of an operation for adding hardware to the information processing system according to an embodiment. FIG. 3 is a diagram illustrating an example of an SBOM and an available SBOM for the information processing system according to an embodiment. FIG. 4 is a diagram illustrating an example of software information for software for operating additional hardware in the information processing system according to an embodiment. FIG. 5 is a diagram illustrating an example of SFOP information for the information processing system according to an embodiment. FIG. 6 is a diagram illustrating changes in the SBOM, available SBOM, and S / W information for the information processing system according to an embodiment. FIG. 7 is a diagram illustrating changes in the SBOM, available SBOM, and S / W information for the information processing system according to an embodiment. FIG. 8 is a diagram illustrating changes in the SBOM, available SBOM, and S / W information for the information processing system according to an embodiment. FIG. 9 is a flowchart illustrating an example of an operation for re-authentication of the information processing system according to an embodiment. FIG. 10 is a flowchart illustrating an example of an operation for addressing vulnerability in the information processing system according to an embodiment.

[0011] (Summary of the Present Disclosure) The summary of the present disclosure is as follows.

[0012] An information processing method according to a first aspect of the present disclosure is an information processing method executed by a computer in a vehicle that switches whether or not each of the equipped functions is operable depending on whether or not the user of the vehicle has a contract, and includes a detection step of detecting new additions of software for operating one or more functions, a determination step of determining whether or not the user has a contract for the function operated by the software for which the new addition has been detected, an acquisition step of acquiring software information corresponding to the software for which it has been determined that the user has a contract, and an update step of updating a software information list of functions that are operable in the vehicle by adding the acquired software information.

[0013] According to this information processing method, software for operating hardware that has actually been contracted for and is available for use in a vehicle (hardware that executes operable functions) can be managed as software information using a software information list. Therefore, software that is being used even though its software information is not included in the software information list due to the addition of software, software that is not being used even though its software information is not included in the software information list due to the presence of hardware but not being contracted for, and software that is included in the software information list but is not being used, can be managed more appropriately because the software information list of the present disclosure does not include such software.

[0014] Furthermore, an information processing method according to a second aspect of the present disclosure is the information processing method described in the first aspect, wherein the acquisition step further acquires software information corresponding to software for which it is determined that the user has no contract, and the update step updates the software information list of functions that can be operated in the vehicle by adding software information corresponding to software for which it is determined that the user has a contract from the acquired software information, and updates the equipped software information list of functions equipped in the vehicle by adding all of the acquired software information.

[0015] This allows software management using a software information list of functions that can be operated in the vehicle, which is separate from the software information list.

[0016] Furthermore, an information processing method according to a third aspect of the present disclosure is the information processing method described in the first or second aspect, wherein the detection step detects the addition of new software by introducing into the vehicle hardware that is operated by software and performs a function corresponding to the software.

[0017] This allows the addition of hardware to be used as a trigger to update the software information list, regarding it as the addition of software.

[0018] Furthermore, an information processing method according to a fourth aspect of the present disclosure is an information processing method according to any one of the first to third aspects, and further includes a switch detection step of detecting that one or more pieces of software among the operable software have been switched to an inoperable state, and a deletion / update step of updating the software information list by deleting software information corresponding to the software for which the switch has been detected from the software information list.

[0019] According to this, by detecting when software is switched to an inoperable state, the software information of the inoperable software can be deleted from the software information list, thereby maintaining the software information list in accordance with the actually available software.

[0020] Furthermore, an information processing method according to a fifth aspect of the present disclosure is the information processing method described in the fourth aspect, in which the switch detection step detects a switch to an inoperable state of one or more pieces of software due to a change from a state in which a user has a contract for a function operated by the software to a state in which the contract does not exist.

[0021] This makes it possible to detect when the software becomes inoperable by detecting a change from a state in which the user has a contract to a state in which the user does not have the contract.

[0022] An information processing method according to a sixth aspect of the present disclosure is the information processing method according to the fifth aspect, wherein the software information includes information on a type of function operated by the corresponding software.

[0023] This allows software to be managed using information about the type of function operated by the software.

[0024] Furthermore, an information processing method according to a seventh aspect of the present disclosure is the information processing method described in the sixth aspect, wherein in the deletion / update step, if information regarding the type of function operated by the software for which switching has been detected satisfies a first condition, software information corresponding to the software for which switching has been detected is prohibited from being deleted from the software information list.

[0025] According to this, when the information on the type of function operated by the software satisfies the first condition, it is possible to prevent the software information from being deleted from the software information list.

[0026] Furthermore, an information processing method according to an eighth aspect of the present disclosure is the information processing method described in the seventh aspect, wherein in the deletion and update step, when information regarding the type of function operated by the software whose switching has been detected satisfies a first condition and the state of the vehicle satisfies a second condition, the software information corresponding to the software whose switching has been detected is prohibited from being deleted from the software information list.

[0027] According to this, when the information regarding the type of function operated by the software satisfies the first condition and the vehicle state satisfies the second condition, the software information can be prevented from being deleted from the software information list.

[0028] In addition, an information processing method according to a ninth aspect of the present disclosure is an information processing method described in any one of the first to eighth oil resistance aspects, and further includes a vulnerability management step of managing vulnerabilities in software for operating functions that can be operated in the vehicle using the updated software information list.

[0029] This makes it possible to use the updated software information list to manage vulnerabilities in software for operating functions that are operable in a vehicle.

[0030] An information processing method according to a tenth aspect of the present disclosure is the information processing method according to the ninth aspect, wherein the vulnerability management step is executed at predetermined intervals.

[0031] This allows for the management of software vulnerabilities for operating functions that are operable in a vehicle to be performed at predetermined intervals (i.e., periodically) using the updated software information list.

[0032] In addition, an information processing device according to an eleventh aspect of the present disclosure is an information processing device mounted on a vehicle that switches whether or not each of the equipped functions is operable depending on whether or not the user of the vehicle has a contract, and includes a detection unit that detects new addition of software for operating one or more functions, a determination unit that determines whether or not the user has a contract for the function operated by the software for which the new addition has been detected, an acquisition unit that acquires software information corresponding to the software for which it has been determined that the user has a contract, a memory unit that stores a software information list of functions that are operable in the vehicle, and an update unit that updates the stored software information list by adding the acquired software information.

[0033] This provides the same effects as the information processing method described above.

[0034] A program according to a twelfth aspect of the present disclosure is a program for causing a computer to execute the information processing method according to any one of the first to tenth aspects.

[0035] According to this, by using a computer, the same effects as those of the information processing method described above can be achieved.

[0036] These general or specific aspects may be realized by a device, an integrated circuit, a computer program, or a non-transitory recording medium such as a computer-readable CD-ROM, or by any combination of a device, an integrated circuit, a computer program, and a non-transitory recording medium.

[0037] Hereinafter, embodiments will be described in detail with reference to the accompanying drawings. However, more detailed explanation than necessary may be omitted. For example, detailed explanation of well-known matters or redundant explanation of substantially the same configuration may be omitted. This is to avoid unnecessary redundancy in the following explanation and to facilitate understanding by those skilled in the art.

[0038] The present inventors have provided the accompanying drawings and the following description to enable those skilled in the art to fully understand the present disclosure, and do not intend for them to limit the subject matter described in the claims.

[0039] (Embodiment) Fig. 1 is a diagram illustrating an overview of an information processing system according to an embodiment. Fig. 1 shows a vehicle 100, a server 200, and a wireless audio 300, which is an example of added hardware (hereinafter sometimes referred to as H / W), which constitute the information processing system according to the embodiment. Here, an example will be described in which, when the wireless audio 300 is added by being connected to the vehicle 100, operation control software (hereinafter sometimes referred to as S / W) for operating the wireless audio 300 is added as one piece of software for the vehicle 100.

[0040] The added S / W is S / W for operating the wireless audio 300, which is one of many H / W components that can be connected to the vehicle 100. In other words, the vehicle 100 is equipped with S / W for operating each of the many H / W components, including the added S / W. Typically, such S / W is managed by the manufacturer of the vehicle 100 using information about one or more S / W components included in each S / W, i.e., a software bill of materials (SBOM). If a malfunction or other problem occurs in the vehicle 100, the manufacturer refers to the SBOM to consider necessary S / W modifications, or, if the SBOM contains a S / W component with a newly discovered vulnerability, to update the corresponding S / W component. In this way, the SBOM is used to manage the S / W installed in the vehicle 100.

[0041] Meanwhile, conventionally, because SBOMs can be managed centrally on a server, they have been stored on a server operated by the manufacturer, and not on vehicle 100. In contrast, the inventors of the present application have discovered that if SBOMs are stored on the vehicle, the SBOMs can be dynamically changed and used on the vehicle side even when connection to the server is unavailable or there are communication delays, and therefore such SBOMs can be used to verify vulnerabilities in zero-trust systems for software installed on the vehicle. The present invention is based on this finding.

[0042] 1 , vehicle 100 includes SBOM management unit 101, authentication unit 102, execution control unit 103, vulnerability management unit 104, camera 105, fingerprint authentication sensor 106, SBOM 107, available SBOM 108, function SFOP information 109, autonomous driving system 110, audio player 111, etc. The configuration of vehicle 100 is not limited to this example, and one or more of the above components may be omitted. The above components included in vehicle 100 include a processing unit, which is a virtual functional configuration realized by computer processing using an on-board computer, memory, programs, etc., and a device unit, which is a functional configuration involving physical devices, etc.

[0043] SBOM management unit 101 is a processing unit that updates SBOM 107, which is a list of software information corresponding to each piece of software installed in vehicle 100, and available SBOM 108, which is a list of software information available to individual users among the software installed in vehicle 100, by adding new software information to or deleting software information from SBOM 107 and available SBOM 108. SBOM management unit 101 detects the addition of new hardware to vehicle 100, thereby detecting the addition of software for operating the hardware that accompanies the addition of the hardware. SBOM management unit 101 then updates SBOM 107 and available SBOM 108 by adding software information corresponding to the added software to these SBOMs. SBOM management unit 101 adds software information corresponding to all of the added software to SBOM 107, and, on the other hand, adds only a portion of the software information corresponding to the added software to usable SBOM 108, as the case may be, thereby individually updating SBOM 107 and usable SBOM 108. SBOM management unit 101 may detect the addition of software instead of detecting the addition of hardware.

[0044] Specifically, SBOM management unit 101 determines whether a function executed by the operation of each H / W installed in vehicle 100 is a function for which the user of vehicle 100 has already signed a contract, and determines S / W information to be added to or deleted from available SBOM 108 based on the determination result. That is, in this embodiment, vehicle 100 can switch whether or not each of the functions executed by the installed H / W is operable depending on whether or not the user of vehicle 100 has signed a contract for the function. The management of whether or not each function is operable in vehicle 100 is determined based on whether or not the user's contract for the function exists in user authentication information and user contract information 201 stored in server 200. Note that some of the functions installed in vehicle 100 do not have the concept of a user contract. Available SBOM 108 also includes software information corresponding to software for operating hardware for executing functions for which the concept of a user contract does not exist (for example, functions used for basic operation of vehicle 100, basic car audio functions, etc.). This makes it possible to obtain software information currently available to each individual user in real time by referring to available SBOM 108, and even when a user changes or a contract is renewed, vulnerability management and access control based on the latest information can be performed by using the software information.

[0045] The authentication unit 102 is a processing unit that acquires input information for user authentication by using the camera 105, the fingerprint authentication sensor 106, etc., and determines whether the user using the vehicle 100 is a registered user. In addition, if there are multiple registered users, the authentication unit 102 also performs processing to identify which of the multiple registered users is the user currently using the vehicle 100.

[0046] Execution control unit 103 is a processing unit that controls the execution of the software installed in the vehicle. For example, execution control unit 103 permits the execution of software corresponding to software information included in available SBOM 108, and does not permit the execution of software corresponding to software information that is installed in vehicle 100 but is not included in available SBOM 108. This allows some hardware to operate using software corresponding to software information included in available SBOM 108. As described above, available SBOM 108 contains only software information for software corresponding to functions for which the user has already signed up or functions that do not require a user contract. Therefore, execution control unit 103 can operate only software corresponding to functions that are substantially operable for the user.

[0047] Vulnerability management unit 104 is a processing unit that determines whether or not there is a vulnerability in the software installed in vehicle 100, and takes measures to address the vulnerability as necessary. Furthermore, when a vulnerability has been addressed, vulnerability management unit 104 modifies the software related to the response, and therefore may instruct SBOM management unit 101 to update the software information in SBOM 107 and usable SBOM 108.

[0048] The camera 105 is a device mounted on the vehicle 100 in a position that allows it to capture an image of the user's face. The camera 105 is used for face authentication of the user, for example.

[0049] The fingerprint authentication sensor 106 is a device mounted in a position in the vehicle 100 where it can detect a user's fingerprint. The fingerprint authentication sensor 106 is used when authenticating a user's fingerprint, for example.

[0050] The camera 105 and the fingerprint authentication sensor 106 are not essential components, and instead of these, a microphone used for voiceprint authentication of a user, or a vein sensor used for vein authentication of a user may be provided.

[0051] SBOM 107 is an example of an equipment software information list, and is information stored in a storage unit (not shown). There are no particular limitations on the format of SBOM 107 as long as it lists software information.

[0052] Available SBOM 108 is an example of a software information list, and is information stored in a storage unit (not shown), etc. There are no particular limitations on the format of available SBOM 108 as long as it lists the software information. However, since the software information in SBOM 107 may be referenced and incorporated into available SBOM 108, it is preferable that the format be consistent with that of SBOM 107.

[0053] Function SFOP information 109 is information regarding types when classifying each function installed in vehicle 100 from the viewpoints of safety (S), finance (F), operation (O), and privacy (P), and is stored in a storage unit (not shown) or the like. Function SFOP information 109 includes, for each function, four values: whether or not the function corresponds to SFOP S, whether or not the function corresponds to SFOP F, whether or not the function corresponds to SFOP O, and whether or not the function corresponds to SFOP P, but is not limited to these. For example, function SFOP information 109 may include only information regarding whether or not the function corresponds to SFOP S. A reference destination for function SFOP information 109 is specified by software information included in SBOM 107 or available SBOM 108. That is, predetermined information in the SFOP information 109 of the function is referenced for each piece of S / W information, and four values ​​of SFOP for each function are provided.

[0054] The autonomous driving system 110 is an example of a function that requires a user contract, and is a device unit that includes various sensors, an automatic steering device, and a control device that processes the sensing results and controls the automatic steering device. The autonomous driving system 110 is attached to the vehicle 100 by a manufacturer, for example, when the vehicle 100 is manufactured.

[0055] The audio player 111 is an example of a function that requires a user contract, and is a device unit that includes a sound source data input unit, a speaker, and a drive unit that drives the speaker based on the sound source data input by the sound source data input unit. The audio player 111 may be attached to the vehicle 100 by the manufacturer when the vehicle 100 is manufactured, or may be attached or replaced by the user by a contractor or the like different from the manufacturer.

[0056] Server 200 is a data server operated by the manufacturer of vehicle 100. Server 200 includes user authentication information and user contract information 201, additional H / W S / W information 202, vehicle SBOM 203, vehicle available SBOM 204, function SFOP information 205, and vulnerability database 206.

[0057] The components included in the server 200 are all information stored in a storage unit (not shown) or the like.

[0058] The user authentication information and user contract information 201 is a database that links authentication information, such as a camera image or a fingerprint, input by the user with the user's personal information, and also links the user's personal information with information on functions that the user has subscribed to. The authentication unit 102 uses the input information as a query, refers to the user authentication information and user contract information 201, and reads out the user's personal information and information on functions that the user has subscribed to.

[0059] The additional H / W software information 202 is a database of software information for one or more pieces of H / W that can be added to each vehicle model or vehicle. For example, a manufacturer of the additional H / W that has a contract with the manufacturer of the vehicle 100 links authentication information to be attached to the additional H / W with software information for operating the additional H / W stored in the additional H / W and delivers the resulting information to the manufacturer of the vehicle 100 in advance. The manufacturer of the vehicle 100 constructs the additional H / W software information 202 using the delivered authentication information and the software information for operating the additional H / W. Then, when the additional H / W is connected to the vehicle 100, for example, the authentication unit 102 references the additional H / W software information 202 using the authentication information of the additional H / W as a query, and reads the software information for operating the additional H / W. This ensures safety that the additional H / W is made by an additional H / W manufacturer that has a contract with the vehicle manufacturer, and also makes it possible to obtain S / W information for the S / W that operates the additional H / W.

[0060] The vehicle SBOM 203 is a database that synchronizes and stores one or more individual vehicle SBOMs 107. For example, the SBOM management unit 101 periodically copies and transmits the SBOM 107 to the server 200 to update the vehicle SBOM 203.

[0061] Vehicle's available SBOM 204 stored in server 200 is synchronized with vehicle's available SBOM 108 in vehicle 100. For example, SBOM management unit 101 periodically copies and transmits available SBOM 108 to server 200 to update vehicle's available SBOM 204. Vehicle's SBOM 203 and vehicle's available SBOM 204 are provided for each vehicle 100.

[0062] SFOP information 205 of functions present on server 200 is synchronized with SFOP information 109 of functions in vehicle 100. For example, when SBOM management unit 101 updates SBOM 107 and available SBOM 108, it copies SFOP information 205 of functions on server 200 and updates SFOP information 109 of functions. As a result, if SFOP information 205 of functions on server 200 is updated, SFOP information 109 of functions on vehicle 100 is automatically kept up to date.

[0063] The vulnerability database 206 is a database constructed by collecting information on software vulnerabilities. The vulnerability database 206 is updated by collecting information on software vulnerabilities periodically or as needed.

[0064] The wireless audio 300 is an example of additional H / W, and in this case, it is H / W that enables sound source data from a wireless transmission device to be input to the sound source data input section of the audio player 111 via short-range wireless communication.

[0065] The wireless audio 300 includes a wireless communication module 301 , an audio control unit 302 , H / W authentication information 303 , and S / W 304 for operating the wireless audio 300 .

[0066] The wireless communication module 301 receives audio source data from a wireless transmitting device through short-range wireless communication, and includes an antenna, an amplifier, a signal conversion circuit, and the like.

[0067] The audio control unit 302 is a processing unit that converts the sound source data received by the wireless communication module 301 into a format that can be input to the sound source data input unit of the audio player 111 and inputs the converted data.

[0068] The H / W authentication information 303 is authentication information for the wireless audio 300. When the wireless audio 300 is connected, the authentication unit 102 reads the authentication information from the H / W authentication information 303 and makes an inquiry to the server 200 to confirm that the wireless audio 300 is an authentic product sold by a manufacturer of additional H / W that has entered into a contract with the manufacturer of the vehicle 100, and also reads S / W information corresponding to S / W 304 from the S / W information 202 of the additional H / W.

[0069] The S / W 304 is S / W for operating the wireless audio 300 on the vehicle 100 side.

[0070] Next, the operation of the information processing system configured as described above will be described with reference to Fig. 2. Fig. 2 is a flowchart showing an example of the operation of the information processing system according to the embodiment when adding H / W. As shown in Fig. 2, for example, when wireless audio 300 is connected to vehicle 100, vehicle 100 detects the connection and thereby detects the addition of H / W (detection step S11).

[0071] The authentication unit 102 reads the authentication information of the wireless audio device 300 and queries the server to authenticate the hardware (first authentication step S12). At this time, the vehicle 100 reads and acquires software information corresponding to the software 304 from the software information 202 of the additional hardware (acquisition step). If the hardware authentication is successful (Yes in the first authentication step S12), the authentication unit 102 further queries the server to authenticate the user using the input information (second authentication step S13). If the user authentication determines that the user is appropriate to use the vehicle 100, the authentication is successful (Yes in the second authentication step S13), and it is determined whether the user has subscribed to a function executed by operation of the wireless audio device 300 (determination step S14). For example, in the second authentication step, the authentication unit 102 reads the user's personal information along with information on the functions subscribed to by the user associated with the personal information. It is determined whether the user has subscribed to a function executed by operation of the wireless audio device 300 based on the information on the functions subscribed to by the user.

[0072] If it is determined that the user has already subscribed to the function executed by the operation of the wireless audio 300 (Yes in determination step S14), S / W 304 for operating the wireless audio 300 is installed, and the S / W information is added to the SBOM 107 and to the available SBOM 108, thereby updating the SBOM 107 and the available SBOM 108 (steps S15 and S16).

[0073] On the other hand, if it is determined that the user has not subscribed to the function executed by operation of wireless audio 300 (No in determination step S14), S / W 304 for operating wireless audio 300 is installed, and the S / W information is added to SBOM 107, thereby updating SBOM 107 (step S17). At this time, although S / W 304 is installed, the S / W information is not added to available SBOM 108, and available SBOM 108 is not updated. Steps S15, S16, and S17 are all included in the update step.

[0074] If the H / W authentication is not successful (No in the first authentication step S12) and if the user authentication is not successful (No in the second authentication step S13), the process ends without performing any further processing.

[0075] As a result of this operation, S / W information corresponding to all S / W installed in vehicle 100 is included in SBOM 107, and S / W information corresponding to S / W that is available to the user because of a contract among the installed S / W is included in available SBOM 108. As a result, available SBOM 108 can list the S / W that is actually being used in vehicle 100, and by using such available SBOM 108, it is possible to address S / W vulnerabilities and perform access control on the S / W that is actually being used. For example, if an SBOM containing S / W information for S / W installed by a manufacturer is stored only on a server operated by the manufacturer, a discrepancy may occur between the S / W information in the SBOM and the S / W that is actually being used when a user adds H / W. In contrast to this, in the present embodiment, by dynamically storing the software information of the software actually used in the vehicle 100 as the available SBOM 108, it becomes possible to always respond to software vulnerabilities and perform access control in accordance with the actual use. In other words, it becomes possible to respond to attacks on the software with zero trust.

[0076] Furthermore, SBOM 107, which is updated separately from available SBOM 108, allows a list of software installed in vehicle 100. When deleting software information from available SBOM 108 (described later), the information on the software installed in vehicle 100 can be retained even when there is no communication between vehicle 100 and server 200. This allows software information to be deleted from available SBOM 108 without communication between available SBOM and server 200. Therefore, even when there is no communication between vehicle 100 and server 200, it is possible to switch software not to be used and to switch the functions operated by that software to an inoperable state. Therefore, providing SBOM 107 separately from available SBOM 108 has the advantage of improving responsiveness.

[0077] The following describes specific examples of the formats of SBOM 107 and available SBOM 108. Fig. 3 is a diagram showing an example of the SBOM and available SBOM of the information processing system according to the embodiment. Fig. 4 is a diagram showing an example of software information of software for operating additional hardware in the information processing system according to the embodiment.

[0078] As shown in Figures 3 and 4, the SBOM 107, available SBOM 108, and software information in this example are written in SPDX format. As shown in the figures, all are version SPDX-2.2, and the data license is CC0-1.0. As an example, this shows an example in which "USB_AUDIO_1" is added as additional hardware to the SBOM 107 and available SBOM 108 of "IVI_1." "SPDXRef-DOCUMENT" is set as the SPDXID, and "https: / / ..." is declared as the namespace.

[0079] 3, SBOM 107 and available SBOM 108 contain multiple pieces of software information, including "linux_kernel," "glibc," and software not shown. Details of each piece of software will be omitted, but for example, the software information for each piece of software includes "SPDXID," "PackageVersion (software version)," "PackageDownloadLocation (s / w acquisition source)," "PackageLicenseDeclared (s / w license information)," "PackageLicenseComments (additional information in the software license)," "FileName," "SPDXID," "FileChecksum (identity confirmation information)," etc. For example, from the viewpoint of responding to software vulnerabilities, since the software version and software license information are important, other information may not be included as long as this information is included in SBOM 107 and available SBOM 108. Furthermore, depending on how SBOM 107 and available SBOM 108 are used, they may be configured with only other information, excluding the software version and software license information.

[0080] 4, the software information of the software for operating the additional hardware includes multiple pieces of software information, including "libusb," "curl," and software not shown. Details of each piece of software will be omitted, but for example, the software information of the software for operating each piece of additional hardware includes information similar to that of SBOM 107 and available SBOM 108. Furthermore, the software information of the software for operating the additional hardware includes "OTHER SFOP_information" as the value of "Relationship," i.e., information about the SFOP of the function of the additional hardware. Here, the information includes the reference destination of the SFOP information for each function when referencing the SFOP information 109 of the function.

[0081] FIG. 5 is a diagram illustrating an example of SFOP information of the information processing system according to the embodiment.

[0082] 5, the SFOP information is composed of four values ​​indicating whether it corresponds to "Safety" (True) or not (False), whether it corresponds to "Financial" (True) or not (False), whether it corresponds to "Operational" (True) or not (False), or whether it corresponds to "Privacy" (True) or not (False). In the example shown in the figure, it is indicated that it corresponds to "Safety" and "Operational" (True), and not to "Financial" and "Privacy" (False).

[0083] Such SFOP information is referenced when deleting software information from the available SBOM 108, as will be described later.

[0084] 6 to 8 are diagrams showing changes in the SBOM, available SBOM, and software information of the information processing system according to the embodiment. In FIGS. 6 to 8, (a) shows SBOM 107, (b) shows available SBOM 108, and (c) shows software information for the software required to operate the additional hardware. Also, FIG. 6 shows the state before the hardware is added to vehicle 100, FIG. 7 shows the state after the hardware is added to vehicle 100 and before the user signs a contract for the function, and FIG. 8 shows the state after the hardware is added to vehicle 100 and after the user signs a contract for the function.

[0085] As shown in Figures 6 to 8, if hardware is added before a function contract is made, the software information of the additional hardware is added only to SBOM 107, and the software information of the additional hardware is not added to usable SBOM 108. If a user contracts for the function in this state, the software information of the additional hardware is also added to usable SBOM 108, and the function executed by the operation of this hardware becomes available. Here, if the software information of the additional hardware has been added to SBOM 107, the software information of the additional hardware may be obtained from server 200 or from SBOM 107. In other words, if the software information of the additional hardware has already been added to SBOM 107, the update of usable SBOM 108 in vehicle 100 is completed when the function is subsequently contracted.

[0086] Next, another operation of the information processing system configured as described above will be described with reference to Fig. 9. Fig. 9 is a flowchart showing an example of the operation of the information processing system according to the embodiment in re-authentication. The flowchart shown in Fig. 9 illustrates an example in which the addition of H / W is completed in the flowchart shown in Fig. 2 and then user authentication is performed again. For example, the operation shown in Fig. 9 is performed when the use of the vehicle 100 is stopped and then resumed, or when the use of the vehicle 100 exceeds a certain time.

[0087] 9 , first, authentication unit 102 re-authenticates the user (step S21). If user authentication is not successful (No in step S21), it means that a user other than the current user is using vehicle 100, and therefore usable SBOM 108 needs to be updated to match the user currently using vehicle 100. Here, an example in which usable SBOM 108 is added during the update will be described with reference to FIG. 2 and its description, and an example in which usable SBOM 108 and software information are deleted during the update will be described.

[0088] If user authentication is not successful (No in step S21), SBOM management unit 101 identifies candidate functions to be stopped (step S22). Identifying candidate functions to be stopped is an example of a switch detection step for detecting switching of software to an inoperable state. SBOM management unit 101 identifies functions to be switched to an inoperable state as candidate functions to be stopped, for example, based on the available SBOM 108 of the original user and information on functions subscribed to by the current user that are linked to the personal information of the current user.

[0089] SBOM management unit 101 then determines whether the identified candidate function to be stopped satisfies a predetermined first condition (step S23). The first condition is, for example, that the candidate function to be stopped is a function that corresponds to "Safety" in the SFOP information that classifies the candidate function to be stopped. Note that the first condition here is merely an example, and may be set appropriately depending on the management of S / W that is to be realized using SBOM 107 and available SBOM 108.

[0090] SBOM management unit 101 refers to the SFOP information of the identified candidate function to be stopped, and if "Safety" is True, determines that a predetermined first condition is satisfied (Yes in step S23), and acquires the state of vehicle 100 (step S24). If "Safety" is True in the SFOP information of the identified candidate function to be stopped, switching the candidate function to be stopped to an inoperable state may lead to safety implications, so it further determines whether or not to switch the candidate function to be stopped to an inoperable state depending on the state of the vehicle.

[0091] Therefore, SBOM management unit 101 further determines whether the acquired state of vehicle 100 satisfies a second condition (step S25). The second condition is that the acquired state of vehicle 100 is a state that is not recommended for stopping the candidate functions to be stopped (for example, a state in which the vehicle is running or the IG power is on). Note that the second condition here is an example, and may be set appropriately depending on the management of software to be achieved using SBOM 107 and available SBOM 108.

[0092] If SBOM management unit 101 determines that the predetermined second condition is satisfied based on the acquired state of vehicle 100 (Yes in step S25), it ends the processing. In this way, if SBOM management unit 101 determines that the identified candidate function to be stopped satisfies the predetermined first condition and also satisfies the predetermined second condition, it prohibits switching the candidate function to be stopped to inoperable.

[0093] On the other hand, SBOM management unit 101 refers to the SFOP information of the identified candidate function to be stopped, and if "Safety" is False, it determines that the predetermined first condition is not met (No in step S23), and proceeds to deletion / update step S26 without acquiring the state of vehicle 100. Similarly, if SBOM management unit 101 determines that the predetermined second condition is not met from the acquired state of vehicle 100 (No in step S25), it proceeds to deletion / update step S26.

[0094] In the deletion / update step S26, the software information of the software that operates the candidate function to be stopped is deleted from the available SBOM 108 and updated. If the user authentication is successful (Yes in step S21), it is determined whether the user's contract for the function is still in effect (step S27). If the contract for the function is not in effect (No in step S27), that is, if the user's contract for the function has changed from a state in which the user had a contract to a state in which the contract is not in effect, step S22 is executed to identify the function for which the contract is no longer in effect as a candidate function to be stopped. If the user authentication is successful (Yes in step S21) and the user's contract for the function is still in effect (Yes in step S27), the process ends.

[0095] Such re-authentication processing is executed periodically or as needed. That is, after the processing is completed, if the conditions for starting re-authentication are met, the processing is started again from step S21.

[0096] Next, still another operation of the information processing system configured as above will be described with reference to Fig. 10. Fig. 10 is a flowchart showing an example of the operation of the information processing system according to the embodiment in response to vulnerability.

[0097] In the present embodiment, the description has been given of using usable SBOM 108 to address vulnerabilities in the software installed in vehicle 100. In the operation example shown in Fig. 10, the operation of the information processing system in addressing this vulnerability will be described.

[0098] As shown in FIG. 10 , first, for any of the software information in the available SBOM 108, processing to address that software information, i.e., software vulnerability management, is performed (vulnerability management step S30). In the vulnerability management step S30, the vulnerability database 206 is queried for the software information to obtain the latest vulnerability information (step S301). Then, it is determined whether there is any vulnerability information requiring action (step S302). For example, if new vulnerability information is found in the vulnerability database, it is determined that there is vulnerability information requiring action (Yes in step S302), and action is taken to address the vulnerability (step S303). If it is determined that there is no vulnerability information requiring action (No in step S302), the vulnerability management step S30 is terminated. Next, it is determined whether processing has been completed for all of the software information included in the available SBOM 108 (step S31). If processing has not been completed for all of the software information (No in step S31), the vulnerability management step S30 is initiated for the next software information. If the processing for all the software information has been completed (Yes in step S31), the processing ends.

[0099] This vulnerability response process is executed periodically or as needed. That is, after the process is completed, if the re-authentication start condition is met, the process is restarted from step S30.

[0100] Other Embodiments Although the control device and the like according to the embodiments of the present disclosure have been described above, the present disclosure is not limited to these embodiments.

[0101] For example, in the above embodiments, each component may be configured with dedicated hardware, or may be realized by executing a software program suitable for each component. Each component may be realized by a program execution unit such as a CPU or processor reading and executing a software program recorded on a recording medium such as a hard disk or semiconductor memory.

[0102] Each component may be a circuit (or integrated circuit). These circuits may form a single circuit as a whole, or each may be a separate circuit. Each of these circuits may be a general-purpose circuit or a dedicated circuit.

[0103] Furthermore, the general or specific aspects of the present disclosure may be realized as a system, an apparatus, a method, an integrated circuit, a computer program, or a non-transitory recording medium such as a computer-readable CD-ROM. Also, they may be realized as any combination of a system, an apparatus, a method, an integrated circuit, a computer program, and a computer-readable non-transitory recording medium. Furthermore, in the above embodiments, the processing performed by a specific processing unit may be performed by another processing unit. Furthermore, the order of multiple processes in the operation of the communication system described in the above embodiments may be changed, or multiple processes may be performed in parallel.

[0104] In addition, this disclosure also includes forms obtained by applying various modifications to each embodiment that a person skilled in the art would think of, or forms realized by arbitrarily combining the components and functions of each embodiment within the scope that does not deviate from the intent of this disclosure.

[0105] The present disclosure is useful in managing software in a vehicle.

[0106] 100 Vehicle 101 SBOM management unit 102 Authentication unit 103 Execution control unit 104 Vulnerability management unit 105 Camera 106 Fingerprint authentication sensor 107 SBOM 108 Usable SBOM 109, 205 SFOP information of function 110 Autonomous driving system 111 Audio player 200 Server 201 User authentication information and user contract information 202 S / W information of additional H / W 203 SBOM of vehicle 204 Usable SBOM of vehicle 206 Vulnerability database 300 Wireless audio 301 Wireless communication module 302 Audio control unit 303 H / W authentication information 304 S / W

Claims

1. An information processing method executed by a computer in a vehicle that switches whether or not each of the equipped functions is enabled depending on whether or not the user of the vehicle has a contract for the function, the information processing method including: a detection step of detecting new addition of software for operating one or more functions; a determination step of determining whether or not the user has a contract for the function operated by the software for which the new addition was detected; an acquisition step of acquiring software information corresponding to the software for which it was determined that the user has a contract; and an update step of updating a software information list of functions that are enabled in the vehicle by adding the acquired software information.

2. The information processing method of claim 1, further comprising: in the acquisition step, acquiring software information corresponding to the software for which it is determined that the user has no contract; and in the update step, updating a software information list of functions operable in the vehicle by adding, from the acquired software information, software information corresponding to the software for which it is determined that the user has a contract; and updating an equipped software information list of functions equipped in the vehicle by adding all of the acquired software information.

3. The information processing method according to claim 1, wherein the detection step detects the new addition of the software by introducing into the vehicle hardware that is operated by the software and performs a function corresponding to the software.

4. The information processing method according to claim 1, further comprising: a switch detection step of detecting when one or more of the operable software pieces are switched to an inoperable state; and a delete / update step of updating the software information list by deleting from the software information list the software information corresponding to the software piece for which the switch has been detected.

5. The information processing method according to claim 4, wherein said switch detection step detects a switch to an inoperable state of one or more of said software programs by a change from a state in which the user has a contract for a function operated by said software to a state in which said contract does not exist.

6. The information processing method according to claim 5, wherein the software information includes information regarding a type of function operated by the corresponding software.

7. The information processing method of claim 6, wherein in the deletion / update step, if information regarding the type of function operated by the software in which switching has been detected satisfies a first condition, the software information corresponding to the software in which switching has been detected is prohibited from being deleted from the software information list.

8. The information processing method according to claim 7, wherein in the deletion and update step, when information regarding the type of function operated by the software in which switching has been detected satisfies the first condition and the state of the vehicle satisfies a second condition, deletion of the software information corresponding to the software in which switching has been detected from the software information list is prohibited.

9. The information processing method according to any one of claims 1 to 8, further comprising a vulnerability management step of managing vulnerabilities in software for operating functions operable in the vehicle using the updated software information list.

10. The information processing method according to claim 9, wherein the vulnerability management step is executed at predetermined intervals.

11. An information processing device mounted on a vehicle that switches whether or not each of the equipped functions is enabled depending on whether or not a contract has been made by the user of the vehicle, the information processing device comprising: a detection unit that detects new addition of software for operating one or more functions; a determination unit that determines whether or not the user has a contract for the function operated by the software for which new addition has been detected; an acquisition unit that acquires software information corresponding to the software for which it has been determined that the user has a contract; a memory unit that stores a software information list of functions that are enabled in the vehicle; and an update unit that updates the stored software information list by adding the acquired software information.

12. A program for causing a computer to execute the information processing method according to claim 1.

Citation Information

Patent Citations

  • Transmission device, reception device, container transmission system, method, and program

    WO2021260753A1

  • Method for downloading application software to on-board device, and the on-board device

    JP2013126802A

  • Distributed ledger for software distribution in wireless ad hoc network for ad-hoc data processing on source node

    JP2021111970A

  • Apparatuses, Methods, and Computer Programs for Determining a Status of a Vehicle and for Determining a Software Update of a Vehicle

    US20230032689A1

  • Software management system

    WO2023074904A1