DMS module processing method, vehicle and storage medium

Abstract

An embodiment of the present invention provides a processing method, vehicle, and storage medium for a DMS module. The method includes: a DMS conversion module sends the recognition result information obtained from an external interface dependency module to a DMS middleware module; the DMS middleware module generates a data message corresponding to at least one software function module based on the obtained vehicle information, project identification, and recognition result information; the DMS middleware module sends the data message to the software function module corresponding to the data message, so that when developing a new vehicle-mounted project, the project identification will be updated as the vehicle-mounted project is updated, and the staff only needs to add the interface implementation class corresponding to the updated project identification to enable the vehicle-mounted project to be successfully executed; the function of the DMS module is adjusted so that the DMS module can adapt to different vehicle-mounted projects and software function modules, reducing the development time of the driver monitoring system when developing new vehicle-mounted projects.

Description

Technical field

[0001] Embodiments of the present invention relate to the field of vehicle technology, and more particularly to a DMS module processing method, a vehicle, and a storage medium. [Background Technology]

[0002] Currently, most car models support a Driver Monitoring System (DMS). This system uses cameras to identify the driver's movements and provides corresponding prompts and interactions to ensure safe driving. However, DMS functionality is not yet fully adapted for development. When developing additional in-vehicle projects, the corresponding DMS code must be rewritten or refactored, resulting in significant development time. [Summary of the invention]

[0003] In view of this, embodiments of the present invention provide a DMS module processing method, a vehicle, and a storage medium to solve the problem of consuming a large amount of development time when developing new vehicle-mounted projects in the prior art.

[0004] In a first aspect, an embodiment of the present invention provides a method for processing a DMS module. The method is applied to a DMS module of a driver monitoring system, wherein the DMS module includes a DMS conversion module and a DMS middleware module. The method includes:

[0005] The DMS conversion module sends the recognition result information obtained from the external interface dependency module to the DMS middleware module;

[0006] The DMS middleware module generates a data message corresponding to at least one software function module based on the acquired vehicle information, project identification and the recognition result information;

[0007] The DMS middleware module sends the data message to the software function module corresponding to the data message.

[0008] In one possible implementation, the vehicle information includes first vehicle information and second vehicle information, and the DMS middleware module generates a data message corresponding to at least one software function module based on the acquired vehicle information, project identifier, and the identification result information, including:

[0009] The DMS middleware module determines whether the first vehicle information is preset information according to the first vehicle information;

[0010] If the DMS middleware module determines that the first vehicle information is preset information, it generates a data message corresponding to at least one software function module according to the second vehicle information, the project identifier and the recognition result information.

[0011] In one possible implementation, the DMS middleware module includes a functional middleware module corresponding to each software functional module, and the DMS middleware module generates a data message corresponding to at least one software functional module based on the second vehicle information, the project identifier, and the recognition result information, including:

[0012] The functional middleware module generates a dynamic class name according to the second vehicle information and the project identifier;

[0013] The functional middleware module generates a data message corresponding to a target software functional module according to the dynamic class name and the identification result information, and the target software functional module is a software functional module corresponding to the functional middleware module.

[0014] In a possible implementation, the functional middleware module generates a data message corresponding to the target software functional module according to the dynamic class name and the identification result information, including:

[0015] The functional middleware module generates a data message corresponding to the target software functional module according to the dynamic class name and the identification result information through a reflection function.

[0016] In a possible implementation, the second vehicle information includes a module name and a fixed suffix of a functional middleware module, and the dynamic class name includes the project identifier, the module name, and the fixed suffix.

[0017] In a second aspect, an embodiment of the present invention provides a DMS module, wherein the DMS module includes a DMS conversion module and a DMS middleware module;

[0018] The DMS conversion module is used to send the recognition result information obtained from the external interface dependency module to the DMS middleware module;

[0019] The DMS middleware module is used to generate a data message corresponding to at least one software function module based on the acquired vehicle information, project identification and the recognition result information; and send the data message to the software function module corresponding to the data message.

[0020] In a third aspect, an embodiment of the present invention provides a vehicle, comprising a driver monitoring system, the system comprising an external interface dependency module, a DMS module, and at least one software function module; the DMS module comprising a DMS conversion module and a DMS middleware module;

[0021] The external interface dependency module is used to send the recognition result information to the DMS conversion module;

[0022] The DMS conversion module is used to send the recognition result information to the DMS middleware module;

