JP6714633B2 - VR content management system - Google Patents

Description

The present invention relates to a VR (Virtual Reality) content management system.

2. Description of the Related Art Conventionally, there is known a system for managing VR content that virtually allows a viewer to experience immersion in content. For example, in Japanese Patent Laid-Open No. 2000-057373 (Patent Document 1), a virtual reality environment or scene is not divided into a file format but divided into separate records and stored in a database format, which is created, edited and distributed. A system is disclosed. The system allows multiple users to work on individual parts of a common 3D environment in parallel, and to give each person access to different parts of the 3D environment. It will be possible.

JP, 2000-057373, A

Creating the VR content includes creating an object that appears in the virtual space, and setting and editing the state of the object in the virtual space. To create an object that appears in a virtual space, specialized knowledge and technology, software such as three-dimensional CAD (Computer-Aided Design) capable of three-dimensional modeling, and a high-performance computer capable of operating the software are required. Often becomes.

It is difficult for a beginner who has no experience in creating VR content to create an object that appears in a virtual space and set and edit the state of the object in the virtual space. However, the system disclosed in Patent Document 1 does not consider facilitating the creation of VR content even for a beginner.

The present invention has been made to solve the above problems, and an object thereof is to facilitate the creation of VR contents.

A VR content management system according to an embodiment of the present invention includes a server, an object creating device, a content creating device, and a viewing device. The server converts the object data of the specific format into object data of a common format different from the specific format, and includes the object data of the common format and a setting file in which the state of the object data of the common format in the virtual space is saved. Manage VR content. The object creating device creates object data in a specific format and uploads it to the server. The content creation device creates VR content including object data in the common format downloaded from the server and a setting file in which the state of the object data in the virtual space is saved, and uploads the setting file to the server. The viewing device virtually allows the viewer to experience immersion in the VR content that is the viewing target downloaded from the server.

In the VR content management system according to the present invention, the VR content includes object data and a setting file separated from each other. By using the object data created by an experienced person who has the experience of creating object data, it is sufficient to create the VR content by editing the setting file. According to the VR content management system of the present invention, it is possible to easily create VR content.

1 is an overall configuration diagram of a VR content management system according to an embodiment. 6 is a flowchart for explaining a process performed by a server control unit. FIG. 3 is a schematic diagram of a website listing object data uploaded by an object creator. It is a block diagram which shows the function structure of a content creation apparatus. It is a figure which shows the mode of VR content creation software displayed on the display part. It is a figure which shows the dialog displayed when the list button of FIG. 5 is pressed down. It is a figure which shows the dialog displayed when the layout button of FIG. 5 is pressed down. It is a figure which shows the dialog displayed when the viewpoint management button of FIG. 5 is pressed down. It is a figure which shows the content of the setting file preserve|saved when the save button of FIG. 5 is pressed down. FIG. 9 is a diagram showing a state of the display unit after the user changes the arrangement of object data. It is a figure which shows the content of the setting file corresponding to FIG.

Hereinafter, embodiments will be described in detail with reference to the drawings. In the drawings, the same or corresponding parts are designated by the same reference numerals and the description thereof will not be repeated in principle.

FIG. 1 is an overall configuration diagram of a VR content management system 100 according to an embodiment. As shown in FIG. 1, a VR content management system 100 includes a server 10, an object creating device 20 (notebook personal computer 20A, workstation 20B), a content creating device 30 (smartphone 30A, notebook personal computer 30B), a viewing device 40. With. The VR content management system 100 is a client-server type system in which the object creation device 20, the content creation device 30, and the viewing device 40 are clients.

The server 10 includes a server control unit 11 and a storage unit 12. The server control unit 11 responds to requests from each client of the server 10. In FIG. 1, the server control unit 11 responds to a request from each client via the website Ws which is an interface. However, with the content creation device 30 and the viewing device 40, the server control unit 11 directly receives the request without using the website Ws. May be connected. A database 121 (first database) and a database 122 (second database) are formed in the storage unit 12. The database 121 is an RDB (Relational Database). The database 122 is a non-relational database based on NoSQL. The search speed of the database 122 is faster than the search speed of the database 121. The server 10 stores the VR content including the object data in the common format F10 and the setting file in which the state of the object data in the common format F10 in the virtual space (for example, object name, type, position, orientation, scale, etc.) is stored. to manage. Examples of the format of the setting file include JSON (JavaScript (registered trademark) Object Notation), XML (eXtensible Markup Language), and CSV (Comma-Separated Values).

The notebook computer 20A creates the object data md11 of the format F1 (specific format) and uploads it to the server 10. The workstation 20B creates the object data md12 in the format F2 (specific format) and uploads it to the server 10. The server 10 converts each of the object data md11 and md12 into object data of the common format F10 and stores it in the database 121.

