Frequently asked questions about YateUCN

Do you have PCRF?

We have PCEF component in our solutions. PCRF is on the billing side. Nevertheless, we have two billing partners that we are working with (Aradial and Porta One) and can introduce you to.


Simplified NFV architecture

Supported


Use of Commodity Hardware (Dell, Hp, IBM etc. servers)

Supported


Flexible Hypervisor usage ( Vmware, KVM, Citrix etc.)

Supported

Notes: Virtualization / hypervisor needs to be configured for performance and tested


Compatible with small cell eNBs.

Supported


Probes/Analytics for high traffic & congestion management

Supported

Notes: Performance counters, congestion control


EMS for network nodes management (configuration & Fault)

Supported


Tools for KPI metrics measurement & Performance reporting

Supported

Notes: Zabbix server


Initial 100k concurrent subscribers scalable upwards.

Supported

Notes: 5 instances required for 100k EPS connections + IMS


WAG/Wifi/Wifi offload solution

Partially supported

Notes: WiFi RADIUS authentication by EAP-SIM, EAP-AKA. SIM authenticated ePDG. No VoWiFi support


3GPP Release 13 compatible

Supported


UL & DL AMBR enforcement

Partially supported

Notes: UL AMBR is enforced by ENB


Usage Monitoring at PCC rule level

Supported


IMSI level troubleshooting - Debug

Partially supported

Notes: Individual IMSI/MSISDN tracing only in HSS


3GPP compliant interfaces i.e. Gx, Gy, Sy, S11, S6a, S1,S5/S8S10,Rx,Sgi etc. and interface debugging

Partially supported

Notes: Only Gx, Gy, S6a, S1, S5/S8, SGi RADIUS for offline charging


Policing GBR Dedicated Bearers

Supported

Notes: GBR maximum limits configurable per AP


Volume based Reauthorisation request support

Supported


Time and Volume based quota exhaustion

Supported


Traffic Class to QCI mapping

Supported

Notes: Each QCI is mapped to a DSCP


Multiple APN Connection

Supported

Notes: Multiple APNs and aliases are supported


PGW Initiated Bearer modification with/without bearer qos update

Supported


Support MAP V1,2,3

Supported


Support CAMEL2,3

Supported


Diameter S6

Supported


DIAMETER over SCTP

Supported


SIP

Supported


allPacketOrientedServicesBarred

Supported


RoamerAccessToHPLMN-AP-Barred

Supported


RoamerAccessToVPLMN-AP-Barred

Supported


RoamingOutsidePLMNOG-CallsBarred

Supported


Barring Outgoing Calls (BAOC)

Supported


Barring of Outgoing International Calls (BOIC)

Supported


Barring of Incoming Calls except from Home Country (BOIC ex HC)

Supported


Barring of All Incoming Calls (BAIC)

Supported


Barring of Incoming Calls while roaming (BIC Roam)

Supported


RADIUS and GPRS Transparent Tunneling Protocol (GTTP) accounting

Supported


Several PDP Contexts (Primary/Secondary) and EPS Bearers (Default/Dedicated) activation

Supported


QoS support (maximum bandwidth limitation for the PDP);

Supported


QCI support

Supported


RADIUS authentication and authorization on AAA server;

Supported


Policy Control and Charging (PCC) architecture support in accordance with 3GPP TS 23.203 specification

Supported


GTP v1 and v2 support

Supported


Intra and Inter RAT handover procedures support in accordance with the 3GPP TS 23.401 specification

Supported


IP address allocation by existing DHCP server or AAA server via RADIUS protocol

Supported


What are MSRNS?

MO calls already start with MSISDN as Calling Party Number (A-number) and generally do not require any changes.

Only in the case of multi-MSISDN can home routing be required using CAMEL to rewrite the A-number to the desired one.
A MVNO never has MSRNs because it does not have MSCs to which MT calls should be routed.
It may instead have various other types of numbers for landing or services.
If it is MNO then it will have its own MSRNs which if it receives inbound roamers it will communicate to others under the conditions below.
If it does not have inbound roamers then the calls to MSRN will come only from their own GMSC and the rules are internal.
A MNO can tell you its own MSRN range, if those numbers are inaccessible from normal telephony and / or may require special routing.
It is common for an MNO to allocate special calling routes for:
MSRNs, possibly each MSC with its range and route (so that the MNO does not have to route between them, to get there from the first place)
MO calls that are home routed by local rules set by the MNO
Separate Billing - Many billing platforms require separate physical trunks or addresses to separate MVNO / local roaming from interconnect billing

Definitions:
Local / national roaming = the MVNO subscriber is in the MNO network with which he has a contract
Roaming (generic / international) = the MVNO subscriber is in a different network than the MNO with which he has a national contract
Interconnect = call between different networks (A and B are not subscriptions of the same operator) regardless of roaming


How many GTP sessions your PGW supports?

On a Ethernet link of 40Gb/s, maximum IPv4 useful data will be 38,4 Gb/s and if IPv6 is used the maximum will be 37,88 Gb/s.


If I want just the PGW from the UCN, do I get a discount?

We have public pricing and sell the entire license. The price is for all the features and you will get all of them, but can use only some components of it, depending on your needs.