Product Description

nanoBTS Product Description Software Specification

Note that the value of the SW Configuration attribute in a SW Activate Request message

sent by an object is therefore not the same as that of the SW Configuration attribute

obtained by sending a Get Attributes message to the object. i.e. the SW Configuration

Attribute reported as a response to the "GetAttributes" message includes the "Boot

application"; the "Boot application" is not included in "SW Activate Request" messages.

Where a SW Activate Request contains more than one SW Description for a given image

type, the first one is the "default" image. An image can be selected (eg. under user control)

as the default image by sending a manufacturer-defined operations and maintenance

message, "Set Default SW" to the nanoBTS.

Note: The term "Boot" in "Set Default SW" does not refer to the nanoBTS’s boot code

image, it refers to the (backhaul and TRX) software that the nanoBTS should run

by default the next time it is rebooted.

The BTS expects to receive a SW Activate message in response to each SW Activate

Request that it sends. The SW Activate message may contain 0, 1, or more SW

Descriptions – and each of these must have been present in the corresponding SW

Activate Request message. If it contains no SW Descriptions, the object to which it is sent

will default to activating the most sensible default set of software. If it contains more than

one SW Description, they should be such that they can all be activated (for example, there

should not be more than one version for a given File Id).

Each managed object as defined in GSM 12.21 (Site Manager, BTS, Baseband

Transceiver, Radio Carrier, and Channel) has a SW Configuration attribute, which is a list

of one or more SW Description attributes. In the nanoBTS, each object’s SW Configuration

will contain a SW Description for each version of each of the images on which the object

depends. (An object depends on a software image if the physical item that it represents

requires the image to be executed before it can provide any service.)

Each 12.21 managed object has a HW Configuration attribute, which is a list of one or

more HW Description attributes. In the case of the nanoBTS, each object’s HW

Configuration attribute will contain exactly one HW Description, which will have the same

value for all objects. This HW Description relates to the PCB assembly inside the

nanoBTS.

The BTS’s Site Manager object sends a SW Activate Request containing a SW Description

for each backhaul software image that is present. The first (and perhaps only) of these

refers to the backhaul software that is currently running.

The BTS expects the BSC to send a SW Activate message containing either no SW

Descriptions, or one SW Description. If there is no SW Description or there is one and it

refers to the version of backhaul software that the BTS is currently executing, that is

marked as having been activated, and the procedure continues. If there is one SW

Description and it refers to the version of backhaul software in the other bank, the BTS

marks that version as the default, and restarts itself. On restart, the BTS executes the

version marked as the default, and repeats the software activation procedure. Note that it

shall not send anything else to indicate that it had to reboot (such as a FER). This time, the

Site Manager’s SW Activate Request message will include the SW Description for the

backhaul software that is now executing before the SW Description for the version that it

was previously executing.