Академический Документы
Профессиональный Документы
Культура Документы
1 Goal
This format will be used to exchange microwave data between telecommunication operators and the regulatory
commission. It will be used under those circumstances:
- The regulator can ask the operator a file with all its links to initialise its own database. In order to fulfil its
mission of assigning, coordinating, and notifying microwave links, the regulator may need some
administrative or technical parameters that were not communicated by the operator in the past but may
have become necessary to take into account the evolution of techniques and international practices.
- The operator may send its application forms for new links as a file, this will allow for an automatic import
of data inside the regulator’s database, with two advantages : data imported quickly and with no error.
- The regulator can send as a file the operator’s links back to the operator with supplementary information
so as the link’s status (rejected, accorded, coordinated, notified), the frequencies assigned to the link, the
link’s annual fee…
2 Description of format
The data file consists of one table with one record per microwave link ; it may be sent in two forms :
- Either a .CSV file delimited with comma or semicolon ; (You may use Microsoft Excel o a similar tool
to input the data, then save as a CSV file. Be aware that you may lose some information in the process,
for example the digits after the decimal point may be limited to two; In the Windows control panel, in
regional preferences, check the number of digits after the decimal point : 4 at a minimum, check the
delimiter : comma or semicolon) check the date format : Day/month/year)
Date fields must be entered either as an integer calculated with the formula (Year*10000)+
(Month*100)+Day (19991123 holds for 23 nov 1999), either with the form
<day>/<month>/<year> (23/11/99 or 23/11/1999 for 23 november 1999)
The first line of the CSV file must hold the column names (uppercase or lowercase).
Note:
- Some of the information is facultative ; if you don’t have the information, it is possible to omit the
column in the CSV file or in the MDB table (For example, colunns AL_EMAIL et BL_EMAIL may be
skipped if you don’t have the email address of the guy esponsible for a site.)
- The order of columns may be changed
- New columns can be added in the exchange file, under the condition that the first letter of their name
be different from L, A, and B. They will be ignored by the regulatory instance.
Sample files will be provided by the regulator to the operator with sample links.
Each line of the file allows to input a simple unidiectional or bidirectional link :
A_FREQ is the frequency transmitted from A to B, and B_FREQ the frequency transmitted back from B to A.
Sub tables
The regulator’s database is organized into specific sub tables for :
- Geographic positions (Precise geographic coordinates of the transmitting tower)
- Frequency plans
- Emission equipments (more precisely equipment configurations, whose characteristics are ITU
Designation of emission, reception thresholds,…)
- Antenna models, as described in the antenna manufacturers catalogs, for example Andrew VHP4-77
- A microwave link table with references to operator, equipment, antenna, frequency plan,
When the regulator imports link data from the operator, the antenna… equipment objects must be identified or
created in the regulator’s database so it is very important to take care of the so called “key” fields :
Let’s take the antenna model as an example :
- If the operator’s database has its own antenna model table, then the pimary key of this table should be
copied into the AA_KEY column : When the regulator imports for the first time a record with the value
AA_KEY= xxxx1(for example), a record is created into the regulator’s database and will be initialised
with the values from the AA_MANUF, AA_MODEL, and so on... Later, as soon as the value 'xxxx1' is met
we can retrieve the already created antenna model and reuse it for the new link. Please take note that the
regulator’s database records the primary keys of your database.
- If the operator’s database does not have its antenna model table, then leave the AA_KEY field blank.
Fields list
Each field has a name; the first letter of that name can be ‘L’, ‘A’ or ‘B’ ; The L prefix identifies a link
characteristics, whereas a A or B prefix identifies a characteristics of one of the two stations. In fact, all fields
beginning with a A have their counterpart beginning with a B, since a bi-directional link is a symmetrical
object.
In the following, the character ‘*’ is indicating a A or a B.
Link table
L_… : General informations on the link
L_OPID Char(20) Facultative : The operator ident for this link. When the
regulator sends link data back to the operator, this ident will
be included and help the operator retrieve the link it refers to
in his database. The operator can put whatever he wants in
this field (limited to 20 characters)
L_BIUSE Date Mandatory : Bring Into Use date
L_EOUSE Date End of use date (if known)
If the link is a temporary link, the information is mandatory ;
on the contrary the operator must leave the field blank.
L_APPL_DAT Date Mandatory : Application date
L_APPL_REF Char(20) Mandatory : Application operator’s reference
L_APPL_REM Char(100) Facultative : Operator’s remarks concerning the link
L_MBIT_S Number Mandatory : link bitrate in Mbit/s
L_PROGRAM Char(50) Facultative : Name of the broadcast program
L_BW Number Mandatory : Necessary bandwidth (kHz) needed by the link;
must be equal to the channel separation in the used frequency
plan
L_OPERATOR Char(50) Mandatory : Name of the operator operating the link, if
different from the licencee. A short name will suffice. The
operating operator is the one the regulator should contact in
case of interference or other operating technical problem.
L_STUDY_DATE Date Date of technical study by the regulator. Only the regulator
can fill in this field
L_STUDY_AUTHOR Char(3) Person who has done the technical study
Only the regulator can fill in this field
L_AVIS_ART Char(1) Regulator outcome following technical study :
C Agreement
D Agreement with comments
E Agreement under conditions
Z Refused
Only the regulator can fill in this field
LP_KEY Char(50) Facultative : Key for the frequency plan. Fill in this field only
if a given key value implies always the same value in
following fields.
LP_PLAN Char(16) Name of the fequency plan Ex : 38G-14M
Mandatory if the link is to be assigned a frequency plan
channel.
LP_CH_SEP Number Channel separation in kHz
Mandatory if the link is to be assigned a frequency plan
channel.; must be identical to L_BW
Remark 1 : A link can refer to only one frequency plan ; if a bidirectional link has Go and Return frequencies
belonging to distinct plans, you have to declare two unidirectional links.
Une liaison ne peut faire référence qu’à un seul plan de fréquence, si une liaison bidirectionnelle utilise une
fréquence Aller et une fréquence retour appartenant à des plans de fréquence différents, alors il faut déclarer
séparément deux liaisons unidirectionnelles.
Remark 3 : The frequency plan channel description is a public information that should not be included into the
exchange file ; starting from the frequency plan reference and the assigned frequencies in MHZ, the regulator
can retrieve the channel number.
Sub-table of users
LO_… : Prefixes owner of the link characteristics (O=Owner)
It will be the licensee (the applicant) ; if the licensee delegates the operation of the link to some other operator,
then this operator will appear in the L_OPERATOR field. The Licensee/Owner is the one who owns the licence
and may have to pay for it.
LO_KEY Char(50) Facultative : User primary key. Fill in this field only if a given
key value implies always the same value in following LO_
fields.
LO_NAME Char(50) Facultative : Applicant name Ex: “Bandit
telecommunications”
LO_IDENT Char(32) Facultative : Do not fill
LO_REPRESENT Char(50) Facultative : Contact name
LO_ADDRESS Char(100) Facultative : Adress (it is a multiline field, 3 lines maximum)
Ex : « First bank building
Plot 5, Imam Abib Adetoro str., off Ajose adeogun »
LO_POSTCODE Char(10) Facultative : Zip Code
LO_CITY Char(50) Facultative : City
LO_PROVINCE Char(50) Facultative : Province (state)
LO_COUNTRY Char(3) Facultative : Country
LO_TEL Char(20) Facultative : Phone number
LO_FAX Char(20) Facultative : Fax number
LO_EMAIL Char(50) Facultative : Email address
Remark 1 : Beware, the equipment defined in this table may be different from the equipment defined in the
operator’s database ; Fill in LE_KEY only if there is a good match. In particular from the regulator point of
view the nominal power is a characteristics of the link, and the designation of emission is a characteristic of
Attention, l’équipement défini dans cette table peut être différent de la table des modèles d’équipements de
l’opérateur ; Pour l’ART la puissance nominale de l’équipement est une caractéristique de la liaison, mais la
désignation d’émission est une caractéristique de l’équipement. Si l’opérateur utilise LE_KEY, il doit être sûr
que cela implique toujours la même désignation d’émission.
Remarque 2 : Si la station A est un passif il faut laisser les champs LE_… vides ;
Par localisation géographique, il faut entendre la coordonnée géographique précise du support de l’antenne, et
non un site plus ou moins étendu ;
Remarque 1: Si l’antenne utilisée sur la station B est identique à celle utilisée en Station A, il est possible de
laisser l’ensemble des champs BA_… vide ; l’ART prendra pour défaut l’antenne de la station A (AA_…).;
Enfin si toutes les liaisons du fichier sont dans ce cas il est possible même de supprimer les colonnes BA_… du
fichier.
Remarque 2 : Si la station A est un passif plan il faut laisser les champs AA_… vides ; Si la station B est un
passif plan il faut laisser les champs BA_… vides.
Paramètres techniques
A_… Champs décrivant les paramètres de la liaison côté station A
B_… Champs décrivant les paramètres de la liaison côté station B
Remarque 1 : Si le fichier ne contient aucune liaison avec passif, il est possible de supprimer les colonnes
A_PASSIVE et B_PASSIVE, la valeur par défaut s’appliquant alors.
Remarque 2 : La PIRE ne fait pas partie du fichier, car ce champ est recalculé par l’ART ;
- En cas de station non passive, la formule utilisée est la suivante :
(Si A_PASSIVE=0)
PIRE(dBW)= A_NOM_POWER(dBm)-30+AA_GAIN(dBi)-A_TX_LOSSES(dB)
- En cas de passif réflecteur plan, il est tenu compte de la surface du passif (B_PSURFACE);
- En cas de passif back to back, il est tenu compte du gain des antennes et des pertes du dispositif
(B_PLOSSES) affaiblissement guide d’ondes, etc…
Liaisons unidirectionnelles
Si la liaison est unidirectionnelle, on placera l’émetteur en A et le récepteur en B.
Un champ B_FREQ non rempli indique que la liaison est unidirectionnelle ;
Réflecteur passif
Cas d'une liaison utilisant un réflecteur passif plan ou back to back :
Il faut utiliser deux lignes consécutives (dans l’ordre indiqué) pour coder cette liaison :
L'ART reconstituera une seule liaison avec passif; Le deuxième enregistrement présente les contraintes
suivantes :
- Le champ L_OPID peut être différent, mais seul le premier sera mémorisé par l’ART (L’ART ne
mémorise qu’un identifiant par liaison, aussi si l’opérateur a deux identifiants pour les liaisons de
part et d’autre d’un passif, seul un des identifiants sera retenu)
- Tous les champs commençant par L_ devraient être identiques, aussi l’ART ignorera leur valeur
sur la deuxième ligne. On peut parfaitement ne pas les renseigner dans le deuxième
enregistrement.
- Les champs LE_(ligne 2) ne doivent pas être remplis : un passif ne possède pas d’équipement ; Ils
seront ignorés
- Si les champs BA_(ligne 2) ne sont pas remplis, l’ART prendra pour défaut la valeur des champs
AA_(ligne 1) : L’antenne par défaut pour la station 2 est celle de la station 1.
- Tous les champs AL_ et BL_ doivent être remplis.
- B_AGL2(ligne 1) et A_AGL2(ligne 2) seront ignorés : pas de diversité d’espace au niveau du
passif.
- B_TX_LOSSES(ligne 1), B_RX_LOSSES(ligne 1), A_TX_LOSSES(ligne 2),
A_RX_LOSSES(ligne 2) sont ignorés
Diversité de fréquence
Cas d'une liaison utilisant la diversité de fréquence : Si la station A émet fA1,fA2,fA3 et reçoit de la station B
les fréquences fB1,fB2 il faut décomposer en trois enregistrements :
Station A fA1 <-> Station B fB1
Station A fA2 <-> Station B fB2
Station A fA3 <-> Station B -
L'ART ne gère pas la diversité de fréquence et considérera avoir affaire à trois liaisons indépendantes.
Il n’est pas gênant pour l’ART que ces trois liaisons aient le même identifiant opérateur (L_OPID)