The smartphone 30A downloads the object data md13 of the common format F10 from the server 10 and creates the VR content Cn11. The smartphone 30A saves the state of the object data md13 in the virtual space in the setting file sf11 and uploads the setting file sf11 to the server 10. The notebook computer 30B downloads the object data md14 of the common format F10 from the server 10 and creates the VR content Cn12. The laptop computer 30B saves the state of the object data md14 in the virtual space in the setting file sf12 and uploads the setting file sf12 to the server 10. The server 10 stores the setting files sf11 and sf12 in the database 122.

The viewing device 40 downloads the VR content Cn12 from the server 10. The viewing device 40 virtually allows the viewer Vwr to experience immersion in the VR content Cn12. When updating the VR content Cn12, the viewing device 40 downloads the latest version of the setting file sf12 from the server 10 and updates the object data md14 when the object data md14 of the VR content Cn12 has not been updated since the previous download. do not do. The viewing device 40 is not limited to the binocular head mounted display as shown in FIG. 1, and may be, for example, a smartphone, a PC (Personal Computer), or a monocular head mounted display. Good. Although FIG. 1 shows a case where the viewing device 40 downloads the VR content Cn12 from the server 10 and allows the viewer Vwr to view the VR content Cn12, the VR content downloaded from the server 10 by the viewing device 40 is limited to Cn12. Absent. For example, the viewing device 40 can also download the VR content Cn11 from the server 10 and allow the viewer Vwr to view the VR content Cn11.

In the VR content management system 100, the format of the object data created by the object creating device 20 is converted into a common format F10 that can be browsed by the content creating device 30 and the viewing device 40. The content creation device 30 can create VR content by using the object data created by the object creation device 20. The creator of the VR content does not need to create and edit the objects that appear in the virtual space, and thus can easily create the VR content.

Further, what is necessary when the VR content creator updates the VR content is to upload the setting file to the server 10, and it is not necessary to upload the object data to the server 10. Object data, which is three-dimensional data, often has a larger size than a setting file. By limiting the data uploaded to the server 10 to the setting file when updating the VR content, it is possible to reduce the time required for the VR content creator to update the VR content and reduce the communication load. .. Similarly, by limiting the data downloaded from the server 10 to the setting file when the viewer updates the VR content, the time required for the viewer to update the VR content can be shortened and the communication load can be reduced. can do.

In the VR content management system 100, VR content setting files are frequently communicated between the server 10 and the content creation apparatus 30, and between the server 10 and the viewing apparatus 40. In the server 10, since the setting file is stored in the database 122 of NoSQL, which has a faster search speed than RDB, the upload request and the download request of the setting file are more than those in the case where the setting file is stored in the database 121 which is the RDB. The response type to can be shortened.

FIG. 2 is a flowchart for explaining the process performed by the server control unit 11. The process shown in FIG. 2 is called by a main routine (not shown) when there is a request from the client. In the following, the step is simply described as S.

As shown in FIG. 2, in S100, the server control unit 11 determines whether the request received from the client is an object data upload request by the object creating device 20. When the request received from the client is an object data upload request (YES in S100), the server control unit 11 determines whether or not the format of the object data uploaded in S101 is the common format. When the format of the object data is the common format (YES in S101), the server control unit 11 advances the processing to S103. When the format of the object data is not the common format (NO in S101), the server control unit 11 converts the object data into the object data in the common format in S102 and advances the process to S103. In S103, the server control unit 11 saves the object data in the database 121 and returns the process to the main routine.

When the request from the client is not the upload request for the object data (NO in S100), the server control unit 11 determines in S110 whether the request from the client is a download request for the object data from the content creation device 30. To do. If the request received from the client is the object data download request (YES in S110), server control unit 11 transmits the object data to content creation device 30 in S111, and returns the process to the main routine.

If the request from the client is not the object data download request (NO in S110), the server control unit 11 determines in S120 whether the client request is a setting file upload request from the content creation device 30. To do. When the request from the client is a setting file upload request (YES in S120), the server control unit 11 saves the setting file in the database 122 in S121 and returns the process to the main routine (not shown).

If the request from the client is not a setting file upload request, the server control unit 11 determines in S130 whether the request from the client is a VR content browsing request from the viewing device 40. When the request from the client is the VR content browsing request (YES in S130), the server control unit 11 transmits the setting file of the VR content for which the browsing request is made to the viewing device 40 in S131, and advances the processing to S132. .. In S132, the server control unit 11 determines whether or not the object data of the VR content requested to be browsed has already been transmitted to the viewing device 40. When the object data has not been transmitted to viewing device 40 (NO in S132), server control unit 11 advances the process to S133. The server control unit 11 transmits the object data to the viewing device 40 in S133, and returns the processing to the main routine. If the object data has been transmitted to viewing device 40 (YES in S132), server control unit 11 returns the process to the main routine.

FIG. 3 is a schematic diagram of a website Ws listing object data md1 to md6 uploaded by an object creator. While viewing the screen, the VR content creator appropriately selects the object data necessary for creating the VR content, associates it with his/her account in the server 10, and downloads it to the content creation device 30. The VR content creator can also delete the object data associated with his/her account on the website Ws.

FIG. 4 is a block diagram showing a functional configuration of the content creation device 30. The content creation device 30 includes a control unit 31, a display unit 32, a storage unit 33, an input unit 34, and a communication unit 35. The control unit 31 executes the content creation software stored in the storage unit 33 and displays it on the display unit 32. The user operates the content creation software by operating the input unit (for example, mouse, keyboard, or touch panel). The content creation device 30 communicates with the server 10 via the communication unit 35.

FIG. 5 is a diagram showing a state of the VR content creation software displayed on the display unit 32. The VR content creator creates and edits the VR content while operating the VR content creation software. The VR content displayed in FIG. 5 is the interior of the supermarket in the virtual space being designed.

As shown in FIG. 5, the VR content creation software includes a main window Wn11 (first area), a sub window Wn12 (second area), and a sub window Wn13 (third area). The VR content creation software includes a list button Bn1, a layout button Bn2, a viewpoint management button Bn3, a save button Bn4, and an upload button Bn5.

In FIG. 5, the object data md5 and md6 are arranged inside the supermarket. In the sub window Wn12, a state of looking inside the supermarket from the viewpoint vp1 is displayed. In the sub-window Wn13, a state where the inside of the supermarket is viewed from the viewpoint vp2 is displayed. The viewpoint vp2 is a viewpoint set in order to confirm the appearance of the inside of the supermarket from the entrance Ent. The viewpoints vp1 and vp2 are displayed as eye images in FIG. 5, but may be other images (for example, cameras).

FIG. 6 is a diagram showing a dialog Dg1 displayed when the list button Bn1 of FIG. 5 is pressed. As shown in FIG. 6, the dialog Dg1 includes an add button Bn11, a delete button Bn12, a close button Bn13, and a scroll bar Sc1. In the dialog Dg1, a list (thumbnail and name) of the object data downloaded from the server 10 to the content creation device 30 is displayed. In FIG. 6, thumbnails and names of the object data md1 to md6 are displayed.

A user of the VR content creation software (VR content creator) operates the scroll bar Sc1 up and down to change the object data displayed in the dialog Dg1, thereby obtaining all the object data downloaded to the content creation device 30. Can be confirmed. The user can download new object data from the server 10 by pressing the add button Bn11. The user can delete desired object data from the list displayed in the dialog Dg1 by pressing the delete button Bn12. The user can place the selected object data in the virtual space by pressing the thumbnail or the name of the object data. The dialog Dg1 is closed by pressing the close button Bn13. Note that only the object data that the user has associated with his/her account on the website Ws shown in FIG. 3 may be displayed in the dialog Dg1.

FIG. 7 is a diagram showing a dialog Dg2 displayed when the layout button Bn2 of FIG. 5 is pressed. As shown in FIG. 7, the dialog Dg2 includes a list box Lb20, a close button Bn20, a delete button Bn21, and edit boxes Eb21 to Eb27. In the dialog Dg2, the X-coordinate, Y-coordinate, Z-coordinate, X-axis rotation angle, Y-axis rotation angle, Z-axis rotation angle, and magnification of the object data of the name displayed in the list box Lb20 are displayed in the edit box. They are displayed in Eb21 to Eb27, respectively. By operating the list box Lb20, the user can select the object data whose state in the virtual space is to be edited and edit each of the edit boxes Eb21 to Eb27. In FIG. 7, the object data md6 is selected in the list box Lb20, and the state of the object data md6 is displayed in the edit boxes Eb21 to Eb27. The user can delete the object data selected in the list box Lb20 from the virtual space by pressing the delete button Bn21. The dialog Dg2 is closed by pressing the close button Bn20. Note that the user can directly pick the object displayed in the main window Wn11 of FIG. 5 to move and rotate it in the virtual space without depending on the dialog Dg2. The state of the editable object in the virtual space is not limited to the items shown in FIG. 7, and may include the color of the object data, for example.

