Virtual fusion simulation driving control method, device and system, equipment and medium

Abstract

The present application discloses a virtual-reality fusion simulation driving control method, device and virtual-reality fusion simulation driving system, as well as electronic equipment, computer storage medium and computer program product, wherein the virtual-reality fusion simulation driving control method includes: in response to the connected driving simulation device, loading the driver plug-in corresponding to the connected driving simulation device; based on the driver plug-in, mapping the operation data sent by the driving simulation device through the physical interface to the standard operation parameters of the atomic interface, so that the atomic interface sends the standard operation parameters to the virtual driving software; and / or, based on the driver plug-in, mapping the standard control parameters of the atomic interface to the control data of the physical interface sent to the driving simulation device, the standard control parameters are sent by the virtual driving software to the atomic interface. The technical solution provided by the present application can reduce the development cost of the driving simulation system.

Description

Technical Field

[0001] The present application belongs to the field of simulation driving control technology, and in particular relates to a virtual-reality fusion simulation driving control method, device and virtual-reality fusion simulation driving system, as well as electronic equipment, computer-readable storage medium and computer program product. Background Art

[0002] With the development of digital economy and information technology, simulation has been widely used in vehicle driving experience. The virtual-reality fusion simulation driving system can simulate the authenticity of vehicle dynamics, the authenticity of simulator operation and the authenticity of driving environment. In this system, on the one hand, in order to improve the simulation effect, various types or models of driving simulation equipment are often used. The above-mentioned driving simulation equipment can include vibration seats, active seat belts, six-degree-of-freedom equipment, speed fans and other experience equipment, as well as various simulators and other control equipment generated by different manufacturers; on the other hand, various virtual driving software will be set up on the software simulation platform of the virtual-reality fusion simulation driving system.

[0003] For various virtual driving software installed on the software simulation platform, in order to transmit data to driving simulation devices that support different types of physical interfaces, such as when collecting data or sending data, different virtual driving software needs to be developed separately for physical driving simulation devices so that they can transmit data with the driving simulation devices. Therefore, the existing technology has the defect of high development cost of virtual-real fusion simulation driving system. Summary of the invention

[0004] The present application aims to solve at least one of the technical problems existing in the prior art. To this end, the present application proposes a virtual-reality fusion simulation driving control method, device and virtual-reality fusion simulation driving system, as well as an electronic device, a computer-readable storage medium and a computer program product, which can reduce the development cost of the virtual-reality fusion simulation driving system.

[0005] In a first aspect, the present application provides a virtual-reality fusion simulation driving control method, comprising:

[0006] In response to the connected driving simulation device, loading a driver plug-in corresponding to the connected driving simulation device;

[0007] Based on the driver plug-in, the operation data sent by the driving simulation device through the physical interface is mapped into standard operation parameters of the atomic interface, so that the atomic interface sends the standard operation parameters to the virtual driving software; and / or,

[0008] Based on the driver plug-in, the standard control parameters of the atomic interface are mapped to the control data of the physical interface sent to the driving simulation device, and the standard control parameters are sent to the atomic interface by the virtual driving software.

[0009] In some embodiments, the physical interface configured by the driving simulation device includes at least two types, and the method further includes:

[0010] A driver plug-in is created according to the interface protocol of the atomic class interface and the interface protocols of at least two types of physical interfaces, and each type of physical interface corresponds to a driver plug-in.

[0011] In some embodiments, loading a driver plug-in corresponding to the connected driving simulation device includes:

[0012] A driver plug-in corresponding to the type of the physical interface of the driving simulation device is loaded.

[0013] In some embodiments, the atomic class interface is a preconfigured interface, or a custom interface.

[0014] In some embodiments, the atomic class interface includes at least one of an axis type atomic class interface, a button type atomic class interface, and a switch type atomic class interface.

[0015] In some embodiments, the standard operating parameters and / or standard control parameters of the axis-type atomic class interface are a predetermined range of values ​​that vary continuously;

[0016] The standard operation parameters and / or standard control parameters of the button type atomic class interface are a predetermined number of button state values;

[0017] The standard operating parameters and / or standard control parameters of the switch type atomic class interface are predetermined switch identification values.

[0018] In some embodiments, mapping the operation data sent by the driving simulation device through the physical interface to the standard operation parameters of the atomic class interface based on the driver plug-in includes at least one of the following:

[0019] Converting the shaft operation data sent by the driving simulation device through the physical interface into a continuously changing predetermined value range based on the driver plug-in;

[0020] Converting the key operation data sent by the driving simulation device through the physical interface into a predetermined number of key state values ​​based on the driver plug-in;

[0021] The switch operation data sent by the driving simulation device through the physical interface is converted into a predetermined switch identification value based on the driver plug-in.

[0022] In some embodiments, mapping the standard control parameters of the atomic class interface to control data sent to the physical interface of the driving simulation device based on the driver plug-in includes at least one of the following:

[0023] Converting a continuously changing predetermined value range into axis control data sent to a driving simulation device based on a driver plug-in;

[0024] Converting a predetermined number of key state values ​​into key control data sent to the driving simulation device based on the driver plug-in;

[0025] The predetermined switch identification value is converted into switch control data sent to the driving simulation device based on the driver plug-in.

[0026] In some embodiments, the axle operation data includes at least one of steering wheel operation data and pedal operation data, and the axle control data includes at least one of steering wheel control data and pedal control data;

[0027] The key operation data includes at least one of speaker operation data and game button operation data, and the key control data includes at least one of speaker control data and game button control data;

[0028] The switch operation data includes at least one of turn signal switch operation data and knob switch operation data, and the switch control data includes at least one of turn signal switch control data and knob switch control data.

[0029] In some embodiments, it also includes:

[0030] Create shared memory;

[0031] The atomic class interface sends standard operating parameters to the virtual driving software via shared memory, and / or,

[0032] The atomic class interface receives standard control parameters sent by the virtual driving software through shared memory, and / or,

[0033] The shared content is also used to store the interface protocol of the driver plug-in and the atomic class interface.

[0034] In some embodiments, it also includes:

[0035] In response to the disconnected driving simulation device, the driver plug-in corresponding to the connected driving simulation device is uninstalled.

[0036] In some embodiments, it also includes:

[0037] Based on the driver plug-in, the device description information of the connected driving simulation device is obtained and displayed, and the device description information includes at least one of the device model, device identification and device manufacturer identification. In the second aspect, a virtual-reality fusion simulation driving control device is provided, including:

[0038] A plug-in loading module, configured to load a driver plug-in corresponding to the connected driving simulation device in response to the connected driving simulation device;

[0039] a mapping module, for mapping the operation data sent by the driving simulation device through the physical interface to standard operation parameters of the atomic interface based on the driver plug-in, so that the atomic interface sends the standard operation parameters to the virtual driving software; and / or,

