A logging data fast storage access system and method

Abstract

The application provides a logging data quick storage access system and method, comprising the following modules: a data storage access module, receiving a storage access request of a user, and sending the storage access request of the user to a data cache module; the data cache module, providing different data object cache data storage access services, calling a logging data storage format file storage access uniform interface module, and synchronizing the data cache module with data formats in the logging data storage format file; a file each data node storage access interface module, reading information headers of corresponding nodes in the logging data storage format file through access requirements received by the file storage access uniform interface module; and the file storage access uniform interface module, providing storage access functions of different file node data by calling the logging data storage format file each data node storage access interface module. The purpose of quick storage access logging data is achieved.

Description

Technical Field

[0001] This invention relates to the field of oil and gas exploration and development technology, specifically to a system and method for rapid storage and access of well logging data. Background Technology

[0002] Well logging, as a crucial method and technology for oil and gas field exploration and development, provides vital support for oil and gas exploration, development, and production. Well logging data, as an important storage medium for geological information, requires unified management. Currently, well logging data is characterized by diverse storage formats, with commonly used formats including GDS (Geophysical Data Storage), LDF (Logging Data Format), and WIS (Well Information Standard). Each data format is applied to different scenarios and systems; for example, GDS and WIS formats are typically used for well logging data processing and interpretation, while LDF format is typically used for well logging data acquisition and processing. Different data formats have different data access interfaces and methods, and data format conversion is often required when applying them to different systems. Format conversion can lead to problems such as redundant data storage and information loss, affecting data integrity and reliability, and causing problems for data exchange, archiving, and storage. Summary of the Invention

[0003] To address the issues in existing technologies where data format conversion is often required when applying data to different systems, leading to problems such as redundant data storage and information loss, this invention provides a system and method for rapid storage and access of well logging data. It supports the entire process of well logging data acquisition, processing, interpretation, and evaluation, and provides a system for rapid storage and access of well logging data based on this data storage format, achieving the goal of rapid storage and access to well logging data.

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

[0005] A system for rapid storage and access of well logging data includes the following modules:

[0006] Data storage access module: Receives user storage access requests and sends them to the data cache module;

[0007] Data caching module: Provides data storage and access services for different data objects, calls the unified interface module for storing and accessing well logging data storage format files, and synchronizes the data caching module with the data format in the well logging data storage format files;

[0008] File data node storage access interface module: Reads the information header of the corresponding node in the well logging data storage format file through the access request received by the file storage access unified interface module;

[0009] Unified file storage access interface module: Provides storage access functions for data at different file nodes by calling the storage access interface modules of each data node in the well logging data storage format file.

[0010] Furthermore, it also includes a data cache management module: this module stores different data objects in the form of key-value pair containers, and uses the global path of the data object as the index of the key-value pair container to facilitate the retrieval of data cache modules for different data objects; this module manages all data caches in a unified manner, and when any data cache module needs to request cache, it calls the data cache management module to allocate cache.

[0011] Furthermore, the well logging data storage format file includes data format file header information, single-well data area file, and multi-well data area file. A unified well logging data storage format file can effectively speed up the file processing.

[0012] A method for fast storage and access of well logging data includes the following steps:

[0013] S1: Call the interface in the data storage access module to obtain the data cache object;

[0014] S2: Determine if the data storage access scope is in the cache;

[0015] S3: If it is in the cache, then determine whether the data in the cache is synchronized with the file;

[0016] S4: If the data in the cache is synchronized with the file, perform data storage access in the page cache, write the data in the cache to the file after data storage, and end the execution.

[0017] Furthermore, if the data storage access range is not in the cache, then the page cache corresponding to the data storage range is requested.

[0018] Furthermore, if the data in the cache is out of sync with the file, the data in the file will be read into the page cache.

[0019] Furthermore, determining whether the data storage access range is in the cache refers to considering the storage access location P, size S, and page size S. p Calculate the range of page cache numbers to be stored: Determine if the above page number is in the key-value pair container of the page cache.

[0020] A method for fast storage and access of well logging data, when the user selects real-time data storage, includes the following methods:

[0021] S1: Call the interface in the data storage access module to obtain the data cache object;

[0022] S2: And write the real-time data to the real-time page cache;

