Method and device for processing data associated with a product designed for use of software functions

Abstract

The invention relates to a method, for example a computer-implemented method, for processing data associated with a product designed for use of software functions, said method comprising: determining a knowledge graph based on a system description characterising at least part of the product; determining, based on the knowledge graph, initial information characterising a significance of at least one of the software functions for a homologation of the product.

Description

[0001] Description

[0002] title

[0003] Method and apparatus for processing data associated with a product designed to use software functions

[0004] State of the art

[0005] The disclosure relates to a method for processing data associated with a product configured to use software functions.

[0006] The disclosure relates to an apparatus for processing data associated with a product configured to use software functions.

[0007] Disclosure of the invention

[0008] Example embodiments relate to a method, for example a computer-implemented method, for processing data associated with a product designed to use software functions, comprising: determining a knowledge graph based on a system description characterizing at least part of the product, determining, based on the knowledge graph, first information that characterizes a significance of at least one of the software functions for a homologation of the product. In further example embodiments, this enables, for example, an evaluation of software components, e.g., software functions, of the product or for the product with regard to relevance with regard to homologation, which may be important, e.g., in cases of changes to the software components, e.g., software functions.In further exemplary embodiments, homologation refers to a process of approval and / or certification, e.g. to ensure that the product complies with legal regulations and / or standards, e.g., in the case of a motor vehicle, with regard to emissions and / or safety and / or performance.

[0009] In further exemplary embodiments, it is provided that the first information characterizes a significance of a) at least one new software function and / or b) at least one modified software function for the homologation of the product.

[0010] In further exemplary embodiments, it is provided that the system description is in machine-readable form, for example in an XML, extended markup language, -based format, for example in an Automotive Open System Architecture, AUTOSAR, XML, ARXML, format.

[0011] In further exemplary embodiments, it is provided that the system description describes a vehicle, for example a motor vehicle, for example an overall system corresponding to the motor vehicle, for example formed by the motor vehicle.

[0012] In further exemplary embodiments, the principle according to the embodiments can be used, for example, for automated and / or assisted determination of homologation relevance, e.g., of new or modified software functions for a motor vehicle. As vehicles become increasingly digitalized and their range of functions increases, exemplary embodiments result in a growing need for retrofitting functionalities onto a motor vehicle, e.g., after the vehicle is already in the field and has been homologated. For example, UN Regulation R 156 requires a review of whether a software update is relevant for type approval.

[0013] In conventional approaches, the above-mentioned process can be represented, for example, by a new or modified software component being developed, e.g., by an original equipment manufacturer (OEM), or a supplier, and then deployed to the corresponding vehicles, e.g., via an over-the-air update (OTA update) mechanism. Between these two processes (development and deployment), a release process takes place, for example, in which tests are conducted in various dimensions (e.g., technical tests (software tests, system tests, etc.), compliance checks (legality, etc.).

[0014] In further exemplary embodiments, at least one dimension of these tests relates to vehicle approval or homologation. For example, it may involve proving that new or modified software in a component does not invalidate the vehicle's type approval.

[0015] The principle according to the embodiments enables, in further exemplary embodiments, for example, the provision of a method that serves to determine and / or verify the homologation relevance of a software change, e.g., in an automated manner (i.e., e.g., without human interaction), for example based on the described knowledge graph or the initial information. This enables, in further exemplary embodiments, for example, a structured analysis of causal chains between a new / modified software component and homologation-relevant software components that are already installed in the vehicle.

[0016] In further exemplary embodiments, it is provided that the method comprises: providing, for example importing, the system description.

[0017] In further exemplary embodiments, it is provided that the method comprises: creating, for example, automatically creating, at least one machine-readable report based on the first information, and, optionally, evaluating, for example, automatically evaluating, the at least one machine-readable report, and, optionally, influencing at least one aspect of a development process and / or manufacturing process associated with the product based on the evaluation and / or based on the at least one machine-readable report. In further exemplary embodiments, it is provided that the method comprises at least one of the following elements: a) assigning a significance for the homologation of the product, for example, a homologation relevance, to at least one of the software functions, b) identifying at least one of the software functions with regard to its significance for the homologation of the product,for example, their homologation relevance, c) determining at least one chain of effects that describes at least some, for example, all, connections between new software functions and / or modified software functions and / or existing software functions of the product, for example by evaluating links in the knowledge graph, d) using information about links between components, for example, software functions, of the product based on a system description of an AUTOSAR Virtual Function Bus (VFB), and / or by incorporating a call tree of software functions into the knowledge graph, e) determining at least one set of software components, for example, software functions, that are associated with the at least one chain of effects, for example, belonging to the at least one chain of effects, for example, organizing the set of software components in the form of a list,f) Evaluating the set of software components, for example software functions, for their homologation relevance, for example obtaining a set of software functions classified as homologation relevant, g) Creating at least one report based on the set of software functions classified as homologation relevant.

