.png){kind=logo}
.png)
.png)
.png)
.png)
Fully containerized cloud-native IMS
Our flagship product – our fully containerized and cloud-native IMS – is the first 100% containerized and Kubernetes-based full feature IMS solution for VoLTE/ VoNR with under 25MB of container image size.
Fully containerized IMS for VoLTE and VoNR
Our flagship product is a fully containerized and cloud-native IMS, which is the first 100% containerized and Kubernetes-based solution for VoLTE/VoNR, with a container image size of less than 25MB. It's ideal for operators looking to future-proof their 4G/5G networks while prioritizing cost-effectiveness and ease of deployment. Our solution offers the full suite of IMS features, ensuring that our clients can take advantage of the latest advancements in this space. Additionally, our products are infrastructure agnostic, meaning they can be easily deployed on any cloud platform.
Discover our solutions
ng-voice IMS Application Servers
ng-voice IMS Core
ng-voice IMS Core
P-CSCF, I-CSCF, S-CSCF, E-CSCF (Emergency Call Session Control Function), BGCF (Breakout Gateway control Function ...
Read more
ng-voice IMS Application Servers
(AGW) Authentication Gateway, IP-SM-GW (IP Short Message Gateway), MMTel/TAS (Multimedia Telephony Application Server) ...
Read more
ng-voice PCRF
Policy and Charging Function (PCRF)
The PCRF dynamically allocates and manages bandwidth requirements for various use cases. For VoLTE/VoNR, it is required to provide a better QoS and, in turn, an excellent user experience. The PCRF provides the QoS ...
Read more
ng-voice HSS
HSS (Home Subscriber Server)
ng-voice provides a software solution for the Home Subscriber Server (HSS), Home Location Register (HLR), Authentication Centre (AuC), and Equipment Identity Register (EIR) functionalities. ng-voice's subscriber database solution ...
Read more
ng-voice ePDG/AAA
ePDG/AAA (Evolved Packet Data Gateway / Authentication Authorization Accounting)
Operators who want to supplement LTE coverage by offering VoWiFi to their end-users require the addition of an AAA and ePDG to the Packet Core and IMS. Subscribers can then use WiFi to ...
Read more
ng-voice IMS Application Servers
AWG Authentication Gateway
The Authentication Gateway (AGW) acts as HTTP Proxy for other services, providing authentication using the HSS and SIM-Card credentials. Typical use cases are the Ut-Interface for supplementary service configuration or other custom web-based services. It supports Header insertion, URL rewriting as well as load sharing and failover capabilities.
The AGW is compliant to 3GPP release 15. Applicable standards include 3GPP TS 33.220.
IP-SM-GW (IP Short Message Gateway)
The ng-voice IP-SM-GW provides SMS interworking between native VoLTE handsets and other networks using a standard MAP protocol. While the SIP protocol is one of the most popular protocols used for voice calls, SS7/MAP (Mobile Application Part) is a widely used protocol for SMS service. MAP is used between the SMSC and IP-SM-GW to allow MO-SM origination and MT-SM delivery over the IMS. CS terminating SMS is also delivered via the SMSC and signaling passes the IP-SM-GW if the SMS originates on IMS.The solution supports S6c diameter interface towards HSS to enable the retrieval of routing information for the transfer of short messages and to report the status of the delivery status of a short message. Together with its “Store and forward” capabilities, it eliminates the requirement for a standalone SMSc in pure 4G/5G networks.The IP-SM-GW is compliant to 3GPP release 15.
MMTel/TAS (Multimedia Telephony Application Server)
The MMTel enhances the telephony service with the following features:
- Call Forwarding (unconditional, busy, not available, timeout)
- Call Forward Targets (to number or voice box)
- Call Blocking (inbound, outbound, anonymous call rejection, black-lists, white-lists, matching patterns)
- CLIP/CLIR
- Dialing patterns
- Network announcements through MRF
- Full feature-set in alignment with GSMA IR.92
Besides talking to the IMS Core and or MRF using the standardized ISc Interface, it provides the following external interfaces:
- Sh-Interface (Diameter) towards the HSS for storing and retrieving the settings from a centralized HSS
- Ut-Interface (XCAP) towards the User-Equipment (UE) for configuring the settings directly on the handset
- It may also integrate with the IT systems via Diameter over the Rf reference point.
The MMTel is compliant to 3GPP release 15. Applicable standards include 3GPP TS 29.328, TS 29.329, TS 24.623, TS 24.607. TS 24.604 and GSMA IR 92.
Media Resourse Function (MRF)
The ng-voice MRF provides media-related functions such as conferencing and announcements. The ng-voice MRF is a combined MRFC (Media Resource Function Controller) with a MRFP (Media Resource Function Processor).The MRF is compliant to 3GPP release 15. Applicable standards include RFC 4240 and 3GPP TS 24.229.
SCC-AS (Service Centralization and Continuity Application Server) / T-ADS (Terminating Access Domain Selection)
The ng-voice SCC-AS with SRVCC functionality provides seamless handover from a 4G packet-switched networks towards a legacy 2G/3G circuit switched network as well as T-ADS functionality. In case a handover is requested by the MSC of the 2G/3G network, a voice call towards the Session-Transfer Number (STN-NR) is initiated and the ng-voice SCC-AS initiates an RE-INVITE (for connected sessions) or an UPDATE (for sessions in early stage) to the other party to update the Media-Path for a session, in accordance with RFC 3891. SRVCC is implemented according to 3GPP Release 8. Furthermore, the SCC-AS provides the T-ADS functionality to enable proper domain selection for correct call routing. In ng-voice’s T-ADS solution, calls are terminated by default to ng-voice’s IMS. An IMS registration check of the terminating user determines whether the IMS continues routing the call over IMS or routes the call back to the CS network.
LI (Lawful Intercept)
The IMS Platform, as a communications platform carrying voice, fax, and messaging data has to provide means for lawful interception of the content of communication by third-party entities. Law Enforcement Agencies (LEAs) have to be able to connect to the IMS platform in a standardized way — ETSI, 3GPP, and other organizations define the interface (and data exchange) between telecommunication operators and LEAs.
ng-voice provides the X1, X2, X3 interfaces:
- X1 – The X1 interface is used by an LI provider to create, modify, delete, and list interceptions on the IMS platform
- X2 – The X2 interface is a TLV (Type–length–value) based interface with a simple request/response mechanism over a secure TLS connection, used to pass intercepted signaling data towards an LI provider.
- X3 – The X3 interface is also a TLV-based interface with a binary payload encapsulating the intercepted RTP data.
USSD (Unstructured Supplementary Service Data) Gateway
USSD is typically used to provide supplementary services, such as credit-queries and cash-up for prepaid services. It may also be used for any other service, such as interactive news retrieval or any other text-based and interactive service.ng-voice provides a simple to use and easy to integrate USSD-Gateway which allows you to quickly build and integrate USSD-services without having the need to fallback to 2G/3G for using such services. It connects directly to the IMS-Core using a standardized ISc-Interface and can send and retrieve the user input and the responses from and to a subscriber from a web-based service.
ng-voice IMS Core
P-CSCF
The Proxy-CSCF is an edge access function and is the entry point for a UE to request services from an IMS network. This CSCF acts as a proxy by accepting incoming requests and forwarding them to the entity that can service them. Examples of requests include registration and invitation for a multimedia session. ng-voice’s P-CSCF consists of the control component, the media handling component, and session storage components - following a truly cloud-native and microservices approach.
Main Features of ng-voice’s P-CSCF:
- Signaling firewall and user identity assertion (P-Preferred-Identity, P-Asserted-Identity header support)
- Integrity protection and optional encryption based on IPSec
- Rx-interface towards the PCRF in order to ensure QoS on the mobile network and to achieve the highest quality for Voice- and Video-Calls
- Transcoding of the following codecs:
- G711a/u
- G722
- AMR
- AMR-WB
- and various others
- Lawful intercept interfaces: X1, X2, and X3
- It is fully compliant with 3GPP release 15 and implemented according to 3GPP TS 29.214 and 3GPP TS 24.229
I-CSCF
The I-CSCF determines which S-CSCF should be assigned for handling the session requested by the UE. The I-CSCF determines the most suitable serving S-CSCF by inspecting the UE capabilities as well as the capabilities of the available S-CSCFs.
The ng-voice I-CSCF is optimized for speed and minimalist state information is kept in it.
The I-CSCF is compliant with 3GPP release 15 and implemented following the 3GPP Specs TS 29.228, 3GPP TS 29.229 and TS 24.229.
S-CSCF
The S-CSCF is responsible for conducting both session control and registration. It is responsible for maintaining the state of sessions and registrations and will trigger applications either provided by ng-voice or by a third party based on the service-profile provided by the HSS and using a 3GPP compliant ISC interface.ng-voice’s S-CSCF consists of the control component and session storage components - following a truly cloud-native and microservices approach.
The S-CSCF is compliant with 3GPP release 15 and implemented following the 3GPP Specs TS 29.228, 3GPP TS 29.229, 3GPP TS 24.229 and 3GPP TS 32.229.
E-CSCF (Emergency Call Session Control Function)
The ng-voice MRF provides media-related functions such as conferencing and announcements. The ng-voice MRF is a combined MRFC (Media Resource Function Controller) with a MRFP (Media Resource Function Processor).The MRF is compliant to 3GPP release 15. Applicable standards include RFC 4240 and 3GPP TS 24.229.
BGCF (Breakout Gateway Control Function)
The ng-voice BGCF acts as a Gateway between the IMS and other networks. It allows manipulation of the signaling to meet requirements either on the IMS or on the outbound Gateway - in order to simplify Interworking between networks.
Main Features of ng-voice’s BGCF:
- Outbound routing based on source-number and destination-prefix
- Caller-ID and R-URI manipulation for out- and inbound calls
- Authentication for outbound calls
The BGCF is compliant to 3GPP release 15. Applicable standards include 3GPP TS 24.229.
ENUM (E.164 Number Mapping)
The ENUM server maps the telephone number of the destination into an URI (Uniform Resource Identifier). The URI is a SIP phone number that identifies the destination network. The ENUM server provides an API for provisioning and an option for bulk uploading provisioning entries. It can provide support for Number portability based on RFC4694.The ENUM is compliant to 3GPP release 15.
ng-voice PCRF
Policy and Charging Function (PCRF)
The PCRF dynamically allocates and manages bandwidth requirements for various use cases. For VoLTE/VoNR, it is required to provide a better QoS and, in turn, an excellent user experience. The PCRF provides the QoS authorization that decides how a certain data flow will be treated in the PCRF, typically the PGW, and ensures that this follows the user’s subscription profile.
Main Features of ng-voice's PCRF:
- Support for the Diameter Gx interface with PGW/GGSN as per 3GPP TS 29.210
- Support for the Diameter Rx interface with CSCF as per 3GPP TS 29.214
- Support for Dynamic PCC rules
- Support for both session and bearer binding as per 3GPP TS 23.203 during IMS default and dedicated bearer setup and teardown
- Provision of QoS information
- Support for network-initiated dedicated bearer establishment based on application (e.g., the P-CSCF) request over the Rx interface
- Support for Network Provided Location Information during IMS call-initiation
The PCRF is compliant with 3GPP release 15. Applicable standards include 3GPP TS 29.212, TS 23.203, TS 29.213, and TS 29.214.
ng-voice HSS
HSS (Home Subscriber Server)
ng-voice provides a software solution for the Home Subscriber Server (HSS), Home Location Register (HLR), Authentication Centre (AuC), and Equipment Identity Register (EIR) functionalities. ng-voice's subscriber database solution supports 3G, 4G, and 5G technologies and VoLTE, VoNR, and VoWiFi services. The HSS is the System Architecture Evolution (SAE)'s central database in LTE networks where important subscriber information is stored. GSM networks have a Home Location Register (HLR) and Authentication Centre (AuC). The equivalent of this in LTE networks is the HSS. The MME/SGSN communicates with the HSS over the S6a/S6d Diameter interface for authentication, location, and service information about the subscriber. Besides LTE, the HSS is also a functional element of IMS/VoLTE. The HSS database supports the IMS network entities that handle calls/sessions. It contains user profiles, performs authentication and authorization of the user, and can provide their location information. From an IMS perspective, the components communicating with the HSS are the Application Servers (AS) and Call State Control Function servers (CSCFs). Upon being queried by the Interrogating-CSCF (I-CSCF) when SIP registration is performed, the HSS retrieves the Serving-CSCF (S-CSCF) address and assigns it to a user. The user's information and profile data are then downloaded from the backend database and stored by the HSS, where the data can be accessed. After successful authentication on the same interface, the S-CSCF downloads the subscriber's profile over the Cx Diameter interface. The profile contains the Initial Filter Criteria providing the logic to the IMS for triggering SIP messages to the appropriate Application Servers. Application Servers (AS) access the HSS over the Sh diameter interface. Besides public identifiers, IMS user identities, and location information, the HSS also stores repository data related to a service (e.g., Supplementary Service data). Furthermore, the Authentication, Authorization, and Accounting (AAA) function communicates with the HSS over the SWx interface to support non-3GPP access to the network for VoWiFi service. ng-voice's subscriber database solution also provides Authentication Centre (AuC) and Equipment Identity Register (EIR) functionalities. The AuC provides authentication parameters (e.g., authentication vectors) for the authentication process. The EIR provides blacklisting/whitelisting functionalities over the S13 interface.
Main Features of ng-voice’s subscriber database solution:
- Supported interfaces include:
- S6a and S6d interfaces provide procedures for attaching the device to 3G and 4G packet networks.
- Cx and Sh interfaces provide procedures for accessing IMS services.
- SWx interface providing procedures for VoWiFi access.
- Zh interface provides authentication procedures for Supplementary Service configuration.
- The S6c interface provides procedures for SMS operations with the HSS.
- 5G interfaces including Nhss, NU1, NU2, N70 and N71.
- SS7 MAP interfaces, including MAP C and MAP D, through an additional interworking function, translating S6d to MAP - Authentication procedures included EPS AKA, IMS AKA, and 5G AKA.
- Provisioning through REST-based APIs.
- User Management through GUI
- Robust and geo-redundant backend database
The HSS is compliant to 3GPP release 17. Applicable standards include 3GPP TS 29.228, 3GPP TS 29.229, TS 24.229, TS 29.328 and TS 29.329.
Supported interfaces include:
- S6a and S6d interfaces, which provide procedures for attaching the device to 3G and 4G packet networks
- Cx and Sh interfaces, which provide procedures for accessing IMS services
- SWx interface, which provides procedures for VoWiFi access
- Zh interface, which provides authentication procedures for Supplementary Service configuration
- S6c interface, which provides procedures for SMS operations with the HSS
- 5G interfaces, including Nhss, NU1, NU2, N70, and N71
- SS7 MAP interfaces, including MAP C and MAP D, through an additional interworking function translating S6d to MAP
- EPS AKA, IMS AKA, and 5G AKA authentication procedures
- Provisioning through REST-based APIs
- User Management through GUI
- Robust and geo-redundant backend database.
The HSS is compliant with 3GPP release 17. Applicable standards include 3GPP TS 29.228, 3GPP TS 29.229, TS 24.229, TS 29.328, and TS 29.329.
ng-voice ePDG/AAA
ePDG/AAA (Evolved Packet Data Gateway / Authentication Authorization Accounting)
Operators who want to supplement LTE coverage by offering VoWiFi to their end-users require the addition of an AAA and ePDG to the Packet Core and IMS. Subscribers can then use WiFi to access EPC networks when LTE coverage is unavailable. As there are different access networks in scope, there is a need for handover between VoLTE and VoWiFi to ensure continuity of services. Hence, the handover function is one of the features of our solution. VoWiFi subscribers use the ePDG to attach to an EPC network and then register with the IMS network. The ePDG interworks with the AAA server to authenticate the UEs. After UE authentication, the ePDG forwards messages to the PGW over the S2b interface.
Main Features of ng-voice's ePDG/AAA:
- The ePDG communicates with the AAA and PGW, providing signaling and data channels for UEs
- The AAA communicates with the ePDG over the SWm interface to authenticate VoWiFi subscribers
- The AAA communicates with the PGW over the S6b interface and with the HSS over the SWx interface
The ePDG/AAA is compliant with 3GPP release 15. Applicable standards include 3GPP TS 23.402, TS 33.402, TS 29.273, and TS 29.274.
