Billing Integration Function – OSS/BSS and Core Network integration

YateBIF is a charging gateway that integrates Telecom charging protocols into Billing products. All charging functions are delivered to the billing system as structured HTTP requests. This way, the billing platform does not need to support each front-end protocol.

The OSS/BSS integration with the Core Network can be a difficult technical process – it entails huge investments and time. Most billing companies are faced with certain challenges when it comes to billing integration.

YateBIF solves all those challenges by receiving CDR messages from the mobile operator’s Core Network using any type of communication protocols – Diameter, Radius, CAMEL, SS7 MAP (for SMSs) – and sends it over to the billing system through HTTP (JSON API). 

Billing companies need to overcome the industry challenges

  • Reduce your high OPEX caused by the integration process
    » Billing integration is both expensive and time-consuming. Billing companies spend a huge part of their budget to achieve a successful integration. This leaves them with low profits or no profits at all.
    » The problem here is that billing companies cannot serve more customers at once due to a lack of resources.
  • Overcome the lack of technical expertise in communication protocols
    » Most OSS/BSS companies are not specialized in communication protocols. Communication protocols need to be integrated properly and correctly - you need technical knowledge for that. This is why integration is often hampered.
  • Implement a simple technical solution that provides all the features you need
    » Currently, billing companies use a complicated technical solution. They manage to get all the features they need by acquiring different products.
    » This requires a lot of support from equipment vendors and it is not cost-effective.
  • Develop a general integration solution that works for every type of Core Network
    » The billing integration is done for each client at a time. This means billing companies are losing efficiency. They install custom integration for everyone of their customers.
    » This approach is keeping the engineers busy and keeps the company from growing.

YateBIF solves all those barriers by:

  • Saving your resources for better profits
    ✓ You don't waste time or money because the integration is easy to perform. YateBIF received charging information on various protocols.
    ✓ It is a cost-effective solution with low maintenance costs and we offer 6-months of free support.
    ✓ You can also install it on a virtual machine and avoid the hardware costs.
  • Reducing the technical knowledge needs
    ✓ YateBIF is an integrated charging gateway function with all the extra features included - SRF, USSD-GW and SMS-GW
    ✓ You don't need engineers specialized in communication protocols. The integration with YateBIF is done via JSON API (HTTP).
    ✓ It runs on commodity hardware, reducing deployment costs and management requirements
  • Allowing you to enter the Telecom market
    ✓ Billing companies that wish to serve the Telecom market can use YateBIF. It is specialized in Core Network communication protocols and delivers information via JSON.
    ✓ YateBIF is an opportunity to lower billing prices and increase your market share. If the prices are lower, then more operators would be encouraged to enter this business. This way, your market grows and brings you more customers.
  • Developing your business by serving more customers
    ✓ Reducing the time of deployment for every project is an opportunity for you to serve more customer at once and do more in your business.
    ✓ YateBIF is a scalable solution. Once you integrate it to your OSS/BSS system, you can just add more functions if needed.
    ✓ If you don't use up your resources for integration, you can redirect them to the company's development and growth.

YateBIF components

  • CGF - Charging Gateway Function
    » It receives charging information on various protocols.
    » This is the major component of YateBIF. CGF interconnects to the Telecom functions that produce charging data or require online (prepaid) charging.
    » It supports CAMEL, Diameter and RADIUS protocols.
  • SRF - Specialized Resources Function
    » It plays prompts for voice calls.
    » This component is used to play the prompts when voice calls are controlled by CAMEL to gsmSSF or by RADIUS to a SBC or other type of voice switch.
  • USSD Gateway
    » Allows user interaction via USSD menus and notifications.
    » The USSD Gateway component allows the billing platform to offer a menu-based end-user interface.
    » It also supports network initiated notifications and menus.
    » USSD is an interactive session service and requires that the subscriber has coverage.
  • SMS Gateway
    » Allows user interaction via SMS.
    » For persistent interaction with the subscriber YateBIF includes a SMS Gateway function.
    » SMS is a store-and-forward service, messages are delivered when the subscriber is online.

YateBIF features

  • YateBIF runs on commodity hardware, reducing deployment costs and management requirements
  • The operating system is Linux, well known in the servers world
  • Can be deployed on various types of Virtual Machines or in Cloud environments
  • Allows for scaling as you grow - you can add more servers as the subscriber base increases
  • Handles all mobile services - calls, messages and data
  • Simultaneous online and offline charging
  • Allows the end-user to interact with the billing system via voice prompts, USSD and SMS
  • Integration of configuration, management and monitoring via similar JSON API
  • Active/Active or K out of N redundancy by simply load balancing between multiple instances

Software Specifications

  • SS7 connectivity
  • SIGTRAN, SCTP/IP, Multipath
  • M2UA, M2PA, M3UA
  • ETSI MAP v3
  • E.212 or Translation Type (ANSI)
  • E.214 (ITU)
  • E.164
  • gsmSCF/MSC
  • ETSI MAP v3
  • Supported operations:
    • HLR <-> gsmSCF messages (USSD)
    • MSC <-> HLR messages (SMS Routing)
    • MSC <-> SMSC messages (SMS Forwarding)
    • VLR <-> HLR messages (Registration for SMS, optional)
  • SIP
  • RFC 3261 standard
  • SIP-T support (RFC 3372)
  • RTP (RFC3550) with sideband DTMF (RFC2833)
  • Codecs
  • G.711a, G.711u
  • GSM-FR 06.10, GSM-EFR, AMR-NB
  • G.722, AMR-WB (wideband)
  • iLBC
  • iSAC (wideband)
  • speex (narrowband, wideband, ultrawideband)n
  • USSD
  • Supports both USSD v1 and v2
  • Sessions can be user or network initiated
  • One-shot notifications (USSN)
  • Automatic conversion to UTF-8 on the application side
  • Templated Web service URL per USSD code
  • SMS
  • Format: Text or T-PDU (MO and MT)
  • MAP/SS7 transport (T-PDU format)
  • Registration to HLR (optional)
  • HTTP Interface
  • Templated URLs for each request type
  • HTTPS support for client and server
  • Configuration and management
  • Web interface
  • YAML/HTTP API (optional)
  • Authentication (optional)
  • Monitoring
  • Active agent for Zabbix server
  • Alarms via SNMP v2 or v3 traps
  • Status and stats via JSON/HTTP API
  • Operating system
  • Linux based

Virtual Machine specifications

  • CPU
    24 vCores (12C/24T)
  • RAM
  • Storage
    500 GB