[0018] Further exemplary embodiments relate to an apparatus for carrying out the method according to the embodiments.

[0019] Further exemplary embodiments relate to a computer-readable storage medium comprising instructions that, when executed by a computer, cause the computer to perform the method according to the embodiments.

[0020] Further exemplary embodiments relate to a

[0021] Computer program comprising instructions which, when executed by a computer, cause the computer to carry out the method according to the embodiments.

[0022] Further exemplary embodiments relate to a data carrier signal that transmits and / or characterizes the computer program according to the embodiments.

[0023] Further exemplary embodiments relate to a use of the method according to the embodiments and / or the device according to the embodiments and / or the computer-readable storage medium according to the embodiments and / or the computer program according to the embodiments and / or the data carrier signal according to the embodiments for at least one of the following elements: a) automation of homologation relevance tests, b) generation of machine-readable reports for one or more automated

[0024] Process steps relating to the product, c) testing, for example efficient testing of whether a change to software for the product is relevant for type-approval, d) avoiding the expiry of a type-approval of the product, e) structured analysis of causal chains between software components for the product.

[0025] Further features, possible applications, and advantages of the invention will become apparent from the following description of exemplary embodiments of the invention, which are illustrated in the figures of the drawing. All described or illustrated features, individually or in any combination, constitute the subject matter of the invention, regardless of their summary in the claims or their references, as well as regardless of their wording or representation in the description or in the drawing.

[0026] The drawing shows:

[0027] Fig. 1 schematically shows a simplified flow diagram according to exemplary embodiments, Fig. 2 schematically shows a simplified block diagram according to exemplary embodiments,

[0028] Fig. 3 schematically shows a simplified flow diagram according to exemplary embodiments,

[0029] Fig. 4 schematically shows a simplified flow diagram according to exemplary embodiments,

[0030] Fig. 5 schematically shows a simplified flow diagram according to exemplary embodiments,

[0031] Fig. 6 schematically shows a simplified flow diagram according to exemplary embodiments,

[0032] Fig. 7 schematically shows a simplified block diagram according to exemplary embodiments,

[0033] Fig. 8 schematically illustrates aspects of uses according to exemplary embodiments.

[0034] Exemplary embodiments, Fig. 1, 2, relate to a method, for example a computer-implemented method, for processing data DAT-10 associated with a product 10 designed to use software functions SW-F (Fig. 2), comprising: determining 102 (Fig. 1) a knowledge graph KG based on a system description SD characterizing at least a part of the product 10, determining 104, based on the knowledge graph KG, first information 1-1 that characterizes a significance of at least one of the software functions SW-F for a homologation HOMOLOG-10 of the product 10. In further exemplary embodiments, this enables, for example, an evaluation of software components, e.g., software functions, of the product 10 or for the product 10 with regard to relevance with regard to a homologation, which may be necessary, for example, in cases of changes to the software components, e.g.,Software functions, may be important. In further exemplary embodiments, the software functions SW-F may be at least one of the following elements: a) current software function, e.g., currently used in the product 10; b) new software function, e.g., modified, e.g., planned for future use in the product 10.

[0035] In further exemplary embodiments, Fig. 2, it is provided that the first information 1-1 characterizes a meaning of a) at least one new software function SW-Fn and / or b) at least one modified software function SW-F' for the homologation HOMOLOG-10 of the product.

[0036] In further exemplary embodiments, it is provided that the system description SD is in machine-readable form, for example in an XML, extended markup language, -based format, for example in an Automotive Open System Architecture, AUTOSAR, XML, ARXML, format.

[0037] In further exemplary embodiments, Fig. 2, it is provided that the system description SD describes a vehicle, for example a motor vehicle, 10, for example an overall system corresponding to the motor vehicle 10, for example formed by the motor vehicle 10.

[0038] In further exemplary embodiments, Fig. 2, the principle according to the embodiments can be used, for example, for automated and / or assisted determination of homologation relevance, for example of new or modified software functions SW-F, SW-Fn, SW-F' for a motor vehicle 10. As vehicles become increasingly digitalized and their range of functions increases, exemplary embodiments result in a growing need for functionalities to be loaded onto a motor vehicle, for example, after the vehicle is already in the field and has been homologated. For example, UN Regulation R 156 requires a check to determine whether a software update is relevant for type approval.

