Method and system for transmitting seismic data from nodes based on a piggybacking communication

Abstract

The application discloses a node seismic data transmission method and system based on piggyback communication. The method comprises the following steps: a user end generates a piggyback instruction based on the file name of seismic data files needing retransmission and the corresponding node seismic instrument equipment ID and sends the piggyback instruction to a cloud server; the cloud server judges whether the piggyback instruction relative to the node seismic instrument is received in response to a communication link establishment request sent by the node seismic instrument, and if yes, sends the piggyback instruction to the node seismic instrument together with a response message relative to the communication link establishment request; the node seismic instrument judges whether the piggyback instruction is contained in the message sent by the cloud server, and if yes, performs seismic data time-sharing transmission first, and then sends the seismic data files needing retransmission to the cloud server. The system comprises various functional modules for realizing the above steps. According to the application, the problem that the seismic data file transmission is incomplete or lost in the process of existing seismic data file time-sharing transmission can be solved.

Description

TECHNICAL FIELD

[0001] The present application belongs to the technical field of petroleum seismic exploration data acquisition, and more particularly relates to a node seismic data transmission method and system based on piggyback communication. BACKGROUND

[0002] In recent years, with the development of communication technology, seismic exploration acquisition technology has gradually developed from wired node seismographs to wireless node seismographs. At present, the application of 5G communication technology enables wireless node seismographs to transmit the collected seismic data in real time. However, considering the portability of the equipment, the capacity of the power supply battery of the existing wireless node seismograph is limited.

[0003] In order to prolong the working time of the wireless node seismograph as much as possible under the condition of limited power supply battery capacity, the existing wireless node seismograph generally adopts a task-driven communication mechanism to transmit seismic data in time, that is, after collecting seismic data for a period of time, the communication link with the cloud server is started to connect, and the seismic data collected in this period of time is sent to the cloud server, and after the data is sent, the communication connection with the cloud server is disconnected.

[0004] During the time-sharing transmission of the seismic data file, due to unreliable network and other reasons, the problem of incomplete or missing transmission of the seismic data file may occur. For this part of the seismic data file, a retransmission mechanism needs to be started. However, during the period of time when the wireless node seismograph collects seismic data, the cloud server cannot communicate with the wireless node seismograph, so that the retransmission command of the seismic data file cannot be issued. SUMMARY

[0005] The purpose of the present application is to solve the problem of incomplete or missing transmission of the seismic data file in the process of time-sharing transmission of the existing seismic data file.

[0006] In order to achieve the above purpose, the present application provides a node seismic data transmission method and system based on piggyback communication.

[0007] According to the first aspect of the present application, a node seismic data transmission method based on piggyback communication is provided, which comprises the following steps:

[0008] The user end generates a piggyback instruction based on the pre-acquired file name of the seismic data file that needs to be retransmitted and the device ID of the node seismograph corresponding to the seismic data file, and sends the piggyback instruction to the cloud server;

[0009] The cloud server judges whether the piggyback instruction relative to the node seismograph is received in response to the communication link establishment request sent by the node seismograph, and sends the piggyback instruction relative to the node seismograph and the response message relative to the communication link establishment request to the node seismograph if yes.

[0010] The node seismograph judges whether the piggyback instruction is contained in the message sent by the cloud server, and performs predetermined time-sharing transmission of seismic data and sends the seismic data file that needs to be retransmitted by the node seismograph to the cloud server if yes.

[0011] Preferably, before the user terminal generates the piggyback instruction based on the file name of the seismic data file that needs to be retransmitted and the device ID of the node seismograph corresponding to the seismic data file, the method further comprises:

[0012] The user terminal acquires the file name of the seismic data file that needs to be retransmitted and the device ID of the node seismograph corresponding to the seismic data file.

[0013] Preferably, the user terminal acquires the file name of the seismic data file that needs to be retransmitted and the device ID of the node seismograph corresponding to the seismic data file comprises:

[0014] The seismic data file that needs to be retransmitted is determined by comparing the transmission time and size of the seismic data stored on the network storage server;

[0015] The file name of the seismic data file that needs to be retransmitted and the device ID of the node seismograph corresponding to the seismic data file are acquired according to the determined seismic data file that needs to be retransmitted.