[0040] It is used to map the standard control parameters of the atomic interface into control data sent to the physical interface of the driving simulation device based on the driver plug-in, and the standard control parameters are sent to the atomic interface by the virtual driving software.

[0041] In a third aspect, the present application provides an electronic device comprising a processor and a memory, wherein the processor is used to execute a computer program in the memory, and the computer program can execute the virtual-reality fusion simulation driving control method described in the first aspect.

[0042] In a fourth aspect, the present application provides a virtual-reality fusion simulation driving system, comprising at least one driving simulation device, the virtual-reality fusion simulation driving control device as described above connected to the at least one driving simulation device, the electronic device as described above, and a software simulation platform, wherein at least one virtual driving software is arranged on the software simulation platform.

[0043] In a fifth aspect, the present application provides a computer-readable storage medium for storing a computer program, which can execute the virtual-reality fusion simulation driving control method described in the second aspect.

[0044] In a sixth aspect, the present application provides a computer program product, which is used to execute the virtual-reality fusion simulation driving control method described in the second aspect.

[0045] The technical solution provided by the embodiment of the present application is based on the driver plug-in that can map the operation data sent by the driving simulation device to the standard operation parameters of the atomic interface, and / or, map the standard control parameters of the atomic interface to the control data sent to the driving simulation device, so that when the driving simulation device communicates with each virtual driving software, it can be considered that it is communicating with the standardized atomic interface, and the virtual driving software does not communicate with each different type of virtual driving device, and it also communicates with the standardized atomic interface. Through the above technical solution, the virtual driving software does not need to care about the type of interface protocol of the physical interface supported by the access driving simulation device. At the same time, the driving simulation device does not need to perform access adaptation control for which virtual driving software is accessed, thereby simplifying the access process of the driving simulation device. In addition, there is no need to develop a driver plug-in for each virtual driving software separately, so as to reduce the development cost of the driving simulation system.

[0046] Additional aspects and advantages of the present application provided by the embodiments of the present application will be given in part in the description below, and in part will become apparent from the description below, or will be learned through the practice of the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0047] The above and / or additional aspects and advantages of the present application will become apparent and easily understood from the description of the embodiments in conjunction with the following drawings, in which:

[0048] Figure 1 This is a structural schematic diagram of a virtual-reality fusion simulation driving system in an embodiment of the present application;

[0049] Figure 2 A flowchart of a virtual-reality fusion simulation driving control method in an embodiment of the present application;

[0050] Figure 3 A flowchart of an initialization process of a virtual-reality fusion simulation driving system in an embodiment of the present application;

[0051] Figure 4 This is a structural schematic diagram of a virtual-reality fusion simulation driving control device in an embodiment of the present application;

[0052] Figure 5 It is a schematic diagram of the structure of an electronic device in an embodiment of the present application. DETAILED DESCRIPTION

[0053] The embodiments of the present application will be described in more detail below with reference to the accompanying drawings. Although certain embodiments of the present application are shown in the accompanying drawings, it should be understood that the present application can be implemented in various forms and should not be construed as being limited to the embodiments described herein. Instead, these embodiments are provided to provide a more thorough and complete understanding of the present application. It should be understood that the drawings and embodiments of the present application are only for exemplary purposes and are not intended to limit the scope of protection of the present application.

[0054] It should be understood that the various steps described in the method implementation of the present application can be performed in different orders and / or performed in parallel. In addition, the method implementation may include additional steps and / or omit the steps shown. The scope of the present application is not limited in this respect.

[0055] The term "including" and its variations used herein are open inclusions, i.e., "including but not limited to". The term "based on" means "based at least in part on". The term "one embodiment" means "at least one embodiment"; the term "another embodiment" means "at least one additional embodiment"; the term "some embodiments" means "at least some embodiments". The relevant definitions of other terms will be given in the following description.

[0056] It should be noted that the concepts such as "first" and "second" mentioned in this application are only used to distinguish different devices, modules or units, and are not used to limit the order or interdependence of the functions performed by these devices, modules or units.

[0057] It should be noted that the modifications of "one" and "plurality" mentioned in the present application are illustrative rather than restrictive, and those skilled in the art should understand that unless otherwise clearly indicated in the context, it should be understood as "one or more".

[0058] As described in the background technology, in some virtual-reality fusion simulation driving systems, it is necessary to develop a "driver program" for each virtual driving software so that the virtual driving software can control the driving simulation device through the above-mentioned "driver program". However, with the continuous development and improvement of the virtual-reality fusion simulation driving system, more and more driving simulation devices can be connected therein, and the types of physical interfaces supported by these driving simulation devices are also increasing. Each type of physical interface requires a separate "driver program" development; and when multiple virtual driving software are set on the software simulation platform of the virtual-reality fusion simulation driving system, it is necessary to repeat the "driver program" development for each virtual driving software, which will lead to excessively high development costs of the virtual driving software.

[0059] In order to solve the above technical problems, an embodiment of the present application provides a technical solution. Figure 1 Schematic diagram of the structure of a virtual-reality fusion simulation driving system in an embodiment of the present application. Figure 1 As shown, in the virtual-reality fusion simulation driving system provided in the technical solution, a unified hardware access plug-in interface is set, and each driving simulation device can be connected to the software simulation platform through the hardware access plug-in interface. Specifically, the above-mentioned hardware access plug-in interface can be a virtual-reality fusion simulation driving control device 1, and in the virtual-reality fusion simulation driving control device, it can include a plug-in management module 11 and a mapping module 12, wherein at least two driver plug-ins 121 can be set in the mapping module 12, and the mapping module 12 can map the operation data sent by the driving simulation device through the physical interface to the standard operation parameters of the atomic interface based on the driver plug-in 121, so that the atomic interface can send the standard operation parameters to the virtual driving software, and / or map the standard control parameters of the atomic interface to the control data of the physical interface sent to the driving simulation device, and the standard control parameters are sent by the virtual driving software to the atomic interface. As shown in FIG. Figure 1 As shown, at least one virtual driving software may be provided on the software simulation platform, wherein the number of the virtual driving software may be multiple, for example Figure 1The first virtual driving software and the second virtual driving software shown in the figure can be continuously increased as the user's demand for simulation driving training increases.

[0060] Figure 2 This is a flow chart of a virtual-reality fusion simulation driving control method in an embodiment of the present application, which can be applied to Figure 1 The virtual-reality fusion simulation driving system shown in the figure may specifically include the following steps:

[0061] Step 101: In response to a connected driving simulation device, a driver plug-in corresponding to the connected driving simulation device is loaded;

