14 August 2019

CIS-75 FSK 75Bd/250

CIS-75-75/250  is a Russian/CIS system supposed in use by Military in HF. As its name, this system use F1B modulation with 250 Hz shift and 75 bps speed, most likely a broadcast with linear encryption (ACF=0). The transmission was heard today on 9188 KHz (cf), operating continuously from the first morning. It's worth noting that during the days back, while I was monitoring the Swiss-MIL on 9187 KHz/USB, this FSK signal was not present: maybe 9188 KHz is not a primary channel, but it's a my guess.


According to several TDoA localizations, the site of Tx is in the area of Moscow.


kiwi-kuo.aprs.fi_2019-08-14T13_08_37Z_9188.00_iq.wav

13 August 2019

Defence Australia 188-110 Serial transmissions

The Australian 188-110A Serial running on 14385.0 KHz/USB (600bps KW-46/KIV-7M secured broadcast) and 10407.0 KHz/USB (2400bps 1536-bit TDM protocol), already discussed here, are most likely originated from Defence Australia Tx sites which are located in North West Cape (Exmouth) and Townsville (Bohle River).



18 July 2019

KG-STV MSK 1200Bd/600 (via Qatar-OSCAR 100)

KG-STV is a digital SSTV system developed by JJ0OBZ (K.G. from Japan). Unlike the analog SSTV, which scans the image line by line, KG scans the image in blocks of 16x16 pixels, i.e. 15 scan lines each conisting of 20 blocks of 16x16 pixels, that during transmission are compressed and digitally encoded one by one.The image has also one of the formats used in SSTV, which is 320 by 240 pixels. The 300 blocks of the image are transmitted fropm left to right and from top to bottom. The reception can be made at any time during transmission as in analog SSTV [1].
KG-STV is also the nome of the experimental program coded by JJ0OBZ to transfer digital images and short text-based messages [2].

Fig. 1
The program allows to use one of two types of digital modulation: MSK and 4LFSK. In MSK, KSG forward to 1200 Baud (equivalent in this case of MSK, 1200 bps) and the frequency of marks and spaces are 1800 and 1200 Hz respectively (4LFSK: '00 '1200Hz, '01' 1400Hz, '10' 1600Hz, '11' 1800Hz).
The 4LFSK is a version of 4 levels of MSK, and therefore carries twice as many bits, ie with the same 1200 Baud, transmits 2400 bits per second, but requires a channel with less noise. The transmission can be done with Viterbi convolutional code error correction (NASA standard K = 7 convolutional), but in this case the transmission is obviously more time consuming (almost twice as long).

KG uses a synchronization sequence of 63 bits: 
000011100001001000110110010110101110111100110001010100111111010

and a scrambling pseudo random sequence of 127 bits (polynomial x^21+x^3+1):
1110110011000100100111001111100100000100011010101001101101001010
000101100001100101111111010110111011110001110100010101110000001

Fig. 2
Fig. 3
Although KG-STV can be seen on amateur SSTV bands (3733, 7173, and 14233 kHz), I tuned it on 10.496,25 GHz (Fig. 1) via AMSAT P4-A transponder on Qatar-OSCAR 100 (Es’hail-2), the first geostationary amateur radio transponder: more precisely I used the Qatar-OSCAR 100 Narrowband WebSDR [3] since I'm not equipeed for satellite receptions :).



10 July 2019

what a blunder :)

some days ago I went on a S4285 modem running on 4271.0 KHz/USB in 600bps/L submode. Bitstream after demodulation showed a 2163-bit length period: clearly a test tape. Once reshaped, an asynchronous transmission appeared and I thought of a strange 6N1 framing!!!
It was thaks to @swlfrance Nicolas (and later AngazU) that I understood my mistake: actually it was a common ITA2 5E1 framing used in this case by French Ny HQ FUJ in Port des Galets, Nouméa.
Anyway, it was the first time I met that framing.





4 July 2019

110A 2400bps modem carrying 1536-bit protocol

Signal recorded on 14600.0 KHz/USB tranks to the KiwiSDR http://collie2.ddns.net:8073/ located in Western Australia. 
The used HF waveform is 188-110A Serial in 2400 bps mode, note the 48 symbols length frames (32+16 UK). ACF value is 200ms that makes 1440-bits/480-symbols: the length of the ACF is due to the short interleaver matrix dimensions for 2400 bps speed (40 rows x 70 columns) as discussed here.
Fig. 1
Once demodulated, we get a stream that has the well-known period of 1536 bits length that can be attributable to the GA-205 multiplexer: don't know if they were using 4 of 12 channels only. Also found the sync characters 9C16 and 9D16 ... but it might be a mere coincidence.  Most likely it's a naval broadcast by the Australian Navy RAN.

Fig. 2
Fig. 3


20 June 2019

unid QPSK 9KHz 4800Bd

Just working on the wideband signal spotted by Christoph first on 10160.0 KHz (cf) and more in detail discussed here in his blog. Replied his same results: period consisting of 984 bits (492 symbols) and 24-bit long sub-frames. As a further detail, I want just to add how the sub-frames seem to use different polarity.  Same result also for the geo location of Tx site (prob. Luxembourg).
Thanks to Christoph for reporting and sharing.





Signal recorded using the KiwiSDR owned by IW2NKE in Italy.

3 June 2019

STANAG-4285 1200bps/L in async mode


Interesting recording of STANAG-4285 1200bps/L blocks which transport 8N1 framed streams (async ops).

Fig. 1
After demodulation (I preferred to use my Harris RF-5710A modem), each block consists of 476 bytes of data and share the same header (Fig. 2):
00 52 00 00 A4 3A 29 21 5C F0 01 4C 00 00 00 00 00 00 00 F2 40 19 77 E6 ...
don't know what the "signature" could be (encryption, compression, protocol encapsulation...), anyway the messages are not sent in clear-text.

Fig. 1
Recording picked up on 7559.0 KHz/USB using http://swloi33.proxy.kiwisdr.com:8073/ 

https://yadi.sk/d/ceWfDANNQF9yIw
 


28 May 2019

KW-46/KIV-7M secured fleet broadcast using the GA-205 multiplex (Australian RAN)


This is a very interesting STANAG-4285 signal spotted on May 24 on 6378.0 KHz USB thanks to the KiwiSDR owned by VK6QS in Collie, Western Australia. About the 6378 KHz, some old WUN logs report the callsign VZD800, at that time attribuited to the Royal Australian Navy (RAN). On my side, on that same frequency I spotted the Australian MHFCS net operating in ISB/FSK: so, as also confirmed by the direction finding, the source is definitely in Australia. 
In my opinion, I believe this is a KW-46 (or KIV-7M) secured multichannel fleet broadcast originated by the GA-205 TDM [1]: a 12-channel time division multiplexer that was just deployed at RAN by DRS Technologies (Fig. 1).

Fig. 1

Now, the way I came up to this conclusion.
The HF waveform is STANAG-4285, here used in the usual "600bps/Long" sub-mode (Fig. 1): waveform that is easily recognizable and then demodulable by almost all software decoders. Given the evidence of regular patterns, I reshaped the demodulated stream to a 12-bit format, just as the number of the input ports of the GA-205 TDM. After reshaping, you can clearly see that the 12 input channels transport exactly the same data (Fig. 2).

Fig.2
Then I exctracted a single payload (i.e. a column of the stream), reshaped it to a 7-bit frames format and tested it for LFSR delimitation: as expected, the KW-46 "sign" was detected (Fig. 3). Indeed, as from STANAG-5065, the "Fibonacci bits" originated by the polynomial x^31+x^3+1 are used by KW-46 cryptographic equipment to provide  synchronization.  

Fig.3
In synchronous mode the TDM works by the muliplexer giving exactly the same time slot to each device connected to it even if one or more devices have nothing to transmit. The data rates of different input devices control the number of the slots: a device may have one slot, other may have two or three according to their data rate. In this case, all the input channels have the same data rate of 600:12=50 Baud, therefore share the same number of slots.  Managing a TDM requires that some control bits (sync, device tagging, ...) be appended to the beginning of each slot, but I did not find such bits in the streams I demodulated: a recording of the initial part of a similar transmission could help.
From what above, in my opinion the heard S4285 transmission is a fleet broadcast consisting of 12 "flat multiplexed" [2] channels that transport the same KW-46/KIV-7M secured payload (real traffic or pseudo-random chars).

Monitoring the 6378.0 KHz frequency, on May 25 I saw that they switched to the ISB mode (Fig. 4), more precisely: LSB for a single channel fleet broadcast and USB for a multi channel (GA-205 TDM) fleet broadcast; both the broadcasts are KW-46 secured and use the same STANAG-4285 600bps/L waveform. Don't know if they carry the same payloads. 
The same STANAG-4285 configuration and broadcast paradigm were also spotted on 7462, 8460.2, 9140, 10368, 10407, and 10847.2 KHz (logged on May, 28): surely there are many other operating frequencies that I do not currently know.


For what concerns the source of the signal, TDoA direction findings indicate the "Naval Communication Station Harold E. Holt" (NCS HEH) which is located 6km north of Exmouth (Fig. 5). COMMSTA HEH is jointly manned by Royal Australian Navy and US Navy Personnel. The High Frequency Transmitter (HFT) site building houses a number of transmitters, many of which are dedicated to point to point communication circuits. These circuits are established with shore facilities and navy surface ships operating within the station's area of communications responsibility.
My friend Eddy Waters (member of Utility DXers Forum) from Australia emailed me: "there seem to be transmitter site changes happen at different times of the day. Sometimes these signals come from Exmouth Western Australia, sometimes from Lyndoch, New South Wales, sometimes from Humpty Doo, Northern Territory. There are more and more frequencies changing over to the ISB STANAG setup that you describe".
 
Fig. 5

As far as I know, RAN fleet broadcasts come in using the GA-205 in a 6-channels configuration, it's not clear to me the use of 12-channels that - moreover- transport the same payload. I tried to reshape the stream to a 6-bit frames format (and 6-bit multiples)... but the KW-46 synch missed. By the way,  it's interesting to mention the KW-46 secured transmissions (probably also them from RAN) reported here: https://i56578-swl.blogspot.com/.../kw-46-secured-traffic-over-188-110a.html
 
[1]  https://www.yumpu.com/.../ga-205-time-division-multiplexer
[2] I used the term "flat multiplexed" to mean the fact that no classified multiplexing algorithm seems to be used.

24 May 2019

KG-84, KW-46, ...

In this blog I often use terms like "KG-84", "KW-46", "BID",..., as well as the names of other cryptographic devices, but this does not necessarily mean that those devices are physically used ashore or on aboard of ships! Rather than to the equipments, those names must be understood as referring to the used "algorithms", since - unless few exceptions - many of those devices are now obsolete and no longer used. Actually, the algorithms are emulated by interoperable and more compact devices such as - for example - the KIV-7M Programmable Multi-Channel Encryptor that can be used for communicating with a KIV-7 family device or the older KG-84/BID family of devices.
In general:
KG means Key Generator which could be used with any digital input device;
KI is for data transmission;
KW is the prefix for a Teletype encryption device;
KY stands for a voice encryption device. 

Also note that these products are only used by the US Government, their contractors, and federally sponsored non-US Government activities, in accordance with the International Traffic in Arms Regulations (ITAR), as well as by NATO and by the administrations of some NATO countries.

22 May 2019

THALES HFXL, "wide band link" phase? (tentative)
AngazU, i56578


In our recent THALES HFXL monitorings we noted an initial "leader" burst which is exchanged in each frequency of the channel between the peers, the exchanges occurs after the 2G-ALE phase and just before the traffic starts: in our guess it appears to be the "wide band link", i.e. the third step of the HFXL link establishment procedure.
The used waveform is the same of HFXL-S4539: you may note the presence of the Thales "extented" preamble in Fig. 1

Fig. 1 . the presence of the THALES extened preamble following the S4539 normal preamble
It's interesting to note that after removing the mini-probes, the data blocks symbols show a regular structure of 768 bits (!), i.e. the 256 tribit data symbols of the S4539 framing appear as composed of repeated sequences/data; indeed, such a perfect 768-bit period does not occur in cases where user data such as chat, HTML, FTP, emails,... are sent. The presence of such repetitions is also clearly visible at a glance in the bistream (Fig. 2).

Fig. 2
Another clue in favor of repeated sequences in the data blocks is the ease with which the autocorrelation of 27648 bits is detected (Fig. 3): that's the length of the inteleaver block and just thanks to repeated data that it's possible to mark it. Also, the strong result of the autocorrelation leads to think of the use of Walsh Orthogonal Modulation, although it's not provided in S4539. Indeed, the detection of the interleaver length is facilitated because the last di-bit in any interleaver block is identified by the use of alternate set of Walsh sequences.

Fig. 3 - result from the autocorrelation
AngazU edited a header to eliminate the miniprobes (roughly)  and the resulting ACF is 26.6 ms considering both polarities and 13.3 ms considering only one. This indicates that it could be a walsh code of 32 symbols that is repeated inverted (Fig.4): 64 (32+32) symbols lasting ~26.6ms makes a data rate of 2400 Baud.
But be careful, it's just a speculation! We'll need a good quality recording to demodulate it and to verify it at  bit level.

Fig. 4

From the above, we think that the initial bursts use Walsh modulation and are used as a negotiation phase before the traffic starts: possibly we are facing with the "wide band link" (Fig. 4) that makes use of the "Cognitive Engine" software during the link establishment procedure, taking into account information on MUF, requested SNR, noise level, propagation modes, antenna performances.
As said, the above are only our hypotheses, we do not yet have any confirmation of them. Comments are welcome.

Fig. 4 - HFXL link establishment procedure