A webpage three-dimensional scene data lightweight processing method and system

Abstract

The application relates to the technical field of three-dimensional data processing, and discloses a webpage three-dimensional scene data lightweight processing method and system, which classifies and manages three-dimensional models in a three-dimensional scene, extracts feature parameters of the models to be created and saves the feature parameters; when a three-dimensional scene is loaded, the same three-dimensional models in the same scene are cached into a local cache library. The application solves the problems of slow uploading speed, relatively large consumption of network resources, inconvenience for users and the like.

Description

Technical Field

[0001] This invention relates to the field of 3D data processing technology, specifically a lightweight processing method and system for 3D scene data of web pages. Background Technology

[0002] When marketing personnel communicate with clients about proposed solutions, they often use drag-and-drop model loading to create 3D solution presentations. Due to varying degrees of complexity, complex solutions can involve anywhere from hundreds to tens of thousands of models in the resulting 3D scene. If a single model is around 1MB, the storage space required after the 3D scene is built can range from hundreds of megabytes (MB) to gigabytes (GB). Using conventional full-scale 3D scene saving methods would require sending network requests to the server for storage, resulting in slow upload speeds, high network resource consumption, and inconvenience for users. Summary of the Invention

[0003] To overcome the shortcomings of existing technologies, this invention provides a lightweight processing method and system for webpage 3D scene data, solving problems such as slow upload speed, excessive network resource consumption, and inconvenience for users.

[0004] The technical solution adopted by the present invention to solve the above problems is:

[0005] A lightweight processing method for webpage 3D scene data is proposed, which classifies and manages 3D models in the 3D scene, extracts and saves the feature parameters of the 3D models, and caches the same 3D models in the same scene to the local cache library when loading the 3D scene.

[0006] As a preferred technical solution, the steps include:

[0007] SA, 3D Scene Saving: Stores the feature parameters of the 3D model in the 3D scene;

[0008] SB, 3D Scene Loading: Loads the feature parameters of the 3D model in the 3D scene.

[0009] As a preferred technical solution, step SA includes the following steps:

[0010] SA1, users upload 3D models in FBX format to the hardware product library;

[0011] SA2, Enter the basic information of the 3D model;

[0012] SA3 allows you to load and build models; and also allows you to create and build custom models.

[0013] SA4, Model Information Classification and Writing to Model Set: Based on the model model, the model information is classified and written to the corresponding model set. When a model is deleted in the scene, the current model is removed from the model set.

[0014] SA5, Enable Scene Saving: Enables the scene saving function;

[0015] SA6, Model Feature Parameter Extraction: Extract model feature parameters based on model type;

[0016] SA7 performs parameter assembly: all extracted model feature parameters are assembled into JSON data and uploaded to the server for storage.

[0017] As a preferred technical solution, SA4 includes the following steps:

[0018] SA41: After the basic information is entered, the image bound to the 3D model is tiled in the sidebar of the webpage. When the user clicks on the model image, a network request is initiated to download the FBX model file from the server. The 3D model file is parsed, and the model is rendered in the browser. After successful loading, the model is stored locally. When the model is loaded again, it is loaded locally without initiating a network request.

[0019] SA42, when loading a model, generates a unique model ID, binds the product ID, model, and model name in the price library, and sets the equipment type, conveying speed, lifting speed, pick-up and drop-off speed, number of pieces / hour, pick-up and drop-off equipment, and loading equipment name;

[0020] SA43 allows users to create drag-and-drop control tools by building modules on a webpage, clicking on the rendered 3D model, and using the XYZ axes and center point in the tool to move and modify the model's position by holding down the mouse.

[0021] SA44 allows users to create custom models of shelves, floors, tracks, text, and walls by building modules within a webpage.

[0022] As a preferred technical solution, in SA6, the method for extracting model feature parameters based on model type is as follows:

[0023] If the model type is floor type, extract the floor ID, floor name, floor height, and floor length and width;

[0024] If the model type is a shelf, extract the shelf location depth, shelf location length, shelf location height, number of shelf location columns, number of shelf location layers, column thickness, beam height, and picking height. Also extract the shelf model ID, center point coordinates, shelf length, width, height, rotation angle, and model color.

