Agile development method and system for vehicle-mounted domain controller, electronic equipment and storage medium

Abstract

The invention discloses a vehicle-mounted domain controller agile development method and device, electronic equipment and a storage medium, and relates to the field of vehicle-mounted display, and the method comprises the steps: obtaining the information of the iteration state of a vehicle-mounted domain controller; the information of the iteration state of the vehicle-mounted domain controller comprises the steps that the state determined by the function of the vehicle-mounted domain controller serves as a node, and iteration is conducted from the current node to the next node version; wherein the vehicle-mounted domain controller function determination state of the current node is taken as a reference, and development iteration is carried out on the vehicle-mounted system for realizing the vehicle-mounted domain controller function; the vehicle-mounted system comprises a vehicle-mounted domain controller. By changing the brightness control logic and software design of the display screen, the brightness debugging efficiency of the display screen can be greatly improved, the brightness interaction between the display screen and the domain controller becomes simple and rapid, meanwhile, the brightness of different display screen products can be conveniently subjected to platform unified management, and the user experience is improved. The function dependence on the domain controller is reduced, and the functionality of the display screen is further improved.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of vehicle display, and in particular to a vehicle domain controller agile development method and system, an electronic device, and a storage medium. BACKGROUND

[0002] With the development of intelligent and networked vehicles, the speed of development iteration is getting faster and faster. For example, as a window for human-computer interaction, the display screen plays an increasingly important role. The design and development of display functions are diverse, and the display strategy of the display screen needs to be modified frequently during the development of the vehicle system.

[0003] In the vehicle system, the display function is actually realized by the cooperation of the vehicle domain controller and the display screen, but the software function of the domain controller itself is multiple, which leads to slow software version iteration, and therefore is not conducive to the rapid iteration of display functions.

[0004] Therefore, there is a need for a vehicle domain controller agile development scheme to reduce the defects of the vehicle domain controller, such as multiple software functions and slow software version iteration, which affect the rapid iteration of display functions in the vehicle system. SUMMARY

[0005] Therefore, the present application aims to provide a vehicle domain controller agile development method, a vehicle domain controller agile development system, an electronic device, and a storage medium, which at least solve the technical problem of how to realize the rapid iteration of display functions in the vehicle system, and solve the problem of how to version iterate under the same display function.

[0006] The present application provides the following scheme:

[0007] According to one aspect of the present application, a vehicle domain controller agile development method is provided, which comprises:

[0008] obtaining information of the iteration state of the vehicle domain controller;

[0009] The information of the iteration state of the vehicle domain controller comprises, with the state determined by the vehicle domain controller function as a node, version iteration from the current node to the next node;

[0010] wherein, with the state determined by the vehicle domain controller function of the current node as a reference, the vehicle system for realizing the vehicle domain controller function is developed and iterated;

[0011] wherein, the vehicle system comprises a vehicle domain controller.

[0012] Further, it further comprises:

[0013] obtaining information of the iteration state of the vehicle system;

[0014] The information of the iteration state of the vehicle-mounted system comprises, taking the state determined by the vehicle-mounted system function as a node, iteration from a current node to a next node version;

[0015] The vehicle-mounted system further comprises a display screen.

[0016] The vehicle-mounted system function determined state of the current node is taken as a reference to develop iteration of the vehicle-mounted domain controller or / and the display screen for realizing the vehicle-mounted system function.

[0017] Further, it further comprises:

[0018] The screen display function is defined according to the vehicle-mounted system function determined state.

[0019] The first version of the screen display function is defined according to the vehicle-mounted system function determined state of the current node as a reference.

[0020] The vehicle-mounted domain controller first function range and the display screen first function range are divided according to the vehicle-mounted system comprising the display screen and the vehicle-mounted domain controller and the first version of the screen display function.

[0021] The development progress of the vehicle-mounted domain controller and the display screen is evaluated according to the division of the vehicle-mounted domain controller first function range and the display screen first function range.

[0022] It is judged whether the development progress of the vehicle-mounted domain controller lags behind the development progress of the display screen and is greater than a preset progress threshold.

[0023] If yes, and greater than, the function in the vehicle-mounted domain controller first function range that can be developed and realized by the display screen is segmented according to the development progress and developed and realized by the display screen.

[0024] The second version of the screen display function is defined according to the segmentation of the function in the vehicle-mounted domain controller first function range that can be developed and realized by the display screen and the development and realization of the display screen.

[0025] The development of the display screen and the domain controller is promoted according to the definition of the second version of the screen display function.

[0026] Further, the definition of the second version of the screen display function comprises:

[0027] It is judged whether the development progress of the vehicle-mounted domain controller completes the function of the vehicle-mounted domain controller first function range.

[0028] If yes, the function in the vehicle-mounted domain controller first function range that is developed and realized by the display screen is closed or deleted.

[0029] The first version of the defined screen display function is realized according to the closing or deleting of the function in the vehicle-mounted domain controller first function range that is developed and realized by the display screen.

[0030] Further, further comprising:

[0031] determining whether the second version of the screen display function is earlier than the first version of the screen display function and greater than a preset time interval threshold value;

[0032] If yes, early, and greater than, determining whether the time node of the second version of the screen display function is earlier than a preset time node;

[0033] If yes, early, then according to the completion of the second version of the screen display function, the screen display function of the vehicle-mounted system is released.

[0034] Further, further comprising:

[0035] Obtaining target information of the vehicle-mounted system development iteration;

[0036] According to the target information of the vehicle-mounted system development iteration, planning the vehicle-mounted domain controller version iteration step;

[0037] According to the vehicle-mounted domain controller version iteration step, planning the display screen version iteration step;

[0038] According to the vehicle-mounted domain controller version iteration step, planning the display screen version iteration step includes, according to the synchronization of the development progress of the vehicle-mounted domain controller and the display screen, the resource balance, the version compatibility and the remote update elements, planning the version iteration step;

[0039] According to the planning version iteration step, setting the release cycle and the update cycle of the vehicle-mounted system.

[0040] Further, according to the completion of the second version of the screen display function, the screen display function of the vehicle-mounted system is released, which includes verifying the second version of the screen display function;

[0041] The verification includes: interface compatibility test, function stability test and performance stress test of the vehicle-mounted domain controller and the display screen.

[0042] According to the two aspects of the present application, a vehicle-mounted domain controller agile development device is provided, which comprises:

[0043] An iteration information module is used to obtain information of the iteration state of the vehicle-mounted domain controller;

[0044] The information of the iteration state of the vehicle-mounted domain controller includes the state determined by the function of the vehicle-mounted domain controller as a node, and the version iteration from the current node to the next node;

[0045] An iteration control module is used to determine the state of the function of the vehicle-mounted domain controller as a reference to the vehicle-mounted system development iteration for realizing the function of the vehicle-mounted domain controller;

[0046] The vehicle-mounted system comprises a vehicle-mounted domain controller.

[0047] According to the three aspects of the present application, an electronic device is provided, comprising a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory complete communication with each other through the communication bus.

[0048] The memory stores a computer program, and when the computer program is executed by the processor, the processor executes the steps of the agile development method of the vehicle-mounted domain controller.

[0049] According to the four aspects of the present application, a computer readable storage medium is provided, which stores a computer program executable by an electronic device, and when the computer program runs on the electronic device, the electronic device executes the steps of the agile development method of the vehicle-mounted domain controller.

[0050] Through the above scheme, the following beneficial technical effects are obtained:

[0051] The present application can quickly respond to the control information of other systems according to the existing stable state node without waiting for the release of the software of the domain controller if the development progress of the domain controller and the display screen is inconsistent in the development stage, thereby improving the test efficiency of the related components.

[0052] The present application can greatly improve the efficiency of brightness debugging of the display screen by changing the brightness control logic and software design of the display screen, so that the brightness interaction between the display screen and the domain controller becomes simple and fast, and the brightness of different display screen products can be conveniently managed on a platform, thereby reducing the functional dependence on the domain controller and further improving the functionality of the display screen. BRIEF DESCRIPTION OF DRAWINGS

[0053] Figure 1 is a flowchart of a vehicle-mounted domain controller agile development method provided by one or more embodiments of the present application.

[0054] Figure 2 is a structural diagram of a vehicle-mounted domain controller agile development device provided by one or more embodiments of the present application.

[0055] Figure 3 is a schematic diagram of a node strategy of a vehicle-mounted domain controller agile development of one specific embodiment of the present application.

[0056] Figure 4 is a schematic diagram of a vehicle-mounted domain controller software function of one specific embodiment of the present application.

