Transcoder Free Operation (TrFO)

Transcoder Free Operation (TrFO) is a standard mechanism to provide transcoderless connection for 3G speech calls. Its functionality is mainly defined in 3GPP TS 23.153 Out of Band Transcoder Control, Stage 2. The operation is based on codec negotiation and selection performed by the MSS and the user plane operations of the MGW, including user plane protocol handling and automatic transcoder removal and insertion, when applicable. Codec negotiation between MSSs can be performed either through BICC, SIP-I, or SIP-T signalling. Interworking with IM CN network can be performed through the 3GPP SIP signalling and interworking with FSS network can be performed through the SIP-I signalling. In case of BICC, the Application Transport Mechanism (APM) is used to transfer bearer-related parameters, for example, speech codecs. In case of SIP-I, 3GPP SIP, and SIP-T signalling, the Session Description Protocol (SDP) is used to carry the corresponding codec information.

Figure: Transcoder Free Operation (TrFO) Corresponding functions are available when SIP-I, 3GPP SIP, or SIP-T is used as a signalling protocol. SIP-T usage is not standardised by 3GPP, but it is Nokia proprietary. Codec negotiation is performed by the MSSs interacting with each other and with the RNCs/UEs. On the mobile-originating side, the UE provides its supported codec list to the MSS in a SETUP message. The MSS, RAN, and MGW capabilities are taken into account during the codec negotiation and codec selection procedures. After the MSS has (pre)selected the MGW(s) through which the call is routed, it further deletes the not supported codecs from the list. Additionally, the MSS and MGW supported codecs are added to the list as fallback codecs to guarantee that user plane can be established. The UPDspecific codec preference list is also taken into account (if defined) when the UPD level codec support is checked, and when the priority order of the given codecs is determined. The codec list is further sent in a BICC IAM (or SIP INVITE) message to the next MSS. An intermediate node, if any, when receiving a BICC IAM (SIP INVITE) message, compares the received list of codecs with the codecs supported by the MGW(s) it selects. The UPD-specific codec preference list is also taken into account (if defined) when codec support is checked. The not supported codecs are deleted from the list. The list is further sent in the BICC IAM (SIP INVITE) to the next node. The mobile-terminating MSS receives codecs supported by the terminating UE in a CALL CONFIRMED message. The terminating MSS selects the highest priority codec in the received list (in BICC IAM/SIP INVITE) also supported by the terminating UE. The UPD-specific codec preference list is also taken into account (if defined) at this step.

The selected codec is sent back in a BICC APM (SIP SESSION PROGRESS) message. When receiving this message, each node knows the selected codec to be used in a speech path and is further able to control the MGW(s) accordingly. The MGW is controlled through the H.248 interface by defining the used codec and other parameters related to the user plane protocol for each MGW termination created for a call. After termination properties are provided, the bearer requirements are known, and bearer connections through the core network can be set up by the MGWs involved. With TrFO, the core network technology can either be based on RTP/IP or AAL2/ATM, and different methods exist (that is, forward and backward) for bearer establishment. However, the method or technology used does not prevent TrFO operations. Interaction towards the RAN and the UE is performed by requesting a Radio Access Bearer (RAB) suitable for the selected codec and by indicating the used codec to the UE, when necessary.

Figure: Successful BICC codec negotiation In addition to the end-to-end TrFO calls, there are cases where transcoding has to be applied, for example, when the call is going to the PSTN network. Even though transcoding could not totally be avoided, it is beneficial to optimise the location of the inevitable transcoder that is commonly referred to as a transcoder at the edge. It means that the compressed speech is transferred as widely as possible and transcoding is performed at the edge of the PLMN. It results transmission capacity savings in the core network.

Figure: Optimising the transcoder location With a UE-originating call going to a PSTN, the edge MSS selects a suitable mobile-originating codec backwards and orders the MGW to insert an interworking transcoder. The MGW terminates the user plane towards the PLMN and performs transcoding between the codecs.

Figure: Transcoder at the PSTN edge, UE-originated call Generally, a predefined order is used for MSS codec preference, where typically the compressed codecs have the first priority. For PSTN-originating calls, supported cellular codecs are added to the BICC IAM (SIP INVITE) codec list according to the predefined MSS codec preference. The terminating MSS selects the suitable codec supported by the terminating UE. In this case, TrFO applies towards the Gateway MGW.

Figure: Transcoder at the PSTN edge, PSTN-originated call If the connection goes through a TDM network, or codec negotiation is not supported in some part of the connection, the transcoder at the edge can be performed at both sides of the connection. This can be the case, for example, when operators are connected to each other by using PCM lines. Transcoding is not avoided, but transmission savings can be achieved in both PLMNs.

Figure: Transcoder at the edge, TDMrouted call Currently the only mandatory codec for 3G UE is UMTS AMR (3GPP R99) or UMTS AMR2 (3GPP R4) and this codec is selected with most of the TrFO calls. Other codecs, for example, the GSM EFR are not supported for 3G calls. Even though UMTS AMR (3GPP R99) or UMTS AMR2 (3GPP R4) is likely to be the selected one, an end-to-end negotiation is essential to agree that both sides use exactly the same mode set of the AMR multimode codec. The negotiation of used codec modes is performed by MSSs simultaneously with the actual codec type negotiation. User plane initialisations TrFO break