CN117274457A - A 3D model hierarchical compression and display method, device, storage medium and equipment - Google Patents

Abstract

The specification provides a 3D model hierarchical compression and display method, a device, a storage medium and computer equipment, which are applied to a user client. The server corresponding to the user client maintains model files corresponding to the definition levels respectively, wherein the model files are obtained by carrying out hierarchical compression on original model files corresponding to the 3D model according to the preset definition levels. The 3D model grading display method comprises the following steps: determining a target definition level corresponding to an operating environment of the user client in response to a model presentation request for the 3D model; acquiring a target model file corresponding to the target definition level from the server; and loading the obtained target model file to display the 3D model to a user.

Description

A 3D model hierarchical compression and display method, device, storage medium and equipment

Technical field

The embodiments of this specification relate to the field of computer technology, and more specifically, the embodiments of this specification relate to a 3D model hierarchical compression and display method, device, storage medium and equipment.

Background technique

With the continuous development of computer graphics and computing power, when displaying objects and scenes, such as museum collections and merchant merchandise displays, in addition to traditional display methods such as text, pictures, and videos, more and more platforms and users Start paying attention to the way objects are displayed using 3D models. However, 3D model production and transmission usually require high costs, and 3D models usually require large resource overhead when loading.

Contents of the invention

In order to overcome the problems existing in related technologies, this specification provides the following methods and devices.

In the first aspect of the implementation of this specification, a 3D model hierarchical display method is provided, which is applied to the user client; the server corresponding to the user client maintains multiple preset definition levels for all objects. The original model files corresponding to the 3D model are obtained after hierarchical compression, and the model files respectively corresponding to the multiple definition levels are obtained; the method includes:

In response to a model display request for the 3D model, determining a target clarity level corresponding to the operating environment of the user client;

Obtain the target model file corresponding to the target clarity level from the server;

Load the obtained target model file to display the 3D model to the user.

In the second aspect of the implementation of this specification, a 3D model hierarchical display device is provided, which is applied to a user client; the server corresponding to the user client maintains a plurality of preset definition levels for all objects. The original model files corresponding to the 3D model are obtained after hierarchical compression, and the model files respectively corresponding to the multiple definition levels are obtained; the device includes:

a determining unit configured to determine a target clarity level corresponding to the running environment of the user client in response to a model display request for the 3D model;

An acquisition unit, configured to acquire the target model file corresponding to the target clarity level from the server;

A loading unit is used to load the obtained target model file to display the 3D model to the user.

In the third aspect of the implementation of this specification, a 3D model hierarchical compression method is also provided, which is applied to the server; the method includes:

Obtain the original model file corresponding to the 3D model, and perform hierarchical compression on the original model file according to multiple preset definition levels to obtain model files corresponding to the multiple definition levels;

In response to the file acquisition request for the 3D model sent by the user client, determine the target model file corresponding to the target definition level; wherein the target definition level is the definition corresponding to the running environment of the user client grade;

The target model file is returned to the user client, so that the user client loads the obtained target model file and displays the 3D model to the user.

In the fourth aspect of the implementation of this specification, a 3D model hierarchical compression device is also provided, which is applied to the server; the device includes:

A compression unit, used to obtain the original model file corresponding to the 3D model, and perform hierarchical compression on the original model file according to multiple preset definition levels to obtain model files corresponding to the multiple definition levels;

A selection unit configured to determine a target model file corresponding to a target clarity level in response to a file acquisition request for the 3D model sent by the user client; wherein the target clarity level is the same as the operation of the user client. The clarity level corresponding to the environment;

A return unit is used to return the target model file to the user client, so that the user client loads the obtained target model file and displays the 3D model to the user.

In a fifth aspect of the embodiment of this specification, a storage medium is provided; a computer program is stored on the storage medium, and when the computer program is executed, the steps of the above method are implemented.

In a sixth aspect of the embodiment of this specification, a computer device is provided, including a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein when the processor executes the program Implement the above method.

The above embodiments in this specification have at least the following beneficial effects:

In the above technical solution, the model files corresponding to the 3D model are compressed in stages in advance, and according to the running environment of the user client, the quality loss and file size gain are weighed, and the target definition level is determined, and the corresponding model is obtained from the server. The file is loaded; in low-end devices or when the network environment is poor, the network and device memory pressure can be reduced and the loading speed is improved; while in high-end devices or when the network environment is good, the model quality can be ensured and 3D display can be maximized The details of the model; therefore, the technical solutions in this manual can improve the experience of using 3D models on different devices and network environments.

Description of the drawings

In order to more clearly explain the embodiments of this specification or the technical solutions in the prior art, the drawings needed to be used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings in the following description are only some embodiments recorded in this specification. For those of ordinary skill in the art, other drawings can also be obtained based on these drawings.

Figure 1 schematically shows an architectural diagram of a 3D model hierarchical display method according to an embodiment of this specification;

Figure 2 schematically shows a flow chart of a 3D model hierarchical display method according to an embodiment of this specification;

Figure 3 schematically shows a structural diagram of a 3D model file according to an embodiment of this specification;

Figure 4 schematically shows an interactive flow chart of a 3D model hierarchical compression method according to an embodiment of this specification;

Figure 5 schematically shows a flow chart of a 3D model hierarchical compression method according to an embodiment of this specification;

Figure 6 schematically shows a block diagram of a 3D model hierarchical display device according to an embodiment of this specification;

Figure 7 schematically shows a block diagram of a 3D model hierarchical compression device according to an embodiment of this specification;

FIG. 8 schematically shows a hardware structure diagram of a computer device in which a 3D model hierarchical display method is implemented according to an embodiment of this specification.

In the drawings, the same or corresponding reference numerals represent the same or corresponding parts.

Detailed ways

The principles and spirit of the present specification will be described below with reference to several exemplary embodiments. It should be understood that these embodiments are provided only to enable those skilled in the art to better understand and implement the present specification, and are not intended to limit the scope of the present specification in any way. Rather, these embodiments are provided so that this disclosure will be thorough and complete, and will fully convey the scope of the disclosure to those skilled in the art.

