Subsea ROV Communication Protocol Segmentation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current subsea remotely operated vehicle (ROV) systems face challenges with slower data transmission speeds, particularly with protocols like RS-232, RS-422, or RS-485, which can be hazardous at depth and around structures, and require faster Ethernet-based communication for increased bandwidth and scalability, along with the need for redundant systems for backup operations.

Innovation Solution

A scalable modular design that supports concurrent or sequential operation of multiple data transmission protocols, including RS-232/RS-422 and Ethernet, within a single signal transmission pathway, utilizing separate transceivers for each protocol to ensure reliable and efficient data communication, with the ability to switch between protocols for fault tolerance and diagnostics.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If standard communication protocols are used for remote vehicle control, then device compatibility is improved, but security against hacking and unauthorized access deteriorates

Engineering Contradiction:
Improvedevice compatibilityVSAvoidsecurity
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The communication protocol is divided into multiple layers: a standard upper layer for compatibility and a custom lower layer for security. This segmentation allows the system to use widely supported protocols like TCP/IP for device compatibility while implementing proprietary security mechanisms in the data link layer, thus resolving the contradiction between compatibility and security.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

A custom data link layer acts as an intermediary between the standard network layer and the application layer. This intermediary layer provides security functions (authentication, encryption, error checking) while maintaining compatibility with standard communication protocols, thereby enabling both device compatibility and enhanced security.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If custom communication protocols are implemented to improve security, then security is improved, but device compatibility and ease of integration deteriorates

Engineering Contradiction:
ImprovesecurityVSAvoiddevice compatibility
Core Design Contradiction:
ReliabilityVSAdaptability or versatility

Solution Approach 1:

The protocol stack is segmented such that security-critical functions are implemented in a custom data link layer while the network and application layers use standard protocols. This allows security to be enhanced without sacrificing device compatibility, as standard devices can still communicate at the network layer and above.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The custom data link layer is designed to work with multiple standard network protocols (TCP, UDP, WebSocket), providing universal security functionality across different communication channels. This multi-functionality approach maintains broad device compatibility while implementing unified security standards.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Reliability

If encryption and authentication mechanisms are added to communication protocols, then security is improved, but communication latency and response time deteriorates

Engineering Contradiction:
ImprovesecurityVSAvoidcommunication latency
Core Design Contradiction:
ReliabilityVSSpeed

Solution Approach 1:

Authentication and encryption keys are established through a preliminary handshake process before actual data transmission begins. This preliminary action allows security mechanisms to be in place before critical control commands are sent, minimizing the impact on real-time vehicle control latency.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

Security authentication is performed periodically at defined intervals rather than continuously for every data packet. This periodic approach maintains security while reducing the cumulative latency impact, allowing real-time control commands to pass through with minimal delay after initial authentication.

Inventive Principle:
Principle #19Periodic action

Data Source

PatentEP3286858B1Remotely operated vehicle control communication system and method of use
Publication Date: 2019.10.09 OCEANEERING INTERNATIONAL INC
  • EP3286858B1 patent drawingFigure 1~2
  • EP3286858B1 patent drawingFigure 3~4
  • EP3286858B1 patent drawingFigure 5

AI summary

For remotely operated vehicles (ROV) deployed subsea, communications between an ROV and a system remote from the ROV may use a remotely operated vehicle control communication system to achieve simultaneous and/or discrete data communications at two differing data transmission speeds using two differing data protocols over a common signal transmission pathway configured for use subsea at the first data transmission speed and the second data transmission speed, either separately or concurrently.