[0023] The DMS middleware module is configured to generate a data message corresponding to at least one software function module based on the acquired vehicle information, project identification, and the recognition result information; and to send the data message to the software function module corresponding to the data message;

[0024] The software function module is used to receive the data message.

[0025] In a possible implementation, the vehicle information includes first vehicle information and second vehicle information.

[0026] The DMS middleware module is specifically used to determine whether the first vehicle information is preset information based on the first vehicle information; if the first vehicle information is determined to be preset information, a data message corresponding to at least one software function module is generated based on the second vehicle information, the project identifier and the recognition result information.

[0027] In one possible implementation, the DMS middleware module includes a functional middleware module corresponding to each software functional module;

[0028] The functional middleware module is used to generate a dynamic class name based on the second vehicle information and the project identifier; generate a data message corresponding to the target software function module based on the dynamic class name and the identification result information, and the target software function module is the software function module corresponding to the functional middleware module.

[0029] In a fourth aspect, an embodiment of the present invention provides a storage medium, which includes a stored program, wherein when the program is running, the device where the storage medium is located is controlled to execute the processing method of the DMS module in the above-mentioned first aspect or any possible implementation of the first aspect.

[0030] In a technical solution for a DMS module processing method, vehicle, and storage medium provided in an embodiment of the present invention, the method is applied to the DMS module of a driver monitoring system, wherein the DMS module includes a DMS conversion module and a DMS middleware module; the DMS conversion module sends recognition result information obtained from an external interface dependency module to the DMS middleware module; the DMS middleware module generates a data message corresponding to at least one software function module based on the obtained vehicle information, project identification, and recognition result information; the DMS middleware module sends the data message to the software function module corresponding to the data message, thereby eliminating the need for staff to rewrite or reconstruct the code corresponding to the driver monitoring system when developing new in-vehicle projects; when developing new in-vehicle projects, the project identification will be updated as the in-vehicle project is updated, and staff only need to add an interface implementation class corresponding to the updated project identification to implement the execution of the new in-vehicle project; the functions of the DMS module are adjusted so that the DMS module can adapt to different in-vehicle projects and software function modules, reducing the development time of the driver monitoring system when developing new in-vehicle projects.

Brief Description of the Drawings

[0031] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the following briefly introduces the drawings required for use in the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0032] Figure 1 A flowchart of a processing method of a DMS module provided in an embodiment of the present invention;

[0033] Figure 2 A schematic diagram of a DMS framework provided in an embodiment of the present invention;

[0034] Figure 3 A flow chart of generating a data message provided by an embodiment of the present invention;

[0035] Figure 4 Another flow chart for generating a data message provided by an embodiment of the present invention;

[0036] Figure 5 A schematic structural diagram of a DMS module provided in an embodiment of the present invention;

[0037] Figure 6 A schematic structural diagram of a vehicle provided in an embodiment of the present invention. [Specific implementation method]

[0038] In order to better understand the technical solution of the present invention, the embodiments of the present invention are described in detail below with reference to the accompanying drawings.

[0039] It should be understood that the embodiments described are only a portion of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by persons of ordinary skill in the art without creative work are within the scope of protection of the present invention.

[0040] The terms used in the embodiments of the present invention are only for the purpose of describing specific embodiments and are not intended to limit the present invention. The singular forms "a", "an", "the" and "the" used in the embodiments of the present invention and the appended claims are also intended to include plural forms unless the context clearly indicates otherwise.

[0041] It should be understood that the term "and / or" as used herein is merely a description of the relationship between associated objects, indicating that three possible relationships exist. For example, "A and / or B" can represent: A exists alone, A and B exist simultaneously, or B exists alone. Furthermore, the character " / " in this document generally indicates that the associated objects are in an "or" relationship.

[0042] It should be understood that although the terms first, second, third, etc. may be used to describe numbers in embodiments of the present invention, these numbers should not be limited to these terms. These terms are merely used to distinguish numbers from each other. For example, a first number may also be referred to as a second number, and similarly, a second number may also be referred to as a first number without departing from the scope of embodiments of the present invention.

[0043] The word "if," as used herein, may be interpreted as "at the time of" or "when" or "in response to determining" or "in response to detecting," depending on the context. Similarly, the phrases "if it is determined" or "if (stated condition or event) is detected" may be interpreted as "when it is determined" or "in response to the determination" or "when detecting (stated condition or event)" or "in response to detecting (stated condition or event)," depending on the context.

