The assignment-format

Like with the scenario-format, we have a start section following "FORMAT" that contains information on the type of the format and the version of the format. This is useful for future extensions.

The data for the carriers is given in tuples in a cell-by-cell fashion. A tuple contains the ARFCN of the assigned channel (or an indicator that no channel is assigned) and the changeability status. For each cell, tuples are listed according to the implicit order of the carriers associated to the cell. First, carrier 0, then carrier 1, and so on.

FORMAT {
   TYPE                              ASSIGNMENT;
   VERSION                           1.0;
}
 
GENERAL_INFORMATION {
   SCENARIO_ID                       name;
   NAME                              text;
  [ANNOTATION                        text;]
}
 
CELLS {
 ( cell_idi { (carrier status)>=1; })>=0
}

All notation and all types except for the ``carrier status'' have already been used in the definition of the scenario-format (see section 3.2).

carrier status

The carrier status is a pair containing the assigned channel and the changeability status. In case no channel is assigned, a dash ('-') used. If the carrier assignment is unchangeable, a zero ('0') is given. In case the assignment may be changed, the entry is '+'. Formally, such a tuple looks as follows: '(' ( int | '-' ) ',' ( '0' | '+' ) ')'.

It is not an error to list a cell_id for which no cell is given in the corresponding scenario. In case there is a cell in the scenario for which no assignment is listed or for which too few assignments are listed, all carriers not explicitly specified are implicitly set to be unassigned and changeable, i.e., this is equivalent to specifying "(-, +)".