Development Interface Device Compatible with Multiple VR Devices

Abstract

An embodiment of the present invention discloses a development interface device compatible with multiple VR devices. The device pre-sets the corresponding relationships between different VR device models and call requests for obtaining device information and instructions recognizable by the VR devices, as well as the corresponding relationships between different VR device models and operation requests for device operations and operation instructions recognizable by the VR devices, so as to perform unified conversion of requests into instructions for different types of VR device models, enabling VR content to be automatically adapted to different models of VR devices, improving compatibility and reducing the development burden.

Description

Technical Field

[0001] The present invention relates to the field of VR technology, and particularly relates to a development interface device compatible with multiple VR devices. Background Art

[0002] Virtual Reality (VR) technology is a computer simulation system that can create and experience virtual worlds. It uses a computer to generate a simulated environment and enables users to immerse themselves in that environment. With the development of VR technology, VR head-mounted devices (simply referred to as VR devices) have become increasingly popular. However, there are numerous models of related VR devices from different manufacturers, which poses a huge challenge to VR content developers. When developing VR content applications, VR content developers often can only develop for specific models of VR devices. When porting them to other VR devices, a large amount of re-adjustment work is required. Summary of the Invention

[0003] In view of this, the purpose of the present invention is to provide a development interface device compatible with multiple VR devices, so as to automatically adapt to different VR devices and achieve compatible use of VR content.

[0004] In a first aspect, there is provided a development interface device compatible with multiple VR devices, the device comprising:

[0005] A model determination module for determining the current device model;

[0006] A device information acquisition module for converting the call request into an acquisition instruction recognizable by the corresponding VR device in response to the call request and the current device model; and

[0007] A device operation module for converting the operation request into an operation instruction recognizable by the corresponding VR device in response to the operation request and the current device model, and controlling the VR device to execute the operation instruction.

[0008] In some embodiments, the device further comprises:

[0009] A storage module for storing the correspondence between the acquisition instruction and the call request corresponding to each device model, and the correspondence between the operation instruction and the operation request corresponding to each device model.

[0010] In some embodiments, the call request includes at least one of the following operations:

[0011] Obtaining the rendering level of the fixation point; obtaining the current volume value; obtaining the maximum volume value; obtaining the current device brightness value; obtaining the device identifier; and obtaining the sleep state of the device.

[0012] In some embodiments, the operation request includes at least one of the following operations:

[0013] Setting a fixation rendering level; initializing the volume; operating a volume service; operating a power service; setting the volume; setting a brightness value; a sleep operation; a key function operation; a screen mirroring function operation; a screen-on operation; a configuration operation; and a power-on / off operation.

[0014] In some embodiments, the key function operation includes:

[0015] Enabling or disabling a head-mounted confirmation key; enabling or disabling volume keys; enabling or disabling a head-mounted return key; restoring the default key configuration.

[0016] In some embodiments, the device information acquisition module is configured to receive the call request through a first service interface.

[0017] In some embodiments, the device operation module is configured to receive the operation request through a second service interface.

[0018] In some embodiments, the device model includes manufacturer information.

[0019] In a second aspect, there is provided a computer-readable storage medium having stored therein a computer program, which when executed by a processor implements the apparatus as described in the first aspect.

[0020] In a third aspect, there is provided an electronic device including a memory and a processor, the memory being used to store one or more computer program instructions, wherein the one or more computer program instructions are executed by the processor to implement the apparatus as described in the first aspect.

[0021] In the embodiments of the present invention, by presetting the corresponding relationships between different VR device models and call requests for device information acquisition and instructions recognizable by VR devices, as well as the corresponding relationships between different VR device models and operation requests for device operations and operation instructions recognizable by VR devices, the conversion of unified requests to instructions for different types of VR device models is performed, so that VR content can be automatically adapted to different models of VR devices, improving compatibility and reducing the development burden. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] Through the following description of the embodiments of the present invention with reference to the drawings, the above and other objects, features, and advantages of the present invention will become more apparent. In the drawings:

[0023] Figure 1 is a block diagram of a development interface device compatible with multiple VR devices according to an embodiment of the present invention;

[0024] Figure 2It is a flow chart for the instruction conversion of the development interface device compatible with multiple VR devices according to the embodiments of the present invention;

[0025] Figure 3 It is a schematic diagram of an electronic device according to the embodiments of the present invention. Specific embodiments

[0026] The present invention will be described based on the embodiments below, but the present invention is not limited to these embodiments only. In the following detailed description of the present invention, some specific details are described in detail. Those skilled in the art can fully understand the present invention without the description of these details. In order to avoid obscuring the essence of the present invention, well-known methods, processes, flows, elements and circuits are not described in detail.

[0027] In addition, those of ordinary skill in the art should understand that the drawings provided herein are for illustrative purposes only, and the drawings are not necessarily drawn to scale.

