Real-time execution system integration method, device, equipment, medium and vehicle

Abstract

The invention discloses a real-time execution system integration method and device, equipment, a medium and a vehicle. The method comprises the steps that development request information of a real-time execution system is acquired; analyzing the development request information by using a pre-configured first script to obtain to-be-developed interface information in a to-be-integrated real-time execution system; the to-be-developed interface information is configured in an ARXML configuration file through a pre-configured second script, a target ARXML configuration file is obtained, and the target ARXML configuration file comprises all interface information in a to-be-integrated real-time execution system. Therefore, the effect of efficiently configuring the RTE integration is achieved.

Description

Technical Field

[0001] The present disclosure belongs to the field of computer technology, and in particular relates to a real-time execution system integration method, device, equipment, medium and vehicle. Background Art

[0002] The current automotive industry's Automotive Open System Architecture (AUTOSAR) basic software development is based on mature tools on the market, and the use of these tools is operated through a graphical interface. In the process of AUTOSAR basic software development, the integration of the real-time executive system (RTE) is an important task. AUTOSAR RTE integration development is currently configured in the graphical interface of the Da Vinci tool "click-click" and then the ARXML configuration file is finally generated through the "click-click" configuration. Specifically, it is used to integrate the corresponding controls of RTE in the graphical interface of the Da Vinci tool, and then configure the RTE integration, and finally generate the ARXML (Autosar Extensible Markup Language) configuration file.

[0003] However, since RTE integration is a tedious, complex, and fixed-process task, the user needs to repeatedly click the corresponding controls of RTE integration in the graphical interface of the Da Vinci tool to configure the RTE integration, and then click the Generate ARXML configuration file control in the graphical interface of the Da Vinci tool to generate an ARXML configuration file configured with the RTE interface integration. This operation is cumbersome and the configuration efficiency of RTE integration is low. Summary of the invention

[0004] The purpose of the embodiments of the present application is to provide a real-time execution system integration method, device, equipment, medium and vehicle to achieve the effect of efficiently configuring RTE integration.

[0005] The technical solution of this application is as follows:

[0006] In a first aspect, a real-time execution system integration method is provided, the method comprising:

[0007] Obtain development request information for real-time execution systems;

[0008] Parsing the development request information using a pre-configured first script to obtain information of an interface to be developed in a real-time execution system to be integrated;

[0009] The interface information to be developed is configured in an ARXML configuration file in the DaVinci tool through a pre-configured second script to obtain a target ARXML configuration file, wherein the target ARXML configuration file has each interface information in the real-time execution system to be integrated.

[0010] In a second aspect, a real-time execution system integration device is provided, the device comprising:

[0011] An acquisition module, used to acquire development request information of a real-time execution system;

[0012] A parsing module, used to parse the development request information using a pre-configured first script to obtain information of an interface to be developed in the real-time execution system to be integrated;

[0013] The configuration module is used to configure the interface information to be developed in the ARXML configuration file in the Da Vinci tool through a pre-configured second script to obtain a target ARXML configuration file, wherein the target ARXML configuration file has the interface information in the real-time execution system to be integrated.

[0014] In a third aspect, an embodiment of the present application provides a real-time execution system integration device, which includes a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the real-time execution system integration method described in any one of the embodiments of the present application.

[0015] In a fourth aspect, an embodiment of the present application provides a computer-readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the real-time execution system integration method described in any of the embodiments of the present application are implemented.

[0016] In a fifth aspect, an embodiment of the present application provides a vehicle, the vehicle comprising at least one of the following:

[0017] The real-time execution system integration device as described in the first aspect;

[0018] The real-time execution system integration device as described in the second aspect;

[0019] A computer-readable storage medium as described in the third aspect.

[0020] The technical solution provided by the embodiments of the present application brings at least the following beneficial effects:

[0021] In an embodiment of the present application, the development request information of the acquired real-time execution system is parsed through a pre-configured first script to obtain the interface information to be developed in the real-time execution system to be integrated, and then the interface information to be developed is directly configured in the ARXML configuration file in the Da Vinci tool through a pre-configured second script to obtain the target ARXML configuration file. In this way, there is no need to perform multiple click operations in the Da Vinci tool to configure the interface to be developed and generate the ARXML configuration file. The operation is simple, which improves the configuration efficiency of RTE integration.