[0025] If the model type is a trajectory line, extract the straight lines, curves, docking points, and arrow models and their corresponding model parameters in sequence. At the same time, extract the ID, coordinates, model length, width, height, rotation angle, and model color of the overall trajectory line model.

[0026] If the model type is text, extract the model ID, text name, text size, model coordinates, model length, width and height, rotation angle, and model color;

[0027] If the model type is a path set, extract the path ID, path name, preceding model ID, and subsequent model ID from the path set;

[0028] If the model type is a module type, extract the module ID, module name, module length, width, height, and rotation angle, and then iterate through the models in the module in turn.

[0029] If the model type is a self-built model, extract the following information: model product library ID, hardware product library ID, model center point coordinates, model length, width, height, rotation angle, and model color.

[0030] As a preferred technical solution, in step SA6, if the model type is a trajectory line type, when the type is a straight line, the line segment type, start point, end point, and center point coordinates of the line segment are extracted; when the type is a curve, the line segment type, start point, end point, and center point coordinates of the line segment in the drawing direction are extracted; when the type is a stop point, the stop point type and center point coordinates are extracted; when the type is an arrow, the arrow type, start point coordinates, end point coordinates, and center point coordinates of the arrow are extracted.

[0031] As a preferred technical solution, step SB includes the following steps:

[0032] SB1: Select the saved scene scheme and send a network request to load the scene file from the server;

[0033] SB2, parses the scene file;

[0034] SB3: Determine if the model in the scene file is a self-built model; if not, proceed to step SB4; if yes, proceed to step SB5.

[0035] As a preferred technical solution, step SB4 includes the following steps:

[0036] SB41, execute external model loading;

[0037] SB42, Determine if the current model exists in the scene; if yes, clone the model in the scene; if no, proceed to step SB43;

[0038] SB43 checks if the current model is cached locally. If so, it reads the model from the local cache, parses the file, and creates a 3D model. If not, it initiates a network request to retrieve the model file from the server and writes the file to the local cache.

[0039] As a preferred technical solution, step SB5 includes the following steps:

[0040] SB51, Load the model based on the model type;

[0041] SB52 checks if a model with the same parameters already exists in the scene; if yes, clones the model in the scene; otherwise, creates a new model.

[0042] In SB51, the method for loading models based on model type is as follows:

[0043] If the model type is floor type, create a new floor model based on the floor height, floor length and width, and assign floor ID and floor name;

[0044] If the model type is a shelf, create a shelf model based on the location depth, location length, location height, number of location columns, number of location layers, column thickness, beam height, and picking height, and assign values ​​to the shelf model ID, center point coordinates, shelf length, width, height, rotation angle, and model color.

[0045] If the model type is a trajectory line, extract the straight line, curve, stop point, and arrow model and their corresponding model parameters in sequence, and assign the ID, coordinates, model length, width and height, rotation angle and model color of the overall trajectory line model.

[0046] If the model type is text, create a text model based on the text name and text size, and assign values ​​to the model's ID, model coordinates, model length, width, height, rotation angle, and model color.

[0047] If the model type is a path set, determine whether the model has been successfully loaded from the loaded scene based on the path ID, path name, preceding model ID, and subsequent model ID in the path set. If the model is successfully loaded, create a new path set.

[0048] If the model type is a module type, create an empty module model, assign the module ID, module name, module length, width, height, and rotation angle, and then iterate through the models in the module.

[0049] A lightweight webpage 3D scene data processing system, used to implement the aforementioned lightweight webpage 3D scene data processing method, includes the following interconnected modules:

[0050] 3D scene storage module: Used to store the feature parameters of 3D models in a 3D scene;

[0051] 3D Scene Loading Module: Used to load the feature parameters of 3D models in a 3D scene.

[0052] Compared with the prior art, the present invention has the following advantages:

[0053] (1) The self-built model of this invention is stored in the local cache after the first loading. When it is loaded again, it supports copying the model in the cache library when the model type and model attributes are consistent, thus reducing the computational overhead of the local client.

[0054] (2) This invention classifies and manages models in a 3D scene, extracts and saves the feature parameters of the created model, reduces the amount of data to be saved in a large scene, and improves the scene saving and loading speed.

