Software automatic configuration method, system, device and medium based on shelter access process

Abstract

The application relates to the technical field of emergency equipment, and discloses a software automatic configuration method, system, device and medium based on a shelter access process, which comprises the following steps: in response to a vehicle-mounted access request of a functional shelter, obtaining shelter configuration parameters of the functional shelter; according to a pre-established software configuration rule, generating software configuration content meeting the functional execution logic of the functional shelter according to the shelter configuration parameters, and synchronously updating the software configuration content to a vehicle-mounted configuration running environment to obtain a vehicle-mounted functional shelter after the functional shelter is accessed; and in the case that the vehicle-mounted functional shelter after the functional shelter is accessed is removed, removing the software configuration content of the functional shelter from the configuration running environment. The method improves the configuration correctness and configuration efficiency in the scene where the shelter is frequently replaced.

Description

Technical Field

[0001] This invention relates to the field of emergency equipment technology, and in particular to a software-automated configuration method, system, device, and medium based on the modular shelter access process. Background Technology

[0002] In the field of emergency equipment management, it involves the identification and management of access to different functional modular units (power generation, drainage, communication, monitoring, etc.).

[0003] In existing methods for managing mobile shelter access, the software configuration is usually manually modified through manual configuration or conventional software loading to achieve functional adaptation. This method requires manual intervention or adjustment, resulting in low configuration efficiency. Furthermore, in scenarios where mobile shelters are frequently changed, configuration errors are prone to occur, thereby affecting the operating efficiency and reliability of the equipment. Summary of the Invention

[0004] In view of this, the present invention provides a software automatic configuration method, system, device and medium based on the mobile cabin access process, which solves the technical problems of low configuration efficiency due to manual intervention or manual adjustment of configuration during mobile cabin access management, and the easy occurrence of configuration errors in scenarios where mobile cabins are frequently changed, thereby affecting the operating efficiency and reliability of equipment.

[0005] The first aspect of this invention provides a software-automated configuration method based on the mobile cabin access process, comprising:

[0006] In response to the vehicle access request of the functional modular unit, the modular unit configuration parameters are obtained.

[0007] According to the pre-established software configuration rules, software configuration content that satisfies the functional execution logic of the functional modular unit is generated based on the modular unit configuration parameters, and the software configuration content is synchronously updated to the vehicle's configuration and operation environment to obtain the vehicle after accessing the functional modular unit.

[0008] If the vehicle removes the functional module after it has been accessed, the software configuration content of the functional module is removed from the configuration operating environment.

[0009] In one embodiment, the step of obtaining the cabin configuration parameters of the functional cabin in response to the vehicle access request of the functional cabin includes:

[0010] The physical connection signal of the vehicle when it connects to the functional cabin is obtained, and the cabin type of the functional cabin is determined based on the physical connection signal.

[0011] A preset communication protocol corresponding to the type of modular shelter is determined, a communication connection is established with the functional modular shelter based on the preset communication protocol, and the modular shelter configuration parameters of the functional modular shelter are obtained.

[0012] In one embodiment, the modular cabin configuration parameters include cabin type, rated operating parameters, and equipment specification information;

[0013] The step of generating software configuration content that satisfies the functional execution logic of the functional modular container based on the pre-established software configuration rules and the modular container configuration parameters includes:

[0014] Extract multiple parameter category identifiers and parameter value features corresponding to each parameter category identifier from the configuration parameters of the mobile cabin. Perform format standardization combination on each parameter category identifier and its corresponding parameter value features to generate a standardized feature set.

[0015] Each standardized feature combination in the standardized feature set is matched one by one with the rule items in the software configuration rules to determine at least one target rule item for each standardized feature combination.

[0016] Based on at least one of the target rule items, the corresponding standardized feature combination is configured and mapped to obtain the software configuration sub-content corresponding to each standardized feature combination;

[0017] Based on the functional execution logic of the functional cabin, the sequential relationship between each software configuration sub-content is determined, and the software configuration sub-content is arranged in a structured manner based on the sequential relationship to obtain the software configuration content.

[0018] In one embodiment, the step of configuring and mapping the corresponding standardized feature combinations according to at least one of the target rule items to obtain the software configuration sub-content corresponding to each standardized feature combination includes:

[0019] Obtain the functional category identifier of each target rule item, and divide each target rule item into functional categories according to the functional category identifier to obtain the set of target rule items under each functional category;

[0020] For each set of target rule items under each functional category, the standardized feature combination is configured and mapped according to the software configuration items and mapping range corresponding to the target rule items, so as to obtain the software configuration sub-content corresponding to each standardized feature combination.

[0021] In one embodiment, the step of determining the sequential relationship between the various software configuration sub-contents based on the functional execution logic of the functional cabin, and structuring the various software configuration sub-contents based on the sequential relationship to obtain the software configuration content includes:

[0022] Based on the functional execution logic of the aforementioned functional modular unit, the functional execution order and data transmission order are determined.

[0023] Based on the function execution order and the data transmission order, the software configuration sub-contents are rearranged to obtain the first software configuration sequence and the second software configuration sequence.

[0024] Based on the direct dependency between pre-function triggering and post-data transmission, the first software configuration sequence and the second software configuration sequence are cross-compared to determine the mapping and matching relationship between pre-configuration sub-content and post-configuration sub-content; wherein, the pre-configuration sub-content is the software configuration sub-content in the first software configuration sequence, and the post-configuration sub-content is the software configuration sub-content in the second software configuration sequence that has a direct dependency relationship with the pre-configuration sub-content;

[0025] Based on the mapping matching relationship, the pre-configuration sub-content and the post-configuration sub-content are bound to obtain a software configuration mapping pair;

[0026] Based on the functional execution order among the software configuration mapping pairs, the software configuration mapping pairs are sorted to obtain the software configuration content.

[0027] In one embodiment, the step of synchronously updating the software configuration content to the vehicle's configuration and operating environment to obtain the vehicle after accessing the functional cabin further includes:

[0028] Determine whether the functional module participates in collaborative operations with other functional modules;

[0029] If it is determined that the functional module does not participate in collaborative operations with other functional modules, the software configuration content is loaded in real time through the configuration operating environment of the vehicle after accessing the functional module, and based on the preset operating organization relationship, the vehicle application that matches the software configuration content is matched and the matched vehicle application is enabled; wherein, the operating organization relationship includes the mapping relationship between the software configuration content and the vehicle application.

[0030] If it is determined that the functional module participates in collaborative operations with other functional modules, then the cross-module operation organization relationship is determined by combining the collaborative operation status and the software configuration content, and the vehicle-mounted application of each functional module participating in collaborative operations is activated and started according to the cross-module operation organization relationship.

[0031] In one embodiment, the step of removing the software configuration content of the functional module from the configuration operating environment when the vehicle removes the functional module after it has been accessed includes:

[0032] If the vehicle removes the functional module after it has been connected to the functional module, the cross-module operation organization relationship and operation organization relationship corresponding to the functional module are terminated, the software configuration content of the functional module is removed, and the vehicle application corresponding to the functional module is deactivated.

[0033] Secondly, the present invention also provides a software-automated configuration system based on the modular hospital access process, comprising:

[0034] The parameter acquisition module is used to obtain the cabin configuration parameters of the functional cabin in response to the vehicle access request of the functional cabin.

[0035] The configuration access module is used to generate software configuration content that satisfies the functional execution logic of the functional modular cabin according to the pre-established software configuration rules and the configuration parameters of the modular cabin, and to synchronously update the software configuration content to the configuration and operation environment of the vehicle to obtain the vehicle after accessing the functional modular cabin;

[0036] A configuration removal module is used to remove the software configuration content of the functional module from the configuration operating environment when the vehicle removes the functional module after it has been accessed.

[0037] Thirdly, the present invention also provides an electronic device, the electronic device including a memory and a processor, the memory storing a computer program, the computer program being executed by the processor causing the processor to perform the steps of the software automatic configuration method based on the mobile cabin access process as described in the first aspect.

[0038] Fourthly, the present invention also provides a computer-readable storage medium having a computer program stored thereon, which, when executed, implements the steps of the software automatic configuration method based on the modular access process as described in the first aspect.

[0039] As can be seen from the above technical solutions, the present invention has the following advantages:

[0040] By responding to the vehicle access request of the functional module, the system obtains the module's configuration parameters, providing a clear parameter basis for subsequent configuration processing. Furthermore, based on pre-established software configuration rules, it generates software configuration content that satisfies the functional module's execution logic according to the module's configuration parameters, ensuring that the software configuration content matches the functional module's execution logic. This software configuration content is then synchronously updated to the vehicle's configuration runtime environment, enabling the accessed functional module to form a corresponding software configuration state within the vehicle. This, in turn, drives the vehicle to respond to the module's functional requirements in real time. Even when the vehicle detects the removal of a functional module after its access, the system removes the functional module's software configuration content from the configuration runtime environment, ensuring consistency between the software configuration content and the currently accessed functional module's state. Based on this, the entire technical solution achieves automatic creation and removal of software configurations during the functional module access and removal process, thereby improving configuration accuracy and efficiency in scenarios with frequent module changes. Attached Figure Description

[0041] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0042] Figure 1 This is a schematic diagram of the structure of a vehicle control system provided in an embodiment of the present invention;

[0043] Figure 2 A flowchart illustrating an automatic software configuration method based on the access process of a mobile cabin, provided in an embodiment of the present invention;

[0044] Figure 3 This is a schematic diagram illustrating the implementation process of step S1 provided in an embodiment of the present invention;

[0045] Figure 4 This is a schematic diagram illustrating the implementation process of step S2 provided in an embodiment of the present invention;

[0046] Figure 5 A schematic diagram of the structure of a software automatic configuration system based on the access process of a mobile cabin provided in an embodiment of the present invention;

[0047] Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of the present invention. Detailed Implementation

[0048] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0049] In the field of vehicle-mounted equipment management, it is typically necessary to identify and manage the access of different functional modules to enable them to participate in the operation of the vehicle platform. However, in related technologies, module function adaptation usually relies on manual configuration or conventional software loading methods. That is, after the functional module is connected to the chassis, the operator manually selects the corresponding equipment type and loads the corresponding software configuration in the vehicle-mounted control terminal. When different functional modules are replaced or reinstalled between vehicles, the vehicle-mounted control terminal struggles to automatically identify the currently connected module type, thus requiring manual reconfiguration, increasing operational steps and extending equipment preparation time. Furthermore, in emergency missions or on-site operating environments, functional modules may need to be frequently changed. Manual configuration requires setting each configuration item individually, which is prone to errors or omissions, resulting in inconsistencies between the final loaded software configuration and the actual connected functional module. This affects monitoring, data acquisition, and equipment control processing during operation.

[0050] To address the aforementioned issues, this application proposes an automatic software configuration method based on the modular cabin access process. First, in response to the vehicle access request from the functional modular cabin, the modular cabin configuration parameters are obtained, providing a clear parameter basis for subsequent configuration processing. Second, according to pre-established software configuration rules, software configuration content that satisfies the functional cabin's functional execution logic is generated based on the modular cabin configuration parameters, and this software configuration content is synchronously updated to the vehicle's configuration runtime environment, resulting in the vehicle after the functional cabin access, thus enabling the accessed functional cabin to form a corresponding software configuration state within the vehicle. Third, if the vehicle detects the removal of the functional cabin after access, the software configuration content of the functional cabin is removed from the configuration runtime environment, ensuring that the software configuration content in the configuration runtime environment remains consistent with the currently accessed functional cabin state. Based on this, the entire technical solution achieves automatic establishment and automatic cancellation of software configuration during the functional cabin access and removal process, thereby improving configuration accuracy and efficiency in scenarios with frequent modular cabin changes.

[0051] The software automatic configuration method based on the modular shelter access process provided in this invention can be applied to, for example... Figure 1The vehicle control system shown includes a functional cabin, a chassis, and a vehicle control terminal. The functional cabin communicates with the chassis via a wireless communication network, and the functional cabin communicates with the vehicle control terminal via a wireless communication network.

[0052] In practical applications, firstly, when the vehicle control terminal detects that a functional module has been connected to the chassis corresponding to the vehicle control terminal, it responds to the functional module's vehicle access request and obtains the module's configuration parameters, thus providing a clear parameter basis for subsequent configuration processing. Secondly, based on pre-established software configuration rules, the vehicle control terminal generates software configuration content that satisfies the functional module's functional execution logic according to the module configuration parameters, and synchronously updates the software configuration content to the configuration management module's configuration runtime environment, thus obtaining the vehicle after the functional module has been connected. Thirdly, when the vehicle control terminal detects that the functional module has been removed after being connected, it removes the functional module's software configuration content from the configuration runtime environment, thereby ensuring that the software configuration content in the configuration management module remains consistent with the current state of the functional module on the chassis.

[0053] The vehicle-mounted control terminal is a terminal device, which refers to a device that corresponds to a server and provides local services to operators. This terminal device includes, but is not limited to, vehicle-mounted industrial control terminals, vehicle-mounted operation consoles, vehicle-mounted industrial computers, and control devices integrated into the vehicle control system.

[0054] In one embodiment, such as Figure 2 As shown, this application embodiment provides a software automatic configuration method based on the modular shelter access process, which is applied to... Figure 1 Taking the vehicle-mounted control terminal as an example, the explanation includes the following steps S1 to S3. Wherein:

[0055] Step S1: In response to the vehicle access request from the functional module, obtain the module configuration parameters.

[0056] For example, the vehicle access request is initiated by the vehicle control terminal detecting whether a functional module is connected to the chassis. The vehicle control terminal refers to a control device located in the driver's cab, used to manage and control the functional module installed on the chassis; for example, it may be an onboard computer or a vehicle control host in the driver's cab. When a functional module is installed on the chassis, it establishes a connection with the chassis through an interface. The vehicle control terminal then detects changes in the connection status of this interface to identify the installation of a new functional module and issues a vehicle access request.

[0057] Based on this, the vehicle-mounted control terminal acquires the configuration parameters of the functional modular unit. These configuration parameters describe the basic configuration of the functional modular unit within the vehicle, including but not limited to the modular unit type, rated operating parameters, and equipment specifications. The modular unit type information includes whether it is a power generation modular unit or a drainage modular unit; the rated operating parameters include rated power, rated voltage, or rated drainage capacity; and the rated operating parameters also include fuel type, engine displacement, and curb dimensions.

[0058] Step S2: Based on the pre-established software configuration rules, generate software configuration content that satisfies the functional execution logic of the functional modular unit according to the modular unit configuration parameters, and synchronously update the software configuration content to the vehicle's configuration and operation environment to obtain the vehicle's configuration after accessing the functional modular unit.

[0059] For example, the software configuration rules represent the pre-defined parameter correspondence, which are used to explain the software configuration content that should be generated in the vehicle control terminal for different cabin configuration parameters (the software configuration rules are pre-set). For example, when the cabin type identified in the cabin configuration parameters is a power generation cabin, software configuration content related to the operation and management of power generation equipment (such as generator operation status monitoring configuration, power generation data acquisition configuration, and power generation equipment start-stop control configuration) is generated accordingly.

[0060] When the container type identified in the container configuration parameters is a flood drainage container, corresponding software configuration content related to the operation and control of drainage equipment (such as drainage pump operation status monitoring configuration, drainage flow data acquisition configuration, and drainage equipment start-stop control configuration) will be generated.

[0061] In the specific processing, the vehicle-mounted control terminal extracts the cabin type, rated operating parameters and equipment specifications information contained in the cabin configuration parameters, and then converts the above information into software configuration content corresponding to the current functional cabin according to the configuration rules.

[0062] For example, the monitoring configuration content is formed by determining the equipment objects to be monitored based on the container type information and equipment specifications. For instance, the generator operation status monitoring item is determined based on the generator type information and generator equipment specifications, and the drainage pump operation status monitoring item is determined based on the drainage container type information and drainage equipment specifications. The data collection configuration content is formed by determining the operating data to be collected based on the container type information and rated operating parameters. For instance, the power generation data collection item is determined based on the rated power parameters of the generator, and the drainage flow data collection item is determined based on the rated drainage volume parameters of the drainage container. The control configuration content is formed by determining the equipment operation control parameters based on the equipment specifications and rated operating parameters. For instance, the generator start-stop control parameters are determined based on the generator equipment specifications and rated power parameters, and the drainage pump start-stop control parameters are determined based on the drainage equipment specifications and rated drainage volume parameters.

[0063] Furthermore, the vehicle-mounted control terminal writes the software configuration results to the configuration management module, which represents the configuration and operation environment inside the vehicle-mounted control terminal used to record and run the software configuration results corresponding to the current functional cabin, such as the software configuration table or software configuration file set in the vehicle-mounted control terminal.

[0064] Step S3: If the vehicle-mounted removal function module is detected after the access function module is detected, remove the software configuration content of the function module from the configuration operation environment.

