Seismic data query method

Abstract

The embodiment of the invention relates to the technical field of data processing, and discloses a seismic data query method. The method comprises the steps of querying initial seismic data under the condition that a data query request of a target format sent by a client is received through a hypertext transfer protocol interface; and determining target seismic data in the target format according to the initial seismic data, and sending the target seismic data to the client through the hypertext transfer protocol interface. According to the technical scheme provided by the embodiment of the invention, the problem of poor universality of seismic data query is solved.

Description

Technical Field

[0001] This invention relates to the field of data processing technology, and in particular to a method for querying earthquake data. Background Technology

[0002] Seismic data is a core foundation for industrial automation, data processing, and distributed computing related to geological exploration. Against this backdrop, querying seismic data has become a crucial aspect of geological exploration.

[0003] However, currently available earthquake data query services can only provide earthquake data query services to fixed clients such as fixed software, fixed platforms, or fixed web pages, resulting in poor universality of earthquake data query services, which urgently needs to be addressed. Summary of the Invention

[0004] This invention provides a method for querying earthquake data, which solves the problem of poor universality in earthquake data querying.

[0005] According to one aspect of the present invention, a seismic data query method is provided, which may include:

[0006] Upon receiving a data query request in the target format from a client via a Hypertext Transfer Protocol interface, query the initial earthquake data;

[0007] Based on the initial seismic data, the target seismic data in the target format is determined, and the target seismic data is sent to the client via the Hypertext Transfer Protocol interface.

[0008] The technical solution of this invention, upon receiving a data query request in a target format from a client via a Hypertext Transfer Protocol (HTTP) interface, queries initial seismic data; based on the initial seismic data, it determines target seismic data in the target format and sends the target seismic data to the client via the HTTP interface. This technical solution provides seismic data query services to clients capable of sending data query requests in a target format via the HTTP interface, thus overcoming the limitation of providing seismic data query services only to fixed clients and solving the problem of poor universality in seismic data querying.

[0009] It should be understood that the description in this section is not intended to identify key or important features of the embodiments of the present invention, nor is it intended to limit the scope of the invention. Other features of the invention will become readily apparent from the following description. Attached Figure Description

[0010] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0011] Figure 1 This is a flowchart of an earthquake data query method provided by an embodiment of the present invention;

[0012] Figure 2 This is a flowchart of another earthquake data query method provided by an embodiment of the present invention;

[0013] Figure 3 This is a flowchart of another earthquake data query method provided by an embodiment of the present invention;

[0014] Figure 4 This is a schematic diagram of an optional example of another earthquake data query method provided according to an embodiment of the present invention;

[0015] Figure 5 This is a flowchart of another optional example of a seismic data query method provided according to an embodiment of the present invention;

[0016] Figure 6 This is a schematic diagram of yet another optional example of a seismic data query method provided according to an embodiment of the present invention;

[0017] Figure 7 This is a flowchart of yet another optional example of a seismic data query method provided according to an embodiment of the present invention;

[0018] Figure 8 This is a structural block diagram of an earthquake data query device provided according to an embodiment of the present invention;

[0019] Figure 9 This is a schematic diagram of the structure of an electronic device that implements the earthquake data query method of this invention. Detailed Implementation

[0020] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

[0021] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such data can be interchanged where appropriate so that embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. The same applies to "target," "original," etc., and will not be repeated here. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0022] Before introducing the embodiments of the present invention, we will first provide an exemplary description of the current application scenarios for earthquake data querying, the implementation process of the solutions used for earthquake data querying, and the reasons for the poor universality of earthquake data querying. This will help to better understand why the solution proposed in the embodiments of the present invention can solve the problem of poor universality of earthquake data querying.

[0023] For example, in the fields of industrial automation, data processing and distributed computing related to geological exploration, with the continuous advancement of seismic exploration technology and the development of computer software technology, the forms of batch seismic operations are becoming increasingly complex. The complex forms of seismic operations lead to the generation of a large amount of seismic data, and the querying of seismic data is a key link to ensure the system stability and efficiency in the field of geological exploration.

[0024] Various seismic data processing clients typically suffer from inefficient management of seismic data query workflows, and an inability to fully accommodate the diverse needs of processing personnel, platform reliability, and scalability. For example, they often require inefficient manual searching of seismic data, hindering fast and efficient automated querying, particularly impacting scenarios requiring real-time automated seismic data retrieval. To improve efficiency and achieve accurate and comprehensive processing of seismic data, these clients rely on interaction with servers that provide automated seismic data querying. However, currently, servers offering seismic data query services only provide services to fixed software, platforms, or web pages with a direct interaction relationship. For instance, users can only query seismic data through a fixed webpage, making it difficult to provide seismic data query services to third-party seismic data processing clients such as maintenance platforms and data analysis tools that do not have a direct interaction relationship with the server. In other words, users cannot easily query seismic data through third-party platforms.

[0025] To address this, embodiments of the present invention can provide earthquake data query services to clients capable of sending data query requests in a target format via the Hypertext Transfer Protocol interface. This eliminates the limitation of providing earthquake data query services only to fixed clients, thus solving the problem of poor universality in earthquake data querying. This will be explained in detail below.

[0026] Figure 1 This is a flowchart of a seismic data query method provided in an embodiment of the present invention. This embodiment is applicable to seismic data query scenarios. The method can be executed by the seismic data query device provided in this embodiment of the present invention. This device can be implemented in software and / or hardware, and can be integrated into an electronic device, which can be various user terminals or servers.

