Skip to main content

Telecom Network FAQs

Everything you need to know about Summa Networks' products in one place. 100+ questions organised by product — HLR/HSS, 5G, PCRF, SMSC, VoLTE, IMS and AAA.

This telecom network FAQ covers Summa Networks’ core products: HLR/HSS, 5G SDM, PCRF, SMSC, VoLTE, IMS and AAA.

Summa Networks customer?

Frequently Asked Questions

Frequently Asked Questions by Product

Answers to the most common questions about Summa Networks’ products, organised by product. Use the search or filter by product to jump straight to what you need.

Service Templates

Service templates in Summa Networks’ NextGen HSS are designed to improve the provisioning and management of subscriber profiles. They allow operators to create basic elements of HLR and HSS profiles once and reuse them across multiple templates, reducing repetitive tasks during subscriber creation.

Service templates streamline the provisioning process by allowing operators to define and reuse profile elements. This prevents repetitive tasks and ensures consistency across subscribers.

The Summa NextGen HSS allows operators to create subscribers that either share all objects from common service templates or have completely independent objects. This flexibility enables a wide range of options, such as having shared APNs and individual entities for each subscriber.

Service templates can categorise users based on the services they are associated with. For example, administrators can create pre-paid, premium and corporate service templates, each with specific services, supplementary services and PDPs activated for those categories.

Examples of services that can be included in service templates are APNs (Access Point Names), supplementary services, PDP (Packet Data Protocol) contexts and other network-related entities. These services can be predefined and linked to different templates based on the user category.

Service templates enhance efficiency by allowing operators to define reusable profiles, reducing the need for repetitive setup tasks. This consistency also ensures that all subscribers within a template receive the same predefined services, simplifying management and updates.

Yes. Administrators can create different types of service templates to suit various user groups, such as pre-paid users, premium users and corporate users. Each template can have specific services and configurations tailored to the needs of those groups.

Interfaces and Communication

The Summa NextGen HSS supports the Nudm, Nhss and Nudr interfaces for direct interworking with the User Data Management (UDM) and User Data Repository (UDR) in 5G networks.

HLR/HSS Compatibility, Security, and Features

HLR/HSS solutions are designed to support various telecommunications networks, including legacy circuit-switched networks (e.g. GSM, CDMA) and next-generation packet-switched networks (e.g. LTE, IMS). They can be deployed in both mobile and fixed-line networks, providing essential subscriber management functions across different network technologies.

Securing an HLR/HSS deployment relies on a few core practices: strong data protection, strict access control, and continuous system monitoring, backed by regular audits, vulnerability assessments and timely security updates. Reliability comes from building in redundancy and failover mechanisms, so the subscriber databases stay available even in the event of a failure or disruption. Summa Networks supports operators in applying these practices — and, as an ISO/IEC 27001:2022-certified company, applies internationally recognised information-security standards to its own processes.

General Information

Summa SDM 5G is a solution that provides system architecture, scalability and a subscriber data model for 5G networks. It includes various Network Functions (NFs) such as the Authentication Server Function (AUSF), Unified Data Management (UDM) and User Data Repository (UDR).

Summa SDM 5G can be deployed as a standalone process on a virtual machine, inside a container such as Docker, or alongside other pods using an orchestrator such as Kubernetes.

Architecture and Components

The key components are the AUSF (Authentication Server Function), the UDM (Unified Data Management) and the UDR (User Data Repository).

Summa SDM 5G complies with several 3GPP standards, including TS 23.501, TS 23.502, TS 29.500, TS 29.501, TS 33.501 and TS 23.632.

Features and Functionality

The UDM provides functionalities such as generating 3GPP AKA authentication credentials, user identification handling, access authorization based on subscription data, service/session continuity, MT-SMS delivery support, lawful intercept functionality, subscription management and SMS management.

Summa SDM 5G uses the HTTP/2 protocol for 5G communications, both for the 3GPP standard API and the management API.

Technical Details

The UDM supports several service operations, including: get security information; generate authentication vectors (4G and 5G); manage subscriber data; register and deregister UE contexts; and subscribe and unsubscribe to event notifications.

Interworking and Compatibility