Those skilled in the art know that the embodiments of this specification can be implemented as a system, device, equipment, method or computer program product. Therefore, this specification can be implemented in the following form, namely: complete hardware, complete software (including firmware, resident software, microcode, etc.), or a combination of hardware and software.

First, we will introduce some related concepts that may be involved in the manual:

SoC (System on a Chip) is a chip that integrates multiple key components and functions, including central processing unit (CPU), graphics processing unit (GPU), memory controller, storage controller, and multimedia processing. units, communication modules (such as wireless networking and Bluetooth), sensor interfaces, security modules, etc. In a mobile phone, the SOC is the core component responsible for handling the main computing and control tasks of the mobile phone. It integrates the CPU to perform computing tasks, the GPU for graphics rendering, the multimedia accelerator to process audio and video data, the communication module for network communication, and other necessary interfaces and modules to realize various functions of the mobile phone.

URL (Uniform Resource Locator, Uniform Resource Locator), commonly known as web page address, or URL for short, is the address of a standard resource on the Internet. Usually, each valid URL can point to a unique resource.

With the continuous development of computer graphics and computing power, when displaying objects and scenes, such as museum collections and merchant merchandise displays, in addition to traditional display methods such as text, pictures, and videos, more and more platforms and users Start paying attention to the way objects are displayed using 3D models. However, 3D model production and transmission usually require high costs, and 3D models usually require large resource overhead when loading.

Compared with two-dimensional display forms such as pictures and videos, because 3D models need to display more details of objects in three-dimensional space and support multi-angle viewing, 3D models usually have a larger amount of data and more complex data. Structure usually requires calling the 3D engine of the user client for real-time rendering, thus consuming more resources of the user client.

When a 3D model contains more details, its model file may be larger and consume more network and memory resources when loading. Especially when displaying 3D models on mobile phones, due to the complexity of mobile phone performance and network conditions; on mid- to low-end mobile phones or when the network environment is poor, it may take a long time to load larger 3D models, and errors may occur during display. Stuttering, frame drops and other unsmooth situations.

In view of this, the purpose of this manual is to propose a technical solution that provides different levels of 3D model files for different user client operating environments to adapt to different operating environments for 3D model compression and display.

During implementation, the server can perform hierarchical compression on the original model files of the 3D model according to multiple preset definition levels in advance to obtain multi-level model files with multiple definition levels;

Further, when the user client needs to display the 3D model, the definition level of the 3D model that needs to be displayed can be determined according to the running environment of the user client, and the corresponding model file can be obtained from the server and loaded for display.

It can be seen that in the technical solution in this manual, the model file corresponding to the 3D model is compressed in stages in advance, and the target definition level is determined by weighing the quality loss and file size gain according to the running environment of the user client. Obtain the corresponding model file from the server and load it; in low-end devices or when the network environment is poor, it can reduce the network and device memory pressure and improve the loading speed; and in high-end devices or when the network environment is good, it can ensure Model quality, showing the details of the 3D model to the greatest extent; therefore, the technical solutions in this manual can improve the use experience of the 3D model in different devices and network environments.

The solutions of this specification will be described in detail below with reference to the accompanying drawings.

Please refer to FIG. 1 , which is a schematic architectural diagram of a 3D model hierarchical display system provided by an exemplary embodiment. As shown in Figure 1, the system may include a network 10, a server 11, and several electronic devices, such as computers 12, 13, and 14.

The server 11 may be a physical server including an independent host, or the server 11 may be a virtual server, cloud server, etc. hosted by a host cluster. Computers 12-14 are just one type of electronic device available to users. In fact, users can obviously also use electronic devices such as the following types: tablet devices, mobile phones, PDAs (Personal Digital Assistants), wearable devices (such as smart glasses, smart watches, etc.), etc., one or at least one of this manual An embodiment is not limited in this regard. Network 10 may include various types of wired or wireless networks.

In one embodiment, the server 11 can cooperate with the computers 12-14; the computers 12-14 can accept user operations and upload the received commands and files to the server 11 through the network 10, and then the server 11 can The file is processed according to the program in the instructions. In another embodiment, the computer 12-14 can independently implement the solution of this description; wherein, the computer 12-14 accepts user operations and processes the accepted commands and files based on the solution of this description to achieve 3D model grading. exhibit.

Please refer to Figure 2. Figure 2 is a flow chart of a 3D model hierarchical display method provided by an exemplary embodiment. The method is applied to a processing device. The processing device can be the server 11 or computers 12-14 shown in Figure 1. wait.

The server corresponding to the user client maintains the original model file corresponding to the 3D model according to multiple preset definition levels, and the models corresponding to the multiple definition levels are obtained after hierarchical compression. document;

The method may include the following steps:

Step 202: In response to a model display request for the 3D model, determine a target clarity level corresponding to the running environment of the user client.

Usually, the model file corresponding to the 3D model to be displayed on the user client is stored in the server corresponding to the user client. When the user needs to view the 3D model, the user client can send a request to the server. After the server receives the request , the model file corresponding to the 3D model can be sent to the user client. The user client loads the received model file to display it to the user.

When the model file is large, more resources will be consumed for transmission and loading, which may affect the user experience. Therefore, the model file can be compressed on the server in advance to obtain a model file with lower definition. Generally, a model file with higher definition can show more details, but its file size is larger and consumes more resources to load; a model file with lower definition can show less details, but its file size is larger. The smaller it is, the fewer resources it consumes to load.

It can be seen that model files with lower definition are suitable for loading in user clients with poor running environments; however, for user clients with better running environments, using model files with lower definition will also cause them to lose the model. details, reducing user experience.

Therefore, it is necessary to prepare multiple model files with different resolution levels for user clients that do not require a running environment. Specifically, a hierarchical compression method can be used to compress the original model file at multiple levels based on different compression parameters to obtain model files with multiple definition levels to adapt to user clients in different operating environments.

