JP2005165873A - Web 3d-image display system - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To provide a Web 3D-image display system which is not limited to a platform and a Web browser. <P>SOLUTION: The system comprises a 3D applet that reads a Web 3D file of a standard format, such as a VRML, edits a 3D scene, assigns various pieces of information to it, compresses 3D scene information including attribute information necessary for animation, etc. and displays a 3D scene based on the compressed file, and a 3D scene editing means that creates a 3D-control applet that transfers event inputs by a keyboard, a mouse, etc. to the 3D applet, and performs interactive operations, such as moving or changing the 3D object, and a Web page that calls up these applets, and stores these 3D information files necessary for displaying the 3D scene in a memory unit. The system reads the stored 3D information files with a Web browser, executes the read-in applets, and displays the 3D scene that is interactive with a user. <P>COPYRIGHT: (C)2005,JPO&NCIPI

Description

  The present invention relates to a bidirectional real-time 3D (three-dimensional) image display system for a user using a Web browser, and more specifically, by a user without installing special plug-in software in the Web browser. The present invention relates to a Web 3D image display system that enables interactive operation.

Conventionally, VRML (Virtual Reality Modeling Language) is known as a standard format for displaying 3D images for the Web.
There is a Web browser (VRML browser) configured to display 3D images by a plug-in dedicated to directly reading this VRML file, but only the convenience problem that the plug-in needs to be installed by the user's own operation In addition, the creation of a 3D scene for realizing an interactive operation with the user in the VRML browser in which the plug-in is installed in this way requires a great amount of complicated manual work, and the work efficiency is extremely poor. was there. Further, when the VRML file is used as it is, there is a problem not only in the type of interactive operation but also in the responsiveness due to the complexity and weight of the processing, and a light and multifunctional 3D scene cannot be displayed.

As a system that performs 3D display on a Web browser that improves this, there is a “Web 3D image display system” (Patent Document 1) by the same inventor as the present invention.
Patent Document 1 is a system that reads a standard Web3D file such as VRML, customizes the read 3D scene, adds a 3D animation, etc., and generates a file group for lightly operating on a Web browser. The part related to the interactive operation with the user is provided with an original Java (R) script API (Application Program Interface) in the Java (R) applet for displaying the 3D scene generated for display on the Web browser, and the Web page This was realized through this unique script described in (HTML file).

International Publication No. 03/033455 Pamphlet

  However, since the function that realizes interactive operation with the user is described by a Java (R) script, the operating environment such as platform differences (OS: Operating System, machine environment differences) and Web browser differences, etc. Depending on the difference, it becomes necessary to change the description of the script, or the Java® API does not function well depending on the operating environment, and the operating environment must be limited. In addition, the script description itself needs to be manually created by the web editor, and 3D scene image display, animation, and interactive operations are performed by running the script on the web browser each time and confirming the operation. It was.

  In order to solve the problems as described above, an object of the present invention is to provide a Web 3D image display system that realizes an interactive operation with a user with the operating environment such as a platform and a Web browser as limited as possible. In addition, a Web 3D image that generates a Web page by a Web 3D authoring tool that can mutually confirm description of a program for realizing an interactive operation with a user using the same display screen as the 3D scene displayed on the Web browser An object is to provide a display system.

In order to achieve the above object, the invention described in claim 1 is based on a Web3D file in a file format described in a standard 3D graphics description language for Web such as VRML generated by various 3D modeling software programs. A computer system that edits a 3D scene and displays the 3D scene on a web browser,
3D scene customization means for customizing 3D scenes based on the Web3D file including 3D objects and 3D scene information and providing various information for displaying the 3D scene on the Web browser, and obtained from the Web3D file 3D compressed file generating means for generating a 3D compressed file by compressing 3D object and 3D scene information including attribute information necessary for animation and the like, and the Web based on the 3D object and 3D scene information of the compressed 3D compressed file 3D applet generation means for generating a 3D applet for executing a real-time 3D rendering and motion algorithm on a browser to display a 3D scene, and a user event input by a keyboard / mouse on the Web browser A 3D control applet generating means for generating a 3D control applet for performing an interactive operation with a user such as transfer and change of a 3D object, and an applet tag for calling the 3D applet and the 3D control applet. Web page generation means for generating an included Web page, and a 3D information file including the generated 3D compressed file, the 3D applet, the 3D control applet, the Web page, and a texture file necessary for displaying a 3D scene A 3D scene editing means including at least a 3D information storage means for storing the information in a storage device,
The 3D applet executing means for reading the stored 3D information file by the web browser and executing the 3D applet and the 3D control applet, and the interactive 3D scene with the user by executing the 3D applet and the 3D control applet. And an interactive display processing means for displaying the above.