[0023] S3: Determine if the real-time data has been written. If the current real-time data has been written, terminate the execution.

[0024] Furthermore, before writing real-time data to the page cache, it is determined whether a real-time page cache exists. If it does not exist, a page cache of a fixed size is requested, and then the real-time data is written to the page cache. If a page cache exists, the real-time data is written directly to the page cache.

[0025] Furthermore, if the real-time page cache is full, write the data in the cache to a file, clear the page cache, and write the real-time data to the page cache.

[0026] Compared with the prior art, the present invention has the following beneficial technical effects:

[0027] To ensure rapid access to logging data storage format files, this invention provides a rapid logging data storage and access system. It supports the entire process of logging data acquisition, processing, interpretation, and evaluation, and is highly scalable. It supports various logging data sources, including cable-based, drilling-while-drilling, and storage-based systems, as well as logging data storage using isobathous sampling, isochronous sampling, and non-isobathous / non-isochronous sampling. This system establishes a unified data storage format and access interface within the logging industry, allowing for application in different systems without data format conversion. It solves problems such as redundant data storage and information loss caused by format conversion, providing complete and reliable logging data for upper-level applications.

[0028] This paper presents a fast storage and access method for well logging data based on the data storage format. It can dynamically allocate idle cache resources to different data objects according to user requests, make full use of system resources, and effectively alleviate the IO pressure of upper-layer applications. Users can realize fast storage and access to well logging data by calling a unified data storage and access interface, which supports high-frequency real-time data storage and access of small data volumes. Attached Figure Description

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

[0030] Figure 1 A system connection diagram of a rapid storage and access system for well logging data provided in an embodiment of the present invention;

[0031] Figure 2This is a flowchart of the data cache management part of a method for fast storage and access of well logging data provided in an embodiment of the present invention;

[0032] Figure 3 An example diagram of the paging cache portion of a fast storage and access method for well logging data provided in an embodiment of the present invention;

[0033] Figure 4 This is a flowchart of the data storage file judgment and storage cache synchronization part in a fast storage and access method for well logging data provided in an embodiment of the present invention;

[0034] Figure 5 This is a flowchart of the data storage file access part of a method for fast storage and access of well logging data provided in an embodiment of the present invention;

[0035] Figure 6 This is a flowchart of the data storage file judgment and real-time data storage cache synchronization part of a method for fast storage and access of well logging data provided in an embodiment of the present invention;

[0036] Figure 7 This is an example diagram of a single-well data structure in a rapid storage and access system for logging data provided in an embodiment of the present invention. Detailed Implementation

[0037] In the following description, only certain exemplary embodiments are briefly described. As those skilled in the art will recognize, the described embodiments can be modified in various ways without departing from the spirit or scope of the invention. Therefore, the drawings and description are considered to be exemplary in nature and not restrictive.

[0038] The embodiments of the present invention will now be described in detail with reference to the accompanying drawings.

[0039] Example 1:

[0040] This invention provides a system for rapid storage and access to well logging data, such as... Figure 1 As shown, it includes the following modules:

[0041] Data storage access module: It interacts with the logging application to receive storage access requests from users and executes the storage access requests from the logging application by calling the data cache management module.

[0042] Data Cache Management Module: Provides data caching and cache management services for data objects;

[0043] Specifically, this module stores different data objects (curves, tables, curve information, etc.) in the form of key-value pair containers, and uses the global path of the data object (file path + data type + data name) as the index of the key-value pair container to facilitate the retrieval of data cache modules for different data objects.

[0044] This module provides unified management of all data caches. When any data cache module needs to request cache, it uniformly calls the data cache management module for cache allocation. Figure 2 As shown, the system first obtains the cache size requested by the data caching module, then determines whether there is an available cache size in the system. If not, it iterates through all data caching modules, releases the least recently used cache with the fewest usages, and repeats the above cache release process until the available cache size in the system is greater than the requested cache size. Then, it notifies the data caching module that it can request a cache.

[0045] Data caching module: Provides data storage and access services for different data objects, and calls the unified interface module for file storage access to synchronize the cached data with the data in the file.

[0046] At the same time, this module adopts different caching strategies depending on the data object:

[0047] Specifically, for data such as tables, well information, and curve information, a list approach is used to fully cache all data in the file nodes corresponding to the data.

[0048] For well logging curve data, a paginated caching method is used to cache a portion of the data in the corresponding file node. The paginated caching method is as follows: Figure 3 As shown, the cache is divided into several file cache pages and one real-time data cache page: the data of a logging curve node is sequentially mapped to several consecutive file cache pages of the same size, while a real-time data cache page is provided for real-time logging curve data storage and access. The above page caches are stored in the form of key-value pair containers, with the page number as the index of the key-value pair container. Each page cache includes attributes such as page number, hit count, last used time, and whether it is synchronized with file data. In actual use, according to the location of the stored and accessed curve data, the data in the relevant files is scheduled to be stored and accessed to the page cache, and the cache is requested and released in conjunction with the data cache management module.

[0049] Unified file storage access interface module: Provides storage access functions for data at different file nodes by calling the storage access interface modules for each data node of the file.

[0050] The file data node storage access interface module mainly reads the information header of the corresponding node in the well logging data format file, obtains the data block size, and then reads the corresponding size of the data block.

[0051] It should be noted that the data storage format in this invention supports multiple logging data sources, including cable logging, drilling logging, and storage logging, as well as logging data storage for iso-depth sampling, iso-time sampling, and non-iso-depth / non-iso-time sampling. A tree structure is used to manage data nodes, specifically including data format file header information, single-well data area, and multi-well data area. Specifically, it includes:

[0052] Data format file header information: Records information such as the type identifier, major version number, minor version number, creation time, and modification time of the well logging data format file.

[0053] Single-well data area: Records logging curve data, raw logging data, logging information data, logging resource data, logging parameter card data, logging table data, etc. of a single well.

[0054] Well logging curve data includes curve header, depth data, time data, and value data.

[0055] For curves with equal depth sampling, depth data may not be required; the depth is constructed in real time using the curve header information.

[0056] For curves sampled at equal time intervals, time data may be missing; the time can be constructed in real time using the curve header information.

[0057] For non-isotropic sampling curves, both depth and time data must exist.

[0058] Raw well logging data includes a raw data header and a raw data body.

[0059] Well logging data includes well information, operation information, and instrument information.

[0060] Well logging resource data includes a resource information header and a resource data body.

[0061] The logging parameter card data includes the parameter card header and the parameter card content.

[0062] The table data includes a table header and a table body.

[0063] Multi-well data area: Records interpretation models, interpretation charts, seismic data, multi-well comparison data, and other data for multiple wells in the oilfield area.

[0064] It mainly includes the header and the data body.

[0065] If single-well data is stored, the multi-well data area will not exist.

[0066] Based on the above-mentioned well logging data storage format, in order to achieve rapid storage and access to well logging data, this invention provides a method for rapid storage and access of well logging data. The well logging data storage and access steps are as follows: Figure 4 and Figure 5As shown, the well logging data storage and access steps are as follows:

[0067] S1: Call the data storage or access interface in the data storage access module;

[0068] S2: Retrieve the data cache object;

[0069] S3: Determine whether the data storage access scope is in the cache. If it is in the cache, execute S4; otherwise, execute S5.

[0070] S4: Determine whether the data in the cache is synchronized with the file. If it is synchronized, execute S7; otherwise, execute S6.

[0071] S5: Request the page cache corresponding to the storage data range;

[0072] S6: Read the data from the file into the page cache;

[0073] S7: Store accessed data in the page cache;

[0074] S8: During data storage, write the cached data to a file.

[0075] Furthermore, the data storage access interface described in S1 includes data storage access interfaces for different data objects, and the interface parameters include the global path of the data object, the storage access location, the storage access size, etc.

[0076] The process described in S2, which involves calling the data cache management module, uses the global path of the data object to retrieve the corresponding cache object from the key-value pair container.

[0077] The determination of whether a data storage access range is in the cache, as described in S3, refers to determining the storage access location P, size S, and page size S. p Calculate the range of page cache numbers to be stored: Determine if the above page number is in the key-value pair container of the page cache.

