9 Interaction with Lawful Intercept
22.0533GPPRelease 17Service descriptionStage 1Tandem Free Operation (TFO)TS
In the case where lawful intercept is required in a TFO call, the intercept shall not cause any degradation in the speech quality received by the A and B parties.
Annex A (informative):
Limitations of initial in-band TFO implementations
This annex highlights the limitations of the applicability of the in-band TFO solutions, some of these limitations could be overcome, however they imply modifications of equipments that are not in the scope of the specifications.
When analogue lines are used TFO either in-band or out-if-band can not apply.
The main limitation of TFO in-band is the digital transparency of the PCM lonks behind the MSCs that cannot be guaranteed in all the configurations of Mobile-to-Mobile calls.
When digital lines are used the non-transparency is mainly due to the use of In Path Equipments (IPE). These IPEs consist mainly in Echo Cancellers and DCMEs.
The Network Echo Cancellers intend to remove the echo due to the unbalanced hybrids present in the PSTN when going from four wires to two wires in the subscriber local loops. These IPEs are useful in the mobile-to-PSTN calls. These Echo Cancellers should not be used in mobile-to-mobile calls since both terminals are digital. The enabling and disabling of these equipments are properly managed in some countries and not in other countries. Therefore TFO can apply to inter-PLMN calls in the countries where the network echo cancellers are properly configured. The main issue is that there’s no easy internationally recognised way to identify mobile-to-mobile calls. They are usually correctly configured for Mobile-to-Mobile calls within a PLMN.
Another limitation that should apply to a very small number of mobile-to_mobile calls is the use of A/µ Laws converters in some international calls.
In some networks Acoustical Echo Cancellers are used. It would be preferable to keep them enabled in Tandem Free calls. This implies that this be taken into account by the Acoustical Echo Cancellers.
The DCMEs they are mainly used in the long distance calls although some operators use them in their PLMN. The only known way to disable the DCMEs is to ask for a transparent 64 kbit/s UDI connection. This option is not reasonable since such connections are more expensive than the speech calls and would imply modifications in the MSCs. Therefore when a DCME is used in-band TFO cannot be established.
In order to get TFO working for the vast majority of the Mobile-to-Mobile calls it is desirable that the IPEs be modified in order to allow the in-band TFO cross them without modification.
TFO implies that compatible speech codec configurations are being used in both MSs. In-band TFO can be established only after the call set-up has been made and thus there can be different speech codecs used in the MSs. The TFO standard shall include ways to solving the codec mismatch otherwise in-band TFO won’t apply to these Mobile-to-Mobile calls.
Annex B (informative):
Change history
|
SMG# |
SPEC |
CR |
VERS |
NEW_VERS |
PHASE |
SUBJECT |
|||||||
|
s23 |
02.53 |
new |
2.0.0 |
5.0.0 |
R97 |
Tandem Free Operation Stage 1 |
|||||||
|
s24 |
02.53 |
A001 |
5.0.0 |
5.1.0 |
R97 |
CR to GSM 02.53 Modifications to Annex A (informative): Limitations of initial in-band TFO implementations |
|||||||
|
s25 |
02.53 |
new |
5.1.0 |
7.0.0 |
R98 |
Version change as part of Release 1998 |
|||||||
|
s29 |
02.53 |
7.0.0 |
7.0.1 |
R98 |
Publication of version 7.0.1 |
||||||||
|
02.53 |
7.0.1 |
R99 |
Version 8.0.0 |
||||||||||
|
Change history |
|||||||||||||
|
Date |
TSG SA# |
TSG Doc. |
CR |
Rev |
Subject/Comment |
Old |
New |
||||||
|
2001-03 |
11 |
SP-010098 |
002 |
Extension of TFO to AMR |
8.0.0 |
4.0.0 |
|||||||
|
2001-09 |
Clean-up |
4.0.0 |
4.0.1 |
||||||||||
|
2002-06 |
16 |
Version for Release 5 |
4.0.1 |
5.0.0 |
|||||||||
|
2004-12 |
Version for Release 6 |
5.0.0 |
6.0.0 |
||||||||||
|
2007-06 |
36 |
Version for Release 7 |
6.0.0 |
7.0.0 |
|||||||||
|
2008-12 |
42 |
Version for Release 8 |
7.0.0 |
8.0.0 |
|||||||||
|
2009-12 |
46 |
Version for Release 9 |
8.0.0 |
9.0.0 |
|||||||||
|
2011-03 |
51 |
Version for Release 10 |
9.0.0 |
10.0.0 |
|||||||||
|
2012-09 |
57 |
Version for Release 11 |
10.0.0 |
11.0.0 |
|||||||||
|
2014-09 |
65 |
Version for Release 12 |
11.0.0 |
12.0.0 |
|||||||||
|
2015-12 |
70 |
Version for Release 13 |
12.0.0 |
13.0.0 |
|||||||||
|
Change history |
|||||||
|
Date |
Meeting |
TDoc |
CR |
Rev |
Cat |
Subject/Comment |
New version |
|
2017-03 |
75 |
Version for Release 14 |
14.0.0 |
||||
|
2018-06 |
80 |
Version for Release 15 |
15.0.0 |
||||
|
2020-07 |
SA#88e |
– |
– |
– |
– |
Updated to Rel-16 by MCC |
16.0.0 |
|
2022-04 |
– |
– |
– |
– |
– |
Update to Rel-17 version (MCC) |
17.0.0 |