[0065] For example, the vehicle control terminal continuously detects whether a functional module is connected to the chassis. When it detects that the physical interface previously connected to the functional module has changed from connected to disconnected, it is determined that the functional module has been removed from the chassis. At this time, the vehicle control terminal needs to process the software configuration results previously generated for the functional module accordingly.

[0066] Specifically, the vehicle control terminal searches for the software configuration content corresponding to the functional cabin in the configuration management module and removes the software configuration content, that is, deletes the software configuration content corresponding to the functional cabin from the configuration management module, so that the configuration management module no longer records the software configuration content corresponding to the functional cabin, and ensures that the software configuration content recorded in the configuration management module is always consistent with the status of the functional cabin actually connected to the current chassis.

[0067] It should be noted that, in response to the vehicle access request of the functional module, this application embodiment obtains the module configuration parameters, thus providing a clear parameter basis for subsequent configuration processing. Furthermore, based on pre-established software configuration rules, it generates software configuration content that satisfies the functional module's functional execution logic according to the module configuration parameters, ensuring that the software configuration content matches the functional module's functional execution logic. The software configuration content is then synchronously updated to the vehicle's configuration runtime environment, enabling the accessed functional module to form a corresponding software configuration state within the vehicle. This drives the vehicle to respond to the module's functional requirements in real time. Additionally, if the vehicle detects the removal of the functional module after its access, the software configuration content of the functional module is removed from the configuration runtime environment, ensuring consistency between the software configuration content and the currently accessed functional module's state. Based on this, the entire technical solution achieves automatic creation and removal of software configuration during the functional module access and removal process, thereby improving configuration accuracy and efficiency in scenarios with frequent module changes.

[0068] In some embodiments, such as Figure 3 As shown, in step S1, in response to the vehicle access request from the functional module, the module configuration parameters are obtained, including:

[0069] Step S101: Obtain the physical connection signal when the vehicle access functional cabin is used, and determine the cabin type of the functional cabin based on the physical connection signal.

[0070] Step S102: Determine the preset communication protocol corresponding to the type of modular shelter, establish a communication connection with the functional modular shelter based on the preset communication protocol, and obtain the modular shelter configuration parameters of the functional modular shelter.

[0071] Among them, the physical connection signal is generated when the functional module is installed on the chassis. The functional module establishes a connection with the chassis through the physical interface connected to the chassis. The vehicle control terminal detects the change in the access status of the interface to identify the completion of the installation of a new functional module, thereby generating an electrical or digital signal to characterize the functional module access event. This signal not only reflects the on / off status of the interface, but also includes the interface location, interface type, etc.

[0072] Preferably, the vehicle-mounted control terminal can determine the type of the functional cabin based on the physical connection signal. Since different types of functional cabins are connected to the chassis through different forms of interfaces, the type of the functional cabin can be determined based on the type of interface accessed (e.g., the number and location of the interfaces).

[0073] For example, when the physical connection signal is detected that three interfaces on the chassis used for installing the functional cabin are simultaneously in the connected state and the three interfaces are located on the left and middle areas of the chassis respectively, it is determined to be a first type of functional cabin; when the physical connection signal is detected that two interfaces on the chassis are simultaneously in the connected state and both interfaces are located in the rear area of ​​the chassis, it is determined to be a second type of functional cabin.

[0074] After determining the type of functional module, the corresponding preset communication protocol is matched in the communication protocol library according to the type of functional module. The communication protocol library contains communication protocols that are mapped one-to-one with each type of functional module. For example, the first type of functional module corresponds to the CAN-FD protocol, and the second type of functional module corresponds to the Modbus TCP protocol, etc.

[0075] The vehicle-mounted control terminal establishes a communication connection with the functional cabin according to the connection method corresponding to the preset communication protocol, so that the cabin configuration parameters in the functional cabin can be read by the vehicle-mounted control terminal. For example, the vehicle-mounted control terminal sends a connection establishment request to the functional cabin according to the determined functional cabin type, and completes the connection confirmation through handshake interaction with the functional cabin, thereby establishing a wireless communication connection to read the cabin configuration parameters stored in the functional cabin.

[0076] In one embodiment, the modular shelter configuration parameters include the modular shelter type, rated operating parameters, and equipment specification information; based on this, such as Figure 4As shown, in step S2, according to the pre-established software configuration rules, software configuration content that satisfies the functional execution logic of the functional modular container is generated based on the modular container configuration parameters, including:

[0077] Step S201: Extract multiple parameter category identifiers and parameter value features corresponding to each parameter category identifier from the configuration parameters of the mobile cabin. Perform format standardization combination on each parameter category identifier and its corresponding parameter value features to generate a standardized feature set.

[0078] Among them, the parameter category identifier is a semantic classification of parameter categories. For example, the parameter category identifier for container type information is container type, the parameter category identifier for rated operating parameters is rated power, rated displacement, etc., and the parameter category identifier for equipment specification information is engine displacement, equipment size, etc.; the parameter value characteristics are standardized values ​​or tuples obtained after numerical extraction, unit stripping and structural mapping.

[0079] Because the configuration parameters of the modular shelter are raw information containing text, units, and other messy elements, such as "power generation modular shelter," "50kW," and "4m×2m×2m," the vehicle-mounted control terminal cannot use them directly. It is necessary to filter out useless information, standardize the format, and extract concise, standardized feature values ​​to facilitate subsequent matching rules. Therefore, this application also standardizes the format of the extracted parameter category identifiers and their corresponding parameter value features, removing text and units from the parameter value features and retaining only the core numbers / numbers, converting them into a simple format that can be recognized by a computer.

[0080] For example, the vehicle-mounted control terminal classifies the configuration parameters of each cabin according to the parameter category identifier to distinguish different categories of parameters such as cabin type, rated operating parameters and equipment specification information. Then, it reads the parameter value corresponding to each parameter category identifier as the parameter value feature and converts the parameter value feature into information that can reflect the current functional cabin characteristics.

[0081] For example, for the container type information identified based on the parameter category identifier, its parameter values ​​are converted into corresponding type numbers to form container type features. For instance, when the parameter category identifier is "Container Type" and the parameter value is "Power Generation Container," container type feature value 01 is generated; when the parameter value is "Flood Drainage Container," container type feature value 02 is generated. As another example, for the rated operating parameters identified based on the parameter category identifier, the numerical part of the parameter value is used as the operating capacity feature. For instance, when the parameter category identifier is "Rated Power" and the parameter value is 50kW, the rated operating capacity feature is generated. The operational capability feature value is 50. When the parameter category is rated displacement and the parameter value is 2000 m³ / h, the operational capability feature value is 2000. For example, for equipment specification information identified by the parameter category, the structural dimensions or specification values ​​in the parameter values ​​are extracted as equipment specification features. For instance, when the parameter category is engine displacement and the parameter value is 3.0L, the equipment specification feature value is 3.0; when the parameter category is equipment size and the parameter value is 4m×2m×2m, the equipment specification feature value is (4,2,2). After completing the above processing, the onboard control terminal organizes the various feature information extracted from the configuration parameters of each cabin to obtain multiple standardized feature combinations, thus forming a standardized feature set corresponding to the current functional cabin.

[0082] Step S202: Match each standardized feature combination in the standardized feature set with the rule items in the software configuration rules one by one to determine at least one target rule item for each standardized feature combination.

[0083] The software configuration rules specify the rule items corresponding to standardized feature combinations. Each rule item represents a specific rule unit within the configuration rules; that is, each rule item contains specific parameter characteristics and the corresponding software configuration content when those characteristics are met. For example, a rule item might stipulate that when a standardized feature combination contains a specific type of modular shelter feature value and a specific operational capability feature value, monitoring configuration content, data acquisition configuration content, or equipment control configuration content related to the operation of that type of functional modular shelter should be generated. Each standardized feature combination in the standardized feature set is matched against each rule item in the software configuration rules to find all matching target rule items.

[0084] For example, the vehicle control terminal reads each rule item in the configuration rules and compares the parameter feature conditions contained in the rule item with each standardized feature combination in the standardized feature set. When each standardized feature combination in the standardized feature set satisfies the parameter feature conditions set by a certain rule item, the rule item is determined as the target rule item. For example, if the parameter feature condition of a certain rule item is "modular cabin type 02 and operational capability feature value ≥ 1500", and the standardized feature combination is "modular cabin type feature value 02, operational capability feature value 2000", then the rule item is matched by the standardized feature combination and becomes the target rule item. Here, the target rule item represents the rule item that is successfully matched under the parameter feature conditions of the current functional modular cabin and used to generate software configuration content.

[0085] Step S203: Configure and map the corresponding standardized feature combination according to at least one target rule item to obtain the software configuration sub-content corresponding to each standardized feature combination.