[0078] The determination of whether the data in the cache is synchronized with the file, as described in S4, refers to retrieving the corresponding page cache from the key-value pair container based on the page cache number in S3, and using the "whether it is synchronized with the file data" attribute in the page cache to indicate whether the data in the cache is synchronized with the file.

[0079] The page cache corresponding to the data range described in S5 is requested by calling the data cache management module based on the number of page caches calculated in S3, and then requesting the corresponding number of page caches in sequence and storing them in the page cache key-value pair container.

[0080] The process described in S6, which reads data from a file into a page cache, refers to calling the unified interface module for file storage access to read file data into all newly allocated page caches and page caches that are out of sync with the file. The mapping relationship between each page cache data and the file node data position is [0, n-1]-[in, (i+1)], where n is the page cache size and i is the page cache number.

[0081] The storage of accessed data in the page cache as described in S7 refers to storing accessed data based on the storage access location P, size S, and page size S. p To retrieve the location of the data to be stored in the page cache: the starting storage access location is: page number 1. Page P%S p The end of the storage access is at position: (bit number missing) Page (P+S)% p The bits are then stored sequentially for each page cache access.

[0082] S8 is executed only during data storage. The description of writing cached data to a file refers to calling the unified interface module for file storage access to store the page cache data modified in S7 into a file.

[0083] Example 3:

[0084] like Figure 7 As shown, the data storage structure for the solidification data of Well Xian 11 is provided, specifically including:

[0085] Data format file header information: includes the type identifier of the well logging data format file, major version number, minor version number, creation time, modification time, etc., which are formed into a JSON string in the form of key-value pairs and stored in the meta node under the root path of Xian11 well .gdsx.

[0086] Single-well data area: Records logging curves, raw data, information, resources, parameter cards, tables, and other data for a single well.

[0087] The solidification node of well Xian 11 and all its sub-nodes belong to the single-well data area. The solidification node of well Xian 11 includes the nodes curve, info, para, res, and table.

[0088] The curve node is the root node of the curve data. The AC, AMP, BR, and other nodes under the curve are curve nodes. The number of nodes represents the number of logging curves.

[0089] For curve nodes such as Natural Gamma (GR), since it is a constant depth sampling and there is no time data, this node includes the curve information header meta and the value data data node.

[0090] The curve information includes curve name, flag, major version number, minor version number, curve identifier, curve dimension, curve description, curve recording method, time dimension start value, time dimension end value, time dimension interval, time dimension length, time dimension unit, time dimension type, depth dimension start value, depth dimension end value, depth dimension interval, depth dimension length, depth dimension unit, depth dimension type, data dimension start value, data dimension end value, data dimension interval, data dimension length, data dimension unit, data dimension type, etc., which are formed into a JSON string in the form of key-value pairs and stored in the meta node.

[0091] The curve's value data is stored in the data node as a binary stream.

[0092] The info node is the root node for information data. This node can store information such as well information, operational information, and instrument information.

[0093] This well instance only stores the well information node, which includes well name, well type, well location, completed well depth, wellhead X coordinate, wellhead Y coordinate, ground elevation, core filling height, core filling elevation, oil field, client unit, etc. It is stored in the wellinfo node as a JSON string in the form of key-value pairs.

[0094] The para node is the root node for parameter card data. Parameter card data is stored under each node according to the processing module. The cementing quality evaluation VDL node represents a processing module node.

[0095] The processing module nodes record parameter card data in chronological order from most recent to oldest. Each time node includes a parameter card information header (meta) node and a parameter card content (data) node.

[0096] The parameter card information includes well name, processing module name, application, etc., which is stored as a JSON string in key-value pairs in the meta node. The parameter card content is stored as a binary stream in the data node.

[0097] The res node is the root node for resource data. It can include multiple resource data nodes. The node name is the name of the resource data. Each resource data node includes a resource header (meta) and a resource data body (data).

[0098] Resource information includes resource name, resource category, resource suffix, resource size, creation time, etc., which are stored in the meta node as a JSON string in the form of key-value pairs.

[0099] Resource data is stored in data nodes as a binary stream.

[0100] The `table` node is the root node for table data. It can contain multiple tables, and the node name is the name of the table. The `table` node includes the table header (`meta`) and the table data body (`data`).