[0055] (3) When loading a 3D scene, the present invention caches the same model in the same scene to the local cache library, saving network resources and accelerating model construction. Attached Figure Description

[0056] Figure 1 A flowchart illustrating the process of lightweight saving of 3D scenes;

[0057] Figure 2 for Figure 1 One of the magnified views of a section;

[0058] Figure 3 for Figure 1 The second enlarged view of a section;

[0059] Figure 4 for Figure 1 The third enlarged view of a section;

[0060] Figure 5 A flowchart illustrating the lightweight loading process for a 3D scene;

[0061] Figure 6 for Figure 4 One of the magnified views of a section;

[0062] Figure 7 for Figure 5 The second enlarged view of a section;

[0063] Figure 8 for Figure 5 The third enlarged view of a section;

[0064] Figure 9 A flowchart illustrating the process of inputting basic information for a 3D model;

[0065] Figure 10 A flowchart illustrating the process of modifying model attributes;

[0066] Figure 11This is a schematic diagram illustrating the steps of a lightweight webpage 3D scene data processing method according to the present invention (including saving and loading). Detailed Implementation

[0067] The present invention will be further described in detail below with reference to the embodiments and accompanying drawings, but the embodiments of the present invention are not limited thereto.

[0068] Example 1

[0069] like Figures 1 to 11 As shown, in response to the problems in the background technology, a lightweight method for saving and loading web page 3D scenes has been invented. The system extracts and stores the feature parameters of individual models in the 3D scene, and finally reduces the storage of scenes of hundreds of megabytes to less than 10 megabytes on the server, thereby reducing the consumption of network resources and improving the speed of loading and saving 3D scenes.

[0070] This invention relates to loading 3D models in FBX format, generating self-built models, and lightweight storage and loading of 3D scenes. The aim is to quickly save and load 3D model scenes for web pages, and to identify parameters of the 3D models within the scene, providing attribute support for subsequent model assignment operations and scene animation. The specific implementation method is as follows: Figure 1 As shown.

[0071] SA1. Users open the system in a web browser, select the FBX format model exported from 3DMAX for uploading. During the model upload, the system binds the 3D model file with the system hardware product price database data.

[0072] SA2. Enter the basic information of the model into the system. The information includes conveying speed, lifting speed, picking and placing speed, number of pieces / hour, equipment function type (conveying equipment, single machine equipment, storage equipment, track equipment, code sorting equipment, robot equipment, AGV equipment), define the name of picking and placing equipment and the name of loading equipment. The name corresponds to the sub-model in the 3D model, and upload the model screenshot.

[0073] SA3. After the basic information is entered, the system will tile the image bound to the 3D model in the sidebar of the webpage. When the user clicks on the model image, the system will initiate a network request to download the FBX model file from the server. The system will parse the 3D model file and render the model in the browser. After successful loading, the system will store the model locally. When the model is loaded again, the system will load it locally without initiating a network request, thus reducing network overhead.

[0074] When the system loads a model, it generates a unique model ID, binds it to the product ID, model, and model name in the price database, sets the equipment type (conveyor equipment, single machine equipment, storage equipment, track equipment, code sorting machine equipment, robot equipment), and sets the conveying speed, lifting speed, picking and placing speed, number of pieces / hour, picking and placing equipment, and loading equipment name.

[0075] Users can build modules on the webpage, click on the rendered 3D model, and the system will create a drag-and-drop control tool for the model. Users can use the XYZ axes and center point in the tool, and hold down the mouse to move and modify the position of the model.

[0076] Users can create their own models such as shelves, floors, trajectory lines, text, and walls by building modules on the webpage.

[0077] SA4. When a user loads an FBX model or creates a self-built model, the system writes the model ID and model number into the corresponding model set A_Models[modelA,modelB,modelc] and B_Models[modelA,modelB,modelc] based on the model model. When a model is deleted in the scene, the current model is removed from the model set.

[0078] When saving in SA5 and SA6, the system iterates through the set of models in the scene and extracts different parameters based on the model type.

[0079] If it is not a self-built model, record the model product library ID, hardware product library ID, model center point coordinates, model length, width and height, rotation angle, and model color. Self-built models will proceed to the next step for processing.