[0027] See Figure 1 The method of this invention is applied to the server side, and the method of this invention specifically includes the following steps:

[0028] S110. Upon receiving a data query request in the target format from a client via the Hypertext Transfer Protocol interface, query the initial earthquake data.

[0029] It should be noted that the method of this embodiment is applied to the server side, specifically to an earthquake data management system on the server side (e.g., a data server). This earthquake data management system is developed based on the C++ language. The earthquake data management system can provide Hypertext Transfer Protocol (HTTP) services through a Representational State Transferful (RESTful) design framework to support cross-platform calls. It can also use a plug-in architecture and can uniformly store and manage earthquake data, thereby achieving centralized management and efficient access to earthquake data. This effectively solves the limitations of traditional systems in earthquake data storage and management, improves the availability of earthquake data, and thus helps to realize earthquake data querying in this embodiment.

[0030] In this embodiment of the invention, upon receiving a data query request in the target format from a client via a Hypertext Transfer Protocol (HTTP) interface, before querying the initial seismic data, an earthquake data management system containing an earthquake data interface and plugins can be started in the server's Linux operating system environment. The earthquake data interface and plugins adopt a RESTful service architecture developed in C++. The earthquake data interface and plugins are then invoked to initialize the earthquake data management environment. For example, upon receiving a data query request in the target format from a client via a HTTP interface, before querying the initial seismic data, an earthquake data management system containing an earthquake data interface and plugins can be started in the server's Linux operating system environment. The compilation and installation of core dependency libraries, including the earthquake data interface, asynchronous input / output (I / O), and earthquake data, are prepared to ensure the integrity of the underlying support system. Standardized management of earthquake data plugins is implemented, meaning all earthquake data plugins are stored uniformly in a directory, with each earthquake data plugin's independent subdirectory containing dynamic libraries, configuration files, and dependency declarations. A RESTful interface service is then built and started.

[0031] The Hypertext Transfer Protocol interface can be understood as an interface that uses the Hypertext Transfer Protocol.

[0032] A client can be understood as an end capable of sending data query requests in a target format using the Hypertext Transfer Protocol.

[0033] The target format can be understood as a format that the server can process; specifically, it can be a format that both the server and the client can handle. The target format can be a relatively common data format, such as JavaScript Object Notation (JSON).

[0034] A data query request can be understood as a request sent by the client to query earthquake data.

[0035] Initial earthquake data can be understood as earthquake data retrieved in response to a data query request.

[0036] In this embodiment of the invention, initial seismic data can be queried upon receiving a data query request via a Hypertext Transfer Protocol (HTTP) interface. For example, upon receiving a JSON-formatted data query request from a client via an HTTP interface, a method for querying seismic data can be invoked to query and read the initial seismic data under the target job corresponding to the job identifier in the data query request. Performing the data query based on the HTTP interface ensures the secure and universal transmission of the data query request. Using a JSON-formatted data query request enables lightweight transmission and universal request processing. Therefore, performing the data query based on the HTTP interface and using a JSON-formatted data query request improves the response speed, efficiency, and universality of seismic data queries. It should be noted that since seismic data may be generated during actual geological exploration and other operations, the initial seismic data queried can be seismic data generated during the operation of the target job corresponding to the job identifier. For another example, the data query request can be parsed to obtain the seismic data identifier; a search query can then be performed in the seismic data management system based on the seismic data identifier to retrieve the initial seismic data.

[0037] It is important to note that if a data query request is received from a client through the Hypertext Transfer Protocol (HTTP) interface, it means that the client also sent the data query request through the HTTP HTTP interface, and the client can send the data query request using the HTTP POST method.

[0038] In this embodiment of the invention, if no initial earthquake data is found, the client can be responded with error messages such as "NOSUCHLISTFILE" and / or "NOSUCHLOGTFILE" via the Hypertext Transfer Protocol interface to terminate the earthquake data query process.

[0039] S120. Based on the initial seismic data, determine the target seismic data in the target format, and send the target seismic data to the client via the Hypertext Transfer Protocol interface.

[0040] In this embodiment of the invention, target seismic data in a target format can be determined based on the initial seismic data, thereby achieving standardized processing of the initial seismic data.

[0041] In this embodiment of the invention, if the initial seismic data is seismic data in the target format, the initial seismic data can be directly used as the target seismic data.

[0042] In this embodiment of the invention, the target seismic data can be sent to the client via the Hypertext Transfer Protocol interface, thereby achieving standardized transmission of the target seismic data.

[0043] In this embodiment of the invention, when querying initial seismic data, the database information of the database where the initial seismic data is located can be determined (the database information may include at least one of the database name and table name, etc.), and then the database information can be mapped to the target seismic data so that the source of the target seismic data can be traced in the future.

[0044] The solution of this invention not only solves the problem of poor universality in earthquake data querying, but also enables remote query and management of earthquake data by the client, thereby improving the efficiency of remote interaction in earthquake data querying. Furthermore, the solution of this invention has the advantages of high flexibility, high convenience, strong portability, strong scalability, strong maintainability, and low maintenance cost. It is particularly suitable for earthquake data querying in terms of data storage and management, workflow management, access control, and client interaction, and can meet the collaborative needs between different clients, which helps to achieve efficient management and access control of earthquake data.

[0045] The solution of this invention can be used not only for querying earthquake data, but also for other management such as adding, deleting and modifying earthquake data. For example, when a data deletion request in a target format is received from a client through a Hypertext Transfer Protocol interface, the earthquake data corresponding to the data deletion request can be deleted.

[0046] The technical solution of this invention, upon receiving a data query request in a target format from a client via a Hypertext Transfer Protocol (HTTP) interface, queries initial seismic data; based on the initial seismic data, it determines target seismic data in the target format and sends the target seismic data to the client via the HTTP interface. This technical solution provides seismic data query services to clients capable of sending data query requests in a target format via the HTTP interface, thus overcoming the limitation of providing seismic data query services only to fixed clients and solving the problem of poor universality in seismic data querying.

[0047] An optional technical solution for querying initial earthquake data includes: parsing the data query request to obtain an earthquake data identifier, and verifying the client's identity based on the earthquake data identifier; and querying the initial earthquake data if the client's identity verification is successful.

[0048] Here, earthquake data identifier can be understood as the identifier corresponding to the earthquake data requested; earthquake data identifier may include at least one of the following: operation identifier, survey line identifier, project identifier, and work area identifier.

[0049] Understandably, data query requests can include earthquake data identifiers, which are then parsed to obtain these identifiers. It's important to note that parsing data query requests can be achieved using efficient parsing algorithms (such as JSON parsers) to quickly extract key information like earthquake data identifiers, ensuring a timely response.

[0050] Client identity can be understood as the identity of a client; client identity can be, for example, a legitimate identity or an illegitimate identity, or an authorized identity or an unauthorized identity, and so on.

[0051] In this embodiment of the invention, client identity verification and / or legitimacy verification can be performed based on the seismic data identifier. For example, it can be verified whether the identifier format of the seismic data identifier meets a preset format specification, and / or whether the identifier field of the seismic data identifier meets a preset field specification. If not, it indicates that the client may be an unauthorized client that is not authorized to understand the query specifications for seismic data queries (e.g., including preset format specifications and / or preset field specifications, etc.), thereby helping to prevent unauthorized access and thus helping to protect the overall security of seismic data queries. Another example is that the value of the job identifier field in the seismic data identifier can be extracted, and the client identity can be verified based on the value of the job identifier field.

[0052] In this embodiment of the invention, initial earthquake data can be queried after the client has been successfully authenticated.

[0053] In this embodiment of the invention, if client authentication fails, an error message can be returned to the client via the Hypertext Transfer Protocol interface.

[0054] The solution of this invention verifies the client's identity based on the earthquake data identifier, and queries the initial earthquake data if the client's identity verification is successful. The mechanism of verifying the client's identity determines the rationality of the data query request, thereby ensuring the security and stability of earthquake data query, and preventing the waste of resources due to invalid data query requests from clients whose client identity verification fails.

[0055] Another optional technical solution, before determining the target seismic data in the target format based on the initial seismic data, the seismic data query method further includes: parsing the data query request to obtain survey line information; normalizing the initial seismic data based on the survey line information; and updating the initial seismic data based on the obtained normalization result.

[0056] Among them, survey line information can be understood as information related to survey lines in seismic data; survey line information may include at least one survey line attribute such as survey line length and orientation angle.

[0057] In this embodiment of the invention, the data query request can be parsed to obtain the survey line information. For example, the data query request can be parsed to obtain the seismic data identifier, and the survey line information can be determined based on the seismic data identifier (for example, the survey line information can be extracted from the seismic data identifier that includes the survey line information, or the survey line information can be determined based on the survey line identifier in the seismic data identifier, etc.).

[0058] In this embodiment of the invention, the initial seismic data can be normalized based on the survey line information. For example, the survey line attributes such as survey line length and orientation angle in the initial seismic data can be normalized based on the survey line information.

[0059] In this embodiment of the invention, the initial seismic data can be updated based on the normalization result obtained after normalizing the initial seismic data.

[0060] In this embodiment of the invention, the initial seismic data is normalized by parsing the survey line information obtained from the data query request, and the initial seismic data is updated based on the normalization result, which can ensure the availability and consistency of the initial seismic data.

[0061] Another optional technical solution involves querying initial seismic data, including: parsing the data query request to obtain query information, wherein the query information includes at least one of project information and work area information; and querying the initial seismic data based on the query information.

[0062] The query information can be understood as information used to query initial earthquake data.

[0063] Project information can be understood as information about the project corresponding to the initial seismic data requested in the query. Project information may include project-level information such as project name and project number. It should be noted that since seismic data may be generated during actual geological exploration and other projects, the initial seismic data can be queried through project information; that is, the initial seismic data generated during the process of the project corresponding to the project information can be retrieved through project information.

[0064] Work area information can be understood as information about the work area corresponding to the initial seismic data requested in the query. Work area information can include work area name and work area number, among other work area-level information. It is important to note that seismic data may be generated during the process of seismic data acquisition or other geological exploration related work within the work area. Therefore, the initial seismic data can be queried through the work area information; that is, the initial seismic data generated during work within the work area corresponding to the work area information can be retrieved through the work area information.

[0065] In this embodiment of the invention, a data query request can be parsed to obtain query information. For example, a data query request can be parsed to obtain an earthquake data identifier, and the query information can be determined based on the earthquake data identifier (for example, the query information can be extracted from the earthquake data identifier that includes the query information, or the query information can be determined based on the query identifier in the earthquake data identifier, etc.).