When the user client needs to display the 3D model to be displayed, for example, the user opens the page where the 3D model is located, the user performs a trigger operation corresponding to the 3D model, etc., it can be regarded as the user client obtains the display of the 3D model. ask;

When the user client obtains the display request, the user client can determine the current running environment of the user client, and determine the target clarity level for 3D model display based on the current running environment.

Among them, the operating environment of the user client may include device performance parameters of the device where the user client is located, current network performance parameters, and user-set preference settings, etc. This specification does not specifically limit this.

The current running environment of the user client may be detected in real time by the user client, or may be stored in the user client, which is not specifically limited in this specification.

In an exemplary embodiment shown in this description, the user client directly maintains the corresponding relationship between the user client's running environment and the target clarity level.

According to the running environment of the user client, the corresponding target definition level can be uniquely determined.

In the running environment of the user client, the factor that has the greatest impact on loading speed is usually the network environment. Since the model file needs to be downloaded from the server to the user client, when the network transmission speed is slow, the model needs to wait for a long time to be downloaded from the server, which consumes more time and the user's patience.

Therefore, the target clarity level can be determined based on the network performance parameters of the user client. Network performance parameters may include network performance, which represents the speed of network transmission.

When the network performance of the user client is high, a higher definition level is determined; when the network performance of the user client is low, a lower definition level is determined.

Network performance parameters may also include network type.

In addition, the user's network type can also affect the determination of the target clarity level. For example, when users use traffic metered networks, such as mobile data, they may be more sensitive to data traffic usage and can be determined to a lower resolution level to use model data with smaller files; while users using non-metered traffic meters When using low-cost data, such as WIFI networks, it is not sensitive to file size and can be determined to a higher definition level to use higher quality model data.

In addition to network performance parameters, device performance parameters can also be used to evaluate the operating environment of the user client.

The higher the performance of the device where the user client is located, the faster the model file will be loaded and the smoother the 3D model will run. Devices with lower device performance may take a longer time to load model files with larger file sizes and more model details, and may experience lags, frame drops, etc. during runtime, affecting the User experience; when loading model files with smaller file sizes and less model details, users can get a better experience because they require lower device performance, faster loading, and smoother operation.

Therefore, when the performance of the device where the user client is located is high, it can be determined to be a higher definition level; when the performance of the device where the user client is located is low, it can be determined to be a lower definition level.

To determine the performance of the device where the user client is located, you can obtain its device model, resolution, SOC parameters, etc., and conduct a comprehensive evaluation of it; usually, the device model and corresponding device performance parameters, or clarity level, can be maintained in the user client corresponding relationship.

In addition, a variety of parameters can also be used to comprehensively evaluate the operating environment of the user client and jointly determine the target clarity level corresponding to the user client.

For example, in an illustrative embodiment shown in this description, the network type used by the device where the user client is located and the device performance parameters can be used to jointly determine the target clarity level.

Taking the device where the client is located as a mobile phone as an example, during implementation, based on preset rules, mobile phones can be divided into high-end machines, mid-range machines and low-end machines according to device performance parameters from high to low; the network used by the mobile phone It is divided into traffic network and WIFI network.

The definition level can be divided into three levels from high to low, original picture OD, high definition HD and standard definition SD.

Among them, when the definition level is the original painting OD, the corresponding model file is the uncompressed original model file.

The corresponding relationship for determining the target clarity level is as follows:

For low-end machines and mid-range machines using data traffic, determine it as standard definition SD; for mid-range machines using WIFI or high-end machines using data traffic, determine it as high definition; for high-end machines using WIFI, determine it as original painting OD.

As shown in the following table:

Low-end machine Mid-range machine High-end machine flow SD SD HD WIFI SD HD OD

Step 204: Obtain the target model file corresponding to the target definition level from the server.

The model files corresponding to the 3D model are hierarchically compressed on the server side and then saved separately. After the user client determines the target clarity level for 3D model display, it can send a request to the server to obtain the model file corresponding to the target clarity level.

After receiving the request, the server can send the model file corresponding to the target clarity level to the user client.

Step 206: Load the obtained target model file to display the 3D model to the user.

After receiving the model file corresponding to the target definition sent by the server, the user client can record the model file and perform real-time rendering to display the above-mentioned 3D model file to be displayed to the user.

In the above embodiment, the model files corresponding to the 3D model are compressed hierarchically in advance, and according to the running environment of the user client, the quality loss and the file size gain are weighed, and the corresponding model is obtained from the server based on the determined target definition level. The file is loaded; in low-end devices or when the network environment is poor, the network and device memory pressure can be reduced and the loading speed is improved; while in high-end devices or when the network environment is good, the model quality can be ensured and 3D display can be maximized The details of the model; therefore, the technical solutions in this manual can improve the experience of using 3D models on different devices and network environments.

Errors and damage to model files may occur during compression, storage, transmission, loading, etc. Therefore, errors may occur when the above model files are loaded on the user client.

When the model file fails to load, you can reload it, including reloading the obtained model file, and re-obtaining the model file from the server for loading, etc.

If the model file still fails to load after reloading multiple times, it means that there may be an error in the model file stored on the server. For example, an error may occur during compression, causing the file to fail to load normally.

You can preset a threshold for the number of loading failures, such as 3 times/5 times, etc. When the number of loading failures exceeds the threshold, it can be considered that reloading cannot solve the problem of loading failures.

At this time, you can obtain the uncompressed model file with the resolution level of the original painting from the server and load it.

In an exemplary embodiment shown in this description, the model file corresponding to the 3D model consists of two parts, the model main file and the model external data. Model external data, also known as remote resources, are stored in external storage space. Only the address where the model external data is stored is saved in the model main file. When the model main file needs to be loaded, the model can be obtained from the corresponding address based on this address. external data.

Using this separated mode to store model files can reduce the size of the main model file.

The model body file is usually a description file used to describe the content of the three-dimensional scene that makes up the 3D model. Some of the content can be represented in the form of external data of the remote model, such as model geometry data describing the shape of the 3D model, model texture data describing the surface of the 3D model, model animation data describing the movement of the 3D model over time, etc., this description This is not specifically limited.