[0062] In the embodiment of the present application, after the driver plug-in is developed in advance, during the use of the virtual-reality fusion simulation driving system, the connected driving simulation device is identified, and then the driver plug-in is loaded according to the situation of the connected driving simulation device. Specifically, the developed driver program can be stored in the plug-in database, and then in response to the access notification of each driving simulation device, the driver plug-in is obtained from the plug-in database and loaded, so that the driver plug-in can realize the communication between the driving simulation device and the virtual driving software in the subsequent process.

[0063] Step 102: based on the driver plug-in, the operation data sent by the driving simulation device through the physical interface is mapped to the standard operation parameters of the atomic class interface, so that the atomic class interface sends the standard operation parameters to the virtual driving software; and / or, based on the driver plug-in, the standard control parameters of the atomic class interface are mapped to the control data of the physical interface sent to the driving simulation device, and the standard control parameters are sent by the virtual driving software to the atomic class interface.

[0064] In an embodiment of the present application, based on the driver plug-in, the operation data sent by the driving simulation device can be mapped to the standard operation parameters of the atomic interface, and / or the standard control parameters of the atomic interface can be mapped to the control data sent to the driving simulation device, so that when the driving simulation device communicates with each virtual driving software, it can be considered that it is communicating with the standardized atomic interface, and the virtual driving software does not communicate with each different type of virtual driving device, and it also communicates with the standardized atomic interface. Through the above technical solution, the virtual driving software does not need to care about the type of interface protocol of the physical interface supported by the access driving simulation device. At the same time, the driving simulation device does not need to perform access adaptation control for which virtual driving software is accessed, thereby simplifying the access process of the driving simulation device. In addition, there is no need to develop a driver plug-in for each virtual driving software separately, thereby reducing the development cost of the driving simulation system.

[0065] In addition, the above-mentioned driver plug-in can realize communication connection with multiple driving simulation devices using the same type of physical interface. There is no need to develop "drivers" for each driving simulation device for each virtual driving software separately. Instead, a one-time driver plug-in can be developed to meet the communication access of all driving simulation devices of the same type, thereby avoiding unnecessary driver plug-in development and reducing the development cost of the virtual-reality fusion simulation driving system.

[0066] In the above embodiment, the driver plug-in is mainly used to realize the data mapping between the physical interface connected to the driving simulation device and the standardized atomic interface. Therefore, each driver plug-in can be created according to the interface protocol of the atomic interface and the interface protocol of at least two types of physical interfaces. Each type of physical interface corresponds to a driver plug-in. Figure 2 In step 101 shown, the step of loading the driver plug-in corresponding to the connected driving simulation device may be specifically as follows:

[0067] According to the type of the physical interface of the connected driving simulation device, a driver plug-in corresponding to the type of the physical interface is loaded.

[0068] The above-mentioned driver plug-in can be pre-created and stored in the plug-in database, or it can be created in real time according to the type of physical interface of the connected driving simulation device, which is not limited in the embodiments of the present application.

[0069] In the embodiment of the present application, the atomic class interface is a plug-in program that abstracts the functional type of operating data or control parameters that may be generated during driving, and supports a standard operating data and / or control parameter. If the pre-configured atomic class interface does not match the type of operating data and / or control parameters included in the driving simulation device to be connected, a new atomic class interface can be created in a customized manner.

[0070] The operating data in the above embodiments mainly refers to the operating data fed back by the driving simulation device, which is generated by the user by operating the driving simulation device, and can be collected and reported by sensors; and the control parameters mainly refer to the control parameters generated on the virtual driving software for each simulated driving device. The above control data and control parameters are both applied to the driving simulation device, and the types included can be consistent, for example, they can include axis types, button types and switch types, and the atomic class interface is also a plug-in program that abstracts the functional types of the above types of data. Therefore, the atomic class interface in the embodiments of the present application may also include at least one of an axis type atomic class interface, a button type atomic class interface and a switch type atomic class interface.

[0071] In some embodiments, for the axis type atomic class interface, the operation data or control data therein can be an angle range value, such as the angle operation data or angle control data generated on the driving simulation device such as the steering wheel and the pedals. According to the driving simulation device and the interface protocol of its physical interface, the angle value can be between [0, 360°], [0, 65535], or [-1, 1]. These situations are all possible. Therefore, the corresponding standard operation parameters and / or standard control parameters can be a predetermined numerical range that changes continuously. In the embodiment of the present application, it can be standardized to a value between [-1, 1].

[0072] Atomic interface of button type, in which the operation data or control data can usually be a state value. Generally, the button is triggered once and the button state value is modified once to indicate the state of the button. The button can be a speaker button, a game button, etc., which can be operated to generate corresponding operation data, or controlled to form button control data. The value range of this type of data is indefinite, for example, it can be state values ​​such as 00, 01, 0100, 0001, etc.; therefore, the corresponding standard operation parameters and / or standard control parameters can be a predetermined number of button state values ​​to indicate different states, and 00 is uniformly used to indicate on and 01 is uniformly used to indicate off.

[0073] The switch type atomic class interface will send switch type data only when the switch is triggered. It is necessary to identify which switch is triggered. For example, if two switches are included, the operation data will be sent continuously as long as the products of different models or manufacturers are triggered. Different information can be used to represent it. For example, the letter A represents switch 1, the letter B represents switch 2, or 00 represents switch 1, 01 represents switch 2, and so on. The same situation also exists for the above control data; therefore, in the application embodiment, the above standard operation parameters and / or standard control parameters are predetermined switch identification values, and 00 is uniformly used to represent switch 1 and 01 represents switch 2.

[0074] In the case where the standard operating parameters and / or standard control parameters of each type of atomic class interface are set as above, Figure 2 In step 102 of the illustrated embodiment, the operation data sent by the driving simulation device through the physical interface is mapped to standard operation parameters of the atomic class interface based on the driver plug-in, including at least one of the following:

[0075] Based on the driver plug-in, the shaft operation data sent by the driving simulation device through the physical interface is converted into a predetermined value range that changes continuously, for example, the operation data with a value between [0, 65535] is converted into a standard operation parameter with a value between [-1, 1];

[0076] Based on the driver plug-in, the key operation data sent by the driving simulation device through the physical interface is converted into a predetermined number of key state values; for example, the standard key on state 0100 is converted into 01, which is one of the predetermined number of key state values.

[0077] The switch operation data sent by the driving simulation device through the physical interface is converted into a predetermined switch identification value based on the driver plug-in; for example, the identification value B of the identification switch 2 is converted into 01, which is one of the predetermined switch identification values.

[0078] Correspondingly, for Figure 2 In step 102 of the illustrated embodiment, mapping the standard control parameters of the atomic class interface to control data of the physical interface sent to the driving simulation device based on the driver plug-in may include at least one of the following:

[0079] Based on the driver plug-in, the continuously changing predetermined numerical range is converted into the axis control data sent to the driving simulation device; for example, the standard control parameter with a value between [-1, 1] is converted into the control data with a value between [0, 65535].

[0080] Based on the driver plug-in, a predetermined number of key status values ​​are converted into key control data sent to the driving simulation device; for example, the standard control parameter 01 representing the key on state is converted into 0100, which is the key control data sent to the driving simulation device, indicating that the control key is on.

[0081] The predetermined switch identification value is converted into switch control data sent to the driving simulation device based on the driver plug-in. For example, 01 in the predetermined switch identification value is converted into identification value B, and the identification value B identifies switch 2.

[0082] In the embodiment of the present application, the shaft operation data may be for a driving simulation device such as a steering wheel or a pedal, and therefore, the shaft operation data includes at least one of steering wheel operation data and pedal operation data, and the shaft control data includes at least one of steering wheel control data and pedal control data;

[0083] The button device may be a speaker or a game button, and the game button may be a button on a game steering wheel, etc., so the button operation data includes at least one of speaker operation data and game button operation data, and the button control data includes at least one of speaker control data and game button control data;

[0084] The switch may be a turn signal switch or a knob switch. The turn signal switch may include a left turn signal switch and a right turn signal switch. The knob switch may be a light knob of a sewing machine modification part, etc. Therefore, the switch operation data includes at least one of the turn signal switch operation data and the knob switch operation data, and the switch control data includes at least one of the turn signal switch control data and the knob switch control data.

[0085] In the above embodiments of the present application, for driving simulation devices of different manufacturers and equipment models, the interface protocols of the physical interfaces supported are not the same. Therefore, the formats of the operating data generated or the control data supported will also be different. The embodiments of the present application are configured to map the operating data of the above-mentioned different formats into standard operating parameters of the atomic interface, and map the standard control parameters of the atomic standard interface into control data supported by the interface protocol of the physical interface of each driving simulation device, thereby realizing support for physical interfaces of different interface protocols. For virtual driving software, it only needs to support standard operating parameters and standard control parameters to realize support for driving simulation devices of different manufacturers and equipment models, and for the development of driver plug-ins, it only needs to create corresponding driver plug-ins for different types of physical interfaces.

[0086] In the embodiment of the present application, the atomic class interface needs to send standard operating parameters to the virtual driving software, and / or the atomic class interface needs to receive standard control parameters sent by the virtual driving software. In the embodiment of the present application, the standard operating parameters or standard control parameters can be transmitted by means of shared memory.

[0087] Specifically, the above method may further include:

[0088] Create a shared memory, and the atomic class interface sends standard operating parameters to the virtual driving software through the shared memory, and / or the atomic class interface receives standard control parameters sent by the virtual driving software through the shared memory. The above-mentioned shared memory is an inter-process communication mechanism, which allows multiple processes to access the same memory area, thereby realizing data sharing and transmission. This method can avoid data duplication between different processes, and therefore can effectively improve the efficiency of data exchange.

[0089] Furthermore, the above-mentioned shared content can also be used to store driver plug-ins and interface protocols of atomic class interfaces, so that in the virtual-reality fusion driving control process, the interface protocols and driver plug-ins of the above-mentioned atomic class interfaces can be obtained by accessing the shared memory, which not only saves computing and storage resources, but also has the technical effect of high communication efficiency.

[0090] In addition, the above technical solution can also be implemented using the Message Queuing Telemetry Transport (MQTT) communication interface. MQTT is a lightweight message transmission protocol based on the publish / subscribe model, which is built on the TCP / IP protocol. MQTT distinguishes different message channels by topics. You can subscribe to specific topics to receive messages, or publish messages to topics. Topics usually have a hierarchical structure, with slashes separating different levels. In addition, MQTT also supports the use of wildcards to subscribe to multiple topics, which increases the flexibility of the protocol; and by selecting the appropriate QoS level, MQTT can meet the requirements for message delivery reliability in different scenarios.

[0091] In the above embodiment of the present application, the driver plug-in 121 is respectively configured in a one-to-one correspondence with the type of physical interface used by the driving simulation device, for example, Figure 1 As shown, when three driver plug-ins 121 are included, namely, driver plug-in A, driver plug-in B and driver plug-in C, they correspond to physical interfaces of type A, type B and type C. After the driver plug-in 121 establishes a communication connection with the driving simulation device through the physical interface, the driver plug-in 121 can perform data transmission with the driving simulation device in communication connection therewith.

[0092] In an embodiment of the present application, the driver plug-in 121 is capable of communicating with different virtual driving software and transmitting data, so as to map the operation data collected from each driving simulation device into standard operation parameters and send them to the above-mentioned virtual driving software, or convert the standard control parameters issued by the virtual driving software into control data and then send them to the driving simulation device.

[0093] Therefore, in the embodiment of the present application, an atomic class interface is set to achieve a communication connection with the virtual driving software set on the software simulation platform. The atomic class interface may include the above-mentioned axis type atomic class interface, button type atomic class interface and switch type atomic class interface, etc.

[0094] In some embodiments, the types of physical interfaces that can be used for driving simulation devices are different, mainly their interface protocols, which can also be called different communication protocol types. The driver plug-in in the embodiment of the present application is created based on the interface protocol of the atomic class interface and the interface protocol of the physical interface. Specifically, the above-mentioned interface protocol types may include at least one of the USB communication protocol, HID communication protocol, TCP communication protocol, UDP communication protocol, Dinput communication protocol, Xinput communication protocol and serial communication protocol. By creating a corresponding driver plug-in for each type of physical interface, support for driving simulation devices using different types of interface protocols can be achieved.

[0095] In the above embodiment, for example Figure 2 In step 101 shown in FIG. 1 , a driver plug-in corresponding to the connected driving simulation device can be loaded in response to the connected driving simulation device. This step can be performed as follows: Figure 1 The plug-in management module 11 in the virtual-reality fusion simulation driving system shown is implemented. The plug-in management module 11 can also uninstall the driver plug-in corresponding to the connected driving simulation device in response to the disconnected driving simulation device.

[0096] In the embodiment of the present application, the plug-in management module 11 may specifically use an aggregate catalog and a composition container to dynamically manage the driver plug-in 121, such as loading or unloading the driver plug-in.

[0097] In some embodiments, if the virtual-reality fusion simulation driving system is started, each driver plug-in 121 will be initialized. During the initialization process, each driver plug-in needs to perform a driving simulation device detection to determine the driving simulation device to establish a communication connection. Specifically, it can detect whether there is a driving simulation device connected to it for communication, and when a driving simulation device connected to it is detected, a communication connection with the above-mentioned driving simulation device is established.

