1 2 3 4 5 6 7 8 9 10

3GPP2 S.R0096-0 Version 1.0 Version Date: 18 March 2004

Transcoder Free Operation

11 12 13 14 15 16 17 18 19 20 21 22 23 24 25

Stage 1 Requirements

COPYRIGHT NOTICE
3GPP2 and its Organizational Partners claim copyright in this document and individual Organizational Partners may copyright and issue documents or standards publications in individual Organizational Partner's name based on this document. Requests for reproduction of this document should be directed to the 3GPP2 Secretariat at secretariat@3gpp2.org. Requests to reproduce individual Organizational Partner's documents should be directed to that Organizational Partner. See www.3gpp2.org for more information.

26 27

S.R0096-0 v1.0
1 2 3 4 EDITOR R. L. Bunting; RLBunting@Lucent.com REVISION HISTORY

5 Rev. # 1.0 6 REVISION HISTORY Descriptions Initial publication Date 18 March 2004

S.R0096-0 v1.0

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19

Table of Contents
Table of Contents............................................................................................ 1 List of Tables 2 List of Figures 3 1 INTRODUCTION .................................................................................... 4 1.1 Typical TrFO / RTO Transcoder Configurations .......................... 4 2 REFERENCES ....................................................................................... 6 3 DEFINITIONS AND ABBREVIATIONS ..................................................... 6 4 GENERAL FEATURE DESCRIPTION ...................................................... 7 4.1 Normal Procedures with Successful Outcome ............................. 7 4.2 Exception Procedures or Unsuccessful Outcome ........................ 8 4.3 Alternative Procedures ............................................................... 9 4.4 Interactions with Other Wireless Services ................................... 9 5 Requirements ........................................................................................ 9 5.1 Network Requirements ............................................................... 9 5.2 TrFO / RTO Interaction with Services....................................... 10

S.R0096-0 v1.0

1 2 3 None Included

List of Tables

S.R0096-0 v1.0

1 2 3 4 5 6 7 8 9

List of Figures
Figure 1: Typical Vocoder Arrangement Prior to TrFO/RTO........................................................................ 5 Figure 2: TrFO Bearer Arrangement .............................................................................................................. 5 Figure 3: RTO Transcoder Arrangement (Mobile-to-Mobile) ....................................................................... 6 Figure 4: RTO Transcoder Arrangement (MS-to-PSTN / PSTN-to-MS)....................................................... 6

S.R0096-0 v1.0

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36

INTRODUCTION
Transcoder Free Operation [1] (TrFO) is the transport of compressed speech, from legacy mobiles, in a packet transport network through the elimination of unnecessary coding and decoding of the signal by intermediate elements in the bearer path. Transcoders may be associated either with the RAN or Media Gateway (MGW). By transporting only the compressed speech, TrFO achieves bandwidth efficiencies in the bearer stream and reduces round trip delays introduced by unnecessary transcoding. Also, TrFO may increase voice quality. TrFO is not applicable to VoIP. TrFO is a capability of the Legacy MS domain. TrFO utilizes out of band signaling capabilities that include the ability to determine the negotiated codec type to be used at the two end nodes. If the two end nodes are capable of the same codec operations, it may be possible to traverse the entire packet network using only the compressed speech (of the preferred codec). TrFO is a mechanism for configuring a call such that no transcoders are needed in the core network. The vocoders that are needed for this call are located in the Mobile Station (MS). Remote Transcoder Operation (RTO) is a mechanism for configuring a call such that a transcoder resource is needed in the core network. RTO does not imply a tandem operation, instead only a single resource may be needed. E.g. To support a MS to PSTN call, a transcoder is inserted at the MGW or BSC. For a MS to MS call, where the codecs in the two MS differ, a transcoder is needed in the network. This eliminates the typical tandem use where two transcoders are used to transcode the two endpoints to a common but unique protocol for transport. RTO is just a special case of TrFO.

1.1