[0044] Figure 1 A flowchart of a DMS module processing method provided by an embodiment of the present invention is applied to a DMS module of a driver monitoring system, wherein the DMS module includes a DMS conversion module and a DMS middleware module; Figure 1 As shown, the method includes:

[0045] Step 101: The DMS conversion module sends the recognition result information obtained from the external interface dependency module to the DMS middleware module.

[0046] In an embodiment of the present invention, the DMS module can be mounted on a vehicle, which also includes an external interface dependency module, the external interface dependency module includes an external dependency interface, and the external interface dependency module can interact with the DMS module through the external dependency interface. The external interface dependency module includes, but is not limited to, a camera recognition module, a microphone module, and the like. For example, when the external interface dependency module is a camera recognition module, the external dependency interface is a camera recognition interface, and the camera recognition module generates recognition result information when it recognizes that the driver has entered the vehicle. The recognition result information includes information that the driver has entered the vehicle; the camera recognition module sends the recognition result information to the DMS conversion module through the camera recognition interface. The DMS middleware module includes a functional middleware module corresponding to each software functional module, and step 101 includes: the DMS conversion module sends the recognition result information to at least one functional middleware module.

[0047] Figure 2 A schematic diagram of a DMS framework provided by an embodiment of the present invention is shown as follows: Figure 2 As shown, the external interface dependency module is connected to the DMS module, which is in turn connected to the software module. The external interface dependency module is used to generate recognition result information; the DMS module is used to encapsulate the recognition result information, generate at least one data message, and send the at least one data message to the software module; the software module is used to receive the at least one data message. The software module includes multiple software functional modules, including a voice app module, a personal center app module, and other system app modules. The DMS module includes a DMS conversion module, multiple functional middleware modules, and a project module. The multiple functional middleware modules include a voice middleware module, a personal center middleware module, and other functional middleware modules, each of which has a corresponding software functional module in the software module. Each functional middleware module includes a module interface, a module interface implementation factory, an interface implementation class module, and an integration module. The module interface implementation factory includes an annotation module and a reflective loading specified project interface implementation class module. The project module includes Project 1, which stores the identifier corresponding to the vehicle-mounted project. The project identifier can be updated based on updates to the vehicle-mounted project.

[0048] like Figure 2As shown, each functional middleware module includes a module interface, and each module interface encapsulates at least one function corresponding to the functional middleware module. For example, the voice middleware module corresponds to the voice broadcast function and the voice control function. The middleware module encapsulates the voice broadcast function and the voice control function into methods and writes them into the module interface of the voice middleware module. Different interface implementation classes can be encapsulated for different vehicle models. The module interface of the voice middleware module can be used to know the corresponding function of the voice middleware module, and each functional middleware module corresponds to one module interface, which facilitates the management and adaptation of the functional middleware module. For example, the recognition result information includes the driver's entry information; the DMS conversion module needs to send the driver's entry information to the voice middleware module and the personal center middleware module. The DMS conversion module sends the driver's entry information to the voice middleware module through the module interface of the voice middleware module; and sends the driver's entry information to the personal center middleware module through the module interface of the personal center middleware module.

[0049] Step 102: The DMS middleware module generates a data message corresponding to at least one software function module according to the acquired vehicle information, project identification, and recognition result information.

[0050] In the embodiment of the present invention, the DMS middleware module includes a project module, which stores a unique project identifier. The project identifiers stored in the project module may be different or the same in vehicles of different models. The vehicle information includes first vehicle information and second vehicle information; the first vehicle information includes the vehicle identifier, and the second vehicle information includes the module name and a fixed suffix. The module name refers to the module name of the functional middleware module, such as Figure 2 As shown, the module name of the voice middleware module is TTS.

[0051] The DMS middleware module includes a functional middleware module corresponding to each software functional module. Step 102 includes: the functional middleware module generates a data message corresponding to a target software functional module based on the acquired vehicle information, project identification, and recognition result information. The target software functional module is the software functional module corresponding to the functional middleware module.

[0052] like Figure 2 As shown, the DMS middleware module includes multiple functional middleware modules, each corresponding to a software functional module. Specifically, the voice middleware module corresponds to the voice app module, the personal center middleware module corresponds to the personal center app module, and other functional middleware modules correspond to other system app modules. If the functional middleware module is a voice middleware module, it generates data messages corresponding to the voice app module based on the acquired vehicle information, project identification, and recognition result information.

