Dynamic configuration mapping system and method of VR head-mounted display device

Abstract

The invention discloses a dynamic configuration mapping system and method for VR head-mounted display equipment. In the invention, through the design of each sub-module of the intelligent mapping matching module, the development and maintenance cost is greatly reduced. The configuration validity verification sub-module checks the integrity of a configuration structure in advance, and running errors caused by invalid configuration are avoided; the device name matching sub-module adopts inclusion relation search instead of accurate matching, supports a device group and wildcard character form, and does not need to compile a large number of if-else codes like a traditional scheme; the mapping index positioning sub-module corresponds to equipment and configuration one by one through array indexes, new equipment only needs to add corresponding items in a configuration file, core codes do not need to be modified, the access period of the new equipment is remarkably shortened, meanwhile, the workload of regression testing is reduced, the risk of configuration conflicts is avoided, and the efficiency is improved. When the fault-tolerant degradation processing sub-module does not find the matching configuration, the wildcard character is automatically triggered to carry out the default configuration or load the default configuration, so that the interface component is ensured to be normally rendered all the time, and the robustness of the system and the user experience are improved.

Description

Technical Field

[0001] This invention belongs to the field of VR headset technology, specifically a dynamic configuration mapping system and method for VR headset devices. Background Technology

[0002] VR device configuration management refers to the comprehensive management process of systematically setting up, optimizing, and maintaining virtual reality hardware and its operating environment. Its core objective is to ensure stable device performance, a comfortable user experience, and good application compatibility. This management scope covers the calibration of key hardware parameters such as headset resolution, refresh rate, interpupillary distance, and safe zone boundaries, as well as the setting of controller tracking accuracy, controller mapping, and haptic feedback intensity. Simultaneously, it involves fine-tuning software aspects such as audio output, rendering quality, and motion smoothness to balance visual effects and system load. Effective configuration management not only reduces user dizziness through personalized settings but also allows for quick switching to the optimal performance solution based on different application scenarios (such as gaming, design, and training). It is an indispensable foundation for ensuring efficient VR system operation and enhancing immersion and interactive experience.

[0003] However, existing technologies use hard-coded if-else logic to adapt to devices, requiring modifications to the core code for each new device, resulting in high maintenance costs and long integration cycles for new devices. At the same time, the configuration items lack specificity, displaying the same configuration items on all devices, and still showing unsupported functions to users, leading to a poor user experience. Summary of the Invention

[0004] The purpose of this invention is to provide a dynamic configuration mapping system and method for VR headsets in order to solve the problems mentioned above.

[0005] The technical solution adopted in this invention is as follows: A dynamic configuration mapping system for VR head-mounted display devices, comprising: a configuration storage module, a device detection module, an intelligent mapping matching module, and an interface rendering module; The intelligent mapping matching module is internally configured with: a configuration validity verification submodule, a device name matching submodule, a mapping index positioning submodule, a fault tolerance and degradation processing submodule, and a result adaptation and output submodule. The output of the configuration storage module is connected to the configuration data input of the intelligent mapping matching module, providing it with an array of device names and an array of configuration maps; The output of the device detection module is connected to the device information input of the intelligent mapping and matching module, transmitting the model of the currently connected VR device. The configuration output of the intelligent mapping matching module is connected to the configuration input of the interface rendering module, and sends the adapted configuration object to the interface rendering module for dynamically generating the user interface.

[0006] In a preferred embodiment, the configuration storage module internally includes a configuration file storage unit, a device name array management unit, a configuration mapping array management unit, and a configuration item classification unit. The configuration file storage unit stores the `deviceSettingConfig.js` file, which contains configuration information for all devices in the system. The device name array management unit maintains a `deviceName` array, whose elements support three formats: device group expansion, exact device name, and wildcards. The configuration mapping array management unit maintains a corresponding `mapping` array, where each element is a configuration object that corresponds one-to-one with the index in the `deviceName` array. The configuration item classification unit divides the configuration into three categories according to sections: basic settings, display settings, and advanced settings, with each category containing multiple configuration items.