Summa SDM 5G implements an interworking function to ensure functional decoupling between 4G and 5G systems, allowing for dual or standalone installations.

Yes. Summa SDM 5G can interconnect with other telco elements using the HTTP/2 protocol, for both the 3GPP standard API and the management API.

Deployment Scenarios

For a 5G SA global solution, Summa Networks recommends a converged and extended control plane solution that includes all necessary control-plane NFs and uses a single database to manage all subscriber data.

Compliance and Standards

Summa SDM 5G supports a wide range of 3GPP services, including Nausf_SoRProtection, Nausf_UPUProtection, Nausf_UEAuthentication, Nudm_UEAuthentication, Nudm_SubscriberDataManagement, Nudm_UEContextManagement, Nudm_EventExposure, Nudm_ParameterProvision and Nudm_NIDDAuthorization.

Summa SDM 5G implements specifications from 3GPP TS 29.509, TS 29.503, TS 29.504 and TS 29.505, covering various aspects of network functions and subscriber data management.

AUSF Features

The AUSF component supports: HTTP/2 with TLS; OAuth 2.0; NRF registration and discovery, with fallback to local configuration if the NRF is not available; communication models C and D; 5G-AKA basic authentication; and EAP-AKA basic authentication.

UDM Features

The UDM component supports: HTTP/2 with TLS; OAuth 2.0; NRF registration and discovery, with fallback to local configuration if the NRF is not available; communication models C and D; NEF discovery; validation of the serving network name against the peer; 5G-AKA basic authentication; EAP-AKA basic authentication; and provisioning of subscription data for 5G roaming scenarios.

UDR Features

The UDR component supports: HTTP/2 with TLS; OAuth 2.0; NRF registration and discovery, with fallback to local configuration if the NRF is not available; and communication models C and D.

Interworking with 4G

5G coverage expands gradually. During this period, users who need wide-area mobility and stable IP addresses can rely on other radio access technologies when out of 5G coverage. Summa NextGen HSS and Summa SDM 5G both meet the requirements for 4G and 5G interworking as specified in 3GPP Release 16.

Interworking is defined in the following 3GPP specifications: 3GPP TS 23.501 (5G System Architecture); 3GPP TS 23.632 (LTE and 5G User Data Interworking); and 3GPP TS 29.563 (HSS Services for Interworking with UDM).

In single-registration mode, the UE has one active Mobility Management state for 3GPP access toward the core network. The UE context information is transferred between systems when the UE moves between 4G and 5G, either via N26 or by moving each PDN Connection or PDU Session to the other system without N26.

In dual-registration mode, the UE maintains independent Mobility Management states for 3GPP access toward the 5GC and the EPC using separate RRC connections. The UE can be registered to 5GC only, EPC only, or both.

N26 is a signalling interface between the AMF and the MME to transfer the mobile’s authentication and session context between the two systems. It provides seamless mobility with minimal interruption to the mobile’s IP session.

When moving between EPS and 5GS without N26, the mobile may need to re-authenticate, causing an interruption. Single-registration capable mobiles could experience up to 3 seconds of interruption, while dual-registration capable mobiles can pre-register in both systems, reducing interruption to around 800 ms. The HSS and UDM maintain the session in both the MME and the AMF until the UE can successfully transfer the PDU session.

Introduction to PCRF

PCRF stands for Policy and Charging Rules Function. It is a key component of a telecommunications network that enables operators to implement policies for controlling data traffic, managing quality of service (QoS) and enforcing charging rules for various services. Summa Networks PCRF offers a range of features including VoLTE, VoWiFi and basic data capabilities, data policy and control functionalities, and transparent extension to 5G PCF. It supports seamless integration with various network elements and can function as a standalone entity or as part of a converged solution.

The PCF (Policy Control Function) is the 5G core function responsible for network policy — quality of service, charging rules and access control. It is the 5G evolution of the PCRF (Policy and Charging Rules Function) used in 4G networks. Summa Networks’ policy solution covers both: the PCRF for 4G and VoLTE/VoWiFi, with a transparent extension to the 5G PCF, so operators can move toward 5G policy control at their own pace and without replacing their core.

Stakeholders and Configuration