[0080] If it is a floor type, the system extracts the floor ID, floor name, floor height, and floor length and width.

[0081] If it is a shelving type, the system extracts the location depth, location length, location height, number of rows, number of layers, column thickness, beam height, and retrieval height. It also extracts the shelving model ID, center point coordinates, shelving dimensions (length, width, height), rotation angle, and model color.

[0082] If the type is a trajectory line, the system sequentially extracts the models of straight lines, curves, stops, and arrows from the trajectory line. When the type is a straight line: it extracts the line segment type, start point, end point, and center point coordinates. When the type is a curve: it extracts the line segment type, start point, end point, line segment drawing direction (clockwise, counterclockwise), and center point coordinates. When the type is a stop point: it extracts the stop point type and center point coordinates. When the type is an arrow: it extracts the arrow type, start point coordinates, end point coordinates, and center point coordinates. Simultaneously, it extracts the overall trajectory line model's ID, coordinates, model length, width, height, rotation angle, and model color.

[0083] If it is a text type, the system extracts the model's ID, text name, text size, model coordinates, model length, width and height, rotation angle, and model color.

[0084] If it is a module type, the system extracts the module ID, module name, module length, width, height, and rotation angle. Simultaneously, step S8 is executed to extract different types of model parameters within the module.

[0085] The system extracts the path ID, path name, preceding model ID, and subsequent model ID from the path set.

[0086] SA7. The system assembles all extracted model feature parameters into JSON data and uploads it to the server for storage. Throughout this process, conventional scene saving involves storing vertex data, triangle indices, and textures of all models in the scene, resulting in a massive amount of information, ranging from hundreds of megabytes (MB) to gigabytes (GB). This method, by extracting the scene model's feature parameters and storing them on the server, reduces the scene's size from hundreds of megabytes (MB) to less than 10 MB, significantly improving the saving speed.

[0087] When a user loads a saved scene from the system, the stored scene has been streamlined from hundreds of megabytes to less than 10MB. This also reduces the network resources consumed by the system when loading the server scene. The specific steps are as follows: Figure 5 As shown.

[0088] SB1: When the user selects a saved scene scheme in the system, the system sends a network request to load the scene file from the server.

[0089] SB2 and SB3: The system parses the scene file, iterates through the model parameters in the file, and if it is an external model, removes the model product library ID parameter. The system matches the product library model file URL address, initiates a network request to load the corresponding FBX format model file, and assigns parameters such as coordinates, length, width, height, and rotation angle to the model. After the model is loaded for the first time, it is cached locally to reduce the network overhead of repeated loading. If it is a self-built model, it proceeds to the next step for processing.

[0090] If it is a floor type, the system creates a new floor model based on the floor height, floor length and width, and assigns a floor ID and floor name.

[0091] If it is a shelf type, the system creates a shelf model based on the depth, length, height, number of rows, number of layers, column thickness, beam height, and picking height, and assigns the shelf model ID, center point coordinates, shelf length, width, height, rotation angle, and model color.

[0092] If the type is a trajectory line, the system sequentially parses the straight lines, curves, docking points, arrows, and other models within the trajectory line. When the type is a straight line: a straight line is created based on the start and end points, and the line segment type and center point coordinates are assigned. When the type is a curve: a curve is created based on the start and end points and the line segment drawing direction (clockwise or counterclockwise), and the line segment type and center point coordinates are assigned. When the type is a docking point: a docking point model is created and the docking point type and center point coordinates are assigned. When the type is an arrow: an arrow line segment is created based on the start and end point coordinates and the arrow type and center point coordinates are assigned. Simultaneously, the overall trajectory line model's ID, coordinates, model length, width, height, rotation angle, and model color are assigned.

[0093] If it is a text type, the system creates a text model based on the text name and text size, and assigns the model's ID, model coordinates, model length, width and height, rotation angle, and model color.

[0094] If it is a module type, the system creates an empty module model and assigns the module ID, module name, module length, width, height, and rotation angle. At the same time, steps S17-S22 are executed to create different types of models within the module and add them to the empty module model.

[0095] The system determines whether a model has been successfully loaded from the loaded scene based on the path ID, path name, preceding model ID, and subsequent model ID in the path set. If the model is successfully loaded, a new path set is created.