Typical TrFO / RTO Transcoder Configurations Figures 1-4 illustrate some of the many possible TrFO / RTO network configurations. Because of the flexibility for transcoder location (e.g. MGW or RAN), the figure does not show precise transcoder placement. For figures 2-4, the network architecture could be either Intra-LMSD or Inter-LMSD (e.g. the call may be contained completely in a single LMSD or the compressed bearer may be between two separate LMSDs). In the figures, the solid lines and objects represent bearer paths and transcoders or vocoders that are in the bearer path. The drawing elements that are shown in gray represent the corresponding elements that were included in previous figures that are no longer required in the situation illustrated.

S.R0096-0 v1.0

1 2 3 4 5 6

1.1.1

Figure-1: Typical Vocoder Arrangement Prior to TrFO/RTO A typical vocoder arrangement for LMSD Step-1 is shown in Figure-1. This arrangement requires the placement of two vocoders in the bearer path even though the two endpoints are utilizing compatible codecs. This tandem arrangement of transcoders is typical for LMSD Step-1 and is the configuration that the TrFO enhancement avoids.
MS1/ codec1 EVRC EVRC transcoder E G EVRC G.711 G.711 transcoder GE EVRC codec2/ MS2 EVRC EVRC

7 8 9 10 11 12 13 14 15 16 17 18

Figure-1: Typical Vocoder Arrangement Prior to TrFO/RTO

1.1.2

Figure-2: TrFO Bearer Arrangement Using TrFO, the two tandem transcoders shown in Figure-1 are eliminated as part of the codec negotiation on call setup. The native (compressed) speech provided by the two compatible vocoders is transported through the network without the additional delays and bandwidth or quality losses added by using two unnecessary transcoders. This arrangement is illustrated in Figure-2. Note that the unneeded transcoders are shown in dotted blue in the diagram with an end-to-end bearer transport of compressed (EVRC) speech illustrated. This figure illustrates a mobile-to-mobile call, where the mobiles have compatible codecs. The network configuration could be either Intra-LMSD or Inter-LMSD.
MS1/ codec1 EVRC transcoder EVRC EVRC EVRC transcoder codec2/ MS2 EVRC

19 20 21 22 23 24 25 26 27 28 29 30 Figure-2: TrFO Bearer Arrangement

1.1.3

Figure-3: RTO Transcoder Arrangement (Mobile-to-Mobile) The next configuration worth noting is the RTO. For RTO a single transcoder may be necessary in a bearer path when the two end point codecs are incompatible. There are still noteworthy efficiencies, since the tandem configuration as illustrated in Figure-1 is reduced to one, not a pair of transcoders. This is illustrated in Figure-3. The network configuration could be either IntraLMSD or Inter-LMSD. Depending on network configuration and vocoder placement, the transcoder placement shown could be either in the RAN or the MGW.

S.R0096-0 v1.0

MS1/ codec1 EVRC EVRC

transcoder EVRC

transcoder E 13 EVRC 13 K 13 K

codec2/ MS2 13 K 13 K

1 2 3 4 5 6 7 8
MS1/ codec1 EVRC EVRC transcoder EVRC transcoder EP EVRC PCM PCM PSTN PCM PCM

Figure-3: RTO Transcoder Arrangement (Mobile-to-Mobile)

1.1.4

Figure-4: RTO Transcoder Arrangement (MS-to-PSTN / PSTN-to-MS) Figure-4, illustrates the RTO transcoder arrangement for a Mobile-to-PSTN and PSTN-to-Mobile call. The compressed speech bearer could be either Intra-LMSD or Inter-LMSD. Again, there are no restrictions on the transcoder placement.