[0022] It should be understood that the foregoing general description and the following detailed description are exemplary and explanatory only and are not restrictive of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] The drawings herein are incorporated into the specification and constitute a part of the specification, illustrate embodiments consistent with the present application, and together with the specification are used to explain the principles of the present application, and do not constitute improper limitations on the present application.

[0024] Figure 1 It is a flowchart of a real-time execution system integration method provided by an embodiment of the first aspect of the present application;

[0025] Figure 2 It is a schematic diagram of the generation process of C language source code involved in the prior art;

[0026] Figure 3 It is a structural schematic diagram of a real-time execution system integration device provided by an embodiment of the second aspect of the present application;

[0027] Figure 4 It is a structural schematic diagram of an electronic device provided in an embodiment of the third aspect of the present application. DETAILED DESCRIPTION

[0028] In order to more clearly understand the above-mentioned objectives, features and advantages of the present disclosure, the scheme of the present disclosure will be further described below. It should be noted that the embodiments of the present disclosure and the features in the embodiments can be combined with each other without conflict.

[0029] In the following description, many specific details are set forth to facilitate a full understanding of the present disclosure, but the present disclosure may also be implemented in other ways different from those described herein; it is obvious that the embodiments in the specification are only part of the embodiments of the present disclosure, rather than all of the embodiments.

[0030] As described in the background technology section, there is a problem of low configuration efficiency of RTE integration in the prior art. In order to solve this problem, the embodiments of the present application provide a real-time execution system integration method, apparatus, equipment, medium and vehicle. The development request information of the acquired real-time execution system is parsed through a pre-configured first script to obtain the interface information to be developed in the real-time execution system to be integrated, and then the interface information to be developed is directly configured in the ARXML configuration file through a pre-configured second script to obtain the target ARXML configuration file. In this way, there is no need to perform multiple clicks in the Da Vinci tool to configure the interface to be developed and generate the ARXML configuration file. The operation is simple, which improves the configuration efficiency of the RTE integration.

[0031] The real-time execution system integration method provided by the embodiment of the present application is described in detail below through specific embodiments and their application scenarios in conjunction with the accompanying drawings.

[0032] Figure 1 It is a flow chart of a real-time execution system integration method provided in an embodiment of the present application. The execution subject of the real-time execution system integration method may be a server. It should be noted that the above execution subject does not constitute a limitation on the present application.

[0033] like Figure 1 As shown, the real-time execution system integration method provided by the embodiment of the present application may include steps 110 to 130.

[0034] Step 110: Acquire development request information of the real-time execution system.

[0035] The development request information may be a request for configuring a real-time execution system, and specifically may be a request for configuring an RTE interface.

[0036] In some embodiments of the present application, the above development request information may be sent by a client or obtained from a memory, which is not limited here. In addition, the development request information here may be an instruction of a development request or a document of a development request, which is not limited here.

[0037] Step 120: parse the development request information using a pre-configured first script to obtain information of interfaces to be developed in the real-time execution system to be integrated.

[0038] The first script may be a script written in advance by a user for parsing development request information. The script may be a script in Python or other languages, which is not limited here.

[0039] The interface information to be developed may be information of the interface to be developed, and may specifically include the interface to be developed, the running function corresponding to the interface to be developed, and the trigger information of the running function, etc. In some embodiments of the present application, when the development request information is a document, such as an Excel table, the development request information may include an interface to be developed field, a running function field corresponding to the interface to be developed, and a trigger information field of the running function of the interface to be developed.

[0040] When the development request information is a document, step 120 may specifically include:

[0041] The pre-configured first script is used to parse the interface to be developed field, the running function field and the trigger information field respectively, to obtain the interface to be developed, the running function and the trigger information corresponding to the running function.

[0042] The interface to be developed may be an interface to be developed. The running function may be a function that runs based on the interface to be developed. The trigger information may be information about when the running function is triggered to work.