[0057] Figure 5A schematic diagram of a function range division of a vehicle domain controller according to one embodiment of the present application.

[0058] Figure 6 An electronic device structure block diagram of a vehicle domain controller agile development method according to one or more embodiments of the present application. DETAILED DESCRIPTION

[0059] The technical solutions of the present application will be described clearly and completely below with reference to the drawings. Obviously, the described embodiments are part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative labor fall within the scope of protection of the present application.

[0060] Figure 1 A flow chart of a vehicle domain controller agile development method according to one or more embodiments of the present application.

[0061] As shown in Figure 1 the vehicle domain controller agile development method includes:

[0062] Step S1, obtaining information of an iteration state of the vehicle domain controller;

[0063] The information of the iteration state of the vehicle domain controller includes, taking a state determined by a vehicle domain controller function as a node, iterating from a current node to a next node version.

[0064] Step S2, taking the state determined by the vehicle domain controller function of the current node as a reference, developing and iterating a vehicle system for realizing the vehicle domain controller function;

[0065] The vehicle system includes the vehicle domain controller.

[0066] Specifically, the vehicle system includes the vehicle domain controller, and further includes other device modules cooperating with the vehicle domain controller. The vehicle domain controller and the other device modules jointly form the function of the vehicle system.

[0067] The development iteration of the vehicle system involves the joint development iteration of the vehicle domain controller and the other device modules, and then a new vehicle system version is formed.

[0068] For example, taking the state determined by the vehicle domain controller function of the current node as a reference, developing and iterating the vehicle system for realizing the vehicle domain controller function can only develop and iterate the other device modules, and then be compatible with the vehicle domain controller to form a new vehicle system version.

[0069] For example, the software function of the vehicle-mounted domain controller itself is multiple, resulting in slow software version iteration. The function of the new vehicle-mounted system version can be defined, and the development iteration of other device modules is attempted, that is, the new vehicle-mounted system version is implemented, and the development cycle is shortened.

[0070] In the embodiment, the vehicle-mounted system further includes:

[0071] The information of the iteration state of the vehicle-mounted system is obtained.

[0072] The information of the iteration state of the vehicle-mounted system includes, taking the state determined by the vehicle-mounted system function as a node, iteration from a current node to a next node version.

[0073] The vehicle-mounted system further includes a display screen.

[0074] The vehicle-mounted domain controller or / and the display screen for implementing the vehicle-mounted system function is developed and iterated based on the state determined by the vehicle-mounted system function of the current node.

[0075] Specifically, when the state determined by the vehicle-mounted system function is taken as a node and iteration from a current node to a next node version is performed, the vehicle-mounted domain controller or the display screen can be developed and iterated to implement the iteration of the vehicle-mounted system from the current node to the next node version, and the vehicle-mounted domain controller and the display screen can also be developed and iterated.

[0076] In one specific embodiment, a novel brightness control method of a display screen is disclosed. The brightness control logic of the display screen is integrated in the software of the domain controller. When the corresponding table of the brightness level and the brightness percentage (see Table 1) is changed, the software of the domain controller needs to be changed, and the debugging of the display screen needs to wait for the release of the software of the domain controller. Because the software function of the domain controller is multiple and the software version iteration is slow, it is not conducive to quickly change the brightness of the display screen (for example, the software function of the vehicle-mounted domain controller is shown in FIG. 1). Figure 4

[0077]

[0078] Table 1

[0079] The brightness control logic of the display screen is transferred from the software of the domain controller to the software of the display screen in the embodiment. The software of the domain controller only needs to provide the position lamp signal and the brightness level value, and the corresponding brightness percentage can be calculated by the software of the display screen. Finally, the display screen performs brightness display, as shown in FIG. 2. Figure 5 The function range of the vehicle-mounted domain controller is divided, as shown in FIG. 2. In the embodiment, the corresponding table of the brightness level and the brightness percentage is changed frequently. Therefore, the method can greatly improve the convenience and timeliness of debugging.

[0080] ​In the above embodiment, by changing the brightness control logic and software design of the display screen, the efficiency of the brightness debugging of the display screen can be greatly improved, the brightness interaction between the display screen and the domain controller becomes simple and fast, and the brightness of different display screen products can be conveniently platformized and uniformly managed, the function dependence on the domain controller is reduced, and the functionality of the display screen is further improved.

[0081] In the embodiment, the method further comprises:

[0082] defining the screen display function according to the vehicle system function determination state;

[0083] defining a first version of the screen display function according to the vehicle system function determination state of the current node as a reference;

[0084] dividing a first function range of the vehicle domain controller and a first function range of the display screen according to that the vehicle system comprises the display screen and the vehicle domain controller and the first version of the screen display function;

[0085] evaluating the development progress of the vehicle domain controller and the display screen according to the division of the first function range of the vehicle domain controller and the first function range of the display screen;

[0086] judging whether the development progress of the vehicle domain controller lags behind the development progress of the display screen and is greater than a preset progress threshold;

[0087] if yes, and greater than, then according to the development progress, dividing the function in the first function range of the vehicle domain controller that can be developed and implemented by the display screen, and developing and implementing the function by the display screen;

[0088] defining a second version of the screen display function according to the development and implementation of the function in the first function range of the vehicle domain controller by the display screen.

[0089] according to the definition of the second version of the screen display function, promoting the development of the display screen and the domain controller.

[0090] Specifically, the second version of the screen display function is consistent with the external display function of the first version of the screen display function, but the internal development iteration state of the vehicle domain controller and the display screen is not necessarily the same. A part of the development content that should be implemented by the vehicle domain controller is replaced by the development of the display screen, the screen display function is realized as a whole, and the development cycle is shortened.

[0091] In the embodiment, the definition of the second version of the screen display function comprises:

[0092] judging whether the development progress of the vehicle domain controller completes the function in the first function range of the vehicle domain controller;

[0093] if yes, completing, then closing or deleting the function in the first function range of the vehicle domain controller that is developed and implemented by the display screen;

[0094] According to the closing or deleting of the function developed by the display screen in the first function range of the vehicle domain controller, the first version of the defined screen display function is realized.

[0095] Specifically, when the vehicle domain controller develops the content of the first function range of the vehicle domain controller, the function of the display screen is no longer needed to replace the function of the vehicle domain controller, and then the related program modules in the display screen are closed or deleted, so that the display screen returns to the general version and ensures the compatibility.

[0096] In the embodiment, further comprising:

[0097] determining whether the second version of the screen display function is earlier than the first version of the screen display function and greater than a preset time interval threshold value;

[0098] If yes, and yes, then determining whether the time node of the second version of the screen display function is earlier than a preset time node;

[0099] If yes, and yes, then according to the completion of the second version of the screen display function, the screen display function of the vehicle system is released.

[0100] Specifically, since the vehicle system needs to be iterated quickly, waiting for the complete development of the domain controller will cause the display screen development to also need to wait for a long time, wasting development resources and prolonging the development cycle of the vehicle system.

[0101] The second version of the screen display function can be realized first to release the product in advance and strive for the market share. Since the second version of the screen display function is consistent with the first version of the screen display function in external function, and is internally developed by the display screen to replace a part of the functions that should be developed by the vehicle domain controller, the iteration cycle is shortened as a whole.

[0102] When the domain controller is developed, the vehicle domain controller program can be refreshed through the remote OTA mode, the function modules of the display screen are closed, and the vehicle system is in the first version of the screen display function.

[0103] In the embodiment, further comprising:

[0104] obtaining target information of the development iteration of the vehicle system;

[0105] According to the target information of the development iteration of the vehicle system, the version iteration step of the vehicle domain controller is planned;

[0106] According to the version iteration step of the vehicle domain controller, the version iteration step of the display screen is planned;

[0107] According to the vehicle domain controller version iteration step, the display screen version iteration step includes planning version iteration steps according to the synchronization of the development progress of the vehicle domain controller and the display screen, resource balancing, version compatibility, and remote update elements.

[0108] According to the planning version iteration step, the release cycle and the update cycle of the vehicle system are set.

[0109] Specifically, in one specific embodiment, as shown in the node strategy of the agile development of the vehicle domain controller, Figure 3 the domain controller is at different development nodes, and different functions are divided to the display screen development corresponding to different development nodes. For example, at the third node, the brightness adjustment is taken as the iteration content, the domain controller side outputs the instruction data of the brightness level, and the display screen develops the content of the brightness adjustment. With the progress of the development progress, the iteration of the vehicle domain controller is constantly improved, and the display screen can close the corresponding function module, so that the display screen gradually returns to the general state. During this period, the vehicle system composed of the vehicle domain controller and the display screen can be continuously produced. When the development of the vehicle domain controller is completed, the display screen is restored to the ordinary display screen through the OTA refresh program strategy, and the universality of the display screen as a spare part is ensured.

