BFX – the world’s most advanced multi-protocol routing and interworking signaling gateway – is in use for many different use cases with service providers all over the world. BFX helps providers to cost-effectively and quickly enable services and overcome signaling challenges in multi-vendor, multi-technology networks. Some examples of customer use cases implemented with BFX are listed below.
Call Barring (Black/White listing)
BFX provides a dynamic network based call barring function. It enables operators to create a call barring list for A-Numbers, B-Numbers or combinations of A- and B-Numbers. These barring entries are provisioned on BFX. For each call request, BFX verifies the call barring list in order to allow or block individual calls.
Enterprise Gateway (M2M/IoT)
BFX provides intelligent routing functions enabling an enterprise – owning their own IMSI range (and associated SIM cards) – to choose another network provider without the need to swap SIM cards. BFX powers the world first Private Virtual Network Operator (PVNO) for a Dutch energy company with millions of smart meters.
DRA running as VNF in OpenStack environment
BFX is provided as a Virtual Network Function within the ETSI compliant Network Function Virtualization Infrastructure. BFX can run in OpenStack Mitaka and Newton environments supporting VNF instantiation and scale-up/down and scale-out/in of BFX. BFX is ‘cloud-aware’, with separately scalable management, traffic and database functions.
DRA in the cloud
BFX provides the DRA/DEA function as a virtualized network function on a common platform run from the cloud. BFX runs in the Amazon AWS Cloud supporting a high available architecture. The cloud-native BFX solution enables the migration of signaling operations from proprietary appliance based systems to a standard hardware and cloud based infrastructure.
Multi-IMSI for roaming
BFX provides a Multi-IMSI roaming function which enables roaming capabilities for partner MNO’s and MVNO’s via the operators IMSI. BFX achieves this by mapping the roaming IMSI to the home IMSI for all signaling services for roaming subscribers.
ENUM server for IMS
BFX acts as a server for ENUM queries (for Number Portability / number resolution), where the incoming ENUM requests can be forwarded to external data sources over any of the protocols BFX supports (e.g. ENUM, INAP, MAP, HTTP, …) or served from a local cache or local database on-board of BFX. BFX is in use at large service providers with hundreds of millions of database records on BFX.
BFX provides an HTTP proxy function enabling interoperability between different HTTP formats as XML, SOAP, REST and JSON. BFX handles protocol incompatibilities, enabling multiple systems to communicate with each another irrespective of the HTTP-format used. This function is in use with operators and enterprises.
Telco-IT interworking gateway
BFX provides the interworking gateway between the telco- and the IT-domain. Responses from either domain are evaluated by BFX and are used to adapt the original service request (e.g. block the service, re-route the service etc.). This enables the operator to extend Telco signalling scenarios into the IT domain enabling new services. This function is in use at several operators enabling scenarios such as INAP to HTTP, MAP to HTTP and INAP to LDAP.
FMC, Fixed/Wi-Fi to cellular authentication
BFX provides interworking between AAA and HSS/HLR for EAP-SIM authentication of Wi-Fi users in the Mobile core. In addition, BFX integrates AAA with the mobile OCS and PCRF function, to provide unified billing and policy across Wi-Fi and mobile services. BFX converts RADIUS to Diameter (Gx/Gy) while accommodating for the differences with respect to charging/usage counters between both protocols.
BFX helps operators to work around limitations in HSS systems that only allow for a maximum of two direct MME connections or lack a license for DRA integration. The “Virtual MME” function on BFX allows the HSS to service as many MMEs as are needed for roaming, without the need to provision them on the HSS. The existing HSS with the aid of BFX can support hundreds of connections. In addition the HSS is not required to support interfacing with a DRA as BFX presents itself to the HSS as just two MME nodes.