[0066] In this embodiment of the invention, initial seismic data can be queried based on query information. For example, first seismic data can be queried based on project information (specifically, by filtering out seismic data that does not belong to the project corresponding to the project information, the first seismic data can be obtained; this process of querying the first seismic data can be understood as filtering out seismic data that is irrelevant to the project corresponding to the project information); initial seismic data can be filtered from the first seismic data based on work area information. In this case, the initial seismic data can be understood as the seismic data belonging to the work area corresponding to the work area information, filtered out from the first seismic data based on the work area information.

[0067] The solution of this invention parses the data query request to obtain query information, and then queries the initial earthquake data based on the query information, which can improve the accuracy of the queried initial earthquake data.

[0068] Figure 2 This is a flowchart of another seismic data query method provided in this embodiment of the invention. This embodiment is based on and optimized from the above-described technical solutions. In this embodiment, optionally, determining the target seismic data in the target format based on the initial seismic data includes: if the data size of the initial seismic data is greater than or equal to a first preset block size, dividing the initial seismic data into blocks to obtain at least two data blocks; establishing a block index for the at least two data blocks, and converting the block index into the target seismic data in the target format. The explanations of terms that are the same as or corresponding to those in the above embodiments are not repeated here.

[0069] See Figure 2 The method of this embodiment is applied to the server side, and the method of this embodiment may specifically include the following steps:

[0070] S210. Upon receiving a data query request in the target format from a client via the Hypertext Transfer Protocol interface, query the initial earthquake data.

[0071] S220. If the size of the initial seismic data is greater than or equal to the first preset block size, the initial seismic data is divided into blocks to obtain at least two data blocks.

[0072] Here, "data size" can be understood as the size of the initial seismic data.

[0073] The first preset block size can be understood as the minimum data size when the initial seismic data needs to be processed in blocks; the first preset block size can be, for example, a preset specific byte size, such as 10MB.

[0074] A data block can be understood as block-shaped data obtained after dividing the initial seismic data into blocks.

[0075] In this embodiment of the invention, if the initial seismic data size is greater than or equal to a first preset block size, the initial seismic data can be divided into blocks to obtain at least two data blocks. For example, if the initial seismic data size is greater than or equal to the first preset block size, a corresponding block division algorithm can be used to adaptively divide the initial seismic data into blocks to obtain at least two data blocks. Another example is that if the initial seismic data size is greater than or equal to the first preset block size, the number of blocks can be calculated based on the data size and a second preset block size, and the initial seismic data can be divided into blocks based on the number of blocks and the second preset block size to obtain at least two data blocks.

[0076] S230. Create block indexes for at least two data blocks and convert the block indexes into target seismic data in the target format.

[0077] Here, a block index can be understood as an index related to at least two data blocks presented in an index structure; a block index may include, for example, index entries corresponding to at least two data blocks respectively, and each index entry may include, for example, at least one of the block information of the corresponding data block and relevant information of the seismic data in the data block (e.g., it may include entry information of the seismic data).

[0078] In this embodiment of the invention, a block index for at least two data blocks can be established, and the block index can be converted into target seismic data.

[0079] In this embodiment of the invention, for each data block, the data block can be converted into a conversion block of the target format, and each conversion block can be used as a target seismic data. The obtained target seismic data can then be sent to the client sequentially through the Hypertext Transfer Protocol interface.

[0080] S240. Send the target seismic data to the client via the Hypertext Transfer Protocol interface.

[0081] The technical solution of this invention involves dividing the initial seismic data into blocks when the initial seismic data size is greater than or equal to a first preset block size, resulting in at least two data blocks. A block index is then established for each of the at least two data blocks, and the block index is converted into target seismic data in the target format. This technical solution, by converting the block index into target seismic data sent to the client, avoids excessive resource consumption caused by directly transmitting large amounts of initial seismic data and ensures efficient response to seismic data queries.

[0082] An optional technical solution involves determining target seismic data in a target format based on initial seismic data, and further includes converting the initial seismic data into target seismic data in the target format if the data size is smaller than the size of a first preset block.

[0083] In this embodiment of the invention, when the data size is smaller than the first preset block size, the initial seismic data can be converted into target seismic data, and the target seismic data converted from the initial seismic data can be directly sent to the client through the Hypertext Transfer Protocol interface, thereby ensuring the integrity of the seismic data sent to the client when the data size is smaller than the first preset block size.

[0084] Another optional technical solution involves dividing the initial seismic data into blocks to obtain at least two data blocks, including: determining the data distribution of the initial seismic data, and determining a block division strategy based on the data distribution, data size, and a second preset block size; and dividing the initial seismic data into blocks according to the block division strategy to obtain at least two data blocks.

[0085] The data distribution can be understood as the distribution of information in the initial earthquake data.

[0086] The second preset block size can be understood as the maximum, minimum and / or expected size of the data block; for example, the second preset block size could be 4MB.

[0087] The block-based strategy can be understood as the strategy adopted for processing initial seismic data into blocks.

[0088] In this embodiment of the invention, a block partitioning strategy can be determined based on the data distribution, data size, and a second preset block size. For example, the second preset block size can be adjusted, the number of blocks determined, the partitioning method determined, and / or the partitioning order determined based on the data distribution, data size, and the second preset block size. The partitioning strategy is then determined based on the adjusted second preset block size, number of blocks, and / or partitioning order. Specifically, for example, the second preset block size is 4MB (the maximum size a data block can reach), the data size is 32MB, and the data distribution is that the initial seismic data is divided into four parts: header information, execution information, completion information, and tail information, with the execution information being the most resource-intensive part. Based on the data distribution, data size, and the second preset block size, the number of blocks is determined to be 8, and the partitioning method is to dynamically divide the execution information into 1-5 blocks according to its information size, with each of the other parts consisting of one block. The partitioning strategy is then determined based on the number of blocks and the partitioning method.