[0096] It should be noted that the following examples illustrate the concept of "system":

[0097] The "system" provided in this embodiment has the following features and functions:

[0098] This software, developed using the Three.js 3D engine, loads external FBX models or creates basic 3D models using the Three.js engine, assembling them into meaningful models such as shelves, trajectory lines, and text. Users upload FBX format models and input model parameters on a webpage, then load, create, and drag the models to form a complete 3D scene. Conventional 3D scene saving methods store the entire scene data, consuming enormous space, and the network request from the webpage to the server takes considerable time. Therefore, this method extracts feature parameters from the complete 3D scene, extracting different model feature parameters based on the model type. Finally, it merges and assembles the parameters of all models in the scene into a scene JSON file, which is then uploaded to the server for storage. Users can view the saved scene information on a webpage and recreate the scene, achieving rapid saving and loading of 3D scenes.

[0099] It should be noted that the above description of the "system" does not imply that such a "system" is an essential technical feature, nor should it limit the scope of protection of this invention. This embodiment merely employs the method of utilizing the "system" for the purpose of more conveniently and clearly explaining the content of this invention.

[0100] In summary, the present invention has the following characteristics:

[0101] The invention stores the self-built model in the local cache after the first loading. When loading again, if the model type and model attributes are consistent, it supports copying the model from the cache library, reducing the computational overhead of the local client.

[0102] This invention classifies and manages models in a 3D scene, extracts and saves the feature parameters of the created model, reduces the amount of data to be saved in a large scene, and improves the scene saving and loading speed.

[0103] When loading a 3D scene, this invention caches the same model in the same scene to a local cache library, saving network resources and accelerating model construction.

[0104] As described above, the present invention can be implemented well.

[0105] All features disclosed in all embodiments of this specification, or steps in all methods or processes implied in the disclosure, may be combined and / or extended or replaced in any way, except for mutually exclusive features and / or steps.

[0106] The above description is merely a preferred embodiment of the present invention and is not intended to limit the present invention in any way. Based on the technical essence of the present invention, any simple modifications, equivalent substitutions, and improvements made to the above embodiments within the spirit and principles of the present invention shall still fall within the protection scope of the present invention.

Claims

1. A lightweight processing method for webpage 3D scene data, characterized in that, The process involves classifying and managing 3D models within a 3D scene, extracting and saving their feature parameters, and caching identical 3D models within the same scene to a local cache when loading the scene. This includes the following steps: SA, 3D Scene Saving: Stores the feature parameters of the 3D model in the 3D scene; Step SA includes the following steps: SA1, users upload 3D models in FBX format to the hardware product library; SA2, Enter the basic information of the 3D model; SA3 allows you to load and build models; and also allows you to create and build custom models. SA4, Model Information Classification and Writing to Model Set: Based on the model model, the model information is classified and written to the corresponding model set. When a model is deleted in the scene, the current model is removed from the model set. SA5, Enable Scene Saving: Enables the scene saving function; SA6, Model Feature Parameter Extraction: Extract model feature parameters based on model type; SA7 performs parameter assembly: all extracted model feature parameters are assembled into JSON data and uploaded to the server for storage; SA4 includes the following steps: SA41: After the basic information is entered, the image bound to the 3D model is tiled in the sidebar of the webpage. When the user clicks on the model image, a network request is initiated to download the FBX model file from the server. The 3D model file is parsed, and the model is rendered in the browser. After successful loading, the model is stored locally. When the model is loaded again, it is loaded locally without initiating a network request. SA42, when loading a model, generates a unique model ID, binds the product ID, model, and model name in the price library, and sets the equipment type, conveying speed, lifting speed, pick-up and drop-off speed, number of pieces / hour, pick-up and drop-off equipment, and loading equipment name; SA43 allows users to create drag-and-drop control tools by building modules on a webpage, clicking on the rendered 3D model, and using the XYZ axes and center point in the tool to move and modify the model's position by holding down the mouse. SA44 allows users to create custom models of shelves, floors, trajectory lines, text, and walls by building modules within a webpage. In SA6, the method for extracting model feature parameters based on model type is as follows: If the model type is floor type, extract the floor ID, floor name, floor height, and floor length and width; If the model type is a shelf, extract the shelf location depth, shelf location length, shelf location height, number of shelf location columns, number of shelf location layers, column thickness, beam height, and picking height. Also extract the shelf model ID, center point coordinates, shelf length, width, height, rotation angle, and model color. If the model type is a trajectory line, extract the straight lines, curves, docking points, and arrow models and their corresponding model parameters in sequence. At the same time, extract the ID, coordinates, model length, width, height, rotation angle, and model color of the overall trajectory line model. If the model type is text, extract the model ID, text name, text size, model coordinates, model length, width and height, rotation angle, and model color; If the model type is a path set, extract the path ID, path name, preceding model ID, and subsequent model ID from the path set; If the model type is a module type, extract the module ID, module name, module length, width, height, and rotation angle, and then iterate through the models in the module in turn. If the model type is a self-built model, extract the following information: model product library ID, hardware product library ID, model center point coordinates, model length, width, height, rotation angle, and model color.

