Seismic data volume web efficient access and request method, system and equipment

Abstract

The invention provides a seismic data volume web efficient access and request method, system and device, and belongs to the field of oil exploration. The method comprises the following steps: inputting an original seismic SEGY data volume; the original seismic SEGY data volume is analyzed through OpenVDS and then stored in a VDS data storage layer of the server side; the Web side establishes connection with the data service interface layer of the server side after acquiring a user instruction, establishes a request body according to the user instruction, and transmits the request body to the data service interface layer of the server side in a json mode; and after receiving the data request, the data service interface layer of the server side reads the corresponding data stored in the VDS data storage layer according to the data request and transmits the data to the Web side. According to the method, second-level data service response can be provided, the method is supported to be applied to any web system conforming to a front-end and back-end separation technology, and efficient access and visualization of large-scale seismic data are achieved.

Description

Technical Field

[0001] This invention belongs to the field of petroleum exploration, and specifically relates to a method, system and device for efficient web access and request of seismic data. Background Technology

[0002] With the rapid development of big data, internet, and physical hardware technologies, the amount of data in various fields is growing exponentially. In the oil exploration field, the efficient loading and display of gigabyte-scale single seismic data volumes has gradually become an important application requirement for exploration and development decision-making and deployment analysis. Traditional seismic data display often relies on desktop professional software, which has high environmental dependence and low loading and display efficiency, failing to meet the application needs of front-line researchers for rapid visualization of seismic data volumes.

[0003] Chinese patent publication CN103399347A discloses a method for rapid network visualization of 3D seismic data. It primarily uses bitmap indexing, where the server locates the storage unit corresponding to a specified local area image sent by the client within the study area, compresses the local area image to obtain a compressed local image, and transmits it to the client over the network; the client then displays the compressed local image. This technology, which generates an image from data on the server side and transmits it to the front end, requires significant network bandwidth, and the image resolution is often limited, making it impossible to obtain the data details the user wants to see. Summary of the Invention

[0004] The purpose of this invention is to solve the problems existing in the prior art and provide a method, system and device for efficient web access and request of seismic data volumes. By using OpenVDS technology, a data request interface for seismic data volumes is invented, which can provide data service response in seconds and supports application in any web system that conforms to the front-end and back-end separation technology, realizing efficient access and visualization of large-scale seismic data.

[0005] This invention is achieved through the following technical solution:

[0006] A first aspect of the present invention provides a method for efficient web access and request of seismic data volumes, comprising:

[0007] Input the raw seismic SEGY data volume;

[0008] The original seismic SEGY data volume is parsed using OpenVDS and then stored in the VDS data storage layer on the server.

[0009] After the web client receives the user's command, it establishes a connection with the data service interface layer of the server and creates a request body based on the user's command, which is then transmitted to the data service interface layer of the server in JSON format.

[0010] After receiving a data request, the server-side data service interface layer reads the corresponding data stored in the VDS data storage layer and transmits it to the Web client.

[0011] A further improvement of the present invention is that:

[0012] The raw seismic SEGY data volume was analyzed using OpenVDS technology. Specific operations included:

[0013] First, OpenVDS preprocesses the SEGY data body to convert the SEGY data body format into VDS source data;

[0014] Then, the VDS source data is processed by layering and segmenting, storing the text header, track header, and track data in the data body separately, and establishing index information, and storing them in the form of file storage or object storage.

[0015] A further improvement of the present invention is that:

[0016] The VDS data storage layer includes two data access interfaces: the layout interface and the accessManager interface. Different parts of the data can be accessed through different interfaces.

[0017] A further improvement of the present invention is that:

[0018] The layout interface provides macroscopic access to VDS data, and is responsible for describing and managing the organization and storage of volumetric data. Users can quickly obtain VDS block, dimension, sampling, compression method and metadata.

[0019] A further improvement of the present invention is that:

[0020] The accessManager interface is responsible for coordinating access to and management of volume data, ensuring efficient reading and writing of data, and accessing data from the outside world through requests.