[0043] In some embodiments of the present application, a first script can be pre-configured, and then the script can be used to parse the interface to be developed field, the running function field and the trigger information field to obtain the interface to be developed, the running function and the trigger information corresponding to the running function.

[0044] In an embodiment of the present application, by using a pre-configured first script to parse the interface to be developed field, the running function field and the trigger information field respectively, the interface to be developed, the running function of the interface to be developed and the trigger information corresponding to the running function can be accurately obtained, so as to accurately configure the RTE integration.

[0045] Step 130: Configure the interface information to be developed in the ARXML configuration file in the DaVinci tool through a pre-configured second script to obtain a target ARXML configuration file.

[0046] The second script may be a script written in advance by a user for configuring the interface information to be developed in an ARXML configuration file in the Da Vinci tool. The script may be a script in Python or other languages, which is not limited here.

[0047] The ARXML configuration file may be a configuration file in the ARXML format in the DaVinci tool, and the configuration file contains information of the RTE interface to be integrated.

[0048] The target ARXML configuration file may be a configuration file in ARXML format obtained after the configuration of the information to be developed is completed in the ARXML configuration file. The target ARXML configuration file may contain information of various interfaces in the real-time execution system to be integrated.

[0049] In some embodiments of the present application, the information of the interface to be developed can be directly configured in the ARXML configuration file in the Da Vinci tool through a pre-configured second script, without the need to perform multiple click operations in the Da Vinci tool to configure the interface to be developed and generate the ARXML configuration file. The operation is simple and the configuration efficiency of RTE integration is improved.

[0050] In some embodiments of the present application, the second script may include a second calling instruction for calling an ARXML configuration file. In order to further improve the configuration efficiency of RTE integration, step 130 may specifically include:

[0051] Run the second script;

[0052] Calling the ARXML configuration file based on a second calling instruction in the second script;

[0053] In response to the configuration operation of the interface information to be developed in the ARXML configuration file in the DaVinci tool, a target ARXML configuration file is obtained.

[0054] The second calling instruction may be an instruction in the second script for calling an ARXML configuration file in the DaVinci tool.

[0055] In some embodiments of the present application, an ARXML configuration file in the Da Vinci tool can be called by a second calling instruction in a pre-configured second script, and then the user can perform configuration operations on the interface information to be developed in the ARXML configuration file. The server responds to the user performing the configuration operations on the interface information to be developed in the ARXML configuration file, completes the configuration of the interface information to be developed, and generates a target ARXML configuration file.

[0056] It should be noted that, in some embodiments of the present application, the configuration of the interface information to be developed may include at least one of the following:

[0057] Add, delete and modify the interfaces to be developed corresponding to the interface information to be developed.

[0058] In some embodiments of the present application, when configuring the interface information to be developed in the ARXML configuration file, the existing interface information in the ARXML configuration file may be modified, new interface information may be added to the ARXML configuration file, or some interface information in the ARXML configuration file may be deleted. This is not limited here.

[0059] In an embodiment of the present application, the ARXML configuration file in the Da Vinci tool is called by the second calling instruction in the pre-configured second script, and then in response to the user performing a configuration operation on the interface information to be developed in the ARXML configuration file, the configuration of the interface information to be developed is completed, and the target ARXML configuration file is generated. In this way, there is no need to perform multiple click operations in the Da Vinci tool to configure the interface to be developed and generate the ARXML configuration file. The operation is simple, which improves the configuration efficiency of RTE integration.

[0060] In some embodiments of the present application, since the end user needs the C language source code, the code in the target ARXML configuration file cannot be embedded into the chip. Therefore, after generating the target ARXML configuration file, it is also necessary to generate the RTE integrated C language source code based on the target ARXML configuration file. Figure 2 Currently, when generating C language source code according to ARXML configuration file, it is generated by clicking the Generate C language source code control in ARXML configuration file in DaVinci tool kernel for many times. This method is cumbersome and the efficiency of C language source code generation integrated in RTE is low.

[0061] In order to solve the above problem, after step 130, the above method may further include:

[0062] Get the pre-configured groovy script;

[0063] The target ARXML configuration file is parsed using a groovy script to generate C language source code corresponding to the interface information to be developed in the real-time execution system to be integrated.