[0053] Step 103: The DMS middleware module sends the data message to the software function module corresponding to the data message.

[0054] In the embodiment of the present invention, Figure 2 As shown, the voice middleware module sends the data message to the voice app module, so that the voice app module generates reminder information based on the data message. The personal center middleware module sends the data message to the personal center app module, so that the personal center app module determines whether the driver is the car owner based on the data message.

[0055] An embodiment of the present invention provides a processing method for a DMS module, which is applied to the DMS module of a driver monitoring system. The DMS module includes a DMS conversion module and a DMS middleware module; the DMS conversion module sends the recognition result information obtained from the external interface dependency module to the DMS middleware module; the DMS middleware module generates a data message corresponding to at least one software function module based on the obtained vehicle information, project identification and recognition result information; the DMS middleware module sends the data message to the software function module corresponding to the data message, so that when developing a new vehicle-mounted project, the staff does not need to rewrite or reconstruct the code corresponding to the DMS module; and when developing a new vehicle-mounted project, the project identification will be updated as the vehicle-mounted project is updated, and the staff only needs to add an interface implementation class corresponding to the updated project identification to successfully trial implement the vehicle-mounted project; the function of the DMS module is adjusted so that the DMS module can adapt to different vehicle-mounted projects and software function modules, reducing the development time of the driver monitoring system when developing a new vehicle-mounted project.

[0056] In a possible implementation, step 103 includes: the functional middleware module sending the data message to the software functional module corresponding to the functional middleware module. Step 103 also includes: the software functional module receiving the data message; and executing the steps corresponding to the data message according to the data message.

[0057] In this embodiment of the present invention, the functional middleware module includes an integration module. Because multiple modules may exist and need to interact with multiple modules, the integration module needs to integrate the SDKs provided by the modules. This allows the software function modules corresponding to the functional middleware modules to provide corresponding SDK interfaces. By calling the interfaces within the SDK, data messages are delivered to the software function modules corresponding to the functional middleware modules.

[0058] Because different vehicle models correspond to different interface implementation classes, the steps performed by different vehicle models may be different. For example, the voice middleware module sends the driver's vehicle entry information to the voice mobile phone software (Application, App) module. The voice App module of vehicle model one generates a first reminder message based on the driver's vehicle entry information. The first reminder message is "Welcome to the car owner"; the voice App module of vehicle model two generates a second reminder message based on the driver's vehicle entry information. The second reminder message is "Please fasten your seat belt."

[0059] In a possible implementation, the vehicle information includes first vehicle information and second vehicle information. Figure 3 A flow chart of generating a data message provided by an embodiment of the present invention is as follows: Figure 3 As shown, step 102 may specifically include:

[0060] Step 1021 : The DMS middleware module determines whether the first vehicle information is preset information based on the first vehicle information. If so, step 1022 is executed; if not, step 1023 is executed.

[0061] In the embodiment of the present invention, the first vehicle information includes a vehicle identification, the preset information includes a preset identification, and the DMS middleware module includes a functional middleware module corresponding to each software functional module, and the functional middleware module determines whether the vehicle identification is a preset identification according to the vehicle identification.

[0062] Because multiple interface implementation classes include interface implementation classes corresponding to different vehicle models, and vehicle models correspond to vehicle identifiers, the vehicle identifier corresponding to the corresponding interface implementation class is defined as a preset identifier. To avoid situations where a corresponding implementation class does not exist for the vehicle model, the functional middleware module screens vehicles based on the vehicle identifier corresponding to the vehicle model. If it is determined that the vehicle identifier of the vehicle is not the preset identifier, then the multiple interface implementation classes do not include the interface implementation class corresponding to the vehicle, and the functional middleware module executes step 1023. If it is determined that the vehicle identifier of the vehicle is the preset identifier, then the multiple interface implementation classes include the interface implementation class corresponding to the vehicle, and the functional middleware module executes step 1022.

[0063] like Figure 2 As shown, the annotation module identifies the vehicle model based on the obtained vehicle identification. In the code corresponding to the annotation module, the judgment logic is written into the annotation-related judgment logic through annotations, making the code logic clearer. Using annotations can decouple parts of the code and also help to quickly locate the problem after it occurs.

[0064] Step 1022: The DMS middleware module generates a data message corresponding to at least one software function module according to the second vehicle information, the project identifier, and the recognition result information.