[0021] A further improvement of the present invention is that:

[0022] The request body built by the web client based on user instructions includes: fileID(Int), direction(String), lineRange(Int), traceIndex(Array), step(Int), and byteOrder(String).

[0023] fileID(Int): A unique identifier for the requested VDS data body;

[0024] direction(String): Used to specify the dimension from which data is extracted from the 3D volume data;

[0025] lineRange(Int): The range of data for a specific dimension in the requested data body;

[0026] traceIndex(Array): A set of pointers to specify the required trace data.

[0027] step(Int): The step size used to return the data;

[0028] byteOrder(String): Specifies the byte order of data during storage and transmission.

[0029] A further improvement of the present invention is that:

[0030] The data service interface layer adopts the Spring Boot architecture. The data service interface layer communicates with the Web client through the RESTful protocol, providing the Web client with seismic trace data service data request interface, trace head information service data request interface, and text header service data request interface.

[0031] A further improvement of the present invention is that:

[0032] After receiving a data request, the server-side data service interface layer reads the corresponding data stored in the VDS data storage layer according to the data request and transmits it to the Web client. Specific operations include:

[0033] After receiving the request, the server-side data service interface layer parses it and instantiates it into a request body (req). It then defines the data storage space based on the data range in the request body, instantiates the output stream (OutputStream) to obtain the output stream organization, and passes the request body and the output stream organization to the accessManager interface of the VDS data storage layer. It then obtains the returned data (floatbuffer), writes it into the OutputStream according to the specified sequence, and finally packages it into a responseEntity and transmits it to the Web client.

[0034] A second aspect of the present invention provides a web-based efficient system for accessing and requesting seismic data, comprising: a web client and a server.

[0035] The server-side consists of an input layer, a VDS data storage layer, and a data service interface layer.

[0036] The input layer is used to input the raw seismic SEGY data volume;

[0037] The VDS data storage layer is used to store the SEGY data body parsed using OpenVDS;

[0038] The data service interface layer adopts the Spring Boot architecture. The data service interface layer communicates with the web client through the RESTful protocol. It provides the web client with data request interfaces for seismic track data service, track header information service, and text header service. After receiving the request from the web client, the data service interface layer retrieves the corresponding data from the VDS data storage layer and returns it to the web client.

[0039] A third aspect of the present invention is a computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor, when executing the computer program, implements the steps of a method for efficient web access and request of seismic data.

[0040] Compared with the prior art, the beneficial effects of the present invention are:

[0041] This invention supports the automated conversion of seismic data volumes to VDS format data files and their storage in object storage. It provides a standard and efficient VDS parsing algorithm that supports multidimensional indexing and fast retrieval, enabling the location of the required data portion within seconds. It also supports parallel data processing and can utilize multi-core processors to accelerate data operations.

[0042] Using this invention, the storage space of the dumped seismic data volume can be reduced to 30% of the original while ensuring data quality, greatly optimizing data redundancy. Furthermore, this invention offers platform independence and flexibility, utilizing a microservices approach for development, supporting use in different computing environments, and can be integrated into various seismic data processing or visualization systems as needed. It is particularly suitable for B / S architecture seismic exploration data management systems, supporting the management of large-scale (TB-level or even PB-level) data volumes. Based on front-end data requests, it quickly retrieves target feature data, transmits data via byte streams, and supports real-time data rendering and visualization, significantly improving front-end visualization efficiency.

[0043] This invention can be directly used in the oil and gas exploration industry for previewing and visualizing large-scale seismic data volumes, especially in geophysical data management systems. For the need for efficient web-based access to seismic data volumes, this invention provides sub-second data response times without requiring special porting or adaptation. It only requires code integration and the provision of a specified data request body, effectively solving the web visualization and access needs of massive seismic data volumes, greatly improving data management efficiency, and facilitating rapid access to seismic data volumes for business personnel, thus demonstrating its practicality. Furthermore, this invention is a backend service interface that supports cloud deployment with a microservice architecture, eliminating the cumbersome nature and high environmental dependence of traditional desktop software, further highlighting its novelty and inventiveness. Attached Figure Description