2. The lightweight processing method for webpage 3D scene data according to claim 1, characterized in that, It also includes the following steps: SB, 3D Scene Loading: Loads the feature parameters of the 3D model in the 3D scene.

3. The lightweight processing method for webpage 3D scene data according to claim 1, characterized in that, In step SA6, if the model type is a trajectory line, when the type is a straight line, extract the line segment type, start point, end point, and center point coordinates of the line segment; when the type is a curve, extract the line segment type, start point, end point, and center point coordinates of the line segment in the drawing direction; when the type is a stop point, extract the stop point type and center point coordinates; when the type is an arrow, extract the arrow type, start point coordinates, end point coordinates, and center point coordinates of the arrow.

4. The lightweight processing method for webpage 3D scene data according to claim 2, characterized in that, Step SB includes the following steps: SB1: Select the saved scene scheme and send a network request to load the scene file from the server; SB2, parses the scene file; SB3: Determine if the model in the scene file is a self-built model; if not, proceed to step SB4; if yes, proceed to step SB5.

5. The lightweight processing method for webpage 3D scene data according to claim 4, characterized in that, Step SB4 includes the following steps: SB41, execute external model loading; SB42, Determine if the current model exists in the scene; if yes, clone the model in the scene; if no, proceed to step SB43; SB43 checks if the current model is cached locally. If so, it reads the model from the local cache, parses the file, and creates a 3D model. If not, it initiates a network request to retrieve the model file from the server and writes the file to the local cache.

6. The lightweight processing method for webpage 3D scene data according to claim 5, characterized in that, Step SB5 includes the following steps: SB51, Load the model based on the model type; SB52 checks if a model with the same parameters already exists in the scene; if yes, clones the model in the scene; otherwise, creates a new model. In SB51, the method for loading models based on model type is as follows: If the model type is floor type, create a new floor model based on the floor height, floor length and width, and assign floor ID and floor name; If the model type is a shelf, create a shelf model based on the location depth, location length, location height, number of location columns, number of location layers, column thickness, beam height, and picking height, and assign values ​​to the shelf model ID, center point coordinates, shelf length, width, height, rotation angle, and model color. If the model type is a trajectory line, extract the straight line, curve, stop point, and arrow model and their corresponding model parameters in sequence, and assign the ID, coordinates, model length, width and height, rotation angle and model color of the overall trajectory line model. If the model type is text, create a text model based on the text name and text size, and assign values ​​to the model's ID, model coordinates, model length, width, height, rotation angle, and model color. If the model type is a path set, determine whether the model has been successfully loaded from the loaded scene based on the path ID, path name, preceding model ID, and subsequent model ID in the path set. If the model is successfully loaded, create a new path set. If the model type is a module type, create an empty module model, assign the module ID, module name, module length, width, height, and rotation angle, and then iterate through the models in the module.

7. A lightweight processing system for webpage 3D scene data, characterized in that, A lightweight processing method for webpage 3D scene data as described in any one of claims 1 to 6 includes the following connected modules: 3D scene storage module: Used to store the feature parameters of 3D models in a 3D scene; 3D Scene Loading Module: Used to load the feature parameters of 3D models in a 3D scene.

Images