[0007] In a preferred embodiment, the device detection module internally includes a device connection status monitoring unit, a device model identifier acquisition unit, and a device status real-time update unit. The device connection status monitoring unit continuously checks whether the VR device is connected; the device model identifier acquisition unit extracts the device model identifier from the connected device; and the device status real-time update unit synchronizes changes in the device's connection or disconnection status to ensure that the system obtains the latest device information in a timely manner.

[0008] In a preferred embodiment, the configuration validity verification submodule comprises five parts: an input parameter validity verification module, a double array structure integrity verification module, an element format compliance detection module, a dependency compliance verification module, and an error handling mechanism module. The input parameter validity verification module verifies whether the input configuration object contains the two core attributes, deviceName and mapping, and that both are non-empty arrays. The double array structure integrity verification module ensures that each device name or device group has a corresponding configuration mapping by comparing the lengths of the deviceName array and the mapping array, avoiding index misalignment. The element format compliance detection module checks whether each element in the deviceName array is a string or an array containing strings, and verifies whether each element in the mapping array is a valid JSON object containing required fields. The dependency compliance verification module checks whether the spread operator is used correctly when expanding device groups, and whether the wildcard format conforms to system conventions. The error handling mechanism module returns undefined when verification fails and records detailed error logs, facilitating quick problem location for developers and supporting custom error messages to improve debugging efficiency.

[0009] The formula for verifying the consistency of the lengths of the two arrays is as follows: ; In the formula: D represents an array of device names, which stores a collection of exact device names, device groups, or wildcards; M represents the configuration mapping array, which stores a collection of configuration objects that correspond one-to-one with the elements of the device name array. Length(·) returns the number of elements in the array.

[0010] In a preferred embodiment, the device name matching submodule comprises five parts: a device name traversal submodule, an inclusion relationship detection submodule, a priority sorting submodule, a wildcard processing submodule, and an index return submodule. The device name traversal submodule accesses each element sequentially according to the original order of the device name array, ensuring that the matching process follows preset priority rules. The inclusion relationship detection submodule determines whether the current VR device model identifier is contained in the array element (supporting exact device names, expanded arrays of device groups, and wildcards), implementing the core logic of non-exact matching. The priority sorting submodule maintains the order of the array, ensuring that exact device names take precedence over device groups, and device groups take precedence over wildcards, avoiding configuration conflicts. The wildcard processing submodule identifies and processes wildcard elements such as "allDevices," providing default mappings for all devices that do not match a specific configuration. The index return submodule returns the corresponding array index when a match is successful, and returns an identifier value (e.g., -1) when no match is found, providing crucial input for subsequent configuration mappings.

[0011] In a preferred embodiment, the mapping index positioning submodule comprises five parts: a device name array traversal submodule, an inclusion relationship matching algorithm submodule, an array boundary verification submodule, a wildcard priority processing submodule, and a configuration mapping index acquisition submodule. The device name array traversal submodule is responsible for traversing each element in the deviceName array in sequence, supporting traversal of exact device names (such as "PIMAX_P3C9_V1"), device groups (such as [...HmdDeviceNames.PIMAX_P3C9]), and wildcards (such as "allDevices"). The inclusion relationship matching algorithm submodule adopts dynamic inclusion detection logic, which determines the matching index by judging whether the current device model exists in a certain element of the deviceName array (such as hmdName∈deviceName[i]). The array boundary verification submodule checks whether the index is within the valid range (0≤i<|deviceName|) during traversal to avoid out-of-bounds access. The wildcard priority processing submodule ensures that wildcard elements are selected only when there is no exact or device group match, following the rule of "exact priority, wildcard as a fallback". The configuration mapping index acquisition submodule directly obtains the corresponding configuration object from the configuration mapping array mapping based on the matched index i, realizing the index association of the two arrays.