[0089] The solution of this invention divides the initial seismic data into blocks according to a block division strategy determined by the data distribution, data size and second preset block size, to obtain at least two data blocks. This ensures that the initial seismic data can be divided into blocks to meet the requirements of the initial seismic data.

[0090] Figure 3 This is a flowchart of another seismic data query method provided in this embodiment of the invention. This embodiment is based on the above-described technical solutions and optimized. In this embodiment, optionally, the target seismic data includes block entries corresponding to at least two data blocks respectively; after sending the target seismic data to the client through the Hypertext Transfer Protocol interface, the method further includes: upon receiving an entry query request from the client for a target entry in the target seismic data through the Hypertext Transfer Protocol interface, determining the target block corresponding to the target entry from the at least two data blocks, wherein the block entries corresponding to the at least two data blocks respectively include the target entry; converting the target block into a format block of the target format, and sending the format block to the client through the Hypertext Transfer Protocol interface. The explanations of terms that are the same as or corresponding to those in the above embodiments are not repeated here.

[0091] See Figure 3 The method of this embodiment is applied to the server side, and the method of this embodiment may specifically include the following steps:

[0092] S310. Upon receiving a data query request in the target format from a client via the Hypertext Transfer Protocol interface, query the initial earthquake data.

[0093] S320. If the size of the initial seismic data is greater than or equal to the first preset block size, the initial seismic data is divided into blocks to obtain at least two data blocks.

[0094] S330. Establish block indexes for at least two data blocks and convert the block indexes into target seismic data in the target format, wherein the target seismic data includes block entries corresponding to the at least two data blocks respectively.

[0095] Here, a block entry can be understood as an entry in the target seismic data, and each block entry can correspond to a data block; each block entry can, for example, correspond to an index entry; a block entry can, for example, include at least one of the block information of the corresponding data block and the relevant information of the seismic data in the data block (e.g., it can include the entry information of the seismic data).

[0096] In this embodiment of the invention, the target seismic data may include block entries corresponding to at least two data blocks, so as to perform subsequent format block access and management through the block entries corresponding to at least two data blocks.

[0097] S340. Send the target seismic data to the client via the Hypertext Transfer Protocol interface.

[0098] S350. Upon receiving an entry query request from a client for a target entry in the target seismic data via a Hypertext Transfer Protocol interface, determine the target block corresponding to the target entry from at least two data blocks, wherein the block entries corresponding to the at least two data blocks respectively include the target entry.

[0099] The target entry can be understood as the entry corresponding to the data block that the client needs to query.

[0100] An entry query request can be understood as a request to query the data blocks under a target entry.

[0101] A target block can be understood as a data block corresponding to a target entry.

[0102] In this embodiment of the invention, when an entry query request sent by a client is received through the Hypertext Transfer Protocol interface, the target block can be determined from at least two data blocks.

[0103] It should be noted that the client may send an information query request for a specific entry in the target entry. However, since the seismic data corresponding to that entry is located in the target block, the information query request can be regarded as an entry query request. Alternatively, the seismic data corresponding to the information query request can be determined from at least two data blocks, and that seismic data can be used as the target block.

[0104] S360: Convert the target block into a format block of the target format, and send the format block to the client via the Hypertext Transfer Protocol interface.

[0105] In this context, a format block can be understood as block-shaped data obtained by converting a target block into a target format.

[0106] In this embodiment of the invention, the target block can be converted into a format block, and the format block can be sent to the client through the Hypertext Transfer Protocol interface.

[0107] The technical solution of this invention, upon receiving an entry query request from a client for a target entry in target seismic data via a Hypertext Transfer Protocol (HTTP) interface, determines a target block corresponding to the target entry from at least two data blocks, wherein each of the at least two data blocks corresponds to a block entry including the target entry; the target block is converted into a format block of the target format, and the format block is sent to the client via the HTTP interface. This technical solution, by determining the target block upon receiving an entry query request from a client via the HTTP interface, converting the target block into a format block, and sending the format block to the client via the HTTP interface, can send the seismic data requested by the client to the client without excessive resource consumption caused by directly transmitting large amounts of initial seismic data.

[0108] An optional technical solution, after dividing the initial seismic data into blocks to obtain at least two data blocks, the seismic data query method further includes: establishing a temporary storage space and storing at least two data blocks in the temporary storage space; determining the target block corresponding to the target entry from the at least two data blocks, including: determining the target block corresponding to the target entry from the at least two data blocks stored in the temporary storage space.

[0109] Temporary storage space can be understood as storage space that temporarily stores at least two data blocks.

[0110] In this embodiment of the invention, a temporary storage space can be established, for example, according to the storage strategy configured in the earthquake data management system.

[0111] In this embodiment of the invention, the target block can be determined from at least two data blocks stored in the temporary storage space.

[0112] The solution of this invention can establish a temporary storage space and store at least two data blocks in the temporary storage space to determine the target block from the at least two data blocks stored in the temporary storage space, thereby achieving an efficient storage space management mechanism to ensure stability and reliability when querying large-scale seismic data or querying large-scale seismic data.