[0098] Specifically, for different types of driving simulation devices, the detection method may be different. As recorded in the above embodiments, the driving simulation device may be a hardware device using any one of the USB communication protocol, HID communication protocol, UDP communication protocol, TCP communication protocol, Dinput communication protocol, Xinput communication protocol and serial port communication protocol.

[0099] For example, for hardware devices using the USB communication protocol, such as hardware devices such as game steering wheels or controllers, they can be automatically detected when the virtual-reality fusion simulation driving system is started, for example, using the SetupAPI of the Windows system or the libusb of the Linux system for inspection, and communicating with them through the corresponding driver plug-in to transmit the hardware data collected from the hardware device; for hardware devices using the Dinput communication protocol, such as game controllers or joysticks, when the system starts, the Directinput API in the driver plug-in can be used to detect the connected hardware device, and after the hardware device is detected, it can be communicated with it through the Directinput API to transmit the hardware data collected from the hardware device; for hardware devices using the serial port communication protocol, such as commonly used industrial equipment or sensors, they can be automatically detected when the virtual-reality fusion simulation driving system is started, and communicated with them through the corresponding driver plug-in to transmit the hardware data collected from the hardware device; for hardware devices using the UDP communication protocol, when the virtual-reality fusion simulation driving system is started, the corresponding driver plug-in can be used to listen to its port to realize device detection, and communicate with it through the corresponding driver plug-in to receive the UDP data packet sent by it.

[0100] In some embodiments, the above-mentioned driver plug-in 121 is also used to obtain the description information of the driving simulation device that establishes the communication connection, and the description information may include at least one of the device model, device identification and device manufacturer. For example, for a certain model of simulated steering wheel device, it can be connected via USB. After detecting and identifying the simulated steering wheel in the above-mentioned manner during the initialization process, the device descriptor of the simulated steering wheel can be obtained. The device descriptor includes detailed device description information, such as at least one of the device model, device identification and device manufacturer identification. After reading the above-mentioned device description information, the device can be configured according to the device description information to prepare for reading hardware data. For example, for a simulated steering wheel, it can be to read steering wheel data. For another type of simulated steering wheel, it can be to detect whether there is a corresponding simulated steering wheel when the driver plug-in 121 is started, and multiple communication connections can be attempted. After the communication connection is successful, the status of the corresponding driver plug-in is marked as available.

[0101] In the above embodiment, after each driver plug-in 121 detects the driving simulation device that is communicatively connected to it, it may mark the state of the driver plug-in 121 as available, that is, the driver plug-in has a driving simulation device that is communicatively connected to it.

[0102] In some embodiments, an information display module may be provided, which may include an information display interface, and may generate plug-in display information and display it on the information display interface. Specifically, the plug-in display information includes at least one of the following:

[0103] The status of the driver plug-in, the driving simulation device that is connected to the driver plug-in for communication, and the description information of the driving simulation device.

[0104] As described above, the status of the driver plug-in can indicate whether the driver plug-in has a driving simulation device that is communicatively connected to it. If so, it indicates that the driver plug-in is available; the driving simulation device that establishes a communication connection with the driver plug-in, mainly after the driver plug-in is communicatively connected to the driving simulation device, can display the various available driver plug-ins and the driving simulation devices with which the communication connection is established; in some cases, the descriptive information of the driving simulation device that is communicatively connected to the driver plug-in can be displayed to make the detailed information of the driving simulation device clearer.

[0105] In some embodiments, when the driver plug-in 121 establishes a communication connection with one or more driving simulation devices, the activation state of the driving simulation device can also be set. For example, the driving simulation device can be set to an enabled or disabled state through the above-mentioned information display interface, so that the driver plug-in can collect the hardware data of the driving simulation device in the enabled state, and the hardware data of different driving simulation devices can be switched by setting the enabled state or disabled state of the driving simulation device; or at least two driving simulation devices can be enabled at the same time to obtain the hardware data on multiple driving simulation devices. By performing the above settings on multiple driver plug-ins, multiple types of hardware data can be obtained.

[0106] The technical solution provided by the embodiment of the present application can collect operation data or send the control data generated by each virtual driving software to it after completing the above initialization process and completing the identification and communication connection establishment process of the driving simulation device by the driver plug-in 121, wherein the operation data can be generated by the sensor module set on each simulation driving device. For example, for a game steering wheel with a force feedback function, it can establish a hardware connection through a USB interface and transmit data through the HID communication protocol. For the above-mentioned game steering wheel, multiple sensor modules can be set on it to detect the rotation or pressing of the steering wheel; and a force feedback module can be set to generate a reaction force; the operation data generated on the above-mentioned sensor modules can be transmitted to the driver plug-in through the HID communication protocol, and finally sent to the virtual driving software on the software simulation platform; and the control data obtained according to various application scenarios on the virtual driving software, such as force feedback data, can also be sent to the force feedback module through the driver plug-in to generate a reaction force.

[0107] The above sensor modules can detect the steering wheel angle, rotation and button pressing to obtain the operation data, and report it in real time through communication protocols such as USB, serial port, UDP or TCP. For the key data, after the software simulation platform receives it, it will update the key data according to the specific key configuration, key switch type, etc. In addition, for some customized driving simulation equipment, filters or voltage regulators can also be used to process hardware data, or to calibrate sensor data, etc.

[0108] For driving simulation devices such as pedals, the virtual-reality fusion simulation driving system using the USB communication interface can identify the pedal through a driver plug-in and establish a communication connection between the driver plug-in 121 and the pedal, thereby reading the operating data of the pedal through the USB communication interface. The driver plug-in sends the above-mentioned pedal operating data to the virtual driving software on the software simulation platform, such as driving game software. The driving game software can also drive the plug-in to realize data interaction with the pedal and realize various operations in the driving game.

[0109] In the embodiment of the present application, the operation data can be directly collected through the driver plug-in 121, which can solve the problem of being unable to collect the operation data of the virtual driving device after losing focus during the development of the virtual driving software.

[0110] In an embodiment of the present application, after the above-mentioned operation data is obtained, it can be displayed in real time on the data display interface, so that the user can see the operation data more intuitively and verify the accuracy of the operation data.

[0111] In an embodiment of the present application, by respectively setting driver plug-ins 121 corresponding to different types of physical interfaces, data interaction with a driving simulation device using the type of physical interface is achieved, operation data is collected from the corresponding driving simulation device, and control data is transmitted to the corresponding driving simulation device. In the specific implementation process, although each driver plug-in corresponds to a driving simulation device using the same type of physical interface, the manufacturers, device models, etc. of each driving simulation device may be different, so that the supported operation data or control data formats are not consistent. Based on the driver plug-in 121, the operation data sent by the driving simulation device through the physical interface can be mapped to the standard operation parameters of the atomic interface, so that the atomic interface sends the standard operation parameters to the virtual driving software; and / or, based on the driver plug-in, the standard control parameters of the atomic interface are mapped to the control data of the physical interface sent to the driving simulation device, and the standard control parameters are sent by the virtual driving software to the atomic interface.