[0012] The index matching formula is: ; In the formula: i represents the index of the array of matched device names; h represents the model identifier of the currently connected VR device; D represents an array of device names (containing exact device names, device groups, or wildcards). |D| represents the length of the device name array; [0,|D|-1] represents the valid range of the index; ∈ indicates that an element belongs to a set; The configuration mapping formula is: C = M[i]; In the formula: C represents the configuration object that matches the current device; M represents the configuration mapping array; i represents the index of the array of matched device names.

[0013] In a preferred embodiment, the fault-tolerant degradation processing submodule comprises five parts: a matching result null value detection submodule, a wildcard fallback matching submodule, a system default configuration loading submodule, an error log recording submodule, and a configuration conflict priority handling submodule. The matching result null value detection submodule checks whether the configuration object returned by the mapping index positioning submodule is undefined, determining whether a degradation process needs to be triggered. The wildcard fallback matching submodule automatically searches for the configuration mapping corresponding to the element marked "allDevices" in the device name array when there is no exact or device group match, providing a fallback for general configurations. The system default configuration loading submodule loads predefined system-level default configurations (such as IPD range 50-80mm) when wildcard matching fails, ensuring that interface components can still render normally. The error log recording submodule records detailed information when degradation is triggered, including device model, reason for matching failure, and degradation path, facilitating subsequent configuration optimization. The configuration conflict priority handling submodule follows the priority rule of "exact match > device group match > wildcard match > default configuration" to avoid configuration conflicts caused by multi-path matching.

[0014] The formula for obtaining the fault tolerance and degradation configuration is: ; In the formula: C represents the device configuration object that is ultimately applied to the interface components; M represents the configuration mapping array; i represents the array index of the device names matched exactly or by the device group; D represents an array of device names; |D| represents the number of elements in the device name array; M w This represents the configuration object corresponding to the wildcard "allDevices"; w represents the index of the wildcard element in the device name array; C d This represents the system's predefined default configuration object; The wildcard index matching formula is: ; In the formula: w represents the index of the wildcard element in the device name array; D represents an array of device names; findIndex means returning the index of the first element in the array that meets the given condition; allDevices represents the wildcard identifiers agreed upon by the system.

[0015] In a preferred embodiment, the result adaptation output submodule comprises five parts: a configuration object parsing submodule, an interface component attribute binding submodule, a data format conversion submodule, a dynamic UI element generation submodule, and a configuration change monitoring submodule. The configuration object parsing submodule is responsible for decomposing the mapping-matched configuration object into discrete attributes that can be directly used by the interface components, such as extracting the minimum and maximum range values ​​and unit information from the IPD adjustment configuration; the interface component attribute binding submodule directly associates the parsed attributes with the parameters of the corresponding UI components, such as setting the IPD range value as the value range of the slider component; the data format conversion submodule processes the display format of device data according to the format rules in the configuration, such as concatenating the firmware version number into a user-readable string according to a specified format; the dynamic UI element generation submodule determines whether to render specific interface elements based on the functional support in the configuration, such as automatically hiding the corresponding calibration button for devices that do not support eye tracking; the configuration change monitoring submodule continuously monitors the device connection status and configuration file updates, and automatically triggers a re-adaptation process when a device switch or configuration change is detected, ensuring that the interface always displays the latest adapted configuration.

[0016] In a preferred embodiment, the interface rendering module internally includes a component dynamic generation unit, a configuration attribute binding unit, a dynamic UI element control unit, and a configuration change monitoring unit. The component dynamic generation unit creates the corresponding interface component based on the typeName in the configuration; the configuration attribute binding unit associates the properties of the mapped configuration object with the parameters of the component; the dynamic UI element control unit decides whether to render a specific interface element based on the functional support in the configuration; and the configuration change monitoring unit monitors the device connection status and configuration file updates, triggering component re-adaptation and rendering.

