Project

General

Profile

Actions

Feature #1771

open

osmo-bts-trx: clarify check_transceiver_availability()

Added by neels over 7 years ago. Updated about 6 years ago.

Status:
New
Priority:
Low
Assignee:
-
Category:
-
Target version:
Start date:
07/08/2016
Due date:
% Done:

0%

Spec Reference:

Description

The functions

  • check_transceiver_availability()
  • check_transceiver_availability_trx()

seem to be an important step in OML communication. Their main purpose is to send OML
states after receiving a Set BTS Attributes message.

However, they are named for their peculiar side-purpose to delay this step
in case the transceiver has not sent the first clock yet.

Also, it is clear that if the function were called twice, it would send Disabled
states for the RADIO-CARRIER and CHANNEL objects every time, without really
checking the transceiver availability.

Particulary, an erratic BSC might send a Set BTS Attributes out of sequence,
which would cause above OML objects to change to Disabled state immediately.

This is in need of clarification:

  • rename the functions
  • implement saner logic to detect availability transitions
  • comment lusciously

Related issues

Related to OsmoBTS - Bug #1770: osmo-bts-trx goes through OML initialization twiceClosedneels07/08/2016

Actions
Actions #1

Updated by neels over 7 years ago

  • Related to Bug #1770: osmo-bts-trx goes through OML initialization twice added
Actions #2

Updated by laforge over 7 years ago

  • Assignee set to neels
Actions #3

Updated by neels over 7 years ago

  • Priority changed from Normal to Low
Actions #4

Updated by laforge over 7 years ago

  • Target version set to osmo-bts-trx refresh
Actions #5

Updated by neels about 7 years ago

  • Assignee changed from neels to 118
Actions #6

Updated by laforge about 7 years ago

  • Assignee changed from 118 to msuraev
Actions #7

Updated by laforge about 6 years ago

  • Assignee deleted (msuraev)
Actions

Also available in: Atom PDF

Add picture from clipboard (Maximum size: 48.8 MB)