[0112] In combination with the technical solutions described in the above embodiments, Figure 3FIG. 1 is a flow chart of the initialization process of the virtual-reality fusion simulation driving system in the embodiment of the present application. Figure 3 As shown, in the embodiment of the present application, the virtual-reality fusion simulation driving system may mainly include the following steps during the initialization process when it is powered on:

[0113] Step 201, traverse each driver plug-in 121 in turn, if a driver plug-in that has not been initialized is found, select the driver plug-in 121 and execute step 202, if all driver plug-ins 121 have completed initialization, execute step 204;

[0114] Step 202, execute initialization of the driver plug-in 121 selected in step 201. The initialization step includes the above-mentioned detection and identification of the driving simulation device. For the specific detection method, reference can be made to the records in the above-mentioned embodiments. For example, for USB devices, detection can be performed based on the VID or PID of each device; for Dinput devices, detection can be performed based on the device name query API; for serial port devices, judgment can be made by linking to the specified Com port; for UDP devices, judgment can be made based on the device's own protocol as to whether there is a communication connection.

[0115] After the above detection and identification of the corresponding driving simulation device, a communication connection can be established between the driver plug-in 121 and the driving simulation device, and according to the technical scheme in the above embodiment, the operation data sent by the driving simulation device through the physical interface can be mapped to the standard operation parameters of the atomic interface based on the driver plug-in, so that the standard operation parameters can be sent to the virtual driving software by the atomic interface; and / or, the standard control parameters of the atomic interface can be mapped to the control data of the physical interface sent to the driving simulation device based on the driver plug-in, and the standard control parameters are sent to the atomic interface by the virtual driving software.

[0116] In this process, description information of the driving simulation device may also be obtained. For a specific explanation of the description information of the driving simulation device, reference may be made to the relevant content in the above embodiments.

[0117] Step 203: If, during the initialization process of the driver plug-in in the above steps, a driving simulation device that establishes a communication connection with the driver plug-in is detected, the driver plug-in can be considered to have completed initialization. If no driving simulation device that establishes a communication connection is detected, the driver plug-in cannot complete initialization, and an abnormality can be prompted, the instantiation operation of the driver plug-in is stopped, and the driver plug-in can be recorded in the form of a log that the driver plug-in cannot detect a driving simulation device that can communicate with it. After a driver plug-in is initialized, step 201 can be executed again.

[0118] Step 204: System initialization ends.

[0119] In the technical solution provided by the embodiment of the present application, the driver plug-in 121 can be enabled during the above-mentioned initialization process, and a communication connection between the driver plug-in 121 and the driving simulation device is established; after the communication connection is established, the driver plug-in 121 can collect the operation data of each driving simulation device on the one hand, and then convert the operation data and send it to the virtual driving software on the software simulation platform. On the other hand, the virtual driving software can generate control data, such as various virtual driving software developed using development platforms such as Unity and SCANNet, which can generate control data such as vehicle posture data and driving status data, and the driver plug-in sends the above control data to each driving simulation device, and the above software data can be adapted to different simulators, such as the above-mentioned steering wheel, pedals, six-degree-of-freedom devices or customized simulators; specifically, the above-mentioned control data can realize the movement of six-degree-of-freedom devices at different speeds, emergency stops or acceleration states, or force feedback of steering wheels and pedals, etc., which can improve the driving experience of the virtual-real fusion simulation driving system.

[0120] For example, in the embodiment of the present application, when the virtual-reality fusion simulation driving system supports the access of the six-degree-of-freedom device, the six-degree-of-freedom device can be controlled by the virtual driving software on the software simulation platform. For the virtual driving software on the software simulation platform, it may include a sensor module and a control algorithm module, wherein the sensor module is mainly used to monitor the state of the driving simulation device in real time, including acceleration, deceleration, emergency stop, sharp turn, uphill, downhill, etc., and the control algorithm module is used to obtain corresponding control data based on the state of the driving simulation device, for example, the rotation angle is converted into a rotation arc, and the control interface of the virtual driving software can be used to set the frequency of issuing and adjust the conversion mode to adapt to different types of six-degree-of-freedom devices. The control data obtained by the above conversion can be issued to each six-degree-of-freedom device through a driver plug-in, so that the six-degree-of-freedom device receives the control data, and parses the control data of each six-degree-of-freedom device, such as rotation angle data or rotation arc data, and the six-degree-of-freedom device controls the movement of the platform according to the rotation angle data or the rotation arc data, so as to achieve synchronization with the rotation angle of the virtual driving vehicle.

[0121] In an embodiment of the present application, in order to ensure that the six-degree-of-freedom device can receive the above-mentioned control data in a timely and accurate manner, such as rotation angle data or rotation arc data, the driver plug-in can provide real-time transmission and stability of control data transmission; and, it can try to avoid delays and packet loss that may occur during the communication process, and adopt a low-latency communication strategy or protocol format to improve the reliability and real-time performance of communication.

[0122] For example, when the driving simulation system is applied to force feedback in the embodiment of the present application, it can obtain force feedback data such as road surface feedback, collision feedback, steering damping, speed, force feedback linearity, etc. through various virtual driving software, and use it as control data in the above embodiment; the above force feedback data can be calculated based on the vehicle physics engine and user operation. After obtaining the above force feedback data, it can be sent to the driving simulation device, such as a steering wheel or pedal, through the driver plug-in.

[0123] Furthermore, the technical solution provided in the embodiment of the present application can be compatible with driving simulation devices of different brands or types, such as various types of steering wheels or pedals, which can use the Human Interface Device (HID) protocol to report operation data through the technical solution provided in the above embodiment, such as steering wheel angle, button status, and pedal position. In the embodiment of the present application, the above operation data and control data can be interacted through a driver plug-in, and a standardized data interface can be provided by the driver plug-in, that is, the data formats supported by different driving simulation devices can be converted into a standard unified data format, and the unified data format can be achieved by defining a standard data structure. The technical solution provided in the embodiment of the present application can be more compatible with various types of equipment, such as various steering wheels, various pedals, etc. This function can be achieved by the above-mentioned format conversion module,

[0124] After the driver plug-in converts the force feedback data from a standard unified data format to a first data format supported by the driving simulation device, it can be sent to the driving simulation device, wherein the driver plug-in and the driving simulation device can communicate via a USB HID protocol or other proprietary protocols. In the process of generating the force feedback data, the specific performance of each driving simulation device can also be considered, such as the response characteristics of the feedback electrode or the maximum torque.

