Description
Service Change and UDI/RDI Fallback (SCUDIF) is a network service capability defined within the 3GPP architecture, primarily documented in specifications such as TS 23.018 and TS 23.172. It operates within the core network, specifically involving the Mobile Switching Centre (MSC) and the Gateway MSC (GMSC), to handle scenarios where a requested bearer service or teleservice cannot be established as initially intended. The mechanism is invoked during call setup or service modification procedures. When the network determines that the requested service (e.g., a specific data rate or multimedia service) is not available due to terminal capabilities, network congestion, or inter-system handovers, SCUDIF triggers a fallback procedure. This procedure attempts to establish an alternative, typically more basic, bearer service. The fallback targets either an Unrestricted Digital Information (UDI) bearer, which supports transparent data transfer, or a Restricted Digital Information (RDI) bearer, often used for fax services. The selection between UDI and RDI is based on the original service request and network policies.
The architectural role of SCUDIF is integral to service negotiation and mobility management. It interacts with protocols like BSSAP (Base Station System Application Part) and ISUP (ISDN User Part) to communicate service change decisions between the MSC, GMSC, and the radio access network. Key components involved include the call control function within the MSC, which evaluates service compatibility, and the interworking functions that adapt the bearer service parameters. SCUDIF is particularly important in legacy circuit-switched domains, ensuring that calls do not fail outright when advanced services are unavailable, thereby improving call completion rates and user experience.
In operation, SCUDIF follows a defined sequence. Upon receiving a service request, the network performs compatibility checks. If incompatibility is detected, the MSC may initiate a service change notification to the calling and called parties, indicating a modification to the bearer capability. Subsequently, it attempts to establish a fallback connection using UDI or RDI parameters. This process may involve negotiation with the remote end and potentially modifying the traffic channel in the radio access network. SCUDIF's role extends to handover scenarios between GSM and other systems (like PSTN), where service continuity must be maintained despite differing service support. Its implementation ensures backward compatibility and smooth interworking between network elements of varying capabilities, which is a cornerstone of robust telecommunications service design.
Purpose & Motivation
SCUDIF was introduced to address critical issues of service interoperability and call completion in heterogeneous and evolving mobile networks. In the early phases of GSM and UMTS deployment, networks and user equipment supported a wide range of bearer services and teleservices, from basic voice to various data services. However, not all network nodes or subscriber terminals supported every advanced service. Without a fallback mechanism, a call or session requesting an unsupported service would simply fail, leading to poor user experience and inefficient network resource utilization. SCUDIF was created to solve this by providing a standardized procedure to gracefully downgrade to a commonly supported basic digital bearer service (UDI or RDI), ensuring the call could proceed, albeit with potentially reduced capabilities.
The historical context lies in the transition from analog to digital cellular systems and the introduction of supplementary services. As 3GPP Release 99 and subsequent releases expanded service offerings, the need for robust service negotiation became paramount. Previous approaches often relied on static service profiles or led to call drops, which were unacceptable for commercial telephony. SCUDIF formalized a dynamic fallback process, allowing networks to adapt to limitations in terminal capabilities, network congestion, or inter-system handovers (e.g., to a PSTN network that only supports basic digital services). This was especially important for facilitating roaming and inter-operator connectivity, where service support could vary significantly.
By addressing these limitations, SCUDIF enhanced network reliability and user satisfaction. It allowed operators to deploy new services incrementally without breaking existing calls, supporting a smoother evolution path. The mechanism also played a role in optimizing network resources by preventing unnecessary call setup failures and subsequent re-attempts, thereby improving overall network efficiency and service availability.
Detected Changes Across Releases
from 3GPP Change RequestsSpecific changes extracted from the „Change history“ tables of 3GPP specifications (5 CRs across 3 releases). Complements the general historical overview above with the evidence-based evolution of this function.
In Release 16, the SCUDIF function was updated with a correction to the serving node change procedure and addressed a missing trigger for Guaranteed Flow Bit Rate (GFBR) status changes. These enhancements ensure service continuity during inter-system changes between different radio access technologies. The updates focus on maintaining the user experience during such transitions without noticeable interruption.
In Release 17, the specific update for the SCUDIF function was a change to the abbreviation of "DN." The term "DN" was redefined to stand for both "Data Network" and "Distinguished Name," changing from its previous sole meaning of "Destination Network." This was an editorial clarification within the 3GPP vocabulary with no associated technical procedure changes noted for SCUDIF in the provided context.
- Change of abbreviation of DN from Destination Network to Data Network and Distinguished Name TS 21.905CR0125
In Release 18, the SCUDIF (Service Continuity for UDI/RDI Fallback) function was enhanced to ensure charging session continuity identification specifically during a v-SMF change. This update provides a mechanism to maintain consistent charging records when the virtualized Session Management Function serving a user is relocated, which is a key scenario in modern disaggregated 5G core networks. The change ensures service continuity for a user's data session is seamlessly supported from a charging perspective during such network function changes.
- Rel-18 CR 32.298 QBC Charging Session Continuity Identification at v-SMF Change TS 32.298CR0962
Explore further
Broader topics and technologies where SCUDIF plays a role.
Defining Specifications
3GPP specifications that define or reference SCUDIF, with the latest known release. Sourced from the 3GPP document catalog — see methodology.
| Specification | Title | Release |
|---|---|---|
| TR 21.905 vj00 | 3GPP Technical Terms and Definitions | Rel-19 |
| TS 23.018 vj00 | Basic call handling in 3GPP CS domain | Rel-19 |
| TS 23.172 vj00 | Service Change and UDI Fallback (SCUDIF) | Rel-19 |
| TS 23.231 vj00 | SIP-I based CS core network stage 2 | Rel-19 |
| TS 32.250 vj00 | Circuit Switched Offline Charging | Rel-19 |
| TS 32.298 vj30 | Charging Data Record (CDR) Parameter Specification | Rel-19 |