3. The 3D compressed file according to claim 2, comprising at least 3D scene information including shape, coordinate transformation, light, and camera information called from the 3D applet, and is stored in a single file as binary data. And
The 3D applet according to claim 3 is composed of a plurality of applet classes and includes at least each class of scene elements including shape, coordinate transformation, light, and camera, and wireframe, flat shading, and goo shading. The class required for displaying the 3D scene is selected from each class including a shader class and various core classes for displaying a 3D image, and is stored as one compressed file.
The information exchanged with the 3D applet according to the execution of the 3D control applet according to claim 4 includes at least an object, a shape, coordinates, a camera, an animation, in order to display a 3D image that can be interactively operated with a user. It includes any one or more of image display and user interface information.
The 3D control applet according to claim 5, wherein the 3D control applet includes at least a selection button by an image, a selection button by a text, a check box for selecting from a plurality of candidates, a selection button for selection by a drop-down list, and a text input field. A plurality of applet classes including each class and each class of tag range designation in the web page, image tag information, and text area tag information constitute part of the passing information with the 3D applet, The class required for the interactive operation is selected from each class, and is stored as one compressed file.
7. The 3D applet according to claim 6, wherein the 3D applet has a unique script interface that enables interactive operation with a user by script code, and the 3D applet is executed by the execution of the 3D control applet. Passing of information and information associated with the interactive operation is performed through the script interface.
8. The 3D scene customizing unit according to claim 7, further comprising a script language editing unit for customizing the 3D scene and a program source compiling unit described in the script language, wherein the 3D control is performed by the compiling unit. A scripting engine for exchanging information with the 3D applet through the script interface is generated by executing the applet.
The 3D scene editing unit according to claim 8 confirms and displays the 3D scene including a 3D image displayed on a Web browser, a 3D image animation, a user operation button for performing an interactive operation with a user, and the like. And a display unit including at least a script description part for customizing a 3D scene of the preview part.
The 3D scene customization such as 3D image shape, coordinates, camera, texture, animation, interactive operation with a user, etc. in the script description unit according to claim 9 is performed for each program step. The change of the 3D scene reflected by the interactive operation by the user operation button or the like of the preview part is reflected in the description part of the program source text of the script description part, and is reflected in the part, and the script description part or the preview part The editing or operation result of either one of these is reflected mutually in substantially real time.

According to the Web 3D image display system of the present invention, a script that has been manually entered in a Hyper Text Markup Language (HTML) page is called as a 3D control applet of an external file. There is an effect that an unrestricted system can be constructed.
This 3D control applet can edit 3D scenes using a script conforming to the Java® script that can be programmed while referring to the same display screen as the 3D scene displayed on the actual Web browser. Since it is configured so as to be generated by the means, the effect of reducing the burden on the person in charge of web editing is also great.

  A specific example of the embodiment of the Web 3D image display system according to the present invention will be described with reference to the drawings.

FIG. 1 is a schematic diagram showing a configuration of a Web 3D image display system according to the present embodiment.
FIG. 1A shows a configuration of a computer system that generates 3D information data for displaying a light 3D scene by realizing interactive operation with a user on a Web browser, and FIG. A computer terminal such as a PC (personal computer) having a Web browser for reading the 3D information data generated in FIG. 1A and displaying a 3D scene.
Each means shown in FIG. 1 realizes its function by installing and executing a software program on a commercially available PC or workstation. The PC or workstation stores a CPU (Central Control Unit), a memory, a hard disk or the like. Device, a display device for displaying images, text, etc., an input device such as a keyboard and a mouse, and other generally known computer devices equipped with other input / output devices and peripheral devices. The configuration drawing is omitted.
Further, the computer used in FIGS. 1A and 1B may be either a different configuration or a configuration using the same computer.

Reference numeral 1 denotes a Web 3D image generation system that generates various file groups for displaying a 3D scene on a Web browser. Reference numeral 2 denotes a computer having a Web browser for reading various generated 3D information files and displaying the 3D scene. It is.
Reference numeral 10 denotes a 3D object creation means, which creates a 3D object or 3D scene that is a basis for generating the 3D information data of the present invention using various 3D modeling software.
Reference numeral 11 denotes VRML file generation means for outputting 3D objects and 3D scene information created by 3D modeling software as VRML files.

Reference numerals 12 to 17 denote each means constituting the 3D scene editing means.
Reference numeral 12 denotes 3D scene customization means, which is an addition / editing means for reading a VRML file generated by 3D modeling software and displaying a 3D scene that can be interactively operated with a user by an applet loaded on a Web browser. Various necessary information such as movement, rotation, enlargement / reduction, and animation is added to the 3D object and 3D scene information by the web editor.

Reference numeral 13 denotes a 3D compressed file generating means, which combines a 3D object or 3D scene having attribute information added / edited by the 3D scene customizing means 12 together with a texture file (not shown) as a single 3D compressed file using binary data. Generate.
Reference numeral 14 denotes a 3D applet generation means. An applet group necessary for displaying a 3D object and a 3D scene that can be interactively operated with a user based on the 3D compressed file generated by the 3D compressed file generation means 13 is displayed. Generate as a compressed file.
Reference numeral 15 denotes a 3D control applet generation means, which is necessary for handling event input associated with an interactive operation with a user when a 3D object or 3D scene is displayed via the 3D applet generated by the 3D applet generation means 14. A group of applets is generated as a compressed file. The applet group generated by the 3D control applet generation means 15 includes not only an interface for interactive operation with a user but also an interface with a 3D applet for displaying 3D objects and 3D scenes.

Reference numeral 16 denotes a Web page generation unit that automatically generates a Web page (HTML page) including the 3D control applet tag generated by the 3D control applet generation unit 15 for displaying a 3D scene.
Reference numeral 17 denotes a 3D information storage unit for storing various 3D information necessary for displaying the 3D scene generated by the 3D scene editing unit. The 3D information storage unit 17 is generated by each generation unit necessary for displaying the 3D scene on the Web browser. These various types of 3D information are stored and accumulated as 3D information data 18 in a storage device (not shown) in the Web image generation system.

Reference numerals 21 to 26 denote each means for reading a Web page in which an applet tag is described by a Web browser and executing the applet by a VM (virtual machine) installed in the Web browser.
Reference numeral 21 denotes 3D control applet request means, which requests a 3D control applet by an applet tag described in the Web page and loads it into the Web browser.
Reference numeral 22 is a 3D applet request means for requesting a 3D applet by the loaded 3D control applet and loading it into the Web browser. Reference numeral 23 is a request for a 3D compressed file by the loaded 3D applet and loading it into the Web browser to display the 3D scene. 3D compressed file requesting means.

