TrFO and TFO
TrFO and TFO
TrFO and TFO
Table of Contents
Chapter 5 TrFO and TFO ................................ ................................ ................................ .......... 5-1 5.1 Overview of TrFO and TFO ................................ ................................ ........................... 5-1 5.2 TrFO Functions ................................ ................................ ................................ ................. 1 5.3 TFO Functions ................................ ................................ ................................ .................. 3 5.4 TrFO and TFO ................................ ................................ ................................ .................. 4 5.5 Function of MGW during TrFO/TFO ................................ ................................ .................. 4
Control Plane
Oo Codec Negotiation
RANA
earer
ME
RNC
Req
Use r Plane
Radio earer
Iu earer
MSC S e e
MSC S e e
RANA MW Control
earer
Oo Codec Negotiation
Req
MGW
RNC
ME
Iu earer
Radio earer
Figure 5-1 TrFO application network structure In the TrFO mode, the calling ME performs out-of-band negotiation with the called ME. If they support the same codec type, transcoding is not needed in the service bearer set-up process, that is, transcoders are not necessary to add. In the TrFO mode, voice codec type negotiation is implemented by (G)MSC Server nodes. A typical negotiation process involving more than two (G)MSC Servers is detailed as below. 1) The originating (G)MSC Server (O-MSC) sends the codec types and an option list (IAM messages) supported, which are arranged as preference. After receiving the information from the originating (G)MSC Server node, the intermediate (G)MSC Server node deletes the options it does not support and then continue to send the list. The preference parameter in the list is not changed. The termination (G)MSC Server node (T-MSC) analyzes the list, then selects the codec type with the highest preference (an APM message, containing the selected codec type and optional codec types list), and finally returns its selection result. Till now, the negotiation process is completed. If no commonly supported code type can be selected during negotiation, transcoders need to be inserted for transcoding. The OoBTC negotiation can be classified into three types. And different negotiation processes correspond to different services:
Basic negotiation process (originating A, intermediate B and remote C): In this process, basic calling services are involved.
Bearer modification process (originating A, remote B and remote C): C needs to modify B selection and bearer. The services concerned are CFU, CFB, CFNRy, CFNRc, CD, ECT and IN (with a more completed process). Three-party negotiation process (originating A, remote B and remote C): CCD (Conference Call Device) is located at A. Firstly set up the link between A and B (A, B, Codec x), and then add C, which is only connected with A (A, C, Codec y).The concerned services are CW, CH and MPTY.
LM
LM
MS UE
Transcoding Function
Transcoding Function
MS UE
ecoding
ecoding
compressed speech
Figure 5-2 Typical cascaded operations of TCs When an MS accesses another MS, the voice transcoding process is described as follows: The originating MS encodes voice signals, and then sends them to the P MN A it resides in through radio links. The local TC decodes the compressed voice and according to ITU-T G.711, converts the decompressed voice to A-law or U-law PCM voice that is then transferred to the radio network P MN B across the fixed network. The TC of P MN B encodes the voice and the P MN B sends the compressed voice to another MS. In the above networking application, the two TCs are in cascading operation status. As the voice is encoded and decoded twice in the call process, the voice signals shall be damaged especially in a low-rate TC. To minimize the damage on voice and improve voice quality, the TC functions are disabled at the P MN A and P MN B so that the voice signals are transparently transmitted between the originating and terminating MSs provided that the originating and terminating MS uses the same TC. This is the function of the TFO protocol. In this case, voice signals are only coded at the originating MS and decoded the terminating MS once, thus improving the voice quality. TFO affords the following functions:
Establishing a channel for transparent transmission between two TCs. Providing in-band signaling between two TCs for TFO operation control. Transferring information of TC configurations such as ACS and SCS between two TCs. Making codec types matched. Enabling and implementing TFO if the same codec type is selected by both sides. Restoring the TC cascading operation status quickly and seamlessly from TFO status if necessary.
To make codec types matched, the method of optimising TC can be used. The optimising results may require TFO. In this case, other functional entities such as RNC may be required to participate in enabling TFO. TFO offers multiple benefits including:
Avoid repeated TC operations and improved voice quality. The effect is especially obvious in the presence of low-rate transcoding. Occupy less PMN resources. During TFO, 16kbit/s or 8kbit/s multiplexed voice signals that are compressed are transferred across networks. Save the power of network equipments. During TFO, TC is disabled. Possibly reduce the point-to-point transmission delay.
At present, UMG8900 supports TFO of AMR transcoding only. For details about TFO message sequence, please see 3GPP TS 28.062 specifications.
If the OoBTC fails to establish the TrFO and transcoders are required, then in-band TFO may be used for negotiation. TFO is activated either at set-up or during the communication phase. In-band TFO shall be used for interworking with the 2G systems, and TrFO shall used for pure 3G network application. In-band TFO shall be the fallback mechanism when transcoders cannot be avoided,
R99 set limitations of TrFO. The BICC protocol set1 only support AA 1 and AA 2, and does not support bearer modification or repeated codec negotiation. For example, if a node has no BC modification capability, you have to release the bearer link already set up and then set up a new one.
During TFO, TC is responsible for the whole negotiation process, including making the decision whether to perform transcoding.