[0017] In summary, due to the adoption of the above technical solution, the beneficial effects of the present invention are: 1. In this invention, the design of each sub-module of the intelligent mapping and matching module significantly reduces development and maintenance costs. The configuration validity verification sub-module checks the integrity of the configuration structure in advance to avoid runtime errors caused by invalid configurations; the device name matching sub-module uses inclusion relationship lookup instead of exact matching, supports device groups and wildcard forms, and eliminates the need to write a large amount of if-else code as in traditional solutions; the mapping index positioning sub-module uses array indexes to correspond one-to-one between devices and configurations, so adding a new device only requires adding the corresponding item to the configuration file, without modifying the core code, which significantly shortens the access cycle of new devices, reduces the workload of regression testing, and avoids the risk of configuration conflicts.

[0018] 2. In this invention, the fault tolerance and degradation processing submodule automatically triggers a wildcard fallback or loads the default configuration when no matching configuration is found, ensuring that the interface components can always render normally and that the service will not be interrupted due to device matching failure. The result adaptation and output submodule parses the configuration object into attributes that the components can directly use, dynamically generates UI elements that conform to the device's functions, and automatically hides unsupported function options to prevent users from seeing irrelevant or unusable settings. In addition, the system supports real-time re-adaptation when switching devices without manual intervention from the user. The configuration update takes effect immediately, allowing users to have a smooth and consistent operating experience when using different VR headsets, thereby improving the robustness of the system and the user experience. Attached Figure Description

[0019] Figure 1 This is a system block diagram of the present invention; Figure 2 This is a system block diagram of the intelligent mapping and matching module in this invention. Detailed Implementation

[0020] To make the objectives, technical solutions, and advantages of this invention clearer, the invention will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative and not intended to limit the invention.

[0021] Example: Reference Figure 1-2 A dynamic configuration mapping system for VR headsets, comprising a configuration storage module, a device detection module, an intelligent mapping matching module, and an interface rendering module; The intelligent mapping matching module has the following internal settings: configuration validity verification submodule, device name matching submodule, mapping index positioning submodule, fault tolerance and degradation processing submodule, and result adaptation output submodule; The output of the configuration storage module is connected to the configuration data input of the intelligent mapping matching module, providing it with an array of device names and an array of configuration maps; The output of the device detection module is connected to the device information input of the intelligent mapping and matching module to transmit the model of the currently connected VR device. The configuration output of the intelligent mapping matching module is connected to the configuration input of the interface rendering module, and sends the adapted configuration object to the interface rendering module for dynamically generating the user interface.

[0022] The configuration storage module internally includes a configuration file storage unit, a device name array management unit, a configuration mapping array management unit, and a configuration item classification unit. The configuration file storage unit stores the `deviceSettingConfig.js` file, which contains configuration information for all devices in the system. The device name array management unit maintains a `deviceName` array, whose elements support three formats: device group expansion, exact device name, and wildcards. The configuration mapping array management unit maintains a corresponding `mapping` array, where each element is a configuration object that corresponds one-to-one with the index in the `deviceName` array. The configuration item classification unit divides the configuration into three categories based on sections: basic settings, display settings, and advanced settings, with each category containing multiple configuration items.

[0023] The device detection module internally includes a device connection status monitoring unit, a device model identifier acquisition unit, and a device status real-time update unit. The device connection status monitoring unit continuously checks whether the VR device is connected; the device model identifier acquisition unit extracts the device model identifier from the connected device; and the device status real-time update unit synchronizes changes in the device's connection or disconnection status to ensure that the system obtains the latest device information in a timely manner.

