WO2013015794A1

WO2013015794A1 - Systems and methods of data exchange with field nodes

Info

Publication number: WO2013015794A1
Application number: PCT/US2011/045428
Authority: WO
Inventors: Kevin Swier; Gary LUTNESKY
Original assignee: Hewlett-Packard Development Company, L.P.
Priority date: 2011-07-26
Filing date: 2011-07-26
Publication date: 2013-01-31

Abstract

Systems and methods of data exchange for field nodes. An example method comprises automatically establishing a wireless communications connection with a field node when the field node is engaged with a pocket at a docking station. The method also comprises transferring monitoring data stored in the field node to the docking station via the communications connection.

Description

SYSTEMS AND METHODS OF DATA EXCHANGE WITH FIELD ODES

BACKGROUND

[0001J Acoustic signals propagated into the earth, reflected by various features below the earth's surface, and then recorded as seismic data can be used to generate seismic surveys of the earth's subsurface. This seismic data can be detected and recorded by seismic sensors, and then offloaded for subsequent analysis. Seismic surveys can be used to identify the presence of subsurface formations, fluids, and gases, and therefore have application in a variety of fields, including but not limited to, oil and gas exploration.

0002| Seismic sensors may be deployed to remote locations and distributed over large areas. For example, hundreds and even thousands of seismic sensors may be deployed over an area of several hundred square miles. Various transmission systems are then used to offload seismic data to data collection stations), where the data can be further processed.

£00Q3 Seismic sensors may be physically connected (e.g., via a hard wired connection) to data collection station(s) for offloading seismic data. Hardwiring may be through mechanical connectors on the external housing of the acquisition units. The connector is often subject to harsh environments (including exposure to sand, mud, and water). Therefore the connector is usually sealed in order to maintain the mechanical and electrical integrity of the connection during deployment of the seismic sensors. The seal has to be opened each time data is offloaded from the seismic sensors, and then closed again prior to redeployment of the seismic sensors. This process of removing a cap, connecting a data transfer cable and reconnecting the cap can be tedious work, particularly for a large number of seismic sensors. The connectors can become worn over time and/or may not be properly sealed again prior to redeployment, resulting in damage to the connector and/or the seismic sensor itself.