[0113] Based on the above solution, another optional technical solution is that, after the target seismic data is sent to the client via the Hypertext Transfer Protocol interface, the seismic data query method further includes: releasing temporary storage space upon receiving a query end request from the client for the target seismic data via the Hypertext Transfer Protocol interface.

[0114] The query end request can be understood as a request to end the query for the target seismic data.

[0115] In this embodiment of the invention, when a query end request is received from the client via the Hypertext Transfer Protocol interface, that is, when the client will no longer send query requests for block entries in the target seismic data, temporary storage space can be released, thereby saving storage space.

[0116] To better understand the technical solutions of the above embodiments of the present invention, an optional example is provided herein. For example, see [link to example]. Figure 4 In the earthquake data management system, the service layer can utilize a Hypertext Transfer Protocol (HTTP) listener to route and distribute data query requests in JSON format received from clients (e.g., multiple World Wide Web (Web) clients) via the HTTP interface. The data processing layer parses the query requests to obtain earthquake data identifiers, verifies the client's identity based on these identifiers, and, if client authentication is successful, queries the initial earthquake data from the storage layer using multiple dimensions. If the initial earthquake data size is greater than or equal to the first preset block size, the data processing layer performs adaptive block processing on the initial earthquake data and establishes temporary storage space in the storage layer, storing at least two data blocks in this temporary space. The data processing layer also creates a block index and converts it into target earthquake data in JSON format. Finally, the response layer in the earthquake data management system performs an HTTP response, sending the target earthquake data to the client via the HTTP interface. The above technical solution solves the problem of poor universality of earthquake data query, realizes standardized query and access control of earthquake data, improves the processing efficiency of earthquake data query, realizes efficient and automated earthquake data query, ensures accurate and comprehensive query of earthquake data, and improves the flexibility and convenience of earthquake data query.

[0117] To better understand the technical solutions of the above embodiments of the present invention, another optional example is provided here. For example, see... Figure 5The system starts the earthquake data management system containing the earthquake data interface and plugins; upon receiving a JSON-formatted data query request from the client via the Hypertext Transfer Protocol (HTTP) interface, it parses the data query request to obtain the job identifier; based on the job identifier, it verifies the client's identity, and returns an error message if the client's authentication fails; if the client's authentication is successful, it queries the initial earthquake data from the storage layer from multiple dimensions; if the initial earthquake data is not found, it returns an error message; if the initial earthquake data is found, it performs adaptive block processing on the initial earthquake data; it establishes a block index and converts the block index into target earthquake data in JSON format; and it sends the target earthquake data to the client via the HTTP interface.

[0118] To better understand the technical solutions of the above embodiments of the present invention, another optional example is provided here. For example, see [link to example]. Figure 6 The client can send a data query request in JSON format. The server, upon receiving the request via the Hypertext Transfer Protocol (HTTP) interface, can query the initial seismic data. If the initial seismic data is not found, the server responds with a "NOSUCHFILE" error message. If the initial seismic data is found, a block-based discrimination process is executed, determining whether the initial seismic data size is greater than or equal to 10MB. If the data size is less than 10MB, the initial seismic data is converted into target seismic data in JSON format and sent to the client via the HTTP interface. If the initial seismic data size is greater than or equal to 10MB, a block-based strategy is determined, and the initial seismic data is divided into blocks according to the strategy, resulting in at least two data blocks. Temporary storage space is established, and the at least two data blocks are stored in this temporary storage space. A block index is created, and the block index is converted into target seismic data in JSON format and sent to the client via the HTTP interface. Upon receiving a JSON-formatted query completion request from the client regarding the target seismic data via the HTTP interface, the temporary storage space is released.

[0119] To better understand the technical solutions of the above embodiments of the present invention, another optional example is provided here. For example, see... Figure 7Upon receiving a data query request from a client via the Hypertext Transfer Protocol (HTTP) interface, the system parses the request to obtain the seismic data identifier and verifies the client's identity based on this identifier. If authentication fails, and the client has already been re-authenticated three times, an error message is returned. If the client has been re-authenticated less than three times, the system repeats the authentication process based on the seismic data identifier. If client authentication is successful, the system queries the initial seismic data. Based on the initial seismic data, it determines the target seismic data in the target format and sends the target seismic data to the client via the HTTP interface.

[0120] Figure 8 This is a structural block diagram of an earthquake data query device provided in an embodiment of the present invention. This device is used to execute the earthquake data query method provided in any of the above embodiments. This device and the earthquake data query methods of the above embodiments belong to the same inventive concept. Details not described in detail in the embodiments of the earthquake data query device can be found in the embodiments of the above earthquake data query methods. See also... Figure 8 The device is configured on the server side and may specifically include: an initial seismic data query module 410 and a target seismic data transmission module 420.

[0121] The initial earthquake data query module 410 is used to query the initial earthquake data when a data query request in the target format is received from the client through the Hypertext Transfer Protocol interface.

[0122] The target seismic data sending module 420 is used to determine the target seismic data in the target format based on the initial seismic data, and send the target seismic data to the client through the Hypertext Transfer Protocol interface.

[0123] Optionally, the target seismic data transmission module 420 may include:

[0124] The data block acquisition submodule is used to divide the initial seismic data into blocks when the initial seismic data size is greater than or equal to the first preset block size, to obtain at least two data blocks.

[0125] The block index conversion submodule is used to create block indexes for at least two data blocks and convert the block indexes into target seismic data in the target format.