Usually, the parts that occupy a larger file size can be represented in the form of data external to the model to reduce the size of the main model file.

Therefore, the model main file usually occupies a small space, and the efficiency of compressing it is not high. When performing hierarchical compression on model files, you can mainly compress the external data of the model.

Specifically, when the model file is hierarchically compressed according to multiple preset definition levels, each definition level can correspond to the preset compression parameters, and the compression parameters can include specific parameters such as compression method, compression target size, compression rate, etc. , this manual does not specifically limit this.

Multiple model external data obtained through hierarchical compression can be stored in the file service on the server side respectively, and the storage address of the external model data is saved in the model main file.

In an illustrative embodiment shown in this description, a corresponding model main file can be generated for each definition level, and the model main file stores the storage where the compressed model external data of the corresponding definition level is located. address.

For example, when there are three definition levels of the original painting OD, high definition HD and standard definition SD, a model main file can be generated for these three definition levels respectively. The model main files corresponding to different definition levels are the same.

After the model external data corresponding to the three definition levels are stored in the file service of the server, the storage addresses of the model external data corresponding to the definition levels are stored in the model main files corresponding to the three definition levels. .

Through the above method, you can obtain three model main files that respectively store the storage addresses of the corresponding external data.

When the model main file corresponding to a certain definition level is loaded, the corresponding model external data can be obtained based on its saved storage address to complete the loading of the 3D model of this definition level.

In another illustrative embodiment shown in this description, the storage addresses of the compressed model external data corresponding to different definition levels can be stored in one model main file.

When the model main file is loaded, the storage address corresponding to the external model data that needs to be loaded can be determined according to the target definition level, and the corresponding model external data is obtained based on the storage address to complete the 3D model of the target definition level. of loading.

In this specification, the format of the model file corresponding to the 3D model is not limited. For example, the format of the model file can be fbx format, gltf format, obj format, x3d format, etc.

In an exemplary embodiment shown in this description, the format of the model file corresponding to the 3D model may be gltf format.

The Gltf (GL Transmission Format) format is an open standard format for transmitting and loading 3D models. It is lightweight, efficient, and open. It is one of the 3D model formats widely used on the Internet today.

Model files in Gltf format can be stored in separate storage formats as described above.

Please refer to Figure 3, which is a schematic structural diagram of a 3D model file provided by an exemplary embodiment.

Model files in Gltf format can include gltf files as model main files, and model geometry data and model texture data as model external data.

Among them, the model geometry data can be used to describe the model shape of the 3D model; and the model texture data can be used to describe the surface of the 3D model.

Model geometry data can usually be stored in the form of bin files, while model texture data can usually be stored in the form of png files.

Bin files and png files are stored in the corresponding file service on the server side, and their storage locations are represented in the gltf file in the form of URLs.

The three parts of Gltf file, bin file, and png file can be combined into a complete and usable model file in gltf format, which can be loaded on the user client.

The hierarchical compression of model files in gltf format can include hierarchical compression of model geometry data (bin files) and model texture data (png files).

The following discusses the hierarchical compression of model geometry data and model texture data respectively.

The model geometry data that describes the model shape of the 3D model mainly includes mesh data that describes the polygon mesh structure corresponding to the 3D model.

3D models implemented in computers usually use polygonal mesh structures to represent the surface of objects. The more polygons used, the more detailed the model and the larger the model file.

In gltf format files, the mesh data in the model geometry data usually adopts a triangular mesh structure, that is, the surface of the 3D model is composed of several triangles.

The mesh data describing the polygon mesh includes a series of coordinate data, including polygon vertex coordinates, normal coordinates, texture coordinates, etc. The coordinate data in Mesh data is usually represented by floating point data.

A method of compressing mesh data that can convert the coordinate data in the mesh data from floating point data to integer data. Integer data takes up less space than floating point data. In this way, mesh data can be compressed by reducing the coordinate accuracy in the polygon grid. This compression method can usually be achieved using KHR_mesh_quantization technology.

In addition to reducing the accuracy of the coordinates in the polygon grid in the mesh data, the mesh data can also be compressed by reducing the number of polygons in the polygon grid.

Usually, adjacent polygons with small angles between each other, such as less than a certain preset threshold, can be merged into larger polygons to reduce the number of polygons in the polygon network. Reducing the number of polygons will cause the 3D model to lose some surface details, but it can also effectively compress the size of the mesh data. This compression method can usually be achieved using mesh_quantization technology.

By reducing the accuracy of coordinate data and reducing the number of polygons, mesh data can be effectively compressed, thereby compressing model collection data.

Model map data can usually include color map (basic color map), normal map (normal map), orm map (material texture map), etc. Among them, the number of a certain type of texture may be 0, 1, or multiple.

Texture data is usually a png file. The compression technology of png files is relatively mature and common, and will not be explained in detail in this manual.

Specifically, one or more of the following methods can be used to compress texture files in png format:

Use pngquant for compression; pngquant is an image compression algorithm that mainly uses an improved version of the median cut quantization algorithm and K-means color correction, which can significantly reduce the file size and maintain full alpha transparency;

Convert images in png format to jpg format; the alpha transparency channel will be lost and the file size will be reduced;

Convert texture files in png format to ktx2 format; the file size can be reduced.

Depending on actual compression needs, you can also use common image compression methods such as converting texture files in png format to webp format and performing size compression on texture files in png format. This description does not specifically limit this.

In an illustrative embodiment shown in this description, the following compression strategy can be adopted:

The three definition levels of OD/HD/SD are still used, and OD level model files are not compressed;

HD level: perform pngquant 75% quality compression on png format texture files, and convert png format texture files to jpg format, compare png format texture files after pngquant 75% quality compression and converted jpg format texture files, Keep smaller files; use mesh_quantization technology to process mesh data;

SD level: Convert texture files in png format to ktx2 format; use mesh_quantization and triangle surface merging and optimization processing for mesh data. Among them, surface optimization is not performed when the bin file is less than 2MB. When the bin file is 2-4MB, the surface compression rate is set to 0.9 ;Set the surface compression rate to 0.8 when the bin file is 4-6MB, and set the surface compression rate to 0.6 when the bin file is larger than 6MB.

The process of hierarchical compression of model files will be described in detail below with reference to Figure 4.

As shown in Figure 4, Figure 4 schematically shows an interactive flow chart of a 3D model hierarchical compression method according to an embodiment of this specification.

Still taking the model file in gltf format as an example, the compression process of the model file will be explained.

The compression process of the 3D model model files is performed in advance on the server side. The server side can include a workspace that performs the hierarchical compression process, a compression tool that actually compresses the files, and a media service that saves the remote resource files as a file service.

The original model file in Gltf format is saved in the media service in the form of gltf file, bin file and png file.

The following is the detailed process of hierarchical compression in the form of interaction between workspace, compression tool and media service:

Step 401: The workspace requests the original model file from the media service;

Step 402: The media service accepts the request and sends the gltf file, bin file and png file to the job;

Step 403: Determine multiple definition levels, and configure compression parameters corresponding to each definition level;

For each target clarity level, the following steps 404 - 412 are performed:

Step 404: Read the compression configuration corresponding to the target definition level;

Step 405: Pass the compression parameters corresponding to the model geometry data to the compression tool;

Step 406: The compression tool compresses the bin file according to the incoming compression parameters, and returns the compressed bin file to the workspace;

Step 407: Pass the compression parameters corresponding to the model texture data into the compression tool;

Step 408: The compression tool compresses the png file according to the incoming compression parameters, and returns the compressed png file to the workspace;

Step 409: Upload the compressed bin file and png file to the media service;

Step 410: The media service sends the resource remote addresses of the bin file and png file to the workspace;

Step 411: Update the URLs corresponding to the bin file and png file in the gltf file;

Step 412: Upload the updated gltf to the media service.

Step 413: Delete the workspace cache file.

In an exemplary embodiment shown in this specification, a 3D model hierarchical compression method is also provided.

Please refer to Figure 5. Figure 5 is a flow chart of a 3D model hierarchical compression method according to an embodiment of this specification. This method is applied to a processing device, which may be a server 11 or a computer 12-14 as shown in Figure 1.

The method may include the following steps:

Step 502: Obtain the original model file corresponding to the 3D model, and perform hierarchical compression on the original model file according to multiple preset definition levels to obtain model files corresponding to the multiple definition levels.

In an illustrative embodiment shown in this description, the model file includes a model main file and model external data; wherein, the model external data is stored in the file service of the server, and the model main file saves The storage address corresponding to the external data of the model;

Perform hierarchical compression on the original model file according to multiple preset definition levels to obtain model files corresponding to the multiple definition levels, including:

Perform hierarchical compression on the external data of the model according to multiple preset definition levels, and store them in the file service on the server side respectively;

The storage addresses of the compressed model external data corresponding to each definition level are respectively saved into the model main file corresponding to the 3D model, thereby obtaining model files corresponding to the plurality of definition levels respectively.

In an illustrative embodiment shown in this description, the 3D model includes a 3D model in gltf format;

The model main file includes a gltf model file; the model external data includes model geometry data used to describe the shape of the model, and/or model texture data used to describe the model surface;

The step of performing hierarchical compression on the external data of the model according to multiple preset definition levels includes:

The model geometric data and/or the model texture data are compressed hierarchically according to a plurality of preset definition levels.

In an illustrative embodiment shown in this description, the model geometry data includes mesh data used to describe the polygon mesh structure corresponding to the 3D model.

In an illustrative embodiment shown in this description, compression of the model geometry data includes:

The coordinate data contained in the mesh data is converted from floating point data to integer data to achieve compression.

In an illustrative embodiment shown in this description, compression of the model geometry data includes:

Merge at least part of the adjacent polygonal networks in the polygonal meshes contained in the mesh data that have an angle smaller than the preset value to achieve compression.

In an exemplary embodiment shown in this description, the model texture data includes a texture file in png format;

Compression of the model texture data includes one or more of the following:

Perform pngquant compression on the texture file in png format to achieve compression;

Convert the texture file in png format to jpg format to achieve compression;

Convert the texture file in png format to ktx2 format to achieve compression.

Step 504: In response to the file acquisition request for the 3D model sent by the user client, determine the target model file corresponding to the target definition level; wherein the target definition level is corresponding to the running environment of the user client. clarity level.

In an exemplary embodiment shown in this description, the file acquisition request includes running environment parameters corresponding to the running environment of the user client;

Determining the target model file corresponding to the target clarity level includes:

The target model definition level corresponding to the user client is determined based on the running environment parameters included in the file acquisition request, and the target model file corresponding to the target definition level is determined.

The file acquisition request includes a level identifier of a target clarity level determined by the user client and corresponding to the running environment of the user client;

In an exemplary embodiment shown in this description, determining the target model file corresponding to the target clarity level includes:

The target model definition level corresponding to the user client is determined based on the level identifier included in the file acquisition request, and the target model file corresponding to the target definition level is determined.

The above target clarity level can be determined by the user client or by the server corresponding to the user client.

When the target clarity level is determined by the client, the file acquisition request sent by the user client to the server contains the level identifier corresponding to the target clarity level determined by the user client;

When the target clarity level is determined by the server, the file acquisition request sent by the user client to the server contains the operating environment parameters corresponding to the operating environment of the user client used to determine the target clarity level;

After the server receives the above running environment parameters, it can determine the target clarity based on the running environment parameters.

In an exemplary embodiment shown in this description, the operating environment parameters include:

The network performance parameters of the user client; and/or,

Device performance parameters of the user client.

Step 506: Return the target model file to the user client, so that the user client loads the obtained target model file and displays the 3D model to the user.

For the specific compression method of the 3D model, please refer to the above embodiment, and will not be described in detail here.

In the illustrative embodiment of this specification, a 3D model hierarchical display device is also provided. Please refer to FIG. 6 , which is a block diagram of a 3D model hierarchical display device according to an embodiment of this specification.