9 10 11 12 13 14 15 16 17 18 19 BSC CN Inter-LMSD Base Station Controller Core Network Between two distinct LMSD systems (e.g. the architecture of LMSD Step-1). In the context of TrFO/RTO, a compressed speech bearer path is established between media gateways located in two different systems. Within the same LMSD system (e.g. a mobile-to-mobile, mobile-to-PSTN or PSTN-to-mobile call that is treated within a single LMSD system) Media GateWay Mobile Station Mobile Switching Center Public Switched Telephone Network Remote Transcoder Operation: a network capability for endpoints with Figure-4: RTO Transcoder Arrangement (MS-to-PSTN / PSTN-to-MS)

REFERENCES
[1] Work Item Name: Transcoder Free Operation; 3GPP2-00072; Submission Date: 2003/02/17; Work Item Status: Proposed [2] A.S0004-B v2.0 CDMA Tandem Free Operation Specification -Release B (TIA-895-A), August 2002

DEFINITIONS AND ABBREVIATIONS

Intra-LMSD MGW MS MSC PSTN RTO

S.R0096-0 v1.0 incompatible codecs. RTO attempts to enable the bearer by matching the incompatible codecs with a single transcoder. Ideally compressed speech is passed between the endpoints. For circumstances where a single transcoder is not available to enable the bearer, two tandem transcoders may be required to find a match between the endpoints. TFO TrFO Tandem Free Operation Transcoder Free Operation: a network capability for mobile-to-mobile calls, where the mobiles have identical codecs. TrFO enables the bearer path without introducing vocoders in the bearer path. Compressed speech is passed between the mobile endpoints.

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30

GENERAL FEATURE DESCRIPTION

A typical use of end-to-end TrFO is a mobile-to-mobile call where the same codec is used for each Mobile Station and no additional transcoders are required in the transport network. Alternatively for a mobile to PSTN call, the only transcoder required may be at the Core Network (CN) to PSTN boundary (e.g. transcoding at the edge). The situation requiring a single transcoder is described here as RTO Where a change to the call state of a transcoder free connection occurs, such that compressed speech cannot be maintained, a transcoder or pair of transcoders may be required in the path (e.g. handoff to a system not capable of TrFO, or at the edge of a CN network). In the situation where additional handoffs occur and TrFO can be supported, the call should revert to TrFO. TrFO is an enhancement over Tandem Free Operation [2] (TFO) because it increases transport bandwidth efficiency. See also Figures 1 through 4 in the INTRODUCTION for additional illustrations of possible transcoder arrangements using TrFO and RTO.

4.1

Normal Procedures with Successful Outcome Authorization The subscriber is authorized to use this service without prior arrangement. The network performs TrFO configuration and no subscriber authorization is required. De-Authorization The subscriber is authorized to use this service without prior arrangement. The network performs TrFO configuration and no subscriber deauthorization is needed. Registration TrFO is a network enhancement. It is not offered as a subscriber service and no registration for this service is required. De-Registration Not Required, see Registration above.

S.R0096-0 v1.0

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37

Activation TrFO is a network enhancement. It is not offered as a subscriber service and no subscriber feature activation is required. De-Activation TrFO is a network enhancement. It is not offered as a subscriber service and no subscriber feature de-activation is required. Invocation Invocation of TrFO may occur in the network for mobile-to-mobile call when both ends of the call will be using the same codec. Invocation of RTO may occur for a call traversing a RTO capable network, where the only occurrence of a codec is at the network edge when the call is exiting the network for another network that is not TrFO or RTO capable (e.g. PSTN). Normal Operation with Successful Outcome TrFO utilizes out of band signaling capabilities that include the ability to determine the negotiated codec type to be used at the two end nodes. If the two end nodes are capable of the same codec operations, it may be possible to traverse the entire packet network using only the compressed speech (of the preferred codec). Call Detail Record Enhancements to call detail recording are desirable to provide the ability to determine on a per call-leg or route basis the transcoder configuration that was established for a particular call. This information is useful for customer service, trouble reporting, capacity and provisioning and is part of the general accounting information. There is not implied billing impact for these enhancements. 4.2 Exception Procedures or Unsuccessful Outcome Registration Not Applicable. De-Registration Not Applicable. Activation Not Applicable. De-Activation Not Applicable. Invocation Not Applicable . 8

