Point cloud data processing method and device based on browser storage
By automatically acquiring and storing compressed packages of point cloud data in a browser environment, the problems of cumbersome operations and security risks in point cloud data processing are solved, and efficient and secure access to point cloud data is achieved.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- BEIJING XIAOYU INTELLISYS CO LTD
- Filing Date
- 2026-03-18
- Publication Date
- 2026-07-07
Smart Images
Figure CN121880288B_ABST
Abstract
Description
Technical Field
[0001] This disclosure relates to the field of data processing technology, and in particular to a method and apparatus for processing point cloud data based on browser storage. Background Technology
[0002] In related technologies, the demand for online loading and interaction of large-scale point cloud data is increasing in web-based 3D visualization applications. Currently, the traditional solution requires users to download the entire compressed point cloud data package to their local machine, manually decompress it, and then re-upload it to the browser for parsing and rendering via a webpage file selector. This process is fragmented, cumbersome, and results in repeated downloads of the same data, wasting network bandwidth and increasing user waiting time. Furthermore, the decompressed files are scattered across the local disk, making them difficult to manage and posing a security risk of leaving sensitive data behind. Summary of the Invention
[0003] To overcome the problems existing in related technologies, this disclosure provides a method and apparatus for processing point cloud data based on browser storage.
[0004] According to a first aspect of the present disclosure, a point cloud data processing method based on browser storage is provided, comprising:
[0005] In response to a user's request to access a point cloud file in the browser, if the point cloud file does not exist in the browser's index database, a compressed package of the point cloud file is obtained; the point cloud file includes point cloud data.
[0006] The compressed package is decompressed in a browser environment to obtain a point cloud file;
[0007] Store the point cloud file in the browser's source private file system and obtain the file handle corresponding to the point cloud file;
[0008] The index record including the file handle is stored in the index database;
[0009] If an index record for the point cloud file exists in the index database, the point cloud file is retrieved from the source private file system using the file handle in the index record.
[0010] According to a second aspect of the present disclosure, a point cloud data processing apparatus based on browser storage is provided, characterized in that it includes:
[0011] The first acquisition unit is configured to respond to a user's access request for a point cloud file input into the browser, and if no index record of the point cloud file exists in the browser's index database, acquire a compressed package of the point cloud file; the point cloud file includes point cloud data.
[0012] The decompression unit is used to decompress the compressed package in a browser environment to obtain a point cloud file;
[0013] The first storage unit is used to store the point cloud file in the browser's source private file system and obtain the file handle corresponding to the point cloud file.
[0014] The second storage unit is used to store index records, including the file handle, into the index database;
[0015] The second acquisition unit is used to acquire the point cloud file from the source private file system by using the file handle in the index record when the index record of the point cloud file exists in the index database.
[0016] According to a third aspect of the present disclosure, an electronic device includes: a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the computer program, implements the method as described in any one of the first aspects.
[0017] According to a fourth aspect of the present disclosure, a computer-readable storage medium is provided having a computer program stored thereon, which, when executed by a processor, implements the method as described in any one of the first aspects.
[0018] According to a fifth aspect of the present disclosure, a computer program product is provided, including a computer program that, when executed by a processor, implements the method as described in any one of the first aspects.
[0019] The technical solutions provided by the embodiments of this disclosure can include the following beneficial effects: by responding to access requests for point cloud files, the system intelligently determines whether a corresponding index record already exists in the browser's index database. If it does not exist, it automatically executes a complete process of obtaining a compressed package, decompressing it in the browser environment to obtain the point cloud file, storing it in the browser's source private file system, and generating an index record containing the obtained file handle and storing it in the index database. If the index record already exists, the corresponding point cloud file can be quickly obtained from the source private file system directly using the file handle in the record. This mechanism realizes fully automatic processing of point cloud data from remote compressed packages to browser-localized and indexed storage, and provides a fast reading path for subsequent access without repeated downloading and decompression, thereby significantly improving access efficiency and user experience while ensuring data persistence and security.
[0020] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description
[0021] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with the invention and, together with the description, serve to explain the principles of the invention.
[0022] Figure 1 This is a flowchart illustrating a point cloud data processing method based on browser storage, according to an exemplary embodiment.
[0023] Figure 2 This is a block diagram illustrating a browser-based point cloud data processing apparatus according to an exemplary embodiment.
[0024] Figure 3 This is a block diagram illustrating an apparatus for a browser-based point cloud data processing method according to an exemplary embodiment.
[0025] Figure Labels
[0026] 201-First acquisition unit; 202-Decompression unit; 203-First storage unit; 204-Second storage unit; 205-Second acquisition unit; 300-Device; 302-Processing component; 304-Memory; 306-Power component; 308-Multimedia component; 310-Audio component; 312-I / O interface; 316-Communication component; 320-Processor. Detailed Implementation
[0027] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numerals in different drawings denote the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present invention. Rather, they are merely examples of apparatuses and methods consistent with some aspects of the invention as detailed in the appended claims.
[0028] The terminology used in this disclosure is for the purpose of describing particular embodiments only and is not intended to be limiting of the present disclosure. The singular forms “a” and “the” as used in this disclosure and the appended claims are also intended to include the plural forms, unless the context clearly indicates otherwise.
[0029] It should be understood that although the terms first, second, third, etc., may be used to describe various information in embodiments of this disclosure, such information should not be limited to these terms. These terms are only used to distinguish information of the same type from one another. For example, first information may also be referred to as second information without departing from the scope of embodiments of this disclosure, and similarly, second information may also be referred to as first information. Depending on the context, the words “if” and “suppose” as used herein may be interpreted as “when”, “when”, or “in response to a determination”.
[0030] Furthermore, various forms of processes shown in the embodiments of this disclosure can be used to reorder, add, or delete steps. For example, the steps described in this application can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution disclosed in this disclosure can be achieved, and no limitation is imposed herein.
[0031] It should be noted that the collection, storage, use, processing, transmission, provision, and disclosure of user personal information involved in the technical solution disclosed herein all comply with the provisions of relevant laws and regulations and do not violate public order and good morals.
[0032] Figure 1 This is a flowchart illustrating a point cloud data processing method based on browser storage, according to an exemplary embodiment, such as... Figure 1 As shown, it should be noted that the browser-stored point cloud data processing method of this disclosure is applied to a browser-stored point cloud data processing device. Figure 1 As shown, the method may include the following steps:
[0033] Step 101: In response to the user's request to access the point cloud file in the browser, if there is no index record of the point cloud file in the browser's index database, obtain the compressed package of the point cloud file.
[0034] The point cloud file includes point cloud data.
[0035] It should be noted that a point cloud file can be a type of computer file used to store a set of three-dimensional spatial points. Internally, it records the spatial coordinates (X, Y, Z) and additional attributes (such as color, intensity, echo count, etc.) of a massive number of discrete points in a structured format (such as the modular container and playback format MCAP, and the LiDAR data exchange standard format LAS). It is generated by high-precision scanning and sampling of real-world scenes or object surfaces. Such files are usually large in data volume and complex in structure. They need to be decoded by a dedicated parser before they can be visualized as interactive graphics by a 3D rendering engine. In traditional web processing workflows, they face challenges such as slow download speed, time-consuming parsing, interactive lag, and management difficulties.
[0036] In one embodiment, an index record can be a structured data entry stored in a browser index database (such as Indexed DB). Its core content can include a file handle pointing to a specific point cloud file in the browser's Origin Private File System (OPFS), as well as metadata (such as task identifier, storage timestamp, etc.) used to identify and retrieve the file. By associating easily queryable identification information with the underlying file access handle, the index record can quickly locate and obtain the corresponding file handle based on index conditions such as task ID or point cloud file identification information. This skips the repeated download and decompression process and directly reads the point cloud file from local storage, achieving efficient and accurate file retrieval and access acceleration.
[0037] In one embodiment, the index database is a structured local database running in the browser environment, used to store index records with metadata such as task identifiers as retrieval keys. By establishing a mapping relationship between metadata fields and file handles, the database builds a lightweight index directory that can reside in the browser sandbox for a long time, thereby enabling the corresponding record to be queried in milliseconds based on the identification information in the access request, and then extracting the point cloud file handle stored in the browser's source private file system.
[0038] In this embodiment of the disclosure, when a user initiates a request to view or use a specific point cloud file through a browser interface, the index database running locally on the browser can be queried based on the identification information (such as task ID or point cloud file identification information) carried in the access request. If the query result shows that there is no index record corresponding to the point cloud file in the database, it is determined that this is the first access, and the compressed package (which can be in .tar.gz format) corresponding to the point cloud file is obtained from the remote server, thereby preparing the data source for the subsequent local decompression, storage and indexing process.
[0039] Step 102: Decompress the compressed package in a browser environment to obtain the point cloud file.
[0040] In this embodiment, the browser environment refers to an application runtime sandbox and execution platform built on Web standards and provided by a Web browser. It may include a JavaScript scripting language engine, a rendering engine, a network module, and a series of browser application programming interfaces (APIs). In this disclosure, this environment enables all data processing steps—including downloading point cloud compressed packages, streaming decompression in memory, parsing and filtering file content, and even persistent storage in the source private file system OPFS—to be completed directly within the user's local browser process, without relying on local operating system tools or additional software. This achieves deep integration of data processing logic with Web applications.
[0041] In some embodiments of this disclosure, step 102 may specifically include the following steps:
[0042] Obtain the binary data of the compressed file;
[0043] The binary data is decompressed using a decompression function to obtain the archived data;
[0044] The archived data is parsed according to the preset format specifications to extract point cloud files.
[0045] In this embodiment, after obtaining the compressed package, a JavaScript-based decompression library is called within the browser runtime to decompress the binary data stream of the compressed package, restore the archive file data, parse the file header information and data blocks according to archive format specifications such as TAR, and extract the embedded point cloud files and their original directory structure item by item. The entire process is completed entirely in the browser's memory and computing resources, without relying on the local operating system or external decompression tools. This achieves a seamless and secure online conversion of point cloud data from a compressed state to a processable state, preparing for the subsequent persistent storage of point cloud files to the browser's private file system.
[0046] In one embodiment, archived data can refer to the original binary data collection organized according to a specific packaging format (such as the magnetic tape archive format TAR) obtained after decompressing a compressed package using a first-layer general compression algorithm. Internally, it follows a clear format specification (such as the POSIX ustar archive format for portable operating system interfaces), continuously concatenating and encapsulating multiple independent files, directory hierarchies, and related file metadata (such as filenames, sizes, and permissions) into a single linear data stream. In step 102 of this disclosure, the archived data, as intermediate data after decompression, is further parsed to reconstruct the original point cloud file and its complete directory tree.
[0047] In one embodiment, a TAR archive parser can be configured that strictly adheres to the POSIX ustar format specification, parsing and extracting content from TAR archive data block by block in 512-byte units. Its workflow includes: first, reading the 512-byte header of each entry, extracting the filename, parsing the file size stored in octal encoding, and identifying the entry type (regular file or directory); then, calculating the precise location of the data block based on the file size and extracting the original file content; for directory entries and padding blocks required by the archive format, the parser automatically identifies and skips them. This allows for autonomous and precise deconstruction of TAR archives in a pure browser environment, without relying on external libraries or local operating system capabilities, laying the foundation for the independent extraction and storage of subsequent point cloud files.
[0048] In some embodiments of this disclosure, after step 102, the method may further include: filtering the point cloud file based on preset system file feature rules to exclude metadata files automatically generated by the operating system.
[0049] In this embodiment of the disclosure, the decompressed file list can be quickly scanned and filtered according to a set of preset feature rules for common operating system hidden metadata files (e.g., matching filenames starting with "." and specific suffixes). This actively identifies and excludes system files that are automatically generated by the operating system or compression tools and are unrelated to the point cloud data content. This ensures that only the valid point cloud files that the user truly needs are retained in the subsequent storage and indexing process, avoiding irrelevant data from occupying the browser's local storage space and interfering with the file management logic, thereby improving storage purity and processing efficiency.
[0050] As an example of a possible implementation, a predefined set of regular expression rules is used to automatically scan and match the list of files to be processed after decompression. This aims to accurately identify and exclude system files and metadata files automatically generated by the operating system or compression tools that are unrelated to the point cloud business logic. These file characteristics cover operating system prefix files, directory service storage files, Windows system thumbnail database files, desktop configuration files, and compressed metadata directories commonly found in cross-platform compressed packages.
[0051] Step 103: Store the point cloud file in the browser's source private file system and obtain the file handle corresponding to the point cloud file.
[0052] In this embodiment of the disclosure, the corresponding directory hierarchy can be recursively created in the browser's source private file system (OPFS) based on the original path structure of the decompressed point cloud file, and a file can be created and binary content written at the target location, thereby persistently storing the file in the exclusive sandbox storage space allocated by the browser for the current webpage origin; at the same time, the file handle of the stored file can be obtained synchronously through the OPFS API.
[0053] In one embodiment, a file handle can be a persistent reference object that points to a specific file in OPFS and has direct read and write permissions, providing technical credentials for subsequent indexing and enabling fast file access without repeated path resolution.
[0054] In some embodiments of this disclosure, step 103 may specifically include the following steps:
[0055] Obtain the original path information of the point cloud file, and recursively create the directory structure corresponding to the original path information in the source private file system;
[0056] In the created directory structure, create a storage file with the same name as the point cloud file, and write the binary data from the point cloud file into the storage file.
[0057] In this embodiment, the complete original path information carried by the decompressed point cloud file is parsed out. The OPFS API is called layer by layer from the root directory through a recursive algorithm to create subdirectories at each level of the path in turn, until the directory tree structure completely consistent with the original compressed package is completely reproduced in the source private file system. This ensures that the point cloud file can be stored in a logical location that completely corresponds to the source, laying a structural foundation for subsequent path-based fast retrieval and user-intuitive file management.
[0058] In this embodiment, under the reconstructed corresponding directory path, a new file with the same name as the original point cloud file (i.e., the aforementioned storage file) is created using the OPFS API, and its file handle is obtained. A writable stream is opened using this handle, and the original binary data blocks of the decompressed point cloud file are directly written into the stream. After writing is completed, the stream is properly closed to ensure that all data is synchronized to disk-level storage. This not only achieves secure and persistent storage of point cloud content in the browser sandbox, but also enables subsequent access to read the complete data directly and efficiently using the same file handle, without the need for decompression or network transmission again.
[0059] Step 104: Store the index record, including the file handle, into the index database.
[0060] In some embodiments of this disclosure, step 104 may specifically include the following steps:
[0061] Index records are generated based on file handles and the metadata associated with the file handles; the metadata includes the identification information and storage timestamp of the point cloud file;
[0062] Store index records in the index database.
[0063] In this embodiment of the disclosure, the file handle obtained in step 103 and related metadata (which may include a task identifier that uniquely identifies the point cloud file and a timestamp of the current storage operation) are encapsulated to generate a structured index record. This index record is then persistently stored in an index database (such as Indexed DB) running locally on the browser through standard database operations. This establishes a file location mapping directory that can be stored in the browser for a long time and supports efficient querying through metadata fields such as task ID. This provides a fast file location capability for any subsequent access request for the same file without the need for repeated downloading and decompression.
[0064] Step 105: If an index record for the point cloud file exists in the index database, retrieve the point cloud file from the source private file system using the file handle in the index record.
[0065] In this embodiment, when an index record for the corresponding point cloud file is detected in the index database, the efficient reading process is directly initiated. This involves querying and locating the index record based on the identifier information in the access request, then extracting the persistently stored file handle from the record. Based on the file handle, without any network requests or decompression operations, the corresponding point cloud file binary data is directly read from the browser's source private file system (OPFS). This step completely bypasses the traditional "download-decompression-upload" chain, achieving rapid acquisition of point cloud files by directly accessing local storage and indexes, improving user experience, and saving bandwidth and computing resources.
[0066] In some embodiments of this disclosure, the access request includes identification information of the point cloud file, and step 105 may specifically include the following steps:
[0067] Based on the identification information of the point cloud file, query the target index record corresponding to the identification information in the index database;
[0068] Obtain the file handle from the target index record;
[0069] Binary data of point cloud files is obtained from the source private file system based on file handles.
[0070] In this embodiment, the point cloud file identification information (such as a task ID) carried in the access request can be extracted and used as a query key to quickly retrieve the target index record matching it in the browser's index database. The pre-stored file handle is then extracted from this record and used directly as an access credential to read the corresponding point cloud file binary data from the browser's Source Private File System (OPFS). This entire process, using identification information as an index, database queries as a bridge, and file handles as the key, achieves efficient and accurate direct mapping and retrieval from user requests to local file data, avoiding redundant data transmission and processing overhead.
[0071] In some embodiments of this disclosure, the method further includes:
[0072] Use a parser corresponding to the point cloud file format to decode the point cloud file and extract the point cloud data;
[0073] The point cloud data is transmitted to the 3D rendering engine for visualization rendering to obtain the rendering result.
[0074] In this embodiment of the disclosure, after obtaining the point cloud file, a corresponding dedicated parser can be selected according to the specific format of the point cloud file (such as MCAP, LAS) to decode the binary data read from OPFS, extract the three-dimensional coordinate point set and additional attributes (such as color, reflection intensity), and send this structured point cloud data to the 3D rendering engine integrated in the browser. The 3D rendering engine generates the corresponding three-dimensional spatial graphics according to the point coordinates and attributes, and outputs the results as a visual rendering result that can be rendered and displayed in real time on the browser page, so that users can intuitively browse and operate the point cloud scene.
[0075] In some embodiments of this disclosure, an interface for reading text files can be created to asynchronously read text file content from the Browser Source Private File System (OPFS). It receives a handle to a specific file in OPFS as a parameter. First, it obtains the file object representing the file using the `getFile()` method of the handle. Then, it calls the `text()` method of the file object to asynchronously read the file content and parse it into a UTF-8 encoded string, returning it. This interface can be used to read configuration files, logs, JavaScript object representation JSON metadata, or other text format data stored in OPFS, providing a simple and secure way for upper-layer applications to access text data.
[0076] In some embodiments of this disclosure, an interface for reading binary files can be created to asynchronously read binary file content from OPFS. It receives a file handle, obtains the corresponding File object through the handle, and calls its asynchronous instance method to read the entire file content as an ArrayBuffer binary data buffer object. This function is suitable for processing raw data in images, audio, video, point cloud files with custom binary encoding (such as MCAP), or any non-text format, providing underlying support for direct manipulation of binary data in the browser.
[0077] In some embodiments of this disclosure, a directory file interface can be created to implement recursive traversal and file discovery functions for a specified directory in OPFS: given a directory path name, the OPFS API is used to enter the directory, and an iterator is used to recursively traverse all subdirectories and files under it, collecting and returning an array containing all subfile handles; this function enables applications to dynamically obtain a list of files stored in OPFS for building file browsers, dynamically loading resources, or managing storage space, and is the foundation for realizing file system visualization and management.
[0078] In some embodiments of this disclosure, an interface for deleting directories can be created to provide a method for safely and thoroughly deleting a specified directory and all its contents in OPFS: by calling an asynchronous instance method and setting the recursive parameter to the `{recursive: true}` option, all files and subdirectories under the target directory can be recursively deleted, and the directory itself can be removed from the file system. This is used to clean up temporary data, unload task-related files, or implement user-driven deletion operations, ensuring the dynamic manageability of the browser's local storage space.
[0079] In some embodiments of this disclosure, a compatibility detection interface can be created to detect at runtime whether the current browser environment supports the OPFS function: by checking whether the OPFS function exists, a boolean value is quickly returned indicating whether the OPFS API can be used; in progressively enhanced web applications, this detection can be used to enable advanced local storage functions in browsers that support OPFS, and degrade to other storage solutions (such as IndexedDB binary large object Blob storage) in browsers that do not support OPFS, thereby ensuring the basic availability and compatibility of the application.
[0080] According to the point cloud data processing method based on browser storage proposed in this disclosure, upon responding to an access request for a point cloud file, the method intelligently determines whether a corresponding index record already exists in the browser's index database. If it does not exist, the method automatically executes a complete process: obtaining the compressed package, decompressing it in the browser environment to obtain the point cloud file, storing it in the browser's source private file system, and generating an index record containing the obtained file handle and storing it in the index database. If the index record already exists, the corresponding point cloud file can be quickly obtained from the source private file system directly using the file handle in the record. This mechanism realizes fully automatic processing of point cloud data from remote compressed packages to browser-localized and indexed storage, and provides a fast reading path for subsequent access without repeated downloading and decompression. This significantly improves access efficiency and user experience while ensuring data persistence and security.
[0081] Figure 2 This is a block diagram illustrating a point cloud data processing device based on browser storage, according to an exemplary embodiment. (Refer to...) Figure 2 The device includes a first acquisition unit 201, a decompression unit 202, a first storage unit 203, a second storage unit 204, and a second acquisition unit 205.
[0082] The first acquisition unit 201 is used to respond to a user's access request for a point cloud file input to the browser, and to acquire a compressed package of the point cloud file if there is no index record of the point cloud file in the browser's index database; the point cloud file includes point cloud data.
[0083] The decompression unit 202 is used to decompress the compressed package in a browser environment to obtain a point cloud file;
[0084] The first storage unit 203 is used to store the point cloud file to the browser's source private file system and obtain the file handle corresponding to the point cloud file.
[0085] The second storage unit 204 is used to store index records, including file handles, into the index database;
[0086] The second acquisition unit 205 is used to acquire point cloud files from the source private file system by using the file handle in the index record when there is an index record of point cloud files in the index database.
[0087] In some embodiments of this disclosure, the decompression unit 202 may specifically be used for:
[0088] Obtain the binary data of the compressed file;
[0089] The binary data is decompressed using a decompression function to obtain the archived data;
[0090] The archived data is parsed according to the preset format specifications to extract point cloud files.
[0091] In some embodiments of this disclosure, the apparatus may further include:
[0092] The filtering unit is used to filter point cloud files based on preset system file feature rules to exclude metadata files automatically generated by the operating system.
[0093] In some embodiments of this disclosure, the first storage unit 203 may specifically be used for:
[0094] Obtain the original path information of the point cloud file, and recursively create the directory structure corresponding to the original path information in the source private file system;
[0095] In the created directory structure, create a storage file with the same name as the point cloud file, and write the binary data from the point cloud file into the storage file.
[0096] In some embodiments of this disclosure, the second storage unit 204 may specifically be used for:
[0097] Index records are generated based on file handles and the metadata associated with the file handles; the metadata includes the identification information and storage timestamp of the point cloud file;
[0098] Store index records in the index database.
[0099] In some embodiments of this disclosure, the access request includes identification information of the point cloud file, and the second acquisition unit 205 may specifically be used for:
[0100] Based on the identification information of the point cloud file, query the target index record corresponding to the identification information in the index database;
[0101] Obtain the file handle from the target index record;
[0102] Binary data of point cloud files is obtained from the source private file system based on file handles.
[0103] In some embodiments of this disclosure, the apparatus further includes:
[0104] The extraction unit is used to decode the point cloud file using a parser corresponding to the point cloud file format and extract the point cloud data.
[0105] The rendering unit is used to transmit point cloud data to the 3D rendering engine for visualization rendering and to obtain the rendering results.
[0106] Regarding the apparatus in the above embodiments, the specific manner in which each module performs its operation has been described in detail in the embodiments related to the method, and will not be elaborated upon here.
[0107] The browser-based point cloud data processing device proposed in this disclosure intelligently determines whether a corresponding index record already exists in the browser's index database upon responding to an access request for a point cloud file. If it does not exist, it automatically executes a complete process: obtaining the compressed package, decompressing it in the browser environment to obtain the point cloud file, storing it in the browser's source private file system, and generating an index record containing the obtained file handle and storing it in the index database. If the index record already exists, the corresponding point cloud file can be quickly obtained from the source private file system directly using the file handle in the record. This mechanism realizes fully automatic processing of point cloud data from remote compressed packages to browser-localized and indexed storage, and provides a fast reading path for subsequent access without repeated downloading and decompression, thereby significantly improving access efficiency and user experience while ensuring data persistence and security.
[0108] Figure 3 This is a block diagram illustrating an apparatus for a browser-based point cloud data processing method according to an exemplary embodiment. For example, apparatus 300 may be an electronic device, such as a mobile phone, computer, digital broadcasting terminal, messaging device, tablet device, personal digital assistant, etc.
[0109] Reference Figure 3 The device 300 may include one or more of the following components: a processing component 302, a memory 304, a power component 306, a multimedia component 308, an audio component 310, an input / output (I / O) interface 312, and a communication component 316.
[0110] Processing component 302 typically controls the overall operation of device 300, such as operations associated with display, telephone calls, data communication, camera operation, and recording. Processing component 302 may include one or more processors 320 to execute instructions to perform all or part of the steps of the methods described above. Furthermore, processing component 302 may include one or more modules to facilitate interaction between processing component 302 and other components. For example, processing component 302 may include a multimedia module to facilitate interaction between multimedia component 308 and processing component 302.
[0111] Memory 304 is configured to store various types of data to support the operation of device 300. Examples of such data include instructions for any application or method operating on device 300, contact data, phonebook data, messages, pictures, videos, etc. Memory 304 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk.
[0112] The power supply component 306 provides power to the various components of the device 300. The power supply component 306 may include a power management system, one or more power sources, and other components associated with generating, managing, and distributing power to the device 300.
[0113] Multimedia component 308 includes a screen that provides an output interface between the device 300 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touchscreen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensors may sense not only the boundaries of the touch or swipe action but also the duration and pressure associated with the touch or swipe operation. In some embodiments, multimedia component 308 includes a front-facing camera and / or a rear-facing camera. When the device 300 is in an operating mode, such as a shooting mode or a video mode, the front-facing camera and / or the rear-facing camera may receive external multimedia data. Each front-facing camera and rear-facing camera may be a fixed optical lens system or have focal length and optical zoom capabilities.
[0114] Audio component 310 is configured to output and / or input audio signals. For example, audio component 310 includes a microphone (MIC) configured to receive external audio signals when device 300 is in an operating mode, such as call mode, recording mode, and voice recognition mode. The received audio signals may be further stored in memory 304 or transmitted via communication component 316. In some embodiments, audio component 310 also includes a speaker for outputting audio signals.
[0115] I / O interface 312 provides an interface between processing component 302 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to, home buttons, volume buttons, start buttons, and lock buttons.
[0116] Communication component 316 is configured to facilitate wired or wireless communication between device 300 and other devices. Device 300 can access wireless networks based on communication standards, such as WiFi, 2G, or 3G, or combinations thereof. In one exemplary embodiment, communication component 316 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, communication component 316 also includes a near-field communication (NFC) module to facilitate short-range communication. For example, the NFC module may be implemented based on radio frequency identification (RFID) technology, Infrared Data Association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.
[0117] In an exemplary embodiment, the apparatus 300 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the methods described above.
[0118] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 304 including instructions, which can be executed by a processor 320 of the device 300 to perform the above-described method. For example, the non-transitory computer-readable storage medium may be a ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage device, etc.
[0119] In an exemplary embodiment, a computer program product is also provided, including a computer program that implements the above-described method when executed by the processor 320 of the device 300.
[0120] Other embodiments of the invention will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of the invention that follow the general principles of the invention and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of the invention are indicated by the following claims.
[0121] It should be understood that the present invention is not limited to the precise structure described above and shown in the accompanying drawings, and various modifications and changes can be made without departing from its scope. The scope of the invention is limited only by the appended claims.
Claims
1. A point cloud data processing method based on browser storage, characterized in that, include: In response to a user's request to access a point cloud file in the browser, if the point cloud file does not exist in the browser's index database, a compressed package of the point cloud file is obtained; the point cloud file includes point cloud data. The compressed package is decompressed in a browser environment to obtain a point cloud file; Store the point cloud file in the browser's source private file system and obtain the file handle corresponding to the point cloud file; The index record including the file handle is stored in the index database; If an index record for the point cloud file exists in the index database, the point cloud file is retrieved from the source private file system using the file handle in the index record; The step of storing the point cloud file in the browser's source private file system includes: Obtain the original path information of the point cloud file, and recursively create a directory structure corresponding to the original path information in the source private file system. The OPFS API is called layer by layer from the root directory through the fast return algorithm to create subdirectories at each level of the path in turn until the directory tree structure that is completely consistent with the original compressed package is completely reproduced in the source private file system. In the created directory structure, a storage file with the same name as the point cloud file is created, and the binary data from the point cloud file is written into the storage file. Specifically, in the reconstructed corresponding directory path, a storage file with the same name as the original point cloud file is created using the OPFS API, and the file handle of the storage file is obtained. A writable stream is opened using the file handle, and the original binary data blocks of the decompressed point cloud file are directly written into the writable stream. After the writing is completed, the stream is properly closed to ensure that all data is synchronized to disk-level storage.
2. The point cloud data processing method based on browser storage according to claim 1, characterized in that, The step of decompressing the compressed package in a browser environment to obtain a point cloud file includes: Obtain the binary data of the compressed package; The binary data is decompressed using a decompression function to obtain archived data; The archived data is parsed according to the preset format specifications to extract the point cloud file.
3. The point cloud data processing method based on browser storage according to claim 1, characterized in that, After decompressing the compressed package in the browser environment to obtain the point cloud file, the method further includes: The point cloud files are filtered based on preset system file feature rules to exclude metadata files automatically generated by the operating system.
4. The point cloud data processing method based on browser storage according to claim 1, characterized in that, The step of storing the index record, including the file handle, into the index database includes: An index record is generated based on the file handle and the metadata associated with the file handle; the metadata includes the identification information and storage timestamp of the point cloud file; The index records are stored in the index database.
5. The point cloud data processing method based on browser storage according to claim 1, characterized in that, The access request includes the identification information of the point cloud file; obtaining the point cloud file from the source private file system using the file handle in the index record includes: Based on the identification information of the point cloud file, query the index database for the target index record corresponding to the identification information; Obtain the file handle from the target index record; Based on the file handle, the binary data of the point cloud file is obtained from the source private file system.
6. The point cloud data processing method based on browser storage according to claim 1, characterized in that, The method also includes: The point cloud file is decoded using a parser corresponding to the point cloud file format to extract the point cloud data; The point cloud data is transmitted to a 3D rendering engine for visualization rendering to obtain the rendering result.
7. A point cloud data processing apparatus based on browser storage, employing the point cloud data processing method based on browser storage as described in any one of claims 1-6, characterized in that, include: The first acquisition unit is configured to respond to a user's access request for a point cloud file input into the browser, and if no index record of the point cloud file exists in the browser's index database, acquire a compressed package of the point cloud file; the point cloud file includes point cloud data. The decompression unit is used to decompress the compressed package in a browser environment to obtain a point cloud file; The first storage unit is used to store the point cloud file in the browser's source private file system and obtain the file handle corresponding to the point cloud file. The second storage unit is used to store index records, including the file handle, into the index database; The second acquisition unit is used to acquire the point cloud file from the source private file system by using the file handle in the index record when the index record of the point cloud file exists in the index database.
8. An electronic device, characterized in that, include: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor, when executing the computer program, implements the method as described in any one of claims 1 to 6.
9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the method as described in any one of claims 1 to 6.