[0101] The table information includes the table name, table type, table alias, creation time, column information list, etc., which are formed into a JSON string in the form of key-value pairs and stored in the meta node.

[0102] The table data body uses column field names as keys, and forms an array of table data in the form of key-value pairs. It is then converted into a JSON string and stored in the data node.

[0103] This embodiment provides a method for accessing a single acoustic (AC) logging curve. The acoustic curve in the data file ranges from 1210m to 2160m, with a sampling interval of 0.1m, totaling 9501 sampling points. Access is granted for sampling points 900 to 1600, and the data page cache contains 500 sampling points per page. The specific steps of this fast storage and access method for logging data are as follows:

[0104] S1: Call the data access interface in the data storage access module. The interface parameters include: global path of the data object D:\2-113.gdsx?type=1&name=AC, starting access position at the 900th sampling point, and access data size at the 701st sampling point, etc.

[0105] S2: Call the data cache management module and use the global path of the data object to obtain the cache object corresponding to the acoustic (AC) logging curve in the key-value pair container;

[0106] S3: Calculate the page cache number of the data to be accessed as 1-3 based on the starting access position and the size of the accessed data. Search in the page cache key-value pair container. Page cache number 1 already exists, while page cache numbers 2 and 3 do not exist.

[0107] S4: Get the attribute of whether page cache 1 is synchronized with file data. If the attribute is false, it means that the data in the page cache is not synchronized with the file data. Execute S6.

[0108] S5: Call the data cache management module to request page caches 2 and 3. Each page cache has a size of 500 sampling points. Store the page number and the corresponding page cache object in the page cache key-value pair container.

[0109] S6: This refers to calling the unified interface module for file storage access, reading file data into page buffers 1-3, reading the 501st-1000th sampling point data of the acoustic wave curve in the file into buffer 1, the 1001st-1500th sampling point data into buffer 2, and the 1501st-2000th sampling point data into buffer 3.

[0110] S7: Get the location of the data to be stored in the page cache: access the 400-500th sample point in cache 1, the 1-500th sample point in cache 2, and the 1-100th sample point in cache 3 in sequence.

[0111] Example 4: When performing real-time data storage, such as Figure 6 As shown, the method for fast storage and access of well logging data is as follows:

[0112] S1: Call the real-time data storage interface in the data storage access module;

[0113] S2: Retrieve the data cache object;

[0114] S3: Determine if real-time data cache exists. If not, execute S4; otherwise, execute S5.

[0115] S4: Request a cache for one page of real-time data;

[0116] S5: Write real-time data to the page cache;

[0117] S6: Determine whether the current real-time data has been written. If not, execute S7; otherwise, end the execution.

[0118] S7: Write the data in the real-time data page cache to a file, clear the cache, and execute S5.

[0119] The real-time data storage interface described in S1 includes real-time data storage interfaces for different data objects. The interface parameters include the global path of the data object, etc. The stored real-time data is written to the end of the corresponding file node by default.

[0120] The process described in S2, which involves retrieving the data cache object, involves calling the data cache management module and using the global path of the data object to retrieve the corresponding data cache object from the key-value pair container.

[0121] The determination of whether a real-time data cache exists, as described in S3, refers to whether the key-value pair container of the page cache contains a special cache with a page index of -1.

[0122] In S4, requesting a page of real-time data cache refers to calling the data cache management module, requesting a page of cache, and storing it in the page cache key-value pair container with an index of -1.

[0123] The description of writing real-time data to the page cache in S5 refers to writing real-time data to the page cache sequentially until the cache is full.

[0124] The determination of whether the current real-time data has been written, as described in S6, refers to whether there is still real-time data that has not been written to the cache when the real-time page cache is full.

[0125] The description in S7 of writing data from the real-time data page cache to a file refers to calling the unified file storage access interface module to store the real-time data page cache data into a file.

[0126] The foregoing has shown and described the basic principles, main features, and advantages of the present invention. It will be apparent to those skilled in the art that the present invention is not limited to the details of the exemplary embodiments described above, and that the invention can be implemented in other specific forms without departing from its spirit or essential characteristics. Therefore, the embodiments should be considered illustrative and non-limiting in all respects. The scope of the invention is defined by the appended claims rather than the foregoing description, and thus all variations falling within the meaning and scope of equivalents of the claims are intended to be included within the present invention. No reference numerals in the claims should be construed as limiting the scope of the claims.