[0125] When the technical solution provided in this application is applied to force feedback, it can provide a consistent force feedback experience in a driving simulation system, which can not only improve device compatibility, but also ensure that users can enjoy a more realistic driving experience through standard data formats and flexible force feedback algorithms.

[0126] The technical solution recorded in the above-mentioned embodiments of the present application, wherein support for different types of driving simulation devices can be achieved through a driver plug-in, and communication with different types of driving simulation devices can be achieved, that is, the operation data collected from the driving simulation device is sent to the virtual driving software, and the control data generated on the virtual driving software is sent to the driving simulation device.

[0127] The embodiment of the present application also provides a virtual-reality fusion simulation driving control device, Figure 4 Schematic diagram of the structure of a virtual-reality fusion simulation driving control device in an embodiment of the present application. Figure 4 As shown, it includes a plug-in loading module 11 and a mapping module 12, wherein the plug-in loading module 11 is used to load a driver plug-in corresponding to the connected driving simulation device in response to the connected driving simulation device; the mapping module 12 is used to map the operation data sent by the driving simulation device through the physical interface to the standard operation parameters of the atomic class interface based on the driver plug-in, so that the standard operation parameters are sent to the virtual driving software by the atomic class interface; and / or, is used to map the standard control parameters of the atomic class interface to the control data of the physical interface sent to the driving simulation device based on the driver plug-in, and the standard control parameters are sent by the virtual driving software to the atomic class interface.

[0128] The specific implementation of the virtual-reality fusion simulation driving control device in the embodiment of the present application can refer to Figure 1-Figure 3 The embodiment shown is not described in detail in this embodiment.

[0129] The embodiment of the present application also provides a virtual-reality fusion simulation driving system, which may include at least one driving simulation device. Figure 4 The virtual-reality fusion simulation driving control device shown or the subsequent Figure 5 The electronic device shown in the figure, and the software simulation platform, and at least one virtual driving software is set on the software simulation platform. The technical solution of the virtual-reality fusion simulation driving system can refer to the above Figure 1-Figure 3 The embodiment shown is not described in detail in this embodiment.

[0130] The following specific reference Figure 5 , which shows a schematic diagram of the structure of an electronic device 800 suitable for implementing the embodiment of the present application. The electronic device 800 in the embodiment of the present application may include but is not limited to mobile terminals such as mobile phones, laptop computers, digital broadcast receivers, PDAs (personal digital assistants), PADs (tablet computers), PMPs (portable multimedia players), vehicle-mounted terminals (such as vehicle-mounted navigation terminals), etc., and fixed terminals such as digital TVs, desktop computers, etc. The electronic device shown is only an example and should not bring any limitation to the functions and occupancy range of the embodiments of the present application.

[0131] like Figure 5As shown, the electronic device 800 may include a processing device (e.g., a central processing unit, a graphics processing unit, etc.) 801, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 802 or a program loaded from a storage device 808 into a random access memory (RAM) 803. In the RAM 803, various programs and data required for the operation of the electronic device 800 are also stored. The processing device 801, the ROM 802, and the RAM 803 are connected to each other via a bus 804. An input / output (I / O) interface 805 is also connected to the bus 804.

[0132] Typically, the following devices may be connected to the I / O interface 805: input devices 806 including, for example, a touch screen, a touchpad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; output devices 807 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; storage devices 808 including, for example, a magnetic tape, a hard disk, etc.; and communication devices 809. The communication device 809 may allow the electronic device 800 to communicate with other devices wirelessly or by wire to exchange data. Although an electronic device 800 having various devices is shown, it should be understood that it is not required to implement or have all the devices shown. More or fewer devices may be implemented or have alternatively.

[0133] In particular, according to an embodiment of the present application, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present application includes a computer program product, which includes a computer program carried on a non-transitory computer-readable medium, and the computer program contains a program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication device 809, or installed from the storage device 808, or installed from the ROM 802. When the computer program is executed by the processing device 801, the above-mentioned functions defined in the virtual-reality fusion simulation driving control of the embodiment of the present application are executed.

[0134] It should be noted that the computer-readable medium mentioned above in the present application may be a computer-readable signal medium or a computer-readable storage medium or any combination of the above two. The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination of the above. More specific examples of computer-readable storage media may include, but are not limited to: an electrical connection with one or more wires, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above. In the present application, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in combination with an instruction execution system, device or device. In the present application, a computer-readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, which carries a computer-readable program code. This propagated data signal may take a variety of forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. The computer readable signal medium may also be any computer readable medium other than a computer readable storage medium, which may send, propagate or transmit a program for use by or in conjunction with an instruction execution system, apparatus or device. The program code contained on the computer readable medium may be transmitted using any suitable medium, including but not limited to: wires, optical cables, RF (radio frequency), etc., or any suitable combination of the above.

[0135] In some embodiments, the client and the server may communicate using any currently known or future developed network protocol such as HTTP (HyperText Transfer Protocol), and may be interconnected with any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include a local area network ("LAN"), a wide area network ("WAN"), an internet (e.g., the Internet), and a peer-to-peer network (e.g., an ad hoc peer-to-peer network), as well as any currently known or future developed network.

[0136] The computer-readable storage medium may be included in the electronic device, or may exist independently without being installed in the electronic device.

[0137] The computer-readable storage medium carries one or more programs. When the one or more programs are executed by the electronic device, the electronic device:

[0138] In response to the connected driving simulation device, loading a driver plug-in corresponding to the connected driving simulation device;

[0139] Based on the driver plug-in, the operation data sent by the driving simulation device through the physical interface is mapped into standard operation parameters of the atomic interface, so that the atomic interface sends the standard operation parameters to the virtual driving software; and / or,

[0140] Based on the driver plug-in, the standard control parameters of the atomic interface are mapped to the control data of the physical interface sent to the driving simulation device, and the standard control parameters are sent to the atomic interface by the virtual driving software.

[0141] Computer program code for performing the operations of the present application may be written in one or more programming languages ​​or a combination thereof, including, but not limited to, object-oriented programming languages, such as Java, Smalltalk, C++, and conventional procedural programming languages, such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a separate software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving a remote computer, the remote computer may be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0142] The flow chart and block diagram in the accompanying drawings illustrate the possible architecture, function and operation of the system, method and computer program product according to various embodiments of the present application. In this regard, each square box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the module, the program segment or a part of the code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the square box can also occur in a sequence different from that marked in the accompanying drawings. For example, two square boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each square box in the block diagram and / or flow chart, and the combination of the square boxes in the block diagram and / or flow chart can be implemented with a dedicated hardware-based system that performs a specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0143] The units involved in the embodiments described in this application may be implemented by software or hardware, wherein the name of a unit does not, in some cases, constitute a limitation on the unit itself.