[0086] After determining the target rule item, the vehicle control terminal performs configuration mapping processing on the standardized feature combination according to the software configuration content specified in the target rule item. That is, the relevant parameter feature values ​​in the standardized feature combination are converted into corresponding configuration expression content according to the configuration expression method set in the target rule item, so as to obtain the standardized feature combination.

[0087] For example, when the standardized feature combination includes type feature value 02 and drainage capacity feature value 2000, these parameter feature values ​​are mapped to a high-intensity configuration according to the target rule item, and mapping items related to the high-frequency monitoring of drainage equipment operation status and the high-frequency collection of drainage flow data are generated respectively. When the standardized feature combination includes type feature value 02 and drainage capacity feature value 1000, these parameter feature values ​​are mapped to a medium-intensity configuration according to the target rule item, and mapping items related to the periodic monitoring of drainage equipment operation status and the periodic collection of drainage flow data are generated respectively. When the standardized feature combination includes type feature value 02 and drainage capacity feature value 500, these parameter feature values ​​are mapped to a low-intensity configuration according to the target rule item, and mapping items related to the interval monitoring of drainage equipment operation status and the interval collection of drainage flow data are generated respectively. In this way, the information originally used to describe the features of the functional cabin can be transformed into mapping items that reflect the software configuration content of the vehicle control terminal, and a corresponding mapping item is formed, which serves as the software configuration sub-content.

[0088] Step S204: Based on the functional execution logic of the functional module, determine the sequential relationship between the sub-contents of each software configuration, and arrange the sub-contents of each software configuration in a structured manner based on the sequential relationship to obtain the software configuration content.

[0089] The function execution logic constrains the execution of each software configuration sub-content according to the logical order of actual device operation, ensuring that the function execution order and data transmission order of each software configuration sub-content are accurate and smooth. In other words, the function execution logic defines the sequential relationship between each software configuration sub-content and uses this sequential relationship to structure and arrange each software configuration sub-content, so that the final software configuration content reflects both the temporal dependency of function execution and satisfies the interface constraints of data flow transmission.

[0090] For example, each software configuration sub-content corresponds to a different mapping item. Therefore, the software configuration sub-content needs to be organized in a predetermined order so that different types of software configuration sub-content can be arranged according to a unified software configuration structure to form the final software configuration content. For example, monitoring-related mapping items are located at the beginning of the software configuration structure, data acquisition-related mapping items are located after monitoring-related mapping items, and device control-related mapping items are located after data acquisition-related mapping items. This allows the device operating status to be monitored and identified first, then operating data is collected according to the monitored object, and after obtaining the operating data, the corresponding device control processing is executed, thus ensuring that the software configuration content is consistent with the device operating processing flow.

[0091] In this embodiment, the specific process of generating software configuration content that satisfies the functional execution logic of a functional modular cabin based on pre-established software configuration rules and modular cabin configuration parameters realizes the transformation process of modular cabin configuration parameters from feature extraction and rule matching to sequential configuration generation, so that the software configuration content corresponding to the functional modular cabin can be generated according to the predetermined execution logic structure, thereby ensuring the accurate application of the software configuration content.

[0092] In some embodiments, step S203, configuring and mapping the corresponding standardized feature combinations according to at least one target rule item to obtain the software configuration sub-content corresponding to each standardized feature combination, includes: obtaining the function category identifier of each target rule item; dividing each target rule item into function categories according to the function category identifier to obtain a set of target rule items under each function category; and configuring and mapping each standardized feature combination according to the software configuration item and mapping range corresponding to each target rule item set under each function category to obtain the software configuration sub-content corresponding to each standardized feature combination.

[0093] The functional category identifier is used to characterize the functional attributes of the target rule item in the software configuration, such as monitoring, collection, or control. Target rule items under the same functional category share the same configuration logic framework. Therefore, the mixed target rule items are classified according to the functional category identifier, so that rule items with the same functional attribute are processed in a centralized manner. This not only improves mapping efficiency, but also ensures that the configuration sub-contents of the same type maintain internal consistency in structure and semantics.

[0094] For example, the software configuration content corresponding to each target rule item involves multiple content categories, and the functional categories involved in different target rule items differ. For instance, some rule items involve both monitoring content and data acquisition content, while others involve both monitoring content and device control content, or both data acquisition content and device control content. Therefore, by classifying and organizing target rule items through content category identifiers, target rule items with the same functional category can be uniformly grouped into the same rule item set. For example, when the content category identifier of a target rule item simultaneously represents both monitoring content and data acquisition content, then the target rule item is grouped into the rule item set corresponding to the combination of monitoring content and data acquisition content; when the content category identifier simultaneously represents both monitoring content and device control content, then the target rule item is grouped into the rule item set corresponding to the combination of monitoring content and device control content; when the content category identifier simultaneously represents both data acquisition content and device control content, then the target rule item is grouped into the target rule item set corresponding to the combination of data acquisition content and device control content.

[0095] On the one hand, software configuration items describe the software configuration content that needs to be formed under the corresponding functional category. For example, in the combination of monitoring content and data acquisition content, software configuration items describe the device objects that need to be monitored and the corresponding operational data that needs to be collected, such as device operation status monitoring configuration and device operation data acquisition configuration. In the combination of monitoring content and device control content, configuration content describes the device objects that need to be monitored and the device control configuration that needs to be executed under the corresponding device status, such as device operation status monitoring configuration and device start / stop control configuration. In the combination of data acquisition content and device control content, configuration content describes the operational data that needs to be collected and the device control configuration corresponding to the collected data, such as operational data acquisition configuration and device operation control parameter configuration.

[0096] On the other hand, the mapping range is used to describe the range of feature information involved in the mapping process under the current functional category in the standardized feature combination, so that different target rule item sets correspond to different feature parts when mapping the standardized feature combination, that is, to determine the standardized feature combination covered by the current functional category.

[0097] In the specific processing, the vehicle control terminal reads the target rule item set corresponding to a certain functional category, and extracts relevant standardized feature combinations from the standardized feature combinations according to the mapping range corresponding to the target rule item set. Then, based on the configuration content corresponding to the target rule item set, the extracted standardized feature combinations are converted into corresponding software configuration content, forming a configuration mapping result corresponding to that functional category, i.e., software configuration sub-content. Subsequently, the vehicle control terminal performs the same mapping processing on the target rule item sets corresponding to other functional categories, so that the standardized feature combinations form corresponding software configuration sub-content under different functional categories.

[0098] Furthermore, the software configuration sub-contents of different functional categories can participate in the arrangement process in a combined form during the subsequent sequential combination process. That is, since the configuration mapping stage has already formed a corresponding set of mapping items according to the combination relationship of monitoring content, data acquisition content, and device control content, the vehicle control terminal can directly arrange them uniformly according to the mapping items of each functional category during sequential combination. This ensures that the monitoring configuration, data acquisition configuration, and device control configuration, which originally needed to be used collaboratively, maintain their combination relationship in the software configuration result, thus enabling the final generated software configuration content to reflect the collaborative combination structure between different software configuration contents.

[0099] In this embodiment, firstly, the functional category identifier of each target rule item is obtained. Based on the functional category identifier, each target rule item is divided into functional categories to obtain a set of target rule items under each functional category. This allows the originally mixed target rule items to be categorized and organized according to functional categories. For each set of target rule items under each functional category, each standardized feature combination is configured and mapped according to the software configuration items and mapping range corresponding to the target rule items to obtain the software configuration sub-content corresponding to each standardized feature combination. Based on this, in the entire technical solution, the standardized feature combinations can be processed in an orderly manner according to functional categories during the configuration mapping process, forming a clearly structured software configuration sub-content.

[0100] In some embodiments, in step S204, based on the functional execution logic of the functional module, the sequential relationship between each software configuration sub-content is determined, and the software configuration sub-content is structured and arranged based on the sequential relationship to obtain the software configuration content. This includes: determining the functional execution order and data transmission order based on the functional execution logic of the functional module; rearranging the order of each software configuration sub-content according to the functional execution order and data transmission order to obtain a first software configuration sequence and a second software configuration sequence; cross-comparing the first software configuration sequence and the second software configuration sequence based on the direct dependency relationship between the preceding functional trigger and the subsequent data transmission to determine the mapping matching relationship between the preceding configuration sub-content and the subsequent configuration sub-content; wherein, the preceding configuration sub-content is the software configuration sub-content in the first software configuration sequence, and the subsequent configuration sub-content is the software configuration sub-content in the second software configuration sequence that has a direct dependency relationship with the preceding configuration sub-content; binding the preceding configuration sub-content and the subsequent configuration sub-content according to the mapping matching relationship to obtain software configuration mapping pairs; and sorting each software configuration mapping pair based on the functional execution order between each software configuration mapping pair to obtain the software configuration content.