Reference numeral 24 denotes 3D control applet execution means for executing a 3D control applet loaded in the Web browser, and is executed by a VM installed in the Web browser.
Reference numeral 25 denotes a 3D applet execution unit which is called from a 3D control applet and executes a 3D applet to display a 3D scene.
26 is an interactive display processing means, and the 3D control applet loaded in the Web browser and the 3D applet are executed by the VM installed in the Web browser, thereby continuously displaying the 3D scene.
Various types of 3D information necessary for displaying a 3D scene by being read by the Web browser is stored and accumulated as 3D information data 27 in a storage device (not shown) in the PC 2. The 3D information data 27 in the PC 2 is the same as the 3D information data 18 generated by the Web image generation system 1, and if the Web image generation system 1 and the PC 2 are not the same computer, a recording medium such as a communication line or a CD (see FIG. (Not shown) and copied or loaded from the Web image generation system 1 for use.

  Next, referring to the processing flow diagram of FIG. 2, 3D information data generation for realizing an interactive operation with the user on the Web browser, and the generated 3D information data are read and a 3D scene is read by the Web browser. The operation until display is described.

First, the person in charge of web editing creates a 3D object using a commercially available existing 3D modeling software program as the 3D object creation means 10 (S101).
Any 3D modeling software program can be used as long as it can output as a VRML file (VRML file generation means 11). For example, a 3D object is created by using “3ds (product name)” and the created 3D The object is further subjected to modification processing such as motion, camera, lighting, and material, and the 3D object and the entire 3D scene are exported as a VRML format file included in “3ds” (S102).

The 3D scene editing unit takes in a VRML file (Web3D file) including 3D scene information generated by the 3D object generation unit 10 and the VRML file generation unit 11 (S103), and performs an interactive operation with the user using a Web browser. Various kinds of information regarding the display method of the 3D scene to be enabled are given and stored as 3D information data 18.
The VRML file captures object information such as polygon vertex rows, surface information, color information, and image information including textures to be pasted on each surface, scene information such as cameras and lights, and animation information of each object. It is.

The 3D scene customizing unit 12 uses a VRML file generally known as a description format of a 3D graphics description language as an input tool, takes in a description relating to a 3D world and 3D shape (shape definition) in the VRML file, The 3D applet generated by the 3D applet generation unit 14 gives information such as a 3D scene display method necessary for displaying an interactive (bidirectional) 3D scene with the user (S104, S105).
Information on all customized 3D objects and 3D scenes are combined into a single 3D compressed file in binary format by the 3D compressed file generation unit 13 and stored in the storage device as 3D information data 18 by the 3D information storage unit 17. -Accumulated (S106).

  The VRML file is not a compressed file but is written as a normal text file. For example, when displaying a specific 3D scene, it contains information that is not necessary to display the 3D scene due to its versatility. On the contrary, since there is not enough information to display the interactive 3D scene with the user, the 3D scene editing means is used only for importing the 3D scene information, and the 3D world and 3D shape ( A 3D compressed file is generated by adding information necessary for the 3D scene customization unit 12 using a description relating to (shape definition). The 3D compressed file contains only information necessary for displaying the 3D scene by the 3D applet.

  3D scene customization includes object information such as shading (shading), scene information such as camera and light positions, animation information such as animation editing and naming of each object, background image, and screen size. In addition, display information such as other scene attributes is possible.

  The 3D applet is prepared in advance by 3D scene editing means and is a collection of small Java (R) applications that execute real-time 3D rendering and motion algorithms. Various 3D applets in 3D compressed files set by 3D scene customization The 3D scene information is called by a Web browser and optimized to display the 3D scene lightly. The 3D applet generation means 14 collects only applet class files necessary for displaying the 3D scene from the information of the 3D compressed file set at the time of customization, and generates one ZIP compressed file.

The addition / editing of 3D control information accompanying processing such as event input for interactive operation with the user is mainly performed using a debugger (not shown) (S107, S108).
The debugger is called a so-called visual editor. On the editing screen, a preview part that performs the same operation as when a 3D scene is displayed by a Web browser, and a 3D scene displayed on the preview part are customized. The script description part which consists of a text editor for implement | achieving interactive operation is included. The script is unique to the present invention, but conforms to the grammar of the Java (R) script, and is easy for a web editor to accept.
The operation in the preview part and the edited contents of the program source text in the script description part are configured so that the respective operation results and editing results are mutually reflected in almost real time. The script described in the script description part can confirm the operation for each program step, and can confirm the movement of the 3D scene for each step. Further, when a 3D object or 3D scene in the preview portion is operated, the script of that portion is not only clearly indicated by highlighting or blinking, but a script corresponding to the operation can be automatically generated.

The debugger adds / edits processing such as event input for interactive operation with the user based on each 3D information data generated by the 3D scene customization unit 12, the 3D compressed file generation unit 13, and the 3D applet generation unit 14. The added / edited information is collected by the 3D control applet generation means 15 into a single compressed file as a 3D control information file including the 3D control applet. In addition, the HTML file in which the 3D control applet tag is described is automatically generated by the Web page generating means 16 (S109).
The information added / edited by the debugger is reflected again in the 3D compressed file and 3D applet, and by the 3D information storage means 17, together with the 3D control applet and HTML file, these 3D compressed file, 3D applet, and JPEG (Joint Photographic Experts Groups) The image data of the texture file compressed by the above is stored in the storage device as 3D information data 18 (S110).

  The 3D scene information stored as 3D information data is temporarily stored in a storage device (not shown) such as a hard disk as 3D information data 27 in the PC 2 via a recording medium or a communication line (not shown). If the recording medium is a CD or DVD, it may be read as it is. The 3D scene information is read by the Web browser in the PC 2, and the applet is executed by the VM installed in the Web browser to display the 3D scene.

When a web page for calling and executing 3D scene information is read by a web browser, an applet tag for requesting a 3D control applet is described in the HTML file (3D control applet request means 21), and the 3D control applet. Is loaded into the Web browser, the 3D control applet is executed by the VM installed in the Web browser (3D control applet execution means 24), and the 3D applet for displaying the 3D scene is requested by this 3D control applet ( 3D applet request means 22).
When the 3D applet is loaded, the VM executes the 3D applet (3D applet executing means 25), reads the 3D compressed file and the texture file (3D compressed file requesting means 23), and cooperates with the 3D control applet. The 3D scene that realizes the interactive operation is displayed (interactive display processing means 26) (S111, S112).

Next, the structure of the 3D applet will be described with reference to FIG.
As shown in FIG. 3, the 3D applet represents scene information composed of rendering (rendering) and motion of a 3D object, and has core classes for controlling the 3D scene. All scene information is always stored in a Scene 36 object including all scene elements inherited by the IdObject30 class, and the 3D scene rendering is performed by the Scene 36 rendering method.

  User events entered via the 3D control applet are routed to the Controller 59 class. For example, when a 3D applet is already running, the information is passed to the 3D applet by using a user event, and the Controller 59 class changes the Orientation attribute of the currently selected Transform32 class. Become.

The Shape31 class displays an actual 3D object on the 3D scene, and its attributes include all the information necessary to draw the 3D object on the screen. All Shape31 classes contain a reference to the adjacent Transform32.
The Transform 32 has the position information of the Shape31 class, and is used to position the Shape31 class on the 3D scene. Rendering (drawing) is performed based on each object information and its position information in one scene. When drawing a shape (shape), the I3dObject40 class is used to render the class. All classes that implement the I3dObject40 interface (eg, TextureMap45 class = realization of texture) can be drawn on the screen.

  The Clipper57 class is used in conjunction with the shader class I3dObject40 class to rasterize a certain shape on the screen.

Next, the structure of the applet class shown in FIG. 3 will be described in each of the sections (a) to (c).
An IdObject 30 in the section (a) of FIG. 3 represents a scene element. All scene elements have a unique Id, which is a common feature represented by the IdObject30 class, so all scene elements are inherited by this class (“inheritance” is an object-oriented feature. Yes, Java (R) is an object-oriented programming language). A 3D scene is represented by a hierarchy of elements, and a unique Id is used during the loading of scene information from a 3D compressed file to form this hierarchy. The hierarchy is formed by Transform32 objects (in this case, “object” is a synonym for “class”). Each Transform32 object has a number of Light (Light34 object), shape (Shape31 object), another Transform32 object, and so on. These different types of scene elements may be included.
There is always a root transform that contains all the scene elements, this special transform is called a scene transform and is represented by a single Scene36 object contained within the main applet class (Applet3da56). Yes. Hierarchical information is important for 3D display of scenes. Each Transform32 object represents a position in the 3D world, and all stored elements are moved (coordinate converted) based on this position and displayed.

  Interpolator 33 contains information about writing between a set of values in the scene image element. The interpolator class includes a way to slide between these values and gradually change the properties of the scene elements. The scene elements including the interpolator are Shape 31 and Transform 32. The shape (shape) is morphed using an interpolator. Transform (coordinate transformation) uses an interpolator to move and rotate. In this way, the applet engine performs 3D animation. As the animation plays, the interpolator "slides" between a set of values to set the properties of the scene elements (such as transform position properties for movement or shape coordinates for shape morphing). change. When an animation is being played in the scene, each frame is advanced by a list of active interpolators included in the Scene 36 object, causing a change in the scene, ie, an animation effect. The interpolator knows the passage of time and how much time is needed to advance the value. In this way, the length of animation (animation time) is controlled.

  Light 34 is used to define the lighting of the scene shape. The light contains color properties that define the color and brightness of the light. There are two types of lights: an omni light that includes position information and a spotlight that includes direction information. The light is in a Transform32 object. When you move a transform that contains a light element, the light will also move, changing the way the scene shape is illuminated. When a Shape31 object is rendered on the screen using a shader object (I3dObject40 class), the shader object checks the position, orientation, and color of all scene lights and renders the shape with accurate lighting It becomes possible.

  The Camera 35 defines a viewpoint, and each Camera 35 object includes position and direction information. This information combined with the position of the transform in which the camera is located indicates the viewpoint from which the 3D scene can be depicted and viewed. The Controller 59 object contains a reference to the active camera, which is the camera currently used as the scene viewpoint. Each time a scene image is rendered, all 3D information is changed to the coordinate space of the active camera so that the active camera is at the origin (0, 0, 0) of the world coordinates. This is done by the Scene 36 object. Then, the coordinate-changed scene is drawn to reveal how the 3D scene looks from the camera perspective.

  All the classes in the section of FIG. 3B are called shaders and are objects (applet class) related to shading of 3D objects. All shaders have a common feature represented by the I3dObject40 class, and all shaders inherit from this class. The shader is owned by the Shape31 object. The shader plays a role of rasterizing the owned Shape 31 (creating a 2D bitmap image). Each shader depicts the shape (shape) owned by the shader differently. The shader takes into account scene light, shape color information, shape texture information, etc., and performs operations necessary to rasterize the shape. Each shader that uses this information may use a different method or ignore some of this information. Shape shaders are defined by the “Shade Type” property defined by the 3D scene editor. For example, some shaders create texture shapes, while others create smooth shaded shapes.

  Unlike other shaders, Wire 41 does not display a shape by filling a polygon made up of the shape. This shader draws a wireframe of shapes. This means a line that connects all the points of the shape on which the polygon is drawn to create the wireframe of the shape. The color information of Shape 31 that owns this shader is used as the color for the wire frame.

  Flat 42 depicts a shape with a flat shade. Flat shading is an algorithm where each shape polygon receives a color of the shape and a constant color due to the lights in the scene.

  Gouraud 43 portrays a Gouraud shade shape. Gouraud shading is an algorithm in which the color at three points of each polygon in a shape is calculated according to the color of the shape and the lights in the scene. These colors are then linearly interpolated along the polygon, and the shape is smoothly shaded.

  Environment 44 draws the shape of the texture map. The texture mapping algorithm generates map information based on the directionality of the Transform 32 object including the drawn Shape 31. The algorithm used by this shader is the same as that used by the TextureMap 45 shader except for the map information source. Since the map information now depends on the shape's direction, it looks as if the rotating shape reflects the surroundings or the light source. This illusion can be used to achieve a realistic look and lighting using a simple texture mapping algorithm.

  TextureMap 45 depicts the shape of the texture map. The texture mapping algorithm maps the texture bitmap onto the shape using the map information stored in the Shape31 object that owns the shader object. This renders the shape as if it had some texture or drawn image.

  TextureGur 46 performs both Gouraud shading (such as Gouraud 43) and texture mapping (such as TextureMap 45) to describe the polygons of the shape. This provides an object with texture mapping and smooth shades.

  TextureEnv 47 performs two texture mapping operations with two different texture images and different sets of mapping coordinates, and then combines the images using a blending algorithm. The two mapping operations performed are the same as performing the TextureMap45 rendering algorithm and combining the results with the Environment44 rendering algorithm. This shader is used to give the shape a texture image and reflection / lighting effects.

  The section of FIG. 3 (c) includes other core classes for displaying 3D scenes. These classes contain information necessary for the 3D display engine and perform functions related to this information. For example, Clipper 57 is responsible for rasterization, MyPixelGrabber 51 is responsible for loading an image file, Controller 59 is responsible for changing scene information via a 3D control applet according to a user event, and so on.

The Yoe3types50 class, which needs to be considered as a core class, simply contains the constants used by the Scene36 class, does not perform any function, and does not store any data.
When a 3D compressed file is loaded, the structure of the scene file includes a node representing a scene element or a general scene file. Each node includes subnodes and data fields. Different node types and data field types are identified by their Id numbers preceding them in the file. This class contains constants that indicate the Id of the various possible data nodes and node fields. If a scene loader (running in Scene 36 class) encounters an Id that does not exist in this class, it skips the node or the data field belonging to this node.

  MyPixelGrabber 51 is used in an applet to load an image used in a scene (shape texture, background image, etc.). Also used in conjunction with a class that executes the MyImageObserver52 interface. When the image finishes loading, the MyPixelGrabber 51 object recalls the observer object to inform it that the image has been prepared.

  MyImageObserver 52 defines an interface for a function that is called when the image finishes loading. Some classes implement the MyImageObserver52 interface to notify when the image that requested the load has finished loading. The actual loading of the image by the applet is done using the MyPixelGrabber51 object. When the MyPixelGrabber51 object finishes loading the image, it passes it to the MyImageObserver52 object. An example of such a case is when the applet loads a new background image. The Applet3da56 class calls a method (procedure that defines the operation of the object) in the Yoe3d53 class to set a new background image. The Yoe3d53 that executes the MyImageObserver52 interface creates a MyPixelGrabber51 object that loads an image and then calls a function in the observer (Yeo3d53 in this case). Yoe3d53 contains the loaded image data and uses it to set the applet background.

  Yoe3d53 includes various functions used to perform 3D geometric operations, image processing and mixing operations, rasterization operations, and the like. For example, before the shader class draws a 2D polygon on the screen, the 3D coordinates of each shape's polygon must be converted to 2D coordinate values using a perspective projection algorithm. The function for performing this conversion is executed by Yoe3d53. This class also contains variables used during rasterization of 3D scenes. For example, to accurately display overlapping 3D objects, an algorithm called Z-Buffering is performed by the shader class while embedding each 2D polygon in the displayed bitmap image. The Z-Buffering algorithm requires a large memory buffer that is used to fill the distance from the viewpoint information of each rendered pixel. This memory buffer is in the Yoe3d53 class. The applet contains one generic Yoe3d53 object that resides within the Applet3da56 object.

The I3daPainter 54 that is the parent of the Applet3da56 class is a parent class of the SuperBase55 class. The I3daPainter 54 is merely an interface, does not include actual execution, and other classes that execute the I3daPainter 54 inherit another class. This is also the case with SuperBase 55, which inherits the applet class, which is a standard Java library library class that can be used on any Java-capable system.
The I3daPainter 54 includes an interface for processing events in the scene. Such events include, for example, clicks on shapes or toolbar buttons. These events are then processed accordingly. In the case of Applet3da56, these events are generated by a call from the 3D control applet hosting the applet via the scripting engine described below.

  SuperBase 55 inherits an applet class which is a standard Java library class prepared in any Java-capable system. The basic functions of this class are as described in the description of the Applet3d56 class.

Next, the Applet3da56 class will be described in detail.
Applet3da56 is the main applet class and inherits the Java (R) applet superclass. The applet class provides a standard interface that can be used by all Web browsers that run Java (R) between the applet and its environment, and is executed as part of the standard Java (R) class library. All Java (R) applets displayed on a Web page must be classes that inherit the applet class and implement important interfaces. This interface is a 3D control applet that is executed by a Web browser, using a method of using an applet area via events such as a mouse and a keyboard, a method of processing event input to an applet, and general functions executed in a class. Includes a way to export to be called by.

It is the 3D applet that has defined a new kind of applet by further classifying the applet class. Applet3da56 does not directly inherit the applet class. Instead, it inherits the SuperBase55 class inherited from the applet class.
When the Applet3da class is loaded into the web browser via the 3D control applet, the web browser calls a standard applet interface function executed by Applet3da56.

1) First, the init function (function) is called. This function initializes the internal data of Applet3da56 and loads the scene information into the internal data structure of Applet3da56.
2) Thereafter, the start function is called by the Web browser. As a result, Applet3da56 processes events such as mouse movements and key inputs from the 3D control applet received by the applet. These events are processed by the Controller 59 object included in Applet3da56. Applet3da 56 enters a loop that checks if there is a reason to render the 3D scene (whether something has changed since it was last rendered). If so, draw the scene. The controller 59 is subsequently called to update the scene information by the received event, the change caused by the API function called by the scripting engine, the animation being executed, and the object movement. This process continues in a loop until the applet closes. This loop is as follows.
(A) Change from the last frame?
(B) Call controller to update scene information.
(C) Perform 3D conversion of the entire world on the current viewpoint. (This is done by accessing the Scene36 object stored in Applet3da56)
(D) Draw a scene image. Loop back to (a).
3) When the Web browser closes the applet, it calls the applet3da56 stop / destroy function that publishes the scene information created and stored in Applet3da56.
As specified by the 3D control applet loaded in the web browser, the web browser understands to execute Applet3da56.

  The 3D scene information in the 3D compressed file 60 extracted by the 3D applet has the file contents as shown in FIG. 4 and includes Header 61 (header), Shape 62 (shape), Transform 63 (coordinate conversion), Light 64 (light), It is composed of a camera 65 (camera) or the like, and is stored in a single file as binary data.

