Add passage explaining basic visualisation of stat and rate counter items
with Netdata so user can start utilizing them without any special
configuration.
Related: OS#5671
Change-Id: I124503c3707bbe005abbfb4245abe2829c6ff57c
The files gb-nsw-{configuration-timer,configuration,maintenance} were
not actually chapters, but sub-chapters or sub-sub-chapters. This
breaks our general idea that all of those files are top-level chapters.
It also breaks asciidoc validation on Debian 11:
asciidoc: WARNING: gb-ns2-configuration.adoc: line 1: section title out of sequence: expected level 1, got level 2
asciidoc: WARNING: gb-ns2-maintenance.adoc: line 6: section title out of sequence: expected level 2, got level 3
the only place where they were used was the osmo-gbproxy manual, and
there in the exact sequenc in which I now merged them over here.
Change-Id: I3c618e5af61b376435f400ef9c64245cec2f9b73
... this can be included from the various user manuals to insert some
general language about the systemd service units we ship, and a few key
systemd commands to get users started.
Change-Id: I8b04047cbc4097676d69fad794bb3139c05a4a5f
Copied from osmo-bsc.git/doc/manuals/chapters/mgwpool.adoc, version from
Change-Id Id0d292506e8b2a888c8d7a682a38db80e9d0933a
Related: SYS#5987
Change-Id: Ieda0d4bfe6fc90da6e19c791d8ec2da89427ba3b
Both Synch. sequence and Training sequence are basically the same thing,
only the length is different. I guess this is why 3GPP TS 45.002 names
them differently. Let's mention them both to avoid confusion.
Change-Id: I092af5ef6b66f8bdbd46cc3ae0c77fd806f2fe27
This has been the port used historically in most existing deployments,
and it's the one already documented in the osmux section of user
manuals.
Change-Id: I9593e484a0df7cbfc3fa68f071246e3fb714bd4c
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