[0101] The functional execution logic comprises the inherent temporal constraints and dependencies between functional modules during the operation of the functional cabin. It includes both the sequential execution order of functions and the transitive dependencies in data flow, forming the dual constraint basis for the structured orchestration of software configuration content. The functional execution order ensures that all software configuration sub-contents are arranged according to the actual business process of the equipment's operation, guaranteeing the correctness of the software execution logic and preventing errors such as "control first, monitoring later." For example, in protection or security scenarios, the software configuration sub-content containing equipment status monitoring is executed first to determine the equipment's operating status; then, the software configuration sub-content containing data acquisition is executed to obtain operational data related to the equipment's operation; after obtaining the relevant data, the software configuration sub-content containing equipment control is executed to control the equipment's operation. As another example, in a data-driven control scenario, the software configuration sub-content containing data acquisition is executed first to obtain equipment operational data; then, the software configuration sub-content containing equipment status monitoring is executed to identify the equipment status based on the acquired data; after identifying the equipment status, the software configuration sub-content containing equipment control is executed to control the equipment's operation. For example, in a closed-loop control scenario, the software configuration sub-content containing equipment status monitoring is executed first to obtain the equipment status; then, the software configuration sub-content containing data acquisition is executed to obtain the operating data corresponding to the equipment status; after obtaining the operating data, the software configuration sub-content containing equipment control is executed to adjust the equipment operation based on the acquired data; after the control adjustment is completed, the software configuration sub-content containing equipment status monitoring is executed again to monitor the adjusted equipment status, thus forming a cyclical execution relationship between equipment status monitoring, operating data acquisition, and equipment control.

[0102] Based on this, since different software configuration sub-contents undertake different processing tasks during execution, the software configuration sub-contents can be rearranged according to the function execution order. Specifically, the vehicle control terminal first reads each software configuration sub-content and identifies the function category corresponding to each software configuration sub-content. Then, it determines the arrangement position between each software configuration sub-content according to the pre-set function execution order, and arranges each software configuration sub-content from different function categories in sequence according to the execution order, so that each software configuration sub-content forms a continuous configuration structure according to the function execution order during the execution process, namely the first software configuration sequence.

[0103] In essence, this approach uses software configuration sub-contents to organize the function execution sequence. The rationale behind this is not only that the configuration mapping results themselves correspond to different function categories, but also that the way software configuration sub-contents are processed in the function execution sequence allows multiple interconnected software configuration contents to participate in the execution process as a whole. Since monitoring content, data acquisition content, and equipment control content often need to collaborate in the same processing stage during equipment operation, if they are arranged sequentially as individual configuration contents, other related configuration contents need to be called separately during execution. This results in the functional execution relationships between different configuration contents needing to be re-associated during the execution stage. However, by using software configuration contents that have already formed a combined relationship as software configuration sub-contents in the function execution sequence, monitoring content, data acquisition content, and equipment control content can enter the execution process together according to a predetermined configuration structure, allowing related configurations to be uniformly scheduled and processed in the same execution stage.

[0104] The data transmission order ensures that the data flow between each configuration sub-content is continuous and uninterrupted, guaranteeing that the data output by the previous combination can be smoothly transmitted to the next combination through the interface, forming a complete data link.

[0105] For example, the data transmission order describes the connection relationship between different software configuration sub-contents during the data transmission process. That is, data generated by one software configuration sub-content during execution needs to be transmitted to another software configuration sub-content through an interface, enabling subsequent software configuration sub-contents to continue processing based on this data. For instance, during device operation, software configuration sub-content related to device operation status monitoring generates device status information. This status information is transmitted through an interface to software configuration sub-content containing data acquisition content, allowing the data acquisition process to determine the acquisition object and data based on the device status. The acquired data is then transmitted through an interface to software configuration sub-content containing device control content, enabling the device control process to control the device operation based on the acquired data.

[0106] In the specific processing, the vehicle control terminal first reads the software configuration sub-contents corresponding to different function categories, then determines the data transmission relationship between each software configuration sub-content according to the pre-set data transmission order (i.e., data transmission sequence), and arranges each software configuration sub-content according to the data transmission order so that each software configuration sub-content can form a continuous configuration structure according to the data interaction relationship, i.e., the second software configuration sequence.

[0107] In essence, using software configuration sub-contents in the data transmission sequence is not only justified by the fact that the configuration mapping results correspond to different functional categories, but also by the fact that the organization of software configuration sub-contents in the data transmission sequence makes the data interaction structure between different software configuration sub-contents more stable. During device operation, various software configuration sub-contents often form continuous data transmission links through interfaces. For example, data generated by one configuration content during operation needs to be transmitted to another configuration content through an interface so that subsequent processing can continue based on the previous processing result. If interface associations are established separately for each configuration content, the data connections between each configuration content need to be established item by item, resulting in a scattered interface association structure during the arrangement process. However, by using multiple interrelated software configuration sub-contents in the data transmission sequence as software configuration sub-contents, the configuration content within each software configuration sub-content can form a continuous data transmission relationship within the same interface association structure, thus maintaining an overall correspondence in the data transmission links between different software configuration sub-contents within the configuration structure.

[0108] The direct dependency between the triggering of the preceding function and the subsequent data transmission is reflected in the following: the completion of the preceding function is a necessary prerequisite for the subsequent data transmission. That is, if the preceding function is not completed, the subsequent configuration cannot obtain valid input data. For example, the data acquisition function must be executed first before the generated running data can be used as the input basis for the device control content. If the preceding function is not completed or the output is abnormal, the subsequent data transmission will be interrupted due to the lack of a valid data source, which will cause the entire configuration sequence to stagnate.

[0109] Therefore, to ensure the robustness and real-time response capability of function execution in emergency scenarios, the vehicle control terminal reads each software configuration sub-content in the first software configuration sequence and identifies its position in the function execution order. At the same time, it reads each software configuration sub-content in the second software configuration sequence and identifies its connection position in the data transmission order. Then, based on the task requirements of the equipment operation in the current emergency scenario, it matches the corresponding software configuration sub-content in the two software configuration sequences, so that a mapping matching relationship is established between the position of each software configuration sub-content in the function execution order and the connection position in the data transmission order, which satisfies the direct dependency relationship between the preceding function triggering and the subsequent data transmission.

[0110] For example, in a flood drainage emergency scenario, the vehicle-mounted control terminal continuously acquires drainage flow data and adjusts equipment operation based on flow changes, requiring the drainage equipment to perform a corresponding match between the software configuration sub-contents in the first and second software configuration sequences. Specifically, in the first software configuration sequence, a software configuration sub-content containing equipment status monitoring and data acquisition is identified as being located at the beginning of the function execution sequence. Simultaneously, in the second software configuration sequence, this sub-content is identified as corresponding to a connection position that provides drainage flow data to subsequent software configuration sub-contents. Therefore, a mapping relationship is established between the initial position of this software configuration sub-content in the function execution sequence and the connection position related to drainage flow data output in the data transmission sequence.

[0111] For example, in a power generation emergency scenario, the vehicle-mounted control terminal, based on the task requirements of prioritizing the confirmation of equipment operating status and adjusting operation according to the equipment's operating capacity, matches the software configuration sub-contents in the first and second software configuration sequences. Specifically, in the first software configuration sequence, a software configuration sub-content containing equipment status monitoring and equipment control content is identified as being located at the beginning of the function execution sequence. Simultaneously, in the second software configuration sequence, this software configuration sub-content is identified as corresponding to a connection position that provides equipment status information to subsequent software configuration sub-contents. Therefore, a mapping and matching relationship is established between the initial position of this software configuration sub-content in the function execution sequence and the connection position related to status information output in the data transmission sequence.

[0112] After completing the mapping and matching relationship identification, the vehicle control terminal binds the software configuration sub-contents in the first software configuration sequence and the second software configuration sequence according to the mapping and matching relationship to obtain software configuration mapping pairs. This ensures that each software configuration sub-content maintains both the execution order relationship and the interface association relationship in the final configuration structure. Then, the software configuration mapping pairs are serialized and arranged according to the function execution order, and the execution logic in each mapping pair is embedded into the corresponding interface call node to form an executable configuration chain with timing constraints and data flow closed loop, which is the software configuration content.