[0064] The groovy script is matched with the DaVinci tool, and the groovy script may be a file pre-written by a user for parsing a target ARXML configuration file.

[0065] In some embodiments of the present application, a pre-written groovy script can be used to parse the target ARXML configuration file, so that the groovy script can automatically and directly execute the operation of generating C language source code in the prior art to directly generate C language source code corresponding to the interface information to be developed in the real-time execution system to be integrated.

[0066] In an embodiment of the present application, the target ARXML configuration file is parsed by a pre-written groovy script, so that the groovy script can automatically and directly execute the operation of generating C language source code in the prior art to directly generate the C language source code corresponding to the interface information to be developed in the real-time execution system to be integrated. In this way, there is no need to click the Generate C language source code control in the ARXML configuration file multiple times in the Da Vinci tool kernel, and only the groovy script needs to be run. The operation is simple, which improves the efficiency of C language source code generation for RTE integration.

[0067] In some embodiments of the present application, the groovy script may have a first calling instruction for calling the application programming interface (API) of the core of the Da Vinci tool. The first calling instruction may be an instruction in the groovy script for calling the API of the core of the Da Vinci tool.

[0068] In order to further improve the efficiency of C language source code generation for RTE integration, the groovy script is used to parse the target ARXML configuration file to generate C language source code corresponding to the interface information to be developed in the real-time execution system to be integrated, which may specifically include:

[0069] Run the groovy script;

[0070] Calling the kernel API of the DaVinci tool based on the first call instruction in the groovy script;

[0071] The control API parses the target ARXML configuration file and generates C language source code corresponding to the interface information to be developed in the real-time execution system to be integrated.

[0072] In some embodiments of the present application, by running a groovy script, the API of the kernel of the Da Vinci tool can be called according to the first call instruction in the groovy script. Based on the API, the target ARXML configuration file can be automatically parsed to generate C language source code corresponding to the interface information to be developed in the real-time execution system to be integrated.

[0073] In an embodiment of the present application, by running a groovy script, the API of the kernel of the Da Vinci tool can be called according to the first call instruction in the groovy script. Based on the API, the target ARXML configuration file can be automatically parsed to generate C language source code corresponding to the interface information to be developed in the real-time execution system to be integrated. In this way, there is no need to click the Generate C language source code control in the ARXML configuration file in the Da Vinci tool kernel multiple times. It is only necessary to run the groovy script. The operation is simple, which improves the efficiency of C language source code generation for RTE integration.

[0074] In the embodiments of the present application, through the technical solution of the embodiments of the present application, the RTE integration work can be automatically performed in the ARXML configuration file directly through the script, replacing the developer's configuration on the Da Vinci graphical interface, realizing the automatic coverage of the RTE integration work, and at the same time, the Da Vinci API interface is called by the script to realize the automatic generation of C language source code.

[0075] It should be noted that the real-time execution system integration method provided in the embodiment of the present application may be executed by a real-time execution system integration device, or a control module in the real-time execution system integration device for executing the real-time execution system integration method.

[0076] Based on the same inventive concept as the above-mentioned real-time execution system integration method, the present application also provides a real-time execution system integration device. Figure 3 The real-time execution system integration device provided in the embodiment of the present application is described in detail.

[0077] Figure 3 The figure is a schematic diagram showing the structure of a real-time execution system integration device according to an exemplary embodiment.

[0078] like Figure 3 As shown, the real-time execution system integration device 300 may include:

[0079] An acquisition module 310 is used to acquire development request information of a real-time execution system;

[0080] The parsing module 320 is used to parse the development request information using a pre-configured first script to obtain the interface information to be developed in the real-time execution system to be integrated;

[0081] The configuration module 330 is used to configure the interface information to be developed in the ARXML configuration file in the DaVinci tool through a pre-configured second script to obtain a target ARXML configuration file, wherein the target ARXML configuration file has the interface information in the real-time execution system to be integrated.