[0024] The configuration validity verification submodule comprises five parts: an input parameter validity verification module, a double array structure integrity verification module, an element format compliance detection module, a dependency compliance verification module, and an error handling mechanism module. The input parameter validity verification module verifies whether the passed configuration object contains the two core attributes, `deviceName` and `mapping`, and that both are non-empty arrays. The double array structure integrity verification module ensures that each device name or device group has a corresponding configuration mapping by comparing the lengths of the `deviceName` array and the `mapping` array, avoiding index misalignment. The element format compliance detection module checks each element in the `deviceName` array to ensure it is a string or an array containing strings, and verifies that each element in the `mapping` array is a valid JSON object containing required fields. The dependency compliance verification module checks whether the spread operator is used correctly when expanding device groups, and whether the wildcard format conforms to system conventions. The error handling mechanism module returns `undefined` when verification fails and records detailed error logs, facilitating quick problem location for developers. It also supports custom error messages to improve debugging efficiency.

[0025] The formula for verifying the consistency of the lengths of the two arrays is as follows: ; In the formula: D represents an array of device names, which stores a collection of exact device names, device groups, or wildcards; M represents the configuration mapping array, which stores a collection of configuration objects that correspond one-to-one with the elements of the device name array. Length(·) returns the number of elements in the array.

[0026] The device name matching submodule comprises five parts: device name traversal submodule, inclusion relationship detection submodule, priority sorting submodule, wildcard processing submodule, and index return submodule. The device name traversal submodule accesses each element in the original order of the device name array, ensuring the matching process follows preset priority rules. The inclusion relationship detection submodule determines whether the current VR device model identifier is contained in the array element (supporting exact device names, expanded arrays of device groups, and wildcards), implementing the core logic of non-exact matching. The priority sorting submodule maintains the array's order, ensuring that exact device names have priority over device groups, and device groups have priority over wildcards, avoiding configuration conflicts. The wildcard processing submodule identifies and processes wildcard elements such as "allDevices," providing default mappings for all devices that do not match a specific configuration. The index return submodule returns the corresponding array index when a match is successful, and a flag value (e.g., -1) when no match is found, providing crucial input for subsequent configuration mapping.

[0027] The mapping index positioning submodule consists of five parts: device name array traversal submodule, inclusion relationship matching algorithm submodule, array boundary verification submodule, wildcard priority processing submodule, and configuration mapping index acquisition submodule. The device name array traversal submodule is responsible for traversing each element in the deviceName array in sequence, supporting traversal of exact device names (such as "PIMAX_P3C9_V1"), device groups (such as [...HmdDeviceNames.PIMAX_P3C9]), and wildcards (such as "allDevices"). The inclusion relationship matching algorithm submodule adopts dynamic inclusion detection logic, which determines the matching index by judging whether the current device model exists in a certain element of the deviceName array (such as hmdName∈deviceName[i]). The array boundary verification submodule checks whether the index is within the valid range (0≤i<|deviceName|) during traversal to avoid out-of-bounds access. The wildcard priority processing submodule ensures that wildcard elements are selected only when there is no exact or device group match, following the rule of "exact priority, wildcard as a fallback". The configuration mapping index acquisition submodule directly obtains the corresponding configuration object from the configuration mapping array mapping based on the matched index i, realizing the index association of the two arrays.

[0028] The index matching formula is: ; In the formula: i represents the index of the array of matched device names; h represents the model identifier of the currently connected VR device; D represents an array of device names (containing exact device names, device groups, or wildcards). |D| represents the length of the device name array; [0,|D|-1] represents the valid range of the index; ∈ indicates that an element belongs to a set; The configuration mapping formula is: C = M[i]; In the formula: C represents the configuration object that matches the current device; M represents the configuration mapping array; i represents the index of the array of matched device names.