[0039] In conventional approaches, the above-mentioned process can be represented, for example, by a new or modified software component being developed, e.g., by an original equipment manufacturer (OEM), or a supplier, and then deployed to the corresponding vehicles, e.g., via an over-the-air update (OTA update) mechanism. Between these two processes (development and deployment), a release process takes place, for example, in which tests are conducted in various dimensions (e.g., technical tests (software tests, system tests, etc.), compliance checks (legality, etc.).

[0040] In further exemplary embodiments, at least one dimension of these tests relates to vehicle approval or homologation. For example, it may involve proving that new or modified software in a component does not invalidate the vehicle's type approval.

[0041] The principle according to the embodiments enables, in further exemplary embodiments, for example, the provision of a method which serves to determine and / or prove the homologation relevance of a software change, e.g., in an automated manner (i.e., e.g., without human interaction), for example based on the described knowledge graph KG (Fig. 1) or the first information 1-1. This enables, in further exemplary embodiments, for example, a structured analysis of causal chains between a new / modified software component and homologation-relevant software components that are already installed in the vehicle 10.

[0042] In further exemplary embodiments, Fig. 1, it is provided that the method comprises: providing 100, for example importing 100a, the system description SD.

[0043] In further exemplary embodiments, Fig. 3, it is provided that the method comprises: creating 110, for example automated (e.g. without human interaction) creating 110a, at least one machine-readable report B based on the first information 1-1 (Fig. 1), and, optionally, evaluating 112, for example automated evaluating 112a, the at least one machine-readable report B, and, optionally, influencing 114 at least one aspect ASP-DEV, ASP-PROD of a development process and / or manufacturing process associated with the product 10 based on the evaluating 112, 112a and / or based on the at least one machine-readable report B.

[0044] In further exemplary embodiments, Fig. 4, it is provided that the method comprises at least one of the following elements: a) Assigning 120 a meaning BED for the homologation HOMOLOG-10 (Fig. 2) of the product 10, for example a homologation relevance, to at least one of the software functions SW-F, b) Identifying 121 at least one of the software functions SW-F with regard to its meaning for the homologation of the product, for example its homologation relevance, c) Determining 122 at least one causal chain WK that describes at least some, for example all, connections between new software functions SW-Fn and / or modified software functions SW-F' and / or existing software functions SW-F of the product 10, for example by evaluating 122a links of the knowledge graph KG, d) Using 123 information INF-VFB about links between components, for example software functions,of the product 10 based on a system description of an AUTOSAR Virtual Function Bus, VFB, and / or by incorporating 123a a call tree (hierarchical representation of calls) of software functions into the knowledge graph KG, e) determining 124 at least one set of software components, for example software functions, SW-F-WK, which are associated with the at least one effect chain WK, for example belonging to the at least one effect chain WK, for example organizing 124a the set SW-F-WK of software components in the form of a list, f) evaluating 125 the set of software components, for example software functions, SW-F-WK, for their homologation relevance, whereby, for example, a set of software functions SW-F-HOMOLOG classified as homologation-relevant is obtained, g) creating 126 at least one report B' based on the set of software functions SW-F-HOMOLOG classified as homologation-relevant.

[0045] Fig. 5 schematically shows a simplified flow diagram according to exemplary embodiments. Element E1 symbolizes a system description SD (e.g., present in a standardized format, such as arxml format), and / or a binary call tree, for example. Element E2 symbolizes a conversion of the system description SD into a graph, e.g., the knowledge graph KG (Fig. 1), as well as optional support functions, e.g., to mark existing software components in a system model with regard to their homologation relevance (e.g., by tagging, e.g., "not homologation-relevant," "relevance with regard to ECE-R138.01," etc.).

[0046] Element E4 symbolizes a component for, e.g., systematic analysis of the knowledge graph KG, e.g., with regard to causal chains WK between a new / modified software component SW-Fn, SW-F' and already existing, potentially homologation-relevant software components SW-F in the product 10 (Fig. 2).