FIG. 5 shows each item of the function of Y3dScript API 70 (Application Programming Interface) included in the 3D applet, which is an interface prepared for realizing interactive 3D image display with the user. FIG. 4 is an explanatory diagram of a unique script interface part for performing interactive 3D scene display via a scripting engine.
As shown in FIG. 5, the Y3dScript API 70 includes a Shape 71 (shape), a Shape property 72 (attribute), a Transform 73 (coordinate transformation), a Transform property 74, an Object 75 (object), a Camera 76 (camera), a User interface 77, a user interface 77, and a user interface 77. There are Display 78 (screen display), Animation 79 (animation), and Miscellaneous 80 (others).
The explanation about each function is the same as the explanation about the above-mentioned 3D applet and the explanation described below.

Next, Y3dScript API will be described in detail.
All the functions (functions) of Y3dScriptAPI are public functions executed in the above-mentioned Applet3da56 class or SuperBase55 class. Each 3D applet contains one instance of the Applet3da56 class (materialization: meaning an object created from the class). This instance is a method in which all Java® applets are executed by the Web browser, and is a main applet class loaded and executed by the Web browser. The SuperBase55 class does not have a real instance (substance), and Applet3da56 inherits the SuperBase55 class, so that all Java (R) scripts / API / functions appear to be executed in Applet3da56.