[0065] In the embodiment of the present invention, the second vehicle information includes a module name and a fixed suffix. The module name refers to the module name of the functional middleware module. The DMS middleware module includes a functional middleware module corresponding to each software functional module. Figure 4 Another flow chart for generating a data message provided by an embodiment of the present invention is as follows: Figure 4 As shown, step 1022 may specifically include:

[0066] Step 1022a: The functional middleware module generates a dynamic class name according to the second vehicle information and the project identifier.

[0067] In the embodiment of the present invention, the dynamic class name is obtained by dynamically assembling the project identifier, the module name of the functional middleware module and the fixed suffix. The dynamic class name includes the project identifier, the module name and the fixed suffix. Figure 2 As shown, when the functional middleware module is a voice middleware module, the reflection loading of the voice middleware module specifies that the implementation class module of the project is assembled into the dynamic class name of the implementation class through the project identifier, the module name of the functional middleware module, and the fixed suffix. For example, the project identifier is Saios, the module name of the voice middleware module is TTS, and the fixed suffix is ​​Impl; the dynamic class name of the voice middleware module of the Saios project is SaiosTTSImpl. Different interface implementation classes can be instantiated in vehicles of different models. For example, the reflection loading of the specified project implementation class module of vehicle type 1 outputs a dynamic class name of CarModule1TTSImpl; the reflection loading of the specified project implementation class module of vehicle type 2 outputs a dynamic class name of CarMoudle2TTSImpl.

[0068] Step 1022b: The functional middleware module generates a data message corresponding to the target software functional module according to the dynamic class name and the recognition result information.

[0069] In the embodiment of the present invention, the functional middleware module generates a data message corresponding to the target software functional module according to the dynamic class name and the identification result information through the reflection function. The target software functional module is the software functional module corresponding to the functional middleware module.

[0070] like Figure 2 As shown, the reflective loading module for a specified project interface implementation class uses Java's reflection function to instantiate an interface implementation class with the dynamic class name based on the dynamic class name and recognition result information, and then transmits the instantiated interface implementation class to the interface implementation class module. The interface implementation class module receives the instantiated interface implementation class, which includes specific functional code. The instantiated interface implementation class refers to a data message. The reflective loading module for a specified project implementation class encapsulates the recognition result information by reflecting on the instantiated interface implementation class and transmits the encapsulated result to the interface implementation class module.

[0071] Step 1023, end the process.

[0072] An embodiment of the present invention provides a method for processing a DMS module. This method is applied to the DMS module of a driver monitoring system. The DMS module includes a DMS conversion module and a DMS middleware module. The DMS conversion module transmits recognition result information obtained from an external interface dependency module to the DMS middleware module. The DMS middleware module generates a data message corresponding to at least one software function module based on the obtained vehicle information, project identifier, and recognition result information. The DMS middleware module transmits the data message to the software function module corresponding to the data message. Therefore, when developing a new vehicle-mounted project, staff do not need to rewrite or reconstruct the execution steps of the DMS module. Instead, they only need to add an interface implementation class corresponding to the updated project identifier to successfully test-implement the vehicle-mounted project. This adjusts the functionality of the DMS module, enabling it to adapt to different vehicle-mounted projects and shortening the development time of the DMS module.

[0073] Figure 5 A structural diagram of a DMS module provided in an embodiment of the present invention is shown as follows: Figure 5 As shown, the DMS module 3 includes a DMS conversion module 31 and a DMS middleware module 32;

[0074] The DMS conversion module 31 is used to send the recognition result information obtained from the external interface dependency module 4 to the DMS middleware module 32;

[0075] The DMS middleware module 32 is used to generate a data message corresponding to at least one software function module 5 according to the acquired vehicle information, project identification and recognition result information; and send the data message to the software function module 5 corresponding to the data message.

[0076] In an embodiment of the present invention, the vehicle information includes first vehicle information and second vehicle information. The DMS middleware module 32 is specifically used to determine whether it is preset information based on the first vehicle information; if the first vehicle information is determined to be preset information, a data message corresponding to at least one software function module 5 is generated based on the second vehicle information, the project identifier and the identification result information.

[0077] In an embodiment of the present invention, the DMS middleware module 32 includes a functional middleware module 321 corresponding to each software function module 5. The functional middleware module 321 is used to generate a dynamic class name based on the second vehicle information and the project identifier; and generate a data message corresponding to the target software function module 5 based on the dynamic class name and the identification result information. The target software function module is the software function module 5 corresponding to the functional middleware module 321.