[0082] In an embodiment of the present application, the development request information of the acquired real-time execution system is parsed by a pre-configured first script to obtain the interface information to be developed in the real-time execution system to be integrated, and then the interface information to be developed is directly configured in the ARXML configuration file by a pre-configured second script to obtain the target ARXML configuration file, so that there is no need to perform multiple click operations in the Da Vinci tool to configure the interface to be developed and generate the ARXML configuration file, which is simple to operate and improves the configuration efficiency of RTE integration. The real-time execution system integration method provided by the embodiment of the present application is described in detail below with reference to the accompanying drawings through specific embodiments and their application scenarios.

[0083] In some embodiments of the present application, the acquisition module 310 may also be used to: acquire a pre-configured groovy script;

[0084] The parsing module 320 may also be used to parse the target ARXML configuration file using the groovy script to generate C language source code corresponding to the interface information to be developed in the real-time execution system to be integrated.

[0085] In some embodiments of the present application, the groovy script has a first calling instruction for calling the application program interface API of the kernel of the Da Vinci tool; the parsing module 320 can be specifically used for:

[0086] Run the groovy script;

[0087] Calling the API of the kernel of the DaVinci tool based on the first calling instruction in the groovy script;

[0088] The API is controlled to parse the target ARXML configuration file to generate C language source code corresponding to the interface information to be developed in the real-time execution system to be integrated.

[0089] In some embodiments of the present application, the request information to be developed includes: an interface to be developed field, a running function field corresponding to the interface to be developed, and a trigger information field of the running function of the interface to be developed;

[0090] The parsing module 320 can be specifically used for:

[0091] The interface to be developed field, the running function field and the trigger information field are respectively parsed using a pre-configured first script to obtain the interface to be developed, the running function and the trigger information corresponding to the running function.

[0092] In some embodiments of the present application, the second script includes a second calling instruction of an ARXML configuration file; the configuration module 330 may be specifically used for:

[0093] Run the second script;

[0094] Calling the ARXML configuration file based on the second calling instruction in the second script;

[0095] In response to the configuration operation of the interface information to be developed in the ARXML configuration file in the Da Vinci tool, the configuration of the interface information to be developed is completed.

[0096] In some embodiments of the present application, the configuration module 330 may be specifically used to:

[0097] At least one of adding, deleting and modifying the interface to be developed corresponding to the interface to be developed information.

[0098] In some embodiments of the present application, both the first script and the second script are Python scripts.

[0099] The real-time execution system integration device provided in the embodiment of the present application can be used to execute the real-time execution system integration method provided in the above-mentioned method embodiments. Its implementation principle and technical effect are similar, and for the sake of brief introduction, they will not be repeated here.

[0100] Based on the same inventive concept, an embodiment of the present application also provides an electronic device.

[0101] Figure 4 Schematic diagram of the structure of an electronic device provided in an embodiment of the present application. Figure 4 As shown, the electronic device may include a processor 401 and a memory 402 storing computer programs or instructions.

[0102] Specifically, the processor 401 may include a central processing unit (CPU), or an application specific integrated circuit (ASIC), or may be configured to implement one or more integrated circuits of the embodiment of the present invention.

[0103] The memory 402 may include a large capacity memory for data or instructions. For example, but not limitation, the memory 402 may include a hard disk drive (HDD), a floppy disk drive, a flash memory, an optical disk, a magneto-optical disk, a magnetic tape, or a universal serial bus (USB) drive or a combination of two or more of these. In appropriate cases, the memory 402 may include a removable or non-removable (or fixed) medium. In appropriate cases, the memory 402 may be inside or outside the integrated gateway disaster recovery device. In a specific embodiment, the memory 402 is a non-volatile solid-state memory. The memory may include a read-only memory (ROM), a random access memory (RAM), a disk storage medium device, an optical storage medium device, a flash memory device, an electrical, optical or other physical / tangible memory storage device. Therefore, typically, the memory includes one or more tangible (non-transitory) computer-readable storage media (e.g., memory devices) encoded with software including computer-executable instructions, and when the software is executed (e.g., by one or more processors), it is operable to perform the operations described in the engine cooling system temperature prediction method provided in the above-mentioned embodiments.

[0104] The processor 401 reads and executes computer program instructions stored in the memory 402 to implement any one of the real-time execution system integration methods in the above embodiments.