The API function accesses a part of the Applet3da56 function to perform various tasks in the applet. The following is an example (not shown).
1) The setBGColor () function accesses the “yoe3d.m_gbColor” portion of the SuperBase55 class and sets its value. This value is used as the background color of the applet. After that, Applet is repainted by calling the RedeAfterAfter () method of Applet3da56.
2) The setPos () function is used to set the position of the transform in the 3D scene. This is done by accessing a controller object, ie a part of the SuperBase55 class, to see if a particular 3D transform is currently selected. The controller class method is then used to transform the position passed to the function into a coordinate system with the selected transform. After that, the selected “translation” variable is set to a new location and the Applet3da56's RedrawAfterAct () method is used to repaint the applet.

  The above example shows that the Applet3da56 class contains partial objects that manage different aspects of the applet. (The controller contains information about the selected scene element, and yoe3d53 contains general information such as the applet background color.) These objects are accessed by different API functions, after which the applet scene is rendered. Show the effect of lever access. It is important to understand that these objects do not exist only for access by API functions. These are objects that contain scene information and are used to describe the scene. For example, an event occurs by interaction between a corresponding applet and a user via a 3D control applet. These events are also processed in the Applet3da56 class to access objects through event processing.

6A and 6B are diagrams for explaining the operation of the scripting engine generated by the 3D scene editing unit shown in FIG. 1, wherein FIG. 6A is a diagram for explaining a conventional interactive operation, and FIG. 6B is a diagram for explaining an interactive operation of the present invention. .
As shown in FIG. 6 (a), a conventional 3D applet is obtained by a Java (R) script described in an HTML page via a unique Java (R) script API prepared in the 3D applet. A 3D scene that realizes an interactive operation with the user was displayed.
On the other hand, in the present invention, as shown in FIG. 6B, event information from the 3D control applet is delivered to the unique Y3dScript API in the 3D applet via the scripting engine.
The scripting engine compiles a unique script code that conforms to the Java (R) script grammar described in the script description section that customizes the 3D scene and realizes interactive operation with the user in the 3D scene editing means described above. The user event input by the 3D control applet and the control information of the 3D scene are passed through the scripting engine and a unique script interface (Y3dScript API) in the 3D applet.

  FIG. 7 is a schematic explanatory diagram regarding the user interface part of the 3D control applet. Bitmap Button 91 selected by clicking an arbitrary image, button Butt 92 selected by text, check box Check 93 selected from a plurality of candidates, and a combination of these Select combo box 94, list box 95 for selecting and displaying a drop-down list, edit 96 for editing, label 97 that can be jumped by specifying a label, bit map 98 for displaying an arbitrary image, text input field TextArea 99, and confirmation and operation settings are obtained. Various input means including event inputs such as Dialogs 100 are prepared, and the Java (R) script described in the script description part of the 3D scene editing means is prepared. Corresponding 3D control applet by compiling scripts that conform to the capital of the grammar is generated.