[0078] In the embodiment of the present invention, the functional middleware module 321 is specifically configured to generate a data message corresponding to the target software functional module according to the dynamic class name and the identification result information through a reflection function.

[0079] In the embodiment of the present invention, the second vehicle information includes the module name and fixed suffix of the functional middleware module 321, and the dynamic class name includes the project identifier, the module name and the fixed suffix.

[0080] An embodiment of the present invention provides a DMS module, which includes a DMS conversion module and a DMS middleware module. The DMS conversion module sends recognition result information obtained from an external interface dependency module to the DMS middleware module. The DMS middleware module generates a data message corresponding to at least one software function module based on the obtained vehicle information, project identification, and recognition result information. The DMS middleware module sends the data message to the software function module corresponding to the data message. Therefore, when developing a new vehicle-mounted project, staff do not need to rewrite or reconstruct the execution steps of the DMS module. They only need to add an interface implementation class corresponding to the updated project identification to successfully test-implement the vehicle-mounted project. This adjusts the functions of the DMS module so that it can adapt to different vehicle-mounted projects, shortening the development time of the DMS module.

[0081] Figure 6 A schematic diagram of the structure of a vehicle provided in an embodiment of the present invention is shown in FIG. Figure 6 As shown, the vehicle 1 includes a driver monitoring system 2, which includes an external interface dependency module 4, a DMS module 3 and at least one software function module 5; the DMS module 3 includes a DMS conversion module 31 and a DMS middleware module 32;

[0082] The external interface dependency module 4 is used to send the recognition result information to the DMS conversion module; the DMS conversion module 31 is used to send the recognition result information to the DMS middleware module; the DMS middleware module 32 is used to generate a data message corresponding to at least one software function module 5 based on the acquired vehicle information, project identification and recognition result information; and send the data message to the software function module 5 corresponding to the data message; the software function module 5 is used to receive the data message.

[0083] In an embodiment of the present invention, the vehicle information includes first vehicle information and second vehicle information. The DMS middleware module 32 is specifically used to determine whether it is preset information based on the first vehicle information; if the first vehicle information is determined to be preset information, a data message corresponding to at least one software function module 5 is generated based on the second vehicle information, the project identifier and the identification result information.

[0084] In an embodiment of the present invention, the DMS middleware module 32 includes a functional middleware module corresponding to each software function module 5, and the functional middleware module is used to generate a dynamic class name based on the second vehicle information and the project identifier; and generate a data message corresponding to the target software function module 5 based on the dynamic class name and the recognition result information, and the target software function module is the software function module 5 corresponding to the functional middleware module.

[0085] In the embodiment of the present invention, the functional middleware module is specifically configured to generate a data message corresponding to the target software functional module according to the dynamic class name and the identification result information through a reflection function.

[0086] In the embodiment of the present invention, the second vehicle information includes the module name and fixed suffix of the functional middleware module, and the dynamic class name includes the project identifier, the module name and the fixed suffix.

[0087] An embodiment of the present invention provides a vehicle including a driver monitoring system, the driver monitoring system comprising an external interface dependency module, a DMS module, and at least one software function module; the DMS module comprising a DMS conversion module and a DMS middleware module; the DMS conversion module transmitting recognition result information obtained from the external interface dependency module to the DMS middleware module; the DMS middleware module generating a data message corresponding to at least one software function module based on the obtained vehicle information, project identification, and recognition result information; and the DMS middleware module transmitting the data message to the software function module corresponding to the data message. Thus, when developing a new vehicle-mounted project, staff do not need to rewrite or reconstruct the execution steps of the driver monitoring system; they only need to add an interface implementation class corresponding to the updated project identification to successfully test-implement the vehicle-mounted project. The DMS module's functions are adjusted to adapt to different vehicle-mounted projects, shortening the development time of the driver monitoring system.

[0088] An embodiment of the present invention provides a storage medium, which includes a stored program. When the program is running, the device where the storage medium is located is controlled to execute the steps of the embodiment of the processing method of the above-mentioned DMS module. For a specific description, please refer to the embodiment of the processing method of the above-mentioned DMS module.

[0089] The above description is only a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of the present invention should be included in the scope of protection of the present invention.

Claims