S.R0096-0 v1.0

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36

Exceptions While Roaming Not Applicable. Exceptions During Intersystem Handoff Where a change to the call state of a transcoder free connection occurs, such that compressed speech cannot be maintained, a transcoder or pair of transcoders may be required in the path (e.g. handoff to a system not capable of TrFO, or at the edge of a CN network). In the situation where additional handoffs occur and TrFO can be supported, the call should revert to TrFO. 4.3 4.4 Alternative Procedures None Specified. Interactions with Other Wireless Services The TrFO and RTO capabilities are required to support other wireless services that result in the modification or reconfiguration of the bearer path during TrFO operation (e.g. Addition and removal of conference bridge, etc) See the specific requirements below. 4.4.1 Conferencing Introducing a Conference Bridge into a TrFO call may require the introduction of transcoders to gain a mix of the voice calls from the individual conference participants or reverting to conventional call handling at the base station in order to meet the conferencing restrictions. At the end of the conferencing restrictions, TrFO operation should be resumed. 4.4.2 Announcements Announcements for the purpose of this description may be considered as a special case of conferencing. It may be plausible to consider at what time during the call TrFO will be invoked based on the nature of the announcement (e.g. pre-call, mid-call, or post-call).

5
5.1

Requirements
Specific requirements for the TrFO capability are listed in this section. Network Requirements TrFO TrFO-001: The TrFO network capability shall enable TrFO between Mobile-toMobile calls when the Mobiles have compatible codecs. TrFO-002: The TrFO capability shall be provided for calls between mobile stations that are intra-LMSD (e.g. between MSs that are served by the same LMSD system).

5.1.1

S.R0096-0 v1.0

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38

TrFO-003: The TrFO capability shall be provided for calls between mobile stations that are inter-LMSD (e.g. between MSs where each is served by a separate but networked LMSD). TrFO-004: The mechanism to provide TrFO shall minimize the number of vocoders in the bearer path. (For TrFO, the endpoint codecs are compatible and the minimization results in zero transcoders placed in the bearer path. If the codecs are incompatible, the resultant configuration may be RTO and a single transcoder is placed in the path. If a transcoder match cannot be found and two transcoders are required to match the circuit, then the current situation, shown in Figure-1 may result.) 5.1.2 RTO RTO-001: The RTO capability shall enable RTO between Mobile-to-Mobile calls when the Mobiles have incompatible codecs. RTO-002: The RTO capability shall be provided between mobile stations that are intra-LMSD (e.g. between MSs that are served by the same LMSD). RTO-003: The RTO capability shall be provided between mobile stations that are inter-LMSD (e.g. between MSs where each is served by a separate but networked LMSD). RTO-004: The RTO capability shall be provided between a MS and a network endpoint where incompatible codecs exist, but where a single transcoder will enable the bearer path (e.g., Mobile-to-PSTN, PSTN-to-Mobile). RTO-005: The RTO mechanism shall utilize a transcoder selected from a prioritized list of transcoders. RTO-006: The mechanism to provide RTO shall minimize the number of vocoders in the bearer path. For RTO, the endpoint codecs are not compatible and the minimization results in a single transcoder placed in the bearer path. If a transcoder match cannot be found and two transcoders are required to match the circuit, then the current situation, shown in Figure-1 may result. 5.2 TrFO / RTO Interaction with Services TSv-001: The TrFO and RTO mechanisms shall allow for reconfiguration of transcoders in the bearer path when needed (e.g. application of conference circuits, insertion of announcements, placing subscriber on hold, etc.) TSv-002: It may be necessary to reconfigure a TrFO or RTO bearer path due to certain telephony requirements. (e.g. transcoders may be inserted, dropped or otherwise reconfigured due to certain restrictions, like conferencing). At the end of the reconfiguration, the operation (TrFO or RTO) shall be resumed.

10