FIG. 8 is a diagram showing an example of an HTML source in which applet tags are described. (A) is based on a conventional Java (R) script, and (b) is based on a 3D control applet of the present invention. .
As shown in 101-106 in FIG.
<Apple code = "Applet3da.class" codebase = "../" width = "360" height = "240" id = "Applet1" ARCHIVE = "3danwhere.zip"MAYSCRIPT>
<Param name = "source" value = "example.3da">
:
:
</ Applet>
The Applet3da56 class file is directly called at the “code =” portion of the applet tag, and interactive operation with the user is realized by the Java (R) script 201-205.

On the other hand, in the present invention, as indicated by 301 to 306 in FIG.
<Apple code = "Y3dButton.class" width = "100" height = "30">
<Param name = "name" value = "button1">
<Param name = "Y3dApplet" value = "AppletY3d1">
<Param name = "BGColor" value = "000000">
<Param name = "text" value = "Click me">
</ Applet>
Y3dButton., Which defines an interactive operation with the user in the “code =” part of the applet tag. class (3D control applet) is specified. The portion previously described in Javascript is performed by the 3D control applet and the scripting engine, and the Applet3da56 class file is called through the 3D control applet and the scripting engine. Elements that need to be changed or defined are specified in <param ...>.

Finally, an embodiment of the Web 3D image display system will be described with reference to Example 2 in FIG.
In the second embodiment shown in FIG. 9, the Web 3D image display system of FIG. 1 is configured as a server and a client system. Each information such as a 3D object and a 3D scene is downloaded from a Web server via a communication network, and the client It is configured to display 3D images and 3D animations on a PC web browser.
The Web server 5, FTP server 6, database server 7 and each means 10-17 in the system center 3 and the Web browser and each means 21-26 in the PC 2 are mounted on a commercially available PC (personal computer) or workstation. The computer operates by executing a predetermined program, such as a CPU (Central Control Unit) constituting a PC or a workstation, a storage device such as a memory or a hard disk, a display device for displaying images or text, a keyboard or a mouse, etc. A description of the input device, the input / output device with the communication line, and the like and the configuration drawing thereof are omitted.
In addition, overlapping description of the above-described processing procedure and the like is omitted.