The key stakeholders are: Subscribers (end-users of the network services); Operators (network administrators and engineers managing the PCRF); and Plans (different subscription plans available for subscribers, each with specific policies and rules).

Subscribers and their associated plans are managed through the PCRF web interface, and the policy engine takes them into account while evaluating policies and choosing which plan is used during the session. The interface allows operators to add, modify and delete subscriber information and assign the appropriate plans.

Deployment and Operational Support

Deployment includes installing the PCRF software, configuring network settings, setting up communication protocols and integrating with other network elements.

Operational support involves monitoring system logs, troubleshooting issues and maintaining system performance. Regular updates and patches are also part of operational support.

Security, Compliance, and Network Compatibility

PCRF incorporates security mechanisms to authenticate users, authorise access to network resources and protect against unauthorised activities. It also helps operators comply with regulatory requirements related to data privacy, security and transparency by enforcing appropriate policies and controls. As an ISO/IEC 27001:2022-certified company, Summa Networks applies internationally recognised information-security standards to its own processes.

The PCRF solution is designed to support a wide range of telecommunications networks, including 4G mobile networks, fixed-line networks and converged networks. It can be customized to meet the specific requirements and scalability needs of different operators and network environments.

Summa Networks PCRF Features and Integration

Summa Networks PCRF is built on cloud-native architecture, allowing flexible deployment in any cloud environment, including containers on bare metal, Kubernetes, virtual machines (VMs) and hybrid models.

Yes. Summa Networks PCRF can be integrated with billing, rating, charging, subscriber databases and other 3GPP-compliant elements in the network. It offers both GUI and API functions for seamless interaction with CRM and other systems.

Summa Networks PCRF supports multiple high-value use cases, including VoLTE/VoWiFi deployments, simple data and quota management, and unified policy control for 5G networks. It adapts to diverse network requirements and can scale from small-scale to large-scale deployments.

Comparisons and Advanced Features

In VoLTE environments, PCRF interacts with LTE network components, enforces QoS policies specific to LTE networks and manages mobility during handovers. In VoWiFi environments, PCRF interacts with Wi-Fi infrastructure, ensures QoS over Wi-Fi and manages policies for roaming and interworking with mobile networks.

Upgrades are facilitated through an active-active configuration, allowing nodes to be isolated and upgraded individually without downtime. The system ensures continuous service availability and easy rollback in case of issues.

Voice PCRF vs. Full PCRF: Which One Fits Your Network Needs?

Voice PCRF is tailored specifically for VoLTE/VoWiFi/VoNR deployments, focusing on essential policy enforcement, charging and QoS management. It is designed for simplicity, ensuring quick setup and easy maintenance, and is light on system resources, making it ideal for environments with resource constraints. It is a cost-effective, resource-efficient option for operators that want essential functionality without added complexity, and it also supports 5G NSA for added versatility. Typical use cases include dynamic provisioning of VoLTE calls without subscriber provisioning, location-based filtering for optimising network resources, filtering calls based on IMEI numbers for device-specific policies, application of roaming rules based on MNC and MCC, device-model-based filtering for differentiated policies, time-specific policies such as “happy hour”, policy control for IMS sessions based on media type, priority handling for emergency traffic, and application of policies based on charging characteristics.

Full PCRF offers an extensive feature set, including advanced policy management, dynamic rule creation, and robust charging and billing functionalities. It is designed for large-scale deployments, capable of handling high-traffic network environments effortlessly, and supports complex scenarios such as network slicing, enterprise services and IoT applications. It provides flexibility with a wide range of policy rules and criteria, allowing for tailored solutions, and is compliant with 3GPP standards, integrating seamlessly with other network elements and services for comprehensive network management.

SMSC (Short Message Service Center)

An SMSC, or Short Message Service Center, is a core component of a telecommunications network responsible for the storage, routing and delivery of short text messages (SMS) between mobile devices. The SMSC is a network meta-element that incorporates the behaviour of other entities such as the SC (Service Center), IWMSC (Interworking Mobile Switching Center) and GMSC (Gateway Mobile Switching Center).