[0127] Furthermore, it should be understood that although this specification describes embodiments, not every embodiment contains only one independent technical solution. This narrative style is merely for clarity. Those skilled in the art should consider the specification as a whole, and the technical solutions in each embodiment can be appropriately combined to form other embodiments that can be understood by those skilled in the art. The above content is only for illustrating the technical concept of the present invention and should not be construed as limiting the scope of protection of the present invention. Any modifications made based on the technical concept proposed in this invention shall fall within the scope of protection of the claims of this invention.

Claims

1. A system for rapid storage and access to well logging data, characterized in that, Includes the following modules: Data storage access module: Receives user storage access requests and sends them to the data cache module; It also includes a data cache management module: This module stores different data objects in the form of key-value pair containers, and uses the global path of the data object as the index of the key-value pair container to facilitate the retrieval of data cache modules for different data objects; This module manages all data caches in a unified manner, and when any data cache module needs to request cache, it calls the data cache management module to allocate cache. Data caching module: Provides data storage and access services for different data objects, calls the unified interface module for storing and accessing well logging data storage format files, and synchronizes the data caching module with the data format in the well logging data storage format files; The data caching module employs different caching strategies depending on the data object: for table, well information, and curve information data, a list approach is used to fully cache all data in the corresponding file node; for well logging curve data, a paginated caching approach is used to cache only a portion of the data in the corresponding file node. File data node storage access interface module: Reads the information header of the corresponding node in the well logging data storage format file through the access request received by the file storage access unified interface module; Unified file storage access interface module: Provides storage access functions for data at different file nodes by calling the storage access interface modules of each data node in the well logging data storage format file.

2. The logging data rapid storage and access system according to claim 1, characterized in that, The well logging data storage format file includes data format file header information, single-well data area file, and multi-well data area file; The single-well data area records the logging curve data, raw logging data, logging information data, logging resource data, logging parameter card data, and logging table data of a single well. Well logging data includes a curve header, depth data, time data, and value data; For curves with equal depth sampling, depth data is constructed in real time through the curve information header; For curves sampled at equal time intervals, time data is constructed in real time through the curve information header; For non-isotropic sampling curves, both depth and time data must exist.

3. A method for rapid storage and access of well logging data, characterized in that, A rapid storage and access system for well logging data according to any one of claims 1 to 2 includes the following steps: S1: Call the interface in the data storage access module to obtain the data cache object; S2: Determine if the data storage access scope is in the cache; S3: If it is in the cache, then determine whether the data in the cache is synchronized with the file; S4: If the data in the cache is synchronized with the file, perform data storage access in the page cache, write the data in the cache to the file after data storage, and end the execution; If the data storage access scope is not in the cache, then request the page cache corresponding to the data storage scope; If the data in the cache is out of sync with the file, then the data in the file is read into the page cache; Determining whether the data storage access scope is in the cache refers to determining the storage access location. ,size Page Size Calculate the range of page cache numbers to be stored. Determine whether the above page number is in the key-value pair container of the page cache; The paginated caching method is as follows: the cache is divided into several file cache pages and one real-time data cache page; The data from a well logging curve node is sequentially mapped to several contiguous file cache pages of the same size; The above page cache is stored in the form of a key-value pair container, with the page number used as the index of the key-value pair container; Each page cache includes attributes such as page number, hit count, last used time, and whether it is synchronized with file data.

4. A method for rapid storage and access of well logging data, characterized in that, A rapid storage and access system for well logging data according to any one of claims 1 to 2, when a user selects to store data in real time, includes the following methods: S1: Call the interface in the data storage access module to obtain the data cache object; S2: And write the real-time data to the real-time page cache; S3: Determine if the real-time data has been written. If the current real-time data has been written, terminate the execution. Before writing real-time data to the page cache, check if a real-time page cache exists. If it does not exist, request a page cache of a fixed size and then write the real-time data to the page cache. If a page cache is detected, the real-time data is written directly to the page cache. If the real-time page cache is full, write the data in the cache to a file, clear the page cache, and write the real-time data to the page cache.

Images