[0029] The fault tolerance and degradation processing submodule comprises five parts: a matching result null value detection submodule, a wildcard fallback matching submodule, a system default configuration loading submodule, an error log recording submodule, and a configuration conflict priority handling submodule. The matching result null value detection submodule checks whether the configuration object returned by the mapping index positioning submodule is undefined, determining whether a degradation process needs to be triggered. The wildcard fallback matching submodule automatically searches for the configuration mapping corresponding to the element marked "allDevices" in the device name array when no exact or device group match is found, providing a fallback for general configurations. The system default configuration loading submodule loads predefined system-level default configurations (such as IPD range 50-80mm) when wildcard matching fails, ensuring that UI components can still render normally. The error log recording submodule records detailed information when degradation is triggered, including the device model, the reason for the matching failure, and the degradation path, facilitating subsequent configuration optimization. The configuration conflict priority handling submodule follows the priority rule of "exact match > device group match > wildcard match > default configuration" to avoid configuration conflicts caused by multi-path matching.

[0030] The formula for obtaining the fault tolerance and degradation configuration is: ; In the formula: C represents the device configuration object that is ultimately applied to the interface components; M represents the configuration mapping array; i represents the array index of the device names matched exactly or by the device group; D represents an array of device names; |D| represents the number of elements in the device name array; M w This represents the configuration object corresponding to the wildcard "allDevices"; w represents the index of the wildcard element in the device name array; C d This represents the system's predefined default configuration object; The wildcard index matching formula is: ; In the formula: w represents the index of the wildcard element in the device name array; D represents an array of device names; findIndex means returning the index of the first element in the array that meets the given condition; allDevices represents the wildcard identifiers agreed upon by the system; The result adaptation output submodule comprises five parts: configuration object parsing, UI component attribute binding, data format conversion, dynamic UI element generation, and configuration change monitoring. The configuration object parsing submodule decomposes the mapped configuration object into discrete attributes that can be directly used by UI components, such as extracting minimum and maximum range values ​​and unit information from the IPD adjustment configuration. The UI component attribute binding submodule directly associates the parsed attributes with the parameters of the corresponding UI components, such as setting the IPD range value as the value range of the slider component. The data format conversion submodule processes the display format of device data according to the format rules in the configuration, such as concatenating the firmware version number into a user-readable string according to a specified format. The dynamic UI element generation submodule determines whether to render specific UI elements based on the functional support in the configuration, such as automatically hiding the corresponding calibration button for devices that do not support eye tracking. The configuration change monitoring submodule continuously monitors the device connection status and configuration file updates, automatically triggering a re-adaptation process when a device switch or configuration change is detected, ensuring that the interface always displays the latest adapted configuration.

[0031] The UI rendering module internally includes a component dynamic generation unit, a configuration attribute binding unit, a dynamic UI element control unit, and a configuration change monitoring unit. The component dynamic generation unit creates the corresponding UI component based on the `typeName` in the configuration; the configuration attribute binding unit associates the properties of the mapped configuration object with the component's parameters; the dynamic UI element control unit determines whether to render specific UI elements based on the functionality supported in the configuration; and the configuration change monitoring unit monitors device connection status and configuration file updates, triggering component re-adaptation and rendering.

[0032] A dynamic configuration mapping method for a VR headset, wherein the method runs the aforementioned dynamic configuration mapping system for the VR headset during use.

[0033] From the above, we can conclude that: In this invention, the design of each sub-module of the intelligent mapping and matching module significantly reduces development and maintenance costs. The configuration validity verification sub-module checks the integrity of the configuration structure in advance to avoid runtime errors caused by invalid configurations; the device name matching sub-module uses inclusion relationship lookup instead of exact matching, supports device groups and wildcard forms, and eliminates the need to write a large amount of if-else code as in traditional solutions; the mapping index positioning sub-module uses array indexes to correspond one-to-one between devices and configurations, so adding a new device only requires adding the corresponding item to the configuration file, without modifying the core code, which significantly shortens the access cycle of new devices, reduces the workload of regression testing, and avoids the risk of configuration conflicts.

