Product Description

nanoBTS Product Description Software Specification

The BTS’s Baseband Transceiver object sends a SW Activate Request containing a SW

Description for the backhaul software image that was activated on the Site Manager

object, plus a SW Description for each TRX software image that is present. The BTS

expects the BSC to send a SW Activate message, which may contain no, one, or two, SW

Descriptions. If there is no SW Description, the nanoBTS will activate the "default" TRX

device software. If there is a SW Description for the backhaul, it must match that which

was sent in the SW Activate Request. If there is a SW Description for the TRX software,

the nanoBTS will load the specified version onto the TRX device and execute it.

The nanoBTS’s BTS object sends a SW Activate Request containing a SW Description for

the backhaul software image that was activated on the Site Manager object. The BSC

should send a SW Activate message to the BTS object containing either no SW

Descriptions, or the one SW Description that was in the SW Activate Request. In either

case the procedure continues. If the BSC sends a SW Activate message in response that

does not match any of its SW Descriptions then the BTS shall N’ACK the message.

The BTS’s Radio Carrier object sends a SW Activate Request containing one SW

Description for the backhaul software image that was activated on the Site Manager object

and one for the TRX software that was activated on the Baseband Transceiver object. The

BSC should send a SW Activate message to the BTS object containing either no SW

Descriptions, or one or both of the SW Descriptions that were in the SW Activate Request.

In either case, this is the end of the software activation procedure, and the other

procedures associated with starting up the BTS can be carried out.

5.14 Abis Interface (ABIS)

The BTS conforms to the ip.access Abis Over IP specification.

5.14.1 Operations and Maintenance Signalling Messages

The BTS supports Abis messages according to the ip.access Abis Over IP specification

and as clarified below on both primary and secondary OML links.

The BTS initiates the "Primary OML Establishment" procedure to the defined

"primaryomlipport" parameter in EEPROM configuration. If this is set to the NULL value

(see section 5.12) then the BTS shall use the vendor specific port number as defined in the

software build (IPA BSC = 3002).

The BTS supports the "Connect IP Signalling" message according to the ip.access Abis

Over IP specification.

The BTS supports the "Set Default SW" message according to the ip.access Abis Over IP

specification. This has the effect of adjusting the EEPROM parameter so that on the next

reboot the BTS will boot the specified Backhaul Index (see section 5.4.1). It will also use

the "default" set indexes (for Backhaul and TRX) as its first preference offered to the BSC

in the SW Activation procedures.

On receipt of new configuration the BTS will immediately use the configuration for the

NVConfig Flags F7-F9. Note that in the case of F9 (Second OML Enable) that this does

not disconnect current connections, but stops new connections.

The BTS will adjust the Frequency control immediately upon receipt of new configuration

of the "Frequency Control" IE.