[0044] Figure 1 This is a flowchart illustrating the efficient web access and request method for earthquake data volumes in an embodiment of the present invention.

[0045] Figure 2 This is a schematic diagram of VDS source data parsing;

[0046] Figure 3 A diagram illustrating data request services from the web client and the server.

[0047] Figure 4 This is a schematic diagram of the structure of the efficient web access and request system for earthquake data in an embodiment of the present invention;

[0048] Figure 5 , Figure 6 This is a visualization of the efficient web access to seismic data volumes using the method of this invention. Detailed Implementation

[0049] The present invention will now be described in further detail with reference to the accompanying drawings:

[0050] This invention primarily analyzes the visualization requirements of seismic data volumes (SEGY) in geophysical data management systems within the oil and gas exploration field, and investigates the daily work scenarios of platform users. Based on OpenVDS data reorganization technology, it invents a backend data service interface that enables efficient storage and access to SEGY data volumes, ensures data retrieval performance, and meets the frontend's requirements for efficient visualization.

[0051] The main content includes: dumping the SEGY data body into a VDS file and storing it in S3 object storage or file storage, with file storage being directly stored on the local server; during data access, the backend quickly reads and retrieves the VDS file based on the data request sent by the frontend, and then transmits it to the frontend via byte stream to achieve rapid extraction of the target data, which is then rendered by the frontend for efficient visualization.

[0052] The technologies used in this invention include:

[0053] Seismic data analysis technology: OpenVDS

[0054] Server-side technology: Spring Boot

[0055] Web technologies: JavaScript, Vue 3.0

[0056] The above-mentioned technologies are all mature technologies and can be directly used in this invention.

[0057]

Example 1

[0058] This invention provides a method for efficient web access and request of seismic data volumes, such as... Figure 1 As shown, the specific steps include:

[0059] S1, Input the raw seismic SEGY data volume;

[0060] S2, the original seismic SEGY data volume is parsed using OpenVDS and then stored in the VDS data storage layer on the server.

[0061] S3: After the web client receives the user's command, it establishes a connection with the data service interface layer of the server. At the same time, it creates a request body based on the user's command and transmits it to the data service interface layer of the server in JSON format.

[0062] S4: After receiving a data request, the server-side data service interface layer reads the corresponding data stored in the VDS data storage layer according to the data request and transmits it to the Web client.

[0063] This invention supports the automated conversion of seismic data volumes to VDS format data files and their storage in object storage. It provides a standard and efficient VDS parsing algorithm that supports multidimensional indexing and fast retrieval, enabling the location of the required data portion within seconds. It also supports parallel data processing and can utilize multi-core processors to accelerate data operations.

[0064]

Example 2

[0065] S2, after parsing the original seismic data volume using OpenVDS, stores it in the VDS data storage layer on the server.

[0066] The raw seismic data volume mainly refers to the massive SEGY data volume, which needs to be parsed and read using OpenVDS technology.

[0067] The raw seismic SEGY data is parsed using OpenVDS and stored in the VDS data storage layer on the server. There are two main storage methods: one is storing it as a .vds file in physical storage (file storage); the other is storing it as an object storage method, supporting efficient data retrieval and high-frequency access. Both methods are uniquely identified by a URL or ID, and both provide external data access interfaces.

[0068] The raw seismic SEGY data volume was analyzed using OpenVDS technology. Specific operations included:

[0069] First, OpenVDS preprocesses the SEGY data body to convert the SEGY data body format into VDS source data;

[0070] It should be understood that OpenVDS preprocesses the SEGY data volume. Specifically, OpenVDS reads the EBCDIC header and binary header of the SEGY data volume file to obtain a basic description and key information about the seismic data volume. Following the guidance of the trace header, it reads the seismic trace data trace by trace. During the process of reading the seismic trace data, OpenVDS converts it from SEGY format to VDS format. This conversion process includes data decompression, reorganization, and necessary format adjustments.