The server corresponding to the user client maintains the original model file corresponding to the 3D model according to multiple preset definition levels, and the models corresponding to the multiple definition levels are obtained after hierarchical compression. document;

The device may include the following components:

Determining unit 610, configured to determine a target clarity level corresponding to the running environment of the user client in response to a model display request for the 3D model;

The obtaining unit 620 is used to obtain the target model file corresponding to the target definition level from the server;

The loading unit 630 is used to load the obtained target model file to display the 3D model to the user.

Optionally, the operating environment of the user client includes network performance parameters of the user client;

The determining unit 610 is specifically used for:

Obtain the operating environment of the user client;

Determine the target model clarity level corresponding to the operating environment.

Optionally, the running environment of the user client also includes device performance parameters of the user client.

Optionally, the model definition level includes: original painting level;

Wherein, the model file corresponding to the original painting level is the original model file that has not been compressed.

Optionally, the device also includes:

Overload unit 640 for:

Determine whether the number of failed loadings of the model file reaches a preset threshold;

If the number of failed loadings of the model file reaches a preset threshold, re-determine the target clarity level as the original painting level, and obtain the model file corresponding to the original painting level;

Load the obtained model file corresponding to the original painting level to display the 3D model to be displayed to the user.

Optionally, the model file includes a model main file and model external data; wherein the model external data is stored in the file service of the server, and the model main file stores the storage address corresponding to the model external data;

The original model file corresponding to the 3D model is hierarchically compressed according to multiple preset definition levels, and the model files corresponding to the multiple definition levels obtained include:

From the original model main file corresponding to the 3D model, multiple model main files corresponding to multiple preset definition levels are respectively generated; wherein, in the model main file corresponding to each definition level, the corresponding main model files are respectively saved. The storage address of the compressed model external data corresponding to the definition level; the compressed model external data is hierarchically compressed by the original model external data corresponding to the 3D model based on the preset compression parameters corresponding to the definition level. get later.

Optionally, the acquisition unit 620 is specifically used for:

Obtain the model main file corresponding to the target clarity level from the server;

The loading unit 630 is specifically used for:

Based on the obtained storage address saved in the model main file, obtain the model external file corresponding to the model main file from the server;

Load the model main file and the model external file to display the 3D model to be displayed to the user.

Optionally, the 3D model includes a 3D model in gltf format;

The model main file includes a gltf model file; the model external data includes model geometry data used to describe the shape of the model, and model texture data used to describe the model surface;

The compressed model external data includes compressed model geometry data and compressed model map data.

Optionally, the model geometry data includes mesh data used to describe the polygon mesh structure corresponding to the 3D model.

Optional, the compressed model geometry data includes:

The coordinate data contained in the mesh data in the model geometric data is converted from being described using floating point data to being described using integer data to achieve compressed model geometric data.

Optionally, compressing the model geometric data includes:

Merge at least part of the adjacent polygonal networks in the polygon meshes contained in the mesh data in the model geometry data and whose included angles are smaller than a preset value to achieve compressed model geometry data.

Optionally, the model texture data includes texture files in png format;

The compressed model map data includes one or more of the following:

Perform pngquant compression on the texture file in png format to achieve compressed model texture data;

Convert the texture file in png format to jpg format to achieve compressed model texture data;

Convert the texture file in png format to ktx2 format to achieve compressed model texture data.

In the illustrative embodiment of this specification, a 3D model hierarchical compression device is also provided. Please refer to FIG. 7 , which is a block diagram of a 3D model hierarchical compression device according to an embodiment of this specification.

The device may include the following components:

The compression unit 710 is used to obtain the original model file corresponding to the 3D model, and perform hierarchical compression on the original model file according to multiple preset definition levels to obtain model files corresponding to the multiple definition levels;

The selection unit 720 is configured to respond to the file acquisition request for the 3D model sent by the user client, and determine the target model file corresponding to the target definition level; wherein the target definition level is the same as the target definition level of the user client. The clarity level corresponding to the operating environment;

The return unit 730 is used to return the target model file to the user client, so that the user client loads the obtained target model file and displays the 3D model to the user.

Optionally, the file acquisition request includes running environment parameters corresponding to the running environment of the user client;

The selection unit 720 is specifically used for:

The target model definition level corresponding to the user client is determined based on the running environment parameters included in the file acquisition request, and the target model file corresponding to the target definition level is determined.

Optionally, the file acquisition request includes a level identifier of the target clarity level determined by the user client and corresponding to the running environment of the user client;

The selection unit 720 is specifically used for:

The target model definition level corresponding to the user client is determined based on the level identifier included in the file acquisition request, and the target model file corresponding to the target definition level is determined.

Optionally, the environment operating parameters include:

The network performance parameters of the user client; and/or,

Device performance parameters of the user client.

Optionally, the model file includes a model main file and model external data; wherein the model external data is stored in the file service of the server, and the model main file stores the storage address corresponding to the model external data;

The compression unit 710 is specifically used for:

Perform hierarchical compression on the external data of the model according to multiple preset definition levels, and store them in the file service on the server side respectively;

The storage addresses of the compressed model external data corresponding to each definition level are respectively saved into the model main file corresponding to the 3D model, thereby obtaining model files corresponding to the plurality of definition levels respectively.

Optionally, the 3D model includes a 3D model in gltf format;

The model main file includes a gltf model file; the model external data includes model geometry data used to describe the shape of the model, and/or model texture data used to describe the model surface;

The compression unit 710 is specifically used for:

The model geometric data and/or the model texture data are compressed hierarchically according to a plurality of preset definition levels.

Optionally, the model geometry data includes mesh data used to describe the polygon mesh structure corresponding to the 3D model.

Optionally, the compression unit 710 is specifically used for:

The coordinate data contained in the mesh data is converted from floating point data to integer data to achieve compression.

Optionally, the compression unit 710 is specifically used for:

Merge at least part of the polygonal networks contained in the mesh data that are adjacent and have an included angle smaller than a preset value to achieve compression.

