Binary Interchange of Information and Signaling is an ETSI-standard (ETS 300 230) used for transmission of signaling information for selective calls, status messages, short text messages and data.
|
Parameter |
Value |
|
Frequency range |
VHF/UHF |
|
Operation modes |
CRC and parity |
|
Modulation |
FM, SUB FFSK |
|
Symbol rate |
1200 Baud |
|
Center frequency |
1500 Hz |
|
600 Hz | |
|
Receiver settings |
FM, BW = 15 kHz |
|
Input format(s) |
AF, IF |
|
Additional Info |
Signaling data, Short Data transfer, HDLC possible, ETSI-standard (ETS 300 230) |
The system operates at 1200 Bit/s using indirect FSK modulation in the VHF or UHF band. To accommodate the different types of data, a number of code words have been defined. Every transmission consists of at least one address word. Additional data such as telephone numbers or short text messages may be appended to the address word as one or more data blocks.
For the transmission of longer data packets the High-Level Data Link Control (HDLC) protocol may be implemented in the BIIS devices.
Status messages are transmitted within the address word. The address word contains the Operational Mode Characteristic (OMC), a regional code indicating the country of the device, a common address part, the transmitter address and the receiver address. The address data is displayed in hexadecimal format. OMC code and regional code are displayed as short strings. There are 64 OMC codes consisting of a category part (CAT) and a function part (FNC). Some codes are custom, status or reserved codes. The following table shows all valid codes in string and binary representation.
OMC Strings
|
C |
A |
T |
F |
N |
C |
String |
|
0 |
0 |
0 |
0 |
0 |
0 |
EmRes |
|
1 |
0 |
0 |
0 |
0 |
0 |
Status1 |
|
0 |
1 |
0 |
0 |
0 |
0 |
EmAck |
|
1 |
1 |
0 |
0 |
0 |
0 |
Reser1 |
|
0 |
0 |
1 |
0 |
0 |
0 |
EmCall |
|
1 |
0 |
1 |
0 |
0 |
0 |
Status9 |
|
0 |
1 |
1 |
0 |
0 |
0 |
SysCon |
|
1 |
1 |
1 |
0 |
0 |
0 |
Cust1 |
|
0 |
0 |
0 |
1 |
0 |
0 |
TXKeyON |
|
1 |
0 |
0 |
1 |
0 |
0 |
Status5 |
|
0 |
1 |
0 |
1 |
0 |
0 |
BusyAck |
|
1 |
1 |
0 |
1 |
0 |
0 |
Reser5 |
|
0 |
0 |
1 |
1 |
0 |
0 |
BroCal |
|
1 |
0 |
1 |
1 |
0 |
0 |
Status13 |
|
0 |
1 |
1 |
1 |
0 |
0 |
VotNow |
|
1 |
1 |
1 |
1 |
0 |
0 |
Cust5 |
|
0 |
0 |
0 |
0 |
1 |
0 |
CleaDow |
|
1 |
0 |
0 |
0 |
1 |
0 |
Status3 |
|
0 |
1 |
0 |
0 |
1 |
0 |
GenAck |
|
1 |
1 |
0 |
0 |
1 |
0 |
Reser3 |
|
0 |
0 |
1 |
0 |
1 |
0 |
NorCall |
|
1 |
0 |
1 |
0 |
1 |
0 |
Status11 |
|
0 |
1 |
1 |
0 |
1 |
0 |
DiaDat |
|
1 |
1 |
1 |
0 |
1 |
0 |
Cust3 |
|
0 |
0 |
0 |
1 |
1 |
0 |
RepON |
|
1 |
0 |
0 |
1 |
1 |
0 |
Status7 |
|
0 |
1 |
0 |
1 |
1 |
0 |
IntermAck |
|
1 |
1 |
0 |
1 |
1 |
0 |
Reser7 |
|
0 |
0 |
1 |
1 |
1 |
0 |
ManRes |
|
1 |
0 |
1 |
1 |
1 |
0 |
Status15 |
|
0 |
1 |
1 |
1 |
1 |
0 |
MobEn |
|
1 |
1 |
1 |
1 |
1 |
0 |
Cust7 |
|
0 |
0 |
0 |
0 |
0 |
1 |
Cancel |
|
1 |
0 |
0 |
0 |
0 |
1 |
Status2 |
|
0 |
1 |
0 |
0 |
0 |
1 |
RepAck |
|
1 |
1 |
0 |
0 |
0 |
1 |
Reser2 |
|
0 |
0 |
1 |
0 |
0 |
1 |
PriCal |
|
1 |
0 |
1 |
0 |
0 |
1 |
Status10 |
|
0 |
1 |
1 |
0 |
0 |
1 |
ShorDat |
|
1 |
1 |
1 |
0 |
0 |
1 |
Cust2 |
|
0 |
0 |
0 |
1 |
0 |
1 |
TXKeyOFF |
|
1 |
0 |
0 |
1 |
0 |
1 |
Status6 |
|
0 |
1 |
0 |
1 |
0 |
1 |
CalBaAck |
|
1 |
1 |
0 |
1 |
0 |
1 |
Reser6 |
|
0 |
0 |
1 |
1 |
0 |
1 |
ReqCalBa |
|
1 |
0 |
1 |
1 |
0 |
1 |
Status14 |
|
0 |
1 |
1 |
1 |
0 |
1 |
SatusReq |
|
1 |
1 |
1 |
1 |
0 |
1 |
Cust6 |
|
0 |
0 |
0 |
0 |
1 |
1 |
MaintID |
|
1 |
0 |
0 |
0 |
1 |
1 |
Status4 |
|
0 |
1 |
0 |
0 |
1 |
1 |
AbsentUna |
|
1 |
1 |
0 |
0 |
1 |
1 |
Reser4 |
|
0 |
0 |
1 |
0 |
1 |
1 |
TelCall |
|
1 |
0 |
1 |
0 |
1 |
1 |
Status12 |
|
0 |
1 |
1 |
0 |
1 |
1 |
ChanCha |
|
1 |
1 |
1 |
0 |
1 |
1 |
Cust4 |
|
0 |
0 |
0 |
1 |
1 |
1 |
RepOFF |
|
1 |
0 |
0 |
1 |
1 |
1 |
Status8 |
|
0 |
1 |
0 |
1 |
1 |
1 |
RejAck |
|
1 |
1 |
0 |
1 |
1 |
1 |
Reser8 |
|
0 |
0 |
1 |
1 |
1 |
1 |
ExtAdr |
|
1 |
0 |
1 |
1 |
1 |
1 |
Status16 |
|
0 |
1 |
1 |
1 |
1 |
1 |
MobDis |
|
1 |
1 |
1 |
1 |
1 |
1 |
Cust8 |
Depending on the OMC code, the address word can be followed by one or more data words. Four such cases exist:
Telephone Call
One or more data words containing a telephone number are appended to the address word. The telephone number is displayed in the decoder output.
External Addressing
A datagram for external addressing consists of two address words. The first address word carries the transmitter address including the transmitter regional code and the second address word carries the receiver address including the receiver regional code.
Short Data Transfer
A short data transfer is very similar to the transmission of a telephone number. The address word is followed by some data words. The display format of the decoded information can be switched between binary, hexadecimal, and text data. Text data is displayed in ASCII format.
Dialog Data Transfer
In case of dialog data transfer the BIIS address word is followed by a HDLC control block. This control block is analyzed by the decoder module and the contents are displayed as plain text.
The control block consists of an address, a command-response bit, a control field indicating the frame type and a 32-bit parameter field in hexadecimal format.
I-frames and S-frames contain a receive sequence number N(R) or send sequence number N(S). The usual HDLC commands and responses are displayed in abbreviated form.
Data words following the HDLC control block can be displayed in binary or hexadecimal format.
In the case of system control data (OMC = 011000), a 6-bit custom code is transmitted instead of transmit and receive addresses.
Further information about the OMC coding, regional codes and the HDLC protocol may be found in the ETSI-standard ETS 300 230.
For validation of the code words, CRC and parity checks are used. If the CRC or the parity is incorrect the decoder output is displayed in red.