[0126] Optionally, based on the above-described apparatus, the target seismic data includes block entries corresponding to at least two data blocks respectively;

[0127] The device may also include:

[0128] The target block determination module is used to determine the target block corresponding to the target entry from at least two data blocks after the target seismic data is sent to the client through the Hypertext Transfer Protocol interface and an entry query request sent by the client for the target entry in the target seismic data is received through the Hypertext Transfer Protocol interface. The block entries corresponding to the at least two data blocks include the target entry.

[0129] The format block sending module is used to convert the target block into a format block of the target format and send the format block to the client through the Hypertext Transfer Protocol interface.

[0130] Optionally, based on the above-described apparatus, the apparatus may further include:

[0131] The data block storage module is used to create a temporary storage space after the initial seismic data is processed into blocks to obtain at least two data blocks, and to store at least two data blocks into the temporary storage space.

[0132] The target block determination module may include:

[0133] The target block determination submodule is used to determine the target block corresponding to the target entry from at least two data blocks stored in the temporary storage space.

[0134] Optionally, based on the above-described apparatus, the apparatus may further include:

[0135] The temporary storage space release module is used to release temporary storage space after the target seismic data is sent to the client via the Hypertext Transfer Protocol interface and after receiving a query end request from the client for the target seismic data via the Hypertext Transfer Protocol interface.

[0136] Optionally, based on the above-described device, the target seismic data transmission module 420 may further include:

[0137] The initial seismic data conversion submodule is used to convert initial seismic data into target seismic data in the target format when the data size is smaller than the first preset block size.

[0138] Optionally, based on the above-described apparatus, the data block obtaining submodule may include:

[0139] The block strategy determination unit is used to determine the data distribution of the initial seismic data and to determine the block strategy based on the data distribution, data size, and second preset block size.

[0140] The data block is a unit used to divide the initial seismic data into blocks according to the block division strategy, resulting in at least two data blocks.

[0141] Optionally, the initial seismic data query module 410 may include:

[0142] The client authentication submodule is used to parse data query requests, obtain earthquake data identifiers, and verify the client's identity based on the earthquake data identifiers.

[0143] The first initial earthquake data query submodule is used to query initial earthquake data after the client has been successfully authenticated.

[0144] Optionally, the device may also include:

[0145] The survey line information acquisition module is used to parse the data query request and obtain the survey line information before determining the target seismic data in the target format based on the initial seismic data.

[0146] The initial seismic data update module is used to normalize the initial seismic data based on the survey line information, and update the initial seismic data based on the obtained normalization results.

[0147] Optionally, the initial seismic data query module 410 may include:

[0148] The query information retrieval submodule is used to parse the data query request and obtain the query information, which includes at least one of project information and work area information;

[0149] The second initial earthquake data query submodule is used to query initial earthquake data based on the query information.

[0150] The earthquake data query device provided in this embodiment of the invention, through an initial earthquake data query module, queries initial earthquake data upon receiving a data query request in a target format from a client via a Hypertext Transfer Protocol (HTTP) interface; and through a target earthquake data sending module, determines target earthquake data in a target format based on the initial earthquake data and sends the target earthquake data to the client via the HTTP interface. This device can provide earthquake data query services to clients capable of sending data query requests in a target format via the HTTP interface, thus overcoming the limitation of providing earthquake data query services only to fixed clients and solving the problem of poor universality in earthquake data querying.

[0151] The earthquake data query device provided in this embodiment of the invention can execute the earthquake data query method provided in any embodiment of the invention, and has the corresponding functional modules and beneficial effects of the method execution.

[0152] It is worth noting that in the embodiments of the earthquake data query device described above, the various units and modules included are only divided according to functional logic, but are not limited to the above division, as long as the corresponding functions can be achieved; in addition, the specific names of each functional unit are only for easy differentiation and are not used to limit the scope of protection of the present invention.

[0153] Figure 9 A schematic diagram of an electronic device 10, which can be used to implement embodiments of the present invention, is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the invention described and / or claimed herein.

[0154] like Figure 9 As shown, the electronic device 10 includes at least one processor 11 and a memory, such as a read-only memory (ROM) 12 or a random access memory (RAM) 13, communicatively connected to the at least one processor 11. The memory stores computer programs executable by the at least one processor. The processor 11 can perform various appropriate actions and processes based on the computer programs stored in the ROM 12 or loaded from storage unit 18 into the RAM 13. The RAM 13 may also store various programs and data required for the operation of the electronic device 10. The processor 11, ROM 12, and RAM 13 are interconnected via a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0155] Multiple components in electronic device 10 are connected to I / O interface 15, including: input unit 16, such as keyboard, mouse, etc.; output unit 17, such as various types of displays, speakers, etc.; storage unit 18, such as disk, optical disk, etc.; and communication unit 19, such as network card, modem, wireless transceiver, etc. Communication unit 19 allows electronic device 10 to exchange information / data with other devices through computer networks such as the Internet and / or various telecommunications networks.

[0156] Processor 11 can be a variety of general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. Processor 11 performs the various methods and processes described above, such as seismic data querying methods.

[0157] In particular, according to embodiments of the present invention, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of the present invention include a computer program product comprising a computer program carried on a non-transitory computer-readable medium, the computer program containing program code for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication unit 19, or installed from storage unit 18, or installed from ROM 12. When the computer program is executed by processor 11, it performs the functions defined in the methods of the embodiments of the present invention.

[0158] In some embodiments, the seismic data query method may be implemented as a computer program tangibly contained in a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program may be loaded and / or installed on electronic device 10 via ROM 12 and / or communication unit 19. When the computer program is loaded into RAM 13 and executed by processor 11, one or more steps of the seismic data query method described above may be performed. Alternatively, in other embodiments, processor 11 may be configured to execute the seismic data query method by any other suitable means (e.g., by means of firmware).

[0159] Various embodiments of the systems and techniques described above herein can be implemented in digital electronic circuit systems, integrated circuit systems, field-programmable gate arrays (FPGAs), application-specific integrated circuits (ASICs), application-specific standard products (ASSPs), system-on-a-chip (SoCs), complex programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0160] Computer programs used to implement the methods of the present invention can be written in any combination of one or more programming languages. These computer programs can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when executed by the processor, the computer programs cause the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The computer programs can be executed entirely on a machine, partially on a machine, as a standalone software package partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

[0161] In the context of this invention, a computer-readable storage medium can be a tangible medium that may contain or store a computer program for use by or in conjunction with an instruction execution system, apparatus, or device. A computer-readable storage medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, apparatus, or devices, or any suitable combination thereof. Alternatively, a computer-readable storage medium may be a machine-readable signal medium. More specific examples of machine-readable storage media include electrical connections based on one or more wires, portable computer disks, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fibers, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination thereof.

[0162] To provide interaction with a user, the systems and techniques described herein can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user provides input to the electronic device. Other types of devices can also be used to provide interaction with the user; for example, feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including sound input, voice input, or tactile input).

[0163] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as data servers), or middleware components (e.g., application servers), or frontend components (e.g., user computers with graphical user interfaces or web browsers through which users can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., communication networks). Examples of communication networks include local area networks (LANs), wide area networks (WANs), blockchain networks, and the Internet.

[0164] A computing system can include clients and servers. Clients and servers are generally located far apart and typically interact through communication networks. The client-server relationship is created by computer programs running on the respective computers and having a client-server relationship with each other. The server can be a cloud server, also known as a cloud computing server or cloud host, which is a hosting product within the cloud computing service system to address the shortcomings of traditional physical hosts and VPS services, such as high management difficulty and weak business scalability.

[0165] It should be understood that the various forms of processes shown above can be used, with steps reordered, added, or deleted. For example, the steps described in this invention can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution of this invention can be achieved, and this is not limited herein.

[0166] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. A method for querying earthquake data, characterized in that, Applied to the server side, including: Upon receiving a data query request in the target format from a client via a Hypertext Transfer Protocol interface, query the initial earthquake data; Based on the initial seismic data, target seismic data in the target format is determined, and the target seismic data is sent to the client via the Hypertext Transfer Protocol interface.

2. The method according to claim 1, characterized in that, The step of determining the target seismic data in the target format based on the initial seismic data includes: If the size of the initial seismic data is greater than or equal to the first preset block size, the initial seismic data is divided into blocks to obtain at least two data blocks. Create block indexes for at least two of the data blocks, and convert the block indexes into target seismic data in the target format.

3. The method according to claim 2, characterized in that, The target seismic data includes block entries corresponding to at least two of the data blocks; After sending the target seismic data to the client via the Hypertext Transfer Protocol interface, the method further includes: Upon receiving an entry query request from a client for a target entry in the target seismic data via a Hypertext Transfer Protocol interface, a target block corresponding to the target entry is determined from at least two data blocks, wherein the block entries corresponding to the at least two data blocks respectively include the target entry; The target block is converted into a format block of the target format, and the format block is sent to the client through the Hypertext Transfer Protocol interface.

4. The method according to claim 3, characterized in that, After dividing the initial seismic data into blocks to obtain at least two data blocks, the process further includes: Establish a temporary storage space and store at least two of the data blocks into the temporary storage space; Determining the target block corresponding to the target entry from at least two data blocks includes: From at least two data blocks stored in the temporary storage space, determine the target block corresponding to the target entry.

5. The method according to claim 4, characterized in that, After sending the target seismic data to the client via the Hypertext Transfer Protocol interface, the method further includes: Upon receiving a query termination request from a client for the target seismic data via the Hypertext Transfer Protocol interface, the temporary storage space is released.

6. The method according to claim 2, characterized in that, The step of determining the target seismic data in the target format based on the initial seismic data further includes: If the data size is smaller than the first preset block size, the initial seismic data is converted into target seismic data in the target format.

7. The method according to claim 2, characterized in that, The initial seismic data is divided into blocks to obtain at least two data blocks, including: The data distribution of the initial seismic data is determined, and a block division strategy is determined based on the data distribution, the data size, and the second preset block size; According to the block segmentation strategy, the initial seismic data is segmented to obtain at least two data blocks.

8. The method according to claim 1, characterized in that, The query for initial earthquake data includes: The data query request is parsed to obtain the earthquake data identifier, and the client's identity is verified based on the earthquake data identifier; If the client authentication is successful, query the initial earthquake data.

9. The method according to claim 1, characterized in that, Before determining the target seismic data in the target format based on the initial seismic data, the method further includes: The data query request is parsed to obtain the survey line information; Based on the survey line information, the initial seismic data is normalized, and the initial seismic data is updated based on the obtained normalization result.

10. The method according to claim 1, characterized in that, The query for initial earthquake data includes: The data query request is parsed to obtain query information, wherein the query information includes at least one of project information and work area information; Based on the query information, retrieve the initial earthquake data.

Images