This is merely a historical archive of years 2008-2021, before the migration to mailman3.
A maintained and still updated list archive can be found at https://lists.osmocom.org/hyperkitty/list/gerrit-log@lists.osmocom.org/.
fixeria gerrit-no-reply at lists.osmocom.orgfixeria has submitted this change. ( https://gerrit.osmocom.org/c/osmo-gsm-manuals/+/22612 ) Change subject: TRXC: introduce VAMOS enabled channel combinations ...................................................................... TRXC: introduce VAMOS enabled channel combinations Change-Id: Ic7d4d90df752ded8c778c7b16b22d4d346bf1c9c Related: SYS#4895, OS#4941, OS#4006 --- M common/chapters/trx_if.adoc 1 file changed, 111 insertions(+), 0 deletions(-) Approvals: Jenkins Builder: Verified laforge: Looks good to me, but someone else must approve Hoernchen: Looks good to me, approved diff --git a/common/chapters/trx_if.adoc b/common/chapters/trx_if.adoc index 05c56a5..ad37224 100644 --- a/common/chapters/trx_if.adoc +++ b/common/chapters/trx_if.adoc @@ -200,6 +200,117 @@ Unless explicitly configured as described above, all timeslots will be using the default Training Sequence Code and set configured with the `SETTSC` command. +===== VAMOS enabled channel combinations (optional) + +The BTS may at any time re-configure channel combination of a timeslot (primarily +during channel activation) to activate or deactivate VAMOS mode in the transceiver. +For this purpose, the following additional channel combinations shall be used: + +.List of VAMOS enabled channel combinations and related values +[options="header"] +|=== +| value | Channel Combination +|VFF| V0(TCH/F) & V1(TCH/F), 2 channels total +|VHH| V0(TCH/H0) & V1(TCH/H0) + V0(TCH/H1) & V1(TCH/H1), 4 channels total +|VFH| V0(TCH/F) & V1(TCH/H0) + V0(TCH/F) & V1(TCH/H1), 3 channels total +|HVHH| TCH/H0 + V0(TCH/H1) & V1(TCH/H1), 3 channels total (mixed) +|=== + +where both `V0` and `V1` define a _VAMOS pair_. Symbols `&` and `+` indicate +simultaneous and sequential transmission in the TDMA domain respectively. +Therefore a combination `V0(a) & V1(b)` indicates that both channels `a` +and `b` are simultaneously active during a timeslot period. + +.Example: `VFF` in time domain (2 channels) +---- + MS1: | V0(TCH/F) | V0(TCH/F) | V0(TCH/F) | V0(TCH/F) | ... + -----+-----------+-----------+-----------+-----------+------------> TDMA frames + MS2: | V1(TCH/F) | V1(TCH/F) | V1(TCH/F) | V1(TCH/F) | ... +---- + +.Example: `VHH` in time domain (4 channels) +---- + MS1: | V0(TCH/H0) | | V0(TCH/H0) | | ... + MS2: | | V0(TCH/H1) | | V0(TCH/H1) | ... + -----+------------+------------+------------+------------+--------> TDMA frames + MS3: | V1(TCH/H0) | | V1(TCH/H0) | | ... + MS4: | | V1(TCH/H1) | | V1(TCH/H1) | ... +---- + +.Example: `VFH` in time domain (3 channels) +---- + MS1: | V0(TCH/F) | V0(TCH/F) | V0(TCH/F) | V0(TCH/F) | ... + -----+------------+------------+------------+------------+--------> TDMA frames + MS2: | V1(TCH/H0) | | V1(TCH/H0) | | ... + MS3: | | V1(TCH/H1) | | V1(TCH/H1) | ... +---- + +.Example: `HVHH` in time domain (3 channels) +---- + MS1: | TCH/H0 | | TCH/H0 | | ... + MS2: | | V0(TCH/H1) | | V0(TCH/H1) | ... + -----+------------+------------+------------+------------+--------> TDMA frames + MS3: | | V1(TCH/H1) | | V1(TCH/H1) | ... +---- + +NOTE: Combination `HVHH` is special, because it allows the network to multiplex +a legacy user device (`MS1`) with a pair of VAMOS capable devices (`MS2` and `MS3`) +on the same timeslot, so the former (`MS1`) is neither required to support the new +orthogonal TSC sets nor conform to DARP phase I or II (SAIC support). + +For all VAMOS enabled channel combinations, it's *required* to specify Training +Sequence Code and the TSC set values for all multiplexed subscribers. See 3GPP +TS 45.002, table 5.2.3e for more details on TSC set selection. + +.Example: configuring a timeslot to use `VFF` combination +---- +CMD SETSLOT <timeslot> VFF C0/S1 <1> C0/S2 <2> +RSP SETSLOT <status> <timeslot> VFF C0/S1 C0/S2 +---- +<1> V0(TCH/F) is configured to use TSC 0 from set 1 (table 5.2.3a). +<2> V1(TCH/F) is configured to use TSC 0 from set 2 (table 5.2.3b). + +.Example: configuring a timeslot to use `VFF` combination (legacy MS) +---- +CMD SETSLOT <timeslot> VFF C7/S1 <1> C4/S1 <2> +RSP SETSLOT <status> <timeslot> VFF C7/S1 C4/S1 +---- +<1> V0(TCH/F) is configured to use TSC 7 from set 1 (table 5.2.3a). +<2> V1(TCH/F) is configured to use TSC 4 from set 1 (table 5.2.3a). + +NOTE: Using Training Sequences from the same set for a _VAMOS pair_ (in this example, +`C7/S1 C4/S1`) is not recommended because of their bad cross-correlation properties. +The only exception is when two legacy non-VAMOS capable phones are paired together +and neither of them does support additional TSC sets. + +.Example: configuring a timeslot to use `VHH` combination +---- +CMD SETSLOT <timeslot> VHH C1/S3 <1> C1/S4 <2> +RSP SETSLOT <status> <timeslot> VHH C1/S3 C1/S4 +---- +<1> V0(TCH/H0) and V0(TCH/H1) are configured to use TSC 1 from set 3 (table 5.2.3c). +<2> V1(TCH/H0) and V1(TCH/H1) are configured to use TSC 1 from set 4 (table 5.2.3d). + +.Example: configuring a timeslot to use `VFH` combination +---- +CMD SETSLOT <timeslot> VFH C2/S1 <1> C2/S4 <2> +RSP SETSLOT <status> <timeslot> VFH C2/S1 C2/S4 +---- +<1> V0(TCH/F) is configured to use TSC 2 from set 1 (table 5.2.3a). +<2> V1(TCH/H0) and V1(TCH/H1) are configured to use TSC 2 from set 4 (table 5.2.3d). + +.Example: configuring a timeslot to use `HVHH` combination +---- +CMD SETSLOT <timeslot> HVHH C0/S1 <1> C0/S1 <2> C0/S2 <3> +RSP SETSLOT <status> <timeslot> HVHH C0/S1 C0/S1 C0/S2 +---- +<1> Legacy TCH/H0 is configured to use TSC 0 from set 1 (table 5.2.3a). +<2> V0(TCH/H1) is configured to use TSC 0 from set 1 (table 5.2.3a). +<3> V1(TCH/H1) is configured to use TSC 0 from set 2 (table 5.2.3b). + +NOTE: In the example for `HVHH`, legacy TCH/H0 does not belong to a _VAMOS pair_, +so it can be configured to use any Training Sequence Code without restrictions. + ==== TRXD header version negotiation Messages on DATA interface may have different header formats, defined by a -- To view, visit https://gerrit.osmocom.org/c/osmo-gsm-manuals/+/22612 To unsubscribe, or for help writing mail filters, visit https://gerrit.osmocom.org/settings Gerrit-Project: osmo-gsm-manuals Gerrit-Branch: master Gerrit-Change-Id: Ic7d4d90df752ded8c778c7b16b22d4d346bf1c9c Gerrit-Change-Number: 22612 Gerrit-PatchSet: 2 Gerrit-Owner: fixeria <vyanitskiy at sysmocom.de> Gerrit-Reviewer: Hoernchen <ewild at sysmocom.de> Gerrit-Reviewer: Jenkins Builder Gerrit-Reviewer: fixeria <vyanitskiy at sysmocom.de> Gerrit-Reviewer: laforge <laforge at osmocom.org> Gerrit-Reviewer: pespin <pespin at sysmocom.de> Gerrit-MessageType: merged -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.osmocom.org/pipermail/gerrit-log/attachments/20210213/6f52f3ca/attachment.htm>