Product Description

nanoBTS Product Description Software Specification

• the "Beacon mode" test to enable other basestations to monitor it. This test is

configurable to set the BSIC, ARFCN and transmit power to be used. The test

continues until a "Stop Test" request is made. The transmitted BCCH information

marks the cell as "barred" for all access types.

NWL tests will take the BTS out of service for the duration of the test. The BTS will restart

service after the test is complete. A state change event report is generated at the

beginning and end of the test.

5.13.2 Normal Operation

After boot-up and POST (if enabled), the BTS attempts to connect to Primary OML (as

indicated in IP and Port number settings in database).

Once connection is established, it uses "heart-beat" connection message as defined in the

ip.access Abis Over IP specification to detect if connection has gone down.

The BTS starts up a second OML server (if enabled in NV Config flag F9). It uses the

second OML port specified in NV, or if this is NULL then assume a default of 3006. If the

second oml IP address field is not NULL then it should reject connections from IP

addresses that are not the same. SW activation can occur on either primary or secondary

OML.

On loss of the second OML client the BTS does not reboot. Interrupted procedures are

terminated and do not take effect.

Once the BTS has established any OML connection it performs a "SW Activation Request"

for the Site Object.

Once the BTS has performed the "SW Activation" for the Site object it performs a "SW

Activation Request" for the Baseband Transceiver Object.

Once the BTS has performed the "SW Activation" for the Baseband Transceiver object it

will perform a "SW Activation Request" for the BTS object.

Once the BTS has performed the "SW Activation" for the BTS object it performs a "SW

Activation Request" for the Radio Carrier Object.

The BTS shall send "State Change Event Report" messages at the appropriate times (as

defined in GSM 12.21) whenever the managed object state changes.

5.13.2.1 SW Activation Procedure

The HW Configuration attribute in the SW Activate Request is the same for all objects, and

is the same as would be obtained by sending a Get Attributes message to an object.

The SW Configuration attribute includes at least one SW Description for each type of

image that it is dependent on, excluding boot code.

Note: The boot code has already finished executing by the time software activation

occurs, so there is no need to activate it.

If, when an object sends a SW Activate Request, a version of an image that it depends on

has already been activated, it only includes that version’s SW Description, otherwise it

includes a SW Description for each version of the image that is available for activation.

If the same software version is in both banks, then both banks shall be reported where

applicable (see above).