[0113] In some embodiments, the software configuration content is synchronously updated to the vehicle's configuration runtime environment to obtain the vehicle after accessing the functional module. The process further includes: determining whether the functional module participates in collaborative operations with other functional modules; if it is determined that the functional module does not participate in collaborative operations with other functional modules, then the software configuration content is loaded in real-time through the vehicle's configuration runtime environment after accessing the functional module, and based on a preset operational organization relationship, a vehicle application matching the software configuration content is matched, and the matched vehicle application is activated; wherein, the operational organization relationship includes the mapping relationship between the software configuration content and the vehicle application; if it is determined that the functional module participates in collaborative operations with other functional modules, then the cross-module operational organization relationship is determined by combining the collaborative operation status and the software configuration content, and based on the cross-module operational organization relationship, the vehicle applications of each functional module participating in collaborative operations are activated, and the vehicle applications of each functional module participating in collaborative operations are launched.

[0114] In this context, collaborative operation involves multiple modular units with different functions working together to perform the same emergency task (such as flood drainage or communication support), requiring mutual cooperation. To enable the vehicle-mounted control terminal to automatically synchronize configurations across modular units and ultimately achieve automatic coordinated operation of multiple modular units, this embodiment first determines whether a functional modular unit participates in the collaborative operation.

[0115] If the functional module does not participate in collaborative operations, configuration loading and application activation only need to be completed within the vehicle terminal. Specifically, the vehicle's configuration operation environment after accessing the functional module loads the software configuration content in real time, and uses the mapping relationship (operation organization relationship) between the software configuration content and the vehicle application to match each software configuration sub-content in the software configuration content with the corresponding vehicle application, and accurately activates the associated vehicle application.

[0116] For example, the vehicle control terminal reads the software configuration content corresponding to the functional cabin and parses the various software configuration sub-contents contained therein. Then, it searches for the vehicle application modules corresponding to these software configuration sub-contents in the configuration management module, thereby establishing a mapping relationship between the software configuration content and the corresponding vehicle application modules. This mapping relationship describes the operational association structure between the software configuration sub-contents and the vehicle application modules. This operational association structure can be represented as a one-to-one correspondence between software configuration sub-contents and vehicle application modules, a combined correspondence, or a correspondence formed according to the execution order. For example: one software configuration sub-content corresponds to one vehicle application module, forming a one-to-one correspondence; two software configuration sub-contents jointly correspond to one vehicle application module, or one software configuration sub-content simultaneously corresponds to two vehicle application modules, forming a combined correspondence; three sequentially arranged software configuration sub-contents correspond to three sequentially activated vehicle application modules, forming a correspondence established according to the execution order.

[0117] If the current vehicle control terminal obtains software configuration content from other vehicle control terminals for their respective functional modules, it determines that the functional module is participating in collaborative operations with other functional modules. Collaborative operations typically occur when multiple functional modules participate in the same emergency scenario. For example, when multiple chassis carry different functional modules and arrive at the emergency operation area simultaneously, each vehicle control terminal needs to share the software configuration content of the functional modules it manages. Therefore, before entering multi-functional module collaborative operations, the current vehicle control terminal needs to obtain the software configuration content already generated in other vehicle control terminals. Specifically, when the current vehicle control terminal detects that multiple vehicle control terminals are participating in the same emergency scenario, it first identifies the other vehicle control terminals currently participating in the collaborative operation through the communication connection already established between the vehicles, and sends configuration acquisition requests to these vehicle control terminals, causing the other vehicle control terminals to send the software configuration content they generated for the connected functional modules to the current vehicle control terminal.

[0118] For example, the collaborative operation mode describes the operational coordination between different functional modules in the current emergency task, that is, the division of labor among the functional modules in the same emergency task. For instance, in a flood drainage emergency scenario, the power generation module is used to provide power support, while the drainage module is used to perform drainage operations, thus forming a collaborative operation mode between power generation support and drainage operations. In a communication support emergency scenario, the communication module is used to establish communication connections, while the monitoring module is used to collect on-site environmental information, thus forming a collaborative operation mode between communication support and on-site monitoring. After determining the above collaborative operation mode, the on-board control terminal further identifies the role of the current functional module in this collaborative operation mode, that is, the task positioning of the current functional module in the above division of labor. For example, when the current functional module is a drainage module, it undertakes the drainage task, and when the current functional module is a power generation module, it undertakes the power supply task.

[0119] After identifying the collaborative operation mode and the role of the current functional module, the on-board control terminal reads the software configuration content of each functional module and organizes these software configuration contents in the configuration management module according to the above information, so that the software configuration content of the current functional module corresponds to the software configuration content of other functional modules according to the collaborative operation mode and their roles, thereby forming a cross-module operation organization relationship in the configuration management module.

[0120] Among them, the cross-modal operation organization relationship is a configuration mapping structure established to adapt to the multi-modal cooperation needs in emergency scenarios and ensure that each functional modular unit accurately executes collaborative tasks according to its own division of labor. It includes the software configuration sub-contents corresponding to the division of labor roles of each functional modular unit, as well as the temporal execution relationship between these software configuration sub-contents.

[0121] For example, in a flood control emergency scenario, the on-board control terminal identifies the power generation module as being used to provide power, while the drainage module is used to perform drainage operations. If the current module is the drainage module, its role is that of the main body performing drainage operations. Therefore, in the configuration management module, the configuration content related to the operation control of the drainage equipment in the software configuration of the current module is matched with the configuration content related to the operating status of the power generation equipment in the software configuration of the power generation module, so that the operation of the drainage equipment can obtain power support based on the operating status of the power generation equipment.

[0122] For example, in emergency communication support scenarios, the communication function module is used to establish communication links, while the monitoring function module is used to collect on-site environmental information. If the current function module is the communication function module, its role is to provide communication support. Therefore, in the configuration management module, the configuration content related to the establishment of communication links in the software configuration of the current function module is matched with the configuration content related to environmental data collection in the software configuration of the monitoring function module, so that the monitoring data can be transmitted through the communication link.

[0123] Then, based on the cross-modal operation organization relationship, the vehicle application module corresponding to the current functional modular unit is activated so that the vehicle application module corresponding to the current functional modular unit can operate collaboratively with the vehicle application modules corresponding to other functional modular units.

[0124] For example, the current vehicle-mounted control terminal reads the cross-modal operation organization relationship established in the configuration management module to identify the correspondence between the software configuration content of the current functional modular unit and the software configuration content of other functional modular units. Then, based on this correspondence and the operation organization relationship, it determines the vehicle-mounted application modules in the current functional modular unit that need to participate in collaborative operation. On this basis, the current vehicle-mounted control terminal enables these vehicle-mounted application modules and, during the enabling process, determines the timing coordination method between them and the vehicle-mounted application modules of other functional modular units according to the cross-modal operation organization relationship. For example, based on the operating status of the vehicle-mounted application module corresponding to the power generation functional modular unit, it provides power status information to the vehicle-mounted application module corresponding to the drainage functional modular unit, so that the operation control of the drainage equipment can be adjusted according to the power supply situation; or based on the environmental data collected by the vehicle-mounted application module corresponding to the monitoring functional modular unit, it provides a data source to the vehicle-mounted application module corresponding to the communication functional modular unit, so that the monitoring data can be transmitted through the communication link. Based on this, the vehicle-mounted application modules corresponding to the current functional modular units can work collaboratively with the vehicle-mounted application modules corresponding to other functional modular units during operation. This allows the software configurations of different functional modular units to coordinate during operation, enabling the multi-functional modular units to achieve collaborative operation of their software configurations based on the cross-modal operation organization relationship when operating in conjunction with each other.

[0125] In some embodiments, in step S3, when the vehicle-mounted removal of the functional module after the access functional module is detected, the software configuration content of the functional module is removed from the configuration operation environment, including: when the vehicle-mounted removal of the functional module after the access functional module is detected, the cross-module operation organization relationship and operation organization relationship corresponding to the functional module are terminated, the software configuration content of the functional module is removed, and the vehicle-mounted application corresponding to the functional module is deactivated.

[0126] Preferably, when a functional module is removed, the vehicle control terminal identifies the software configuration content corresponding to the removed functional module, searches for the software configuration result in the configuration management module, locates the corresponding vehicle application module, and then cancels the established operational relationship between the software configuration content and these vehicle application modules. After the operational relationship is canceled, the configuration management module re-identifies the vehicle application modules that still maintain the operational relationship, and updates the operational status of each vehicle application module according to the canceled operational relationship, so that the vehicle application modules that have lost the operational relationship stop running, while the vehicle application modules that still maintain the operational relationship continue to run.

[0127] If the functional module is involved in collaborative operations, there are two scenarios when the functional module is removed:

[0128] In the first scenario, if the current functional module is removed from the corresponding chassis, the current cross-module operation organization relationship will be terminated in the configuration management module of the current vehicle control terminal, and the vehicle application module corresponding to the current functional module will be deactivated.

[0129] For example, after recognizing that the current functional module has been removed from the chassis, the vehicle control terminal reads the software configuration content corresponding to the current functional module and the current cross-module operation organization relationship from the configuration management module. Based on this, the vehicle control terminal removes the current cross-module operation organization relationship from the configuration management module, thus removing the configuration content originally used to describe the collaborative operation relationship between the current functional module and other functional modules. After completing the above removal process, the vehicle control terminal, according to the removed cross-module operation organization relationship, performs a deactivation process on the vehicle application modules related to the current functional module, causing these vehicle application modules to exit the running state, thereby completing the data cancellation process in the case of the removal of the current functional module.

[0130] In the second scenario, if a functional module other than the current functional module is removed from the corresponding chassis, the current cross-module operation organization relationship is adjusted in the configuration management module of the current vehicle control terminal, and the vehicle application module corresponding to the current functional module is reactivated according to the adjusted cross-module operation organization relationship.

[0131] For example, during the coordinated operation of the multi-functional modular cabins, communication connections are maintained between the vehicle-mounted control terminals. Therefore, when a functional cabin on another chassis is removed, the corresponding vehicle-mounted control terminal will stop sending software configuration content related to that functional cabin, or send status information related to the removal of the functional cabin to other vehicle-mounted control terminals. The current vehicle-mounted control terminal can identify that a specified functional cabin other than the current functional cabin has been removed from the corresponding chassis by receiving the status information or detecting that the relevant software configuration content has not been received.

[0132] After identifying the removed functional modules, the current vehicle control terminal reads the original cross-module operation organization relationship from the configuration management module and identifies the software configuration content related to the removed functional modules. Then, the configuration management module removes the software configuration content related to the removed functional modules from the original cross-module operation organization relationship and reorganizes the correspondence between the software configuration content of the remaining functional modules to obtain the adjusted cross-module operation organization relationship. That is, the adjusted cross-module operation organization relationship describes the continued operational coordination among the remaining functional modules. For example, when the original cross-module operation organization relationship includes a power generation functional module, a drainage functional module, and a monitoring functional module, after the monitoring functional module is removed, the configuration management module re-establishes a correspondence between the software configuration content of the power generation functional module and the software configuration content of the drainage functional module, so that the operation of the drainage equipment can still be adjusted according to the operating status of the power generation equipment. After completing the above adjustments, the current vehicle control terminal re-identifies the vehicle application modules that the current functional modules need to participate in the operation based on the adjusted cross-module operation organization relationship and re-enables these vehicle application modules.

[0133] Based on the same inventive concept, this application also provides a software automatic configuration system for implementing the above-mentioned software automatic configuration method based on the modular access process.

[0134] The solution provided by this system is similar to the solution described in the above method. Therefore, the specific limitations of one or more software automatic configuration system embodiments based on the mobile cabin access process provided below can be found in the limitations of the software automatic configuration method based on the mobile cabin access process above, and will not be repeated here.

[0135] like Figure 5 As shown in the figure, this application provides a software automatic configuration system based on the mobile cabin access process, including: a parameter acquisition module 100, a configuration access module 200, and a configuration removal module 300.

[0136] The parameter acquisition module 100 is used to obtain the cabin configuration parameters of the functional cabin in response to the vehicle access request of the functional cabin.

[0137] The configuration access module 200 is used to generate software configuration content that meets the functional execution logic of the functional modular cabin according to the pre-established software configuration rules and the modular cabin configuration parameters, and to synchronously update the software configuration content to the vehicle's configuration and operation environment to obtain the vehicle after accessing the functional modular cabin.

[0138] The configuration removal module 300 is used to remove the software configuration content of the functional module from the configuration operating environment when the vehicle-mounted functional module is detected to be removed after the access functional module is detected.

[0139] In some embodiments, the parameter acquisition module 100 is used for:

[0140] Acquire the physical connection signal when the vehicle access functional cabin is used, and determine the cabin type of the functional cabin based on the physical connection signal;

[0141] Determine the preset communication protocol corresponding to the type of modular shelter, establish a communication connection with the functional modular shelter based on the preset communication protocol, and obtain the modular shelter configuration parameters of the functional modular shelter.

[0142] In some embodiments, the modular cabin configuration parameters include modular cabin type, rated operating parameters, and equipment specification information;

[0143] Configure access module 200 for:

[0144] Extract multiple parameter category identifiers and parameter value features corresponding to each parameter category identifier from the configuration parameters of the mobile cabin. Perform format standardization combination on each parameter category identifier and its corresponding parameter value features to generate a standardized feature set.

[0145] Each standardized feature combination in the standardized feature set is matched against the rule items in the software configuration rules one by one to determine at least one target rule item for each standardized feature combination.

[0146] Based on at least one target rule item, its corresponding standardized feature combination is configured and mapped to obtain the software configuration sub-content corresponding to each standardized feature combination;

[0147] Based on the functional execution logic of the functional module, the sequential relationship between the sub-contents of each software configuration is determined, and the sub-contents of each software configuration are arranged in a structured manner based on the sequential relationship to obtain the software configuration content.

[0148] In some embodiments, the access module 200 is configured to:

[0149] Obtain the function category identifier of each target rule item, and divide each target rule item into function categories according to the function category identifier to obtain the set of target rule items under each function category;

[0150] For each set of target rule items under each functional category, configuration mapping is performed on each standardized feature combination according to the software configuration items and mapping range corresponding to the target rule items, so as to obtain the software configuration sub-content corresponding to each standardized feature combination.

[0151] In some embodiments, the access module 200 is configured to:

[0152] Based on the functional execution logic of the functional modular unit, the order of function execution and data transmission is determined.

[0153] Based on the function execution order and data transmission order, the contents of each software configuration sub-content are rearranged to obtain the first software configuration sequence and the second software configuration sequence.

[0154] Based on the direct dependency between the pre-function triggering and the subsequent data transmission, the first software configuration sequence and the second software configuration sequence are cross-compared to determine the mapping and matching relationship between the pre-configuration sub-content and the subsequent configuration sub-content; wherein, the pre-configuration sub-content is the software configuration sub-content in the first software configuration sequence, and the subsequent configuration sub-content is the software configuration sub-content in the second software configuration sequence that has a direct dependency relationship with the pre-configuration sub-content;

[0155] Based on the mapping matching relationship, the pre-configuration sub-contents are bound to the post-configuration sub-contents to obtain software configuration mapping pairs;

[0156] Based on the functional execution order among the software configuration mapping pairs, the software configuration mapping pairs are sorted to obtain the software configuration content.

[0157] In some embodiments, the system further includes: an application launch module, configured to:

[0158] Determine whether the functional modular unit participates in collaborative operations with other functional modular units;

[0159] If it is determined that the functional module does not participate in collaborative operations with other functional modules, the software configuration content is loaded in real time through the vehicle configuration and operation environment after accessing the functional module, and the vehicle application that matches the software configuration content is matched based on the preset operation organization relationship, and the matched vehicle application is enabled; wherein, the operation organization relationship includes the mapping relationship between the software configuration content and the vehicle application.

[0160] If it is determined that a functional module participates in collaborative operations with other functional modules, the cross-module operation organization relationship is determined by combining the collaborative operation status and software configuration content. Based on the cross-module operation organization relationship, the vehicle-mounted applications of each functional module participating in collaborative operations are activated and launched.

[0161] In some embodiments, the removal module 300 is configured to:

[0162] If the vehicle removes a functional module after it has been connected to the functional module, the cross-module operation organization relationship and operation organization relationship corresponding to the functional module will be terminated, the software configuration content of the functional module will be removed, and the vehicle application corresponding to the functional module will be deactivated.

[0163] like Figure 6 As shown, this application provides an electronic device. The electronic device 10 includes a memory 20 and a processor 30. The memory 20 stores a computer program. When the computer program is executed by the processor 30, the processor 30 performs the steps of the software automatic configuration method based on the cabin access process in the above embodiment.

[0164] This application provides a computer-readable storage medium storing a computer program thereon. When the computer program is executed, it implements the steps of the software automatic configuration method based on the cabin access process as described in the above embodiments.

[0165] Those skilled in the art will clearly understand that, for the sake of convenience and brevity, the specific working processes of the systems, electronic devices, and computer storage media described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0166] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that the embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0167] It should be understood that although the steps in the flowcharts of the embodiments described above are shown sequentially according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless explicitly stated herein, there is no strict order restriction on the execution of these steps, and they can be executed in other orders. Moreover, at least some steps in the flowcharts of the embodiments described above may include multiple steps or multiple stages. These steps or stages are not necessarily completed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be performed alternately or in turn with other steps or at least some of the steps or stages of other steps.

