WO2013015795A1

WO2013015795A1 - Data exchange with a mobile docking station

Info

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

Abstract

Data exchange with a mobile docking station. An example includes a docking station, and a plurality of pocket interfaces each configured to hold a field node and automatically offload data from the field node. A communications link communicatively couples the docking station with a physically remote data collection station to transfer the offloaded seismic data to the data collection station.

Description

DATA EXCHANGE WITH A MOBILE DOCKING STATION

BACKGROUND

[0001] 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 station(s), where the data can be further processed.

[0003] 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.

[0004] Seismic sensors may also be irelessly connected (e.g., via a local area network protocol) to the data collection station(s) for offloading seismic data. Wireless seismic sensors may include an 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 collection stations. While different channels can be assigned to individual or groups of seismic sensors to reduce interference during wireless transmissions, there are a limited 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

[0005] The drawings show example embodiments, wherein:

[0006] Figure 1 is an illustration showing deployment of example data acquisition units or field nodes.

[0007] Figure 2 shows an example data exchange system.

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

[0009] Figure 3 shows an example node dock.

[0010] Figure 4 is a high-level view of an example mobile docking station.

[0011] Figure 5 is a schematic diagram of a mobile docking station.

[0012] Figure 6 is a schematic diagram of a mobile docking station connected to data collection station.

[0013] Figure 7 is a flowchart illustrating example operations which may be implemented for data exchange with a mobile docking station.

DETAILED DESCRIPTION

[0014] 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 physically remote locations. These field nodes may be fairly "low-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.

[0015] The use of a large number of field nodes in a distributed environment, and under various and harsh environmental 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 field 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 with bandwidth limitations typical in remote and distributed environments. Offloading large amounts of data (e.g., from a large number of field nodes) can also 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.

[0016] 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.

[0017] Accordingly, the field nodes may be implemented with a data exchange system to transfer large amounts of data from distributed sources to a data collection station. An example data exchange system includes a mobile docking station. A plurality of connection interfaces at the mobile docking station are each configured to physically engage individual field nodes at substantially the same time and automatically establish communication connections with the individual field nodes when the individual field nodes are physically engaged with the connection interface A controller at the connection interfaces to offload monitoring data stored in the individual field nodes. A communications platform operatively associated with the mobile docking station transfers the offloaded monitoring data to a data collection station at a physically remote location from the mobile docking station.

[0018] Before continuing, it is noted that as used herein, the terms "include," "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."

[0019] 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 110 are used to gather seismic data. The seismic data may be obtained as a result of intentionally emitting acoustic signals 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).

[0020] A large number 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 field nodes 110 may be deployed to remote areas and/or geographically distributed over a relatively large 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. [0021] 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.

[0022] Seismic data may be gathered directly and/or indirectly. In an example where the seismic data is gathered directly, 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.

[0023] 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 can be taken directly to the docking station 155, discussed in more detail below.

[0024] 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.

[0025] 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, such 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.

[0026] 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.

[0027] 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 or other portable computing device 140 for one or more functions. And indeed, the portable computing device 140 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 personal 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.

[0028] 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 field 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.

[0029] At least some degree of data processing may be performed in the field at the mobile 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.

[0030] In 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 110. Such processing in the field may enable issues to be addressed and changes or repairs to be made in real-time, or substantially in real-time, before the user 130 returns from the field.

[0031] 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 collection 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 160 while the mobile platform is still 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.

[0032] Before continuing, it is noted that the field 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.

[0033] 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.

[0034] The data exchange system 200 includes a docking station 210. The docking station 210 may be provided on the mobile platform (e.g., as part of the docking station 155 on mobile platform 150 shown in Figure 1 ), and thus is also 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.

[0035] 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 field 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.

[0036] 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 in the pocket 220 even after the user or "handler" lets go of the field node 230. In an example, the field node 230 is physically engaged in the pocket when the handler presses or pushes the field 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.

[0037] The field node 230 may be modular in shape and configured to slidably engage with any of the pockets 220 at the docking station 210. In this way, the pocket 220 enables fast removal and insertion of the field nodes 230 on an ongoing, repeated, and frequent basis. The field node 230 and/or pocket 220 may also 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 still make the correct connections with the docking station 210.

[0038] As discussed above, pads may be provided on the field node 230 to enable communications and/or electrical connections with the docking station 210. Example pads are shown in more detail in Figure 2a, and may include a flat metal pad 231 a on the field node 230 and a corresponding flat metal pad 231 b inside the pocket 220. Flat metal pads 231 a and 231 b 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 example, the flat metal pads 231 a and 231 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.

[0039] In another example, 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.

[0040] With reference again 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 docking 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- field 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.

[0041] 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 231 a 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 less 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.

[0042] In an example, the data interface for the offload process utilizes a near field communication (NFC) radio link. The NFC radio link enables 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.

