MMTel

A representative sample of commonly invoked MMTel features were used to select the callflows. Online charging via Diameter is active.

  • 51% of calls are originating

  • 49% of calls are terminating

Scenario Percentage

VoLTE full preconditions

50%

CDIV Success-response

40%

CDIV Success-response with OIP

4.5%

CDIV Busy-response

4.5%

VoLTE full preconditions with one session refresh

1%

Call setup time (latency) is measured by the simulator playing the initiating role. For all CDIV scenarios, latency is measured from INVITE to final response. For both preconditions scenario, latency is measured from INVITE to ACK.

VoLTE full preconditions

A basic VoLTE call, with no active MMTel features. Radio bearer quality of service preconditions are used. The B party answers the call, A party hangs up. The call has a 95 second hold time.

Latency is measured from the A party INVITE, to A party ACKing the 200.

VoLTE full preconditions with one session refresh

A basic VoLTE call, with no active MMTel features. Radio bearer quality of service preconditions are used. The B party answers the call, A party hangs up. This variant lasts for the default SIP session refresh interval, 10 minutes.

Latency is measured from the A party INVITE, to A party ACKing the 200.

CDIV Success-response

Callflow with Call Diversion active. B party rejects call, call is diverted to C party, C party accepts call. The call has a 50 second hold time.

Latency is measured from the A party INVITE, to A party receiving the 200.

CDIV Success-response with OIP

Callflow with Call Diversion active, and Originating Identity Presentation (OIP) feature active. B party rejects call, call is diverted to C party, C party accepts call. The call has a 50 second hold time.

Latency is measured from the A party INVITE, to A party receiving the 200.

Sets the Privacy header to: Privacy: user;header;id, to exercise the OIP feature.

CDIV Busy-response

Callflow with Call Diversion active. B party rejects call, call is diverted to C party, C party is not found, call ends with 404.

Latency is measured from the A party Invite, to A party receiving the 404.

SCC

A representative sample of commonly invoked SCC features were used to select the callflows. Online charging is not active.

  • 50% of calls are originating

  • 50% of calls are terminating

Scenario Percentage

SCC originating with provisional SRVCC

30%

SCC T-ADS

50%

Access-Transfer Originating

20%

Call setup time (latency) is measured by the simulator playing the initiating role.

SCC originating with provisional SRVCC

A simple originating SCC call with SRVCC and enabled. B party accepts the call. The call has a variable hold time from 10 seconds to 180 seconds.

Latency is measured from the A party INVITE, to the A party ACKing the 200.

SCC T-ADS

A terminating SCC call with T-ADS. VOPS lookup receives a negative result, call T-ADS to CS and is answered. The call has a 25s hold time.

Latency is measured from the A party INVITE, to the A party ACKing the 200.

Access-Transfer Originating

An originating call with access-transfer. The call is answered then transferred to another bearer after 15s. The call continues for a further 120s.

Latency is measured from the A party INVITE, to the A party receiving the 200.

Previous page Next page