[0110] In this embodiment, according to the realization of the second version of the screen display function, the screen display function of the vehicle system is released, which includes verifying the second version of the screen display function.

[0111] The verification includes interface compatibility testing, function stability testing, and performance stress testing of the vehicle domain controller and the display screen.

[0112] Specifically, since the vehicle domain controller has some functions implemented by the display screen, interactive testing of communication stability is required. For example, interface compatibility testing, function stability testing, and performance stress testing.

[0113] Figure 2 is a structural diagram of a vehicle domain controller agile development device provided by one or more embodiments of the present application.

[0114] As shown in the node strategy of the agile development of the vehicle domain controller, Figure 2 the agile development device of the vehicle domain controller includes an iteration information module and an iteration control module.

[0115] The iteration information module is configured to obtain information of the iteration state of the vehicle domain controller.

[0116] The information of the iteration state of the vehicle domain controller includes a state determined by the function of the vehicle domain controller as a node, and version iteration from a current node to a next node.

[0117] An iterative control module, used to iterate the development of the vehicle system that implements the vehicle domain controller function based on the vehicle domain controller function determination state of the current node;

[0118] Among them, the vehicle-mounted system includes a vehicle-mounted domain controller.

[0119] It is worth noting that although this system only discloses the iterative information module and the iterative control module, it does not mean that this device is limited to the above-mentioned basic functional modules. Rather, what the present invention wants to express is that, based on the above-mentioned basic functional modules, those skilled in the art can arbitrarily add one or more functional modules in combination with the existing technology to form an infinite number of embodiments or technical solutions. In other words, this system is open rather than closed. Just because this embodiment only discloses individual basic functional modules, it cannot be considered that the scope of protection of the claims of the present invention is limited to the above-mentioned basic functional modules.

[0120] In another specific embodiment, by acquiring a position light signal and a brightness level signal sent by a domain controller, the position light signal includes a light control state bit and a scene type identifier;

[0121] Analyze the current driving scene based on the position light signal and obtain the brightness strategy parameters corresponding to the scene;

[0122] Brightness strategy parameters include scene minimum brightness, scene maximum brightness and correction coefficient;

[0123] Based on the brightness level signal and scene strategy parameters, the basic brightness percentage is calculated by a nonlinear mapping algorithm using a gamma correction model: Basic percentage = = ; Where γ is the gamma value, which is dynamically adjusted according to the scene type;

[0124] Correcting the base percentage according to the correction coefficient corresponding to the scene to obtain a corrected brightness percentage;

[0125] Perform safety threshold verification on the corrected brightness percentage, including global minimum / maximum brightness and scene-specific minimum / maximum brightness;

[0126] Output the brightness percentage that passes the verification to the display module to drive the backlight system.

[0127] Further, including:

[0128] The light control status bit includes the on / off status of the width indicator light, the scene identification includes day mode, night mode, tunnel mode and rainy day mode, and the scene analysis step further includes:

[0129] Establishing a mapping table between position light status and scene classification, wherein the mapping table includes light control state combination, scene identification and brightness strategy priority;

[0130] When multiple scene identifications are received, the highest priority scene strategy parameter is selected according to preset priority rules.

[0131] Further, the nighttime city mode correction coefficient is 0.8-0.9, which is used to reduce the brightness to reduce glare;

[0132] The tunnel strong light mode correction coefficient is 1.1-1.3, which is used to increase the brightness to enhance the contrast;

[0133] The rainy day / foggy day mode correction coefficient is 0.85-0.95, which is used to reduce the brightness to reduce glass reflection.

[0134] Further, the safety threshold verification step includes:

[0135] The global safety boundary limit includes: the minimum brightness percentage ≥5% and the maximum brightness percentage ≤100%;

[0136] The scene-specific threshold limit includes: the maximum brightness percentage of the nighttime parking mode ≤30% and the minimum brightness percentage of the direct sunlight scene ≥60%;

[0137] Change rate control: when the difference between the current brightness percentage and the last frame is <±3%, skip adjustment; when the difference is ≥5%, enable linear interpolation gradual transition.