[0071] Then, the VDS source data is processed by layering and segmenting, storing the text header, track header, and track data in the data body separately, and establishing index information, and storing them in the form of file storage or object storage.

[0072] like Figure 2 As shown, the VDS data storage layer includes two data access interfaces: the layout interface and the accessManager interface. Different parts of the data can be accessed through different interfaces. The layout interface provides macroscopic access to VDS data, responsible for describing and managing the organization and storage of volumetric data. Users can quickly obtain VDS chunks, dimensions, sampling, compression methods, and metadata. The accessManager interface is responsible for coordinating access and management of volumetric data, ensuring efficient data reading and writing. It accesses data from the outside world through requests. When the server-side data service interface layer receives a request from the web client, it needs to define a series of standard parameters specified by VDS according to the request (the request parameters between the front-end and back-end are defined in advance during the interface design. This invention defines the interface form based on the RESTful protocol. When the back-end receives the request parameters, it organizes the parameters required by the accessManager according to the request parameters from the front-end, such as data dimensions, data index position information, index offset, interpolation method, etc.) and establishes a request link with the accessManager interface, returning a data block of type floatbuffer. Developers can perform arbitrary transformations, calculations, and other operations on the floatbuffer data.

[0073] Based on the data request sent from the web client, the VDS data storage layer can provide three different types of data: subset, samples, and trace. Subset is used for scenarios that require acquiring data from a large continuous area, and can retrieve a subset of volume data within a specified range. Sample is used for scenarios that require accessing discrete sampling point data, and can retrieve data from specific sampling points within volume data. Trace is used for scenarios that require collecting data along a certain direction or path, and can retrieve arbitrary line data.

[0074]

Example 3

[0075] S3: After the web client receives the user's command, it establishes a connection with the data service interface layer of the server. At the same time, it creates a request body based on the user's command and transmits it to the data service interface layer of the server in JSON format.

[0076] It should be understood that user commands refer to the operations performed by the user when using the corresponding function, such as previewing, network creation, and profile extraction.

[0077] The request body built by the web client based on user instructions includes: fileID(Int), direction(String), lineRange(Int), traceIndex(Array), step(Int), and byteOrder(String).

[0078] fileID(Int): A unique identifier for the requested VDS data body;

[0079] direction(String): Used to specify the dimension from which data is extracted from the 3D volume data;

[0080] lineRange(Int): The range of data for a specific dimension in the requested data body;

[0081] traceIndex(Array): Specifies a set of pointers to the desired trace data;

[0082] step(Int): Returns the step size of the data;

[0083] byteOrder(String): Specifies the byte order of data during storage and transmission.

[0084] The data service interface layer adopts the Spring Boot architecture. It communicates with the web client via the RESTful protocol, providing the web client with data request interfaces for seismic trace data services, trace header information services, and text header services. Upon receiving a request from the web client, the data service interface layer retrieves the corresponding data from the VDS data storage layer and returns it to the web client.

[0085]

Example 4

[0086] S4, after receiving a data request, the server-side data service interface layer reads the corresponding data stored in the VDS data storage layer according to the data request and transmits it to the Web client, such as... Figure 3 As shown, the specific operations include:

[0087] After receiving the request, the server-side data service interface layer parses it and instantiates it into a request body (req). It then defines the data storage space based on the data range in the request body, instantiates the output stream (OutputStream) to obtain the output stream organization, and passes the request body and the output stream organization to the accessManager interface of the VDS data storage layer. It then obtains the returned data (floatbuffer), writes it into the OutputStream according to the specified sequence, and finally packages it into a responseEntity and transmits it to the Web client.

[0088] The request body is parsed and instantiated into a request body req. The specific steps are as follows: First, the server needs to create a class corresponding to the request body and define the corresponding attributes that correspond to the parameters in the request body req. In Java, there are classes and methods for parsing the front-end request body, such as ObjectMapper, which can directly parse the request body req and pass the parsing to the object instantiated from the request body class.

[0089] The data storage space is defined based on the data range in the request body. Since VDS data is a volume of data with at least three dimensions (x, y, z), a class for storing the data space is defined in advance. This class is similar to a multidimensional array and has a class method to set the size of the three dimensions (x, y, z), which is equivalent to a box. When the data range in the request body is obtained, the program will instantiate this class. When retrieving VDS data using AccessManager, this instantiated box object needs to be passed in.

[0090] OutputStream is a Java class used to write primitive data types and string data to an output stream. Before the request is executed, an OutputStream byte stream object is instantiated to receive the data returned by the accessManager, write it into this OutputStream byte stream object, and return it to the web client.

[0091] In this invention, the data floatbuffer may be one of three different types of data: subset, samples, or trace.

[0092]

Example 5

[0093] This invention provides a web-based system for efficient accessing and requesting seismic data volumes, such as... Figure 4 As shown, it includes a web client and a server. The web client and the server communicate via the RESTful protocol.

[0094] The server-side consists of an input layer, a VDS data storage layer, and a data service interface layer.

[0095] The input layer is used to input the raw seismic SEGY data volume;

[0096] The VDS data storage layer is used to store the SEGY data body parsed using OpenVDS;

[0097] The data service interface layer adopts the Spring Boot architecture, providing the web client with data request interfaces for seismic trace data services, trace head information services, and text header services. After receiving the request from the web client, the data service interface layer retrieves the corresponding data from the VDS data storage layer and returns it to the web client.

[0098] The Web application layer directly faces users, providing them with seismic data visualization applications, including 2D profile visualization, arbitrary lines, well-connected profiles, 3D visualization, etc. It communicates with the data service interface layer through the RESTful protocol.

[0099] The data service interface layer in this invention has high portability and integration, and supports integration with all front-end seismic data visualization components that conform to the front-end and back-end separation architecture.

[0100]

Example 6

[0101] In the oil and gas exploration industry, there is a frequent need for online previewing and manipulation of seismic data volumes. One company developed a system for managing geophysical data. The system is based on a front-end / back-end separated microservice architecture, with the front-end using the Vue framework and the back-end using the Spring Boot architecture. It also provides an open S3 object storage interface for storing geophysical data. Seismic data visualization utilizes the INTGeotoolkit visualization component and OpenVDS technology for seismic data management. The platform features data management functions such as seismic data management and work area management, as well as visualization functions such as online visualization of seismic profiles, 2D survey lines, arbitrary line extraction, and excavation. The system preprocesses seismic data volumes into VDS format and stores them in object storage, linking them to a database. Users can preview basin-level seismic work area data within the system. After creating a new seismic network, survey lines can be extracted to display seismic profiles unfolding in any direction. The efficiency of seismic profile response and display is within seconds and does not vary with the user's computer configuration.

[0102] This invention can also be used in the development of professional earthquake processing and interpretation software based on Web technology. For large-scale earthquake data, this invention can provide a standard data access interface, efficient data storage and access, and provide users with richer visualization options and more personalized data display.

[0103] This invention has been applied multiple times in actual production, and its feasibility has been verified. For example... Figure 5 and Figure 6 The image shows the visualization results of efficient web access to seismic data volumes using the method of this invention.

[0104]

Example 7

[0105] This invention provides a computer device, including a memory and a processor. The memory stores a computer program, and the processor executes the computer program to perform the following steps:

[0106] S1, Input the raw seismic SEGY data volume;

[0107] S2, the original seismic SEGY data volume is parsed using OpenVDS and then stored in the VDS data storage layer on the server.

[0108] S3: After the web client receives the user's command, it establishes a connection with the data service interface layer of the server. At the same time, it creates a request body based on the user's command and transmits it to the data service interface layer of the server in JSON format.

[0109] S4: After receiving a data request, the server-side data service interface layer reads the corresponding data stored in the VDS data storage layer according to the data request and transmits it to the Web client.

[0110] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. The computer program can be stored in a non-volatile computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. Any references to memory, storage, databases, or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in various forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), dual data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link DRAM (SLDRAM), Rambus direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.