[0047] Element E5 symbolizes an optional generation and / or provision of reports E6, which, for example, allow a conclusion to be drawn about the homologation relevance of a software change (SW-Fn and / or SW-f').

[0048] Optionally, a user interface E7 can be provided for a user E8. In further exemplary embodiments, the exemplary process described above with reference to Fig. 5 can be carried out, e.g., completely automated. In further exemplary embodiments, the reports E6 can also be used, e.g., completely automated, for example, influencing a development system and / or a production facility, e.g., for the product 10 or associated software functions SW-F.

[0049] Fig. 6 schematically shows a simplified flowchart according to exemplary embodiments. Element E10 symbolizes a start. Element E11 symbolizes an import of the system description E12 of the product 10, e.g., an entire vehicle, and element E13 symbolizes a determination of a corresponding knowledge graph based on the system description E12.

[0050] In further exemplary embodiments, such a system description E12 can be present in various formats, for example in a standardized format such as the AUTOSAR “System Configuration Description”, for example using a standardized XML schema, for example arxml.

[0051] In further exemplary embodiments, only a part of the overall system 10 can be loaded in this form (e.g., a sub-domain such as a powertrain).

[0052] Element E14 symbolizes an identification of software components already present, e.g., in the system, with regard to their homologation relevance. In other exemplary embodiments, this identification may also have been implemented in advance and provided, e.g., by the system description E12 or additional information sources (not shown).

[0053] Element E15 symbolizes a subsequent process step in which, e.g. with the help of a query of links on the knowledge graph KG, a number, e.g. organized in the form of a list, of effect chains WK is determined, e.g. generated, in which at least some, e.g. all, connections between new / changed software components and, e.g. any other software components present in the system are recorded.

[0054] In further exemplary embodiments, additional information about connections between components can be included, for example. One example of this is an AUTOSAR system description that contains, for example, an AUTOSAR Virtual Function Bus (VFB). In some embodiments, dependencies between the senders and the receivers can be determined from the VFB and / or from a (e.g., binary) function call tree (e.g., a "call tree") that is integrated, for example, into the knowledge graph KG. In further exemplary embodiments, this makes it possible, for example, to trace internal wiring and thus filter out irrelevant connections / dependencies.

[0055] Element E16 symbolizes at least one subsequent process step by deriving a further list, which, for example, includes all software components that are part of one of the previously recorded chains of effects. In element E17, this list of affected software components is analyzed, for example, for their homologation relevance, resulting in a filtered list that contains, for example, only those software components that have been classified as homologation-relevant.

[0056] Based on this list, reports E19 are created in element E18, which allow conclusions to be drawn about the homologation relevance of the software change to be examined.

[0057] In further exemplary embodiments, the E19 reports may be written in natural language, for example for human consumption.

[0058] In further exemplary embodiments, the reports E19 may be machine-readable and, in further exemplary embodiments, may be evaluated, for example, for use in subsequent automated process steps.

[0059] Further exemplary embodiments, Fig. 7, relate to an apparatus 200 for carrying out the method according to the embodiments.

[0060] In further exemplary embodiments, it is provided that the device 200 comprises: a computing device ("computer") 202 having at least one computing core 202a, a memory device 204 assigned to the computing device 202 for at least temporarily storing at least one of the following elements: a) data DAT (e.g. the data DAT-10 associated with the product 10 and / or information of the system description SD and / or the first information 1-1 or information associated with the knowledge graph KG), b) computer program PRG, for example for carrying out the method according to the embodiments.

[0061] In further exemplary embodiments, the storage device 204 comprises a volatile memory (e.g., random access memory (RAM)) 204a, and / or a non-volatile (NVM) memory (e.g., flash EEPROM) 204b, or a combination thereof or with other memory types not explicitly mentioned. Further exemplary embodiments relate to a computer-readable storage medium SM, comprising instructions PRG, which, when executed by a computer 202, cause the computer 202 to execute the method according to the embodiments.

[0062] Further exemplary embodiments relate to a computer program PRG comprising instructions which, when the program PRG is executed by a computer 202, cause the computer 202 to carry out the method according to the embodiments.

[0063] Further exemplary embodiments relate to a data carrier signal DCS that characterizes and / or transmits the computer program PRG according to the embodiments. The data carrier signal DCS is exchangeable, e.g., transmittable and / or receivable, via an optional data interface 206 of the device 200.

[0064] Further exemplary embodiments, Fig. 8, relate to a use 300 of the method according to the embodiments and / or the device 200 according to the embodiments and / or the computer-readable storage medium SM according to the embodiments and / or the computer program PRG according to the embodiments and / or the data carrier signal DCS according to the embodiments for at least one of the following elements: a) automation 301 of homologation relevance checks, b) generation 302 of, for example, machine-readable reports B, B' for one or more automated process steps relating to the product 10, c) checking, for example, efficiently checking 303, whether a change to a software for the product 10 is relevant for type approval, d) avoiding 304 a revocation of a type approval for the product 10, e) structured analysis 305 of causal chains WK between software components for the product 10.