When a user sends an SMS message, it is first routed to the SMSC associated with their mobile network operator. The SMSC stores the message temporarily and determines the recipient’s location by querying the Home Location Register (HLR) or Home Subscriber Server (HSS). Once the recipient’s location is determined, the SMSC forwards the message to the recipient’s current location or delivers it to their device when it becomes available.

Yes. Summa Networks SMSC for IoT includes specialized services for handling large volumes of IoT device messages, optimizing delivery and status reporting for IoT communication, and supporting specific protocols commonly used in IoT applications. Its core principles are flexibility and adaptability (tailored to specific customer requirements with an open roadmap, capable of serving from a few hundred to millions of subscribers), transparent total cost of ownership, and a foundation on open standards and open-source solutions to offer a cost-effective, carrier-grade solution. Summa Networks SMSC for IoT adheres to standards compliance, staying compliant with the latest 3GPP release, and empowers smaller service providers to compete effectively in the IoT market.

The SMSC implements the following MAP services: handling MO Forward Short Message requests (TS 29002 12.2); sending MT Forward Short Message requests (TS 29002 12.9); sending Reports SM Delivery Status requests (TS 29002 12.3); handling Alert Service Center messages (TS 29002 12.5); and Status Report Capabilities (TS 23040 3.2.9).

Yes. The SMSC supports the SMPP protocol to send and receive messages. It functions as an SMPP Server and allows multiple known clients to connect securely. The latest version supported is SMPP v3.4.

The SMSC implements a routing system that enables routing messages from SMPP and from MAP. Users can determine how Short Messages are discarded, rejected, or routed between MAP and SMPP.

Yes. SMSC IoT includes advanced routing capabilities tailored for IoT device communication, allowing for efficient handling and prioritisation of messages from various IoT devices.

Yes. SMSC IoT offers enhanced monitoring features to track the performance and reliability of IoT device communication, including KPIs for message handling and device connectivity.

Security and Reliability

Securing an SMSC deployment relies on core practices: strong data protection, strict access control, and continuous system monitoring, backed by regular audits, vulnerability assessments and security updates. Reliability comes from redundancy and failover mechanisms that keep the SMSC available in the event of a failure or disruption. The SMSC also includes a capability to delete messages from specific numbers in the event of a spam attack, adding an extra layer of protection. As an ISO/IEC 27001:2022-certified company, Summa Networks applies internationally recognised information-security standards to its own processes.

Message Delivery

An SMSC employs various mechanisms to ensure message delivery in different scenarios: Immediate Delivery (messages are delivered instantly if the recipient is reachable and their device is available); Deferred Delivery (messages are stored and delivered later if the recipient is temporarily unavailable or their device is offline); and Delivery Reports (the SMSC sends delivery reports to the sender to confirm successful delivery or indicate any delivery failures or delays).

An SMSC implements protocols and mechanisms to ensure the reliability and integrity of message delivery: Message Queuing (messages are queued and resent automatically if delivery fails initially, ensuring reliable delivery); and Error Handling (the SMSC handles errors, retries delivery attempts and reports delivery status to the sender to maintain message integrity).

Benefits and Deployment

Some key benefits of deploying an SMSC include: Efficient Message Delivery (SMSCs ensure fast and reliable delivery of SMS messages, enhancing communication between subscribers); Scalability (SMSCs are scalable and can handle large volumes of messages, making them suitable for growing subscriber bases and network traffic); Flexibility (SMSCs support a wide range of messaging features and protocols, allowing operators to offer diverse messaging services to subscribers); and Revenue Generation (SMS services generate revenue for operators through messaging plans, value-added services and advertising partnerships).

The Short Message Service Center (SMSC) is integrated within the Home Subscriber Server (HSS) to provide comprehensive messaging services. It is set up within the HSS framework, configured for optimal performance and reliability, and can be integrated within existing network infrastructure and systems. Minimum recommended data sets are configured for LTE and HLR functionalities to ensure proper attachment on LTE and 3G networks.

Redcap SMSC for IoT

By providing enhanced connectivity, scalability and efficiency, RedCap SMSC for IoT enables businesses to drive innovation and success in today’s IoT-driven world. Its flexible and adaptable nature, transparent total cost of ownership, adherence to open standards and compliance with the latest 3GPP release contribute to fostering enduring partnerships and empowering smaller service providers.