[0016] Preferably, the user terminal sends the piggyback instruction to the cloud server in the form of mqtt.

[0017] Preferably, before the cloud server judges whether the piggyback instruction relative to the node seismograph is received in response to the communication link establishment request sent by the node seismograph, the method further comprises:

[0018] The cloud server analyzes the received piggyback instruction to acquire the corresponding node seismograph device ID;

[0019] A mapping table of node seismograph device ID and piggyback instruction truth value is established according to the node seismograph device ID acquired by analysis, and the mapping table is cached in the internal memory of the cloud server.

[0020] Preferably, when the cloud server judges whether the piggyback instruction relative to the node seismograph is received in response to the communication link establishment request sent by the node seismograph, if no, only the response message relative to the communication link establishment request is sent to the node seismograph.

[0021] Preferably, when the node seismograph determines whether the message from the cloud server contains piggyback instructions, if not, only the scheduled seismic data transmission is performed.

[0022] The seismic data transmission specifically refers to that the node seismograph sends the seismic data collected by itself in a scheduled time interval to the cloud server.

[0023] Preferably, the sending of the seismic data file that needs to be retransmitted by the node seismograph to the cloud server specifically refers to:

[0024] First, the file name data packet of the seismic data file that needs to be retransmitted is sent to the cloud server, then the seismic data file that needs to be retransmitted is sent to the cloud server, and finally the file end data packet of the seismic data file that needs to be retransmitted is sent to the cloud server.

[0025] Preferably, after the sending of the seismic data file that needs to be retransmitted by the node seismograph to the cloud server, it further includes:

[0026] The cloud server establishes a new file in the cache according to the received file name data packet;

[0027] The data content of the received seismic data file that needs to be retransmitted is written into the new file;

[0028] In response to the received file end data packet, the new file is flushed to the network storage server, and the communication link between the cloud server and the node seismograph is disconnected.

[0029] According to a second aspect of the present application, a node seismic data transmission system based on piggyback communication is provided, which includes the following functional modules:

[0030] The piggyback instruction generation and sending module is arranged at the user end, and is used to generate a piggyback instruction based on the file name of the seismic data file that needs to be retransmitted and the device ID of the node seismograph corresponding to the seismic data file, and send the piggyback instruction to the cloud server;

[0031] The communication link establishment request response module is arranged at the cloud server, and is used to respond to the communication link establishment request from the node seismograph, determine whether the piggyback instruction relative to the node seismograph is received, and if so, send the piggyback instruction relative to the node seismograph to the node seismograph together with the response message relative to the communication link establishment request;

[0032] The earthquake data transmission control module is arranged in the node seismograph, and is used for judging whether the message sent by the cloud server contains a piggyback instruction, if yes, predetermined earthquake data time-sharing transmission is performed, and then the earthquake data file needing retransmission is sent to the cloud server.

[0033] The present application has the following advantages:

[0034] The node earthquake data transmission method based on piggyback communication of the present application comprises the following steps: first, a user end generates a piggyback instruction based on a file name of a retransmission-required earthquake data file and a device ID of a node seismograph corresponding to the earthquake data file, and sends the piggyback instruction to a cloud server; second, the cloud server judges whether the piggyback instruction relative to the node seismograph is received in response to a communication link establishment request sent by the node seismograph, and if yes, sends the piggyback instruction relative to the node seismograph to the node seismograph together with a response message relative to the communication link establishment request; and finally, the node seismograph judges whether the message sent by the cloud server contains a piggyback instruction, if yes, performs predetermined earthquake data time-sharing transmission first, and then sends the earthquake data file needing retransmission to the cloud server.

[0035] The node earthquake data transmission method based on piggyback communication of the present application comprises the following steps: first, a user end generates a piggyback instruction based on a file name of a retransmission-required earthquake data file and a device ID of a node seismograph corresponding to the earthquake data file, and sends the piggyback instruction to a cloud server; second, the cloud server judges whether the piggyback instruction relative to the node seismograph is received in response to a communication link establishment request sent by the node seismograph, and if yes, sends the piggyback instruction relative to the node seismograph to the node seismograph together with a response message relative to the communication link establishment request; and finally, the node seismograph judges whether the message sent by the cloud server contains a piggyback instruction, if yes, performs predetermined earthquake data time-sharing transmission first, and then sends the earthquake data file needing retransmission to the cloud server.