[0111] The above technical solution is only one embodiment of the present invention. For those skilled in the art, based on the principles disclosed in the present invention, it is easy to make various types of improvements or modifications, and not limited to the technical solutions described in the specific embodiments of the present invention. Therefore, the foregoing description is only a preferred option and is not restrictive.

Claims

1. A method for efficient web access and request of seismic data volumes, characterized in that, include: Input the raw seismic SEGY data volume; The original seismic SEGY data volume is parsed using OpenVDS and then stored in the VDS data storage layer on the server. After the web client receives the user's command, it establishes a connection with the data service interface layer of the server and creates a request body based on the user's command, which is then transmitted to the data service interface layer of the server in JSON format. After receiving a data request, the server-side data service interface layer reads the corresponding data stored in the VDS data storage layer and transmits it to the Web client.

2. The method according to claim 1, characterized in that, The raw seismic SEGY data volume was analyzed using OpenVDS technology. Specific operations included: First, OpenVDS preprocesses the SEGY data body to convert the SEGY data body format into VDS source data; Then, the VDS source data is processed by layering and segmenting, storing the text header, track header, and track data in the data body separately, and establishing index information, and storing them in the form of file storage or object storage.

3. The method according to claim 1, characterized in that, The VDS data storage layer includes two data access interfaces: the layout interface and the accessManager interface. Different parts of the data can be accessed through different interfaces.

4. The method according to claim 3, characterized in that, The layout interface provides macroscopic access to VDS data, and is responsible for describing and managing the organization and storage of volumetric data. Users can quickly obtain VDS block, dimension, sampling, compression method and metadata.

5. The method according to claim 3, characterized in that, The accessManager interface is responsible for coordinating access to and management of volume data, ensuring efficient reading and writing of data, and accessing data from the outside world through requests.

6. The method according to claim 1, characterized in that, The request body built by the web client based on user instructions includes: fileID(Int), direction(String), lineRange(Int), traceIndex(Array), step(Int), and byteOrder(String). fileID(Int): A unique identifier for the requested VDS data body; direction(String): Used to specify the dimension from which data is extracted from the 3D volume data; lineRange(Int): The range of data for a specific dimension in the requested data body; traceIndex(Array): A set of pointers to specify the required trace data. step(Int): The step size used to return the data; byteOrder(String): Specifies the byte order of data during storage and transmission.

7. The method according to claim 1, characterized in that, The data service interface layer adopts the Spring Boot architecture. The data service interface layer communicates with the Web client through the RESTful protocol, providing the Web client with seismic trace data service data request interface, trace head information service data request interface, and text header service data request interface.

8. The method according to claim 1, characterized in that, After receiving a data request, the server-side data service interface layer reads the corresponding data stored in the VDS data storage layer according to the data request and transmits it to the Web client. Specific operations include: After receiving the request, the server-side data service interface layer parses it and instantiates it into a request body (req). It then defines the data storage space based on the data range in the request body, instantiates the output stream (OutputStream) to obtain the output stream organization, and passes the request body and the output stream organization to the accessManager interface of the VDS data storage layer. It then obtains the returned data (floatbuffer), writes it into the OutputStream according to the specified sequence, and finally packages it into a responseEntity and transmits it to the Web client.

9. A web-based efficient system for accessing and requesting seismic data volumes, characterized in that: It includes a web client and a server. The server includes an input layer, a VDS data storage layer, and a data service interface layer. The input layer is used to input the raw seismic SEGY data volume; The VDS data storage layer is used to store the SEGY data body parsed using OpenVDS; The data service interface layer adopts the Spring Boot architecture. The data service interface layer communicates with the web client through the RESTful protocol. It provides the web client with data request interfaces for seismic track data service, track header information service, and text header service. After receiving the request from the web client, the data service interface layer retrieves the corresponding data from the VDS data storage layer and returns it to the web client.

10. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the efficient web access and request method for seismic data volumes as described in any one of claims 1-8.

Images