IMS is a critical component in VoLTE architecture, as it provides the framework for delivering multimedia services over IP networks. IMS separates call control from the transport layer, allowing for efficient handling of voice and multimedia services. It manages session initiation, modification and termination using SIP (Session Initiation Protocol), and ensures interoperability between various network types and devices. IMS supports various services such as voice, video and messaging, facilitating a unified and flexible communication platform.

VoLTE enhances voice quality by using advanced audio codecs such as Adaptive Multi-Rate Wideband (AMR-WB) and Enhanced Voice Services (EVS). These codecs support a wider frequency range (50 Hz to 7 kHz for AMR-WB and up to 20 kHz for EVS) compared to the traditional narrowband codecs used in 2G and 3G networks. This results in clearer, more natural-sounding voice calls with reduced background noise and better overall audio fidelity.

Key components of VoLTE architecture include: P-CSCF (Proxy Call Session Control Function), the first point of contact for the UE (User Equipment) in the IMS network, handling SIP signalling; S-CSCF (Serving Call Session Control Function), which manages session control, maintaining session states and interacting with other network elements; I-CSCF (Interrogating Call Session Control Function), which serves as a SIP proxy, routing SIP requests to the appropriate S-CSCF; HSS (Home Subscriber Server), which stores subscriber data, authentication credentials and service profiles; and MGCF (Media Gateway Control Function), which interfaces with the PSTN (Public Switched Telephone Network), enabling communication between IP and traditional circuit-switched networks. These components work together to manage call routing, session control, subscriber data and interconnection with legacy networks.

VoLTE manages simultaneous voice and data sessions by employing Quality of Service (QoS) mechanisms and dedicated bearers. QoS ensures that voice traffic is given priority, maintaining low latency and high reliability. Dedicated bearers are established for voice calls, separating them from data traffic, which helps deliver consistent voice quality even when the network is congested.

In VoLTE, IMS handles session management while SIP is used for signalling. During call setup, SIP messages initiate and negotiate the session parameters between the caller and callee. IMS coordinates the establishment of media paths, manages session states and handles call modifications and terminations. This combination ensures seamless call establishment, maintenance and termination across IP networks.

VoLTE uses Single Radio Voice Call Continuity (SRVCC) to support seamless handovers between LTE and legacy networks (3G and 2G). SRVCC ensures that ongoing voice calls are not interrupted during handovers by transferring the call to the appropriate network without dropping the connection. This is crucial for maintaining service continuity and user experience in areas with varying network coverage.

VoLTE networks implement several security measures to protect against unauthorized access and data breaches: IPSec (Internet Protocol Security), which ensures secure data transmission over IP networks by encrypting the traffic; IMS-AKA (IP Multimedia Subsystem Authentication and Key Agreement), which authenticates users and devices, preventing unauthorized access; and fraud prevention mechanisms, which detect and mitigate fraudulent activities, safeguarding subscriber data and network integrity. As an ISO/IEC 27001:2022-certified company, Summa Networks applies internationally recognised information-security standards to its own processes.

Deploying VoLTE involves several software-related challenges: IMS infrastructure integration (it requires significant changes to the existing network architecture); QoS policy configuration (ensuring that QoS mechanisms are properly implemented to prioritize voice traffic); interoperability with LTE devices (ensuring compatibility between various devices and network components); and scalability and reliability (managing the increased load and ensuring reliable voice services as the number of users grows).

With the evolution towards 5G, VoLTE software architecture is expected to see several enhancements: support for advanced codecs (improved voice quality and efficiency); seamless integration with 5G networks (ensuring compatibility and a smooth transition); and enhanced scalability (supporting a larger number of users and new applications, such as IoT and critical communications).

The N26 interface is crucial for seamless mobility and continuity of IP sessions between LTE and 5G networks. It facilitates minimal interruption (under 300 ms) during network transitions, enhancing user experience by maintaining ongoing sessions without noticeable delays or disruptions.