[0168] In the embodiments provided by this invention, it should be understood that the disclosed systems, electronic devices, computer storage media, and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection between devices or units through some interfaces, and may be electrical, mechanical, or other forms.

[0169] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0170] Furthermore, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0171] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions for executing all or part of the steps of the methods described in the various embodiments of the present invention through a computer device (which may be a personal computer, a server, or a network device, etc.). The aforementioned storage medium includes: USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, optical disks, and other media capable of storing program code.

[0172] The above embodiments are only used to illustrate the technical solutions of the present invention, and are not intended to limit it. Although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A software-automated configuration method based on the modular hospital access process, characterized in that, include: In response to the vehicle access request of the functional modular unit, the modular unit configuration parameters are obtained. According to the pre-established software configuration rules, software configuration content that satisfies the functional execution logic of the functional modular unit is generated based on the modular unit configuration parameters, and the software configuration content is synchronously updated to the vehicle-mounted configuration and operation environment to obtain the vehicle-mounted unit after accessing the functional modular unit; the modular unit configuration parameters include modular unit type, rated operating parameters and equipment specification information; The step of generating software configuration content that satisfies the functional execution logic of the functional modular container based on the pre-established software configuration rules and the modular container configuration parameters includes: Extract multiple parameter category identifiers and parameter value features corresponding to each parameter category identifier from the configuration parameters of the mobile cabin. Perform format standardization combination on each parameter category identifier and its corresponding parameter value features to generate a standardized feature set. Each standardized feature combination in the standardized feature set is matched one by one with the rule items in the software configuration rules to determine at least one target rule item for each standardized feature combination. Based on at least one of the target rule items, the corresponding standardized feature combination is configured and mapped to obtain the software configuration sub-content corresponding to each standardized feature combination; Based on the functional execution logic of the aforementioned functional cabin, the sequential relationship between the various software configuration sub-contents is determined, and the software configuration sub-contents are structured and arranged based on the sequential relationship to obtain the software configuration content, including: Based on the functional execution logic of the aforementioned functional modular unit, the functional execution order and data transmission order are determined. Based on the function execution order and the data transmission order, the software configuration sub-contents are rearranged to obtain the first software configuration sequence and the second software configuration sequence. Based on the direct dependency between pre-function triggering and post-data transmission, the first software configuration sequence and the second software configuration sequence are cross-compared to determine the mapping and matching relationship between pre-configuration sub-content and post-configuration sub-content; wherein, the pre-configuration sub-content is the software configuration sub-content in the first software configuration sequence, and the post-configuration sub-content is the software configuration sub-content in the second software configuration sequence that has a direct dependency relationship with the pre-configuration sub-content; Based on the mapping matching relationship, the pre-configuration sub-content and the post-configuration sub-content are bound to obtain a software configuration mapping pair; Based on the functional execution order among the software configuration mapping pairs, the software configuration mapping pairs are sorted to obtain the software configuration content; If the vehicle removes the functional module after it has been accessed, the software configuration content of the functional module is removed from the configuration operating environment.

2. The software automatic configuration method based on the modular shelter access process according to claim 1, characterized in that, The process of responding to the vehicle access request of the functional modular cabin and obtaining the cabin configuration parameters of the functional modular cabin includes: The physical connection signal of the vehicle when it connects to the functional cabin is obtained, and the cabin type of the functional cabin is determined based on the physical connection signal. A preset communication protocol corresponding to the type of modular shelter is determined, a communication connection is established with the functional modular shelter based on the preset communication protocol, and the modular shelter configuration parameters of the functional modular shelter are obtained.

3. The software automatic configuration method based on the modular shelter access process according to claim 1, characterized in that, The step of configuring and mapping the corresponding standardized feature combinations according to at least one of the target rule items to obtain the software configuration sub-content corresponding to each standardized feature combination includes: Obtain the functional category identifier of each target rule item, and divide each target rule item into functional categories according to the functional category identifier to obtain the set of target rule items under each functional category; For each set of target rule items under each functional category, the standardized feature combination is configured and mapped according to the software configuration items and mapping range corresponding to the target rule items, so as to obtain the software configuration sub-content corresponding to each standardized feature combination.

4. The software automatic configuration method based on the modular shelter access process according to claim 1, characterized in that, The process of synchronizing and updating the software configuration content to the vehicle's configuration and operating environment to obtain the vehicle's configuration after accessing the functional cabin further includes: Determine whether the functional module participates in collaborative operations with other functional modules; If it is determined that the functional module does not participate in collaborative operations with other functional modules, the software configuration content is loaded in real time through the configuration operating environment of the vehicle after accessing the functional module, and based on the preset operating organization relationship, the vehicle application that matches the software configuration content is matched and the matched vehicle application is enabled; wherein, the operating organization relationship includes the mapping relationship between the software configuration content and the vehicle application. If it is determined that the functional module participates in collaborative operations with other functional modules, then the cross-module operation organization relationship is determined by combining the collaborative operation status and the software configuration content, and the vehicle-mounted application of each functional module participating in collaborative operations is activated and started according to the cross-module operation organization relationship.

5. The software automatic configuration method based on the modular shelter access process according to claim 4, characterized in that, The step of removing the software configuration content of the functional module from the configuration operating environment when the vehicle removes the functional module after it has been accessed includes: If the vehicle removes the functional module after it has been connected to the functional module, the cross-module operation organization relationship and operation organization relationship corresponding to the functional module are terminated, the software configuration content of the functional module is removed, and the vehicle application corresponding to the functional module is deactivated.

6. A software-automated configuration system based on the modular hospital access process, characterized in that, include: The parameter acquisition module is used to obtain the cabin configuration parameters of the functional cabin in response to the vehicle access request of the functional cabin. The configuration access module is used to generate software configuration content that satisfies the functional execution logic of the functional modular cabin according to the pre-established software configuration rules and the configuration parameters of the modular cabin, and to synchronously update the software configuration content to the configuration and operation environment of the vehicle to obtain the vehicle after accessing the functional modular cabin; The configuration parameters of the mobile cabin include the type of mobile cabin, rated operating parameters, and equipment specifications. Based on pre-established software configuration rules, software configuration content that satisfies the functional execution logic of the functional modular container is generated according to the modular container configuration parameters, including: Extract multiple parameter category identifiers and parameter value features corresponding to each parameter category identifier from the configuration parameters of the mobile cabin. Perform format standardization combination on each parameter category identifier and its corresponding parameter value features to generate a standardized feature set. Each standardized feature combination in the standardized feature set is matched one by one with the rule items in the software configuration rules to determine at least one target rule item for each standardized feature combination. Based on at least one of the target rule items, the corresponding standardized feature combination is configured and mapped to obtain the software configuration sub-content corresponding to each standardized feature combination; Based on the functional execution logic of the aforementioned functional cabin, the sequential relationship between the various software configuration sub-contents is determined, and the software configuration sub-contents are structured and arranged based on the sequential relationship to obtain the software configuration content, including: Based on the functional execution logic of the aforementioned functional modular unit, the functional execution order and data transmission order are determined. Based on the function execution order and the data transmission order, the software configuration sub-contents are rearranged to obtain the first software configuration sequence and the second software configuration sequence. Based on the direct dependency between pre-function triggering and post-data transmission, the first software configuration sequence and the second software configuration sequence are cross-compared to determine the mapping and matching relationship between pre-configuration sub-content and post-configuration sub-content; wherein, the pre-configuration sub-content is the software configuration sub-content in the first software configuration sequence, and the post-configuration sub-content is the software configuration sub-content in the second software configuration sequence that has a direct dependency relationship with the pre-configuration sub-content; Based on the mapping matching relationship, the pre-configuration sub-content and the post-configuration sub-content are bound to obtain a software configuration mapping pair; Based on the functional execution order among the software configuration mapping pairs, the software configuration mapping pairs are sorted to obtain the software configuration content; A configuration removal module is used to remove the software configuration content of the functional module from the configuration operating environment when the vehicle removes the functional module after it has been accessed.

7. An electronic device, characterized in that, The electronic device includes a memory and a processor. The memory stores a computer program. When the computer program is executed by the processor, the processor performs the steps of the software automatic configuration method based on the mobile cabin access process as described in any one of claims 1-5.

8. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed, it implements the steps of the software automatic configuration method based on the modular access process as described in any one of claims 1-5.

Images