1. A processing method for a DMS module, characterized in that: The method is applied to a DMS module of a driver monitoring system, wherein the DMS module includes a DMS conversion module and a DMS middleware module; the method includes: The DMS conversion module sends the recognition result information obtained from the external interface dependency module to the DMS middleware module; The DMS middleware module generates a data message corresponding to at least one software function module based on the acquired vehicle information, project identification and the recognition result information; The DMS middleware module sends the data message to the software function module corresponding to the data message; The vehicle information includes first vehicle information and second vehicle information, the first vehicle information includes a vehicle identification, and the DMS middleware module generates a data message corresponding to at least one software function module based on the acquired vehicle information, the project identification, and the identification result information, including: The DMS middleware module determines whether the first vehicle information is preset information according to the first vehicle information; If the DMS middleware module determines that the first vehicle information is preset information, it generates a data message corresponding to at least one software function module according to the second vehicle information, the project identifier and the recognition result information; The DMS middleware module includes a functional middleware module corresponding to each software functional module, the second vehicle information includes a module name and a fixed suffix of the functional middleware module, and the DMS middleware module generates a data message corresponding to at least one software functional module based on the second vehicle information, the project identifier, and the recognition result information, including: The functional middleware module generates a dynamic class name according to the second vehicle information and the project identifier; The functional middleware module generates a data message corresponding to a target software functional module according to the dynamic class name and the identification result information, and the target software functional module is a software functional module corresponding to the functional middleware module.

2. The method according to claim 1, characterized in that The functional middleware module generates a data message corresponding to the target software functional module according to the dynamic class name and the identification result information, including: The functional middleware module generates a data message corresponding to the target software functional module according to the dynamic class name and the identification result information through a reflection function.

3. The method according to claim 1, characterized in that The dynamic class name includes the project identifier, the module name and the fixed suffix.

4. A DMS module, characterized in that: The DMS module includes a DMS conversion module and a DMS middleware module; The DMS conversion module is used to send the recognition result information obtained from the external interface dependency module to the DMS middleware module; The DMS middleware module is configured to generate a data message corresponding to at least one software function module based on the acquired vehicle information, project identifier, and the recognition result information; and send the data message to the software function module corresponding to the data message; The vehicle information includes first vehicle information and second vehicle information, wherein the first vehicle information includes a vehicle identification; The DMS middleware module is specifically configured to determine whether the first vehicle information is preset information based on the first vehicle information; if the first vehicle information is determined to be preset information, generate a data message corresponding to at least one software function module based on the second vehicle information, the project identifier, and the recognition result information; The DMS middleware module includes a functional middleware module corresponding to each software functional module, and the second vehicle information includes a module name and a fixed suffix of the functional middleware module; The functional middleware module is used to generate a dynamic class name based on the second vehicle information and the project identifier; generate a data message corresponding to the target software function module based on the dynamic class name and the identification result information, and the target software function module is the software function module corresponding to the functional middleware module.

5. A vehicle, characterized in that: The vehicle includes a driver monitoring system, the system including an external interface dependency module, a DMS module and at least one software function module; the DMS module includes a DMS conversion module and a DMS middleware module; The external interface dependency module is used to send the recognition result information to the DMS conversion module; The DMS conversion module is used to send the recognition result information to the DMS middleware module; The DMS middleware module is configured to generate a data message corresponding to at least one software function module based on the acquired vehicle information, project identification, and the recognition result information; Used to send the data message to the software function module corresponding to the data message; The software function module is used to receive the data message; The vehicle information includes first vehicle information and second vehicle information, wherein the first vehicle information includes a vehicle identification; The DMS middleware module is specifically configured to determine, based on the first vehicle information, whether the information is preset; if the first vehicle information is determined to be preset, generate a data message corresponding to at least one software function module based on the second vehicle information, the project identifier, and the recognition result information; The DMS middleware module includes a functional middleware module corresponding to each software functional module, and the second vehicle information includes a module name and a fixed suffix of the functional middleware module; The functional middleware module is used to generate a dynamic class name based on the second vehicle information and the project identifier; generate a data message corresponding to the target software function module based on the dynamic class name and the identification result information, and the target software function module is the software function module corresponding to the functional middleware module.

6. A storage medium, characterized in that The storage medium includes a stored program, wherein when the program is executed, the device where the storage medium is located is controlled to execute the processing method of the DMS module according to any one of claims 1 to 3.

Images