In dual-registration mode, a device can simultaneously register with both the 5G Core (5GC) and the Evolved Packet Core (EPC). This maintains independent Mobility Management (MM) states, optimizing mobility and session management across both networks. In contrast, single-registration mode involves registration with only one core network at a time, potentially leading to less efficient handling of mobility and session continuity.

Direct UDM-HSS interworking involves ensuring that interfaces support seamless data exchange between the Unified Data Management (UDM) in 5G and the Home Subscriber Server (HSS) in legacy networks. This ensures compatibility and integration across different network generations, facilitating smooth transitions and unified subscriber management.

EPS fallback allows devices to switch to LTE for voice calls when under 5G NR coverage. This leverages existing VoLTE capabilities to ensure voice service continuity in areas where 5G networks do not fully support voice services. It ensures that users experience uninterrupted voice services even as they move between 5G and LTE coverage areas.

Supporting emergency services in 5G networks requires several enhancements: robust voice capabilities (ensuring reliable voice communication during emergencies); emergency PDU sessions (prioritized and dedicated sessions for emergency services); seamless N26 interworking (maintaining session continuity during transitions between 5G and LTE); and enhanced location services (providing accurate location data in compliance with regulatory standards to assist emergency responders).

VoNR enhances voice service continuity during roaming by minimizing call setup delays compared to EPS fallback. It ensures that users experience seamless voice services across different network environments, maintaining high-quality voice calls and reducing latency during network transitions.

Interworking between 4G and 5G networks enables seamless handovers and continuity of services, optimizing service delivery and user experience. This ensures that voice and data sessions are maintained without interruptions as users move between LTE and 5G coverage areas, providing a consistent and reliable experience.

Supporting IMS-based services like VoNR in 5G networks requires integration with the IMS core. This ensures compatibility and quality of voice services across 5G deployments. The network must support high data rates, low latency and robust QoS mechanisms to deliver superior voice and multimedia services.

QoS mechanisms are crucial for VoLTE service delivery, as they prioritize voice traffic over other types of data. This ensures low latency, high reliability and consistent voice call quality, enhancing user satisfaction. QoS policies manage network resources efficiently, preventing congestion and maintaining optimal performance for voice services.

VoLTE is a foundational technology that enhances voice services over LTE, setting the stage for the transition to 5G. It enables high-quality voice calls, efficient use of network resources, and supports new applications and services. As networks evolve to 5G, VoLTE’s principles and technologies are integrated into the new architecture, facilitating seamless integration and paving the way for advanced communication services.

The IMS core network provides: Session Management (handling the control and management of multimedia sessions); Service Delivery (ensuring efficient and reliable delivery of multimedia services across different access networks); and Interoperability (facilitating seamless communication and service continuity between IMS and other network domains).

The Home Subscriber Server (HSS) is a central database that stores user-related information. It contains user profiles, authentication credentials and service authorization details; supports the authentication and registration processes; and provides information to the S-CSCF during session setup and user registration.

IMS primarily utilizes the following protocols: SIP (Session Initiation Protocol), for initiating, managing and terminating sessions; Diameter, for Authentication, Authorization and Accounting (AAA) purposes; RTP (Real-Time Transport Protocol), for transporting real-time audio and video data; and SDP (Session Description Protocol), for describing multimedia session parameters.

IMS ensures QoS through mechanisms such as: Resource Reservation (using protocols like RSVP to reserve necessary resources); Policy Control (implementing policy rules via the Policy and Charging Rules Function, PCRF); and QoS Class Identifier (QCI), assigning specific QoS levels to different service types.

IMS security measures include: Authentication (ensuring that only authorized users can access the network using mechanisms like AKA); Confidentiality (encrypting SIP signalling and media streams to protect against eavesdropping); and Integrity Protection (ensuring that SIP messages are not tampered with during transmission). As an ISO/IEC 27001:2022-certified company, Summa Networks applies internationally recognised information-security standards to its own processes.

IMS supports interoperability with legacy networks through gateway functions and protocol conversion: the Media Gateway Control Function (MGCF) facilitates communication between IMS and circuit-switched networks; the Signalling Gateway (SGW) translates signalling protocols between IMS and legacy networks; and Media Gateways (MGW) convert media streams between IP and traditional telephony formats. Together, these translate signalling and media protocols to ensure compatibility with legacy systems.