[0036] The node earthquake data transmission system based on piggyback communication of the present application belongs to the same general inventive concept as the node earthquake data transmission method based on piggyback communication, and thus has the same advantages as the node earthquake data transmission method based on piggyback communication, which will not be described herein again.

[0037] Other features and advantages of the present application will be described in detail in the following specific embodiments. BRIEF DESCRIPTION OF DRAWINGS

[0038] The above and other objects, features and advantages of the present application will become more apparent from the following detailed description when taken in conjunction with the accompanying drawings in which like reference characters refer to like parts throughout the figures, and in which:

[0039] Figure 1 An implementation flowchart of a method for transmitting node seismic data based on a piggyback communication according to Embodiment 1 of the present application is shown. DETAILED DESCRIPTION

[0040] Preferred embodiments of the present application will be described in more detail below. Although the following describes preferred embodiments of the present application, it should be understood that the present application can be implemented in various forms and should not be limited by the embodiments set forth herein. Rather, these embodiments are provided so that the present application will be thorough and complete, and will fully convey the scope of the present application to those skilled in the art.

[0041] Embodiment 1 Figure 1 An implementation flowchart of a method for transmitting node seismic data based on a piggyback communication according to an embodiment of the present application is shown. Referring to Figure 1 , the method for transmitting node seismic data based on a piggyback communication according to an embodiment of the present application includes the following steps:

[0042] Step S100, a user end generates a piggyback instruction based on a pre-acquired file name of a seismic data file that needs to be retransmitted and a device ID of a node seismic instrument corresponding to the seismic data file, and sends the piggyback instruction to a cloud server;

[0043] Step S200, the cloud server judges whether a piggyback instruction relative to the node seismic instrument is received in response to a communication link establishment request sent by the node seismic instrument, and if so, sends the piggyback instruction relative to the node seismic instrument to the node seismic instrument together with a response message relative to the communication link establishment request;

[0044] Step S300, the node seismic instrument judges whether a piggyback instruction is contained in a message sent by the cloud server, and if so, performs a predetermined time-sharing transmission of seismic data first, and then sends a seismic data file that needs to be retransmitted by itself to the cloud server.

[0045] Further, the method for transmitting node seismic data based on a piggyback communication according to an embodiment of the present application, before the step S100 of the user end generating a piggyback instruction based on a pre-acquired file name of a seismic data file that needs to be retransmitted and a device ID of a node seismic instrument corresponding to the seismic data file, further includes:

[0046] The user end acquires a file name of a seismic data file that needs to be retransmitted and a device ID of a node seismic instrument corresponding to the seismic data file.

[0047] Specifically, in the embodiment of the present application, the user terminal acquires the file name of the seismic data file that needs to be retransmitted and the device ID of the node seismic instrument corresponding to the seismic data file, which comprises:

[0048] By comparing the transmission time and size of the seismic data stored on the network storage server, the seismic data file that needs to be retransmitted is determined;

[0049] According to the determined seismic data file that needs to be retransmitted, the file name of the seismic data file and the device ID of the node seismic instrument corresponding to the seismic data file are acquired.

[0050] Further, in step S100 of the embodiment of the present application, the user terminal sends the piggyback instruction to the cloud server by mqtt.

[0051] Further, the node seismic data transmission method based on piggyback communication in the embodiment of the present application, before the cloud server judges whether it has received the piggyback instruction corresponding to the node seismic instrument in response to the communication link establishment request sent by the node seismic instrument in step S200, further comprises:

[0052] The cloud server analyzes the received piggyback instruction to acquire the corresponding node seismic instrument device ID;

[0053] According to the node seismic instrument device ID acquired by analysis, a mapping table of node seismic instrument device ID and piggyback instruction true value is established, and the mapping table is cached in the internal memory of the cloud server.

[0054] Further, in step S200 of the embodiment of the present application, when the cloud server judges whether it has received the piggyback instruction corresponding to the node seismic instrument in response to the communication link establishment request sent by the node seismic instrument, if not, only a response message corresponding to the communication link establishment request is sent to the node seismic instrument.