[0138] The brightness strategy parameters are stored in a readable and writable configuration file or a non-volatile memory, and the configuration file includes:

[0139] Scene ID, corresponding light control state combination and scene identification;

[0140] Scene minimum brightness, maximum brightness, gamma value and correction coefficient;

[0141] Supporting remote updating of the configuration file through vehicle-mounted Ethernet or CAN bus.

[0142] Further, the non-linear mapping algorithm is adapted to the hardware characteristics, specifically including:

[0143] Identifying the display screen hardware ID, calling the gamma value and maximum brightness limit matched with the hardware;

[0144] According to the PWM response curve of the backlight driving module, the calculated brightness percentage is converted into hardware driving parameters.

[0145] Further, the correction of the base percentage according to the correction coefficient corresponding to the scene further includes:

[0146] Obtaining the ambient light intensity change amount and the vehicle speed coefficient,

[0147] According to the environmental light intensity change amount and the vehicle speed coefficient, the corrected brightness percentage is twice corrected.

[0148] In another embodiment, a vehicle-mounted display screen brightness control system is also provided, comprising:

[0149] The signal receiving module is configured to acquire a position light signal and a brightness level sent by the domain controller.

[0150] The scene analysis module is configured to analyze a driving scene according to the position light signal and call corresponding brightness strategy parameters.

[0151] The algorithm calculation module comprises a non-linear mapping unit and a correction unit, and is configured to correct the calculated basic percentage to generate a corrected brightness percentage.

[0152] The safety verification module is configured to perform threshold verification and change rate control on the corrected brightness percentage.

[0153] The drive output module is configured to convert the brightness percentage that passes the verification into a backlight drive signal.

[0154] Specifically, by changing the brightness control logic and software design of the display screen, the efficiency of the brightness debugging of the display screen can be greatly improved, the brightness interaction between the display screen and the domain controller becomes simple and fast, and the brightness of different display screen products can be conveniently platformized and uniformly managed, the function dependence on the domain controller is reduced, and the functionality of the display screen is further improved.

[0155] Figure 6 The electronic device structure block diagram of the agile development method of the vehicle-mounted domain controller provided by one or more embodiments of the application.

[0156] As Figure 6 shown, the application provides an electronic device, comprising a processor, a communication interface, a memory and a communication bus, wherein the processor, the communication interface and the memory complete mutual communication through the communication bus.

[0157] The memory stores a computer program, and when the computer program is executed by the processor, the processor executes the steps of the agile development method of the vehicle-mounted domain controller.

[0158] The application also provides a computer readable storage medium storing a computer program executable by an electronic device, and when the computer program runs on the electronic device, the electronic device executes the steps of the agile development method of the vehicle-mounted domain controller.

[0159] For the method embodiments, the description is made in a series of action combinations for simplicity and clarity, but those skilled in the art should know that the present application is not limited to the action sequence described, because according to the present application, certain steps can be performed in other sequences or at the same time. In addition, those skilled in the art should know that the embodiments described in the specification are all preferred embodiments, and the actions involved are not necessarily essential to the present application.

[0160] From the above description of the embodiments, those skilled in the art can clearly understand that the present application can be implemented by means of software and the necessary general hardware platform. Based on such understanding, the technical solutions of the present application can be embodied in the form of a software product, which can be stored in a storage medium, such as a ROM / RAM, a magnetic disk, an optical disk, etc., and includes a number of instructions for causing a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in the various embodiments or some parts of the embodiments of the present application.

[0161] Finally, it should be noted that: the above embodiments are only used to illustrate the technical solutions of the present application, and not to limit them; although the present application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that: it can still modify the technical solutions recorded in the foregoing embodiments, or make equivalent replacement for part or all of the technical features; and these modifications or replacements do not make the essence of the corresponding technical solutions deviate from the scope of the technical solutions of the embodiments of the present application.

Claims

1. An agile development method for a vehicle-mounted domain controller, characterized in that: The agile development method for the vehicle domain controller includes: Get the information about the iteration status of the vehicle domain controller; The information of the iteration status of the vehicle domain controller includes, taking the status determined by the vehicle domain controller function as a node, iterating from the current node to the next node version; Among them, based on the current node's vehicle domain controller function determination status, the vehicle system that realizes the vehicle domain controller function is developed and iterated; Wherein, the vehicle-mounted system includes a vehicle-mounted domain controller.