[00043 Seismic sensors may also be wirelessly connected (e.g., via a local area network protocol) to the data coiiection staiion(s) for offloading seismic data. Wireless seismic sensors may include a on-board transmitter and utilize mid-range or long-range radio wireless protocols {e.g., IEEE 802), depending on the distance from the point of deployment to the data coiiection stations. While different channels can be assigned to individual or groups of seismic sensors to reduce interference during wireless transmissions, there are a iimited number of channels available, which may exceed the number of seismic sensors deployed to an area. Sequential uploading may be used to reduce interference, but this approach can greatly increase the upload time.

BRIEF DESCRIPTION OF THE DRAWINGS

[00053 Th drawings show example embodiments, wherein:

[00083 Figure 1 is an illustration showing deployment of example data acquisitio units or field nodes.

[00073 Figure 2 shows an example data exchange system.

[0008] Figure 2a shows example pads for a data exchange system.

[0009] Figures 3a and 3b illustrate example architectures of a Deployment

Management System (DMS).

[00103 Figure 4 is a flowchart illustrating example operations which may be implemented for data exchange.

DETAILED DESCRIPTION

[00113 Systems and methods are disclosed which are directed generally to the gathering or retrieval of data from a number of data acquisition units or field nodes. In an example, the field nodes may be used for seismic data and thus are deployed in physical ly remote locations. These field nodes ma be fairly ow-tech" components, and are deployed in large numbers, making a cost- effect solution desirable. In addition, the field nodes may be fouled by environmental contaminants such as dirt, mud, and water. OOI23 The ^use °f ^a !^ar9^e number of field nodes in a distributed environment, and under various and harsh environmentai conditions, introduces a number of challenges. For example, it may be difficult to quickly and efficiently offload data and recharge batteries without a reliable data and electrical connection between the fieid node and the data collection station. It may also be difficult to offload data from a large number of field nodes without interference from adjacent nodes in the field. It may also be difficult to transfer large amounts of data wit bandwidth; limitations typical in remote and distributed environments. Offloading large amounts of data (e.g., from a large number of field nodes) can aiso adversely affect performance at the data collection station. In addition, the field nodes may need to be redeployed quickly after offloading the data so that additional data can be gathered without significant interruption,

[00133 The systems and methods disclosed herein implement a near-field wireless connection that can be readily established between a pad (or pads) on the field node, and a pad (or pads) at the data collection station. The pads can be easily wiped clean of dirt, water, and other contamination and thus are much more robust than mechanical interconnects, particularly in harsh environments. The near-field wireless protocol also allows data transfer by numerous field nodes at the same time (or substantially the same time), even when in a relatively close proximity to one another, without interference. That is, a reliable communications connection can be established across a relatively short distance (e.g., in the range of about 0 to 5 cm), which does not interfere with communications that are farther away (e.g., more than 5 cm). As such, data can be transferred reliably, at high speeds, and by many field nodes at about the same time without using a mechanical interconnect,

[001 3 Before continuing, it is noted that as used herein, the terms nclude," "includes," and "including" mean, but are not limited to, "include," "includes," or "including," in addition to the less restrictive definitions of "include at least," "includes at least," or "including at least." In addition, the term "based on" means "based on," in addition to the less restrictive definition of "based at least in part on." [0015] Figure 1 is an illustration showing deployment of example recording nodes 100 and field nodes 110, In the examples described herein, the recording nodes 100 and field nodes 1 0 are used to gather seismic data. The seismic data may be obtained as a result of intentional !y emitting acoustic signais into the earth's subsurface (e.g., for subsurface mapping), and/or may include naturally occurring acoustic signals {e.g., indicating seismic activity such as volcanic activity and tectonic plate movement). However, the recording nodes 100 and field nodes 110 are not limited to use with seismic data, and can be used to monitor any of a wide variety of different types of data (e.g., weather data or traffic data).

[0018] A large numbe of recording nodes 100 and/or field nodes 110 may be deployed, for example, over an area covering hundreds of square miles. The recording nodes 100 and fieid nodes 110 may be deployed to remote areas and/or geographically distributed over a relatively iarge area (e.g. , several hundred square miles). However, the recording nodes 100 and/or field nodes 110 are not limited to any particular type of use, physical location, or geographic distribution.

[0017 The recording nodes 100 and field nodes 110 each include at least a memory or computer-readable storage, and a degree of data processing capability at least sufficient to manage a data connection. The memory or computer-readable storage may be used to store seismic data. Although shown as separate functional units in Figure 1 , it is noted that the functions of the recording nodes 100 and the functions of the field nodes 110, described below, may be combined into a single device. When the functions are combined, the combined device is referred to herein as the field nodes 110 and accordingly the field nodes 110 do not need to be operated in conjunction with separate recording nodes.

[0018J Seismic data may be gathered directly and/or indirectly. In an example where the seismic data is gathered directty, the recording nodes 100 may be configured with both a transmitter (to transmit acoustic signals into the earth's surface), and a receiver (for receiving acoustic signals reflected by features in the earth's subsurface). In another example, the recording nodes 100 may be configured with only a receiver for receiving acoustic signals which were transmitted into the earth's subsurface by another transmitting device and/or are naturally occurring,

[0019] Seismic data which is gathered by separate recording nodes 100 may then be transmitted to the field nodes 110. in the example shown in Figure 1 , recording nodes 100a and 100b gather seismic data and transmit the seismic data to the field node 110a. In another example, the recording nodes 100a and 100b may be taken directly to the docking station 155, discussed in more detail below.

[0020] The field nodes 110 store seismic data until the seismic data can be offloaded to data collection station(s) 120. In an example, the field nodes 110 store seismic data on a secure digital (SD) memory card or similar memory. However, other types of non-transient computer readable storage may also be implemented.

[0021] The data collection station 120 may be an intermediate data collection station or a central data collection station. Data collection stations 120 may be any suitable data processing and analysis facility, suc as a business enterprise, university, and/or government entity. It is noted that the data collection station(s) may be any facility, facilities, or combination of facilities.

[0022] Typically, the data collection station 120 has a greater degree of processing capabilities than can be readily provided in a mobile configuration (e.g., on a laptop or tablet computing device). For example, the data collection station 120 may be a data center, a server farm, or an enterprise computing system (e.g., for a business, university, or government entity). The data collection station can be any suitable computing environment, including but not limited to, enterprise and cloud computing systems.

[0023] It is noted that a user 130 in the field may communicate with the recording nodes 100 and/or field nodes 110, for example, using a laptop, tablet o other portable computing device 140, An example is explained in more detail below with reference to Figures 3a and 3b, And indeed, the portable computing device 40 may be used to offload at least some data from the recording nodes 100 and/or field nodes 110 for various functions. However, the mobile computing device 140 is not what is being referred to herein as the data collection station 120. While persona! desktop computers, laptop computers, and mobile computing devices may be implemented at least to some extent for data processing and/or analysis, the large amount of data collected for processing and analysis is typically handled by the data collection station 120 implemented in a large-scale or server computing environment,

[00243 ^A data exchange system (described in more detail below with reference to Figures 2 and 2a) may be used to offload seismic data from the fieid nodes 110 for transmission to the data collection station 120. In an example, the data exchange system is implemented at a mobile platform 150 which can be taken into the field. The mobile platform 150 includes a docking station 155 which can be used to offload seismic data from the field nodes 110 in the field, for example, without bringing the field nodes 110 back to the data collection station(s) for offloading procedures,

[00253 ^A* ^ieast some degree of data processing may be performed in the fieid at the mobiie platform 150. The extent of data processing may vary at least to some extent on the degree of processing power provided at, or in connection with, the mobile platform 150. For example, it is known that sophisticated server systems can be provided in semi truck trailers.

[00263 to other examples, the mobile platform 150 may include lesser processing capabilities, but sufficient processing capabilities to at least perform data format translations, verify that the seismic data is not corrupted, and/or to determine whether there are any "health" issues with the recording nodes 100 and/or field nodes 1 0. Such processing in the field may enable issues to be addressed and changes or repairs to be made i real-time, or substantially in real-time, before the user 130 returns from the field.

[00273 After offloading seismic data from the field nodes 110, and redeploying the field nodes 110 if desired, the seismic data stored at the mobile platform 150 can be delivered to the data collectio station 120. For example, the stored data can be transmitted from the mobile platform 150 to the data collection station(s) via a communications link 180 while the mobile platform is stii! in the field. Suitable communications links 160 include, but are not limited to, satellite and/or other remote transmission systems. In another example, the mobile platform can be moved to a suitable communications facility, where the seismic data can be transferred from the mobile platform 150 to the data collection station(s), for example using a hardwired connection.

[0028J Before continuing, it is noted that the fieid nodes 110 are not limited to use with any particular implementation of the mobile platform 150 or data collection station 120. The offloading procedure, for transferring seismic data from the field nodes 110 to the docking station 155 can be understood in more detail with reference to the data exchange system described below,

[0029] Figure 2 shows an example data exchange system 200. Figure 2a shows example pads provided in a pocket of the data exchange system shown in Figure 2. As will be understood from the following discussion, the pads enable automatically connecting/disconnecting communications and electrical connections when the field node is engaged/disengaged from the pocket.

[00303 The data exchange system 200 includes a docking station 210. The docking station 210 may be provided on the mobile pfatform (e.g., as part of the docking station 155 on mobile platform 150 shown in Figure 1 ), and thus is aiso referred to herein as a mobile docking station. In an example, the docking station 210 is provided in a truck trailer so that the docking station 210 can be moved from multiple locations corresponding to areas of deployment of the field nodes,

[0031] The docking station 210 has at least one pocket 220, and in some examples, many pockets. The number of pockets will depend at least to some extent on the number of fieid nodes expected to be in use during typical offloading procedures. Each pocket 220 is configured to receive an individual field node 230 (e.g., one of the field nodes 110 shown in Figure 1 ). It is noted that in other examples, each pocket 220 may be configured to receive more than one field node.

[0032] The pocket 220 may be formed as a mating assembly for receiving the field node 230, such that the field node 230 can be inserted into the pocket 220 and is held i the pocket 220 even after the user or "handier" lets go of the field node 230. In an example, the field node 230 is physically engaged in the pocket when the handier presses or pushes the fie!d node 230 into the pocket 220, without any additional securement. However, additional securement may be provided, for example as a strap, locking assembly, or interference fit, based on design considerations and/or user preferences.

[0033] The field node 230 may be modular in shape and configured to siidably engage with any of the pockets 220 at the docking station 210. in this way, the pocket 220 enabies fast removai and insertion of the field nodes 230 on an ongoing, repeated, and frequent basis. The field node 230 and/or pocket 220 may aiso be configured such that the fit is uni-directional. That is, the field node 230 only fits into the pocket 220 in one orientation to ensure correct connections with the docking station 210. The field node 230 and/or pocket 220 may also be configured such that the fit is multi-directional. That is, the field node 230 can fit into the pocket 220 in more than one orientation and stiil make the correct connections with the docking station 210.

[00343 ^As discussed above, pads may be provided on the fseld node 230 to enable communications and/or elect icai connections with the docking station 210. Example pads are shown in more detail in Figur 2a, and may include a fiat metal pad 231a on the field nod 230 and a corresponding flat metal pad 231b inside the pocket 220. Fiat metal pads 231a and 231b can be readily "wiped clean" of any dirt or other debris prior to inserting the field node 230 into the pocket 220. It is noted that in this exampie, the flat metal pads 231a and 23 b do not establish a physical connection, but instead are provided "near" to each other for establishing a short range wireless connection therebetween when the field node 230 is physically engaged in the pocket 220.

[00351 in another exampie, the field nodes 230 do not include exposed pads for wireless communications. In such an example, the wireless communications is between transceivers embedded completely within the field 230 and the and pocket 220. These transceivers are specific antennas for near-field communications, which are optimized for communications at short distances and exhibit poor communications at larger distances by design.

[0036] With reference agai to Figure 2, a wireless connection interface (as indicated by arrow 235} is provided to communicatively couple the field node 230 to electronics in the clocking station 210. in an example, the wireless connection interface may operate a near-wireless communication protocol. The near-wireless communication protocol may be implemented between a near- fie!d transceiver 240 in the field node 230 and a near-field transceiver 245 in the docking station 210. in an example, the near-field transceivers 240 and 245 establish a communication connection at a distance of less than about 200 mm, and in another example, at about 10 mm.

[0037] A data controller 250 in the docking station 210 causes the near-field transceivers to transfer data from the node electronics 260 (e.g., a processor and storage capability in the field node) to the docking station 210. In an example, the data controller 250 automatically activates a communications state when the field node is physically engaged in the pocket. For example, when the communications pads 231a and 231 b shown in Figure 2a within a distance of less than about 200 mm from each other, and in another example, at a distance of iess than about 10mm from each other. In the communications state, data stored in the field node {e.g., monitoring data such as seismic data) is transferred to the mobile docking station. A manual action, such as a user operating a switch, may also be utilized to activate the communications state.

[0038] In an example, the data interface for the offload process utilizes a near field communication (NFC) radio link. The NFC radio link enabies very short range linking that emits a very low radio frequency (RF) power, such that there is little, if any, interference with neighboring nodes in the docking station 210 during the offload process, even though the field nodes are located in other pockets in the docking station which may be very close to one another during the offload process {e.g., within about 200mm of one another). As such, the docking station can have many (e.g., hundreds of) nodes simultaneously or substantially simultaneously off-loading data. The NFC link enables high quantities of data collected over the whole survey to be offloaded in a docking station environment.

[00393 ⁱⁿ addition, the NFC link aiso enabies in-field communication from a node to a portable or handheld device (e.g., computing device 140 shown in Figure 1 ) that can be a two-way data exchange, without using a conventional communications network. As such, the NFC link enables real time data to be sampled while the field nodes are "offline" or disconnected from an inter-node communications network.

[0040] The docking station 210 may also implement a translation module 270. The translation module 270 can be an integrated processor with memory and controller, such as a system on chip (SoC). in an example, the translation module 270 may translate wireless communications from the field node 230 (e.g., wireless serial data protocol) to a higher speed and /or higher bandwidth protocol (e.g., for moving onto storage devices at the mobile platform). The wireless communications may be a serial peripheral interface (SPI) protocol and/or an secure digital input output (SDIO) protocol. The high bandwidth protocol may be an Ethernet protocoi or storage area network protocol for transmission via a network 278 to an on-board storage facility and/or the data collection station. Other protocols are also contemplated as being appropriate for the implementations described herein.

[00413 The pocket electronics may also include a user interface 275. The user interface 275 may be used in conjunction with the data controller 250, for example, to report and/or act on health, status, or other information for the field node 230. The pocket electronics may also include charging capability, for charging a battery 280 in the node 230,

[00423 The user interface 275 may also be used in conjunction with the data controller 250 to transfer health and status information for the field node to the mobile docking station in the communications state. Health and status information may include, but is not limited to_; battery health, storage capacity and firmware version,

[0043] The user interface 275 may also be used in conjunction with the data controller 250 may also program and/or update the field node on an as-needed basis via the communications connection. Programming and/or updates for the field node may include, but are not limited to, scheduling information (e.g., for sampling data or emitting acoustic signals), signal emitting strength, and firmware updates. [0044] An electrical connection may also be established between the docking station 210 and the field node 230 for the charging operations. The electrical connection is established when the field node 230 is physically engaged in the pocket 220. In an example, the electrical connection may be established using contact pads, such as those shown in Figure 2a.

[00451 The contact pads 232a and 232b used to establish the electrical connection may be different than the pads 231a and 231 used to establish the communication connection. While the pads 231a and 231b may not establish physical contact therebetween (e.g., when a wireless communication connection is implemented), actual physical contact is typically needed to establish an electrical connection for passing an eiectric current between the contact pads 232a and 232b without arcing.

[0046] in another example, the contact pads 232a and 232b need not be used, and instead a low frequency radio energy wireless power coupling may be used for establishing an electrical connection. As such, the term "electrical connection" as used herein refers to either a physical connection or a wireless connection.

[00473 However, it may be desirabl to have contact pads 232a and 232b which establish a sufficient electrical connection on contact, without a mechanical interconnect, in addition, the contact pads 232a and 232b are subject the same environmental contaminants as the pads 231a and 231b, Therefore, it may also be desirable to provide contact pads 232a and 232b which can be easily "wiped clean" during use. In an example, the contact pads 232a and 232b are mating leaf springs which are at least somewhat compressed during physical contact, to help ensure a good electrical contact and reducing the possibility of arcing when an electric current is being delivered. Yet, the contact pads 232a and 232b can still be readily cleaned prior to inserting the field node 230 into the pocket 220.

[0048] A charge controller 280 may automatically activate a charging state when the field node 230 is physically engaged in the pocket 220. in the charging state, a battery 282 in the field node 230 may be charged via a direct current (DC) power supply 284 in the docking station 210. The DC power supply may be protected by a fuse or other circuit breaker (not shown). In addition, the charge controller 280 may automatica!!y shut off the charging current (e.g., via a power shunt switch 288) if the battery 282 does not need charging or if the battery has reached a charged state.

[0049] The field node 230 need not always be interfaced at the docking station. In another example, the field nodes may also be interfaced on an individual basis, e.g., during deployment in the field with a Deployment Management System (DMS).

[0050] Figures 3a and 3b illustrate example architectures of a DMS 300. The example DMS 300 may be executed on a handheld device {e.g., a mobile or portable device 140 shown in Figure 1 ) that is capable of executing program code (e.g., software applications). The DMS 300 enables a user to view node health, and perform other functions in the field.

[00513 *^{n an} example, machine readable instructions (such as but not limited to, software or firmware) may be executed to implement the DMS 300. The machine-readable instructions may be stored on a non-transient computer readable medium and are executable by one or more processor to perform the operations described herein. It is noted, however, that the components of the example architecture shown in Figures 3a and 3b are provided only for purposes of illustration of an example operating environment, and are not intended to limit implementation to any particular system.

[0052] The architecture may include self-contained modules. These modules can be integrated within a self- standi g tool, or may be implemented as agents that run on top of an existing program code. In an example, the activation/initialization architecture 300 in Figure 3a is shown including a node power module 310, which enables a user to remotely turn on/off power to a field node. A self-test reporting module 312 is also shown, which includes diagnostics for the field node battery, memory, sensor, radio, and global positioning sensor (GPS). A wireless link signal reporting module 314 may output field node signal strength and signal quaiity. A node identity and location storage module 318 may be used for field node location and related information. A node power mode scheduling module 318 may provide scheduling, command, and history functions. A seismic impulse test viewing and analysis module 320 may provide for calibration and diagnostics. A synch viewing and check module 322 may provide offsets for local dock variations. A GPS module 324 may include positioning data.

[0053] in an example, the operations architecture 350 in Figure 3b is shown including a mapping module 380, including map and schedule information. A quality control module 362 may output field node quality control data. A status viewer 364 may provide a location recorder and status information for individual field nodes. A node error and fault reporting module 366 may output node operating fault information. A command center communicator 368 may provide text input/output. Field node parameters may be viewed and/or changed for individual and/or groups of field nodes using module 370.

[0054] it is noted that the architectures 300 and 350 may be used to retrieve and view information for the field nodes, in addition to upload and program the field nodes.

[00553 Before continuing, it should be noted that the examples described above are provided for purposes of illustration, and are not intended to be limiting. Other devices and/or device configurations may be utilized to carry out the operations described herein.

[0056] Figure 4 is a flowchart illustrating exemplary operations which may be implemented for data exchange. Operations 400 may be embodied as logic instructions on one or more computer-readable medium. When executed on a processor, the logic instructions cause a general purpose computing device to be programmed as a special-purpose machine that implements the described operations. In an exemplary implementation, the components and connections depicted in the figures may be used.

[0057] Operation 410 includes automatically establishing a wireless communications connection with a field node when the field node is engaged with a pocket at the mobile docking station. Operation 420 includes transferring monitoring data stored in the field node to the mobile docking station via the communications connection. Operation 430 includes automatically disconnecting the wireless communications connection when the field node is disengaged from the pocket.

[0058] The operations shown and described herein are provided to illustrate exemplary implementations of data exchange. It is noted that the operations are not limited to the ordering shown. Still other operations may also be implemented.

[00593 Further operations may include collecting distributed intelligence from a plurality of field nodes at substantially a same time without wireless communications interference from nearby field nodes. Further operations may include converting serial data communications from the field node to a high bandwidth protocol at the mobile docking station.

[0060] Further operations may include establishing an electrical connection with the field node at the mobsle docksng station, and charging a battery in the field node via the electrical connection. Establishing the electrical connection with the field node may be substantially simultaneously with establishing the communication s con nection .

[0081] Further operations may include transferring health and status information for the field node to the mobile docksng station via the communications connection. Still further operations may include updating the field node on an as-needed basis via the communications connection.

[00623 It is noted that the examples shown and described are provided for purposes of illustration and are not intended to be limiting. Still other examples are aiso contemplated.

Claims

1. A data exchange method for field nodes, comprising:

automatically establishing a wireless communications connection with a field node when the fieid node is engaged with a pocket at a docking station; transferring monitoring data stored in the fieid node to the docking station via the communications connection; and

automatically disconnecting the wireless communications connection when the fieid node is disengaged from the pocket.

2. The method of ciaim 1 further comprising collecting distributed intelligence from a plurality of field nodes at substantially a same time without wireless communications interference from nearby field nodes.

3. The method of claim 1 further comprising converting serial data communications from the field node to a high bandwidth protoco! at the docking station.

4, The method of claim 1 further comprising;

establishing an electrical connection with the field node at the docking station; and

charging a battery in the field node via the electrical connection,

5. The method of claim 4 wherein establishing the electrical connection with the fieid node is substantially simultaneously with establishing the communications connection.

8. The method of ciaim i further comprising transferring health and status information for the fieid node to the docking station via the communications connection.

7. A data exchange system for field nodes, comprising:

a docking station having a pocket;

a wireless connection interface in the pocket to communicatively couple a modular field node in ihe pocket to the docking station; and

a data controller for the wireless connection interface to automatically activate a communications state when the field node is physically engaged in the pocket, wherein in the communications state, monitoring data stored in the field node is transferred to the docking station.

8. The system of claim 7 further comprising a charge controller to automatically activate a charging state when the field node is physically engaged in the pocket, wherein in ihe charging state, a battery in the field node is charged.

9. The system of claim 7 wherein the wireless connection interface operates a near-wireless communication protocol .

10. The system of claim 7 further comprising pads in the pocket and mating pads on the field node, the pads establishing an electrical connection between the pockei and the field node when the field node is physically engaged in the pocket.

11. The system of claim 7 wherein the data controller transfers health and status information for the field node to the docking station in the communications state,

12. The system of ciaim 7 wherein the data controller updates the field node on an as-needed basis via the communications connection.

13. The system of claim 7 wherein the data controller converts wireless serial data communications from the field node to a high bandwidth protocol at the docking station.

14. A seismic data exchange system comprising;

a mobile docking station having a plurality of pockets configured for use with a plurality of field nodes;

a wireiess communications connection automatically established between a field node and the mobile docking station when the fieid node is engaged with one of the pockets to transfer seismic monitoring data stored in the field node to the mobile docking station; and

wherein the wireless communications connection automatically disconnects whe the field node is disengaged from the pocket.

15. The system of claim 14 further comprising an electrical connection automatically established between the field node and the mobile docking station substantially simultaneously with establishing the communications connection when the field node is engaged with one of the pockets to charge a battery in the field node,

16. A field node comprising:

a wireless connection interface to establish communication with a pocket of a docking station when the field node is in the pocket; and

a data storage to store seismic data, the data storage operativeiy associaied with the wireless connection interface to automatically off!oad the seismic data to the docking station when the field node is physically engaged in the pocket.