[0043] In addition, the NFC link also enables 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.

[0044] 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 protocol 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. [0045] 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.

[0046] 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.

[0047] 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.

[0048] 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 physicall engaged in the pocket 220. In an example, the electrical connection may be established using contact pads, such as those shown in Figure 2a.

[0049] The contact pads 232a and 232b used to establish the electrical connection may be different than the pads 231 a and 231b used to establish the communication connection. While the pads 231a and 231 b 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 electric current between the contact pads 232a and 232b without arcing.

[0050] 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.

[0051] However, it may be desirable 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 231 a and 231 b. 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.

[0052J 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 automatically shut off the charging current (e.g., via a power shunt switch 286) if the battery 282 does not need charging or if the battery has reached a charged state.

[0053] Figure 3 shows an example node dock 300. Node dock 300 may be provided as part of the mobile docking station. In the example shown, the node dock 300 may have a height of about 800 mm, a width of about 700 mm, and a length of about 1300 mm. The node dock 300 may include a power supply 310 and/or AC/DC power converter, and a built-in network switch 320 such as an Ethernet switch. In the example shown, the power supply 310 may be a 4kW DC power supply (about 3kW under load), and the network switch 320 may be a 48 port 10/100 Ethernet switch. However, these examples are only illustrative and not intended to be limiting.

[0054] The node dock 300 may also include a plurality of pockets 330. The pockets 330 are configured to receive field nodes 340, e.g., as explained above for the pockets 220 shown in Figures 2 and 2a. Forty-eight pockets 330 are shown in the node dock 300 in Figure 3 for purposes of illustration. However, any number of pockets 330 may be provided in each node dock 300. The node dock 300 is shown having field nodes 340 inserted in the pockets 330. Field node 340a is shown as it may be inserted into (arrow 350a), and withdrawn from (arrow 350b) node pocket 320a.

[0055] Multiple node docks 300 may be used in a mobile docking station, for example, by stacking node docks side by side and/or on top of one another.

[0056] Figure 4 is a high-level view of an example mobile docking station 400. The mobile docking station 400 is shown as it may be implemented in a tractor trailer 401. For purposes of illustration, the mobile docking station 400 is shown having multiple node docks 410, such as the node docks 300 shown in Figure 3.

[0057] The node docks 300 may be connected to an electrical power source 430. A network 420 may couple each of the pockets in each of node docks 410 to a computing system 440 such as an on-board server computer(s) and/or storage system(s). For example, the server computer system 440 may be an on-board rack server system and/or a storage network, such as a random array of independent disks (RAID).

[0058] Suitable backup systems (not shown separately) may also be provided. An environmental control system 450 may also be provided to maintain air conditioning, humidity, and other environmental parameters.

[0059] Figure 5 is a schematic diagram of a mobile docking station 500. The schematic diagram shows communications paths in the mobile docking station, such as between the pockets 510 in the node docks and a multiport switch 520. Multiport switch 520 may be coupled via one or more external switches 530 (e.g., 10GB switches) to the onboard servers and/or storage systems discussed above with reference to Figure 4.

[0060] The schematic diagram shows electrical connections. In an example, the multiport switch 520 is powered by a high voltage power supply 540 such as a 50/60Hz 220VACpower generator. The power supply 540 may also be converted to provide a DC power source 550, such as a 12V, 185A DC power supply with a power factor correction greater than about 0.95 and operating in temperatures as low as 0 to 40 degrees Celsius.

[0061] Figure 6 is a schematic diagram of a mobile docking station 600 connected to a data collection station 610. As discussed above, any suitable communications link can be provided to connect the mobile docking station 600 with the data collection station 610. Examples include, but are not limited to, satellite and/or other remote transmission systems, and moving the mobile platform to a location where a hardwired connection can be established . In any event, the seismic data offloaded from the field nodes can be transferred from the mobile docking station 600 to the data collection station 610.

[0062] The schematic diagram shows a dock group 620 having a plurality of node docks 630. As discussed above, each of the node docks 630 may include a plurality of pockets (e.g., 48 pockets in the example shown in Figure 3) which can be used to offload data from individual field nodes. The offloaded data is then transferred via switch stacks 640a and 640b to the onboard server computer(s) 650 and/or storage system(s) 655. When an uplink is established with the data collection station 610, data may be moved via switches 660 and suitable remote and/or hard-wired transmission system.

[0063] 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.

[0064] Figure 7 is a flowchart illustrating exemplary operations which may be implemented for data exchange with a mobile docking station. Operations 700 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.

[0065] Operation 710 includes establishing a local communications connection with a plurality of field nodes brought to and engaged with the mobile docking station. Operation 720 includes offloading monitoring data stored in the field nodes to the mobile docking station via the communications connection. Operation 730 includes disconnecting the communications connection before returning the field nodes to a remote location from the mobile docking station for continued monitoring. Operation 740 includes transferring the monitoring data from the mobile docking station to a data collection station at a physically remote location from the mobile docking station.

[0066] 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.

[0067] Further operations may include collecting distributed intelligence from all of the field nodes brought to the mobile docking station substantially simultaneously. For example, seismic data from a large number of field nodes distributed over a relatively large area can be collected at the mobile docking station at the same time, limited in time only by the number of node docks at the mobile docking station.

[0068] Further operations may include maintaining a high data collection bandwidth of the data collection station even when offloading data from the plurality of field nodes. For example, converting serial communications for each field node at the pocket into a high-bandwidth, high-speed network protocol such as TCP-IP, enables multiple field nodes to offload data simultaneously or substantially at the same time from a serial data device, while still maintaining network integrity. Thus, large volumes of data may be collected by multiple individual field nodes and transferred to the docking station (using a slower communications connection) at substantially the same time onto a higher speed communications path to handle the accumulating data flow from the multiple individual field nodes. The high data collection bandwidth may be thought of as a "reverse-funnel" approach combining multiple smaller feeders or inputs of data (from the individual field nodes) onto a larger and faster data path for transfer to the data collection station.

[0069] Further operations may include automatically responding to health and status information for the field nodes when the field nodes are brought to the mobile docking station. For example, the docking station may query the field nodes for information, make a determination whether any changes are needed (e.g., firmware upgrades or configuration changes), and then make changes as needed (e.g., uploading self-installing firmware upgrades or making configuration changes).

[0070] Further operations may include substantially simultaneously offloading seismic data on the field nodes to the mobile docking station without communications interference from the plurality of field nodes and without using a multichannel network configuration. For example, the near-field communications protocol described herein may be used to enable a large number of field nodes to communicate wirelessly at the mobile docking station without interfering with the communications of neighboring field nodes during offloading procedures.

[0071] 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 also contemplated.

Claims

1. A data exchange method for a mobile docking station, comprising:

establishing a local communications connection with a plurality of field nodes brought to and engaged with the mobile docking station;

offloading monitoring data stored in the field nodes to the mobile docking station via the communications connection;

disconnecting the communications connection before returning the field nodes to a remote location from the mobile docking station for continued monitoring; and

transferring the monitoring data from the mobile docking station to a data collection station at a physically remote location from the mobile docking station.

2. The method of claim 1 further comprising collecting distributed intelligence from all of the field nodes brought to the mobile docking station substantially simultaneously.

3. The method of claim 1 further comprising maintaining a high data collection bandwidth of the data collection station even when offloading data from the plurality of field nodes.

4. The method of claim 1 further comprising automatically responding to health and status information for the field nodes when the field nodes are brought to the mobile docking station.

5. The method of claim 1 further comprising substantially simultaneously offloading data on the field nodes to the mobile docking station without communications interference from the plurality of field nodes and without using a multichannel network configuration.

6. A data exchange system comprising:

a mobile docking station;

a plurality of connection interfaces at the mobile docking station, the connection interfaces each configured to physically engage individual field nodes at substantially the same time and automatically establish communication connections with the individual field nodes when the individual field nodes are physically engaged with the connection interface;

a controller at the connection interfaces to offload monitoring data stored in the individual field nodes; and

a communications platform operatively associated with the mobile docking station to transfer the offloaded monitoring data to a data collection station at a physically remote location from the mobile docking station.

7. The system of claim 6 wherein the mobile docking station collects distributed intelligence from all of the field nodes brought to the mobile docking station at substantially a same time.

8. The system of claim 6 wherein the serial data communications from each of the plurality of field nodes is converted at the mobile docking station to a high bandwidth data communications platform.

9. The system of claim 6 wherein a high data collection bandwidth is maintained at the data collection station even when offloading data from the plurality of field nodes.

10. The system of claim 6 further comprising a contamination-resistant physical connector for the field nodes to offload data to the mobile docking station.

11. The system of claim 6 further comprising an interference-free communications connection for the field nodes to offload data to the mobile docking station.

12. The system of claim 1 1 wherein the interference-free communications connection is a single channel connection.

13. A seismic data exchange system comprising:

a docking station;

a plurality of pocket interfaces each configured to hold a field node and automatically offload seismic data from the field node at substantially the same time seismic data is being offloaded from other field nodes brought to the docking station; and

a communications link communicatively coupling the docking station with a physically remote data collection station to transfer the offloaded seismic data to the data collection station.

14. The system of claim 13 wherein distributed intelligence is collected from all of the field nodes before transferring the offloaded seismic data to the data collection station.

15. A field node comprising:

a storage medium to store data collected at remote locations from a docking station; and

a communications link communicatively coupling a pocket interface at the docking station, the communications link configured to automatically offload seismic data from the storage medium at substantially the same time seismic data is being offloaded from other field nodes brought to the docking station to transfer the offloaded seismic data to a data collection station.