IMS can be deployed in various ways, including: stand-alone IMS networks (dedicated IMS infrastructure); integrated IMS solutions (combining IMS with existing network elements); and virtualized IMS (deploying IMS functions on virtualized infrastructure for scalability and flexibility).

IMS supports scalability and flexibility through: Modular Architecture (allowing independent scaling of different network elements as needed); and Virtualization (enabling deployment of IMS functions on virtualized infrastructure for efficient resource utilization and rapid scaling).

The Diameter protocol in IMS is used for: Authentication, Authorization and Accounting (AAA), ensuring secure access to network services and accurate billing; Policy Control, facilitating communication between the PCRF and other network elements for enforcing QoS policies; and Information Request, where the IMS core requests information from the HSS using the Diameter interface.

IMS enables service personalization through: User Profiles (stored in the HSS, containing information about user preferences, service entitlements and settings); and Application Servers (delivering customized services based on user profiles and real-time context).

IMS manages user mobility by: Seamless Handover (supporting handover between different network types, e.g. 4G to Wi-Fi, without service interruption); and Location Management (using SIP registration and location services to track user location and route calls accordingly).

The IMS architecture is layered and consists of three main layers: the Transport Layer (handles the IP transport and ensures connectivity); the Control Layer (manages signalling and session control using SIP); and the Application Layer (hosts and executes various multimedia services).

The Proxy-Call Session Control Function (P-CSCF) is the first contact point within the IMS network for the user equipment (UE). It performs SIP message compression and decompression; SIP message forwarding between the UE and the IMS core; and policy control and media authorization.

The Serving-Call Session Control Function (S-CSCF) is central to session control in IMS. It performs session control and registration for the users; interacts with the Home Subscriber Server (HSS) to download user profiles; and ensures proper routing of SIP messages to application servers and other network elements.

The Interrogating-Call Session Control Function (I-CSCF) is responsible for determining the S-CSCF for a given user by querying the HSS; handling routing of SIP messages to the appropriate S-CSCF; and serving as the contact point within an operator’s network for connections with other networks.

IMS manages multimedia sessions using: SIP (for session signalling and control); SDP (for negotiating session parameters such as codec and media types); and RTP (for delivering real-time audio and video streams).

Application Servers (AS) in IMS host and execute multimedia services. They provide services such as VoIP, video conferencing, messaging and presence; interact with the S-CSCF for session control; and implement service logic and business rules.

Fixed-Mobile Convergence (FMC) in IMS refers to the seamless integration of fixed and mobile networks, allowing users to access services regardless of their access network. IMS achieves FMC through: a Common IP core (using the same IP-based infrastructure for both fixed and mobile services); Unified services (offering consistent services across different network types); and Seamless handover (enabling uninterrupted service continuity when moving between networks).

Session Initiation Protocol (SIP) in IMS is used for: Session Management (initiating, modifying and terminating multimedia sessions); Registration (handling user registration and maintaining the user’s location information); and Presence (providing real-time status information about users’ availability and willingness to communicate).

The Policy and Charging Rules Function (PCRF) plays a crucial role in: Policy Control (enforcing network policies for QoS, access control and resource allocation); and Charging Control (managing real-time charging decisions and ensuring proper billing based on service usage and policies).

AAA stands for Authentication, Authorization and Accounting. It is the framework that verifies who a subscriber or device is (authentication), determines what they are allowed to access (authorization), and keeps track of their usage of network resources (accounting). In mobile networks, AAA is essential for granting secure access to services across different access types.

Summa Networks AAA provides Diameter-based authentication, authorization and accounting for secure network access. It is designed for scenarios such as VoWiFi, IoT devices and non-3GPP access, and can be deployed as a standalone entity or integrated with the Summa Networks HSS.

Summa Networks AAA is based on the Diameter base protocol defined by the IETF in RFC 6733, providing a standards-based AAA framework for applications such as network access and IP mobility, in both local and roaming situations.

Yes. Summa Networks AAA can operate as a standalone function or be integrated with the Summa Networks HSS, giving operators flexibility to add AAA capabilities on their own terms and evolve their core at their own pace.