[0034] In this invention, the fault tolerance and degradation processing submodule automatically triggers a wildcard fallback or loads the default configuration when no matching configuration is found, ensuring that the interface components can always render normally and that the service will not be interrupted due to device matching failure. The result adaptation and output submodule parses the configuration object into attributes that the components can directly use, dynamically generates UI elements that conform to the device's functions, and automatically hides unsupported function options to prevent users from seeing irrelevant or unusable settings. In addition, the system supports real-time re-adaptation when switching devices without manual intervention from the user. The configuration update takes effect immediately, allowing users to have a smooth and consistent operating experience when using different VR headsets, thereby improving the robustness of the system and the user experience.

[0035] It should be noted that, in this document, relational terms such as "first" and "second" are used only to distinguish one entity or operation from another, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Furthermore, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0036] 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 dynamic configuration mapping system for a VR headset, characterized in that: include: Configure storage module, device detection module, intelligent mapping matching module and interface rendering module; The intelligent mapping matching module is internally configured with: a configuration validity verification submodule, a device name matching submodule, a mapping index positioning submodule, a fault tolerance and degradation processing submodule, and a result adaptation and output submodule. The output of the configuration storage module is connected to the configuration data input of the intelligent mapping matching module, providing it with an array of device names and an array of configuration maps; The output of the device detection module is connected to the device information input of the intelligent mapping and matching module, transmitting the model of the currently connected VR device. The configuration output of the intelligent mapping matching module is connected to the configuration input of the interface rendering module, and sends the adapted configuration object to the interface rendering module for dynamically generating the user interface.

2. The dynamic configuration mapping system for a VR headset as described in claim 1, characterized in that: The configuration storage module internally includes a configuration file storage unit, a device name array management unit, a configuration mapping array management unit, and a configuration item classification unit. The configuration file storage unit stores the deviceSettingConfig.js file, which contains configuration information for all devices in the system. The device name array management unit maintains the deviceName array, and array elements support three forms: device group expansion, exact device name, and wildcard. The configuration mapping array management unit maintains a corresponding mapping array, where each element is a configuration object that corresponds one-to-one with the index of the deviceName array. The configuration item classification unit divides the configuration into three categories according to sections: basic settings, display settings, and advanced settings, with each category containing multiple configuration items.

3. The dynamic configuration mapping system for a VR headset as described in claim 1, characterized in that: The device detection module internally includes a device connection status monitoring unit, a device model identifier acquisition unit, and a device status real-time update unit; the device connection status monitoring unit continuously checks whether the VR device is in a connected state; the device model identifier acquisition unit extracts the device model identifier from the connected device. The real-time device status update unit synchronizes changes in device connection or disconnection status to ensure that the system obtains the latest device information in a timely manner.

4. The dynamic configuration mapping system for a VR headset as described in claim 1, characterized in that: The configuration validity verification submodule comprises five parts: an input parameter validity verification module, a double array structure integrity verification module, an element format compliance detection module, a dependency compliance verification module, and an error handling mechanism module. The input parameter validity verification module verifies whether the passed configuration object contains the two core attributes, deviceName and mapping, and that both are non-empty arrays. The double array structure integrity verification module ensures that each device name or device group has a corresponding configuration mapping by comparing the lengths of the deviceName array and the mapping array. The formula for verifying the consistency of the lengths of the two arrays is as follows: ； In the formula: D represents an array of device names, which stores a collection of exact device names, device groups, or wildcards; M represents the configuration mapping array, which stores a collection of configuration objects that correspond one-to-one with the elements of the device name array. Length(·) returns the number of elements in the array.

5. The dynamic configuration mapping system for a VR headset as described in claim 1, characterized in that: The device name matching submodule comprises five parts: device name traversal submodule, inclusion relationship detection submodule, priority sorting submodule, wildcard processing submodule, and index return submodule. The device name traversal submodule is responsible for accessing each element in the original order of the device name array to ensure that the matching process follows the preset priority rules. The inclusion relationship detection submodule implements the core logic of non-exact matching by determining whether the current VR device model identifier is included in the array element.