[0028] Unless the context clearly requires otherwise, words such as "including" and "comprising" in the specification should be construed in an inclusive sense rather than an exclusive or exhaustive sense; that is, it is the meaning of "including but not limited to".

[0029] In the description of the present invention, it should be understood that terms such as "first" and "second" are used for descriptive purposes only and cannot be construed as indicating or implying relative importance. In addition, in the description of the present invention, unless otherwise specified, the meaning of "a plurality of" is two or more.

[0030] Figure 1 It is a block diagram of the development interface device compatible with multiple VR devices according to the embodiments of the present invention. As Figure 1 shown, the development interface device 1 compatible with multiple VR devices according to the embodiments of the present invention includes a model determination module 11, a device information acquisition module 12, a device operation module 13 and a storage module 14.

[0031] Among them, the model determination module 11 is used to determine the current device model. Specifically, the model determination module can automatically read the device model of the VR device, or read the setting information about the model to obtain the device model of the VR device. The device model includes manufacturer information. Generally speaking, the instruction systems of VR devices adopted by the same manufacturer are the same. Therefore, the manufacturer information can be used as the device signal to distinguish the instruction sets corresponding to different VR devices. The device information acquisition module 12 is used to convert the call request into an acquisition instruction recognized by the corresponding VR device in response to the call request and the current device model. The device operation module 13 is used to convert the operation request into an operation instruction recognized by the corresponding VR device in response to the operation request and the current device model, and control the VR device to execute the operation instruction. The storage module 14 is used to store the correspondence between the acquisition instruction and the call request corresponding to each device model, and the correspondence between the operation instruction and the operation request corresponding to each device model.

[0032] Thus, through the device information acquisition module 12, the conversion of relevant requests for device information acquisition to the instructions corresponding to the current VR device model can be completed. Through the device operation module 13, the conversion of the operation request for the VR device to the instructions corresponding to the current VR device model can be completed. Thus, during the VR content development process, the two main types of operations that need to be performed can be compatible through the development interface device 1 for compatible multi-VR devices of the present embodiment.

[0033] Specifically, in this embodiment, the call request includes at least one of the following operations: obtaining the rendering level of the fixation point; obtaining the current volume value; obtaining the maximum volume value; obtaining the current device brightness value; obtaining the device identifier; and obtaining the sleep state of the device.

[0034] Thus, various device information and status information common to VR devices can be obtained.

[0035] Specifically, in this embodiment, the operation request includes at least one of the following operations:

[0036] Setting the rendering level of the fixation point; initializing the volume; operating the volume service; operating the power service; setting the volume; setting the brightness value; sleep operation; key function operation; screen mirroring function operation; screen on operation; configuration operation; and power on / off operation. Among them, the key function operation includes: enabling or disabling the head-mounted confirmation key; enabling or disabling the volume key; enabling or disabling the head-mounted return key; restoring the default key configuration.

[0037] Thus, comprehensive operations and settings for the display content, screen mirroring, and other hardware parameters of the VR device can be achieved.

[0038] In this embodiment, the device information acquisition module is configured to receive the call request through the first service interface. The device operation module is configured to receive the operation request through the second service interface. During the call process, requests sent by the upper-layer application or service are received through different service interfaces and converted, which can further improve the standardization degree and compatibility.

[0039] Figure 2 is a flowchart of the instruction conversion of the development interface device compatible with multiple VR devices according to the embodiment of the present invention. As Figure 2 shown, the process of the development interface device performing instruction conversion in this embodiment includes the following steps:

[0040] In step S210, the device model of the current device is determined.

[0041] In step S220, a request is received.

[0042] In step S230, it is determined whether the request is a call request for device information acquisition or an operation request for operating the VR device. If it is a call request, go to step S240; if it is an operation request, go to step S250.

[0043] In step S240, in response to the call request and the current device model, the call request is converted into an acquisition instruction recognizable by the corresponding VR device, and the VR device is controlled to execute the acquisition instruction.

[0044] In step S250, in response to the operation request and the current device model, the operation request is converted into an operation instruction recognizable by the corresponding VR device, and the VR device is controlled to execute the operation instruction.

[0045] Therefore, in the embodiment of the present invention, by presetting the corresponding relationships between different VR device models and call requests for device information acquisition and instructions recognizable by VR devices, and between different VR device models and operation requests for device operations and operation instructions recognizable by VR devices, unified conversion of requests to instructions for different types of VR device models is performed, so that VR content can be automatically adapted to different models of VR devices, improving compatibility and reducing the development burden.

[0046] The embodiment of the present invention also provides an electronic device. Figure 3 is a schematic diagram of the electronic device according to the embodiment of the present invention. As Figure 3 shown, Figure 3The electronic device shown is a general address query device, which includes a general computer hardware structure, and at least includes a processor 31 and a memory 32. The processor 31 and the memory 32 are connected through a bus 33. The memory 32 is adapted to store instructions or programs executable by the processor 31. The processor 31 can be an independent microprocessor or a set of one or more microprocessors. Thus, by executing the instructions stored in the memory 32, the processor 31 executes the method flow of the above-described embodiment or implements the module architecture in the above-described system to process data and control other devices. The bus 33 connects the above-mentioned multiple components together and also connects the above-mentioned components to a display controller 34, a display device, and an input / output (I / O) device 35. The input / output (I / O) device 35 can be a mouse, a keyboard, a modem, a network interface, a touch input device, a body sensing input device, a printer, and other devices well-known in the art. Typically, the input / output (I / O) device 35 is connected to the system through an input / output (I / O) controller 36.

[0047] Those skilled in the art should understand that the embodiments of the present application can be provided as a method, a device (equipment), or a computer program product. Therefore, the present application can take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware aspects. Moreover, the present application can be implemented as a computer program product on one or more computer-readable storage media (including but not limited to disk memories, CD-ROMs, optical memories, etc.) containing computer-usable program codes.

[0048] The present application is described with reference to the flowcharts of methods, devices (equipment), and computer program products according to the embodiments of the present application. It should be understood that each process in the flowchart can be implemented by computer program instructions.

[0049] These computer program instructions can be stored in a computer-readable memory that can direct a computer or other programmable data processing device to work in a specific manner, so that the instructions stored in the computer-readable memory produce a manufactured article including an instruction device, and the instruction device implements the processes Figure 1 specified functions in one process or multiple processes.

[0050] These computer program instructions can also be provided to the processor of a general computer, a special computer, an embedded processor, or other programmable data processing devices to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing devices produce a device for implementing the processes Figure 1 specified functions in one process or multiple processes.

[0051] Another embodiment of the present invention relates to a non-volatile storage medium for storing a computer-readable program, which is used for a computer to execute the above-mentioned partial or all method embodiments.

[0052] That is, those skilled in the art can understand that all or part of the steps in implementing the above-mentioned method embodiments can be completed by specifying relevant hardware through a program. This program is stored in a storage medium and includes several instructions for causing a device (which can be a single-chip microcomputer, a chip, etc.) or a processor to execute all or part of the steps of the methods described in the embodiments of the present application. The aforementioned storage medium includes: various media that can store program codes, such as USB flash drives, mobile hard disks, read-only memories (ROMs), random access memories (RAMs), magnetic disks, or optical discs.

[0053] The foregoing are only the preferred embodiments of the present invention and are not intended to limit the present invention. For those skilled in the art, the present invention may have various modifications and changes. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present invention shall be included within the protection scope of the present invention.

Claims

1. A development interface device compatible with multiple VR devices, characterized in that, The device includes: A model determination module, configured to determine the current device model, where the device model includes manufacturer information, and the manufacturer information is used to distinguish instruction sets corresponding to multiple VR devices; A device information acquisition module, configured to convert the call request into an acquisition instruction recognizable by the corresponding VR device in response to the call request and the current device model; and A device operation module, configured to convert the operation request into an operation instruction recognizable by the corresponding VR device in response to the operation request and the current device model, and control the VR device to execute the operation instruction; Wherein, the call request includes at least one of the following operations: Obtaining the rendering level of the fixation point; obtaining the current volume value; obtaining the maximum volume value; obtaining the current device brightness value; obtaining the device identifier; and obtaining the sleep state of the device.

2. The device according to claim 1, characterized in that, The device further includes: A storage module, configured to store the correspondence between the acquisition instructions and the call requests corresponding to each device model, and the correspondence between the operation instructions and the operation requests corresponding to each device model.

3. The device according to claim 1, characterized in that The operation request includes at least one of the following operations: Setting the rendering level of the fixation point; initializing the volume; operating the volume service; operating the power service; setting the volume; setting the brightness value; sleep operation; key function operation; screen mirroring function operation; screen on operation; configuration operation; and power on / off operation.

4. The device according to claim 3, wherein, The key function operation includes: Enabling or disabling the head-mounted confirmation key; enabling or disabling the volume key; enabling or disabling the head-mounted return key; restoring the default key configuration.

5. The device according to claim 1, characterized in that The device information acquisition module is configured to receive the call request through a first service interface.

6. The device according to claim 1, characterized in that, The device operation module is configured to receive the operation request through a second service interface.

7. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the device according to any one of claims 1-6 is implemented.

8. An electronic device, comprising a memory and a processor, characterized in that, The memory is configured to store one or more computer program instructions, and when the one or more computer program instructions are executed by the processor, the device according to any one of claims 1-6 is implemented.

Images