2. The agile development method for a vehicle-mounted domain controller according to claim 1, characterized in that: Also includes: Get information about the iteration status of the vehicle system; The information of the in-vehicle system iteration status includes taking the status determined by the in-vehicle system function as a node and iterating from the current node to the next node version; Wherein, the vehicle-mounted system further includes a display screen; Among them, based on the status of the vehicle-mounted system function determination of the current node, the vehicle-mounted domain controller and / or display screen that realizes the vehicle-mounted system function is developed and iterated.

3. The agile development method for a vehicle-mounted domain controller according to claim 2, characterized in that: Also includes: Determine the status based on the vehicle system functions and define the screen display functions; Defining a first version of the screen display function based on the state determined by the vehicle system function of the current node; According to the vehicle system including a display screen and a vehicle domain controller, and the first version defining the screen display function, the first functional scope of the vehicle domain controller and the first functional scope of the display screen are divided; Evaluate the development progress of the vehicle domain controller and display based on the division of the first functional scope of the vehicle domain controller and the first functional scope of the display; Determine whether the vehicle domain controller development progress lags behind the display screen development progress and is greater than the preset progress threshold; If yes, and greater than, then according to the development progress, the functions that can be realized by the display screen development in the first functional range of the vehicle domain controller are divided and realized by the display screen development; According to the functions that can be developed and implemented by the display screen in the first functional range of the divided vehicle domain controller, the second version of the display function is defined by developing and implementing the display screen. Based on the definition of the second version of the screen display function, the development of the display screen and domain controller is promoted.

4. The agile development method for a vehicle-mounted domain controller according to claim 3, characterized in that: The second version of defining the screen display function includes: Determine whether the development progress of the vehicle domain controller has completed the functions of the first functional scope of the vehicle domain controller; If completed, the functions implemented by the display screen development in the first functional scope of the split vehicle domain controller are closed or deleted; By closing or deleting the functions implemented by the display screen development in the first functional scope of the split vehicle domain controller, a first version of the defined screen display function is implemented.

5. The agile development method for a vehicle-mounted domain controller according to claim 4, characterized in that: Also includes: Determine whether the second version of the screen display function is implemented earlier than the first version of the screen display function and the time interval is greater than a preset threshold; If , is earlier than , and is greater than , then determine whether the time node for implementing the second version of the screen display function is earlier than the preset time node; If earlier than, then according to the completion of the second version of the screen display function, the screen display function of the vehicle system will be released.

6. The agile development method for a vehicle-mounted domain controller according to claim 5, characterized in that: Also includes: Obtain target information for vehicle system development iterations; Plan the iteration steps for the vehicle domain controller version based on the target information for vehicle system development iteration; Plan the display screen version iteration steps based on the vehicle domain controller version iteration steps; The step of planning the display screen version iteration according to the vehicle domain controller version iteration step includes planning the version iteration step based on the synchronization of the vehicle domain controller and display screen development progress, resource balance, version compatibility, and remote updateability. Set the release cycle and update cycle of the vehicle system according to the planned version iteration steps.

7. The agile development method for a vehicle-mounted domain controller according to claim 3, characterized in that: The releasing of the on-vehicle system's on-screen display function according to the completion of the second version of the on-screen display function includes verifying the second version of the on-screen display function; Verification includes: interface compatibility testing between the vehicle-mounted domain controller and the display screen, functional stability testing, and performance stress testing.

8. An agile development device for a vehicle-mounted domain controller, characterized in that: The vehicle-mounted domain controller agile development device includes: Iteration information module, used to obtain information about the iteration status of the vehicle domain controller; The information of the iteration status of the vehicle domain controller includes, taking the status determined by the vehicle domain controller function as a node, iterating from the current node to the next node version; An iterative control module, used to iterate the development of the vehicle system that implements the vehicle domain controller function based on the vehicle domain controller function determination state of the current node; Wherein, the vehicle-mounted system includes a vehicle-mounted domain controller.

9. An electronic device, characterized in that: include: A processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other via the communication bus; A computer program is stored in the memory, and when the computer program is executed by the processor, the processor executes the steps of the agile development method for a vehicle domain controller according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that It stores a computer program that can be executed by an electronic device. When the computer program runs on the electronic device, the electronic device executes the steps of the agile development method for a vehicle-mounted domain controller according to any one of claims 1 to 7.

Images