US20070201362A1 - Increasing Bandwidth in a Downhole Network - Google Patents
Increasing Bandwidth in a Downhole Network Download PDFInfo
- Publication number
- US20070201362A1 US20070201362A1 US11/674,864 US67486407A US2007201362A1 US 20070201362 A1 US20070201362 A1 US 20070201362A1 US 67486407 A US67486407 A US 67486407A US 2007201362 A1 US2007201362 A1 US 2007201362A1
- Authority
- US
- United States
- Prior art keywords
- node
- data
- network
- encapsulated
- frame
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
- 238000000034 method Methods 0.000 claims abstract description 23
- 230000006854 communication Effects 0.000 claims description 44
- 238000004891 communication Methods 0.000 claims description 44
- 230000005540 biological transmission Effects 0.000 claims description 23
- 238000012795 verification Methods 0.000 claims description 9
- 230000004044 response Effects 0.000 claims description 6
- 238000003860 storage Methods 0.000 claims description 3
- 238000013475 authorization Methods 0.000 claims 2
- 230000000737 periodic effect Effects 0.000 claims 1
- 238000005553 drilling Methods 0.000 description 15
- 238000013524 data verification Methods 0.000 description 5
- 238000012545 processing Methods 0.000 description 5
- 230000009471 action Effects 0.000 description 4
- 238000010586 diagram Methods 0.000 description 4
- 230000006870 function Effects 0.000 description 3
- 230000006855 networking Effects 0.000 description 3
- 230000006978 adaptation Effects 0.000 description 2
- 230000007175 bidirectional communication Effects 0.000 description 2
- 230000015572 biosynthetic process Effects 0.000 description 2
- 238000001514 detection method Methods 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 239000012530 fluid Substances 0.000 description 2
- 238000005755 formation reaction Methods 0.000 description 2
- 238000003780 insertion Methods 0.000 description 2
- 230000037431 insertion Effects 0.000 description 2
- 230000002093 peripheral effect Effects 0.000 description 2
- 238000011084 recovery Methods 0.000 description 2
- 230000007704 transition Effects 0.000 description 2
- 206010009944 Colon cancer Diseases 0.000 description 1
- 238000013459 approach Methods 0.000 description 1
- 230000004888 barrier function Effects 0.000 description 1
- 238000004364 calculation method Methods 0.000 description 1
- 238000012512 characterization method Methods 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 238000005260 corrosion Methods 0.000 description 1
- 230000007797 corrosion Effects 0.000 description 1
- 238000005520 cutting process Methods 0.000 description 1
- 125000004122 cyclic group Chemical group 0.000 description 1
- 230000003247 decreasing effect Effects 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000003628 erosive effect Effects 0.000 description 1
- 230000014509 gene expression Effects 0.000 description 1
- 230000003116 impacting effect Effects 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 239000003607 modifier Substances 0.000 description 1
- 238000005457 optimization Methods 0.000 description 1
- 230000008569 process Effects 0.000 description 1
- 230000003362 replicative effect Effects 0.000 description 1
- 238000000926 separation method Methods 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L12/00—Data switching networks
- H04L12/28—Data switching networks characterised by path configuration, e.g. LAN [Local Area Networks] or WAN [Wide Area Networks]
- H04L12/40—Bus networks
- H04L12/407—Bus networks with decentralised control
- H04L12/417—Bus networks with decentralised control with deterministic access, e.g. token passing
-
- E—FIXED CONSTRUCTIONS
- E21—EARTH DRILLING; MINING
- E21B—EARTH DRILLING, e.g. DEEP DRILLING; OBTAINING OIL, GAS, WATER, SOLUBLE OR MELTABLE MATERIALS OR A SLURRY OF MINERALS FROM WELLS
- E21B47/00—Survey of boreholes or wells
- E21B47/12—Means for transmitting measuring-signals or control signals from the well to the surface, or from the surface to the well, e.g. for logging while drilling
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/08—Configuration management of networks or network elements
- H04L41/0803—Configuration setting
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/12—Discovery or management of network topologies
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L49/00—Packet switching elements
- H04L49/90—Buffering arrangements
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
Definitions
- Downhole tool string configurations often incorporate multiple downhole drilling and exploration devices for reporting temperature, pressure, inclination, salinity, and other factors at or near real-time to the surface.
- FIG. 1 illustrates a block diagram of a network node data communication arrangement in accordance with various embodiments of the present invention
- FIG. 6 illustrates a flowchart view of a portion of the operations of a destination network node in accordance with various embodiments.
- Embodiments provide methods to reduce time, power, size, and computational cycles required for data communication and thereby increase available bandwidth between network nodes or access points or physical mediums on a network. As repeat latency in the network nodes is decreased available bandwidth is increased.
- a ‘token protocol’ based approach is presented, where status from attached and active node may be reported and recorded in a topology without fundamentally impacting the underlying frameworks being used by the network and enabling optimizations in addressing and delivering data being transmitted.
- error checking may also be performed by the network nodes at the NET layer, instead of or in addition to the lower layers, such as the MAC layer. More specifically, in various embodiments, each network node may avoid checking destination addresses for data at the MAC layer and further avoid performing error checking on the body of the data at the MAC layer.
- the downhole network 100 includes a predecessor node 110 , a network node 120 , and a successor node 130 .
- the network node 120 receives and/or transmits data 150 in both directions in the downhole network 100 .
- Data 150 may also be generated by the network node 120 for transmission to at least one of the other nodes, selected from the predecessor node 110 and the successor node 130 .
- data 150 is received from other network nodes physically positioned above and/or below the network node 120 and is then transmitted to other network nodes in the downhole network 100 .
- the network node 120 receives data 150 , from an immediately coupled predecessor node 110 and transmits the data 150 to an immediately coupled successor node 130 .
- the network node 120 will transmit received data 150 to the other immediately coupled nodes, such as the successor node 130 or the predecessor node 1 10 .
- an orphan node 140 in the downhole drilling string will transition to become an active member of the downhole network 100 .
- the data 150 is organized and/or encapsulated in at least one frame 160 , at least one datagram 170 , and may also include at least one packet 180 .
- Each frame may include frame header information and/or a frame payload.
- the frame payload includes at least one datagram 170 .
- at least one datagram 170 is encapsulated in a single physical (PHY) layer frame 160 .
- the network node 120 is configured to perform error checking of the data 150 .
- each packet 180 is configured to individually provide error checking, independent of the datagram 170 and/or the frame 160 .
- the data verification information necessary to perform the error checking is provided for at least one of the packet header information and the packet payload containing the encapsulated data.
- the data 210 is organized and/or encapsulated in at least one PHY frame 220 , at least one MAC datagram 230 , and may also include at least one NET packet 240 .
- each NET packet 240 a includes NET packet header information 250 and a NET packet payload 245 .
- the NET packet header information 250 may include a destination node identifier 251 , destination port information 253 , a source node identifier 255 , source port information 257 , and packet length information 259 .
- the NET packet payload 245 generally includes at least a portion of the encapsulated data 210 .
- the NET packet 240 a is configured to individually provide error checking and/or data verification for at least one of the NET packet header information 250 and the NET packet payload 245 , independent of the MAC datagram 230 and/or the PHY frame 220 .
- one embodiment determines packet validity based on hierarchical error checking and/or data verification of PHY frame header information, MAC datagram header information, and NET packet header information followed by error checking and/or data verification of the NET packet payload.
- a unique distance indicator such as a hop count 270
- the hop count 270 in a downhole network 100 is unique for each node, it may be used to identify the node and also to provide a relative distance of transmitting node that originally generated the packet from the receiving node.
- a modified NET layer packet 240 b is generated from the Net packet 240 a through data manipulation to remove naturally occurring data that also matches the unique identifier.
- One technique of data manipulation includes bit and/or byte stuffing. Once a value is chosen for the identifier, the other normally occurring instances of the identifier are removed and replaced by a replacement indicator to generate a stuffed packet 275 .
- the stuffed packet 275 may be unstuffed back to the original Net packet 240 a by removing the replacement indicators and restoring the original values.
- the network node 300 is coupled to a transmission segment 350 and includes an application layer 310 , network layer 320 , media access layer 330 , and physical layer 340 .
- NET layer parsing and resynchronization which enables each of the network nodes (e.g., 300 a, 300 b, and 300 c ) to recover NET layer packets 370 from a PHY frame 390 and/or a MAC datagram 380 even in some cases after data corruption has occurred within a portion of the PHY frame 390 . More specifically, data recovery may be accomplished by parsing packets for individual links at the NET layer 320 .
- the NET layer packet 370 is similar to the MAC layer datagram 380 in that both may include a header and a payload.
- a cyclic redundancy check is associated with each NET layer packet 370 , so that a corrupted PHY frame 390 and/or a MAC datagram 380 may still include some recoverable NET layer packets 370 .
- a CRC is often computed and appended by a transmitting node to a NET layer packet 370 before transmission or storage, and verified afterwards by the recipient node to confirm that no changes occurred in transit.
- CRCs are provided for both the header and the payload of NET layer packets 370 , where the MAC layer datagram 380 and PHY frame 390 only have a CRC for each respective header portion.
- the header for the NET layer 320 provides addressing and other information about how to handle the data in the NET payload portion of the NET layer packet 370 .
- header portion errors in either a MAC layer datagram 380 and/or a PHY frame 390 are recoverable, so that only detection of a CRC error in a NET layer packet 370 will result in the packet being thrown out.
- the network architecture differs from other networks in that various embodiments perform error checking using a CRC at the NET layer 320 .
- this configuration may allow corrupted packets to pass through the PHY layer 340 and MAC layers 330 , which allows for potential recovery of data in corrupted MAC layer datagrams 380 and/or a PHY frames 390 thereby saving bandwidth by reducing retransmission and increasing the overall speed of the network.
- NET layer packets 370 are exchanged between the NET layer 320 and the MAC layer 330 a CRC is inserted at the end of the header and the payload.
- the CRC is checked to ensure the data has not been corrupted.
- NET layer packets 370 with a bad CRC are thrown out.
- error checking is performed by a NET layer CRC device.
- resynchronization of the parsing at the NET layer 320 enables the system to recover uncorrupted NET layer packets 370 .
- resynchronization may be accomplished by detecting a unique identifier, such as a Packet Synchronization Sequence (PSS), at the start of each NET layer packet 370 .
- PSS Packet Synchronization Sequence
- Other unique identifiers may also be provided between each MAC layer datagram 380 and/or PHY frame 390 .
- the unique identifier is generated through data manipulation to remove naturally occurring data that also matches the unique identifier.
- One technique of data manipulation includes bit and/or byte stuffing each NET layer packet 370 .
- a replacement indicator is removed and the original value is restored.
- an error e.g., CRC
- scanning for the unique identifier provides various possibilities. A bit sequence matching the unique identifier will either identify the start of the next NET layer packet 370 or a corrupted value in the data stream, calculation of the CRC will determine which case is present. In this manner, the receiving node may resynchronize parsing of the NET layer 320 despite the presence of errors and/or data corruption.
- Zero-bit insertion a particular type of bit stuffing, is used to ensure that a PSS doesn't incidentally appear in the contents of the PHY frame 390 , MAC layer datagram 380 , and/or NET layer packet 370 .
- any naturally occurring sequence needs to be removed from the data. For example, if “01111110” was selected as the PSS, the data would need to be altered to ensure that a sequence of 6 consecutive “1” bits are not present in the frame data so as to avoid possible confusion for the PSS.
- zero-bit insertion is used to prevent such a sequence from occurring.
- the receiver node finds “0111111” two possible outcomes may occur. To determine which, the next bit is checked. If the bit is a “0” (i.e. “01111110”) a valid PSS is assumed to have been received. If the bit is another “1” (i.e. “01111111”) then some corruption must have occurred during transmission as that data sequence cannot have been transmitted according to the selected bit sequence for the PSS. In the described example a “0” bit would have been inserted after the fifth “1” bit. Should corruption during transmission result in the PSS being received as part of the data, it is more than likely that the failed CRC would mean that both packets may be suspect to data corruption.
- the illustrated communication module 410 may be connected to the network (see e.g., network 510 in FIG. 5 ) in at least two directions via transmission segments (see e.g., transmission segments 350 in FIG. 3 and/or integrated transmission drill pipe 570 in FIG. 5 ). However, in alternate configurations the communication module 410 may only be connected to the network 510 in one direction.
- the communication module 410 may modulate digital bits on an analog signal to transmit data packets from the network node 400 on the network 510 and demodulates analog signals received from the network 510 into digital data packets.
- the communication module 410 may include a storage medium 470 to temporarily store data in conjunction with transmission.
- a network node 400 may also employ a timing device to calculate whether time-out thresholds have been reached.
- the timing device may include multiple timers individually assigned to each communication interface 420 or to the communication module 410 in general.
- a downhole network node 400 includes a suitable portable power source 480 . Often the downhole network node 400 will need to be self-reliant on multiple battery packs 490 for power requirements. In one embodiment some of the battery packs 490 may be allocated to individual components of the downhole network node 400 based in part on the function provided by the component requesting power. For example, a portion of the battery packs 490 could be dedicated to transmitting received packets (e.g., 410 and 470 ) to the next node. Another portion could be dedicated to maintaining the local processing 440 and related components (e.g., 430 , 450 , and 460 ). In one embodiment, an attached tool may either draw power from the node or provide a source to recharge the batteries.
- each intermediate node may become the bottom node 550 when no data and/or token are received from a successor immediately coupled node for a designated time period based in part on the number of nodes in the downhole network 510 .
- the top node 520 is configured to selectively generate another down-token even if the up-token is not received within a designated time period.
- the designated time period is often based in part on the number of known active nodes in the downhole network.
- the network may employ multiple sub-networks to divide the network 510 and continue data communication.
- the illustrated network 510 may be divided into two sub-networks, the portion of the network 510 in a bottom hole assembly 580 and the top portion of the drill string 560 associated with a sub-network 585 .
- an entire sub-network e.g. all the nodes of network 510 , may transition to an orphan operational status to conserve power or preserve data through active manipulation of timing devices associated with the end node of the sub-network.
- portions of the operations to be performed by network devices may constitute state machines or computer programs made up of computer-executable instructions. Describing portions of the operations by reference to a flowchart enables one skilled in the art to develop programs including instructions to carry out the illustrated methods on suitably configured network devices (e.g., a processor of the network device executing instructions from a computer-accessible media).
- network devices e.g., a processor of the network device executing instructions from a computer-accessible media.
- the computer-executable instructions may be written in a computer programming language or may be embodied in firmware logic. If written in a programming language conforming to a recognized standard, such instructions can be executed on a variety of hardware platforms and for interface to a variety of operating systems.
- the present invention is not described with reference to any particular programming language. It will be appreciated that a variety of programming languages may be used to implement the teachings of the embodiments as described herein.
- the network node operating as a potential destination node 600 receives data in block 610 .
- the received data is modified in block 620 to include relative distance from source node updated by the network node operating as a potential destination node 600 .
- the data is encapsulated in at least one frame having at least one datagram having at least one packet.
- the potential destination node 600 begins to transmit the modified received data in block 630 . In one embodiment, transmission of the frame to the next node may begin as soon as the header is modified by the potential destination node 600 .
- the network node operating as a potential destination node 600 determines the desired destination of data in block 640 .
- each frame is parsed into at least one datagram, and each datagram is parsed into at least one packet of the received data in block 650 .
- the received data is verified in block 660 .
- the packet having packet header information and a packet payload also includes data quality information to verify the received data.
- the data quality information may be associated, individually or collectively, with the packet header information and/or the packet payload.
- the destination identified in the packet header information is verified first by the network node operating as a destination node 600 in block 640 and if the current node is a valid destination, the contents of the packet payload is subsequently verified in block 660 .
- both the packet header information and the packet payload could be verified together.
- the packet data quality information is independent of any data quality verification provided by encapsulated datagram header information and/or frame header information. This separation allows the network node operating as a potential destination node 600 to selectively ignore data errors in the datagram header information and/or the frame header information, if recoverable data is available in the packets associated with the corrupted frame and/or datagram.
- the network node operating as a source node 700 broadcasts a request for status information to other active nodes on the network.
- the network node operating as a source node 700 is a server node and is positioned at the top of the well/downhole network.
- the request includes use of a status token to request responses from attached nodes.
- the information is used to maintain a corresponding network topology table in block 730 .
- the topology table may include a short network identifier (NID) for local communication in the downhole network, a longer global identifier (GUID) for addressing the node from outside the downhole network, and a unique relative distance between the source node 700 and each node.
- the source node 700 verifies the local identification in block 740 , the relative distance in block 750 , and the global identification in block 780 .
- the relative distance such as a hop counts and/or timestamps, may be used as a unique reference for each node.
- the NID is a unique number that identifies the node on the downhole network and may be used for addressing the link from within the network.
- the GUID is a larger unique number than the NID and identifies the node outside of the downhole network.
- a top-hole interface (THI) associated with the source node 700 maintains a topology table to map each node's GUID to the node's NID.
- the topology table may update the relative position of nodes based on the received responses to the information request.
- the source node 700 Upon detecting topology changes in block 770 , the source node 700 periodically generates and distributes the detected changes in blocks 780 and 790 to attached software components outside of the downhole network.
- a message or command may be sent from outside to a node of the downhole network via the THI.
- the THI translates the GUID into the respective node's NID and the command into a port number and payload, and passes the packet(s) down the downhole network.
- the port numbers may specify a specific function to be performed using the information in the payload.
- Each device above the NET layer recognizes port numbers that correspond to functions performed by the device. These devices typically only use packets with recognizable port numbers and ignore others.
Abstract
Description
- This application is a non-provisional application of provisional application 60/766,875, filed Feb. 16, 2006, entitled “Physically Segmented Logical Token Network” and provisional application 60/775,152, filed Feb. 21, 2006, entitled “Node Discovery in Physically Segmented Logical Token Network”, and claims priority from both provisional applications. Both of the above referenced provisional patent applications are hereby incorporated by reference herein for all they disclose.
- 1. Field of the Invention
- Embodiments of the present invention relate to the fields of data processing and data communication. More specifically, embodiments of the present invention relate to methods and apparatus for increasing data communication bandwidth in a downhole networking environment.
- 2. Description of the Related Art
- Advances in data processing and data communication technologies have led to the development of a wide variety of data communication arrangements, including but not limited to various on-chip, on-board and system buses, as well as local and wide area networks. These data communication arrangements are deployed in a wide range of applications, including but not limited data communications in harsh environments, such as oil and gas exploration.
- As exploration and drilling technology matures, the need to accurately communicate data with components located in a downhole tool string is vital to continued success in the exploration and production of oil, gas, and geothermal wells. Downhole tool string configurations often incorporate multiple downhole drilling and exploration devices for reporting temperature, pressure, inclination, salinity, and other factors at or near real-time to the surface.
- Due to the cost of replicating the transmission segments and the difficulty in transmitting data across the barriers, the downhole network is typically limited to only a single physical cable or communication channel, thereby limiting bandwidth. Moreover, the communication channel must be durable to withstand the extreme conditions in a downhole network.
- With respect to power resources, each network node is reliant on downhole generators and other on-board power reserves, which often may not be recharged until the node is physically removed from the downhole environment. These power reserves are gradually depleted with every transmission generated or relayed by the network node. Each data transmission between network nodes typically passes through several intervening drill pipes linked in the drill string by transmission segments and uses both bandwidth and power before reaching their destination.
- Unfortunately, networks associated with the downhole tool string often have unreliable connections along with the limited bandwidth and restricted power resources. A variety of factors including formation fluids, drilling mud, stress corrosion, and erosion from cuttings may contribute to the unreliability of drill string connections. As a result of these and other factors there is likelihood that various errors or data corruption may be introduced into the data or prevent/delay delivery of the data. Moreover, a network will often organize transmitted data in a manner that enables delivery to each network node, such as physical (PHY) layer frames and/or a media access layer (MAC) layer datagrams. Due to the previously identified data corruption, the PHY layer frames and/or the MAC layer datagrams commonly undergo data verification including among other things error-checking to identify corrupt data. Unfortunately, PHY frames and MAC datagrams with errors are entirely discarded by the traditional network protocols and devices, which in the downhole environment is an extremely costly result.
- Accordingly, the corrosive and mechanically violent nature of a downhole drilling environment, combined with the limited ability to communicate with or to deliver power to network nodes at the bottom of the drill string are factors that make the task of providing a commercially acceptable downhole network for bidirectional communication between the surface and the components in the drill string difficult for the industry to overcome.
- The present invention will be described by way of exemplary embodiments, but not limitations, illustrated in the accompanying drawings in which like references denote similar elements, and in which:
-
FIG. 1 illustrates a block diagram of a network node data communication arrangement in accordance with various embodiments of the present invention; -
FIG. 2 illustrates a block diagram of a data structure, in accordance with various embodiments of the present invention; -
FIG. 3 illustrates a block diagram of a source node and a destination node data communication arrangement in accordance with various embodiments of the present invention; -
FIG. 4 illustrates a network node suitable for practicing various embodiments of the present invention as presented inFIG. 1 and inFIG. 5 in further detail, in accordance with various embodiments; -
FIG. 5 illustrates a downhole networking environment suitable for practicing various embodiments of the present invention; -
FIG. 6 illustrates a flowchart view of a portion of the operations of a destination network node in accordance with various embodiments; and -
FIG. 7 illustrates a flowchart view of a portion of the operations of a source network node in accordance with various embodiments. - Various embodiments, described below, have been developed in response to the current state of the art and, in particular, in response to the previously identified problems and needs of downhole networks for bidirectional communication between the surface and the components in the drill string that have not been fully or completely solved by currently available systems and communication protocols for downhole networks.
- Embodiments provide methods to reduce time, power, size, and computational cycles required for data communication and thereby increase available bandwidth between network nodes or access points or physical mediums on a network. As repeat latency in the network nodes is decreased available bandwidth is increased.
- In at least one embodiment, a ‘token protocol’ based approach is presented, where status from attached and active node may be reported and recorded in a topology without fundamentally impacting the underlying frameworks being used by the network and enabling optimizations in addressing and delivering data being transmitted. Moreover, as transmitted data is received by all nodes in the network, error checking may also be performed by the network nodes at the NET layer, instead of or in addition to the lower layers, such as the MAC layer. More specifically, in various embodiments, each network node may avoid checking destination addresses for data at the MAC layer and further avoid performing error checking on the body of the data at the MAC layer.
- In the following detailed description, reference is made to the accompanying drawings which form a part hereof wherein like numerals designate like parts throughout, and in which are shown, by way of illustration, specific embodiments in which the invention may be practiced. It is to be understood that other embodiments may be utilized and structural or logical changes may be made without departing from the scope of the present invention. Therefore, the following detailed description is not to be taken in a limiting sense, and the scope of the present invention is defined by the appended claims and their equivalents.
- Reference in the specification to “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with the embodiment is included in at least one embodiment of the invention. The appearances of the phrase “in one embodiment” in various places in the specification do not necessarily all refer to the same embodiment, but it may. The phrase “A/B” means “A or B”. The phrase “A and/or B” means “(A), (B), or (A and B)”. The phrase “at least one of A, B, and C” means “(A), (B), (C), (A and B), (A and C), (B and C) or (A, B and C)”. The phrase “(A) B” means “(A B) or (B)”, that is “A” is optional.
- Referring to
FIG. 1 , adownhole network 100 in accordance with various embodiments is illustrated. Thedownhole network 100 includes apredecessor node 110, anetwork node 120, and asuccessor node 130. In one embodiment, thenetwork node 120 receives and/or transmitsdata 150 in both directions in thedownhole network 100.Data 150, in an embodiment, may also be generated by thenetwork node 120 for transmission to at least one of the other nodes, selected from thepredecessor node 110 and thesuccessor node 130. - More specifically,
data 150 is received from other network nodes physically positioned above and/or below thenetwork node 120 and is then transmitted to other network nodes in thedownhole network 100. In one embodiment, thenetwork node 120 receivesdata 150, from an immediately coupledpredecessor node 110 and transmits thedata 150 to an immediately coupledsuccessor node 130. In general, thenetwork node 120 will transmit receiveddata 150 to the other immediately coupled nodes, such as thesuccessor node 130 or the predecessor node 1 10. Occasionally, anorphan node 140 in the downhole drilling string will transition to become an active member of thedownhole network 100. - In various embodiments, the
data 150 is organized and/or encapsulated in at least oneframe 160, at least onedatagram 170, and may also include at least onepacket 180. Each frame may include frame header information and/or a frame payload. In one embodiment, the frame payload includes at least onedatagram 170. Accordingly, in one embodiment, at least onedatagram 170 is encapsulated in a single physical (PHY)layer frame 160. - In various embodiments, at least one network (NET)
layer packet 180 is encapsulated in a media access (MAC)layer datagram 170. Each datagram includes datagram header information and a datagram payload. The datagram payload includes at least onepacket 180. In various embodiments, each of the at least onepacket 180 includes packet header information and a packet payload. The packet payload includes a portion of the encapsulateddata 150. - In various embodiments, the
network node 120 is configured to perform error checking of thedata 150. In one embodiment, eachpacket 180 is configured to individually provide error checking, independent of thedatagram 170 and/or theframe 160. The data verification information necessary to perform the error checking is provided for at least one of the packet header information and the packet payload containing the encapsulated data. - Referring now to
FIG. 2 , a data structure is shown, in accordance with various embodiments. Thedata 210 is organized and/or encapsulated in at least onePHY frame 220, at least oneMAC datagram 230, and may also include at least oneNET packet 240. - In various embodiments, each
PHY frame 220 includes PHYframe header information 225 and a frame payload including the at least one encapsulatedMAC datagram 230. In various embodiments, PHYframe header information 225 includes data quality verification for at least the portion of the PHY frame storing the PHYframe header information 225. - In various embodiments, each MAC datagram 230 includes MAC
datagram header information 235 and a MAC datagram payload. The MAC datagram payload of theMAC data gram 230 includes at least oneNET packet 240. In various embodiments, MACdatagram header information 235 includes data quality verification for at least the portion of theMAC datagram 230 storing the MACdatagram header information 235. - In one embodiment, each
NET packet 240 a includes NETpacket header information 250 and aNET packet payload 245. The NETpacket header information 250 may include adestination node identifier 251,destination port information 253, asource node identifier 255,source port information 257, andpacket length information 259. TheNET packet payload 245 generally includes at least a portion of the encapsulateddata 210. - In one embodiment, the
NET packet 240 a is configured to individually provide error checking and/or data verification for at least one of the NETpacket header information 250 and theNET packet payload 245, independent of theMAC datagram 230 and/or thePHY frame 220. Alternatively, one embodiment determines packet validity based on hierarchical error checking and/or data verification of PHY frame header information, MAC datagram header information, and NET packet header information followed by error checking and/or data verification of the NET packet payload. - Resynchronization of parsing of the
NET packets 240 enables the system to recover uncorruptedNET layer packets 240 from corruptedMAC datagrams 230 and/or PHY frames 220. In various embodiments, a unique distance indicator, such as ahop count 270, is added to the Net packet and used for resynchronization upon detection of data corruption. As thehop count 270 in adownhole network 100 is unique for each node, it may be used to identify the node and also to provide a relative distance of transmitting node that originally generated the packet from the receiving node. - Accordingly, a modified
NET layer packet 240 b is generated from theNet packet 240 a through data manipulation to remove naturally occurring data that also matches the unique identifier. One technique of data manipulation includes bit and/or byte stuffing. Once a value is chosen for the identifier, the other normally occurring instances of the identifier are removed and replaced by a replacement indicator to generate astuffed packet 275. Upon reception of the data, thestuffed packet 275 may be unstuffed back to the originalNet packet 240 a by removing the replacement indicators and restoring the original values. - Referring to
FIG. 3 , a data communication arrangement between asource node 300 a and adestination node 300 c is shown, in accordance with various embodiments of the present invention. In one embodiment, the network node 300 is coupled to atransmission segment 350 and includes an application layer 310, network layer 320, media access layer 330, and physical layer 340. - In one embodiment, applications residing in the application layer 310 receive, generate, store, and transmit
data 360. Network layer applications are configured to encapsulate/unpackdata 360 of at least onepacket 370. Media access layer applications are configured to encapsulate/unpack at least onepacket 370 of at least onedatagram 380. Physical layer applications are configured to encapsulate/unpack at least onedatagram 380 of at least oneframe 390. The physical layer applications are also configured to transmit and/or to receive at least oneframe 390 via atransmission segment 350. - In one embodiment, a network node 300 may be configured to operate as either a
source node 300 a and/or adestination node 300 b/300 c. Thesource node 300 a encapsulates and transmits data to at least onedestination node 300 c in a physically segmented logical token network. In the illustrated embodiment, thephysical layer 340 a of thesource node 300 a transmits the at least oneframe 390 via thetransmission segment 350. Thetransmission segment 350 is also coupled to apotential destination node 300 b. Thepotential destination node 300 b is configured to receive at least oneframe 390 at aphysical layer 340 b and to transmit the received at least oneframe 390 onto the next node, such as thedestination node 300 c. - Various embodiments of the present invention perform NET layer parsing and resynchronization, which enables each of the network nodes (e.g., 300 a, 300 b, and 300 c) to recover
NET layer packets 370 from aPHY frame 390 and/or aMAC datagram 380 even in some cases after data corruption has occurred within a portion of thePHY frame 390. More specifically, data recovery may be accomplished by parsing packets for individual links at the NET layer 320. TheNET layer packet 370 is similar to theMAC layer datagram 380 in that both may include a header and a payload. In one embodiment, a cyclic redundancy check (CRC) is associated with eachNET layer packet 370, so that a corruptedPHY frame 390 and/or aMAC datagram 380 may still include some recoverableNET layer packets 370. A CRC is often computed and appended by a transmitting node to aNET layer packet 370 before transmission or storage, and verified afterwards by the recipient node to confirm that no changes occurred in transit. In various embodiments, CRCs are provided for both the header and the payload ofNET layer packets 370, where theMAC layer datagram 380 andPHY frame 390 only have a CRC for each respective header portion. The header for the NET layer 320 provides addressing and other information about how to handle the data in the NET payload portion of theNET layer packet 370. In one embodiment, header portion errors in either aMAC layer datagram 380 and/or aPHY frame 390 are recoverable, so that only detection of a CRC error in aNET layer packet 370 will result in the packet being thrown out. - As such, the network architecture differs from other networks in that various embodiments perform error checking using a CRC at the NET layer 320. Essentially, this configuration may allow corrupted packets to pass through the PHY layer 340 and MAC layers 330, which allows for potential recovery of data in corrupted
MAC layer datagrams 380 and/or a PHY frames 390 thereby saving bandwidth by reducing retransmission and increasing the overall speed of the network. AsNET layer packets 370 are exchanged between the NET layer 320 and theMAC layer 330 a CRC is inserted at the end of the header and the payload. As theNET layer packets 370 are received again from the MAC layer 330 the CRC is checked to ensure the data has not been corrupted.NET layer packets 370 with a bad CRC are thrown out. In one embodiment, error checking is performed by a NET layer CRC device. - Once data corruption has been detected, resynchronization of the parsing at the NET layer 320 enables the system to recover uncorrupted
NET layer packets 370. In one embodiment, resynchronization may be accomplished by detecting a unique identifier, such as a Packet Synchronization Sequence (PSS), at the start of eachNET layer packet 370. Other unique identifiers may also be provided between eachMAC layer datagram 380 and/orPHY frame 390. In various embodiments, the unique identifier is generated through data manipulation to remove naturally occurring data that also matches the unique identifier. One technique of data manipulation includes bit and/or byte stuffing eachNET layer packet 370. Once a value is chosen for the identifier, normally occurring instances are removed and replaced by a replacement indicator. Upon reception of the data, the replacement indicator is removed and the original value is restored. If an error is detected during reception (e.g., CRC), then scanning for the unique identifier provides various possibilities. A bit sequence matching the unique identifier will either identify the start of the nextNET layer packet 370 or a corrupted value in the data stream, calculation of the CRC will determine which case is present. In this manner, the receiving node may resynchronize parsing of the NET layer 320 despite the presence of errors and/or data corruption. - In one embodiment, Zero-bit insertion, a particular type of bit stuffing, is used to ensure that a PSS doesn't incidentally appear in the contents of the
PHY frame 390,MAC layer datagram 380, and/orNET layer packet 370. Once a bit sequence is selected, any naturally occurring sequence needs to be removed from the data. For example, if “01111110” was selected as the PSS, the data would need to be altered to ensure that a sequence of 6 consecutive “1” bits are not present in the frame data so as to avoid possible confusion for the PSS. In one embodiment, zero-bit insertion is used to prevent such a sequence from occurring. More specifically, if a series of five “1” bits are found in the data by the sending node a “0” bit is inserted after the fifth “1” bit, thereby limiting the maximum possible run of “1” bits to five. At a receiver node, if a series of five “1” bits is received, the subsequent “0” bit is removed to recover the original data. - When the receiver node finds “0111111” two possible outcomes may occur. To determine which, the next bit is checked. If the bit is a “0” (i.e. “01111110”) a valid PSS is assumed to have been received. If the bit is another “1” (i.e. “01111111”) then some corruption must have occurred during transmission as that data sequence cannot have been transmitted according to the selected bit sequence for the PSS. In the described example a “0” bit would have been inserted after the fifth “1” bit. Should corruption during transmission result in the PSS being received as part of the data, it is more than likely that the failed CRC would mean that both packets may be suspect to data corruption.
- Referring to
FIG. 4 , anetwork node 400 is shown in further detail, in accordance with various embodiments. An exemplarydownhole network node 400 suitable for practicing various embodiments as presented inFIGS. 1 , 3, and 5 is shown inFIG. 4 , a block diagram of adownhole network node 400 having at least onecommunication interface 420 and acommunication module 410. Thenetwork node 400 includes at least onecommunication interface 420, acommunication module 410, apacket router 430, alocal processing module 440, and a localdata acquisition module 450, coupled to each other as shown. - The illustrated
communication module 410, such as a modem, may be connected to the network (see e.g.,network 510 inFIG. 5 ) in at least two directions via transmission segments (see e.g.,transmission segments 350 inFIG. 3 and/or integratedtransmission drill pipe 570 inFIG. 5 ). However, in alternate configurations thecommunication module 410 may only be connected to thenetwork 510 in one direction. Thecommunication module 410 may modulate digital bits on an analog signal to transmit data packets from thenetwork node 400 on thenetwork 510 and demodulates analog signals received from thenetwork 510 into digital data packets. In various embodiments, thecommunication module 410 may include astorage medium 470 to temporarily store data in conjunction with transmission. - As previously indicated, a
network node 400 may also employ a timing device to calculate whether time-out thresholds have been reached. The timing device may include multiple timers individually assigned to eachcommunication interface 420 or to thecommunication module 410 in general. - The
network node 400 may comprise apacket router 430 that receives packets from thecommunication module 410 and forwards them to one or more of alocal processing module 440, a localdata acquisition module 450, or aperipheral port 460. Packets to be transmitted on thenetwork 510 may also be forwarded to thecommunication module 410 from thepacket router 430. - The
downhole network node 400 includes aperipheral tool port 460, which allows thedownhole network node 400 to collect data from associated tools, packetize the tool data and transmit it to the top of the well. - In one embodiment, a
downhole network node 400 includes a suitableportable power source 480. Often thedownhole network node 400 will need to be self-reliant on multiple battery packs 490 for power requirements. In one embodiment some of the battery packs 490 may be allocated to individual components of thedownhole network node 400 based in part on the function provided by the component requesting power. For example, a portion of the battery packs 490 could be dedicated to transmitting received packets (e.g., 410 and 470) to the next node. Another portion could be dedicated to maintaining thelocal processing 440 and related components (e.g., 430, 450, and 460). In one embodiment, an attached tool may either draw power from the node or provide a source to recharge the batteries. - Referring to
FIG. 5 , adrilling operation 500 with a downhole networking environment suitable for practicing various embodiments of the present invention is shown. Accordingly, when drilling boreholes into earthen formations, thedrilling operation 500 as shown inFIG. 5 may be used. Thedrilling operation 500 may include adrilling rig 505, an integrated downhole physically segmented logicaltoken network 510, and atubular drill string 560 having abottom hole assembly 580. Thebottom hole assembly 580 typically forms the bottom of thedrill string 560, which is typically rotatably driven by thedrilling rig 505 from the surface. In addition to providing motive force for rotating thedrill string 560, thedrilling rig 505 also supplies a drilling fluid under pressure through thetubular drill string 560 to thebottom hole assembly 580. Other components of thebottom hole assembly 580 include adrill collar 575, adrill bit 590, and various other down hole components. In operation, thedrill bit 590 is rotated and weight is applied. This action forces thedrill bit 590 into the earth, and as the bit is rotated, a drilling action is effected. - The downhole physically segmented logical
token network 510 includes a first end node and/or atop node 520, a plurality of transmission segments integrated into thedrill pipe 570, a plurality of intermediate nodes and/ormiddle nodes bottom node 550. Thedownhole network 510 provides an electrical interconnection between thetop node 520 and thebottom node 550. Thetop node 520 may, in accordance with at least one embodiment, be a component of aserver 515. Theserver 515 is positioned near the top of the well in one embodiment and may relay reconstituted well information gathered from various components in thedownhole network 510 to a variety of interested client computing devices across an area network, such as the Internet, using traditional methods known in the art. - The
downhole network 510 operates similar to the previously described network ofFIG. 1 , although features may be described in a more directional nature, for example, in one embodiment of the downhole network 510 a frame may include data associated with a logical token that may be passed up and down thedownhole network 510. In one configuration, a first token may be designated as a down-token, and a second token may be designated as an up-token. Other directional adaptations include referring to the first end node as a top end node and the second end node as a bottom end node. As such, in one embodiment, the down-token may be generated by thetop node 520 that the individual nodes (530, 540, and 550) are cyclically and/or periodically allowed to claim. In one embodiment that tries to equalize the number of transmission opportunities for each node, the up-token is a logical token that only thetop node 520 is allowed to claim. - Although the down-token has been characterized in one embodiment to be an equivalent to the first token and the up-token is characterized as an equivalent to the second token, it is clear to one of skill in the art that other characterizations are possible and should be considered within the scope of the instant invention. For example, the roles of the up and down tokens could be reversed. Moreover, the up-token and the down-token could be functionally the same logical token. In such a configuration, a directional modifier may be assigned at each node based in part on which communication interface received the token.
- As previously indicated, a
downhole network 510 is often a difficult and or discontinuous operating environment. For example, as the well increases in depth, new tubular drill pipe is added to the drill string below thetop node 520, temporarily interrupting data communications between the nodes. Additionally, portions of the drill string may become temporarily unavailable due to mechanical stresses related to drilling operations. As a result in one embodiment, each intermediate node (530 and 540) may become thebottom node 550 when no data and/or token are received from a successor immediately coupled node for a designated time period based in part on the number of nodes in thedownhole network 510. - In various embodiments, the
top node 520 is configured to selectively generate another down-token even if the up-token is not received within a designated time period. The designated time period is often based in part on the number of known active nodes in the downhole network. - Depending on the importance of the data being collected by the portion of the
network 510 in thebottom hole assembly 580, temporarily interrupting data may be unacceptable. In these situations the network may employ multiple sub-networks to divide thenetwork 510 and continue data communication. For example the illustratednetwork 510 may be divided into two sub-networks, the portion of thenetwork 510 in abottom hole assembly 580 and the top portion of thedrill string 560 associated with a sub-network 585. In various embodiments, an entire sub-network, e.g. all the nodes ofnetwork 510, may transition to an orphan operational status to conserve power or preserve data through active manipulation of timing devices associated with the end node of the sub-network. - Turning now to
FIGS. 6-7 , the particular methods of the invention, in accordance with various embodiments, are described in terms of computer firmware, software, and hardware with reference to a series of flowcharts. In various embodiments, portions of the operations to be performed by network devices may constitute state machines or computer programs made up of computer-executable instructions. Describing portions of the operations by reference to a flowchart enables one skilled in the art to develop programs including instructions to carry out the illustrated methods on suitably configured network devices (e.g., a processor of the network device executing instructions from a computer-accessible media). - In various embodiments, the computer-executable instructions may be written in a computer programming language or may be embodied in firmware logic. If written in a programming language conforming to a recognized standard, such instructions can be executed on a variety of hardware platforms and for interface to a variety of operating systems. In addition, the present invention is not described with reference to any particular programming language. It will be appreciated that a variety of programming languages may be used to implement the teachings of the embodiments as described herein. Furthermore, it is common in the art to speak of software, in one form or another (e.g., program, procedure, process, application, etc.), as taking an action or causing a result. Such expressions are merely a shorthand way of saying that execution of the software by a network device causes the processor of the computer to perform an action or a produce a result.
- Referring to
FIG. 6 , a portion of the operations of a network node operating as apotential destination node 600 is shown, in accordance with various embodiments. The network node operating as apotential destination node 600 receives data inblock 610. The received data is modified inblock 620 to include relative distance from source node updated by the network node operating as apotential destination node 600. In one embodiment, the data is encapsulated in at least one frame having at least one datagram having at least one packet. Thepotential destination node 600 begins to transmit the modified received data inblock 630. In one embodiment, transmission of the frame to the next node may begin as soon as the header is modified by thepotential destination node 600. - The network node operating as a
potential destination node 600 determines the desired destination of data inblock 640. In one embodiment, each frame is parsed into at least one datagram, and each datagram is parsed into at least one packet of the received data inblock 650. The received data is verified inblock 660. In one embodiment, the packet having packet header information and a packet payload also includes data quality information to verify the received data. The data quality information may be associated, individually or collectively, with the packet header information and/or the packet payload. In one embodiment, the destination identified in the packet header information is verified first by the network node operating as adestination node 600 inblock 640 and if the current node is a valid destination, the contents of the packet payload is subsequently verified inblock 660. Alternatively, both the packet header information and the packet payload could be verified together. - In one embodiment, the packet data quality information is independent of any data quality verification provided by encapsulated datagram header information and/or frame header information. This separation allows the network node operating as a
potential destination node 600 to selectively ignore data errors in the datagram header information and/or the frame header information, if recoverable data is available in the packets associated with the corrupted frame and/or datagram. - Referring to
FIG. 7 , a portion of the operations of a network node operating as asource node 700 is shown, in accordance with various embodiments. Inblock 710, the network node operating as asource node 700 broadcasts a request for status information to other active nodes on the network. In one embodiment, the network node operating as asource node 700 is a server node and is positioned at the top of the well/downhole network. In one embodiment the request includes use of a status token to request responses from attached nodes. As responses are received inblock 720 by the network node operating as thesource node 700, the information is used to maintain a corresponding network topology table inblock 730. - In one embodiment, the topology table may include a short network identifier (NID) for local communication in the downhole network, a longer global identifier (GUID) for addressing the node from outside the downhole network, and a unique relative distance between the
source node 700 and each node. Thesource node 700 verifies the local identification inblock 740, the relative distance inblock 750, and the global identification inblock 780. In the downhole environment, the relative distance, such as a hop counts and/or timestamps, may be used as a unique reference for each node. In one embodiment, the NID is a unique number that identifies the node on the downhole network and may be used for addressing the link from within the network. The GUID is a larger unique number than the NID and identifies the node outside of the downhole network. - A top-hole interface (THI) associated with the
source node 700 maintains a topology table to map each node's GUID to the node's NID. The topology table may update the relative position of nodes based on the received responses to the information request. Upon detecting topology changes inblock 770, thesource node 700 periodically generates and distributes the detected changes inblocks - Although specific embodiments have been illustrated and described herein, it will be appreciated by those of ordinary skill in the art and others, that a wide variety of alternate and/or equivalent implementations may be substituted for the specific embodiment shown in the described without departing from the scope of the present invention. This application is intended to cover any adaptations or variations of the embodiment discussed herein. Therefore, it is manifested and intended that the invention be limited only by the claims and the equivalents thereof.
- Whereas the present invention has been described in particular relation to the drawings attached hereto, it should be understood that other and further modifications apart from those shown or suggested herein, may be made within the scope and spirit of the present invention.
Claims (27)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/674,864 US20070201362A1 (en) | 2006-02-16 | 2007-02-14 | Increasing Bandwidth in a Downhole Network |
Applications Claiming Priority (3)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US76687506P | 2006-02-16 | 2006-02-16 | |
US77515206P | 2006-02-21 | 2006-02-21 | |
US11/674,864 US20070201362A1 (en) | 2006-02-16 | 2007-02-14 | Increasing Bandwidth in a Downhole Network |
Publications (1)
Publication Number | Publication Date |
---|---|
US20070201362A1 true US20070201362A1 (en) | 2007-08-30 |
Family
ID=38109610
Family Applications (6)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/674,864 Abandoned US20070201362A1 (en) | 2006-02-16 | 2007-02-14 | Increasing Bandwidth in a Downhole Network |
US11/674,844 Active 2028-02-17 US7570175B2 (en) | 2006-02-16 | 2007-02-14 | Node discovery in physically segmented logical token network |
US11/674,874 Abandoned US20080095165A1 (en) | 2006-02-16 | 2007-02-14 | Net-Layer Parsing and Resynchronization |
US11/674,815 Active 2028-02-17 US7649473B2 (en) | 2006-02-16 | 2007-02-14 | Physically segmented logical token network |
US12/489,309 Abandoned US20090257364A1 (en) | 2006-02-16 | 2009-06-22 | Node Discovery in Physically Segmented Logical Token Network |
US12/615,858 Abandoned US20100054273A1 (en) | 2006-02-16 | 2009-11-10 | Physically Segmented Logical Token Network |
Family Applications After (5)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US11/674,844 Active 2028-02-17 US7570175B2 (en) | 2006-02-16 | 2007-02-14 | Node discovery in physically segmented logical token network |
US11/674,874 Abandoned US20080095165A1 (en) | 2006-02-16 | 2007-02-14 | Net-Layer Parsing and Resynchronization |
US11/674,815 Active 2028-02-17 US7649473B2 (en) | 2006-02-16 | 2007-02-14 | Physically segmented logical token network |
US12/489,309 Abandoned US20090257364A1 (en) | 2006-02-16 | 2009-06-22 | Node Discovery in Physically Segmented Logical Token Network |
US12/615,858 Abandoned US20100054273A1 (en) | 2006-02-16 | 2009-11-10 | Physically Segmented Logical Token Network |
Country Status (4)
Country | Link |
---|---|
US (6) | US20070201362A1 (en) |
EP (2) | EP1821463A1 (en) |
CA (2) | CA2578695A1 (en) |
MX (2) | MX2007001829A (en) |
Cited By (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090146836A1 (en) * | 2007-12-11 | 2009-06-11 | Schlumberger Technology Corporation | Methods and apparatus to configure drill string communications |
US20100050017A1 (en) * | 2008-08-25 | 2010-02-25 | Saudi Arabian Oil Company | Intelligent Field Oil and Gas Field Data Acquisition, Delivery, Control, and Retention Based Apparatus, Program Product and Related Methods |
US8949416B1 (en) * | 2012-01-17 | 2015-02-03 | Canyon Oak Energy LLC | Master control system with remote monitoring for handling tubulars |
CN109194539A (en) * | 2018-08-13 | 2019-01-11 | 中国平安人寿保险股份有限公司 | Data management-control method, device, computer equipment and storage medium |
CN111181800A (en) * | 2019-11-27 | 2020-05-19 | 腾讯科技(深圳)有限公司 | Test data processing method and device, electronic equipment and storage medium |
Families Citing this family (55)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7962595B1 (en) * | 2007-03-20 | 2011-06-14 | Emc Corporation | Method and apparatus for diagnosing host to storage data path loss due to FibreChannel switch fabric splits |
US8165021B2 (en) * | 2007-09-05 | 2012-04-24 | Cisco Technology, Inc. | Policy-based resource management |
WO2010036157A1 (en) * | 2008-09-24 | 2010-04-01 | Telefonaktiebolaget L M Ericsson (Publ) | Key distribution to a set of routers |
US7920467B2 (en) * | 2008-10-27 | 2011-04-05 | Lexmark International, Inc. | System and method for monitoring a plurality of network devices |
US8645571B2 (en) * | 2009-08-05 | 2014-02-04 | Schlumberger Technology Corporation | System and method for managing and/or using data for tools in a wellbore |
US8209447B2 (en) | 2009-08-31 | 2012-06-26 | Micron Technology, Inc. | Device to device flow control within a chain of devices |
US9094175B2 (en) | 2010-07-16 | 2015-07-28 | Qualcomm, Incorporated | Method and apparatus for saving power by using signal field of preamble |
US8633830B2 (en) * | 2010-10-06 | 2014-01-21 | Wixxi Technologies, Llc | Intelligent universal wireless adapter |
US9593567B2 (en) | 2011-12-01 | 2017-03-14 | National Oilwell Varco, L.P. | Automated drilling system |
US20130142094A1 (en) * | 2011-12-02 | 2013-06-06 | Qualcomm Incorporated | Systems and methods for frame filtering and for enabling frame filtering |
JP5756430B2 (en) * | 2012-06-05 | 2015-07-29 | 株式会社日立製作所 | Net monitoring device |
US9911323B2 (en) * | 2012-12-04 | 2018-03-06 | Schlumberger Technology Corporation | Toolstring topology mapping in cable telemetry |
WO2014100275A1 (en) | 2012-12-19 | 2014-06-26 | Exxonmobil Upstream Research Company | Wired and wireless downhole telemetry using a logging tool |
US9631485B2 (en) | 2012-12-19 | 2017-04-25 | Exxonmobil Upstream Research Company | Electro-acoustic transmission of data along a wellbore |
US9557434B2 (en) | 2012-12-19 | 2017-01-31 | Exxonmobil Upstream Research Company | Apparatus and method for detecting fracture geometry using acoustic telemetry |
US9816373B2 (en) | 2012-12-19 | 2017-11-14 | Exxonmobil Upstream Research Company | Apparatus and method for relieving annular pressure in a wellbore using a wireless sensor network |
US10480308B2 (en) | 2012-12-19 | 2019-11-19 | Exxonmobil Upstream Research Company | Apparatus and method for monitoring fluid flow in a wellbore using acoustic signals |
WO2014100264A1 (en) | 2012-12-19 | 2014-06-26 | Exxonmobil Upstream Research Company | Telemetry system for wireless electro-acoustical transmission of data along a wellbore |
WO2015080754A1 (en) | 2013-11-26 | 2015-06-04 | Exxonmobil Upstream Research Company | Remotely actuated screenout relief valves and systems and methods including the same |
WO2016039900A1 (en) | 2014-09-12 | 2016-03-17 | Exxonmobil Upstream Research Comapny | Discrete wellbore devices, hydrocarbon wells including a downhole communication network and the discrete wellbore devices and systems and methods including the same |
US9762676B2 (en) | 2014-09-26 | 2017-09-12 | Intel Corporation | Hardware resource access systems and techniques |
US10687381B2 (en) * | 2014-12-01 | 2020-06-16 | Lg Electronics Inc. | Method and apparatus for configuring prohibit timer for prose transmission in wireless communication system |
US9531850B2 (en) * | 2014-12-04 | 2016-12-27 | Cisco Technology, Inc. | Inter-domain service function chaining |
US9863222B2 (en) | 2015-01-19 | 2018-01-09 | Exxonmobil Upstream Research Company | System and method for monitoring fluid flow in a wellbore using acoustic telemetry |
US10408047B2 (en) | 2015-01-26 | 2019-09-10 | Exxonmobil Upstream Research Company | Real-time well surveillance using a wireless network and an in-wellbore tool |
CN106302206B (en) * | 2015-05-28 | 2020-04-24 | 中兴通讯股份有限公司 | Message forwarding processing method, device and system |
US10021018B2 (en) * | 2015-09-07 | 2018-07-10 | Citrix Systems, Inc. | Systems and methods for associating multiple transport layer hops between clients and servers |
US10590759B2 (en) | 2016-08-30 | 2020-03-17 | Exxonmobil Upstream Research Company | Zonal isolation devices including sensing and wireless telemetry and methods of utilizing the same |
US10526888B2 (en) | 2016-08-30 | 2020-01-07 | Exxonmobil Upstream Research Company | Downhole multiphase flow sensing methods |
US11828172B2 (en) | 2016-08-30 | 2023-11-28 | ExxonMobil Technology and Engineering Company | Communication networks, relay nodes for communication networks, and methods of transmitting data among a plurality of relay nodes |
US10465505B2 (en) | 2016-08-30 | 2019-11-05 | Exxonmobil Upstream Research Company | Reservoir formation characterization using a downhole wireless network |
US10697287B2 (en) | 2016-08-30 | 2020-06-30 | Exxonmobil Upstream Research Company | Plunger lift monitoring via a downhole wireless network field |
US10344583B2 (en) | 2016-08-30 | 2019-07-09 | Exxonmobil Upstream Research Company | Acoustic housing for tubulars |
US10364669B2 (en) | 2016-08-30 | 2019-07-30 | Exxonmobil Upstream Research Company | Methods of acoustically communicating and wells that utilize the methods |
US10415376B2 (en) | 2016-08-30 | 2019-09-17 | Exxonmobil Upstream Research Company | Dual transducer communications node for downhole acoustic wireless networks and method employing same |
US20180359130A1 (en) * | 2017-06-13 | 2018-12-13 | Schlumberger Technology Corporation | Well Construction Communication and Control |
US11021944B2 (en) | 2017-06-13 | 2021-06-01 | Schlumberger Technology Corporation | Well construction communication and control |
US11143010B2 (en) | 2017-06-13 | 2021-10-12 | Schlumberger Technology Corporation | Well construction communication and control |
US10837276B2 (en) | 2017-10-13 | 2020-11-17 | Exxonmobil Upstream Research Company | Method and system for performing wireless ultrasonic communications along a drilling string |
US10697288B2 (en) | 2017-10-13 | 2020-06-30 | Exxonmobil Upstream Research Company | Dual transducer communications node including piezo pre-tensioning for acoustic wireless networks and method employing same |
WO2019074657A1 (en) | 2017-10-13 | 2019-04-18 | Exxonmobil Upstream Research Company | Method and system for performing operations using communications |
US11035226B2 (en) | 2017-10-13 | 2021-06-15 | Exxomobil Upstream Research Company | Method and system for performing operations with communications |
AU2018347465B2 (en) | 2017-10-13 | 2021-10-07 | Exxonmobil Upstream Research Company | Method and system for performing communications using aliasing |
WO2019074654A2 (en) | 2017-10-13 | 2019-04-18 | Exxonmobil Upstream Research Company | Method and system for performing hydrocarbon operations with mixed communication networks |
MX2020007277A (en) | 2017-11-17 | 2020-08-17 | Exxonmobil Upstream Res Co | Method and system for performing wireless ultrasonic communications along tubular members. |
US10690794B2 (en) | 2017-11-17 | 2020-06-23 | Exxonmobil Upstream Research Company | Method and system for performing operations using communications for a hydrocarbon system |
US10844708B2 (en) | 2017-12-20 | 2020-11-24 | Exxonmobil Upstream Research Company | Energy efficient method of retrieving wireless networked sensor data |
WO2019133290A1 (en) | 2017-12-29 | 2019-07-04 | Exxonmobil Upstream Research Company | Methods and systems for monitoring and optimizing reservoir stimulation operations |
US11156081B2 (en) | 2017-12-29 | 2021-10-26 | Exxonmobil Upstream Research Company | Methods and systems for operating and maintaining a downhole wireless network |
WO2019156966A1 (en) | 2018-02-08 | 2019-08-15 | Exxonmobil Upstream Research Company | Methods of network peer identification and self-organization using unique tonal signatures and wells that use the methods |
US11268378B2 (en) | 2018-02-09 | 2022-03-08 | Exxonmobil Upstream Research Company | Downhole wireless communication node and sensor/tools interface |
DE102018124184A1 (en) * | 2018-10-01 | 2020-04-02 | Endress+Hauser Process Solutions Ag | Procedure for establishing network communication using OPC UA |
EP3891932B1 (en) * | 2018-12-03 | 2024-01-31 | Deutsche Telekom AG | Method for an improved and simplified operation and architecture of a central office point of delivery within a broadband access network of a telecommunications network, telecommunications network, and system, program and computer program product |
US11293280B2 (en) | 2018-12-19 | 2022-04-05 | Exxonmobil Upstream Research Company | Method and system for monitoring post-stimulation operations through acoustic wireless sensor network |
US11952886B2 (en) | 2018-12-19 | 2024-04-09 | ExxonMobil Technology and Engineering Company | Method and system for monitoring sand production through acoustic wireless sensor network |
Citations (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US4949337A (en) * | 1989-01-30 | 1990-08-14 | Honeywell Inc. | Token passing communication network including a node which maintains and transmits a list specifying the order in which the token is passed |
US5001472A (en) * | 1988-02-11 | 1991-03-19 | Datapoint Corporation | Uneven token distribution technique for token based local area network |
US20020064163A1 (en) * | 2000-11-30 | 2002-05-30 | Takehiko Fujiyama | Method and apparatus for transmitting data in a linear-type or ring-type network |
US6631137B1 (en) * | 1998-08-07 | 2003-10-07 | Cisco Technology, Inc. | Method and system for improving high speed internetwork data transfers |
US20040037320A1 (en) * | 2002-08-21 | 2004-02-26 | Dickson Scott M. | Early transmission and playout of packets in wireless communication systems |
US20050285751A1 (en) * | 2004-06-28 | 2005-12-29 | Hall David R | Downhole Drilling Network Using Burst Modulation Techniques |
US20060007953A1 (en) * | 2004-07-09 | 2006-01-12 | Nokia Corporation | Encapsulator and an associated method and computer program product for encapsulating data packets |
US20060104303A1 (en) * | 2004-11-16 | 2006-05-18 | Srihari Makineni | Packet coalescing |
US20060120336A1 (en) * | 2001-12-03 | 2006-06-08 | Steve Fantaske | Wireless communication system |
US20060181398A1 (en) * | 2005-02-11 | 2006-08-17 | Martich Mark E | Apparatus and method for communication system |
US7342897B1 (en) * | 1999-08-07 | 2008-03-11 | Cisco Technology, Inc. | Network verification tool |
Family Cites Families (21)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DE3268099D1 (en) | 1982-06-15 | 1986-02-06 | Ibm | Method and apparatus for controlling access to a communication network |
US4972437A (en) * | 1988-06-24 | 1990-11-20 | International Business Machines Corporation | Method of controlling limited resource sessions in a data communications network |
CH677568A5 (en) * | 1989-03-21 | 1991-05-31 | Datawatt Bv | |
JP3115451B2 (en) | 1993-05-21 | 2000-12-04 | トヨタ自動車株式会社 | Communication network |
US5959547A (en) * | 1995-02-09 | 1999-09-28 | Baker Hughes Incorporated | Well control systems employing downhole network |
CA2283695C (en) * | 1997-03-17 | 2007-10-02 | Ge-Harris Railway Electronics, L.L.C. | A communications system and method for interconnected networks having a linear topology, especially railways |
US6483812B1 (en) * | 1999-01-06 | 2002-11-19 | International Business Machines Corporation | Token ring network topology discovery and display |
US6853623B2 (en) * | 1999-03-05 | 2005-02-08 | Cisco Technology, Inc. | Remote monitoring of switch network |
US6594232B1 (en) * | 1999-06-02 | 2003-07-15 | Marconi Communications, Inc. | Transmitter-based path protection switching in a ring network |
GB2371625B (en) * | 2000-09-29 | 2003-09-10 | Baker Hughes Inc | Method and apparatus for prediction control in drilling dynamics using neural network |
US7280477B2 (en) * | 2002-09-27 | 2007-10-09 | International Business Machines Corporation | Token-based active queue management |
CA2512651C (en) * | 2003-01-17 | 2009-01-06 | Halliburton Energy Services, Inc. | Integrated drilling dynamics system and method of operating same |
WO2004090285A1 (en) * | 2003-03-31 | 2004-10-21 | Baker Hughes Incorporated | Real-time drilling optimization based on mwd dynamic measurements |
KR100493898B1 (en) * | 2003-04-16 | 2005-06-10 | 삼성전자주식회사 | Network device, system and method for providing list of controlled device |
US8339945B2 (en) * | 2003-07-01 | 2012-12-25 | Mworks Wireless Holdings Llc | Data link control architecture for integrated circuit devices |
US7139218B2 (en) * | 2003-08-13 | 2006-11-21 | Intelliserv, Inc. | Distributed downhole drilling network |
US7529267B2 (en) * | 2004-03-19 | 2009-05-05 | Fujitsu Limited | Data transmissions in communication networks using multiple tokens |
US7672314B2 (en) * | 2004-07-09 | 2010-03-02 | Cisco Technology, Inc. | Scaling VLANs in a data network |
US8406211B2 (en) * | 2004-09-29 | 2013-03-26 | Telefonaktiebolaget Lm Ericsson (Publ) | Forward error correction for broadcast/multicast service |
US7347271B2 (en) * | 2004-10-27 | 2008-03-25 | Schlumberger Technology Corporation | Wireless communications associated with a wellbore |
US7548068B2 (en) * | 2004-11-30 | 2009-06-16 | Intelliserv International Holding, Ltd. | System for testing properties of a network |
-
2007
- 2007-02-14 MX MX2007001829A patent/MX2007001829A/en active IP Right Grant
- 2007-02-14 MX MX2007001832A patent/MX2007001832A/en active IP Right Grant
- 2007-02-14 US US11/674,864 patent/US20070201362A1/en not_active Abandoned
- 2007-02-14 US US11/674,844 patent/US7570175B2/en active Active
- 2007-02-14 US US11/674,874 patent/US20080095165A1/en not_active Abandoned
- 2007-02-14 US US11/674,815 patent/US7649473B2/en active Active
- 2007-02-15 CA CA002578695A patent/CA2578695A1/en not_active Abandoned
- 2007-02-15 CA CA002578886A patent/CA2578886A1/en not_active Abandoned
- 2007-02-16 EP EP07250669A patent/EP1821463A1/en not_active Withdrawn
- 2007-02-16 EP EP07250670A patent/EP1821464A3/en not_active Withdrawn
-
2009
- 2009-06-22 US US12/489,309 patent/US20090257364A1/en not_active Abandoned
- 2009-11-10 US US12/615,858 patent/US20100054273A1/en not_active Abandoned
Patent Citations (11)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5001472A (en) * | 1988-02-11 | 1991-03-19 | Datapoint Corporation | Uneven token distribution technique for token based local area network |
US4949337A (en) * | 1989-01-30 | 1990-08-14 | Honeywell Inc. | Token passing communication network including a node which maintains and transmits a list specifying the order in which the token is passed |
US6631137B1 (en) * | 1998-08-07 | 2003-10-07 | Cisco Technology, Inc. | Method and system for improving high speed internetwork data transfers |
US7342897B1 (en) * | 1999-08-07 | 2008-03-11 | Cisco Technology, Inc. | Network verification tool |
US20020064163A1 (en) * | 2000-11-30 | 2002-05-30 | Takehiko Fujiyama | Method and apparatus for transmitting data in a linear-type or ring-type network |
US20060120336A1 (en) * | 2001-12-03 | 2006-06-08 | Steve Fantaske | Wireless communication system |
US20040037320A1 (en) * | 2002-08-21 | 2004-02-26 | Dickson Scott M. | Early transmission and playout of packets in wireless communication systems |
US20050285751A1 (en) * | 2004-06-28 | 2005-12-29 | Hall David R | Downhole Drilling Network Using Burst Modulation Techniques |
US20060007953A1 (en) * | 2004-07-09 | 2006-01-12 | Nokia Corporation | Encapsulator and an associated method and computer program product for encapsulating data packets |
US20060104303A1 (en) * | 2004-11-16 | 2006-05-18 | Srihari Makineni | Packet coalescing |
US20060181398A1 (en) * | 2005-02-11 | 2006-08-17 | Martich Mark E | Apparatus and method for communication system |
Cited By (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20090146836A1 (en) * | 2007-12-11 | 2009-06-11 | Schlumberger Technology Corporation | Methods and apparatus to configure drill string communications |
US20100050017A1 (en) * | 2008-08-25 | 2010-02-25 | Saudi Arabian Oil Company | Intelligent Field Oil and Gas Field Data Acquisition, Delivery, Control, and Retention Based Apparatus, Program Product and Related Methods |
US8312320B2 (en) | 2008-08-25 | 2012-11-13 | Saudi Arabian Oil Company | Intelligent field oil and gas field data acquisition, delivery, control, and retention based apparatus, program product and related methods |
US8949416B1 (en) * | 2012-01-17 | 2015-02-03 | Canyon Oak Energy LLC | Master control system with remote monitoring for handling tubulars |
CN109194539A (en) * | 2018-08-13 | 2019-01-11 | 中国平安人寿保险股份有限公司 | Data management-control method, device, computer equipment and storage medium |
CN111181800A (en) * | 2019-11-27 | 2020-05-19 | 腾讯科技(深圳)有限公司 | Test data processing method and device, electronic equipment and storage medium |
Also Published As
Publication number | Publication date |
---|---|
EP1821464A3 (en) | 2007-09-12 |
US20100054273A1 (en) | 2010-03-04 |
US20080095165A1 (en) | 2008-04-24 |
US20070189165A1 (en) | 2007-08-16 |
US7570175B2 (en) | 2009-08-04 |
CA2578695A1 (en) | 2007-08-16 |
US20090257364A1 (en) | 2009-10-15 |
EP1821464A2 (en) | 2007-08-22 |
MX2007001832A (en) | 2008-11-18 |
US7649473B2 (en) | 2010-01-19 |
US20070189166A1 (en) | 2007-08-16 |
MX2007001829A (en) | 2008-11-18 |
CA2578886A1 (en) | 2007-08-16 |
EP1821463A1 (en) | 2007-08-22 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20070201362A1 (en) | Increasing Bandwidth in a Downhole Network | |
US8451863B2 (en) | System and method for identifying upper layer protocol message boundaries | |
CN100486241C (en) | Method and system for obtaining path maximum transmission length in channel gateway environment | |
CN108123813A (en) | The transmission method and device of Operations, Administration and Maintenance OAM data | |
US7668118B2 (en) | Directional topology discovery for downhole networks | |
CN104365073A (en) | Host-router multiple tunnel management | |
CN104038322B (en) | Intermediate node, communication network and its data transfer control method | |
US20070124651A1 (en) | Method for lost packet reconstruction and device for carrying out said method | |
CN101494585A (en) | Method and equipment for implementing reliable transmission of universal route encapsulation tunnel | |
CN100484101C (en) | A method, system and device to transport the IPv6 message of Ethernet | |
CN102195750B (en) | Data transfer device and data transfer system | |
US20090210770A1 (en) | Method, system and computer program product for end to end error checking in ethernet | |
EP1357721A2 (en) | System and method for identifying upper layer protocol message boundaries | |
CN108718226B (en) | Transmission method for data of underwater long-delay sensor network transmission layer | |
US20140056103A1 (en) | Seismic survey communication systems and methods | |
JP4401910B2 (en) | Data communication apparatus and data communication method | |
Krimchansky et al. | The Geostationary Operational Satellite R Series SpaceWire Based Data System Architecture | |
JP5532030B2 (en) | Data communication method and data communication apparatus | |
CN105337830B (en) | Data transmission network and data transmission method | |
Daradi | Computer Networks-I | |
Acharya et al. | Delay tolerant networks: A retrospective | |
US8904043B2 (en) | Network device | |
Arango et al. | Compressing MAC headers on shared wireless media | |
EP1734720A2 (en) | System and method for identifying upper layer protocol message boundaries |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: INTELLISERV, INC., UTAH Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:JOHNSON, MONTE;STILLINGS, MARK;MOON, JUSTIN;REEL/FRAME:019033/0531 Effective date: 20070307 |
|
AS | Assignment |
Owner name: INTELLISERV INTERNATIONAL HOLDING, LTD., TEXAS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:INTELLISERV, INC.;REEL/FRAME:020279/0455 Effective date: 20070801 Owner name: INTELLISERV INTERNATIONAL HOLDING, LTD.,TEXAS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:INTELLISERV, INC.;REEL/FRAME:020279/0455 Effective date: 20070801 |
|
AS | Assignment |
Owner name: INTELLISERV INC, TEXAS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:INTELLISERV INTERNATIONAL HOLDING LTD;REEL/FRAME:023649/0390 Effective date: 20090922 Owner name: INTELLISERV INC,TEXAS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:INTELLISERV INTERNATIONAL HOLDING LTD;REEL/FRAME:023649/0390 Effective date: 20090922 |
|
AS | Assignment |
Owner name: INTELLISERV, LLC, TEXAS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:INTELLISERV, INC.;REEL/FRAME:023750/0965 Effective date: 20090925 Owner name: INTELLISERV, LLC,TEXAS Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:INTELLISERV, INC.;REEL/FRAME:023750/0965 Effective date: 20090925 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |