Quantcast
Channel: diario SWL I-56578 Antonio
Viewing all articles
Browse latest Browse all 623

Rus Datalink: a parsing approach

$
0
0

Just a few unpretending notes as a result of web searches regarding the datalink signal, we have currently been monitoring, in particular about the format (69,48), where 48 bits are data, that for example can be heard on 6123.5 kHz, USB during daytime. The information below refers mostly to the AI-011 (АИ-011) device [1]: a DCE (Data Communication Equipment) for mobile systems designed to protect and transmit telecode data(the generic Russian term for radar data) over standard channels of wired, cable, radio relay, tropospheric and HF communication lines. The data transfer rate is 600 or 1200 bits/s FSK. 

Please note that translating from Russian is never easy, I relied on Yandex Translate tool and the acronyms highlighted in orange are just their English translation.

AI-011 (S23) provides operation in duplex, half-duplex and simplex modes. In duplex mode, data blocks are transmitted and received simultaneously also using ARQ. In half-duplex mode the correspondents take turns in transmitting and receiving. In simplex mode the device provides either transmission or reception of data blocks. When exchanging radar information with external subscribers, it ensures the implementation of the exchange protocols:

* AKKORD-SS-PD (АККОРД-СС-ПД) in blocks of length (165, 144) and (69, 48) bits - equipment 55Ts6; in blocks of length (165, 144), (117, 96) and (69, 48) bits - equipment R-050 ;

* IRTYSH (ИРТЫШ) in blocks of length (69, 48) bits - equipment T-235-1L.

When data transmission is carried out in blocks with a length of 69 (or 117) bits, 5 of them are service bits (m,C), 16 (I) are used for error detection and correction and the remaining 48/96 bits (K) are used for data:

Fig. 1 - 69 (117) bit format
 
If bit C = 1, the four m bits indicate the address of the correspondent in binary code: when receiving a data block, the receiving device compares the address of the data block with its own address and if they do not match, the data block is ignored. In addressed mode up to 16 subscribers may be accommodated on the same communication channel. When working without an address, i.e. when   C = 0, the first and second bit m1, m2 define sub-modes: the first element indicates the DRS sub-mode (FEC mode?), the second the DRO sub-mode (ARQ mode?). The third and fourth service bits m3, m4 are used only in duplex mode: m3 is used to transmit an acknowledgement of a received data block, m4 is used to signal the channel status.

The 53-bit strings (m1,m2,m3,m4 + 48-bit data + C) are fed into the FEC encoder which performs a cyclic division by the polynomyal x^16+x^12+x^5+1: the 16-bit remainders (CRC bits) are then appended to the source messages. Because the transmission is synchronous, phasing (synchronization) is carried out with the help of a special pattern which differs in structure from the structure of the payload data messages and consists of a recurring sequence of 69 bits, generated by the polynomial x^8+x^6+x^5+x^4+1. While analyzing the phasing pattern, the error protection decoder circuit will generate an error signal, since the phase combination is formed on the basis of a different polynomial.

The information is transmitted to the communication channel by three types of messages with the following priority:
1. Coordinates of the radar station and information about its operating modes.
2. The coordinates of the targets and bearings on the directors of the ASP.
3. Coordinates and signs of goals and a sign of the ROLE removal channel (automatic or PASS).
Messages of the first priority are issued three times.
I only found the format of the of the third priority message (figure 2): according to a web source [2] it should be the T-235-1L equipment and thus the IRTYSH (69,48) algorithm... but it could be wrong or misleading.

Fig. 2 - structure of the 3rd priority message (69,48)

In addition to radar information, AI-011 sends information about the position of the radar station, which is derived from the navigation and orientation system or from a topographic map. At the same time, X and Y coordinate values in a rectangular coordinate system are entered with signs, and the value of the height coordinate H, and also the magnitude of the angle of direction (likely referred to the target)..

Well, honestly the information I have does not allow for further progress as:
a) we do not know which equipment is used and therefore which algorithm/protocol is used to transfer the data, i.e. if we have to deal with AKKORD-SS-PD or IRTYSH protocol as both provide the same data format (69,48)
b) consequently, we are neither able to determine synchronization nor the correct polarity of the bit stream which in turn involves the parsing of bits m and C (and - obviously - the meaning of the 48-bit data block)
c) we do not know the way the three types of messages are signaled (if any) and therefore we do not know which 48-bit structure we are analyzing: i.e.  it may be that the data fields of messages we observe have a different format an consequently a different interpretation than the one shown in figure 2.
 
However, a couple of remarks seem to be in place:
1. The value of the 4 m bits (0101 or 1010) is the same in all messages that have been demodulated, so it's reasonable to assume that the system works w/out address: if so, the right value of bit(s) C should be "0"  and the DRS sub-mode set (unless all messages are addressed to a single subscriber).
 
2. Assuming that the bitstreams are structured according to figure 2, you may notice that the first byte of the messages (fields: a, b, c, d, e) assumes alternately always the same values and that suggests that the same "type" (priority) of message is being transmitted:
 
m      a     b c  d  e T              H                X                      Y
0101 111 1 0 10 1 11111011 11111111 1 11110111111 1 11011101011 1
0101 001 1 1 00 0 10011110 11101010 1 00110111111 0 01110000111 1
0101 111 1 0 10 1 10011110 01011111 1 11110011110 1 11011011010 1
0101 001 1 1 10 0 11111010 11101011 1 00010101011 1 01100001100 1
0101 111 1 0 10 1 11111010 11101111 1 11110011100 1 01111111001 1
0101 001 1 1 00 0 10011111 11101011 1 00010100111 1 01100001100 1
0101 111 1 0 10 1 10011111 01011111 1 11110011100 1 01111111010 1
 
3. Likewise, the values of the T (time) field are repeated either individually:
 
m      a     b c  d  e T              H                X                      Y
0101 111 1 0 10 1 11111011 11111111 1 11110111111 1 11011101011 1
0101 001 1 1 00 0 10011110 11101010 1 00110111111 0 01110000111 1
0101 111 1 0 10 1 10011110 01011111 1 11110011110 1 11011011010 1
0101 001 1 1 10 0 11111010 11101011 1 00010101011 1 01100001100 1
0101 111 1 0 10 1 11111010 11101111 1 11110011100 1 01111111001 1
0101 001 1 1 00 0 10011111 11101011 1 00010100111 1 01100001100 1
0101 111 1 0 10 1 10011111 01011111 1 11110011100 1 01111111010 1

or in groups:
Fig. 3

By the way, 8 bits are too few to represent a significant time marker when related to a radar track: 16-bit T+H fields would make more sense. In this regard (what are the actual meanings and lengths of the message fields we are seeing) a large field of hypotheses opens up: several solutions can be tried by processing the bitstreams with a spreadsheet to (re)organize, filter, sort and merge the data fields [3].
 
4. The messages are separated by the 69-bit sequence (figure 4):
001010101010101010101010101010101010101010101010101011101000101000000
or splitt into "reversals" +  "0xD1 0x40" (the two bytes belonging to the sequence generated by the polynomial x^8+x^6+x^5+x^4+1):
00101010101010101010101010101010101010101010101010101 11010001 01000000
Don't know if it's used as phasing/sync between messages or in absence of messages to be sent.
 
Fig. 4

That is not the only repeated sequence that is used: indeed, long periods of absence of traffic (sometimes more than one minute) are characterized by the sending at regular intervals (5.4 sec) of the sequence:
101011110110000000011110100001110010111111101110001110110100011111100

Fig. 5

The same sequence is also inserted within the messages stream, apparently without a precise criterion:

Fig. 6

5. In addition to the C bit, two additional (service?) bits emerge which seems to have the function of separators and divide the 48-bit data block into three fields of 1, 2 and 3 bytes but that is speculative (see fig. 7). It's worth noting that, according to [4][5], AKKORD-165 formatted messages may be divided into 6 words of each 24 bits, the number of words depends on the messages length, i.e. 2, 4 or 6 words (48, 96, 144 bit length messages).

Fig. 7

[1] https://vunivere.ru/work3160/page51
[2] https://disk.yandex.com/i/foPNyfiDpCHGPw
[3] https://disk.yandex.com/d/NjiybR9nwwUE9g
[4] https://studizba.com/files/show/doc/209357-4-1.html AKKORD-SS-PD (AKKORD-165)
[5] https://studbooks.net/1194685/bzhd/razrabotka_funktsionalnoy_shemy_peredayuschey_chasti

 


Viewing all articles
Browse latest Browse all 623

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>