Change in osmo-bts[master]: Abis manual: add RSL_IE_OSMO_TRAINING_SEQUENCE

laforge gerrit-no-reply at lists.osmocom.org
Sat Apr 24 08:44:52 UTC 2021


laforge has submitted this change. ( https://gerrit.osmocom.org/c/osmo-bts/+/23849 )

Change subject: Abis manual: add RSL_IE_OSMO_TRAINING_SEQUENCE
......................................................................

Abis manual: add RSL_IE_OSMO_TRAINING_SEQUENCE

Change-Id: Ie583bd5969fdb45f772af198033e58d7c4077306
---
M doc/manuals/abis/rsl.adoc
1 file changed, 74 insertions(+), 0 deletions(-)

Approvals:
  neels: Looks good to me, approved
  laforge: Looks good to me, but someone else must approve
  dexter: Looks good to me, but someone else must approve
  Jenkins Builder: Verified



diff --git a/doc/manuals/abis/rsl.adoc b/doc/manuals/abis/rsl.adoc
index 35fda31..7b45acf 100644
--- a/doc/manuals/abis/rsl.adoc
+++ b/doc/manuals/abis/rsl.adoc
@@ -843,6 +843,7 @@
 | IEI  | Name | This document §
 | 0x01 | RSL_IE_CHAN_NR | <<RSL_IE_CHAN_NR>>
 | 0x60 | RSL_IE_OSMO_REP_ACCH_CAP | <<RSL_IE_OSMO_REP_ACCH_CAP>>
+| 0x61 | RSL_IE_OSMO_TRAINING_SEQUENCE | <<RSL_IE_OSMO_TRAINING_SEQUENCE>>
 | 0xf0 | RSL_IE_IPAC_REMOTE_IP | <<RSL_IE_IPAC_REMOTE_IP>> 
 | 0xf1 | RSL_IE_IPAC_REMOTE_PORT | <<RSL_IE_IPAC_REMOTE_PORT>>
 | 0xf3 | RSL_IE_IPAC_LOCAL_PORT | <<RSL_IE_IPAC_LOCAL_PORT>>
@@ -979,6 +980,79 @@
 
 (Bits 7 is reserved for future use and must be set to zero.)
 
+[[RSL_IE_OSMO_TRAINING_SEQUENCE]]
+==== RSL_IE_OSMO_TRAINING_SEQUENCE
+
+This TLV IE instructs the BTS to use a specific training sequence set and
+training sequence code for a given lchan. It is sent by OsmoBSC in RSL CHANNEL
+ACTIVATION and MODE MODIFY messages to the BTS, iff the BTS is VAMOS-capable,
+i.e. if an Abis-over-IP connected BTS indicated BTS_FEAT_VAMOS in the OML BTS
+features (Manufacturer Id information element, see <<NM_ATT_MANUF_ID>>).
+
+If this information element is present, the receiver shall ignore any other
+training sequence set and training sequence code bits from other information
+elements of the same RSL message.
+
+This is an Osmocom-specific extension of the RSL layer, which was added to
+express more than two TSC sets. For VAMOS operation, OsmoBSC selects from one
+of four separate training sequence codings per modulation scheme, while usual
+RSL IEs are only able to express a single-bit TSC set number. For clarity, this
+IE contains both the TSC set and the TSC in one IE, and is defined as
+overruling any other IEs containing TSC or TSC set numbers.
+
+The first value octet indicates the training sequence set, and the second octet
+indicates the training sequence code to be used. Receiving values from a
+reserved value range should be considered an error condition.
+
+.RSL_IE_OSMO_TRAINING_SEQUENCE
+[options="header",width="80%",cols="20%,80%"]
+|===
+| IE octet | value
+| octet 1 |  RSL_IE_OSMO_TRAINING_SEQUENCE IEI (0x61)
+| octet 2 |  length of the value part (2)
+| octet 3 |  TSC set
+| octet 4 |  TSC
+|===
+
+The training sequence set (TSC set) is coded like the 'CS Domain TSC Set' bits,
+as defined in the 'Extended TSC Set' IE in 3GPP TS 44.018 10.5.2.82
+<<3gpp-ts-44-018>>, and corresponds to the 'TSC Set' as defined in 3GPP TS
+45.002 <<3gpp-ts-45-002>>. The encoded training sequence set number ranges from
+0 to 3, any other values are reserved for future use. The encoded 0 corresponds
+to TSC Set 1, see <<RSL_IE_OSMO_TRAINING_SEQUENCE__TSC_set_coding>>.
+
+[[RSL_IE_OSMO_TRAINING_SEQUENCE__TSC_set_coding]]
+.TSC set (octet 3) coding
+[options="header",width="80%",cols="20%,80%"]
+|===
+| octet 3 value | interpretation
+| 0 | 'TSC Set 1' as in 3GPP TS 45.002
+| 1 | 'TSC Set 2'
+| 2 | 'TSC Set 3'
+| 3 | 'TSC Set 4'
+| 4..255 | reserved values
+|===
+
+The training sequence code (TSC) corresponds to the 'TSC' bits as defined in
+the 'Channel Description 2' IE in 3GPP TS 44.018 10.5.2.5a <<3gpp-ts-44-018>>.
+The training sequence code ranges from 0 to 7, any other values are reserved
+for future use.
+
+.TSC (octet 4) coding
+[options="header",width="80%",cols="20%,80%"]
+|===
+| octet 4 value | interpretation
+| 0 | 'Training Sequence Code (TSC) 0' as in 3GPP TS 45.002
+| 1 | 'Training Sequence Code (TSC) 1'
+| 2 | 'Training Sequence Code (TSC) 2'
+| 3 | 'Training Sequence Code (TSC) 3'
+| 4 | 'Training Sequence Code (TSC) 4'
+| 5 | 'Training Sequence Code (TSC) 5'
+| 6 | 'Training Sequence Code (TSC) 6'
+| 7 | 'Training Sequence Code (TSC) 7'
+| 8..255 | reserved values
+|===
+
 === A-bis RSL Initialization / BTS bring-up
 
 Upon receiving the 'IPA RSL CONNECT' OML message by the respective

-- 
To view, visit https://gerrit.osmocom.org/c/osmo-bts/+/23849
To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings

Gerrit-Project: osmo-bts
Gerrit-Branch: master
Gerrit-Change-Id: Ie583bd5969fdb45f772af198033e58d7c4077306
Gerrit-Change-Number: 23849
Gerrit-PatchSet: 3
Gerrit-Owner: neels <nhofmeyr at sysmocom.de>
Gerrit-Reviewer: Jenkins Builder
Gerrit-Reviewer: dexter <pmaier at sysmocom.de>
Gerrit-Reviewer: laforge <laforge at osmocom.org>
Gerrit-Reviewer: neels <nhofmeyr at sysmocom.de>
Gerrit-CC: fixeria <vyanitskiy at sysmocom.de>
Gerrit-MessageType: merged
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.osmocom.org/pipermail/gerrit-log/attachments/20210424/21d58fdd/attachment.htm>


More information about the gerrit-log mailing list