Codec Management

By -

Codec Management Objectives

Codec Management has following goals:
1.) Optimize the voice quality.
2.) Optimize the bandwidth efficiency
3.) Optimize the transcoder resource in MGW.
4.) Optimize the delay

Voice Quality:

Voice quality is measured in terms of the level, attenuation, delay, echo, and so on and may be used as a basis for the iQoS assessments for conventional VoIP. Voice Quality is measured in terms of R-value and below 50 are not recommended.

Standards                                     Intrinsic quality (R)
------------------------------------------------------
ITU G.711 (64kbps)                                  94.3
ITU G.728 (12.kbps)                                 74.3
ETSI GSM-FR (13kbps)                           74.3
ETSI GSM-HR (5.6kbps)                          71.3
ETSI GSM-EFR (12.2kbps)                      89.3
-----------------------------------------------------


Transcoding can be harmful for voice quality of a call and should be avoided if possible. In 2G, BSC is in charge of transcoding while MSC is the incharge of transcoding in 3G. We have intention to minimise the Transcoder to enhance the voice quality.

Bandwidth efficiency:

Legacy networks use a consistent 64 kbps per channel. Use G.711, packet networks easily surpass 64 kbps. Therefore, compress codecs must be used on core.  Compression ratio of 8:1can be achieved with compressed codecs along with the following techniques : silence suppression, AAL2/RTP multiplexing, IP header compression.

Transcoder Resources optimization:

The third goal of the codec management is to optimize the transcoder resources in the MGW. So, TrFO must be used whenever possible.

Optimization of delay:

Delay can be minimized if reduce the number of transcoders. We can reduce the transcoding time in call.

Comments

  1. aldehetsuMay 21, 2022 at 9:04 AM

    aldehetsu Vicky Mirda https://www.rockcuff.com/profile/Asus-Sonicmaster-Audio-Driver-Extra-Quality-Download/profile
    roochesnibbchi

    ReplyDelete
  2. CloudShope TechnologiesDecember 11, 2023 at 7:34 PM

    Awesome Post! If you are looking for Call Center Solution Provider in India then your search ends there. you can directly contact CloudShope Technologies at 9027890278 or 9649643643.

    ReplyDelete

Post a Comment

Popular posts from this blog

Intelligent Networks (IN) and CAMEL

By -
Image
Intelligent Networks (IN) :-  Intelligent Networks is a concept service intelligence resides in a central node called an SCP and SSPs (residing on Switches) relinquish control to this node at particular stages in a call so that appropriate service logic can be applied. Objectives of IN: - Increased Service Velocity / Speed of Deployment - Increased Range of Services - Evolvability from Existing Networks - Service & Vendor Independent Implementation - MSC just focuses on core job of call processing Network Before IN:   Before IN application, there was messed network for every node: Network with IN : After IN implementation, Network is organised. Basic Concepts  – PIC and DPs & BCSM: Point In Call (PIC)  :  A state in a basic call state model. Detection Point (DP)  :  A point in basic call processing at which specific event is detected. Detection Points represent  transitions  between points in call processing
Read more

Diameter Messages

By -
Capability Exchange: When two peers established transport connection, they must exchange the capability exchange message. this message allows the discovery of peer's identity and its capabilities. Once transport layer is established, CER and CEA exchanged to determine the capability of peer endpoint followed by DWR/DWA. In below example DiameterNodeA start diameter connection with DiameterNodeB after transport layer connection established. In case of TCP (Syn/Syn-Ack) and  SCTP (Init/Init-Ack/Coockie Echo) exchanged. In case of SCTP Connection establishment(CER, CEA, DWR, and DWA) are exchanged with setting out-of-order delivery false to avoid race-condition and for connection termination (DPR/DPA) set the timer to receive out-of-order message before terminating the connection.               DiameterNodeA                     DiameterNodeB                                     <------Transport Layer Established--------->                ---------------------- CER -------
Read more

SRVCC - Single Radio Voice Call Continuity

By -
SRVCC enables continuity of voice call anchored in IMS network, when UE changes its access network from packet based in eUTRAN to circuit based GERAN or UTRAN, without requiring the UE to have simultaneous access to both the radio network.   It accomplishes this by enhancing the MMEs, serving E-UTRAN and the 3GPP CS MSC serving GERAN/UTRAN such that when the UE is still anchored within the E-UTRAN network and triggers a measurement report indicating a need for handover (HO) to GERAN/UTRAN, the MSC can initiate IMS service continuity procedure towards the IMS domain in addition to preparing for a handover into its GERAN/UTRAN access, before the UE is directed to change its access network to GERAN/UTRAN.     The SRVCC feature requires the new Sv interface between MSC and MME. Sv Interface runs over UDP. Following messages are exchanged over Sv Interface:   - PS to CS Request - PS to CS Response - PS to CS Complete Notification - PS to CS Complete Acknowledge - PS t
Read more