Optionally, the model texture data includes texture files in png format;

The compression unit 710 is specifically used for one or more of the following:

Perform pngquant compression on the texture file in png format to achieve compression;

Convert the texture file in png format to jpg format to achieve compression;

Convert the texture file in png format to ktx2 format to achieve compression.

For details on the implementation process of the functions and effects of each unit in the above device, please refer to the implementation process of the corresponding steps in the above method, and will not be described again here.

As for the device embodiment, since it basically corresponds to the method embodiment, please refer to the partial description of the method embodiment for relevant details. The device embodiments described above are only illustrative. The units described as separate components may or may not be physically separated. The components shown as units may or may not be physical units, that is, they may be located in One location, or it can be distributed to at least one network unit. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution in this specification. Persons of ordinary skill in the art can understand and implement the method without any creative effort.

In the exemplary embodiments of this specification, embodiments of a device and a terminal to which it is applied are also provided.

The embodiments of the apparatus in this specification can be applied to computer equipment, such as servers or terminal equipment. The device embodiments may be implemented by software, or may be implemented by hardware or a combination of software and hardware. Taking software implementation as an example, as a device in a logical sense, it is formed by reading the corresponding computer program instructions in the non-volatile memory into the memory and running it through its processor. From a hardware level, as shown in Figure 8, Figure 8 is a hardware structure diagram of a computer device 80 in which a device according to an embodiment of this specification is located. In addition to the processor 810, memory 830, and network interface 820 shown in Figure 8 , and non-volatile memory 840, the server or electronic equipment where the device in the embodiment is located may also include other hardware based on the actual functions of the computer equipment, which will not be described again.

In an exemplary embodiment of this specification, a computer-readable storage medium is also provided, on which a program product capable of implementing the above method of this specification is stored. In some possible embodiments, various aspects of this specification can also be implemented in the form of a program product, which includes program code. When the program product is run on a terminal device, the program code is used to cause the The terminal device performs the steps according to various exemplary embodiments of this specification described in the above-mentioned "Exemplary Method" section of this specification.

The program product used to implement the above method according to the embodiment of the present specification can adopt a portable compact disk read-only memory (CD-ROM) and include program code, and can be run on a terminal device, such as a personal computer. However, the program product of this specification is not limited thereto. In this document, a readable storage medium may be any tangible medium containing or storing a program that may be used by or in combination with an instruction execution system, apparatus or device.

The program product may take the form of one or any combination of at least one readable medium. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device or device, or any combination thereof. More specific examples (non-exhaustive list) of readable storage media include: electrical connection with one or at least one conductor, portable disk, hard disk, random access memory (RAM), read only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination of the above.

A computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave carrying readable program code therein. Such propagated data signals may take many forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the above. A readable signal medium may also be any readable medium other than a readable storage medium that can send, propagate, or transport the program for use by or in connection with an instruction execution system, apparatus, or device.

Program code embodied on a readable medium may be transmitted using any suitable medium, including but not limited to wireless, wireline, optical cable, RF, etc., or any suitable combination of the foregoing.

Program code for performing the operations of this specification may be written in any combination of one or more programming languages, including object-oriented programming languages such as Java, C++, etc., as well as conventional procedures programming language - such as "C" or a similar programming language. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device and partly on a remote computing device, or entirely on the remote computing device or server execute on. In situations involving remote computing devices, the remote computing device may be connected to the user computing device through any kind of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computing device, such as provided by an Internet service. (business comes via Internet connection).