[0055] Specifically, in the embodiment of the present application, the node seismic instrument initiates a communication link establishment request to the cloud server at a predetermined time interval, and registers the node seismic instrument device ID by heartbeat. The cloud server initiates a response, determines whether the node seismic instrument has seismic data files that need to be retransmitted through the mapping table of node seismic instrument device ID and piggyback instruction true value. If the node seismic instrument has seismic data files that need to be retransmitted, the piggyback instruction is sent to the node seismic instrument together with the response message.

[0056] Further, in step S300 of the embodiment of the present application, when the node seismic instrument judges whether the message sent by the cloud server contains a piggyback instruction, if not, only the predetermined seismic data time-sharing transmission is performed;

[0057] The time division transmission of the seismic data is specifically that the node seismic instrument sends the seismic data collected by itself in a predetermined time interval to the cloud server.

[0058] Further, the sending of the seismic data file needing retransmission by the node seismic instrument to the cloud server in step S300 is specifically:

[0059] The file name data packet of the seismic data file needing retransmission is first sent to the cloud server, then the seismic data file needing retransmission is sent to the cloud server, and finally the file end data packet of the seismic data file needing retransmission is sent to the cloud server.

[0060] Further, the node seismic data transmission method based on the piggyback communication in the embodiment of the application further comprises the following steps after the sending of the seismic data file needing retransmission by the node seismic instrument to the cloud server in step S300:

[0061] The cloud server establishes a new file in the cache according to the received file name data packet;

[0062] The data content of the received seismic data file needing retransmission is written into the new file;

[0063] In response to the received file end data packet, the new file is flushed to the network storage server, and the communication link between the cloud server and the node seismic instrument is disconnected.

[0064] Embodiment 2: Based on the node seismic data transmission method based on the piggyback communication proposed in embodiment 1, the embodiment of the application proposes a node seismic data transmission system based on the piggyback communication.

[0065] The node seismic data transmission system based on the piggyback communication in the embodiment of the application comprises the following functional modules:

[0066] The piggyback instruction generation and sending module is arranged at the user end, and is used for generating a piggyback instruction based on the pre-acquired file name of the seismic data file needing retransmission and the device ID of the node seismic instrument corresponding to the seismic data file, and sending the piggyback instruction to the cloud server;

[0067] The communication link establishment request response module is arranged at the cloud server, and is used for responding to the communication link establishment request sent by the node seismic instrument, judging whether the piggyback instruction relative to the node seismic instrument is received, and if so, sending the piggyback instruction relative to the node seismic instrument and the response message relative to the communication link establishment request to the node seismic instrument;

[0068] The seismic data transmission control module is arranged in the node seismograph, and is used for judging whether the message sent by the cloud server contains a piggyback instruction, if yes, predetermined seismic data time-sharing transmission is performed, and then the seismic data file needing retransmission is sent to the cloud server.

[0069] The above has described the embodiments of the present application, the above description is exemplary, not exhaustive, and is not limited to the disclosed embodiments. Many modifications and changes are obvious to those skilled in the art without departing from the scope and spirit of the described embodiments.

Claims

1. A node seismic data transmission method based on piggyback communication, characterized in that, include: The user terminal generates a piggyback instruction based on the filename of the pre-acquired seismic data file that needs to be retransmitted and the device ID of the node seismograph corresponding to the seismic data file, and sends the piggyback instruction to the cloud server. In response to the communication link establishment request sent by the node seismograph, the cloud server determines whether it has received a piggyback instruction relative to the node seismograph. If so, it sends the piggyback instruction relative to the node seismograph along with a response message to the communication link establishment request to the node seismograph. The node seismograph determines whether the message sent by the cloud server contains a piggyback instruction. If so, it first performs the predetermined time-sharing transmission of seismic data, and then sends the seismic data file that it needs to retransmit to the cloud server. Before the user terminal generates the piggyback instruction based on the filename of the pre-acquired seismic data file that needs to be retransmitted and the device ID of the node seismograph corresponding to the seismic data file, the following steps are also included: The user client obtains the filename of the seismic data file that needs to be retransmitted and the device ID of the node seismograph corresponding to the seismic data file. The process of obtaining the filename of the seismic data file to be retransmitted and the device ID of the corresponding node seismograph on the user terminal includes: By comparing the transmission time and size of the earthquake data stored on the network storage server, the earthquake data files that need to be retransmitted are determined. Obtain the filename of the earthquake data file that needs to be retransmitted and the device ID of the corresponding node seismograph based on the identified earthquake data file. Before the cloud server responds to the communication link establishment request sent by the node seismograph and determines whether it has received a piggyback command relative to that node seismograph, the process further includes: The cloud server parses the received piggyback instructions and obtains the corresponding node seismograph device ID; Based on the node seismograph device ID obtained from parsing, a mapping table between the node seismograph device ID and the piggyback command truth value is established, and this mapping table is cached in its own memory.