FIG. 8 is a diagram showing a dialog Dg3 displayed when the viewpoint management button Bn3 of FIG. 5 is pressed. As shown in FIG. 8, the dialog Dg3 includes a list box Lb30, a close button Bn30, an add button Bn31, a delete button Bn32, and edit boxes Eb31 to Eb37. In the dialog Dg3, the X coordinate, Y coordinate, Z coordinate, X axis rotation angle, Y axis rotation angle, Z axis rotation angle, and magnification in the virtual space of the viewpoint of the name displayed in the list box Lb30 are displayed in the edit box Eb31. To Eb37 are displayed respectively. By operating the list box Lb30, the user can select the viewpoint for which the state in the virtual space is to be edited, and can edit each of the edit boxes Eb31 to Eb37. The user can add a new viewpoint to the virtual space by pressing the add button Bn31. The user can delete the viewpoint with the name displayed in the list box Lb30 by pressing the delete button. In FIG. 8, the viewpoint vp1 is selected in the list box Lb30, and the state of the viewpoint vp1 is displayed in the edit boxes Eb31 to Eb37. The dialog Dg3 is closed by pressing the close button Bn30. Note that the editable viewpoint state in the virtual space is not limited to the items shown in FIG. 8, and may include, for example, an effect. The effect means that predetermined processing is applied to the entire appearance from a certain viewpoint. Examples of the predetermined processing include sepia processing, monochrome processing, and noise processing.

FIG. 9 is a diagram showing the contents of the setting file sf1 saved when the save button Bn4 of FIG. 5 is pressed. As shown in FIG. 9, the setting file sf1 stores the object data md5 and md6 arranged in the virtual space and the names, types, coordinates, rotation angles, and magnifications of the viewpoints vp1 and vp2. The type md indicates that the data in the column is object data. The type vp indicates that the data in the column is viewpoint data. The saved setting file sf1 is uploaded to the server 10 by pressing the upload button Bn5 shown in FIG. The setting file sf1 may be automatically uploaded to the server 10 after the save button Bn4 is pressed to save the setting file sf1.

FIG. 10 is a diagram showing a state of the display unit 32 after the user changes the arrangement of the object data md6. Comparing FIG. 10 and FIG. 5, the change in the arrangement of the object data md6 is reflected not only in the main window Wn11 but also in the sub windows Wn12, Wn13 at the same time. By linking a plurality of windows in this way, the user can create VR content while simultaneously confirming the appearance from a plurality of viewpoints (for example, adult eyes and child eyes, or the visual field of a security camera). it can.

FIG. 11 is a diagram showing the contents of the setting file sf1 corresponding to FIG. Comparing FIG. 11 and FIG. 9, the coordinates (P4, P5, P6) of the object data md6 in FIG. 9 are changed to the coordinates (P14, P15, P16) in FIG. The changed setting file sf1 is uploaded to the server 10.

As described above, the VR content management system according to the embodiment can facilitate the creation of VR content.

The embodiments disclosed this time are to be considered as illustrative in all points and not restrictive. The scope of the present invention is shown not by the above description but by the claims, and is intended to include meanings equivalent to the claims and all modifications within the scope.

10 server, 11 server control unit, 12, 33 storage unit, 20 object creation device, 20A, 30B notebook computer, 20B workstation, 30 content creation device, 30A smartphone, 31 control unit, 32 display unit, 34 communication unit, 40 Viewing device, 100 content management system, 121, 122 database, md1 to md6, md11 to md14 object data, sf1, sf11, sf12 setting files.

Claims (4)

The object data of the specific format is converted into object data of a common format different from the specific format, and includes the object data of the common format and a setting file in which the state of the object data of the common format in the virtual space is saved. A server that manages VR (Virtual Reality) content,
An object creating device that creates the object data in the specific format and uploads it to the server,
A content creation device that creates VR content including object data in the common format downloaded from the server and a setting file in which the state of the object data in the virtual space is saved, and uploads the setting file to the server.
A viewing device for virtually allowing a viewer to experience immersion in VR content of a viewing target downloaded from the server ,
The server includes a server control unit, a first database, and a second database,
Regarding the time required by the server control unit for each process of downloading and uploading the setting file, the time when the server control unit performs the process on the second database is the time when the server control unit performs the process. Shorter than the time required for the first database,
A VR content management, wherein the server control unit stores the object data in the common format in the first database and a setting file in which the state of the object data in the common format in the virtual space is stored in the second database. system. The content creation device,
Display part,
A control unit for displaying the VR content to be edited on the display unit,
The control unit is
Displaying the VR content to be edited viewed from the first viewpoint in the virtual space of the VR content to be edited in the first area of the display unit,
The VR according to claim 1, wherein, in the virtual space of the VR content to be edited, the VR content to be edited viewed from a second viewpoint added according to a user's input is displayed in a second area of the display unit. Content management system. The control unit displays the VR content to be edited in a virtual space of the VR content to be edited from the third viewpoint added according to a user's input, in a third area of the display unit. The VR content management system described in 2. When updating the VR content to be viewed, the viewing device downloads the latest version of the setting file of the VR content from the server when the object data of the VR content has not been updated since the previous download, The VR content management system according to claim 1, wherein the object data is not downloaded from the server.

Images