In FIG. 9, 3 is a system center, and 2 is an unspecified number of PCs (client computers) having Web browsers connected to the system center 3 via the Internet 4.
Reference numeral 5 denotes a Web server in the system center 3 that distributes 3D information data 18 to the PC 3 via the Internet 4. An FTP server 6 manages the transfer of the 3D information data 18 and is used when accessing the system center 3 from the outside, but the application is not described here. A database server 7 manages database access. Reference numeral 10 denotes a 3D object creation means for creating a 3D object using various 3D software such as “3ds”. Reference numeral 11 denotes a VRML file generating means for converting the created 3D object file into a VRML format.

12 is a 3D scene customization unit, and 13 is a 3D compressed file generation unit. The 3D scene editing unit extracts scene information from the VRML file, adds customization information, and converts the necessary scene information into a single compressed file. Is stored in a storage device (not shown) as 3D information data 18 together with a texture file (not shown) simultaneously generated by the 3D information storage means 17. Reference numeral 14 denotes 3D applet generation means for generating a 3D applet for performing interactive 3D image display by the 3D scene editing means. Each applet class required to display a 3D scene is saved as a single compressed file.
Reference numeral 15 denotes a 3D control applet generating means for generating a group of applets necessary for handling event inputs accompanying interactive operations with the user as a compressed file. The applet group generated by the 3D control applet generation means 15 includes not only an interface for interactive operation with a user but also an interface with a 3D applet for displaying a 3D object and a 3D scene.

Reference numeral 16 denotes a Web page generation unit that automatically generates a Web page (HTML page) including the 3D control applet tag generated by the 3D control applet generation unit 15 for displaying a 3D scene.
Reference numeral 17 denotes a 3D information storage unit for storing various 3D information necessary for displaying the 3D scene generated by the 3D scene editing unit. The 3D information storage unit 17 is generated by each generation unit necessary for displaying the 3D scene on the Web browser. These various types of 3D information are stored and accumulated as 3D information data 18 in a storage device (not shown) in the Web image generation system.

  On the other hand, the Web browser in the PC 2 has processing functions such as HTML, Java (R) applet, etc., 21 is a 3D control applet request means, and tags described in the HTML page as shown in FIG. To request the Web server 5 of the system center 3 to download the 3D control applet. The downloaded 3D control applet is executed by a VM (virtual machine) in the Web browser (3D control applet execution means 24), and the execution of the 3D control applet activates the 3D applet request means 22 to execute the downloaded 3D applet. The (3D applet executing means 25) activates the 3D compressed file requesting means 23, downloads the 3D compressed file and the texture file, and displays the 3D scene. Reference numeral 26 denotes an interactive display processing means for displaying a 3D scene that realizes an interactive operation with a user using a Web browser alone.

  The embodiment described above is configured to display a 3D scene on a Web browser on a PC. However, the present invention is not limited to a desktop type or a notebook type PC, but a PDA (personal digital assistant), a mobile phone, or the like. 3D scenes can be displayed on a web browser-equipped device having a VM mounted on a mobile terminal of the user, and a 3D scene that can be interactively operated with a user can be displayed using only a Java (R) applet as described above. Because it is configured, it can be incorporated into office equipment, medical equipment, home appliances, AV (audio / video) equipment equipped with VMs (virtual machines), or in-car equipment such as car navigation and instrument panels. . By adopting a system that does not select a platform in this way, 3D scenes can be displayed on various electronic devices, and the applicability of the 3D scenes extends to various fields.