[0144] The functions described above herein may be performed at least in part by one or more hardware logic components. For example, without limitation, exemplary types of hardware logic components that may be used include: field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), systems on chips (SOCs), complex programmable logic devices (CPLDs), and the like.

[0145] In the context of the present application, a machine-readable medium may be a tangible medium that may contain or store a program for use by or in conjunction with an instruction execution system, device, or equipment. A machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or equipment, or any suitable combination of the foregoing. A more specific example of a machine-readable storage medium may include an electrical connection based on one or more lines, a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0146] According to one or more embodiments of the present application, the present application provides a computer-readable storage medium, the storage medium storing a computer program, and the computer program is used to execute any virtual-reality fusion simulation driving control as provided in the present application.

[0147] The above description is only a preferred embodiment of the present application and an explanation of the technical principles used. Those skilled in the art should understand that the scope of disclosure involved in the present application is not limited to the technical solution formed by a specific combination of the above technical features, but should also cover other technical solutions formed by any combination of the above technical features or their equivalent features without departing from the above disclosed concept. For example, the above features are replaced with the technical features with similar functions disclosed in this application (but not limited to) by each other to form a technical solution.

[0148] In addition, although each operation is described in a specific order, this should not be construed as requiring these operations to be performed in the specific order shown or to be performed in a sequential order. Under certain circumstances, multitasking and parallel processing may be advantageous. Similarly, although some specific implementation details are included in the above discussion, these should not be construed as limiting the scope of the application. Some features described in the context of a separate embodiment can also be implemented in a single embodiment in combination. On the contrary, the various features described in the context of a single embodiment can also be implemented in multiple embodiments individually or in any suitable sub-combination mode.

[0149] Although the subject matter has been described in language specific to structural features and / or methodological logical actions, it should be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or actions described above. On the contrary, the specific features and actions described above are merely example forms of implementing the claims.

Claims

1. A virtual-reality fusion simulation driving control method, characterized in that: include: In response to the connected driving simulation device, loading a driver plug-in corresponding to the connected driving simulation device; Mapping the operation data sent by the driving simulation device through the physical interface to standard operation parameters of the atomic interface based on the driver plug-in, so that the atomic interface sends the standard operation parameters to the virtual driving software; And / or, based on the driver plug-in, standard control parameters of the atomic interface are mapped into control data sent to the physical interface of the driving simulation device, and the standard control parameters are sent to the atomic interface by the virtual driving software.

2. The method according to claim 1, characterized in that The physical interfaces configured in the driving simulation device include at least two types, and the method further includes: Creating a driver plug-in according to the interface protocol of the atomic class interface and the interface protocols of at least two types of physical interfaces, each type of physical interface corresponding to a driver plug-in; The loading of a driver plug-in corresponding to the connected driving simulation device includes: A driver plug-in corresponding to the type of the physical interface of the driving simulation device is loaded.

3. The method according to claim 2, characterized in that The atomic class interface includes at least one of an axis type atomic class interface, a button type atomic class interface and a switch type atomic class interface; The standard operating parameters and / or standard control parameters of the axis type atomic class interface are in a continuously changing predetermined value range; The standard operation parameters and / or standard control parameters of the button type atomic class interface are a predetermined number of button state values; The standard operating parameters and / or standard control parameters of the switch type atomic class interface are predetermined switch identification values.

4. The method according to claim 3, characterized in that The mapping of the operation data sent by the driving simulation device through the physical interface to the standard operation parameters of the atomic class interface based on the driver plug-in includes at least one of the following: Converting the shaft operation data sent by the driving simulation device through the physical interface into a continuously changing predetermined value range based on the driver plug-in; Converting the key operation data sent by the driving simulation device through the physical interface into a predetermined number of key state values ​​based on the driver plug-in; The switch operation data sent by the driving simulation device through the physical interface is converted into a predetermined switch identification value based on the driver plug-in.

5. The method according to claim 4, characterized in that The mapping of the standard control parameters of the atomic class interface to control data sent to the physical interface of the driving simulation device based on the driver plug-in includes at least one of the following: Converting a continuously changing predetermined numerical range into shaft control data sent to the driving simulation device based on the driving plug-in; Converting a predetermined number of key state values ​​into key control data sent to the driving simulation device based on the driver plug-in; Based on the driver plug-in, a predetermined switch identification value is converted into switch control data sent to the driving simulation device.

6. The method according to claim 5, characterized in that The shaft operation data includes at least one of steering wheel operation data and pedal operation data, and the shaft control data includes at least one of steering wheel control data and pedal control data; The key operation data includes at least one of speaker operation data and game button operation data, and the key control data includes at least one of speaker control data and game button control data; The switch operation data includes at least one of turn signal switch operation data and knob switch operation data, and the switch control data includes at least one of turn signal switch control data and knob switch control data.

7. The method according to any one of claims 1 to 6, characterized in that: Also includes: Create shared memory; The atomic class interface sends standard operating parameters to the virtual driving software through the shared memory, and / or, the atomic class interface receives standard control parameters sent by the virtual driving software through the shared memory, and / or, The shared content is also used to store the interface protocol of the driver plug-in and the atomic class interface.

8. The method according to any one of claims 1 to 7, characterized in that: Also includes: In response to the disconnected driving simulation device, the driver plug-in corresponding to the connected driving simulation device is uninstalled.

9. The method according to any one of claims 1 to 7, characterized in that: Also includes: The device description information of the connected driving simulation device is obtained based on the driver plug-in and displayed, wherein the device description information includes at least one of a device model, a device identifier, and a device manufacturer identifier.

10. A virtual-reality fusion simulation driving control device, characterized in that: include: A plug-in loading module, configured to load a driver plug-in corresponding to the connected driving simulation device in response to the connected driving simulation device; A mapping module, used for mapping the operation data sent by the driving simulation device through the physical interface to standard operation parameters of the atomic interface based on the driver plug-in, so that the atomic interface sends the standard operation parameters to the virtual driving software; And / or, used to map standard control parameters of the atomic interface into control data sent to the physical interface of the driving simulation device based on the driver plug-in, wherein the standard control parameters are sent to the atomic interface by virtual driving software.

11. An electronic device, characterized in that: It comprises a processor and a memory, wherein the processor is used to execute a computer program in the memory, and the computer program can execute the virtual-reality fusion simulation driving control method as described in any one of claims 1-7.

12. A virtual-reality fusion simulation driving system, characterized in that: It comprises at least one driving simulation device, a virtual-reality fusion simulation driving control device as described in claim 10 or an electronic device as described in claim 11 connected to the at least one driving simulation device, and a software simulation platform, wherein at least one virtual driving software is arranged on the software simulation platform.

13. A computer-readable storage medium, characterized in that: Used to store a computer program capable of executing the virtual-reality fusion simulation driving control method described in any one of claims 1-7.

Images