Underwater telephone The underwater telephone, also known as UQC, AN/WQC-2, or Gertrude, was used by the
U.S. Navy in 1945 after in Kiel, Germany, in 1935 different realizations at sea were demonstrated. The terms UQC and AN/WQC-2 follow the nomenclature of the
Joint Electronics Type Designation System. The type designation "UQC" stands for General Utility (multi use), Sonar and Underwater Sound and Communications (Receiving/Transmitting, two way). The "W" in WQC stands for Water Surface and Underwater combined. The underwater telephone is used on all crewed
submersibles and many Naval surface ships in operation. Voice or an audio tone (morse code) communicated through the UQC are
heterodyned to a high pitch for acoustic transmission through water.
JANUS In April 2017, NATO's
Centre for Maritime Research and Experimentation announced the approval of JANUS, a standardized protocol to transmit digital information underwater using acoustic sound (like
modems and
fax machines do over telephone lines). Documented in
STANAG 4748, it uses 900 Hz to 60 kHz frequencies at distances of up to . It is available for use with military and civilian, NATO and non-NATO devices; it was named after the
Roman god of gateways, openings, etc. The JANUS specification (ANEP-87) provides for a flexible plug-in-based payload scheme. A baseline JANUS packet consists of 64 bits to which further arbitrary data (Cargo) can be appended. This enables multiple different applications such as Emergency location, Underwater AIS (Automatic Identification System), and Chat. An example of an Emergency Position and Status message can be written as the following
JSON representation (the actual packet is in an efficient binary format): { "ClassUserID": 0, "ApplicationType": 3, "Nationality": "PT", "Latitude": "38.386547", // internally in units of 90/8388607 degrees "Longitude": "-9.055858", // ditto "Depth": "16", // internally an integer, meters "Speed": "1.4", // internally in units of 0.1 knots "Heading": "0.0", // internally in units of 0.705 degrees "O2": "17.8", // internally in units of 0.1% (17%-23.3%) "CO2": "5.0", // internally in units of 0.1% (0-6.3%) "CO": "76", // internally in units of 1 ppm "H2": "3.5", // internally in units of 0.1% (0-6.3%) "Pressure": "45.0", // internally in units of 0.1 bar (0.9-103.2 bar) "Temperature": "21.0", // internally in units of 1 celsius (0-63 deg C) "Survivors": "43", // 0-255 "MobilityFlag": "1", // rows starting here are "baseline message" content, as are ClassUserID and ApplicationType. 1 = mobile "ForwardingCapability": "1", // Used for routing "TxRxFlag": "0", // 0 = transmit-only; 1 = bidirectional able "ScheduleFlag": "0" } This Emergency Position and Status Message (Class ID 0 Application 3 Plug-in) message shows a Portuguese submarine at 38.386547 latitude -9.055858 longitude at a depth of 16 meters. It is moving north at 1.4 knots, and has 43 survivors on board and shows the environmental conditions.
Underwater messaging Commercial hardware products have been designed to enable two-way underwater messaging between scuba divers. These support sending from a list of pre-defined messages from a dive computer using acoustic communication. Research efforts have also explored the use of smartphones in water-proof cases for underwater communication, using acoustic
modem hardware as phone attachments as well as using a software app without any additional hardware. The
Android software app, AquaApp, from University of Washington uses the microphones and speakers on existing smartphones and smart watches to enable underwater acoustic communication. It had been tested to send digital messages using smartphones between divers at distances of up to 100 m. == See also ==