[0065] In further exemplary embodiments, the principle according to the embodiments can be used, for example, for at least one of the following elements: a) Software Update Management Systems (e.g. SUMS), e.g. for the automotive sector, e.g. according to the UN R156 regulation, and / or b) in the context of release processes in pipelines for continuous integration (CI) and continuous delivery (CD) ("CI / CD pipelines"), and / or c) in the context of product releases, e.g. vehicle releases, e.g. in general (e.g. during the initial registration of new models).

Claims

Claims 1. Method, for example a computer-implemented method, for processing data (DAT-10) associated with a product (10) designed to use software functions (SW-F), comprising: determining (102) a knowledge graph (KG) based on a system description (SD) characterizing at least part of the product (10), determining (104), based on the knowledge graph (KG), first information (1-1) that characterizes a significance of at least one of the software functions (SW-F) for a homologation (HOMOLOG-10) of the product (10).

2. Method according to claim 1, wherein the first information (1-1) has a meaning a) of at least one new software function (SW-Fn) and / or b) of at least one changed software function (SW-F 1 ) for the homologation (HOMOLOG-10) of the product (10).

3. Method according to at least one of the preceding claims, wherein the system description (SD) is in machine-readable form, for example in an XML, extended markup language, - based format, for example in an Automotive Open System Architecture, AUTOSAR, XML, ARXML, format.

4. Method according to at least one of the preceding claims, wherein the system description (SD) describes a vehicle (10), for example a motor vehicle, for example an overall system corresponding to the motor vehicle (10), for example formed by the motor vehicle (10).

5. Method according to at least one of the preceding claims, comprising: providing (100), for example importing (100a), the system description (SD).

6. The method according to at least one of the preceding claims, comprising: creating (110), for example automated creation (110a), at least one machine-readable report (B) based on the first information (1-1), and, optionally, evaluating (112), for example automated evaluation (112a), the at least one machine-readable report (B), and, optionally, influencing (114) at least one aspect (ASP-DEV, ASP-PROD) of a development process and / or manufacturing process associated with the product (10) based on the evaluation (112a) and / or based on the at least one machine-readable report (B).

7. Method according to at least one of the preceding claims, comprising at least one of the following elements: a) Assigning (120) a meaning (BED) for the homologation (HOMOLOG-10) of the product (10), for example a homologation relevance, to at least one of the software functions (SW-F), b) Marking (121) at least one of the software functions (SW-F) with regard to its meaning (BED) for the homologation (HOMOLOG-10) of the product (10), for example its homologation relevance, c) Determining (122) at least one chain of effects (WK) which contains at least some, for example all, connections between new software functions (SW-Fn) and / or modified software functions (SW-F 1) and / or existing software functions (SW-F) of the product (10), for example by evaluating (122a) links of the knowledge graph (KG), d) using (123) information (INF-VFB) about links between components, for example software functions, of the product (10) based on a system description of an AUTOSAR Virtual Function Bus, VFB, and / or by incorporating (123a) a call tree of software functions into the knowledge graph (KG), e) determining (124) at least one set of software components, for example software functions, (SW-F-WK) that are associated with the at least one chain of effects (WK), for example belonging to the at least one chain of effects (WK), for example organizing (124a) the set of software components (SW-F-WK) in the form of a list, f) evaluating (125) the set of software components, for example software functions, (SW-F-WK) on their homologation relevance,where, for example, a set is defined as, homologation-relevant software functions (SW-F-HOMOLOG), g) preparation (126) of at least one report (B 1 ) based on the set of software functions classified as homologation-relevant (SW-F-HOMOLOG).

8. Device (200) for carrying out the method according to at least one of the preceding claims.

9. Computer-readable storage medium (SM) comprising instructions (PRG) which, when executed by a computer (202), cause the computer to carry out the method according to at least one of claims 1 to 7.

10. Computer program (PRG) comprising instructions which, when the program (PRG) is executed by a computer (202), cause the computer (202) to carry out the method according to at least one of claims 1 to 7.

11. Data carrier signal (DCS) that transmits and / or characterizes the computer program (PRG) according to claim 10.

12. Use (300) of the method according to at least one of claims 1 to 7 and / or the device (200) according to claim 8 and / or the computer-readable storage medium (SM) according to claim 9 and / or the computer program (PRG) according to claim 10 and / or the data carrier signal (DCS) according to claim 11 for at least one of the following elements: a) automation (301) of homologation relevance checks, b) generation (302) of machine-readable reports (B, B') for one or more automated process steps relating to the product (10), c) checking (303), for example efficient checking (303), whether a change to software for the product (10) is relevant for type approval, d) avoiding (304) a loss of type approval for the product (10), e) structured analysis (305) of causal chains between software components for the product (10).

Images