The BroadForward portfolio of routing, interworking, security and number portability products enables many more signaling use cases for operators globally. Here is an overview of some of the signaling scenarios implemented at operators: HTTP Proxy, ENUM server for IMS, Black/White listing, DRA in the cloud, Virtual MME and many more.
Call Barring (Black/White listing)
Security: BroadForward provides a dynamic network-based call barring function. It enables operators to protect their subscribers and networks by blocking nuisance and scam calls at the network level. Using the BroadForward call barring function, the operator can create a call barring list for A-Numbers, B-Numbers or combinations of A- and B-Numbers. These barring entries are provisioned on the BroadForward solution. For each call request, it verifies the call barring list in order to allow or block individual calls.
Enterprise Gateway (M2M/IoT)
Routing: BroadForward 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. The solution today 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
Routing: The BroadForward DSC is provided as a Virtual Network Function within the ETSI compliant Network Function Virtualization Infrastructure. It can run in OpenStack Mitaka and Newton environments supporting VNF instantiation and scale-up/down and scale-out/in. The BroadForward DSC is ‘cloud-aware’, with separately scalable management, traffic and database functions.
DRA in the cloud
Routing: The BroadForward DSC provides the DRA/DEA function as a virtualized network function on a common platform run from the cloud. It runs in the Amazon AWS Cloud supporting a high available architecture. The cloud-native BroadForward DSC enables the migration of signaling operations from proprietary appliance based systems to a standard hardware and cloud based infrastructure.
ENUM server for IMS
Number Portability: BroadForward Number Portability 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 it supports (e.g. ENUM, INAP, MAP, HTTP, …) or served from a local cache or local database on-board. BroadForward Number Portability is in use at large service providers with hundreds of millions of database records on the BroadForward Number Portability installation.
Telco-IT interworking gateway
Interworking: BroadForward interworking provides the interworking gateway between the telco- and the IT-domain. Responses from either domain are evaluated by the gateway 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
Interworking: BroadForward interworking provides interworking between AAA and HSS/HLR for EAP-SIM authentication of Wi-Fi users in the Mobile core. In addition, BroadForward interworking integrates AAA with the mobile OCS and PCRF function, to provide unified billing and policy across Wi-Fi and mobile services. BroadForward interworking converts RADIUS to Diameter (Gx/Gy) while accommodating for the differences with respect to charging/usage counters between both protocols.
Routing: The BroadForward DSC 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 the BroadForward DSC 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 the BroadForward DSC can support hundreds of connections. In addition the HSS is not required to support interfacing with a DRA as the BroadForward DSC presents itself to the HSS as just two MME nodes.