How and when socket statistics are generated is not immediately obvious.
Lets add some documentation about it.
Change-Id: Icb06b3934e9ea5f3526263dc8915bc3529a64324
Related: OS#5701
Introduce a new flag (1-bit field) indicating whether a VAMOS PDU
is for a _primary_ ('0'B) or for a _shadow_ ('1'B) timeslot. This
field shall be present only in the Uplink VAMOS PDUs, which unlike
the Downlink (AQPSK) PDUs are sent separately. This will simplify
routing of such PDUs in osmo-bts.
Change-Id: Ie00a12824938c6a65480bde1af364dcc9febb8f7
Related: SYS#4895, OS#4941, OS#4006
It's unclear why it was removed in I5fe6263ac666e41cbe34407f09e9023aafa57d2c
when common/chapters/glossary.adoc of this very same repository uses it.
Change-Id: Ib8d2f22450a84ed802b34845ad19a7af8d6b7968
This field will also appear in TRXDv2 packet diagrams, in several
places. Let's rename it to 'RFU', because it's actually something
that may want to use in the future, rather than just padding.
Change-Id: I9ac9d387325627d18811fae1d0d7930b69f08129
Related: SYS#4895, OS#4941, OS#4006
* Add 'referred to as NOPE.ind', this is how we usueally call it;
* Change 'IDLE / NOPE' to 'NOPE / IDLE', because:
** there can be 'IDLE TDMA frame', but not 'NOPE frame';
* Avoid using 'high' and 'low' terms for bit values.
* Introduce and use macros for '0'B and '1'B.
Change-Id: I72e0c785efb8a89b664486740ef312e77b81c01a
Related: SYS#4895, OS#4941, OS#4006
Merge gb-variants.adoc into gb-ns2.adoc
Add a general overview of the internal structure which is also used
by the vty.
Move the configuration into a seperate adoc to allow the PCU manual to skip
the part which doesn't apply for it.
Copy the timer configuration into gb.adoc to allow document newer
timers. All users of the NS2 code will use the timer sub-chapter.
Related: OS#5077
Change-Id: I902b850528cbc04bd469590babd84cccf64300e8
The way how the indicated Training Sequence Code is supposed to be
used by the BTS is behind the scope of this protocol specification.
Change-Id: Ibcb0b6bfff0aa80ed2de563b5e749b7811e7a5c2
Related: SYS#4895, OS#4941, OS#4006
AQPSK is used exclusively on Downlink in VAMOS mode. An AQPSK burst
is basically a combination of two Normal Bursts. Each of these two
bursts has the same length as defined for GMSK, while both must be
using Training Sequences from different sets.
Four different sets are defined in 3GPP 45.002, section 5.2.3.1.
Therefore we need *two* bits to encode all possible values. Let's
rearrange the existing combinations and use '11XX'B for AQPSK. The
old combination '011X'B becomes reserved and can be re-purposed.
This change is considered to be safe, given that no implementations
are known to support AQPSK at the moment of making this change.
Change-Id: Ie9b419e4a70fa0eb2888c326ac50d2d40a67a29c
Related: SYS#4895, OS#4941, OS#4006
The chapters are not 100% finished, as there is still some
implementation work going on in terms of the libosmogb 'ns2' code
as well as the introduction of the SGSN pool feature to osmo-gbproxy.
Change-Id: I0ba2ed2a72db52a7282f4f1055812644421b2a98
The VTY features a method to associate commands with certain
attrubutes. Tell the VTY user how to use the help to display the
attributes and their meaning.
Change-Id: If03e07f1f8e7e3c0166a00e3f395e2a46a9a7713
Related: SYS#4937, OS#1601