It is the schematic which shows the structure of the web 3D image display system in embodiment of this invention, (a) is a web 3D image generation system, (b) is each structure of the web browser which displays the produced | generated Web 3D image. FIG. 2 is a processing flowchart of the Web3D image display system shown in FIG. 1. It is the schematic which shows the structure of 3D applet shown in FIG. It is a schematic block diagram which shows the content of the 3D compression file shown in FIG. It is a schematic block diagram of the script interface part of 3D applet shown in FIG. 2A and 2B are operation explanatory views of a scripting engine generated by the 3D scene editing unit shown in FIG. 1, wherein FIG. 1A is a conventional interactive operation, and FIG. 1B is an interactive operation explanatory view of the present invention. It is a schematic explanatory drawing of the user interface part of 3D control applet shown in FIG. It is a figure which shows an example of the HTML source by which the applet tag was described, (a) is based on the conventional Java (R) script, (b) is based on the 3D control applet of this invention. It is a schematic block diagram of Example 2 of the Web3D image display system in the embodiment of the present invention.

Explanation of symbols

1 Web3D image generation system 2 PC (Web browser)
3 System Center 4 Communication Network 5 Web Server 6 FTP Server 7 Database Server 10 3D Object Creation Unit 11 VRML File Generation Unit 12 3D Scene Customization Unit 13 3D Compressed File Generation Unit 14 3D Applet Generation Unit 15 3D Control Applet Generation Unit 16 Web Page Generation means 17 3D information storage means 18, 27 3D information data 21 3D control applet request means 22 3D applet request means 23 3D compressed file request means 24 3D control applet execution means 25 3D applet execution means 26 Interactive display processing means 26

Claims (9)

Edit a 3D scene based on a Web3D file in a file format described in a standard 3D graphics description language for Web such as VRML generated by various 3D modeling software programs, and display the 3D scene on a Web browser A computer system,
3D scene customization means for customizing a 3D scene based on the Web3D file including a 3D object and 3D scene information and providing various information for displaying the 3D scene on the Web browser;
3D compressed file generation means for compressing a 3D object and 3D scene information including attribute information necessary for animation obtained from the Web 3D file and generating a 3D compressed file;
3D applet generation means for generating a 3D applet for displaying a 3D scene by executing real-time 3D rendering and motion algorithm on the Web browser based on the 3D object and 3D scene information of the compressed 3D compressed file;
3D control applet generation means for generating a 3D control applet for performing an interactive operation with a user such as transferring and changing a 3D object by passing a user event input by a keyboard / mouse on the web browser to the 3D applet;
Web page generating means for generating a Web page including an applet tag for calling the 3D applet and the 3D control applet;
3D information storage means for storing a 3D information file including the generated 3D compressed file, the 3D applet, the 3D control applet, the web page, and a texture file necessary for displaying a 3D scene in a storage device; 3D scene editing means including at least
3D applet execution means for reading the stored 3D information file by the web browser and executing the 3D applet and the 3D control applet;
An interactive display processing means for displaying an interactive 3D scene with a user by executing the 3D applet and the 3D control applet, and a Web 3D image display system.   2. The 3D compressed file includes 3D scene information including at least shape, coordinate conversion, light, and camera information called from the 3D applet, and is stored in a single file as binary data. The Web3D image display system described.   The 3D applet includes a plurality of applet classes, each class of scene elements including at least shape, coordinate transformation, light, and camera, a shader class including wireframe, flat shading, and goo shading, and 3D 2. The Web3D according to claim 1, wherein the class necessary for displaying the 3D scene is selected from each class including various core classes for displaying an image, and is stored as one compressed file. Image display system.   The information exchanged with the 3D applet by executing the 3D control applet includes at least an object, a shape, coordinates, a camera, an animation, an image display, and a user interface in order to display a 3D image that can be interactively operated with a user. The Web 3D image display system according to claim 1, comprising any one or more of each of the information.   The 3D control applet includes at least a selection button based on an image, a selection button based on a text, a check box selected from a plurality of candidates, a selection button selected based on a drop-down list, and a user interface class including a text input field, and a Web page A plurality of applet classes including tag range designation, image tag information, and text area tag information classes constitute a part of information exchanged with the 3D applet, and the interactive class is created from within each class. 2. The Web3D image display system according to claim 1, wherein the class required for operation is selected and saved as one compressed file. The 3D applet has a unique script interface that enables interactive operation with a user through script code;
2. The Web 3D image display according to claim 1, wherein the 3D scene information and the information accompanying the interactive operation are exchanged with the 3D applet by executing the 3D control applet through the script interface. system.   The 3D scene customizing unit includes a script language editing unit for customizing the 3D scene and a program source compiling unit described in the script language. The script is obtained by executing the 3D control applet by the compiling unit. The Web 3D image display system according to claim 1, wherein a scripting engine for exchanging information with the 3D applet via an interface is generated.   The 3D scene editing means includes a preview unit for confirming and displaying the 3D scene including a 3D image displayed on a web browser, an animation of a 3D image, a user operation button for performing an interactive operation with a user, and the like. The Web 3D image display system according to claim 1, further comprising display means including at least a script description unit for customizing the 3D scene of the preview unit. The customization of the 3D scene such as the shape, coordinates, camera, texture, animation, interactive operation with the user, etc. of the 3D image in the script description part is reflected in the corresponding part of the 3D scene in the preview part for each program step,
The change of the 3D scene caused by the interactive operation by the user operation button or the like of the preview part is reflected in the description part of the program source text of the script description part,
9. The Web 3D image display system according to claim 8, wherein an editing result or an operation result of either the script description part or the preview part is mutually reflected in substantially real time.

Images