6. The dynamic configuration mapping system for a VR headset as described in claim 1, characterized in that: The mapping index positioning submodule comprises five parts: a device name array traversal submodule, an inclusion relationship matching algorithm submodule, an array boundary verification submodule, a wildcard priority processing submodule, and a configuration mapping index acquisition submodule. The device name array traversal submodule is responsible for sequentially traversing each element in the deviceName array, supporting traversal of exact device names, device groups, and wildcards. The inclusion relationship matching algorithm submodule uses dynamic inclusion detection logic to determine the matching index by judging whether the current device model exists in a certain element of the deviceName array. The array boundary verification submodule checks whether the index is within a valid range during traversal to avoid out-of-bounds access. The wildcard priority processing submodule ensures that wildcard elements are selected only when there is no exact or device group match, following the rule of "exact priority, wildcard as a fallback." The configuration mapping index acquisition submodule directly retrieves the corresponding configuration object from the configuration mapping array mapping based on the matched index i, realizing the index association between the two arrays. The index matching formula is: ； In the formula: i represents the index of the array of matched device names; h represents the model identifier of the currently connected VR device; D represents an array of device names; |D| represents the length of the device name array; [0,|D|-1] represents the valid range of the index; ∈ indicates that an element belongs to a set; The configuration mapping formula is: C = M[i]; In the formula: C represents the configuration object that matches the current device; M represents the configuration mapping array; i represents the index of the array of matched device names.

7. The dynamic configuration mapping system for a VR headset as described in claim 1, characterized in that: The fault tolerance and degradation processing submodule includes five parts: matching result null value detection submodule, wildcard fallback matching submodule, system default configuration loading submodule, error log recording submodule, and configuration conflict priority processing submodule. The matching result null value detection submodule is responsible for checking whether the configuration object returned by the mapping index positioning submodule is undefined and determining whether a fallback process needs to be triggered; the wildcard fallback matching submodule automatically finds the configuration mapping corresponding to the element marked "allDevices" in the device name array when there is no exact or device group match; the system default configuration loading submodule loads the predefined system-level default configuration when wildcard matching fails. The error logging submodule records detailed information when a downgrade is triggered, including the device model, the reason for the matching failure, and the downgrade path; The formula for obtaining the fault tolerance and degradation configuration is: ； In the formula: C represents the device configuration object that is ultimately applied to the interface components; M represents the configuration mapping array; i represents the array index of the device names matched exactly or by the device group; D represents an array of device names; |D| represents the number of elements in the device name array; M w This represents the configuration object corresponding to the wildcard "allDevices"; w represents the index of the wildcard element in the device name array; C d This represents the system's predefined default configuration object; The wildcard index matching formula is: ； In the formula: w represents the index of the wildcard element in the device name array; D represents an array of device names; findIndex means returning the index of the first element in the array that meets the given condition; allDevices represents the wildcard identifiers agreed upon by the system.

8. The dynamic configuration mapping system for a VR headset as described in claim 1, characterized in that: The result adaptation output submodule includes five parts: configuration object parsing submodule, interface component attribute binding submodule, data format conversion submodule, dynamic UI element generation submodule, and configuration change listening submodule.

9. The dynamic configuration mapping system for a VR headset as described in claim 1, characterized in that: The interface rendering module internally includes a component dynamic generation unit, a configuration attribute binding unit, a dynamic UI element control unit, and a configuration change listening unit; the component dynamic generation unit creates the corresponding interface component based on the typeName in the configuration; the configuration attribute binding unit associates the properties of the mapped configuration object with the parameters of the component; The dynamic UI element control unit decides whether to render specific UI elements based on the functional support in the configuration. The configuration change monitoring unit monitors device connection status and configuration file updates, triggering component re-adaptation and rendering.

10. The dynamic configuration mapping method for a VR headset as described in claim 1, characterized in that: The method, when in use, operates a dynamic configuration mapping system based on the VR head-mounted display device according to any one of claims 1 to 9.

Images