[0105] In one example, the electronic device may further include a communication interface 403 and a bus 410. Figure 4 As shown, the processor 401, the memory 402, and the communication interface 403 are connected via a bus 410 and communicate with each other.

[0106] The communication interface 403 is mainly used to implement the communication between the modules, devices, units and / or devices in the embodiment of the present invention.

[0107] Bus 410 includes hardware, software or both, and the parts of electronic equipment are coupled to each other. For example, but not limitation, bus may include accelerated graphics port (AGP) or other graphics bus, enhanced industrial standard architecture (EISA) bus, front side bus (FSB), hypertransport (HT) interconnection, industrial standard architecture (ISA) bus, infinite bandwidth interconnection, low pin count (LPC) bus, memory bus, micro channel architecture (MCA) bus, peripheral component interconnection (PCI) bus, PCI-Express (PCI-X) bus, serial advanced technology attachment (SATA) bus, video electronics standard association local (VLB) bus or other suitable bus or two or more of these combinations. In appropriate cases, bus 410 may include one or more buses. Although the embodiment of the present invention describes and shows a specific bus, the present invention considers any suitable bus or interconnection.

[0108] The electronic device can execute the real-time execution system integration method in the embodiment of the present invention, thereby realizing Figure 1 Described in real-time execution system integration method.

[0109] In addition, in combination with the real-time execution system integration method in the above embodiments, the present invention can provide a readable storage medium to implement the real-time execution system integration method in the above embodiments. The readable storage medium stores program instructions, and when the program instructions are executed by the processor, any real-time execution system integration method in the above embodiments is implemented.

[0110] In addition, in combination with the real-time execution system integration method in the above embodiment, the present invention can provide a vehicle to implement the real-time execution system integration method. The vehicle includes the real-time execution system integration device, the real-time execution system integration equipment and the computer-readable storage medium in the above embodiment.

[0111] It should be clear that the present invention is not limited to the specific configuration and processing described above and shown in the figures. For the sake of simplicity, a detailed description of the known method is omitted here. In the above embodiments, several specific steps are described and shown as examples. However, the method process of the present invention is not limited to the specific steps described and shown, and those skilled in the art can make various changes, modifications and additions, or change the order between the steps after understanding the spirit of the present invention.

[0112] The functional blocks shown in the above-described block diagram can be implemented as hardware, software, firmware or a combination thereof. When implemented in hardware, it can be, for example, an electronic circuit, an application specific integrated circuit (ASIC), appropriate firmware, a plug-in, a function card, etc. When implemented in software, the elements of the present invention are programs or code segments that are used to perform the required tasks. The program or code segment can be stored in a machine-readable medium, or transmitted on a transmission medium or a communication link by a data signal carried in a carrier wave. "Machine-readable medium" can include any medium capable of storing or transmitting information. Examples of machine-readable media include electronic circuits, semiconductor memory devices, ROM, flash memory, erasable ROM (EROM), floppy disks, CD-ROMs, optical disks, hard disks, optical fiber media, radio frequency (RF) links, etc. The code segment can be downloaded via a computer network such as the Internet, an intranet, etc.

[0113] It should also be noted that the exemplary embodiments mentioned in the present invention describe some methods or systems based on a series of steps or devices. However, the present invention is not limited to the order of the above steps, that is, the steps can be performed in the order mentioned in the embodiments, or in a different order from the embodiments, or several steps can be performed simultaneously.

[0114] The above reference is according to the method of the embodiment of the present application, the flow chart of the device (system) and the computer program product and / or the block diagram described various aspects of the present application.It should be understood that each square box in the flow chart and / or the block diagram and the combination of each square box in the flow chart and / or the block diagram can be realized by computer program instructions.These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer or other programmable data processing device to produce a machine so that these instructions executed by the processor of the computer or other programmable data processing device enable the realization of the function / action specified in one or more square boxes of the flow chart and / or the block diagram.Such a processor can be but is not limited to a general-purpose processor, a special-purpose processor, a special application processor or a field programmable logic circuit.It can also be understood that each square box in the block diagram and / or the flow chart and the combination of the square boxes in the block diagram and / or the flow chart can also be realized by the dedicated hardware that performs the specified function or action, or can be realized by the combination of dedicated hardware and computer instructions.