2. The node seismic data transmission method based on piggyback communication according to claim 1, characterized in that, The user terminal sends the piggyback command to the cloud server via MQTT.

3. The node seismic data transmission method based on piggyback communication according to claim 1, characterized in that, When the cloud server responds to the communication link establishment request sent by the node seismograph and determines whether it has received a piggyback instruction relative to the node seismograph, if not, it only sends a response message to the communication link establishment request to the node seismograph.

4. The node seismic data transmission method based on piggyback communication according to claim 3, characterized in that, When the node seismograph determines whether the message sent by the cloud server contains a piggyback instruction, if not, only the predetermined time-sharing transmission of seismic data is performed. The time-division transmission of earthquake data specifically refers to the node seismograph sending the earthquake data it collects within a predetermined time interval to the cloud server.

5. The node seismic data transmission method based on piggyback communication according to claim 4, characterized in that, The specific steps of sending the seismic data files that need to be retransmitted to the cloud server are as follows: First, the filename data packet of the earthquake data file that needs to be retransmitted is sent to the cloud server. Then, the earthquake data file that needs to be retransmitted is sent to the cloud server. Finally, the file end data packet of the earthquake data file that needs to be retransmitted is sent to the cloud server.

6. The node seismic data transmission method based on piggyback communication according to claim 5, characterized in that, After sending the earthquake data files that need to be retransmitted to the cloud server, the process also includes: The cloud server creates a new file in its cache based on the received filename data packet; Write the data content of the received seismic data file that needs to be retransmitted into the new file; In response to the received file end data packet, the new file is refreshed to the network storage server, and the communication link between itself and the node seismograph is disconnected.

7. A node seismic data transmission system based on piggyback communication, characterized in that, include: The piggyback instruction generation and sending module is set on the user end. It is used to generate piggyback instructions based on the file name of the pre-acquired seismic data file that needs to be retransmitted and the device ID of the node seismograph corresponding to the seismic data file, and send the piggyback instructions to the cloud server. The communication link establishment request and response module is set on the cloud server. It is used to respond to the communication link establishment request sent by the node seismograph, determine whether a piggyback instruction relative to the node seismograph is received, and if so, send the piggyback instruction relative to the node seismograph together with the response message relative to the communication link establishment request to the node seismograph. An earthquake data transmission control module, installed on the node seismograph, is used to determine whether the message sent by the cloud server contains a piggyback instruction. If so, the predetermined time-sharing transmission of earthquake data is performed first, and then the earthquake data file that needs to be retransmitted is sent to the cloud server. Before the user terminal generates the piggyback instruction based on the filename of the pre-acquired seismic data file that needs to be retransmitted and the device ID of the node seismograph corresponding to the seismic data file, the following steps are also included: The user client obtains the filename of the seismic data file that needs to be retransmitted and the device ID of the node seismograph corresponding to the seismic data file. The process of obtaining the filename of the seismic data file to be retransmitted and the device ID of the corresponding node seismograph on the user terminal includes: By comparing the transmission time and size of the earthquake data stored on the network storage server, the earthquake data files that need to be retransmitted are determined. Obtain the filename of the earthquake data file that needs to be retransmitted and the device ID of the corresponding node seismograph based on the identified earthquake data file. Before the cloud server responds to the communication link establishment request sent by the node seismograph and determines whether it has received a piggyback command relative to that node seismograph, the process further includes: The cloud server parses the received piggyback instructions and obtains the corresponding node seismograph device ID; Based on the node seismograph device ID obtained from parsing, a mapping table between the node seismograph device ID and the piggyback command truth value is established, and this mapping table is cached in its own memory.

Images