The user information (including but not limited to user equipment information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all authorized by the user or Information and data that have been fully authorized by all parties, and the collection, use and processing of relevant data need to comply with relevant laws, regulations and standards of relevant countries and regions, and provide corresponding operation portals for users to choose to authorize or refuse.

Although this specification contains many specific implementation details, these should not be construed to limit the scope of any invention or what is claimed, but rather serve primarily to describe features of specific embodiments of particular inventions. Certain features described in this specification in the context of at least one embodiment can also be combined in a single embodiment. On the other hand, various features that are described in a single embodiment can also be implemented in at least one embodiment separately or in any suitable subcombination. Furthermore, while features may function in certain combinations as described above and may even be originally claimed as such, one or at least one feature from a claimed combination may in some cases be removed from that combination and as claimed A protected combination can point to a subcombination or a variant of a subcombination.

Similarly, although operations are depicted in a specific order in the drawings, this should not be construed as requiring that the operations be performed in the specific order shown, or sequentially, or that all illustrated operations be performed to achieve desired results. result. In some cases, multitasking and parallel processing may be advantageous. Furthermore, the separation of various system units and components in the above embodiments should not be construed as requiring such separation in all embodiments, and it should be understood that the described program components and systems may generally be integrated together in a single software product , or packaged into at least one software product.

Thus, specific embodiments of the subject matter have been described. Other embodiments are within the scope of the appended claims. In some cases, the actions recited in the claims can be performed in a different order and still achieve desirable results. Furthermore, the processes depicted in the figures do not necessarily require the specific order shown, or sequential order, to achieve desirable results. In some implementations, multitasking and parallel processing may be advantageous.

The above are only preferred embodiments of this specification and are not intended to limit this specification. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of this specification shall be included in this specification. within the scope of protection.

Claims (21)

1. A3D model grading display method is applied to a user client; the server corresponding to the user client maintains model files corresponding to the definition levels respectively, wherein the model files are obtained by carrying out hierarchical compression on original model files corresponding to the 3D model according to the preset definition levels; the method comprises the following steps:

determining a target definition level corresponding to an operating environment of the user client in response to a model presentation request for the 3D model;

acquiring a target model file corresponding to the target definition level from the server;

and loading the obtained target model file to display the 3D model to a user.

2. The method of claim 1, wherein,

the determining a target definition level corresponding to the running environment of the user client comprises:

acquiring operation environment parameters corresponding to the operation environment of the user client;

and determining a target model definition grade corresponding to the user client based on the acquired running environment parameters.

3. The method of claim 2, wherein the environmental operating parameters include:

Network performance parameters of the user client; and/or the number of the groups of groups,

and the equipment performance parameters of the user client.

4. The method of claim 1, wherein,

the model definition level includes: original painting grade; the model files corresponding to the original painting grade are the original model files which are not compressed;

the method further comprises the steps of:

determining whether the number of times of loading failure of the model file reaches a preset threshold value or not;

if the number of times of the model file loading failure reaches a preset threshold, re-determining a target definition level corresponding to the running environment of the user client as an original picture level, and acquiring a model file corresponding to the original picture level;

and loading the obtained model file corresponding to the original painting grade so as to display the 3D model for a user.

5. The method of claim 1, wherein,

the model file comprises a model main body file and model external data; the model external data is stored in a file service of a server, and a storage address corresponding to the model external data is stored in the model main body file.

6. The method of claim 5, wherein,

The obtaining, from the server, the target model file corresponding to the target definition level includes:

acquiring a target model main body file corresponding to the target definition level from the server;

loading the obtained model file to display the 3D model to a user, including:

reading a storage address stored in the model main body file, and acquiring a model external file corresponding to the model main body file from the server based on the storage address;

and loading the model main body file and the model external file to show the 3D model to a user.

7. The method of claim 5, wherein,

the 3D model comprises a gltf format 3D model;

the model body file comprises a gltf model file; the model external data includes model geometry data for describing a shape of the model and/or model map data for describing a surface of the model; the compressed model external data comprises compressed model geometric data and/or compressed model map data.

8. A3D model hierarchical compression method is applied to a server; the method comprises the following steps:

acquiring an original model file corresponding to a 3D model, and performing hierarchical compression on the original model file according to a plurality of preset definition grades to obtain model files respectively corresponding to the definition grades;

Determining a target model file corresponding to a target definition level in response to a file acquisition request for the 3D model sent by a user client; the target definition level is a definition level corresponding to the running environment of the user client;

and returning the target model file to the user client so that the user client loads the obtained target model file and displays the 3D model to a user.

9. The method of claim 8, wherein the file acquisition request contains an operating environment parameter corresponding to an operating environment of the user client;

the determining the target model file corresponding to the target definition level comprises the following steps:

and determining a target model definition grade corresponding to the user client based on the running environment parameters contained in the file acquisition request, and determining a target model file corresponding to the target definition grade.

10. The method of claim 8, wherein the file acquisition request includes a level identification of a target level of sharpness corresponding to a running environment of the user client determined by the user client;

The determining the target model file corresponding to the target definition level comprises the following steps:

and determining a target model definition grade corresponding to the user client based on the grade identification contained in the file acquisition request, and determining a target model file corresponding to the target definition grade.

11. The method of claim 9, wherein the environmental operating parameters include:

network performance parameters of the user client; and/or the number of the groups of groups,

and the equipment performance parameters of the user client.

12. The method of claim 8, wherein,

the model file comprises a model main body file and model external data; the model external data are stored in file service of a server, and storage addresses corresponding to the model external data are stored in the model main body file;

performing hierarchical compression on the original model file according to a plurality of preset definition levels to obtain model files respectively corresponding to the definition levels, wherein the method comprises the following steps:

respectively carrying out hierarchical compression on the external data of the model according to a plurality of preset definition levels, and respectively storing the external data in file services of a server;

And respectively storing the storage addresses of the compressed model external data corresponding to the definition grades into the model main body files corresponding to the 3D model to obtain model files corresponding to the definition grades.

13. The method of claim 12, wherein,

the 3D model comprises a gltf format 3D model;

the model body file comprises a gltf model file; the model external data includes model geometry data for describing a shape of the model and/or model map data for describing a surface of the model;

the step of respectively carrying out step compression on the external data of the model according to a plurality of preset definition levels comprises the following steps:

and respectively carrying out hierarchical compression on the model geometric data and/or the model map data according to a plurality of preset definition levels.

14. The method of claim 13, wherein,

the model geometry data comprise mesh data for describing a polygonal mesh structure corresponding to the 3D model.

15. The method of claim 14, wherein,

compressing the model geometry data, comprising:

and converting the coordinate data contained in the mesh data from the description using floating point type data to the description using integer type data so as to realize compression.

16. The method of claim 14, wherein,

compressing the model geometry data, comprising:

and merging at least partial polygonal networks which are adjacent in the polygonal grids and have included angles smaller than a preset value in the mesh data so as to realize compression.

17. The method of claim 13, wherein,

the model mapping data comprises a mapping file in png format;

compressing the model map data, including one or more of:

carrying out pngquant compression on the map file in the png format to realize compression;

converting the mapping file in the png format into a jpg format so as to realize compression;

and converting the png-format map file into ktx2 format to realize compression.

18. The 3D model grading display device is applied to a user client; the server corresponding to the user client maintains the original model files corresponding to the 3D model according to a plurality of preset definition levels, and model files corresponding to the definition levels are obtained after hierarchical compression; the device comprises:

a determining unit, configured to determine a target definition level corresponding to an operating environment of the user client in response to a model presentation request for the 3D model;

The acquisition unit is used for acquiring a target model file corresponding to the target definition level from the server;

and the loading unit is used for loading the obtained target model file so as to display the 3D model to a user.

19. The 3D model hierarchical compression device is applied to a server; the device comprises:

the compression unit is used for acquiring an original model file corresponding to the 3D model, and carrying out hierarchical compression on the original model file according to a plurality of preset definition grades to obtain model files respectively corresponding to the definition grades;

the selection unit is used for responding to a file acquisition request for the 3D model sent by the user client and determining a target model file corresponding to the target definition level; the target definition level is a definition level corresponding to the running environment of the user client;

and the returning unit is used for returning the target model file to the user client so that the user client loads the obtained target model file and displays the 3D model to a user.

20. A storage medium having stored thereon a computer program which, when executed, performs the steps of the method according to any of claims 1-17.

21. A computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, wherein the processor when executing the program implements the method of: wherein the processor, when executing the program, implements the method of any one of claims 1-17.