[0115] It should be noted that, in this article, relational terms such as "first" and "second" are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the term "comprises" or any other variant thereof is intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the existence of other identical elements in the process, method, article or device including the elements.

[0116] The above is only a specific implementation of the present invention. Those skilled in the art can clearly understand that for the convenience and simplicity of description, the specific working process of the system, module and unit described above can refer to the corresponding process in the aforementioned method embodiment, and will not be repeated here. It should be understood that the protection scope of the present invention is not limited to this. Any technician familiar with the technical field can easily think of various equivalent modifications or replacements within the technical scope disclosed by the present invention, and these modifications or replacements should be covered within the protection scope of the present invention.

Claims

1. A real-time execution system integration method, characterized in that: The method comprises: Obtain development request information for real-time execution systems; Parsing the development request information using a pre-configured first script to obtain information of an interface to be developed in a real-time execution system to be integrated; The interface information to be developed is configured in an ARXML configuration file in the DaVinci tool through a pre-configured second script to obtain a target ARXML configuration file, wherein the target ARXML configuration file has each interface information in the real-time execution system to be integrated.

2. The method according to claim 1, characterized in that After obtaining the target ARXML configuration file, the method further includes: Get the pre-configured groovy script; The target ARXML configuration file is parsed using the groovy script to generate C language source code corresponding to the interface information to be developed in the real-time execution system to be integrated.

3. The method according to claim 2, characterized in that The groovy script has a first calling instruction for calling the application program interface API of the kernel of the Da Vinci tool; The method of parsing the target ARXML configuration file by using the groovy script to generate C language source code corresponding to the interface information to be developed in the real-time execution system to be integrated includes: Run the groovy script; Calling the API of the kernel of the DaVinci tool based on the first calling instruction in the groovy script; The API is controlled to parse the target ARXML configuration file to generate C language source code corresponding to the interface information to be developed in the real-time execution system to be integrated.

4. The method according to claim 1, characterized in that The request information to be developed includes: an interface to be developed field, a running function field corresponding to the interface to be developed, and a trigger information field of the running function of the interface to be developed; The using of the pre-configured first script to parse the development request information to obtain the interface information to be developed in the real-time execution system to be integrated includes: The interface to be developed field, the running function field and the trigger information field are respectively parsed using a pre-configured first script to obtain the interface to be developed, the running function and the trigger information corresponding to the running function.

5. The method according to claim 1, characterized in that The second script includes a second calling instruction of an ARXML configuration file; The method of configuring the interface information to be developed in the ARXML configuration file in the DaVinci tool by using the pre-configured second script to obtain the target ARXML configuration file includes: Run the second script; Calling the ARXML configuration file based on the second calling instruction in the second script; In response to the configuration operation of the interface information to be developed in the ARXML configuration file in the Da Vinci tool, a target ARXML configuration file is obtained.

6. The method according to any one of claims 1 to 5, characterized in that: The configuring the interface information to be developed includes: At least one of adding, deleting and modifying the interface to be developed corresponding to the interface to be developed information.

7. A real-time execution system integration device, characterized in that: The device comprises: An acquisition module, used to acquire development request information of a real-time execution system; A parsing module, used to parse the development request information using a pre-configured first script to obtain information of an interface to be developed in the real-time execution system to be integrated; The configuration module is used to configure the interface information to be developed in the ARXML configuration file in the Da Vinci tool through a pre-configured second script to obtain a target ARXML configuration file, wherein the target ARXML configuration file has the interface information in the real-time execution system to be integrated.

8. A real-time execution system integration processing device, characterized in that: The information locating device comprises: a processor and a memory storing computer program instructions; when the processor executes the computer program instructions, the real-time execution system integration method as described in any one of claims 1-7 is implemented.

9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer program instructions, and when the computer program instructions are executed by a processor, the real-time execution system integration method according to any one of claims 1 to 7 is implemented.

10. A vehicle, characterized in that: The vehicle comprises at least one of the following: The real-time execution system integration device as claimed in claim 7; The real-time execution system integration device as claimed in claim 8.

Images